clone 492205 -1 reassign -1 hw-detect retitle -1 firmware listed multiple times during firmware loading severity -1 minor clone 492205 -2 ressaign -2 hw-detect retitle -2 install more firmware packages than required severity -2 normal clone 492205 -3 reassign -3 hw-detect retitle -3 installation firmware packages with dependencies fails in post-base-installer hook severity -3 grave clone 492205 -4 reassign -4 hw-detect retitle -4 does not handle firmware packages for other architectures on media severity -4 important thanks
On Thu, Jul 24, 2008 at 05:41:17AM -0600, dann frazier wrote: > Thanks for adding the firmware support! I finally got around to > testing it out w/ one of the dailies & thought I'd write up the issues > I ran into in case any of them aren't yet known. Thanks for your detailed report. As we are trying to polish things up for Lenny, this is definitely worthwhile. Would you be able to do other test installations as we fix the issue you have encountered here? (I am leaving this bug report opened in order to allow follow-up.) > Unable to mount usb stick > ------------------------- This issue is already known. See #490562. > fw file dups on error > --------------------- > minor - but each time I returned to the "should i look for firmware" > screen, the displayed list would include more copies of the same > filenames. To illustrate, see the following screen shots: > http://free.linux.hp.com/~dannf/d-i-20080723/missing-fw-1.png > http://free.linux.hp.com/~dannf/d-i-20080723/missing-fw-2.png > http://free.linux.hp.com/~dannf/d-i-20080723/missing-fw-3.png Assigned to hw-detect. I see two possible fix: * make firmware.agent idempotent while adding files to /tmp/missing-firmware, * call "sort -u" or "uniq" in check-missing-firmware.sh:read_log(). > fails to install fw debs into target > ------------------------------------ > I lazily dumped all of the fw debs from the firmware.tar.gz onto my > stick instead of just the one I needed (bnx2). This caused problems > during the base install: > http://free.linux.hp.com/~dannf/d-i-20080723/busybox-error.png > […] > Full syslog file: > http://free.linux.hp.com/~dannf/d-i-20080723/syslog Ok, various interesting bugs happening here (all assigned to hw-detect): * Firmware packages should not be installed for firmware that were not explicitely required. This would need further investigation as the code, as far as I can see, should filter out the packages present on the media based on needed firmware files. * The post-base-installer hook uses "dpkg -i" to install the firmware packages on the target system. This will fail if the firmware package dependencies are not fulfilled on the target at that time of the installation process. Possible fix: switch to a "dpkg --unpack", "apt-get -f install" construct * If firmware packages for other architectures than all or the one being installed are present on the firmware media, the post-base-installer hook will try to install them nevertheless. This will obviously fails. Possible fix: filter packages for wrong architectures in check-missing-firmware.sh > Grub installed to usb stick instead of system disk > -------------------------------------------------- > When prompted if I wanted grub installed to the MBR, I said sure - but > that ended up installing grub to my firmware usb stick ;( > Not sure there's anything we can about this one, other than > potentially warn the user. This issue is strongly connected to the "persistent device naming" issue, which we are aware of and hard enough so we were not able to tackle it on time for Lenny. I do wonder if we should not make an extra confirmation if we detect that grub-installer is going to put the MBR on a USB disk, as it should not be the most common case. Cheers, -- Jérémy Bobbio .''`. [EMAIL PROTECTED] : :Ⓐ : # apt-get install anarchism `. `'` `-
signature.asc
Description: Digital signature
