Just now got to a Windows machine to test Fluppy003 -- bootinst.sh didn't work for my thumbdrive (using Linux).
I am not seeing any wireless access points... oh wait... I think I see why. If you look at the b43 folder now located in /lib/firmware/, you will notice that the next level down in that b43 directory is a directory named 'lib' -- and inside that directory is a directory called 'firmware' -- and inside that directory is the base b43 directory. So the base directory located at /lib/firmware/b43/lib/firmware/b43 really should be /lib/firmware/b43. Might also need the tar.gz in /lib/modules/all-firmware to function, although this is a personal gut feeling rather than a firm statement ATM. Does the b43.tar.gz have to be in /lib/modules/all-firmware to register or something? I seem to recall an issue with an earlier kernel where the tar.gz was supposed to automatically extract from /lib/modules/all-firmware to /lib/firmware/ .... or something to that effect. Maybe I don't know enough about it.
The good news is that creating a 128MB save file on the thumbdrive did not wipe out the ability to reboot this time around.
Let me play with this a bit longer....
-Roy
EDIT: dmesg is still telling me
Code: Select all
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000
b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel configuration.
#