Ben Hutchings <firstname.lastname@example.org> (2014-10-06): > 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. I disagree with the code deletion. It makes it harder to combine various d-i components across distributions to support as many use cases as possible. Keeping a few old lines of shell code shouldn't be a problem. > > 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. I started using this successfully but then I stumbled upon issues with WPA2 (which turned out to be missing modules as we now know), and got to publish Jessie Beta 2. So the current logging situation might not be ideal yet but it seems sufficient to vastly improve the current state of affairs. Mraw, KiBi.
Description: Digital signature