Those two ebuilds put the firmware files in /usr/lib/hotplug/ and should place them in /lib/firmware to work with the new hotplug script ! See bug http://bugs.gentoo.org/show_bug.cgi?id=64869 Reproducible: Always Steps to Reproduce: 1. emerge hotplug-20040920 2. try to modprobe ipw2200 or ipw2100 Actual Results: Fails because firmware isn't loaded Expected Results: should modprobe fine
I'll try to come up with a patch for the ipw ebuild which detects the version of hotplug installed - and places the firmware in the correct place.
Detecting the version is not really a good solution. Imagine: emerge stable hotplug; emerge ipw2100; upgrade hotplug.. *broken* For now, we should put the file in where the stable hotplug expects it, and symlink to it in the new location. Eventually we trade those roles, and once all the older versions of hotplug are removed from portage, we can zap the symlink.
Same problems for DVB drivers from kernel. Kernel (2.6.8) doc still states that firmware should be in /usr/lib/hotplug/firmware, but hotplug scripts search in /lib/firmware How about symlinking?? /lib/firmware -> /usr/lib/hotplug/firmware /usr/lib/hotplug/firmware -> /lib/firmware
Fixed in the ebuild for version 0.11.
This has not been fixed for the ipw2100 yet.
Ok. I added the symlinks to ipw2100-0.55-r2. I've added the symlinks the other way around though (firmware files in /lib/firmware, symlinks in /usr/lib/hotplug/firmware) since /lib/ will always be mounted at boot time but /usr might not be. I suggest the ipw2200-0.11.ebuild is changed to do this as well.
I agree with Henrix (#6). For instance, I have LVM2 set up. The default behavior, even with the "old" hotplug, is that the ipw2200 firmware is not loaded at boot, because /usr (an LVM volume) is not yet available. So I have been putting the firmware in /lib and symlinking from /usr/lib with the "old" hotplug anyway. I'm sure others can imagine even more cases where it would be desirable to have the firmware in /lib rather than just symlinked.
Care to change the owner of this to the owner of the firmware packages, that's not me...
Reassigning to mobile@g.o
I have the ipw2100 firmware in /lib/firmware but after a recent hotplug update (I am currently using sys-apps/hotplug-20040923) it's not found anymore: wopr-mobile ~ # ls -la /lib/firmware total 616 drwxr-xr-x 2 root root 184 Oct 14 18:40 . drwxr-xr-x 10 root root 4248 Oct 15 04:17 .. -rw-r--r-- 1 root root 11880 Oct 14 18:40 ipw2100-1.3-LICENSE -rw-r--r-- 1 root root 201138 Oct 14 18:40 ipw2100-1.3-i.fw -rw-r--r-- 1 root root 196458 Oct 14 18:40 ipw2100-1.3-p.fw -rw-r--r-- 1 root root 209190 Oct 14 18:40 ipw2100-1.3.fw ipw2100: 0000:02:0a.0: Detected at mem: 0xC2005000-0xC2005FFF -> e1940000, irq: 11 eth1: Using hotplug firmware load. eth1: Firmware 'ipw2100-1.3.fw' not available or load failed. eth1: ipw2100_get_firmware failed: -2 eth1: Failed to power on the adapter. eth1: Failed to start the firmware.
I had the same problem, and reverting to udev-36 solved the issue, so it might be udev-38 related.
I too got problems with udev 038, reverting to 036 worked for me
Concerning the udev problem, I've opened a new bug #65059 for this issue. Please track that problem/discussion there, as it's not a ipw2{100,200} problem, but a problem in general with firmware uploading and this version of udev (my prism54 also breaks with that version of udev). Thanks.
*** Bug 67664 has been marked as a duplicate of this bug. ***
net-wireless/ipw2200-0.12 installs firmware to /lib/firmware and symlinks to /usr/lib/hotplug/firmware. Closing as FIXED.