How to detect Wi-Fi adapter capabilities

Questions about hardware, drivers and peripherals.
In the Original Post please also include the output of inxi -Fzx
User avatar
palimmo
Posts: 763
Joined: 19 Nov 2013 19:44
Contact:

How to detect Wi-Fi adapter capabilities

Postby palimmo » 17 Mar 2018 17:01

Is there an easy way to detect your Wi-Fi adapter's capabilities on Linux?
I want to check if my wireless card supports IEEE 802.11 ac and/or n.

Thanks!

Code: Select all

~$ inxi -FNzxx
System:    Host: solydxk Kernel: 4.9.0-6-amd64 x86_64 (64 bit gcc: 6.3.0)
           Desktop: KDE Plasma 5.8.6 (Qt 5.7.1) dm: lightdm Distro: SolydXK                
Machine:   Device: laptop System: Packard Bell product: EasyNote TJ65 v: 0100              
           Mobo: Packard Bell model: SJV50MV v: Rev                                        
           BIOS: Phoenix v: V1.28 date: 10/06/2009                                         
           Chassis: type: 10                                                               
Battery    BAT0: charge: 9.8 Wh 100.0% condition: 9.8/45.0 Wh (22%) volts: 12.2/10.8       
           model: Panasonic AS09A51 serial: 1082 status: Full                              
CPU:       Dual core Pentium T4300 (-MCP-) cache: 1024 KB                                  
           flags: (lm nx sse sse2 sse3 ssse3) bmips: 8379                                  
           clock speeds: min/max: 1200/2100 MHz 1: 1600 MHz 2: 2100 MHz
Graphics:  Card: NVIDIA G98M [GeForce G 105M] bus-ID: 01:00.0 chip-ID: 10de:06ec
           Display Server: X.Org 1.19.2 driver: nvidia Resolution: 1366x768@59.97hz
           GLX Renderer: GeForce G 105M/PCIe/SSE2
           GLX Version: 3.3.0 NVIDIA 340.106 Direct Rendering: Yes
Audio:     Card Intel 82801I (ICH9 Family) HD Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:293e
           Sound: Advanced Linux Sound Architecture v: k4.9.0-6-amd64
Network:   Card-1: Broadcom Limited NetLink BCM5784M Gigabit Ethernet PCIe
           driver: tg3 v: 3.137 bus-ID: 02:00.0 chip-ID: 14e4:1698
           IF: enp2s0 state: down mac: <filter>
           Card-2: Qualcomm Atheros AR928X Wireless Network Adapter (PCI-Express)
           driver: ath9k bus-ID: 03:00.0 chip-ID: 168c:002a
           IF: wlp3s0 state: up mac: <filter>
Drives:    HDD Total Size: 320.1GB (61.2% used)
           ID-1: /dev/sda model: WDC_WD3200BEVT size: 320.1GB
           serial: WD-WX70E99ED623 temp: 56C
Partition: ID-1: / size: 12G used: 8.3G (78%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 4.25GB used: 0.00GB (0%) fs: swap dev: /dev/sda7
Sensors:   System Temperatures: cpu: 61.0C mobo: 61.0C gpu: 0.0:61C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 184 Uptime: 3:42 Memory: 1606.3/3951.3MB
           Init: systemd v: 232 runlevel: 5 default: 2 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121 running in konsole) inxi: 2.3.5 
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

User avatar
Arjen Balfoort
Site Admin
Posts: 8718
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: How to detect Wi-Fi adapter capabilities

Postby Arjen Balfoort » 17 Mar 2018 17:38

Try:

Code: Select all

sudo iwconfig
and

Code: Select all

sudo iw list


SolydXK needs you!
Development | Testing | Translations

User avatar
palimmo
Posts: 763
Joined: 19 Nov 2013 19:44
Contact:

Re: How to detect Wi-Fi adapter capabilities

Postby palimmo » 17 Mar 2018 17:51

Code: Select all

~$ sudo iwconfig
[sudo] 
enp2s0    no wireless extensions.

wlp3s0    IEEE 802.11  ESSID:"o2-WLAN55"  
          Mode:Managed  Frequency:2.432 GHz  Access Point: 1C:74:0D:60:EE:3B   
          Bit Rate=120 Mb/s   Tx-Power=16 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=36/70  Signal level=-74 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:164   Missed beacon:0

lo        no wireless extensions.

Code: Select all

~$ sudo iw list
Wiphy phy0
        max # scan SSIDs: 4
        max scan IEs length: 2257 bytes
        max # sched scan SSIDs: 0
        max # match sets: 0
        max # scan plans: 1
        max scan plan interval: -1
        max scan plan iterations: 0
        Retry short limit: 7
        Retry long limit: 4
        Coverage class: 0 (up to 0m)
        Device supports RSN-IBSS.
        Device supports AP-side u-APSD.
        Device supports T-DLS.
        Supported Ciphers:
                * WEP40 (00-0f-ac:1)
                * WEP104 (00-0f-ac:5)
                * TKIP (00-0f-ac:2)
                * CCMP-128 (00-0f-ac:4)
                * CCMP-256 (00-0f-ac:10)
                * GCMP-128 (00-0f-ac:8)
                * GCMP-256 (00-0f-ac:9)
                * CMAC (00-0f-ac:6)
                * CMAC-256 (00-0f-ac:13)
                * GMAC-128 (00-0f-ac:11)
                * GMAC-256 (00-0f-ac:12)
        Available Antennas: TX 0x3 RX 0x3
        Configured Antennas: TX 0x3 RX 0x3
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
                 * P2P-client
                 * P2P-GO
                 * outside context of a BSS
        Band 1:
                Capabilities: 0x11ce
                        HT20/HT40
                        SM Power Save disabled
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT TX/RX MCS rate indexes supported: 0-15
                Bitrates (non-HT):
                        * 1.0 Mbps
                        * 2.0 Mbps (short preamble supported)
                        * 5.5 Mbps (short preamble supported)
                        * 11.0 Mbps (short preamble supported)
                        * 6.0 Mbps
                        * 9.0 Mbps
                        * 12.0 Mbps
                        * 18.0 Mbps
                        * 24.0 Mbps
                        * 36.0 Mbps
                        * 48.0 Mbps
                        * 54.0 Mbps
                Frequencies:
                        * 2412 MHz [1] (16.0 dBm)
                        * 2417 MHz [2] (16.0 dBm)
                        * 2422 MHz [3] (16.0 dBm)
                        * 2427 MHz [4] (16.0 dBm)
                        * 2432 MHz [5] (16.0 dBm)
                        * 2437 MHz [6] (16.0 dBm)
                        * 2442 MHz [7] (16.0 dBm)
                        * 2447 MHz [8] (16.0 dBm)
                        * 2452 MHz [9] (16.0 dBm)
                        * 2457 MHz [10] (16.0 dBm)
                        * 2462 MHz [11] (16.0 dBm)
                        * 2467 MHz [12] (16.0 dBm) (no IR)
                        * 2472 MHz [13] (16.0 dBm)
                        * 2484 MHz [14] (disabled)
        Supported commands:
                 * new_interface
                 * set_interface
                 * new_key
                 * start_ap
                 * new_station
                 * new_mpath
                 * set_mesh_config
                 * set_bss
                 * authenticate
                 * associate
                 * deauthenticate
                 * disassociate
                 * join_ibss
                 * join_mesh
                 * remain_on_channel
                 * set_tx_bitrate_mask
                 * frame
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * tdls_mgmt
                 * tdls_oper
                 * probe_client
                 * set_noack_map
                 * register_beacons
                 * start_p2p_device
                 * set_mcast_rate
                 * channel_switch
                 * set_qos_map
                 * connect
                 * disconnect
        Supported TX frame types:
                 * IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
                 * P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
        Supported RX frame types:
                 * IBSS: 0x40 0xb0 0xc0 0xd0
                 * managed: 0x40 0xd0
                 * AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * mesh point: 0xb0 0xc0 0xd0
                 * P2P-client: 0x40 0xd0
                 * P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
                 * P2P-device: 0x40 0xd0
        software interface modes (can always be added):
                 * AP/VLAN
                 * monitor
        valid interface combinations:
                 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1,
                   total <= 2048, #channels <= 1, STA/AP BI must match
                 * #{ WDS } <= 2048,
                   total <= 2048, #channels <= 1, STA/AP BI must match
        HT Capability overrides:
                 * MCS: ff ff ff ff ff ff ff ff ff ff
                 * maximum A-MSDU length
                 * supported channel width
                 * short GI for 40 MHz
                 * max A-MPDU length exponent
                 * min MPDU start spacing
        Device supports TX status socket option.
        Device supports HT-IBSS.
        Device supports SAE with AUTHENTICATE command
        Device supports low priority scan.
        Device supports scan flush.
        Device supports AP scan.
        Device supports per-vif TX power setting
        P2P GO supports CT window setting
        Driver supports full state transitions for AP/GO clients
        Driver supports a userspace MPM
        Device supports active monitor (which will ACK incoming frames)
        Driver/device bandwidth changes during BSS lifetime (AP/GO mode)
        Device supports configuring vdev MAC-addr on create.
any idea? :?
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

User avatar
palimmo
Posts: 763
Joined: 19 Nov 2013 19:44
Contact:

Re: How to detect Wi-Fi adapter capabilities

Postby palimmo » 22 Mar 2018 16:26

help please...

I want to be sure I can use with no problems these:

https://www.netcologne.de/privatkunden/ ... rvergleich
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

User avatar
Arjen Balfoort
Site Admin
Posts: 8718
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: How to detect Wi-Fi adapter capabilities

Postby Arjen Balfoort » 22 Mar 2018 16:43

Sorry, I have no idea what commands can show you more info about your adapter.
The only thing you can now do is to check for information on the net. Laptop name and series usually help and if it's home-built you'll have to open the box and check the chipset of the adapter.


SolydXK needs you!
Development | Testing | Translations


User avatar
palimmo
Posts: 763
Joined: 19 Nov 2013 19:44
Contact:

Re: How to detect Wi-Fi adapter capabilities

Postby palimmo » 23 Mar 2018 20:13

thanks kurotsugi.
it should be b / g / n.
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

User avatar
palimmo
Posts: 763
Joined: 19 Nov 2013 19:44
Contact:

Re: How to detect Wi-Fi adapter capabilities

Postby palimmo » 26 Mar 2018 15:36

However I am not sure if it can work both on 2,4 GHz and 5 GHz.... :?
Proud user of SolydK!

Dai diamanti non nasce niente, dal letame nascono i fior. http://aquilone.wordpress.com/

kurotsugi
Posts: 2043
Joined: 09 Jan 2014 00:17

Re: How to detect Wi-Fi adapter capabilities

Postby kurotsugi » 27 Mar 2018 08:55

AFAIK all routers works on 2,4. you can use it for better compatibility. though, the default (automatic) setting usually works fine.


Return to “Hardware”

Who is online

Users browsing this forum: No registered users and 1 guest