Your message dated Sat, 20 Mar 2004 23:03:27 -0500
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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; 11 Nov 2003 16:23:59 +0000
>From [EMAIL PROTECTED] Tue Nov 11 10:21:57 2003
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42]
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AJbHA-0000nA-00; Tue, 11 Nov 2003 10:21:56 -0600
Received: from dragon.kitenet.net (pm3naxs17-110.access.naxs.com [216.98.94.110])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
by kitenet.net (Postfix) with ESMTP
id BDE2917ED6; Tue, 11 Nov 2003 16:21:54 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
id 494846E0CB; Tue, 11 Nov 2003 11:25:47 -0500 (EST)
Date: Tue, 11 Nov 2003 11:25:47 -0500
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: James Bromberger <[EMAIL PROTECTED]>
Subject: Re: Debian Installer II: sr_mod continued
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="hQiwHBbRI9kgIhsi"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.4i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-10.7 required=4.0
tests=EMAIL_ATTRIBUTION,HAS_PACKAGE,QUOTED_EMAIL_TEXT
autolearn=ham version=2.53-bugs.debian.org_2003_11_9
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_9
(1.174.2.15-2003-03-30-exp)
--hQiwHBbRI9kgIhsi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Package: cdrom-detect
Version: 0.38
(This is on a IBM bladecenter which has a USB cdrom drive.)
James Bromberger wrote:
> I grabbed the 2.4.22-386 kernel and added a few of the modules for
> testing:
> ehci-usb seems to fail to laod (with no explanation in dmesg).
> ohci-usb works
> sr_mod works
> tg3 works (ethernet)
>=20
> And I can access the CD ROM. With it unmounted, the installer still
> fails to detect the cdrom drive; there is no /dev/cdrom symlink made
> when the sr_mod detects the /dev/scsi1/host0/bus0/target0/lun0/cd.
Lets file a bug to that effect. It sounds to me like cdrom-detect should
fall back to prompting with a list of all disks (or at least all scsi
disks) in the system if it cannot find a /dev/cdroms/ device.
BTW, sr_mod will be available on the CD's in a couple of days.
> The tg3 network interface I have is detected, but running udhcpc fails.
> The installer meanwhile has bombed out and also complains about a
> missing floppy still (these IBM blade machines have a USB floppy, not
> one that the floppy controller (floppy.o) seems to recognise). Setting
> the address manually seems to be OK.
I'll bet you have a file in /dev for your USB floppy drive, if you have
usb-storage loaded in addition to the modules listed above. Problem is
the installer doesn't know it's a floppy drive as opposed to a scsi
drive. It would know if you booted off the thing.. If there is a device
entry for your USB floppy drive, I can make a similar change to have it
prompt with a list of scsi devices if it cannot find an obvious floppy
drive.
--=20
see shy jo
--hQiwHBbRI9kgIhsi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/sQ2Kd8HHehbQuO8RAvGmAJ9+8SzZTU3KyPNgbfEDQlmDct6gSQCfVu/W
SjS83pRFKBBETiEpqZy7PbQ=
=aqqw
-----END PGP SIGNATURE-----
--hQiwHBbRI9kgIhsi--
---------------------------------------
Received: (at 220230-done) by bugs.debian.org; 21 Mar 2004 04:04:01 +0000
>From [EMAIL PROTECTED] Sat Mar 20 20:04:01 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B4uBt-0007O7-00; Sat, 20 Mar 2004 20:04:01 -0800
Received: from dragon.kitenet.net (216-98-94-78.access.naxs.com [216.98.94.78])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
by kitenet.net (Postfix) with ESMTP id 65EAE180B0
for <[EMAIL PROTECTED]>; Sun, 21 Mar 2004 04:04:00 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
id CBF6F6E7FA; Sat, 20 Mar 2004 23:03:27 -0500 (EST)
Date: Sat, 20 Mar 2004 23:03:27 -0500
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: fixed
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62"
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level:
--+QahgC5+KEYLbs62
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
This bug was fixed a long time ago.
--=20
see shy jo
--+QahgC5+KEYLbs62
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAXRQPd8HHehbQuO8RAmDbAJ9A/C6elbUsPBtaJBgIfFxBb4dqBQCgxD+A
eCGj75xWZL45OPwiV85hpS0=
=KvsS
-----END PGP SIGNATURE-----
--+QahgC5+KEYLbs62--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
