PDA

View Full Version : zd1211b driver will not work with Network Manager


btw9979
27th March 2011, 02:50 AM
Hi,
This is my first post on the forum but I am really stumped on this one. I am running Fedora 14 and I am trying to configure the Wi-Fire device from hfield technologies that claims that it supports linux right out of the box but I can not get it to work properly with network manager. It appears to be loading the drivers up properly but I don't know how to troubleshoot the message below that I am getting in my /var/log/messages. I have an ethernet connection to the pc for now just to remain online. The zd1211b driver is loaded for wlan0. Any help is greatly appreciated.

Travis

Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> Activation (wlan0) starting connection 'System DXHY0 (wlan0)'
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Mar 26 21:37:07 melanie2 NetworkManager[1229]: <info> (wlan0): bringing up device.
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <info> (wlan0): device state change: 5 -> 9 (reason 4)
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <warn> Activation (wlan0) failed for access point (DXHY0)
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <info> Marking connection 'System DXHY0 (wlan0)' invalid.
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <warn> Activation (wlan0) failed.
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <info> (wlan0): device state change: 9 -> 3 (reason 0)
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <info> (wlan0): deactivating device (reason: 0).
Mar 26 21:37:08 melanie2 kernel: [ 4770.057087] usb 2-2: USB control request for firmware upload failed. Error number -110
Mar 26 21:37:08 melanie2 kernel: [ 4770.057095] usb 2-2: Could not upload firmware code uph. Error number -110
Mar 26 21:37:08 melanie2 kernel: [ 4770.057111] zd1211rw 2-2:1.0: couldn't load firmware. Error number -110
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.
Mar 26 21:37:08 melanie2 NetworkManager[1229]: <info> Policy set 'Auto eth0' (eth0) as default for IPv4 routing and DNS.

stoat
27th March 2011, 03:06 AM
There is a zd1211rw driver module included with Fedora kernels. But if you plugged that thing in after you installed Fedora, the firmware package may not be installed. You can confirm the kernel module is being loaded with this...lsmod | sortYou can confirm the firmware package is installed with this...rpm -q zd1211-firmwareIf that does not return a version number, then connect by wire and install it...su
yum install zd1211-firmwareOr you can get it from the Fedora DVD or download it using another computer, transfer it to the wireless computer, and manually install it...su
rpm -ivh zd1211-firmware-1.4-4.fc13.noarch.rpmThat fc13 version is the most current version and still shipped with Fedora 14. Anyway, after that, reboot or restart NetworkManager and check the panel icon for networks.

P.S.: I'm using a ZyXel G-202 USB wireless adapter in Fedora 13, Fedora 14, Debian Lenny, Debian Squeeze with the zd1211rw kernel module, and I had to do nothing more than install the firmware which is also on the Fedora and Debian installation disks and in both repos.

btw9979
27th March 2011, 03:50 AM
I have the firmware installed. I tried uninstalling it just to see what kind of error message I would get and I get an error code of 2 instead of 110. From everything I have read, the firmware is supposed to be installed under /lib/firmware/zd1211. I have verified that it is there. Any other ideas? I also confirmed that when I plug in the usb cable that the driver is loading with lsmod. I also tried stopping Network Manager and bringing up wlan0 but I get an RTNETLINK error about the connection timing out. It does not take long maybe .5 seconds. The messages from the kernel in /var/log/messages are consistent. I also tried setenforce=0 just to make sure selinux wasn't causing any issue with that firmware loading and I got the same results. I really don't know why it looks like it loads fine when plugging the cable in but it dies when I try to initialize the interface. Below is my ifcfg-wlan0 if it helps.

DEVICE=wlan0
IPADDR=192.168.9.79
NETMASK=255.255.255.0
ONBOOT=yes
BOOTPROTO=static
#
# wireless config
#
TYPE=Wireless
MODE=Managed
ESSID=DXHY0
#RATE=54Mb/s
KEY=<secret code>

---------- Post added at 10:50 PM ---------- Previous post was at 10:46 PM ----------

This is some output I get when performing "ifup wlan0":

[root@melanie2 zd1211]# ifup wlan0

** (process:3978): WARNING **: Error in getting active connection 'Vpn' property: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist


** (process:3978): WARNING **: _nm_object_array_demarshal: couldn't create object for /org/freedesktop/NetworkManager/ActiveConnection/1

** (process:3978): WARNING **: Error in getting active connection 'Vpn' property: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist


** (process:3978): WARNING **: _nm_object_array_demarshal: couldn't create object for /org/freedesktop/NetworkManager/ActiveConnection/1

** (process:3978): WARNING **: Error in getting active connection 'Vpn' property: (19) Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist


** (process:3978): WARNING **: _nm_object_array_demarshal: couldn't create object for /org/freedesktop/NetworkManager/ActiveConnection/1
Error: Obtaining active connection for '/org/freedesktop/NetworkManager/ActiveConnection/1' failed.
[root@melanie2 zd1211]#

stoat
27th March 2011, 04:45 AM
Do you have to use a static IP address? And have you been entering things in the old Network Configuration utility (system-config-network) or manually editing its config files? I recommend that you not do either of those things if you want to use NetworkManager to control the interface. The only thing that you really need to do in system-config-network is edit the wireless connection and check "Controlled by NetworkManager" and UNcheck "Activate device when computer starts". It's still great for preconfiguring an interface that will be managed manually or with scripts, but it can knock the slats out of NetworkManager (IMO). Since I started using NetworkManager, I never open that any more. And my various ifcfg-wlan0 files have almost nothing in them, and what little is in them was not put there by me. I can find threads where undoing all of that stuff let NetworkManager take off. Just something to consider.

btw9979
27th March 2011, 01:31 PM
I don't have to use a static ip but I was trying to simplify the problem as much as possible. I have been editing my ifcfg file by hand for wlan0. I tried viewing it through system-config-network and it does see wlan0 (ZyDAS ZD1211B 802.11g) as being an interface on the system. I also tried simplifying my configuration as you suggested and it still did not work. Below is the info from /var/log/messages with your suggested changes applied to ifcfg via system-config-network.

Mar 27 08:26:27 melanie2 kernel: [ 1980.152088] usb 2-2: USB control request for firmware upload failed. Error number -110
Mar 27 08:26:27 melanie2 kernel: [ 1980.152097] usb 2-2: Could not upload firmware code uph. Error number -110
Mar 27 08:26:27 melanie2 kernel: [ 1980.152111] zd1211rw 2-2:1.0: couldn't load firmware. Error number -110
Mar 27 08:26:28 melanie2 kernel: [ 1981.190066] usb 2-2: USB control request for firmware upload failed. Error number -110
Mar 27 08:26:28 melanie2 kernel: [ 1981.190074] usb 2-2: Could not upload firmware code uph. Error number -110
Mar 27 08:26:28 melanie2 kernel: [ 1981.190088] zd1211rw 2-2:1.0: couldn't load firmware. Error number -110
Mar 27 08:26:29 melanie2 kernel: [ 1982.331183] usb 2-2: USB control request for firmware upload failed. Error number -110
Mar 27 08:26:29 melanie2 kernel: [ 1982.331192] usb 2-2: Could not upload firmware code uph. Error number -110
Mar 27 08:26:29 melanie2 kernel: [ 1982.331206] zd1211rw 2-2:1.0: couldn't load firmware. Error number -110
Mar 27 08:26:29 melanie2 dhclient[13855]: receive_packet failed on wlan0: Network is down
Mar 27 08:26:30 melanie2 dhclient[13855]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
Mar 27 08:26:30 melanie2 dhclient[13855]: send_packet: Network is down
Mar 27 08:26:33 melanie2 dhclient[13855]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
Mar 27 08:26:33 melanie2 dhclient[13855]: send_packet: Network is down
Mar 27 08:26:41 melanie2 dhclient[13855]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
Mar 27 08:26:41 melanie2 dhclient[13855]: send_packet: Network is down
Mar 27 08:27:02 melanie2 dhclient[13855]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
Mar 27 08:27:02 melanie2 dhclient[13855]: send_packet: Network is down
Mar 27 08:27:19 melanie2 dhclient[13855]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
Mar 27 08:27:19 melanie2 dhclient[13855]: send_packet: Network is down
Mar 27 08:27:29 melanie2 dhclient[13855]: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
Mar 27 08:27:29 melanie2 dhclient[13855]: send_packet: Network is down
Mar 27 08:27:31 melanie2 dhclient[13855]: No DHCPOFFERS received.



I believe that if I can find out what error 110 means then I will be headed down the right path toward fixing this. I have no idea where to look for that though.

stoat
27th March 2011, 02:06 PM
It's up to you, of course, but I recommend that you download and create a Fedora 14 Live CD. Maybe you already have one. It's good to have one for emergencies and maintenance of the hard drive system anyway. Then plug in that zd1211 wireless device and boot with the live CD. See if it works in that clean environment. Left-click the NetworkManager panel icon and look for available networks. Try to connect. If that worked, then I would go back to the hard drive system and delete the wireless connection in system-config-network, reboot, and start over with just NetworkManager. The wireless connection may be automatically recreated in system-config-network, but leave it and its text config files alone this time. In the case of my zd1211 wireless device, NetworkManager needs no help from me at all. Anyway, if I'm wrong about it in your situation, then that's good for us both to know, too. And you end up with a live CD that may come in handy someday for something else.

btw9979
27th March 2011, 04:11 PM
Unfortunately, I have already tried that option. This is my third wifi card I have tried to get working with fedora with no success. The first was a netgear card the second the linksys ae1000 neither of which have linux support. The reason I bought this particular card is that it claimed that there are modules built into the kernel that support the card. This seems to hold true and it loads the appropriate driver when the usb cable is plugged in. I have even tried a fresh fedora 14 install with the device plugged in just to see if anaconda had some magical detection technique that would help me configure it. I am currently searching for information that will help me troubleshoot why I am getting those unable to load firmware messages. I think /var/log/messages is all I have at the moment and unless I have someway to cross-reference those error codes I am SOL.

bbfuller
27th March 2011, 04:30 PM
I don't have any experience with that chipset, but if it was mine, I'd get the firmware listed here:

http://linuxwireless.org/en/users/Drivers/zd1211rw

and try that just in case there is a problem with what you have.

It should be a simple cut and paste job, and if it makes no difference it would be easy to put things back the way they were.

I suppose you have verified the card works elsewhere?

stoat
27th March 2011, 04:43 PM
Just for the record and other readers who may know something specific for you to try, take a moment to identify the wireless device by brand name and model number, and then by vendor and device numbers in the lsusb output.

Try searching Google with this..."couldn't load firmware. Error number -110". Nearly every item (maybe all of them) relates to the zd1211. There are some interesting things to read regarding different chipset versions, kernel versions, and so on. Also, linuxwireless.org has a fairly informative zd1211 section for general information on the status of its developement, supported devices, etc.

The firmware package hasn't been updated in a long time, I think. But you could try updating your Fedora kernel. It couldn't make things any worse and will eventually need to be done anyway.

btw9979
27th March 2011, 05:55 PM
Here is the line from lsusb:

Bus 002 Device 007: ID 0ace:1215 ZyDAS ZD1211B 802.11g

I had not verified that the card actually did work yet, so I found a win7 netbook and installed the manufacturers driver software on it. It took forever (win7+netbook = super slow) but worked fine.

The card is from hField Technologies and the part number is HFWFG200. The card is called the Wi-Fire Long-Range WiFi adapter.

stoat
27th March 2011, 06:28 PM
Okay. I realize that I'm not helping, but here is an example of a possible issue. It seems that zd211 chipsets are paired with various RF transceiver chips that also have to be programmed by the zd1211 driver. I guess not all RF chips are known to the Linux driver developers. I'm interested because I use an adapter with the zd1211 chipset. Apparently the USB vendor and device numbers are of no use regarding the RF chip which can vary. So I guess I was lucky because I didn't know about this detail concerning the driver...http://wireless.kernel.org/en/users/Drivers/zd1211rw/RFtypesMaybe you can dig something useful out of that stuff, or maybe at least pinpoint the problem if it is related to the RF chip.

btw9979
27th March 2011, 10:52 PM
You guys have both pointed me in the right direction and I appreciate your help. According to hfield, the RF chipset is a UW2453 (http://www.hfield.com/the-wi-fire/platform-compatibility/linux/). I found a thread for a debian bug that gave me a brief glimmer of hope where a guy says that the RF chip is being falsely identified by the driver and provided a small bit of c code to add to the driver in order to get it to load up correctly but my driver already had the code in it. Do you know of anywhere else I can seek help with this? Would this qualify as a bug?

stoat
28th March 2011, 12:07 AM
Do you know of anywhere else I can seek help with this?I wish I did. Really.

Here is the RF chip from the dmesg output for my ZyXel G-202 adapter (for the record). It's the "S" version of the AL2230...$ dmesg | grep zd1211
[ 11.053170] zd1211rw 4-2:1.0: phy0
[ 11.053218] usbcore: registered new interface driver zd1211rw
[ 18.575186] usb 4-2: firmware: requesting zd1211/zd1211b_ub
[ 18.965357] usb 4-2: firmware: requesting zd1211/zd1211b_uphr
[ 19.218069] zd1211rw 4-2:1.0: firmware version 4725
[ 19.257992] zd1211rw 4-2:1.0: zd1211b chip 0586:3410 v4810 high 40-4a-03 AL2230_RF pa0 g--NSAccording to linuxwireless.org, your U2453 RF chip also has been around for several years, and support for it was added to the mainline kernel long ago. So the thing should be working.



Would this qualify as a bug?I don't know. Maybe. But it still could be something unique to your situation that needs to be figured out.

When you tried the Fedora live CD, did the same exact firmware messages appear? Or did it just not work?

I'm using my ZyXel adapter right now in Debian Squeeze (kernel 2.6.32). It also works well in Debian Lenny also on this same Thinkpad (kernel 2.6.26). I like Debian. It stays a step or two behind Fedora regarding kernel and package versions. I hardly ever tell people to do this, but if you have the interest and mental energy for it, you could try it with Debian. I have no logical reason to suggest that. It's a desperate guess. No promises, of course.

P.S.: FWIW, and for the record, here is the contents of my /lib/firmware/zd1211 folder in Debian...$ ls -l /lib/firmware/zd1211
total 64
-rw-r--r-- 1 root root 4018 Oct 4 2007 zd1211b_ub
-rw-r--r-- 1 root root 5120 Oct 4 2007 zd1211b_uph
-rw-r--r-- 1 root root 5120 Oct 4 2007 zd1211b_uphm
-rw-r--r-- 1 root root 5120 Oct 4 2007 zd1211b_uphr
-rw-r--r-- 1 root root 3584 Oct 4 2007 zd1211b_ur
-rw-r--r-- 1 root root 4018 Oct 4 2007 zd1211_ub
-rw-r--r-- 1 root root 5120 Oct 4 2007 zd1211_uph
-rw-r--r-- 1 root root 5120 Oct 4 2007 zd1211_uphm
-rw-r--r-- 1 root root 5120 Oct 4 2007 zd1211_uphr
-rw-r--r-- 1 root root 3584 Oct 4 2007 zd1211_ur

Carshalton Travel Photos on Instagram - Rio Bonito Instagram Photos - Kostrzyn nad Odra Photos