On Mon, 2014-10-06 at 15:37 +0200, Petter Reinholdtsen wrote: > I noticed this bug was mentioned as a regression in the Jessie > installer, and thought I should have a look at how this could be > improved from the hw-detect side. > > The following patch replaces the code looking in > /dev/.udev/firmware-missing and /run/udev/firmware-missing for firmware > wanted by the kernel with code looking for firmware listed in the > meta-info of loaded modules. That seems like a good idea. > It will solve the problem for at least > some kernel modules, but not the class of modules refusing to load if > their firmware files are missing. I'm not aware that there are any of those. > Perhaps something do use while we wait for more information from the > kernel side? [...] I'm afraid I'm unlikely to implement the proposed structured logging in time for jessie, and the installer would need some work to make use of structured log data. However the firmware core code is already patched so that it logs all failure in a consistent format that you can grep for: "firmware: failed to load %s (%d)" The parameters are the filename and negative error code; usually that will be -ENOENT == -2. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong.
Attachment:
signature.asc
Description: This is a digitally signed message part