Bug#492205: installation-reports: firmware load testing - Debian

This is a discussion on Bug#492205: installation-reports: firmware load testing - Debian ; Package: installation-reports Severity: normal Subject: installation-reports: lenny daily / hp dl380g5 Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: i386 netinst daily build 2008.07.23 Date: Machine: HP DL380g5 Partitions: Base System Installation Checklist: [O] = OK, ...

+ Reply to Thread
Results 1 to 14 of 14

Thread: Bug#492205: installation-reports: firmware load testing

  1. Bug#492205: installation-reports: firmware load testing

    Package: installation-reports
    Severity: normal

    Subject: installation-reports: lenny daily / hp dl380g5
    Package: installation-reports
    Severity: normal

    -- Package-specific info:

    Boot method: CD
    Image version: i386 netinst daily build 2008.07.23
    Date:

    Machine: HP DL380g5
    Partitions:


    Base System Installation Checklist:
    [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

    Initial boot: [O]
    Detect network card: [E]
    Configure network: [O]
    Detect CD: [O]
    Load installer modules: [O]
    Detect hard drives: [O]
    Partition hard drives: [O]
    Install base system: [E]
    Clock/timezone setup: [O]
    User/password setup: [O]
    Install tasks: [O]
    Install boot loader: [E]
    Overall install: [@]

    Comments/Problems:

    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.

    Unable to mount usb stick
    -------------------------
    I created a usb stick w/ the firmware debs in the firmware.tar.gz. In
    my case it was a virtual usb device, emulated by the HP iLO 2. I
    created the backend file by mkdosfs'ing an empty 8MB file, loopback
    mounting it, and unpacking the firmware deb tarball in the root.

    The installer correctly discovered that I might need firmware for my
    bnx2 controller, and it asked me if it should look for it on some
    attached media. I selected yes, and it went away for a bit while it
    searched devices, but then eventually returned w/ the same
    prompt. Dropping to a shell, I saw the following messages in dmesg:

    [ 24.285589] FAT: utf8 is not a recommended IO charset for FAT
    filesystems, filesystem will be case sensitive!
    [ 24.299221] Unable to load NLS charset utf8
    [ 24.299224] FAT: IO charset utf8 not found

    I am also unable to mount the usb stick from the shell using the
    same arguments mountmedia uses:
    # mount /dev/sda /media -tauto

    The problem appears to be that the Debian kernel is configured to use
    the utf8 iocodepage by default (see #483781), but the installer does
    not include the nls_utf8 module. If I override this default by passing
    the mount option 'iocodepage=iso8559-1', the mount succeeds. If I copy
    over and load the nls_utf8 module the mount succeeds w/o the
    iocodepage option. And if I use an ext2 stick and load the ext2 module
    early on, this entire step succeeds w/o further intervention.

    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-...ssing-fw-1.png
    http://free.linux.hp.com/~dannf/d-i-...ssing-fw-2.png
    http://free.linux.hp.com/~dannf/d-i-...ssing-fw-3.png

    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-...ybox-error.png

    Looking at syslog, it appears that the problem is unmet dependencies
    for some of the firmware debs:

    base-installer: info: Available initramfs generator(s): 'initramfs-tools'
    Reading package lists...
    Building dependency tree...
    Reading state information...
    You might want to run `apt-get -f install' to correct these:
    The following packages have unmet dependencies:
    atmel-firmware: Depends: perl but it is not installable
    Depends: udev (>= 0.070-3) but it is not going to be installed or
    hotplug (>= 0.0.20040329-12) but it is not installable
    zd1211-firmware: Depends: udev (>= 0.070-3) but it is not going to be installed or
    hotplug (>= 0.0.20040329-19) but it is not installable
    E:
    Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
    base-installer: error: exiting on error base-installer/kernel/failed-package-install

    Full syslog file:
    http://free.linux.hp.com/~dannf/d-i-20080723/syslog

    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.

    --

    Please make sure that the hardware-summary log file, and any other
    installation logs that you think would be useful are attached to this
    report. Please compress large files using gzip.

    Once you have filled out this report, mail it to submit@bugs.debian.org.

    ==============================================
    Installer lsb-release:
    ==============================================
    DISTRIB_ID=Debian
    DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
    DISTRIB_RELEASE="5.0 (lenny) - installer build 20080723-19:07"
    X_INSTALLATION_MEDIUM=cdrom

    ==============================================
    Installer hardware-summary:
    ==============================================
    umame -a: Linux dl380g5 2.6.25-2-486 #1 Fri Jun 27 02:39:22 UTC 2008 i686 unknown
    lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 5000P Chipset Memory Controller Hub [8086:25d8] (rev 93)
    lspci -knn: 00:02.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 2 [8086:25e2] (rev 93)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:03.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 [8086:25e3] (rev 93)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:04.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 [8086:25f8] (rev 93)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:05.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 [8086:25e5] (rev 93)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:06.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 [8086:25f9] (rev 93)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:07.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 [8086:25e7] (rev 93)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:10.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 93)
    lspci -knn: 00:10.1 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 93)
    lspci -knn: 00:10.2 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 93)
    lspci -knn: 00:11.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset Reserved Registers [8086:25f1] (rev 93)
    lspci -knn: 00:13.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset Reserved Registers [8086:25f3] (rev 93)
    lspci -knn: 00:15.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FBD Registers [8086:25f5] (rev 93)
    lspci -knn: 00:16.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FBD Registers [8086:25f6] (rev 93)
    lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 [8086:2690] (rev 09)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2 [8086:2692] (rev 09)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 [8086:2688] (rev 09)
    lspci -knn: Kernel driver in use: uhci_hcd
    lspci -knn: Kernel modules: uhci-hcd
    lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 [8086:2689] (rev 09)
    lspci -knn: Kernel driver in use: uhci_hcd
    lspci -knn: Kernel modules: uhci-hcd
    lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 [8086:268a] (rev 09)
    lspci -knn: Kernel driver in use: uhci_hcd
    lspci -knn: Kernel modules: uhci-hcd
    lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 [8086:268b] (rev 09)
    lspci -knn: Kernel driver in use: uhci_hcd
    lspci -knn: Kernel modules: uhci-hcd
    lspci -knn: 00:1d.7 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller [8086:268c] (rev 09)
    lspci -knn: Kernel driver in use: ehci_hcd
    lspci -knn: Kernel modules: ehci-hcd
    lspci -knn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d9)
    lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller [8086:2670] (rev 09)
    lspci -knn: 00:1f.1 IDE interface [0101]: Intel Corporation 631xESB/632xESB IDE Controller [8086:269e] (rev 09)
    lspci -knn: Kernel driver in use: PIIX_IDE
    lspci -knn: Kernel modules: piix
    lspci -knn: 01:03.0 VGA compatible controller [0300]: ATI Technologies Inc ES1000 [1002:515e] (rev 02)
    lspci -knn: 01:04.0 System peripheral [0880]: Compaq Computer Corporation Integrated Lights Out Controller [0e11:b203] (rev 03)
    lspci -knn: 01:04.2 System peripheral [0880]: Compaq Computer Corporation Integrated Lights Out Processor [0e11:b204] (rev 03)
    lspci -knn: 01:04.4 USB Controller [0c03]: Hewlett-Packard Company Proliant iLO2 virtual USB controller [103c:3300]
    lspci -knn: Kernel driver in use: uhci_hcd
    lspci -knn: Kernel modules: uhci-hcd
    lspci -knn: 01:04.6 IPMI SMIC interface [0c07]: Hewlett-Packard Company Proliant iLO2 virtual UART [103c:3302]
    lspci -knn: 02:00.0 PCI bridge [0604]: Broadcom EPB PCI-Express to PCI-X Bridge [1166:0103] (rev c2)
    lspci -knn: 03:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet [14e4:164c] (rev 11)
    lspci -knn: Kernel driver in use: bnx2
    lspci -knn: Kernel modules: bnx2
    lspci -knn: 04:00.0 PCI bridge [0604]: Broadcom EPB PCI-Express to PCI-X Bridge [1166:0103] (rev c2)
    lspci -knn: 05:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet [14e4:164c] (rev 11)
    lspci -knn: Kernel driver in use: bnx2
    lspci -knn: Kernel modules: bnx2
    lspci -knn: 06:00.0 RAID bus controller [0104]: Hewlett-Packard Company Smart Array Controller [103c:3230] (rev 01)
    lspci -knn: Kernel driver in use: cciss
    lspci -knn: Kernel modules: cciss
    lspci -knn: 09:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port [8086:3500] (rev 01)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 09:00.3 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge [8086:350c] (rev 01)
    lspci -knn: 0a:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 [8086:3510] (rev 01)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 0a:01.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 [8086:3514] (rev 01)
    lspci -knn: Kernel driver in use: pcieport-driver
    lspci -knn: 0a:02.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 [8086:3518] (rev 01)
    lspci -knn: Kernel driver in use: pcieport-driver
    lsmod: Module Size Used by
    lsmod: ufs 69764 0
    lsmod: qnx4 10628 0
    lsmod: ntfs 189760 0
    lsmod: xfs 462836 0
    lsmod: reiserfs 199936 0
    lsmod: jfs 159452 0
    lsmod: ext3 117640 1
    lsmod: jbd 38932 1 ext3
    lsmod: bnx2 57352 0
    lsmod: firmware_class 8832 1 bnx2
    lsmod: vfat 11648 0
    lsmod: fat 45852 1 vfat
    lsmod: ext2 62216 0
    lsmod: mbcache 7680 2 ext3,ext2
    lsmod: cciss 56324 3
    lsmod: isofs 31908 0
    lsmod: nls_base 6784 5 ntfs,jfs,vfat,fat,isofs
    lsmod: zlib_inflate 14208 1 isofs
    lsmod: rsrc_nonstatic 11520 0
    lsmod: pcmcia_core 36112 1 rsrc_nonstatic
    lsmod: ide_generic 1280 0 [permanent]
    lsmod: sg 33328 0
    lsmod: sd_mod 25872 0
    lsmod: sr_mod 16420 0
    lsmod: fan 5508 0
    lsmod: ide_cd_mod 32672 0
    lsmod: cdrom 31776 2 sr_mod,ide_cd_mod
    lsmod: usb_storage 76096 0
    lsmod: scsi_mod 138508 5 cciss,sg,sd_mod,sr_mod,usb_storage
    lsmod: usbhid 39424 0
    lsmod: hid 34816 1 usbhid
    lsmod: ff_memless 5128 1 usbhid
    lsmod: piix 7044 0 [permanent]
    lsmod: ide_core 98500 3 ide_generic,ide_cd_mod,piix
    lsmod: ehci_hcd 31756 0
    lsmod: uhci_hcd 21776 0
    lsmod: usbcore 127600 5 usb_storage,usbhid,ehci_hcd,uhci_hcd
    lsmod: thermal 18844 0
    lsmod: processor 33204 1 thermal
    df: Filesystem 1k-blocks Used Available Use% Mounted on
    df: tmpfs 453244 68 453176 0% /dev
    df: tmpfs 453244 68 453176 0% /dev
    df: /dev/cciss/c0d0p1 67915316 698424 63766936 1% /target
    df: /dev/cciss/c0d0p1 67915316 698424 63766936 1% /dev/.static/dev
    df: tmpfs 453244 68 453176 0% /target/dev
    free: total used free shared buffers
    free: Mem: 906492 590424 316068 0 1384
    free: Swap: 2650684 0 2650684
    free: Total: 3557176 590424 2966752
    /proc/cpuinfo: processor : 0
    /proc/cpuinfo: vendor_id : GenuineIntel
    /proc/cpuinfo: cpu family : 6
    /proc/cpuinfo: model : 15
    /proc/cpuinfo: model name : Intel(R) Xeon(R) CPU 5160 @ 3.00GHz
    /proc/cpuinfo: stepping : 6
    /proc/cpuinfo: cpu MHz : 3000.138
    /proc/cpuinfo: cache size : 4096 KB
    /proc/cpuinfo: fdiv_bug : no
    /proc/cpuinfo: hlt_bug : no
    /proc/cpuinfo: f00f_bug : no
    /proc/cpuinfo: coma_bug : no
    /proc/cpuinfo: fpu : yes
    /proc/cpuinfo: fpu_exception : yes
    /proc/cpuinfo: cpuid level : 10
    /proc/cpuinfo: wp : yes
    /proc/cpuinfo: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe lm constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca lahf_lm
    /proc/cpuinfo: bogomips : 6004.33
    /proc/cpuinfo: clflush size : 64
    /proc/cpuinfo:
    /proc/ioports: 0000-001f : dma1
    /proc/ioports: 0020-0021 : pic1
    /proc/ioports: 0040-0043 : timer0
    /proc/ioports: 0050-0053 : timer1
    /proc/ioports: 0060-006f : keyboard
    /proc/ioports: 0080-008f : dma page reg
    /proc/ioports: 00a0-00a1 : pic2
    /proc/ioports: 00c0-00df : dma2
    /proc/ioports: 00f0-00ff : fpu
    /proc/ioports: 0170-0177 : 0000:00:1f.1
    /proc/ioports: 01f0-01f7 : 0000:00:1f.1
    /proc/ioports: 01f0-01f7 : ide0
    /proc/ioports: 02f8-02ff : pnp 00:01
    /proc/ioports: 02f8-02ff : serial
    /proc/ioports: 0376-0376 : 0000:00:1f.1
    /proc/ioports: 03c0-03df : vga+
    /proc/ioports: 03f6-03f6 : 0000:00:1f.1
    /proc/ioports: 03f6-03f6 : ide0
    /proc/ioports: 03f8-03ff : serial
    /proc/ioports: 0408-040f : pnp 00:01
    /proc/ioports: 04d0-04d1 : pnp 00:01
    /proc/ioports: 0500-050f : 0000:00:1f.1
    /proc/ioports: 0500-0507 : ide0
    /proc/ioports: 0508-050f : ide1
    /proc/ioports: 0700-071f : pnp 00:01
    /proc/ioports: 0800-083f : pnp 00:01
    /proc/ioports: 0900-097f : pnp 00:01
    /proc/ioports: 0900-0903 : ACPI PM1a_EVT_BLK
    /proc/ioports: 0904-0907 : ACPI PM1a_CNT_BLK
    /proc/ioports: 0908-090b : ACPI PM_TMR
    /proc/ioports: 0928-092f : ACPI GPE0_BLK
    /proc/ioports: 0c80-0c83 : pnp 00:01
    /proc/ioports: 0ca0-0ca1 : pnp 00:01
    /proc/ioports: 0ca4-0ca5 : pnp 00:01
    /proc/ioports: 0cd4-0cd7 : pnp 00:01
    /proc/ioports: 0cf8-0cff : PCI conf1
    /proc/ioports: 0f50-0f58 : pnp 00:01
    /proc/ioports: 1000-101f : 0000:00:1d.0
    /proc/ioports: 1000-101f : uhci_hcd
    /proc/ioports: 1020-103f : 0000:00:1d.1
    /proc/ioports: 1020-103f : uhci_hcd
    /proc/ioports: 1040-105f : 0000:00:1d.2
    /proc/ioports: 1040-105f : uhci_hcd
    /proc/ioports: 1060-107f : 0000:00:1d.3
    /proc/ioports: 1060-107f : uhci_hcd
    /proc/ioports: 2000-3fff : PCI Bus #01
    /proc/ioports: 2800-28ff : 0000:01:04.0
    /proc/ioports: 3000-30ff : 0000:01:03.0
    /proc/ioports: 3400-34ff : 0000:01:04.2
    /proc/ioports: 3800-381f : 0000:01:04.4
    /proc/ioports: 3800-381f : uhci_hcd
    /proc/ioports: 4000-4fff : PCI Bus #06
    /proc/ioports: 4000-40ff : 0000:06:00.0
    /proc/ioports: 4000-40ff : cciss
    /proc/iomem: 00000000-0009f3ff : System RAM
    /proc/iomem: 0009f400-0009ffff : reserved
    /proc/iomem: 000a0000-000bffff : Video RAM area
    /proc/iomem: 000c0000-000cafff : Video ROM
    /proc/iomem: 000f0000-000fffff : System ROM
    /proc/iomem: 00100000-cffc7fff : System RAM
    /proc/iomem: 00100000-0029d2a6 : Kernel code
    /proc/iomem: 0029d2a7-0034ef9f : Kernel data
    /proc/iomem: 003a2000-003dd7f7 : Kernel bss
    /proc/iomem: cffc8000-cffcffff : ACPI Tables
    /proc/iomem: cffd0000-cfffffff : reserved
    /proc/iomem: d4000000-d40fffff : PCI Bus #06
    /proc/iomem: d4000000-d403ffff : 0000:06:00.0
    /proc/iomem: d4100000-d41fffff : PCI Bus #02
    /proc/iomem: d4100000-d41fffff : PCI Bus #03
    /proc/iomem: d4100000-d41007ff : 0000:03:00.0
    /proc/iomem: d4200000-d42fffff : PCI Bus #04
    /proc/iomem: d4200000-d42fffff : PCI Bus #05
    /proc/iomem: d4200000-d42007ff : 0000:05:00.0
    /proc/iomem: d8000000-dfffffff : PCI Bus #01
    /proc/iomem: d8000000-dfffffff : 0000:01:03.0
    /proc/iomem: e0000000-efffffff : pnp 00:01
    /proc/iomem: f7df0000-f7df03ff : 0000:00:1d.7
    /proc/iomem: f7df0000-f7df03ff : ehci_hcd
    /proc/iomem: f7e00000-f7ffffff : PCI Bus #01
    /proc/iomem: f7e00000-f7e1ffff : 0000:01:03.0
    /proc/iomem: f7e20000-f7e2ffff : 0000:01:04.2
    /proc/iomem: f7ef0000-f7ef00ff : 0000:01:04.6
    /proc/iomem: f7f00000-f7f7ffff : 0000:01:04.2
    /proc/iomem: f7fc0000-f7fc1fff : 0000:01:04.2
    /proc/iomem: f7fd0000-f7fd07ff : 0000:01:04.2
    /proc/iomem: f7fe0000-f7fe01ff : 0000:01:04.0
    /proc/iomem: f7ff0000-f7ffffff : 0000:01:03.0
    /proc/iomem: f8000000-f9ffffff : PCI Bus #02
    /proc/iomem: f8000000-f9ffffff : PCI Bus #03
    /proc/iomem: f8000000-f9ffffff : 0000:03:00.0
    /proc/iomem: f8000000-f9ffffff : bnx2
    /proc/iomem: fa000000-fbffffff : PCI Bus #04
    /proc/iomem: fa000000-fbffffff : PCI Bus #05
    /proc/iomem: fa000000-fbffffff : 0000:05:00.0
    /proc/iomem: fa000000-fbffffff : bnx2
    /proc/iomem: fdd00000-fdefffff : PCI Bus #06
    /proc/iomem: fddf0000-fddf0fff : 0000:06:00.0
    /proc/iomem: fddf0000-fddf0fff : cciss
    /proc/iomem: fde00000-fdefffff : 0000:06:00.0
    /proc/iomem: fde00000-fdefffff : cciss
    /proc/iomem: fdf00000-fdffffff : PCI Bus #09
    /proc/iomem: fe000000-febfffff : pnp 00:01
    /proc/iomem: fec00000-fecfffff : reserved
    /proc/iomem: fed00000-fed003ff : HPET 0
    /proc/iomem: fee00000-fee0ffff : reserved
    /proc/iomem: ffc00000-ffffffff : reserved
    /proc/interrupts: CPU0
    /proc/interrupts: 0: 135 IO-APIC-edge timer
    /proc/interrupts: 1: 2 IO-APIC-edge i8042
    /proc/interrupts: 3: 26534 IO-APIC-edge serial
    /proc/interrupts: 9: 0 IO-APIC-fasteoi acpi
    /proc/interrupts: 12: 3 IO-APIC-edge i8042
    /proc/interrupts: 14: 669 IO-APIC-edge ide0
    /proc/interrupts: 16: 0 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb6
    /proc/interrupts: 17: 0 IO-APIC-fasteoi uhci_hcd:usb2
    /proc/interrupts: 18: 0 IO-APIC-fasteoi uhci_hcd:usb3
    /proc/interrupts: 19: 0 IO-APIC-fasteoi uhci_hcd:usb4
    /proc/interrupts: 22: 39140 IO-APIC-fasteoi uhci_hcd:usb5
    /proc/interrupts: 208: 109658 PCI-MSI-edge eth0
    /proc/interrupts: 210: 129594 PCI-MSI-edge cciss0
    /proc/interrupts: NMI: 0 Non-maskable interrupts
    /proc/interrupts: LOC: 49081 Local timer interrupts
    /proc/interrupts: TRM: 0 Thermal event interrupts
    /proc/interrupts: SPU: 0 Spurious interrupts
    /proc/interrupts: ERR: 0
    /proc/interrupts: MIS: 0
    /proc/meminfo: MemTotal: 906492 kB
    /proc/meminfo: MemFree: 315776 kB
    /proc/meminfo: Buffers: 1384 kB
    /proc/meminfo: Cached: 535172 kB
    /proc/meminfo: SwapCached: 0 kB
    /proc/meminfo: Active: 164676 kB
    /proc/meminfo: Inactive: 378456 kB
    /proc/meminfo: SwapTotal: 2650684 kB
    /proc/meminfo: SwapFree: 2650684 kB
    /proc/meminfo: Dirty: 672 kB
    /proc/meminfo: Writeback: 0 kB
    /proc/meminfo: AnonPages: 6600 kB
    /proc/meminfo: Mapped: 1692 kB
    /proc/meminfo: Slab: 35580 kB
    /proc/meminfo: SReclaimable: 27372 kB
    /proc/meminfo: SUnreclaim: 8208 kB
    /proc/meminfo: PageTables: 276 kB
    /proc/meminfo: NFS_Unstable: 0 kB
    /proc/meminfo: Bounce: 0 kB
    /proc/meminfo: CommitLimit: 3103928 kB
    /proc/meminfo: Committed_AS: 9812 kB
    /proc/meminfo: VmallocTotal: 122564 kB
    /proc/meminfo: VmallocUsed: 8536 kB
    /proc/meminfo: VmallocChunk: 113008 kB
    /proc/meminfo: HugePages_Total: 0
    /proc/meminfo: HugePages_Free: 0
    /proc/meminfo: HugePages_Rsvd: 0
    /proc/meminfo: HugePages_Surp: 0
    /proc/meminfo: Hugepagesize: 4096 kB
    /proc/bus/input/devices: I: Bus=0003 Vendor=03f0 Product=1027 Version=0101
    /proc/bus/input/devices: N: Name="HP Virtual Keyboard"
    /proc/bus/input/devices: P: Phys=usb-0000:01:04.4-1/input0
    /proc/bus/input/devices: S: Sysfs=/class/input/input0
    /proc/bus/input/devices: U: Uniq=
    /proc/bus/input/devices: H: Handlers=kbd
    /proc/bus/input/devices: B: EV=120013
    /proc/bus/input/devices: B: KEY=10000 7 ff980000 7ff febeffdf ffefffff ffffffff fffffffe
    /proc/bus/input/devices: B: MSC=10
    /proc/bus/input/devices: B: LED=1f
    /proc/bus/input/devices:
    /proc/bus/input/devices: I: Bus=0003 Vendor=03f0 Product=1027 Version=0101
    /proc/bus/input/devices: N: Name="HP Virtual Keyboard"
    /proc/bus/input/devices: P: Phys=usb-0000:01:04.4-1/input1
    /proc/bus/input/devices: S: Sysfs=/class/input/input1
    /proc/bus/input/devices: U: Uniq=
    /proc/bus/input/devices: H: Handlers=mouse0
    /proc/bus/input/devices: B: EV=17
    /proc/bus/input/devices: B: KEY=70000 0 0 0 0 0 0 0 0
    /proc/bus/input/devices: B: REL=3
    /proc/bus/input/devices: B: MSC=10
    /proc/bus/input/devices:

    -- System Information:
    Debian Release: lenny/sid
    APT prefers testing
    APT policy: (500, 'testing')
    Architecture: i386 (i686)

    Kernel: Linux 2.6.25-2-686 (SMP w/4 CPU cores)
    Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
    Shell: /bin/sh linked to /bin/bash



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Bug#492205: installation-reports: firmware load testing

    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-...ssing-fw-1.png
    > http://free.linux.hp.com/~dannf/d-i-...ssing-fw-2.png
    > http://free.linux.hp.com/~dannf/d-i-...ssing-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-...ybox-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 .''`.
    lunar@debian.org : :Ⓐ : # apt-get install anarchism
    `. `'`
    `-

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.6 (GNU/Linux)

    iD8DBQFIiLH02PUjs9fQ72URAlb0AJ4//JOoCvkeN2e2OegcuC9qB5zXYgCfYv+S
    Xlma7zxcuMrmZQ8esSYdAiY=
    =IGal
    -----END PGP SIGNATURE-----


  3. Bug#492205: installation-reports: firmware load testing

    On Thu, Jul 24, 2008 at 06:46:44PM +0200, J?r?my Bobbio wrote:
    > 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?


    Of course! That's the least I can offer..

    > (I am leaving this bug report opened in order to allow follow-up.)


    Thanks for your analysis - it all looks quite reasonable to me, so I
    don't have any specific responses.

    --
    dann frazier




    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Bug#492205: installation-reports: firmware load testing

    Jrmy Bobbio wrote:
    > * 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 filtering worked in my testing. Before I go off on a wild goose
    chase, are we sure that Dan didn't dump the debs into
    /var/cache/firmware/ in d-i? Because it would pefectly explain it trying
    to install all the debs from there.

    Hmm, tested again, code still seems to work:

    # files="foo bar"
    # echo "$files" | sed -e 's/ /\n/g' >/tmp/grepfor
    # cat /tmp/grepfor
    foo
    bar
    # list_deb_firmware () {
    # list_deb_firmware () {
    > ar p "$1" data.tar.gz | tar zt \
    > | grep '^\./lib/firmware/' \
    > | sed -e 's!^\./lib/firmware/!!'
    > }

    # list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb

    zd1211/
    zd1211/zd1211_ub
    zd1211/zd1211_uph
    zd1211/zd1211_uphm
    zd1211/zd1211_uphr
    zd1211/zd1211_ur
    zd1211/zd1211b_ub
    zd1211/zd1211b_uph
    zd1211/zd1211b_uphm
    zd1211/zd1211b_uphr
    zd1211/zd1211b_ur
    # list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb | grep -qf /tmp/grepfor
    # echo $?
    1
    #

    It does, however, think that every deb contains a firmware file named "", so if
    it somehow thinks it needs such a file, it will try to use every deb to provide
    it:

    /ff # files="foo bar "
    /ff # echo "$files" | sed -e 's/ /\n/g' >/tmp/grepfor
    /ff # list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb | grep -qf
    /tmp/grepfor
    /ff # echo $?

    0

    I don't see how $files could get an extra leading/trailing space to
    tickle this problem, unless a module actually requests a firmware file
    with a space in its name. But I've checked in a fix for it anyway..

    > * 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


    Maybe, however firmware debs really have no business depending on
    packages not in base either. And getting the dpkg db into a broken state
    and relying on apt fixing it, noninteractively, seems like it can be
    asking for trouble.

    In particular, atmel-firmware has no reason to depend on perl, since
    atmel_fwl is not used in normal operation. And neither atmel-firmware
    nor zd1211-firmware have any business depending on udev. Bugs filed on
    both.

    Until those two can be fixed, we can simply drop their debs from the
    firmware-nonfree images.

    And for added robustness, I've made it dpkg --remove the package if dpkg
    -i fails.

    > * 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


    Added, but note that this is currently only really useful in the case
    of choosing the right arch ixp4xx-microcode on arm/armel.

    --
    see shy jo

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iD8DBQFIiOMwd8HHehbQuO8RAtUrAKDZFcUgoeATq7bmwx5Vmk zjvnm8dACgoTGN
    Ai2THoGTF0v8lmo2LzW7wXc=
    =H5Tw
    -----END PGP SIGNATURE-----


  5. Bug#492205: installation-reports: firmware load testing

    On Thu, Jul 24, 2008 at 04:16:48PM -0400, Joey Hess wrote:
    > J?r?my Bobbio wrote:
    > > * 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 filtering worked in my testing. Before I go off on a wild goose
    > chase, are we sure that Dan didn't dump the debs into
    > /var/cache/firmware/ in d-i? Because it would pefectly explain it trying
    > to install all the debs from there.


    Yeah, I'm sure

    > Hmm, tested again, code still seems to work:
    >
    > # files="foo bar"
    > # echo "$files" | sed -e 's/ /\n/g' >/tmp/grepfor
    > # cat /tmp/grepfor
    > foo
    > bar
    > # list_deb_firmware () {
    > # list_deb_firmware () {
    > > ar p "$1" data.tar.gz | tar zt \
    > > | grep '^\./lib/firmware/' \
    > > | sed -e 's!^\./lib/firmware/!!'
    > > }

    > # list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb
    >
    > zd1211/
    > zd1211/zd1211_ub
    > zd1211/zd1211_uph
    > zd1211/zd1211_uphm
    > zd1211/zd1211_uphr
    > zd1211/zd1211_ur
    > zd1211/zd1211b_ub
    > zd1211/zd1211b_uph
    > zd1211/zd1211b_uphm
    > zd1211/zd1211b_uphr
    > zd1211/zd1211b_ur
    > # list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb | grep -qf /tmp/grepfor
    > # echo $?
    > 1
    > #
    >
    > It does, however, think that every deb contains a firmware file named "", so if
    > it somehow thinks it needs such a file, it will try to use every deb to provide
    > it:
    >
    > /ff # files="foo bar "
    > /ff # echo "$files" | sed -e 's/ /\n/g' >/tmp/grepfor
    > /ff # list_deb_firmware zd1211-firmware_2.16.0.0-0.1_all.deb | grep -qf
    > /tmp/grepfor
    > /ff # echo $?
    > 0
    >
    > I don't see how $files could get an extra leading/trailing space to
    > tickle this problem, unless a module actually requests a firmware file
    > with a space in its name. But I've checked in a fix for it anyway..


    The bnx2 module requests 2 pieces of firmware - maybe that has
    something to do with it?

    --
    dann frazier




    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  6. Bug#492205: installation-reports: firmware load testing

    dann frazier wrote:
    > The bnx2 module requests 2 pieces of firmware - maybe that has
    > something to do with it?


    Hm, don't think so..

    If you want to test, I've checked fixes for all the issues I understand
    (except for the code page problem) into hw-detect in svn.

    Test image: http://kitenet.net/~joey/tmp/mini.so
    sha1sum: 31716cc357ac0db4a315523dd69daade3453ef00

    If it still tries to install all the firmware .debs, I'd probably need
    to see a sh -x check-missing-firmware to figure out why. Though I did
    add a little bit of logging, that may help pinpoint it.

    --
    see shy jo

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iD8DBQFIiPN7d8HHehbQuO8RAhl+AKCqBA8iix+IzFcQ0TKN5x nhBy9SFwCfYQii
    QmFo+wTQy9fhrWu8gjIXAXA=
    =0eLT
    -----END PGP SIGNATURE-----


  7. Bug#492205: installation-reports: firmware load testing

    On Thu, Jul 24, 2008 at 05:26:19PM -0400, Joey Hess wrote:
    > dann frazier wrote:
    > > The bnx2 module requests 2 pieces of firmware - maybe that has
    > > something to do with it?

    >
    > Hm, don't think so..
    >
    > If you want to test, I've checked fixes for all the issues I understand
    > (except for the code page problem) into hw-detect in svn.
    >
    > Test image: http://kitenet.net/~joey/tmp/mini.so
    > sha1sum: 31716cc357ac0db4a315523dd69daade3453ef00


    I couldn't get this image to work; it seems to load bnx2 on startup
    automatically and, after a 'modprobe -r bnx2', it doesn't seem to ever
    bring up the fw prompt.

    > If it still tries to install all the firmware .debs, I'd probably need
    > to see a sh -x check-missing-firmware to figure out why. Though I did
    > add a little bit of logging, that may help pinpoint it.


    I collected this (after commenting out debconf stuff, and manually
    modprobing bnx2 to create the /tmp/missing-firmware file). See [1].
    The problem appears to be that the grepfor file contains an empty
    trailing line:

    ~ # cat /tmp/grepfor
    bnx2-06-4.0.5.fw
    bnx2-06-4.0.5.fw

    ~ #

    And this is because "$files" has a trailing space:

    ~ # cat /tmp/files2.dannf | sed 's/$/,/'
    bnx2-06-4.0.5.fw bnx2-06-4.0.5.fw ,

    Filtering out the trailing space[2] fixed this for me.

    [1]
    BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) built-in shell (ash)
    Enter 'help' for a list of built-in commands.

    ~ # modprobe -r bnx2
    ~ # ls
    bin dev init lib mnt root sys usr
    cdrom etc initrd media proc sbin tmp var
    ~ # ls /media/
    ~ # ls /tmp
    x
    ~ # modprobe bnx2
    ~ # cat /tmp/missing-firmware
    bnx2 bnx2-06-4.0.5.fw
    bnx2 bnx2-06-4.0.5.fw
    ~ # /bin/check-missing-firmware
    + set -e
    + LOG=/tmp/missing-firmware
    + NL=

    + first=1
    + read_log
    + modules=
    + files=
    + [ -s /tmp/missing-firmware ]
    + mv /tmp/missing-firmware /tmp/missing-firmware.old
    + OLDIFS=

    + IFS=

    + cat /tmp/missing-firmware.old
    + module=bnx2
    + [ -n bnx2 ]
    + modules=bnx2
    + file=bnx2-06-4.0.5.fw
    + [ -n bnx2-06-4.0.5.fw ]
    + files=bnx2-06-4.0.5.fw
    + module=bnx2
    + [ -n bnx2 ]
    + modules=bnx2 bnx2
    + file=bnx2-06-4.0.5.fw
    + [ -n bnx2-06-4.0.5.fw ]
    + files=bnx2-06-4.0.5.fw bnx2-06-4.0.5.fw
    + IFS=

    + rm -f /tmp/missing-firmware.old
    + [ -n bnx2 bnx2 ]
    + return 0
    + ask_load_firmware
    + return 0
    + mountmedia
    mount: option requires an argument -- o
    BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary

    Usage: mount [flags] DEVICE NODE [-o options,more-options]

    umount: cannot umount /media: Invalid argument
    mount: mounting /dev/cciss/c0d0 on /media failed: Invalid argument
    + [ -e /media/bnx2-06-4.0.5.fw ]
    + [ -e /media/bnx2-06-4.0.5.fw ]
    + umount /media
    umount: cannot umount /media: Invalid argument
    + true
    + mountmedia driver
    mount: option requires an argument -- o
    BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary

    Usage: mount [flags] DEVICE NODE [-o options,more-options]

    umount: cannot umount /media: Invalid argument
    mount: mounting /dev/cciss/c0d0 on /media failed: Invalid argument
    mount: option requires an argument -- o
    BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary

    Usage: mount [flags] DEVICE NODE [-o options,more-options]

    umount: cannot umount /media: Invalid argument
    mount: mounting /dev/cciss/c0d1 on /media failed: Invalid argument
    mount: option requires an argument -- o
    BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary

    Usage: mount [flags] DEVICE NODE [-o options,more-options]

    umount: cannot umount /media: Invalid argument
    mount: mounting /dev/cciss/c0d2 on /media failed: Invalid argument
    mount: option requires an argument -- o
    BusyBox v1.10.2 (2008-06-06 18:28:20 UTC) multi-call binary

    Usage: mount [flags] DEVICE NODE [-o options,more-options]

    umount: cannot umount /media: Invalid argument
    + echo bnx2-06-4.0.5.fw bnx2-06-4.0.5.fw
    + sed -e s/ /\n/g
    + [ -f /media/atmel-firmware_1.3-3_all.deb ]
    + list_deb_firmware /media/atmel-firmware_1.3-3_all.deb
    + ar p /media/atmel-firmware_1.3-3_all.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/atmel-firmware_1.3-3_all.deb
    + echo /media/atmel-firmware_1.3-3_all.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/atmel-firmware_1.3-3_all.deb /var/cache/firmware/
    + basename /media/atmel-firmware_1.3-3_all.deb
    + udpkg --unpack /var/cache/firmware/atmel-firmware_1.3-3_all.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/firmware-bnx2_0.12_all.deb ]
    + list_deb_firmware /media/firmware-bnx2_0.12_all.deb
    + ar p /media/firmware-bnx2_0.12_all.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/firmware-bnx2_0.12_all.deb
    + echo /media/firmware-bnx2_0.12_all.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/firmware-bnx2_0.12_all.deb /var/cache/firmware/
    + basename /media/firmware-bnx2_0.12_all.deb
    + udpkg --unpack /var/cache/firmware/firmware-bnx2_0.12_all.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/firmware-iwlwifi_0.12_all.deb ]
    + list_deb_firmware /media/firmware-iwlwifi_0.12_all.deb
    + ar p /media/firmware-iwlwifi_0.12_all.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/firmware-iwlwifi_0.12_all.deb
    + echo /media/firmware-iwlwifi_0.12_all.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/firmware-iwlwifi_0.12_all.deb /var/cache/firmware/
    + basename /media/firmware-iwlwifi_0.12_all.deb
    + udpkg --unpack /var/cache/firmware/firmware-iwlwifi_0.12_all.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/firmware-qlogic_0.12_all.deb ]
    + list_deb_firmware /media/firmware-qlogic_0.12_all.deb
    + ar p /media/firmware-qlogic_0.12_all.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/firmware-qlogic_0.12_all.deb
    + echo /media/firmware-qlogic_0.12_all.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/firmware-qlogic_0.12_all.deb /var/cache/firmware/
    + basename /media/firmware-qlogic_0.12_all.deb
    + udpkg --unpack /var/cache/firmware/firmware-qlogic_0.12_all.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/firmware-ralink_0.12_all.deb ]
    + list_deb_firmware /media/firmware-ralink_0.12_all.deb
    + ar p /media/firmware-ralink_0.12_all.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/firmware-ralink_0.12_all.deb
    + echo /media/firmware-ralink_0.12_all.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/firmware-ralink_0.12_all.deb /var/cache/firmware/
    + basename /media/firmware-ralink_0.12_all.deb
    + udpkg --unpack /var/cache/firmware/firmware-ralink_0.12_all.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/ixp4xx-microcode_2.4-2_armel.deb ]
    + list_deb_firmware /media/ixp4xx-microcode_2.4-2_armel.deb
    + ar p /media/ixp4xx-microcode_2.4-2_armel.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/ixp4xx-microcode_2.4-2_armel.deb
    + echo /media/ixp4xx-microcode_2.4-2_armel.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/ixp4xx-microcode_2.4-2_armel.deb /var/cache/firmware/
    + basename /media/ixp4xx-microcode_2.4-2_armel.deb
    + udpkg --unpack /var/cache/firmware/ixp4xx-microcode_2.4-2_armel.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/libertas-firmware_5.110.22.p14-1_all.deb ]
    + list_deb_firmware /media/libertas-firmware_5.110.22.p14-1_all.deb
    + ar p /media/libertas-firmware_5.110.22.p14-1_all.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/libertas-firmware_5.110.22.p14-1_all.deb
    + echo /media/libertas-firmware_5.110.22.p14-1_all.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/libertas-firmware_5.110.22.p14-1_all.deb /var/cache/firmware/
    + basename /media/libertas-firmware_5.110.22.p14-1_all.deb
    + udpkg --unpack /var/cache/firmware/libertas-firmware_5.110.22.p14-1_all.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/zd1211-firmware_2.16.0.0-0.1_all.deb ]
    + list_deb_firmware /media/zd1211-firmware_2.16.0.0-0.1_all.deb
    + ar p /media/zd1211-firmware_2.16.0.0-0.1_all.deb data.tar.gz
    + grep -qf /tmp/grepfor
    + tar zt
    + grep ^\./lib/firmware/
    + sed -e s!^\./lib/firmware/!!
    + install_firmware_pkg /media/zd1211-firmware_2.16.0.0-0.1_all.deb
    + echo /media/zd1211-firmware_2.16.0.0-0.1_all.deb
    + grep -q \.deb$
    + mkdir -p /var/cache/firmware/
    + cp -a /media/zd1211-firmware_2.16.0.0-0.1_all.deb /var/cache/firmware/
    + basename /media/zd1211-firmware_2.16.0.0-0.1_all.deb
    + udpkg --unpack /var/cache/firmware/zd1211-firmware_2.16.0.0-0.1_all.deb
    (Reading database...)
    (Updating database...)
    + [ -f /media/*.udeb ]
    + [ -f /media/*.ude ]
    + rm -f /tmp/grepfor
    + umount /media
    + modprobe -r bnx2
    + modprobe bnx2
    + modprobe -r bnx2
    + modprobe bnx2
    + read_log
    + modules=
    + files=
    + [ -s /tmp/missing-firmware ]
    + [ -n ]
    + return 1

    [2]
    --- check-missing-firmware.sh (revision 54571)
    +++ check-missing-firmware.sh (working copy)
    @@ -98,7 +98,7 @@
    # This does not use anna because debs can have arbitrary
    # dependencies, which anna might try to install.
    if mountmedia driver; then
    - echo "$files" | sed -e 's/ /\n/g' >/tmp/grepfor
    + echo "$files" | sed 's/\ $//' | sed -e 's/ /\n/g' >/tmp/grepfor
    for filename in /media/*.deb /media/*.udeb /media/*.ude /media/firmware/*.deb /media/firmware/*.udeb /media/firmware/*.ude; do
    if [ -f "$filename" ]; then
    if check_deb_arch "$filename" && list_deb_firmware "$filename" | grep -qf /tmp/grepfor; then





    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  8. Bug#492205: installation-reports: firmware load testing

    dann frazier wrote:
    > I couldn't get this image to work; it seems to load bnx2 on startup
    > automatically and, after a 'modprobe -r bnx2', it doesn't seem to ever
    > bring up the fw prompt.


    The only change I've made that could affect the firmware prompt at all is this
    one:

    - for line in $(cat $LOG.old); do
    + for line in $(sort $LOG.old | uniq); do

    Unless my image is just broken in some way, and /tmp/missing-firmware
    doesn't get populated, or check-missing-firmware fails to run.

    > And this is because "$files" has a trailing space:


    Ah, I see it now, it does in fact always add a trailing space.
    And the fix I already checked in to make list_deb_firmware avoid listing empty
    lines didn't actually fix that, because grep "" file matches all lines
    in the file. Ok, fix checked in.

    --
    see shy jo

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.9 (GNU/Linux)

    iD8DBQFIiRRrd8HHehbQuO8RAlMfAJ99Od13MDwfVAAV3+59Ao YhfiyX+ACfavdW
    xXLsHUSpvhvCn3oLj+0x1II=
    =6vZ9
    -----END PGP SIGNATURE-----


  9. Bug#492249: marked as done (does not handle firmware packages for other architectures on media)


    Your message dated Fri, 25 Jul 2008 21:47:03 +0000
    with message-id
    and subject line Bug#492249: fixed in hw-detect 1.65
    has caused the Debian Bug report #492249,
    regarding does not handle firmware packages for other architectures on media
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system
    misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    492249: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492249
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


  10. Bug#492247: marked as done (install more firmware packages than required)


    Your message dated Fri, 25 Jul 2008 21:47:03 +0000
    with message-id
    and subject line Bug#492247: fixed in hw-detect 1.65
    has caused the Debian Bug report #492247,
    regarding install more firmware packages than required
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system
    misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    492247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492247
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


  11. Bug#492246: marked as done (firmware listed multiple times during firmware loading)


    Your message dated Fri, 25 Jul 2008 21:47:03 +0000
    with message-id
    and subject line Bug#492246: fixed in hw-detect 1.65
    has caused the Debian Bug report #492246,
    regarding firmware listed multiple times during firmware loading
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system
    misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    492246: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492246
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


  12. Bug#492205: installation-reports: firmware load testing

    * Joey Hess [2008-07-24 19:46]:
    > Ah, I see it now, it does in fact always add a trailing space.
    > And the fix I already checked in to make list_deb_firmware avoid listing empty
    > lines didn't actually fix that, because grep "" file matches all lines
    > in the file. Ok, fix checked in.


    So can this bug be closed now or is there anything else that hasn't
    been resolved yet?
    --
    Martin Michlmayr
    http://www.cyrius.com/



    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  13. Bug#492205: marked as done (installation-reports: firmware load testing)


    Your message dated Mon, 15 Sep 2008 10:10:31 -0600
    with message-id <20080915161030.GA1731@colo.lackof.org>
    and subject line Re: Bug#492205: installation-reports: firmware load testing
    has caused the Debian Bug report #492205,
    regarding installation-reports: firmware load testing
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system
    misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    492205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492205
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


  14. Bug#492205: installation-reports: firmware load testing

    On Sat, Sep 13, 2008 at 02:24:21PM +0300, Martin Michlmayr wrote:
    > * Joey Hess [2008-07-24 19:46]:
    > > Ah, I see it now, it does in fact always add a trailing space.
    > > And the fix I already checked in to make list_deb_firmware avoid listing empty
    > > lines didn't actually fix that, because grep "" file matches all lines
    > > in the file. Ok, fix checked in.

    >
    > So can this bug be closed now or is there anything else that hasn't
    > been resolved yet?


    I believe it to be resolved. Closing.

    --
    dann frazier




    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

+ Reply to Thread