Red Hat Bugzilla – Bug 428580
zd1211rw driver is omitted
Last modified: 2008-02-02 05:21:01 EST
Description of problem:
The zd1211rw driver is needed to support my new Belkin Wireless USB adapter.
It's been there, working; now it's gone.
Version-Release number of selected component (if applicable):
It's not there!
Steps to Reproduce:
1. Plug in USB adapter; note that the kernel sees a new USB device.
2. Run ifup wlan0
3. Error message: Device wlan0 does not seem to be present.
Activation and connection.
What's going on with the zd1211rw driver?
In Fedora 8 it is omitted entirely from the latest kernel-18.104.22.168-85.fc8
The immediately prior kernel provides
which works fine on an i386 system.
On Fedora 7, x86_64, the penultimate kernel, 22.214.171.124-34.fc7, provides
zd1211rw-mac80211.ko, while the ultimate kernel, 126.96.36.199-52.fc7,
has switched to zd1211rw.ko. Unfortunately neither seems to work on my
I recently purchased a Belkin Wireless G USB network adapter, part No.
F5D7050, and was pleased to find it was supported by the zd1211rw
driver. However, there seems to be some churning with this software
and I am dismayed to see that only some combinations of kernel and
driver seem usable.
I hope the omission from kernel-188.8.131.52-85.fc8 was merely inadvertent.
Can it be restored?
you are true!
Thx for reporting this.. Actually you have reported it to the wrong component
(firmware instead of the kernel).
But later kernels have it re-enabled. So i suggest to use koji to get a newer
kernel (there is no newer kernel in updates-testing for now) or take an older one..
Upstream the zd1211rw transformed into what had been the zd1211rw-mac80211.
Unfortunately I flubbed the configuration when moving this change into the F8
kernels starting at -80.fc8.
As kwizart suggests, this was resolved starting with the -86.fc8 kernel. As
soon as any newer version becomes available in updates we should see this
issue no more...
In the meantime, I suggest using a kernel from Koji:
*** This bug has been marked as a duplicate of 428660 ***
*** Bug 429392 has been marked as a duplicate of this bug. ***