[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#317381: discover1: detection runs too late on boot



Package: discover1
Version: 1.7.7
Severity: minor


Under /etc/rcS.d the discover script is at S36. Is there a reason it is
so late in the boot process? Surely having all hardware known as much as
possible, and as early as possible, would be for the best?

Specifically for my usage recently, discover runs after 'mdadm-raid'
(S25), meaning in my case that the sata drives the raid was on were
unavailable. This caused headaches (since it wasn't initially obvious
what the problem was - since after system boot, the raid started fine)

Shouldn't discover be closer to the other module-loading init scripts?
(S20module-init-tools and S20modutils?)

-Cameron


-- Package-specific info:
lspci:
0000:00:00.0 0600: 10de:01e0 (rev c1)
0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
0000:00:00.1 0500: 10de:01eb (rev c1)
0000:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
0000:00:00.2 0500: 10de:01ee (rev c1)
0000:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
0000:00:00.3 0500: 10de:01ed (rev c1)
0000:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
0000:00:00.4 0500: 10de:01ec (rev c1)
0000:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
0000:00:00.5 0500: 10de:01ef (rev c1)
0000:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
0000:00:01.0 0601: 10de:0060 (rev a4)
0000:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
0000:00:01.1 0c05: 10de:0064 (rev a2)
0000:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
0000:00:02.0 0c03: 10de:0067 (rev a4)
0000:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.1 0c03: 10de:0067 (rev a4)
0000:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.2 0c03: 10de:0068 (rev a4)
0000:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:06.0 0401: 10de:006a (rev a1)
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
0000:00:08.0 0604: 10de:006c (rev a3)
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
0000:00:09.0 0101: 10de:0065 (rev a2)
0000:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
0000:00:1e.0 0604: 10de:01e8 (rev c1)
0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
0000:01:06.0 0300: 10de:002d (rev 15)
0000:01:06.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15)
0000:01:0b.0 0200: 10ec:8169 (rev 10)
0000:01:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10)
0000:01:0d.0 0180: 1095:3512 (rev 01)
0000:01:0d.0 Unknown mass storage controller: Silicon Image, Inc. (formerly CMD Technology Inc) SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01)
0000:01:0e.0 0c00: 104c:8024
0000:01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link)

discover:

-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)

Versions of packages discover1 depends on:
ii  dash                        0.5.2-4      The Debian Almquist Shell
ii  debconf                     1.4.30.13    Debian configuration management sy
ii  discover1-data              1.2005.01.08 hardware lists for libdiscover1
ii  libc6                       2.3.2.ds1-22 GNU C Library: Shared libraries an
ii  libdiscover1                1.7.7        hardware identification library

-- debconf information excluded



Reply to: