Ask Your Question

Revision history [back]

This looks like a documentation bug. I built using the instructions for generating firmware, and, as described above, no firmware rpm was generated, although the build completed successfully. I did the install as documented, with the exception that I didn't try to install the non-existent firmware rpm. (Tangentially, the kernel header install issued many failures complaining about header file conflicts.) I rebooted anyway and voila! there was my kernel in the grub menu, and my kernel booted fine. I'm not sure if the firmware build is a noop or not, but the system will boot a renamed kernel without explicitly installing the documemted but not generated firmware file.