I get the following problem when generating a livecd from this catalyst project: https://tor-svn.freehaven.net/svn/incognito/trunk/ but I think it should affect all livecds. /etc/init.d/autoconfig extracts /lib/firmware.tar.bz2 into /lib/firmware too late, so when drivers using firmwares are loaded, the firmware cannot be found. In my case it's with the ipw2200 module, but it should affect all firmware dependent drivers. To fix this, I have tried the two following workarounds with success: 1. Interrupt the boot process (by pressing I) before the autoconfig service is started, entering a shell and manually unpacking the firmware: # tar xfj /lib/firmware.tar.bz2 -C /lib/firmware Then continue the boot process. 2. Modify /etc/init.d/autoconf so that the first thing it does on service start is to run the unpack_firmware subroutine. You can probably figure out a more elegant solution than this as this most likely extracts the firmwares twice. I guess the problem is that 'hwsetup -p' on row 267 (in /etc/init.d/autoconfig) run before the firmwares are unpacked on rows 357 to 372. Reproducible: Always Steps to Reproduce: 1. generate a livecd with catalyst (and livecd-tools-1.0.35-r1) and some hardware driver that requires firmware (e.g. put CONFIG_IPW2200 in the kernel config and install net-wireless/ipw2200-firmware) 2. boot livecd on a computer with some of the above hardware (e.g. an Intel 2200BG wireless card) 3. curse when you find out that the module failed to load as the firmware was missing! (e.g. look at errors shown by the output from dmesg | grep ipw2200) Actual Results: Drivers to hardware detected by autoconfig/hwsetup that require firmwares fail to load correctly. Expected Results: Drivers using firmware should load correctly.
Created attachment 129899 [details, diff] Moves coldplug/hotplug/firmware unpack to before hardware probe. I attach a patch which works for me. It simple moves the coldplug/hotplug/firmware unpack section to very early in the autoconfig service start.
I've added this to SVN... thanks for the patch!
OK. This is in 1.0.36 which was just added to the tree.
