Red Hat Bugzilla – Bug 428660
kernel 220.127.116.11-85.fc8 is missing zd1211rw
Last modified: 2008-02-06 15:07:27 EST
Description of problem:
As stated in the summary kernel 18.104.22.168-85.fc8 is missing zd1211rw, making it
impossible to use wireless usb dongles using this chipset with this kernel
Also it seems that FC-7 has a newer kernel then F-8, it currently has a
22.214.171.124 based kernel (or it seems), this kernel does include zd1211rw.
Actually -85.fc8 has zd1211rw, but it does not have zd1211rw-mac80211.
Starting with -86.fc8 there is a MODULE_ALIAS for zd1211rw-mac80211 in the
zd1211rw module, resolving this issue. It is unfortunate that -85.fc8 got
pushed to updates instead of -86.fc8, and even more unfortunate that there has
been no update since. (How does that process work anyway?)
Using any F8 kernel available in Koji with a version later than -85.fc8 should
resolve this issue.
(In reply to comment #1)
> Actually -85.fc8 has zd1211rw, but it does not have zd1211rw-mac80211.
No it doesn't (I think):
[hans@localhost ~]$ cd /lib/modules/126.96.36.199-85.fc8/
[hans@localhost 188.8.131.52-85.fc8]$ find -name '*zd1112rw*'
> Starting with -86.fc8 there is a MODULE_ALIAS for zd1211rw-mac80211 in the
> zd1211rw module, resolving this issue.
This shouldn't be necessary, its an usb device and should get autoloaded on its
usb id's whatever the name, it seems that neither version of the module is
present in 184.108.40.206-85.fc8 .
Yes I was mistaken about -85 having zd1211rw. Still, the point remains -- use
a later kernel.
(In reply to comment #3)
> Yes I was mistaken about -85 having zd1211rw. Still, the point remains -- use
> a later kernel.
I didn't report this for myself, but on behalf of a college of mine who had this
problem. For him a less experienced Fedora user, doing so is less then trivial
if such a kernel is not available from updates. Sure I can help him, but there
are bound to be lots of other people bitten by this. Any chance we could get a
fixed kernel out? For example -86 (assuming that has fixing this as only change,
and thus little chance of causing other issues).
As for your question in comment 1 how the update process work, normally one goes to:
Logs in with once Fedora Account System account and creates the update, how this
goes for the kernel with regard to coordinating this with the other Fedora
kernel developers/maintainers I do not know.
220.127.116.11-115 is in testing now and this should be fixed in that version.
*** Bug 428580 has been marked as a duplicate of this bug. ***
I can confirm that the module is back in 18.104.22.168-115, I downloaded it from
koji though as:
And mirrors, don't have it yet.