Bug 428660
| Summary: | kernel 2.6.23.9-85.fc8 is missing zd1211rw | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Hans de Goede <hdegoede> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 8 | CC: | dad, linville |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 2.6.23.14-115.fc8 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-02-06 20:07:27 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Hans de Goede
2008-01-14 14:04:15 UTC
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/2.6.23.9-85.fc8/ [hans@localhost 2.6.23.9-85.fc8]$ find -name '*zd1112rw*' [hans@localhost 2.6.23.9-85.fc8]$ > 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 2.6.23.9-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: https://admin.fedoraproject.org/updates/new/ 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. 2.6.23.14-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 2.6.23.14-115, I downloaded it from koji though as: http://download.fedora.redhat.com/pub/fedora/linux/updates/testing/8/i386/ And mirrors, don't have it yet. |