> >> I put the firmware file in the firmware dir of the kernel src tree >> and changed >> CONFIG_EXTRA_FIRMWARE_DIR accordingly and recompiled. > > > As the example:
> > CONFIG_FIRMWARE_IN_KERNEL=y > CONFIG_EXTRA_FIRMWARE='iwlwifi-6000-4.ucode' > CONFIG_EXTRA_FIRMWARE_DIR='/lib/firmware' > > Another possibility that wasn't working are the permissions of the > firmware directory and or firmware file. > May want to check it is readable by the user which is building > configuring and building the kernel. Yes I did check that after it failed to work. The permissions are the standard ones - /lib/firmware is 755 and the ucode binary is 644. I assumed the binary doesn't have to be executable in this case as it it only being read. Interestingly, I put the ucode binary in the firmware dir of the kernel source tree but left CONFIG_EXTRA_FIRMWARE_DIR blank, assuming the kernel make would find it by default. It didn't, but it did find it when I added the location to CONFIG_EXTRA_FIRMWARE_DIR. Also, even more interestingly, there is a text file in the kernel source tree firmware dir called README.AddingFirmware, whose first line reads: DO NOT ADD FIRMWARE TO THIS DIRECTORY I guess we all have to manage with a modicum of confusion eh! jb. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
