Summary: | zd1211rw firmware fails to load on my system (SIOCSIFFLAGS: No such file or directory) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Tom Lloyd <napalmllama> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | xmw |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic-p-6330115.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Tom Lloyd
2010-06-25 01:33:52 UTC
hi, you should have CONFIG_FW_LOADER=y on the system, and you can compile the fw files into the kernel blob file. For example CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="iwlwifi-3945-2.ucode microcode.dat" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" This removes the dependency on the external firmware loader support via `/sbin/hotplug`. You should check that this file exists as `/lib/firmware/zd1211/zd1211b_ub` on both systems. That's all info I can provide, I've no experience with hardened sources/GrSec/PaX. Can you please report back if this doesn't help? I'll assign it to hardened@ then. Thanks, Michael Nowadays it is udev's responsibility to get the firmware loaded, so checking out udev is a good place to start. Let's start out with 'emerge --info' output and also 'emerge -pv udev' on this box. First check is whether udev looks new enough, and then we can turn on debugging to verify whether udev is actually receiving the firmware load events. I don't run udev on that system any more, so that's probably it. Udev went badly wrong a while ago, rendering the system unbootable. I turned it off and this is the first repurcussion I've had. I'll try compiling-in the blob, see if that works. Ok, that explains it. Compiling in the firmware should work. Ok to close this bug as solved? Yep, sorry :) |