Your message dated Sat, 29 May 2004 06:17:04 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#236423: fixed in discover1-data 1.2004.02.08-7
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Mar 2004 07:48:38 +0000
>From [EMAIL PROTECTED] Fri Mar 05 23:48:38 2004
Return-path: <[EMAIL PROTECTED]>
Received: from dsl-203-113-235-229.act.netspace.net.au (caesar.andrew.net.au)
[203.113.235.229]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AzWY0-00044X-00; Fri, 05 Mar 2004 23:48:37 -0800
Received: from brutus (brutus.andrew.net.au [172.16.0.2])
by caesar.andrew.net.au (8.12.11.Beta0/8.12.11.Beta0/Debian-1) with ESMTP id
i267mTjv016584;
Sat, 6 Mar 2004 18:48:29 +1100
Received: from apollock by brutus with local (Exim 4.30)
id 1AzWXt-0000ic-0k; Sat, 06 Mar 2004 18:48:29 +1100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Andrew Pollock <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: discover: sprays lots of daunting error messages during boot
X-Mailer: reportbug 2.37
Date: Sat, 06 Mar 2004 18:48:28 +1100
Message-Id: <[EMAIL PROTECTED]>
Sender: Andrew Pollock <[EMAIL PROTECTED]>
X-Scanned-By: MIMEDefang 2.39
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_05
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no
version=2.60-bugs.debian.org_2004_03_05
X-Spam-Level:
Package: discover
Version: 1.5-1.4.3
Severity: normal
Hi,
I'm doing test installs of d-i, and one of the points of feedback I had
was that on my system, when discover ran during the boot of the newly
installed system, it sprayed a lot of daunting looking error messages.
For me, this is only a minor inconvenience in that it blows away my
scrollback buffer, so I can't review the whole bootup, but for a newbie,
it could be quite alarming.
What I've done to reproduce this is run discover again, after bootup.
This is the output from running discover:
Detecting hardware: agpgart eepro100 es1370 i810_rng ich2rom ide-scsi
usb-uhci
Loading agpgart module.
Loading eepro100 module.
Loading es1370 module.
Loading i810_rng module.
/lib/modules/2.4.24-1-686/kernel/drivers/char/i810_rng.o: init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.24-1-686/kernel/drivers/char/i810_rng.o: insmod
/lib/modules/2.4.24-1-686/kernel/drivers/char/i810_rng.o failed
/lib/modules/2.4.24-1-686/kernel/drivers/char/i810_rng.o: insmod
i810_rng failed
Loading ich2rom module.
/lib/modules/2.4.24-1-686/kernel/drivers/mtd/maps/ich2rom.o:
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.24-1-686/kernel/drivers/mtd/maps/ich2rom.o: insmod
/lib/modules/2.4.24-1-686/kernel/drivers/mtd/maps/ich2rom.o failed
/lib/modules/2.4.24-1-686/kernel/drivers/mtd/maps/ich2rom.o: insmod
ich2rom failed
Loading ide-scsi module.
Loading usb-uhci module.
and this is the dmesg output (which is what goes all over the console
during boot):
i810_rng: RNG not detected
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
Search for id:(ff ff) interleave(1) type(1)
Search for id:(bf 57) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(1)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
Search for id:(ff ff) interleave(1) type(2)
JEDEC: Found no ICH2 rom device at location zero
My actual system is a Pentium IV system, with an MSI mainboard, IDE
disks, PCI soundcard, PCI Intel EtherExpressPro 100 NIC, PCI IEEE1394
card, and not a lot else exciting. Here's an lspci in case it's
relevant:
00:00.0 Host bridge: Intel Corp. 82845 845 (Brookdale) Chipset Host Bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 82845 845 (Brookdale) Chipset AGP Bridge (rev 03)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev 12)
00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 12)
00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 12)
00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 12)
00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 12)
00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 12)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev
b2)
03:00.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev 01)
03:01.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08)
03:02.0 FireWire (IEEE 1394): Texas Instruments TSB12LV23 IEEE-1394 Controller
if there's any more information I can provide to be of assistance,
please let me know.
regards
Andrew
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux brutus 2.4.24-1-686 #1 Tue Jan 6 21:29:44 EST 2004 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages discover depends on:
ii ash 0.4.19 Compatibility package for the Debi
ii dash 0.4.19 The Debian Almquist Shell
ii debconf 1.3.22 Debian configuration management sy
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libdiscover1 1.5-1.4.3 hardware identification library
-- debconf information:
discover/manage_cdrom_devices: true
discover/cdrom_base_mountpoint: /
discover/cdrom_base_mountpoint_error:
---------------------------------------
Received: (at 236423-close) by bugs.debian.org; 29 May 2004 10:23:04 +0000
>From [EMAIL PROTECTED] Sat May 29 03:23:04 2004
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BU0zX-0007BJ-00; Sat, 29 May 2004 03:23:03 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1BU0tk-0007pp-00; Sat, 29 May 2004 06:17:04 -0400
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.49 $
Subject: Bug#236423: fixed in discover1-data 1.2004.02.08-7
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 29 May 2004 06:17:04 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Source: discover1-data
Source-Version: 1.2004.02.08-7
We believe that the bug you reported is fixed in the latest version of
discover1-data, which is due to be installed in the Debian FTP archive:
discover1-data-udeb_1.2004.02.08-7_all.udeb
to pool/main/d/discover1-data/discover1-data-udeb_1.2004.02.08-7_all.udeb
discover1-data_1.2004.02.08-7.dsc
to pool/main/d/discover1-data/discover1-data_1.2004.02.08-7.dsc
discover1-data_1.2004.02.08-7.tar.gz
to pool/main/d/discover1-data/discover1-data_1.2004.02.08-7.tar.gz
discover1-data_1.2004.02.08-7_all.deb
to pool/main/d/discover1-data/discover1-data_1.2004.02.08-7_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Petter Reinholdtsen <[EMAIL PROTECTED]> (supplier of updated discover1-data package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 29 May 2004 06:46:40 -0300
Source: discover1-data
Binary: discover1-data discover1-data-udeb
Architecture: source all
Version: 1.2004.02.08-7
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <[EMAIL PROTECTED]>
Changed-By: Petter Reinholdtsen <[EMAIL PROTECTED]>
Description:
discover1-data - hardware lists for libdiscover1
discover1-data-udeb - hardware lists for libdiscover1 (short list) (udeb)
Closes: 236423 244195 248139 249633 250310
Changes:
discover1-data (1.2004.02.08-7) unstable; urgency=low
.
* Gaudenz Steinlin
- Use sata_promise module for PDC20378 (SATA150 TX) (105a3373);
(Closes: #244195)
- Use ata_piix module for 82801EB (ICH5) Serial ATA 150
Storage Controller (808624d1); (Closes: #250310, #249633)
- Use ohci1394 for R5C551 IEEE 1394 Controller and
TSB43AB21 IEEE-1394a-2000; (Closes: #248139)
- Remove wrong modules for 82801BA ISA Bridge (LPC) (80862440) and
82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (8086244e)
(Closes: #236423)
* Petter Reinholdtsen
- Add target 'check-pci-types' to list all used categories
which are unknown to discover1.
- Add myself as uploader.
Files:
b8534f49f219d8016e53e3f0ce12c6b4 713 libs optional discover1-data_1.2004.02.08-7.dsc
1b6fb3a9330c1d2a54e5840920b89eb8 156136 libs optional
discover1-data_1.2004.02.08-7.tar.gz
5f15a2c45bd0568e485c0619bb192b91 14292 debian-installer extra
discover1-data-udeb_1.2004.02.08-7_all.udeb
8fc8196168622e479a5768009cf2c4e6 87544 libs optional
discover1-data_1.2004.02.08-7_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAuFwl20zMSyow1ykRAoESAJ9rSQrPGdN0i1904Kw1ScGUfa3KHgCfd2Q/
mFxgcLyZmasWpKhg6prKcfo=
=v+xS
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
