On Saturday 26 December 2009, Jurij Smakov wrote:
The problem here is that empty $modules does not mean that there are
no files in $MISSING which is set to /dev/.udev/firmware-missing (the
log message is wrong as well).
Nice analysis Jurij.
A lot (most?) devices do have a driver directory
On Saturday 26 December 2009, Jurij Smakov wrote:
The logic in check_missing() function appends the missing firmware
file name to the $files list and the module to $modules list. However,
if such mapping fails (as in this case), nothing is appended to $files
or $modules, and the file is simply
It turns out that the installer does offer an option to load firmware
from external drive, but only *after* I have loaded the firmware by
hand and re-ran 'Detect disks' option from installer menu.
--
Jurij Smakov ju...@wooyd.org
Key:
On Saturday 26 December 2009, Jurij Smakov wrote:
It turns out that the installer does offer an option to load firmware
from external drive, but only *after* I have loaded the firmware by
hand and re-ran 'Detect disks' option from installer menu.
There are calls to a script 'check missing
On Sat, Dec 26, 2009 at 05:03:03PM +0100, Frans Pop wrote:
On Saturday 26 December 2009, Jurij Smakov wrote:
It turns out that the installer does offer an option to load firmware
from external drive, but only *after* I have loaded the firmware by
hand and re-ran 'Detect disks' option from
5 matches
Mail list logo
