Why is USB WiFi device support so poor?

[kutuup]

I'm completely new to Linux, but have enough computing experience to notice that the support for USB WiFi devices with Raspbian is pretty poor.

I've tried three different devices all from different manufacturers now, all of which publish Linux drivers, but none of them seem to be compatible with Raspbian as far as I can see. I've had varying success with each, but never actually managed to build the drivers for any of them successfully.

Be it readme files that lead to non-existant web addresses (not the fault of Raspbian, I know) for required files, or kernel version incompatability, getting my Pi connected to wifi is seeming like a fading dream

The latest device and driver I've tried in a Belkin f5d6050, which purports to have Linux support. I managed to track down the drivers for the specific chipset, an Atmel one, the driver is at76_usb-0.17.

When trying to run make on it via the console in Raspbian, I get an error stating that the kernel at the given address is not configured.

Checking the readme file indicated that you need firmware for the device in order to build the driver. It points to the url: http://developer.berlios.de/projects/at76c503a/.

That's a non-existant address.

Another dead end, sadly, it seems.

[fruitoftheloom]

I'm completely new to Linux, but have enough computing experience to notice that the support for USB WiFi devices with Raspbian is pretty poor.

I've tried three different devices all from different manufacturers now, all of which publish Linux drivers, but none of them seem to be compatible with Raspbian as far as I can see. I've had varying success with each, but never actually managed to build the drivers for any of them successfully.

Be it readme files that lead to non-existant web addresses (not the fault of Raspbian, I know) for required files, or kernel version incompatability, getting my Pi connected to wifi is seeming like a fading dream

The latest device and driver I've tried in a Belkin f5d6050, which purports to have Linux support. I managed to track down the drivers for the specific chipset, an Atmel one, the driver is at76_usb-0.17.

When trying to run make on it via the console in Raspbian, I get an error stating that the kernel at the given address is not configured.

Checking the readme file indicated that you need firmware for the device in order to build the driver. It points to the url: http://developer.berlios.de/projects/at76c503a/.

That's a non-existant address.

Another dead end, sadly, it seems.

https://www.raspberrypi.org/products/usb-wifi-dongle

[kutuup]

That doesn't exactly help. I'm not looking to buy another WiFi device that may or may not work. The problem is I can't get my apparently supported device working.

It's hardly helpful to respond to someone looking for help repairing their Ford by linking them to a website where they can buy an Audi.

[NormanDunbar]

Greetings kutuup,

are you running Jessie or Wheezy? In other words, which Raspbian are you running please?
Much of what you need is different between the two versions. Not Raspbian's fault, it came from Debian changes.

Have you updated to the most recent release of your current version?

Code: Select all

sudo apt-get update
sudo apt-get upgrade

Can you see your device when it is plugged in?

Code: Select all

lsusb

Check out this topic for information the could help:
viewtopic.php?f=28&t=127972

It's a start, but without knowing which Raspbian you are running, helping could be difficult.


Cheers,
Norm.

[fruitoftheloom]

That doesn't exactly help. I'm not looking to buy another WiFi device that may or may not work. The problem is I can't get my apparently supported device working.

It's hardly helpful to respond to someone looking for help repairing their Ford by linking them to a website where they can buy an Audi.

Linux does not have Drivers like Windows you need to have a totally different approach....

With Linux when you plug in a USB Device the outputs of the following will give information to help locate the correct driver / firmware

Code: Select all

lsusb

Code: Select all

uname -a

...as well as the Operating System - Raspbian ??

Therefore there are many Wireless Chipsets supported by the Linux Kernel, and some only need a firmware install.

Regards Linux Drivers many manufacturers only list for x86 Architecture, not for ARM Archectiture of the RPi, and many ignore Linux altogether..

Fortunateley we have many community developers, see: https://wireless.wiki.kernel.org

This is outdated but shows many Chipsets are supported on the RPi http://elinux.org/RPi_USB_Wi-Fi_Adapters

[kutuup]

Greetings kutuup,

are you running Jessie or Wheezy? In other words, which Raspbian are you running please?
Much of what you need is different between the two versions. Not Raspbian's fault, it came from Debian changes.

Have you updated to the most recent release of your current version?

Code: Select all

sudo apt-get update
sudo apt-get upgrade

Can you see your device when it is plugged in?

Code: Select all

lsusb

Check out this topic for information the could help:
viewtopic.php?f=28&t=127972

It's a start, but without knowing which Raspbian you are running, helping could be difficult.


Cheers,
Norm.

I'm using whichever version is installed by the newest release of NOOBS, there doesn't seem to be any indication of which version it is anywhere. How can I find out what version I have? It's not in the readme as far as I can see, and the configuration information doesn't seem to specify which it is.

I've run sudo apt-get update, which ran successfully, but given that I have no internet connection, if it searches online for updates, it's not going to get very far.

The device shows up when I run lsusb, but it is throwing an error due to drivers not being available.

[kutuup]

That doesn't exactly help. I'm not looking to buy another WiFi device that may or may not work. The problem is I can't get my apparently supported device working.

It's hardly helpful to respond to someone looking for help repairing their Ford by linking them to a website where they can buy an Audi.

Linux does not have Drivers like Windows you need to have a totally different approach....

With Linux when you plug in a USB Device the outputs of the following will give information to help locate the correct driver / firmware

Code: Select all

lsusb

Code: Select all

uname -a

...as well as the Operating System - Raspbian ??

Therefore there are many Wireless Chipsets supported by the Linux Kernel, and some only need a firmware install.

Regards Linux Drivers many manufacturers only list for x86 Architecture, not for ARM Archectiture of the RPi, and many ignore Linux altogether..

Fortunateley we have many community developers, see: https://wireless.wiki.kernel.org

This is outdated but shows many Chipsets are supported on the RPi http://elinux.org/RPi_USB_Wi-Fi_Adapters

Now we're getting somewhere.

Apologies for the bluntness of my previous reply, but I'm looking to understand why the device I'm trying to run isn't working, rather than just buying another device.

The OS is Raspbian.

Using lsusb shows the device as installed, but not running due to missing drivers or firmware.

I've downloaded the Linux firmware for the device, but installing it seems to be an uphill battle. The files include an installer, but running it fails. There is also a .bin file for the firmware, but using sudo apt-get install <filename> returns an error saying the package can't be found, so I've hit a dead end there.

[gregeric]

I know that posting the output of lsusb & uname -a may be difficult if you do not have an active network, and apt-get update/upgrade impossible.

Can you connect with ethernet so that you can copy/paste from the Pi? If not redirect their output by adding >/boot/lsusb.txt to create a text file of the output that your PC can read (remove the microSD & your PC will see the /boot folder & the text files).

You'll need to run them as root to be able to write to /boot so:

Code: Select all

sudo lsusb > /boot/lsusb.txt
sudo uname -a > /boot/uname.txt

[kutuup]

I know that posting the output of lsusb & uname -a may be difficult if you do not have an active network, and apt-get update/upgrade impossible.

Can you connect with ethernet so that you can copy/paste from the Pi? If not redirect their output by adding >/boot/lsusb.txt to create a text file of the output that your PC can read (remove the microSD & your PC will see the /boot folder & the text files).

You'll need to run them as root to be able to write to /boot so:

Code: Select all

sudo lsusb > /boot/lsusb.txt
sudo uname -a > /boot/uname.txt

Unfortunately not, I'm using a Pi Zero, so there is no Ethernet port. I can run the commands to write the output to a txt file anyway if the output might be of some help even without an Ethernet connection.

[gregeric]

Code: Select all

sudo dmesg > /boot/dmesg.txt

may help as well if it turns out firmware is missing.

[jamesh]

It sounds like the device you have requires a binary block to be downloaded to the adapter to make it work correctly. So there linux driver is probably there, but the driver cannot find the binary blob that needs to be on the wireless adapter itself to make it work.

So likely you will need to find that binary blob from somewhere, install it to the correct place (you'l need to google for that, I cannot remember off hand), and then things should work.

Or, spend a few pounds and get a wireless device that works without the hassle. The Nano dongle advertised by Pi sellers works well.

[kutuup]

Code: Select all

sudo dmesg > /boot/dmesg.txt

may help as well if it turns out firmware is missing.

I get a permission denied message if I do that.

[kutuup]

I'm starting to think this WiFi adapter may be more trouble than it's worth to get working. God only knows why manufacturers put out hardware that is utterly inhuman to use without the specific installers that they then promptly discontinue I will never know. I find that Belkin are particularly good at issuing hardware that can't be used without endless mandatory proprietary software that they support for about 15 minutes and then axe, leaving the hardware basically inoperable.

[gregeric]

I get a permission denied message if I do that.

Same here when I tried it - I'm sure someone will chime in as to why. Instead,

Code: Select all

dmesg > dmesg.txt
sudo cp dmesg.txt /boot/

Now attach each of those txt files in your reply.

Don't give up, we are bound to get one of your adapters going...

[kutuup]

I get a permission denied message if I do that.

Same here when I tried it - I'm sure someone will chime in as to why. Instead,

Code: Select all

dmesg > dmesg.txt
sudo cp dmesg.txt /boot/

Now attach each of those txt files in your reply.

Don't give up, we are bound to get one of your adapters going...

OK, the txt file was created successfully, here it is. Had to put it in a 7z archive since .txts aren't allowed for attachment.

There seems to be a message at timing 2.957622 stating insufficient power to use a device during the initialization of the USB hub.

That would explain why the device isn't working if it is the WiFi adapter that there isn't enough power for, but it still leaves a question mark over why the drivers and firmware are not installing correctly.

What would you suggest from here?

[gregeric]

Is it an unpowered USB hub? Any possibility to try another, powered hub?

[fruitoftheloom]

Drawing to much power can be an issue with some adaptors.....

What model of RPi do you have, if a 1B+ or 2B then increase USB max current:

https://projects.drogon.net/testing-set ... berry-pi-b

Any other model of RPi then use a Mains Powered Hub......

As pointed out below you have RPi0

[gregeric]

poppycock

If you took the trouble to read the thread it's a Pi Zero.

[fruitoftheloom]

poppycock

If you took the trouble to read the thread it's a Pi Zero.

Not very original cut & paste

[gregeric]

Yes, mea cupla, but it's the word you've used to describe my forum posts when I pointed out that a wiring diagram for an OTG cable wasn't the most relevant to a question about USB client mode, nor my correct knowledge of VAT rules. Sorry OP, but as you have discovered, fotl has a tendency to rush in without reading & prescribe pointless advice.

[NormanDunbar]

There seems to be a message at timing 2.957622 stating insufficient power to use a device during the initialization of the USB hub.

That would explain why the device isn't working if it is the WiFi adapter that there isn't enough power for, but it still leaves a question mark over why the drivers and firmware are not installing correctly.

The output from lsusb will show you details of vendor and product I'd, so run that command, as see what turns up for id 050d:0050 which should indicate the WiFi device or not.

If it is the WiFi dongle, then I assume that because it didn't have enough power, the the firmware couldn't be loaded onto it to make it work. In which case I'd be looking for a powered Usb hub, or, a beefier 5v usb power supply. What's the output volts and amps/milliamps printed on the label of your power supply?

EDIT: updated expected output from lsusb to match potential reality!

Cheers,
Norm.

[MrEngman]

There seems to be a message at timing 2.957622 stating insufficient power to use a device during the initialization of the USB hub.

That would explain why the device isn't working if it is the WiFi adapter that there isn't enough power for, but it still leaves a question mark over why the drivers and firmware are not installing correctly.

What would you suggest from here?

I would suggest you change the port your wifi is connected to in your Belkin hub. Take a look at page 3 of the hubs manual. In the Technical Specifications it states that ports 1 and 2 have a max current limit of 100ma which is probably why you are seeing the current limit message unless using an external power supply.

So seems your hub is not allowing the wifi USB to connect.


MrEngman

[kutuup]

OK, so it seems like it's a power supply issue.

I'll try powering the USB hub (it has an AC port although it's not mandatory) and see what happens then.

I'll report back once I've tried that.

[stderr]

That doesn't exactly help. I'm not looking to buy another WiFi device that may or may not work. The problem is I can't get my apparently supported device working.

A lot of times, there is tons of fun with wifi and Linux. It's not just the pi version. It's almost but not quite as fun as Windows.

It's hardly helpful to respond to someone looking for help repairing their Ford by linking them to a website where they can buy an Audi.

I think they've probably removed the code from their computers that tries to trick the EPA. So might want to dump the Ford and get the Audi.

[kutuup]

So I tried powering the USB hub, and it promptly burst into flames.

Not even joking lol

Sooo it looks like I need a new USB hub now.

I have no idea what went wrong, I just plugged it into the Pi, plugged the AC adapter into the hub, connected the devices, and suddenly, mankind's first discovery was on my desk.

Luckily the Pi and the devices survived, but the hub is now a melted blob :S

Any ideas what could have gone so intensely wrong??