Your message dated 29 Dec 2000 18:12:42 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#80786: 2.2r2 Boot Failure From CDROM
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.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 28 Dec 2000 19:56:14 +0000
>From [EMAIL PROTECTED] Thu Dec 28 13:56:14 2000
Return-path: <[EMAIL PROTECTED]>
Received: from post.tau.ac.il [132.66.16.11]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14Bj9q-00079c-00; Thu, 28 Dec 2000 13:56:14 -0600
Received: from post.tau.ac.il (elvis.iucc.ac.il [128.139.174.10])
by post.tau.ac.il (8.9.3/8.9.3) with ESMTP id VAA00700;
Thu, 28 Dec 2000 21:55:41 +0200 (IST)
Sender: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Date: Thu, 28 Dec 2000 21:55:41 +0200
From: "Jonathan B. Horen" <[EMAIL PROTECTED]>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.18 i586)
X-Accept-Language: en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: 2.2r2 Boot Failure From CDROM
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
Package: boot-floppies
Verson: 2.2r2
flavor: potato
architecture: i386
model: roll-your-own (AMD K6-III/400 on an FIC VA-503A M/B)
memory: 256MB
scsi: n/a
cd-rom: ASUS, ATAPI
network card: Realtek 8139
pcmcia: n/a
Booting from CDROM #1 (acquired from CheapBytes), the boot process runs
fine -- recognizes both my hard drives (Maxtor 20GB and 40GB), my CDROM,
Iomega ZIP drive, and floppy drive -- right up until:
md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
and then quits (hangs) there. No keyboard control (CTL-ALT-DEL
inactive). This is with the 2.2.18pre21 kernel (interestingly, on my
current Redhat/6.2 installation, which I am DYING to replace), I'm
running the 2.2.18 kernel, but I've never encountered this "md driver").
OK, so I looked in the 2.2.18/driver sources and read through md.c --
great, big deal, it's for RAID; so what? Does the kernel get confused
with my 2nd drive and think it's some array? What's the deal?
Alternatively, can I manually turn-OFF the md driver at the boot prompt?
Any ideas what might be going on?
--
JONATHAN B. HOREN UNIX SYSTEM ADMINISTRATION
[EMAIL PROTECTED] IUCC/MACHBA
W: +972-(0)3-640-5203 Tel-Aviv University
F: +972-(0)3-640-9118 Tel-Aviv 69978 Israel
H: +972-(0)3-523-4415 http://www.tau.ac.il/~horen
---------------------------------------
Received: (at 80786-done) by bugs.debian.org; 29 Dec 2000 23:12:19 +0000
>From [EMAIL PROTECTED] Fri Dec 29 17:12:19 2000
Return-path: <[EMAIL PROTECTED]>
Received: from (arroz.fake) [64.22.101.122] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14C8h9-0001B0-00; Fri, 29 Dec 2000 17:12:19 -0600
Received: from arroz.fake (localhost [127.0.0.1])
by arroz.fake (Postfix) with ESMTP
id F208093804; Fri, 29 Dec 2000 18:12:42 -0500 (EST)
Sender: [EMAIL PROTECTED]
To: "Jonathan B. Horen" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#80786: 2.2r2 Boot Failure From CDROM
References: <[EMAIL PROTECTED]>
From: Adam Di Carlo <[EMAIL PROTECTED]>
Date: 29 Dec 2000 18:12:42 -0500
In-Reply-To: "Jonathan B. Horen"'s message of "Thu, 28 Dec 2000 21:55:41 +0200"
Message-ID: <[EMAIL PROTECTED]>
Lines: 33
User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: [EMAIL PROTECTED]
"Jonathan B. Horen" <[EMAIL PROTECTED]> writes:
> Booting from CDROM #1 (acquired from CheapBytes), the boot process runs
> fine -- recognizes both my hard drives (Maxtor 20GB and 40GB), my CDROM,
> Iomega ZIP drive, and floppy drive -- right up until:
>
> md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
>
> and then quits (hangs) there. No keyboard control (CTL-ALT-DEL
> inactive). This is with the 2.2.18pre21 kernel (interestingly, on my
> current Redhat/6.2 installation, which I am DYING to replace), I'm
> running the 2.2.18 kernel, but I've never encountered this "md driver").
>
> OK, so I looked in the 2.2.18/driver sources and read through md.c --
> great, big deal, it's for RAID; so what? Does the kernel get confused
> with my 2nd drive and think it's some array? What's the deal?
The next driver in the list is what is hanging you. I bet it's the
qlogic driver or something.
> Alternatively, can I manually turn-OFF the md driver at the boot prompt?
>
> Any ideas what might be going on?
Yes, and ther'es nothing we can do about it. There is simply no way
to provide one kernel for all i386 machines. At least not in Linux.
Blame IBM or the kernel hackers.
You're solution is to use the 'compact' or 'idepci' flavors, on the
2nd and 3rd CDs.
--
.....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
