WiFi adapter question.

[ViolentMonk]

Would it be easy enough to disable the onboard WiFi and use a different adapter for a raspberry 3b? Was wanting to use a adapter with 5ghz. If someone knows a adapter that will work without a ton of configuration that would be a plus. Also would a adapter need external power? Thank you for the info!

[igorpec]

Also would a adapter need external power?

Dual stream 8812au, which might work with a proper driver, needs up to 600mA. For dual stream AC adaptor you need external powering, while some N or single stream AC @5Ghz it might work.

[broe23]

Yes you can if you wish. A lot of people use a usb adapter instead of the onboard.

[mattmiller]

The problem is finding a 5GHz adaptor that will will work with a Pi.

AFAICR - I've not seen anyone post with success in trying to do that

[sparkie777]

CSL 300Mbit Dual Band USB WLAN / 300Mbps / 5 GHz Dual Band USB WiFi Adapter works here either as client or AP without issues so far (RPi3 with Raspbian/stretch).

Unfortunately I haven't found yet an Atheros based 5GHz Wifi Adaptor suitable for RPi.

lsusb:

Code: Select all

Bus 001 Device 007: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter

iw phy:

Code: Select all

Wiphy phy1
        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.
        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)
        Available Antennas: TX 0 RX 0
        Supported interface modes:
                 * IBSS
                 * managed
                 * AP
                 * AP/VLAN
                 * WDS
                 * monitor
                 * mesh point
        Band 1:
                Capabilities: 0x2fe
                        HT20/HT40
                        SM Power Save disabled
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 2-streams
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 2 usec (0x04)
                HT RX MCS rate indexes supported: 0-15, 32
                TX unequal modulation not supported
                HT TX Max spatial streams: 2
                HT TX MCS rate indexes supported may differ
                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] (33.0 dBm)
                        * 2417 MHz [2] (33.0 dBm)
                        * 2422 MHz [3] (33.0 dBm)
                        * 2427 MHz [4] (33.0 dBm)
                        * 2432 MHz [5] (33.0 dBm)
                        * 2437 MHz [6] (33.0 dBm)
                        * 2442 MHz [7] (33.0 dBm)
                        * 2447 MHz [8] (33.0 dBm)
                        * 2452 MHz [9] (33.0 dBm)
                        * 2457 MHz [10] (33.0 dBm)
                        * 2462 MHz [11] (33.0 dBm)
                        * 2467 MHz [12] (33.0 dBm)
                        * 2472 MHz [13] (33.0 dBm)
                        * 2484 MHz [14] (33.0 dBm)
        Band 2:
                Capabilities: 0x2fe
                        HT20/HT40
                        SM Power Save disabled
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        RX STBC 2-streams
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 2 usec (0x04)
                HT RX MCS rate indexes supported: 0-15, 32
                TX unequal modulation not supported
                HT TX Max spatial streams: 2
                HT TX MCS rate indexes supported may differ
                Bitrates (non-HT):
                        * 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:
                        * 5180 MHz [36] (33.0 dBm)
                        * 5190 MHz [38] (33.0 dBm)
                        * 5200 MHz [40] (33.0 dBm)
                        * 5210 MHz [42] (33.0 dBm)
                        * 5220 MHz [44] (33.0 dBm)
                        * 5230 MHz [46] (33.0 dBm)
                        * 5240 MHz [48] (33.0 dBm)
                        * 5250 MHz [50] (33.0 dBm)
                        * 5260 MHz [52] (33.0 dBm)
                        * 5270 MHz [54] (33.0 dBm)
                        * 5280 MHz [56] (33.0 dBm)
                        * 5290 MHz [58] (33.0 dBm)
                        * 5300 MHz [60] (33.0 dBm)
                        * 5310 MHz [62] (33.0 dBm)
                        * 5320 MHz [64] (33.0 dBm)
                        * 5500 MHz [100] (33.0 dBm)
                        * 5510 MHz [102] (33.0 dBm)
                        * 5520 MHz [104] (33.0 dBm)
                        * 5530 MHz [106] (33.0 dBm)
                        * 5540 MHz [108] (33.0 dBm)
                        * 5550 MHz [110] (33.0 dBm)
                        * 5560 MHz [112] (33.0 dBm)
                        * 5570 MHz [114] (33.0 dBm)
                        * 5580 MHz [116] (33.0 dBm)
                        * 5590 MHz [118] (33.0 dBm)
                        * 5600 MHz [120] (33.0 dBm)
                        * 5610 MHz [122] (33.0 dBm)
                        * 5620 MHz [124] (33.0 dBm)
                        * 5630 MHz [126] (33.0 dBm)
                        * 5640 MHz [128] (33.0 dBm)
                        * 5650 MHz [130] (33.0 dBm)
                        * 5660 MHz [132] (33.0 dBm)
                        * 5670 MHz [134] (33.0 dBm)
                        * 5680 MHz [136] (33.0 dBm)
                        * 5690 MHz [138] (33.0 dBm)
                        * 5700 MHz [140] (33.0 dBm)
                        * 5745 MHz [149] (33.0 dBm)
                        * 5755 MHz [151] (33.0 dBm)
                        * 5765 MHz [153] (33.0 dBm)
                        * 5775 MHz [155] (33.0 dBm)
                        * 5785 MHz [157] (33.0 dBm)
                        * 5795 MHz [159] (33.0 dBm)
                        * 5805 MHz [161] (33.0 dBm)
                        * 5825 MHz [165] (33.0 dBm)
                        * 4920 MHz [184] (disabled)
                        * 4940 MHz [188] (disabled)
                        * 4960 MHz [192] (disabled)
                        * 4980 MHz [196] (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
                 * set_tx_bitrate_mask
                 * frame
                 * frame_wait_cancel
                 * set_wiphy_netns
                 * set_channel
                 * set_wds_peer
                 * probe_client
                 * set_noack_map
                 * register_beacons
                 * start_p2p_device
                 * set_mcast_rate
                 * 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:
                 * #{ AP, mesh point } <= 8,
                   total <= 8, #channels <= 1
        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
        Driver supports full state transitions for AP/GO clients
        Driver supports a userspace MPM
        Device supports configuring vdev MAC-addr on create.

[mattmiller]

CSL 300Mbit Dual Band USB WLAN works here either as client or AP without issues so far (RPi3 with Raspbian/stretch).

Excellent news

Do you know what chipset it uses?

[sparkie777]

please read carefully (1 post above your question)

lsusb:

Code: Select all

Bus 001 Device 007: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter

[mattmiller]

#EpicFail

[mattmiller]

Was it plug and play or did it need driver compilation?

[sparkie777]

My system is Raspbian/ stretch based. You must have installed the package 'firmware-misc-nonfree'. I don't know if that is the case for the standard Raspbian image. From that package the adapter requires firmware file: '/lib/firmware/rt2870.bin'.

It's plug and play. No driver compilation needed. You may even hot swap adapters ('TL-WN722N' and 'CSL 300Mbit Dual Band USB' in my case). I just have to restart 'hostapd' and the access point is up and running again after the swap. For this to work flawlessly you may want to read my howto

[ViolentMonk]

Is there a supplier in the US for the adapter listed or equivalent? Also did this need a external power source?

[sparkie777]

an external power source is neither required nor supported. I can't tell if this piece of hardware is available in the US.

[davidcoton]

Despite one of the posts above suggesting an external PSU, this is unlikely to be necessary.
The Pi's USB sockets are not limiting to 500mA each, but to 1.2A total (some models vary or need configuration).
So a device drawing 600mA will work without power problems unless other USB peripherals draw more than another 600mA in total.

[igorpec]

Despite one of the posts above suggesting an external PSU, this is unlikely to be necessary.
The Pi's USB sockets are not limiting to 500mA each, but to 1.2A total (some models vary or need configuration).
So a device drawing 600mA will work without power problems unless other USB peripherals draw more than another 600mA in total.

If you are lucky, it will work fine otherwise you can waste time and blame drivers ... since with 600mA + Pi3 consumption, you can be near to the edge of (everyday crappy) micro USB connector/cable/PSU combo. Pi1 and Pi2 should not be affected by this problem I guess.

RA5572 or 3572 are also working good on Linux in general and consume less.

[mattmiller]

Found this one - the 3 reviews point to it being plug and play

https://www.modmypi.com/raspberry-pi/co ... -band-5ghz

[jamesh]

Despite one of the posts above suggesting an external PSU, this is unlikely to be necessary.
The Pi's USB sockets are not limiting to 500mA each, but to 1.2A total (some models vary or need configuration).
So a device drawing 600mA will work without power problems unless other USB peripherals draw more than another 600mA in total.

If you are lucky, it will work fine otherwise you can waste time and blame drivers ... since with 600mA + Pi3 consumption, you can be near to the edge of (everyday crappy) micro USB connector/cable/PSU combo. Pi1 and Pi2 should not be affected by this problem I guess.

You should be fine using a 600mA USB device on PI3. Just ensure your power supply and supply cable are decent quality. It's not a question of luck, but of common sense.

[davidcoton]

Despite one of the posts above suggesting an external PSU, this is unlikely to be necessary.
The Pi's USB sockets are not limiting to 500mA each, but to 1.2A total (some models vary or need configuration).
So a device drawing 600mA will work without power problems unless other USB peripherals draw more than another 600mA in total.

If you are lucky, it will work fine otherwise you can waste time and blame drivers ... since with 600mA + Pi3 consumption, you can be near to the edge of (everyday crappy) micro USB connector/cable/PSU combo. Pi1 and Pi2 should not be affected by this problem I guess.

RA5572 or 3572 are also working good on Linux in general and consume less.

Bit late now, but I should have added, to supply 600mA to USB you must have a good PSU and USB power cable for the Pi, capable of 2A at 5V on the Pi end of the cable.
The official PSU is rated 5.1V 2.5A, which allows for the full 1.2A USB load.
Many USB chargers cannot maintain 5V at the rated current, and this can cause problems for USB peripherals

[igorpec]

The official PSU is rated 5.1V 2.5A, which allows for the full 1,2A USB load.

Even without firmware undervoltage protection kicking in?

It's not a question of luck, but of common sense.

Average Joe must have EE knowledge or at least understanding of ohm laws to make use of common sense. Micro USB connector suggests that one can make use of old phone charger to power the board. Commons sense tells him if its rated > 2.5A and can obviously charge the phone and Pi is running fine ... Just a few days ago we had a similar discussion in a local forum and that was average Joe's defense ... how typical.

I am always using lab PSU but experience tells me to not trust micro USB connector to deliver enough juice. So I use a quality powered USB hub for everything that is expected to consume little more power.

When dealing with software development - which compiling and debugging wireless driver is, you want to get rid of such "it must work" bullshit.

[rpdom]

The official PSU is rated 5.1V 2.5A, which allows for the full 1,2A USB load.

Even without firmware undervoltage protection kicking in?

The default is 1.2A now.

[davidcoton]

The official PSU is rated 5.1V 2.5A, which allows for the full 1,2A USB load.

Even without firmware undervoltage protection kicking in?

Yes, that is my point. The official PSU with an attached power lead is properly designed and will deliver 2.5A while maintaining 5V at the Pi. That is plenty for the USB 1.2A as well as the Pi's needs. The undervoltage warning (not actually protection, only detection) only comes on when the supply is not delivering enough voltage.