Bug#79459: marked as done (UDMA66/HPT370 boot problem)
Your message dated 13 Apr 2001 19:35:44 -0400
with message-id <oahezs5q5r.fsf@arroz.fake>
and subject line bugs closed as of boot-floppies 2.3.1
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; 12 Dec 2000 19:56:34 +0000
>From alexs@halifax.rwth-aachen.de Tue Dec 12 13:56:34 2000
Return-path: <alexs@halifax.rwth-aachen.de>
Received: from stargate.halifax.rwth-aachen.de [134.130.48.4] (qmailr)
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 145vXO-0003np-00; Tue, 12 Dec 2000 13:56:34 -0600
Received: (qmail 31099 invoked from network); 12 Dec 2000 19:54:29 -0000
Received: from neptun.halifax.rwth-aachen.de (HELO neptun) (134.130.48.175)
by stargate.halifax.rwth-aachen.de with SMTP; 12 Dec 2000 19:54:29 -0000
Message-ID: <000a01c06475$a978ee80$af308286@neptun>
From: "Alexander" <alexs@halifax.rwth-aachen.de>
To: <submit@bugs.debian.org>
Subject: UDMA66/HPT370 boot problem
Date: Tue, 12 Dec 2000 20:56:48 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0007_01C0647E.0B2365E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Delivered-To: submit@bugs.debian.org
This is a multi-part message in MIME format.
------=_NextPart_000_0007_01C0647E.0B2365E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Package: Disks-i386
Version: UDMA66
When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100 controller, =
with the UDMA66 boot floppies, the system halts during the boot process. =
Why? Thnanks for any help. I=B4m sorry this description got so long, but =
if someone really wants to help he might need some of the info below.
I=B4m booting debian from the UDMA66 rescue disk. The disk works fine at =
my friends computer (Promise UDMA 66 onboard) and I tried several ones =
with the same result.
When I boot from the Debian 2.2r2 CD I can successfully load the kernel =
and get into the install menu, but I have no harddisk detected. I tried =
loading modules from the UDMA66 driver1-4 disks but then I receive an =
error message saying : "Unable to mount disk".
I also tried booting the UDMA flavor from DOS (loadlin) but then I =
receive the exact same result as shown below.
If someone knows some really good boot parameters (and exact use) that =
will get my HPT370 controller to work with the standard flavor, that =
might also help.
Those are the last boot messages I received. The earlier ones seemed =
unimportant.
...
RAM disk driver initialized: 16 RAM disks of 16384K size
loop: registered device at major 7
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with =
idebus=3Dxx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686a IDE UDMA66 controller on pci0:7.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda: DMA, hdb: DMA
HPT370: IDE controller on PCI bus 00 dev 98
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde: DMA, hdf: pio
ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg: pio, hdh: pio
hda: CDR-8482B, ATAPI CDROM DRIVE
hdb: R/RW 4x4x24, ATAPI CDROM DRIVE
ide: Assuming 33MHz system bus speed for PIO modes; override with =
idebus=3Dxx
>>This is were the system stops working. Nothing happens from here on.
At a friends computer the last line was followed by some lines referring =
to his harddrive : Maxtor ... 512K cache ...
I already tried adding idebus=3D33 as a boot parameter, but the system =
just stopped one line earlier.
I=B4m not running a raid array. I just connected my one and only =
harddrive to the HPT370 controller to take advantage of the UDMA100 =
burst speed.=20
I had the second ide channel (ide1) disabled in the BIOS in case someone =
wondered.
Here=B4s a summary of my system
Athlon TB 900
Abit KT7-Raid Motherboard
IBM DTLA 307030 30GB UDMA100 harddrive connected=20
to HPT370 onboard Raid controller (ide2 master)
128MB PC133 SDRAM
Soundblaster PCI 128
Geforce II MX 32MB AGP video card
SMC 1211TX EZ-Card - PCI network card=20
USB Mouse
Thanks a lot. If you are reading this line, I know that you tried.
Alexander
------=_NextPart_000_0007_01C0647E.0B2365E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<P>Package: Disks-i386</P>
<P>Version: UDMA66</P>
<P><STRONG>When I try installing Debian 2.2r2 on my HPT370 Raid/UDMA100=20
controller, with the UDMA66 boot floppies, the system halts during the =
boot=20
process. Why? Thnanks for any help. I=B4m sorry this description got so =
long, but=20
if someone really wants to help he might need some of the info=20
below.</STRONG></P>
<P><STRONG>I=B4m booting debian from the UDMA66 rescue disk. The disk =
works fine=20
at my friends computer (Promise UDMA 66 onboard) and I tried several =
ones with=20
the same result.</STRONG></P>
<P><STRONG>When I boot from the Debian 2.2r2 CD I can successfully load =
the=20
kernel and get into the install menu, but I have no harddisk detected. I =
tried=20
loading modules from the UDMA66 driver1-4 disks but then I receive an =
error=20
message saying : "Unable to mount disk".</STRONG></P>
<P><STRONG>I also tried booting the UDMA flavor from DOS (loadlin) but =
then I=20
receive the exact same result as shown below.</STRONG></P>
<P><STRONG>If someone knows some really good boot parameters (and exact =
use)=20
that will get my HPT370 controller to work with the standard flavor, =
that might=20
also help.</STRONG></P>
<P><STRONG>Those are the last boot messages I received. The earlier ones =
seemed=20
unimportant.</STRONG></P>
<P> </P>
<P><STRONG>...</STRONG></P>
<P><STRONG>RAM disk driver initialized: 16 RAM disks of 16384K =
size</STRONG></P>
<P><STRONG>loop: registered device at major 7</STRONG></P>
<P><STRONG>Uniform Multi-Platform E-IDE driver Revision: =
6.30</STRONG></P>
<P><STRONG>ide: Assuming 33MHz system bus speed for PIO modes; override =
with=20
idebus=3Dxx</STRONG></P>
<P><STRONG>VP_IDE: IDE controller on PCI bus 00 dev 39</STRONG></P>
<P><STRONG>VP_IDE: chipset revision 16</STRONG></P>
<P><STRONG>VP_IDE: not 100% native mode: will probe irqs =
later</STRONG></P>
<P><STRONG>VP_IDE: VIA vt82c686a IDE UDMA66 controller on =
pci0:7.1</STRONG></P>
<P><STRONG>ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda: DMA, hdb:=20
DMA</STRONG></P>
<P><STRONG>HPT370: IDE controller on PCI bus 00 dev 98</STRONG></P>
<P><STRONG>HPT370: chipset revision 3</STRONG></P>
<P><STRONG>HPT370: not 100% native mode: will probe irqs =
later</STRONG></P>
<P><STRONG>ide2: BM-DMA at 0xe400-0xe407, BIOS settings: hde: DMA, hdf:=20
pio</STRONG></P>
<P><STRONG>ide3: BM-DMA at 0xe408-0xe40f, BIOS settings: hdg: pio, hdh:=20
pio</STRONG></P>
<P><STRONG>hda: CDR-8482B, ATAPI CDROM DRIVE</STRONG></P>
<P><STRONG>hdb: R/RW 4x4x24, ATAPI CDROM DRIVE</STRONG></P>
<P><STRONG>ide: Assuming 33MHz system bus speed for PIO modes; override =
with=20
idebus=3Dxx</STRONG></P>
<P> </P>
<P> </P>
<P><STRONG>>>This is were the system stops working. Nothing =
happens from=20
here on.</STRONG></P>
<P><STRONG>At a friends computer the last line was followed by some =
lines=20
referring to his harddrive : Maxtor ... 512K cache ...</STRONG></P>
<P><STRONG>I already tried adding idebus=3D33 as a boot parameter, but =
the system=20
just stopped one line earlier.</STRONG></P>
<P><STRONG>I=B4m not running a raid array. I just connected my one and =
only=20
harddrive to the HPT370 controller to take advantage of the UDMA100 =
burst speed.=20
</STRONG></P>
<P><STRONG>I had the second ide channel (ide1) disabled in the BIOS in =
case=20
someone wondered.</STRONG></P>
<P></P>
<P> </P>
<P><STRONG>Here=B4s a summary of my system</STRONG></P>
<P><STRONG>Athlon TB 900</STRONG></P>
<P><STRONG>Abit KT7-Raid Motherboard</STRONG></P>
<P><STRONG>IBM DTLA 307030 30GB UDMA100 harddrive connected =
</STRONG></P>
<P><STRONG>to HPT370 onboard Raid controller (ide2 master)</STRONG></P>
<P><STRONG>128MB PC133 SDRAM</STRONG></P>
<P><STRONG>Soundblaster PCI 128</STRONG></P>
<P><STRONG>Geforce II MX 32MB AGP video card</STRONG></P>
<P><STRONG>SMC 1211TX EZ-Card - PCI network card </STRONG></P>
<P><STRONG>USB Mouse</STRONG></P>
<P> </P>
<P><STRONG>Thanks a lot. If you are reading this line, I know that you=20
tried.</STRONG></P>
<P><STRONG>Alexander</STRONG></P></FONT></DIV></BODY></HTML>
------=_NextPart_000_0007_01C0647E.0B2365E0--
---------------------------------------
Received: (at 70798-done) by bugs.debian.org; 13 Apr 2001 23:35:29 +0000
>From adam@onshore.com Fri Apr 13 18:35:29 2001
Return-path: <adam@onshore.com>
Received: from arroz.onshored.com [216.220.101.2] (postfix)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 14oD65-0006YA-00; Fri, 13 Apr 2001 18:35:26 -0500
Received: from arroz.fake (localhost [127.0.0.1])
by arroz.onshored.com (Postfix) with ESMTP
id 9D3E993802; Fri, 13 Apr 2001 19:35:44 -0400 (EDT)
Sender: apharris@burrito.onshore.com
To: 69161-done@bugs.debian.org, 75106-done@bugs.debian.org,
80325-done@bugs.debian.org, 80949-done@bugs.debian.org,
56275-done@bugs.debian.org, 62475-done@bugs.debian.org,
64500-done@bugs.debian.org, 65903-done@bugs.debian.org,
67510-done@bugs.debian.org, 68497-done@bugs.debian.org,
69786-done@bugs.debian.org, 70798-done@bugs.debian.org,
72672-done@bugs.debian.org, 73638-done@bugs.debian.org,
75018-done@bugs.debian.org, 78328-done@bugs.debian.org,
78521-done@bugs.debian.org, 78981-done@bugs.debian.org,
79004-done@bugs.debian.org, 79005-done@bugs.debian.org,
79459-done@bugs.debian.org, 79734-done@bugs.debian.org,
79890-done@bugs.debian.org, 82018-done@bugs.debian.org,
82024-done@bugs.debian.org, 82482-done@bugs.debian.org,
82912-done@bugs.debian.org, 84989-done@bugs.debian.org,
84990-done@bugs.debian.org, 85033-done@bugs.debian.org,
85397-done@bugs.debian.org, 88226-done@bugs.debian.org,
90967-done@bugs.debian.org, 93054-done@bugs.debian.org,
93069-done@bugs.debian.org, 93421-done@bugs.debian.org,
83131-done@bugs.debian.org, 92907-done@bugs.debian.org,
64565-done@bugs.debian.org
Subject: bugs closed as of boot-floppies 2.3.1
From: Adam Di Carlo <adam@onshore.com>
Date: 13 Apr 2001 19:35:44 -0400
Message-ID: <oahezs5q5r.fsf@arroz.fake>
Lines: 24
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Delivered-To: 70798-done@bugs.debian.org
Thank you very much for your bug report. We believe the issue you
reported is solved as of boot-floppies 2.3.1. That is the woody
version of boot-floppies, which is available in the archive, or, some
SPARC and i386, at
<URL:http://people.debian.org/~aph/debian/dists/woody/main/>.
If you feel your bug is still outstanding, please let us know or
reopen your bug -- see <http://www.debian.org/Bugs/> for instructions
how to do that.
We are not longer working on Potato boot-floppies, except for critical
issues. If you feel that your bug hasn't been fixed as of
boot-floppies 2.2.22 (the latest Potato version), then you we need to
reopen your bug and put the 'potato' tag on it. Please be sparing --
the more we are distracted with Potato issues, the less effort we are
able to put into Woody boot-floppies.
Again, thanks for your report. Bug reports are a significant
contribution to Debian. We apologize that it probably took so long to
fix the issue you reported.
--
.....Adam Di Carlo....adam@onshore.com.....<URL:http://www.onshored.com/>
Reply to: