On Wed, Jun 18, 2014 at 6:25 PM, Ronald <ronald645@xxxxxxxxx> wrote: > From my .config > > ==> cat /usr/src/config | grep -i b43 > CONFIG_EXTRA_FIRMWARE="b43/ucode5.fw b43/b0g0initvals5.fw > b43/b0g0bsinitvals5.fw b43/pcm5.fw" > ... snip ... That might be rather later, but I seem to have the same problem: CHK kernel/config_data.h MK_FW firmware/amd-ucode/microcode_amd.bin.gen.S /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory /bin/sh: firmware/amd-ucode/microcode_amd.bin.gen.S: No such file or directory firmware/Makefile:185: recipe for target 'firmware/amd-ucode/microcode_amd.bin.gen.S' failed make[1]: *** [firmware/amd-ucode/microcode_amd.bin.gen.S] Error 1 Makefile:896: recipe for target 'firmware' failed make: *** [firmware] Error 2 The directory firmware/amd-ucode does not exist in the kernel source tree, but my .config seems to need it: CONFIG_EXTRA_FIRMWARE="radeon/R700_rlc.bin radeon/RV710_uvd.bin radeon/RV730_smc.bin amd-ucode/microcode_amd.bin" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" Just doing a "mkdir firmware/amd-ucode" lets the build continue and I get a working 3.16 kernel. With 3.15 and earlier I never had a problem with this, but 3.16-rc4 just failed with above message. Do you need my full .config or any other information about my system? I would be happy to provide that and/or test a patch. Thanks for looking into this! Torsten -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
