Re: Second try--can someone interpret these install boot messages?
On Fri, Sep 18, 1998 at 12:20:27PM -0700, Ian Eure wrote: In some cases, with older drive types and/or systems, you can cheat a bit by enabling the system ROM shadow option in your CMOS. I really doubt that this would work on a PS/2, but my older AMD 386DX/40 (a truly super system) with dual seagate 40meg MFM drives (yeah!) didn't like to boot linux without having the main bios shadowed. If it was unshadowed, it wouldn't autodetect the drive geometry. Kinda weird, but it's a kinda weird box, right? Anyways. Neat trick nonetheless. :) Thanks for the suggestion. Unfortunately, for the PS/2 it was another dead end. Since Linux seems not doable for this machine, I've installed WFWG and I'll run Samba. My thanks to those who posted suggestions. Curt Daugaard [EMAIL PROTECTED]
Re: Second try--can someone interpret these install boot messages?
On Thu, Sep 17, 1998 at 04:09:06PM -0500, Nathan E Norman wrote:
On Thu, 17 Sep 1998, Curt Daugaard wrote:
[ snip ]
:hd: controller still busy
:hda: reset timed out: status=0xff { Busy DriveReady WriteFault
:SeekComplete DataRequest CorrectedError Index Error }
:hda: reset timed out: error=0xff { BadSector UncorrectableError
:SectorIdNotFound DriveStatusError TrackZeroNotFound
:AddrMarkNotFound }, CHS=65535/15/255, Sector=0
Drive looks toasted. However ...
: The weird thing: the CHS numbers don't match either what CMOS says
: (under MSD in DOS) or what I pass to the kernel at the boot
: prompt, i.e. hd=1010,12,55. (The drive is a WD Caviar 340 MB.)
Try passing the geometry at the boot prompt:
hda=1010,12,55
The help on the boot floppy is wrong, you can't say hd=...; you must
say hda, hdb, or whatever.
We intsalled on a Tandy machine the other dau that refused to work at
all unless we passed the drive's geometry with hda=... and also
specified hdb=none
You should get the Bootprompt-HOWTO. It addresses many problems of this
type.
In some cases, with older drive types and/or systems, you can cheat a bit
by enabling the system ROM shadow option in your CMOS. I really doubt
that this would work on a PS/2, but my older AMD 386DX/40 (a truly super
system) with dual seagate 40meg MFM drives (yeah!) didn't like to boot
linux without having the main bios shadowed. If it was unshadowed, it
wouldn't autodetect the drive geometry. Kinda weird, but it's a kinda
weird box, right? Anyways. Neat trick nonetheless. :)
PS: Sorry for any incoherency. I'm recovering from a nasty tonsilitis
and am all drugged up on antibiotics stuff. Heh.
--
__
| ian eure, network admin, freelance security consultant, and |
| manically depressed paranoid schizophrenic, at your service. |
; [EMAIL PROTECTED] - http://minion.org ;
: raw speed = 105.6 wpm with 4.5% errors :
. . . . . . . . . . . . . . . . . . . . . .
Second try--can someone interpret these install boot messages?
I'll make this as short as I can.
I've been having a devil of a time trying to get the Hamm install
kernel to read my hd at boot. I'm using the lowmem option to
install on a 4mb PS/2 model 35. (By the way, this is one of the
very few PS/2's that have an AT bus, so MCA is not the problem.)
Both drives I tried are able to boot into DOS and Windows and
check out okay on diagnostic checks.
A newsgroup post suggested compiling a kernel with the old
harddisk MFM/RLL/IDE driver. I did and wrote it to the lowmem
bootdisk. The boot messages say a lot more now, but I'm unable to
interpret them. Can someone on the list give them a shot? Here
they are:
hd: controller still busy
hda: reset timed out: status=0xff { Busy DriveReady WriteFault
SeekComplete DataRequest CorrectedError Index Error }
hda: reset timed out: error=0xff { BadSector UncorrectableError
SectorIdNotFound DriveStatusError TrackZeroNotFound
AddrMarkNotFound }, CHS=65535/15/255, Sector=0
The weird thing: the CHS numbers don't match either what CMOS says
(under MSD in DOS) or what I pass to the kernel at the boot
prompt, i.e. hd=1010,12,55. (The drive is a WD Caviar 340 MB.)
This may indicate the enhanced IDE driver is needed after all, but
that gives the 'timed-out', 'status=0xff', and 'Busy' messages in
any case.
Any help would be greatly appreciated. I'd really like to put
this idle machine to use.
Thanks.
Curt Daugaard
[EMAIL PROTECTED]
Re: Second try--can someone interpret these install boot messages?
On Thu, 17 Sep 1998, Curt Daugaard wrote:
[ snip ]
: hd: controller still busy
: hda: reset timed out: status=0xff { Busy DriveReady WriteFault
: SeekComplete DataRequest CorrectedError Index Error }
: hda: reset timed out: error=0xff { BadSector UncorrectableError
: SectorIdNotFound DriveStatusError TrackZeroNotFound
: AddrMarkNotFound }, CHS=65535/15/255, Sector=0
Drive looks toasted. However ...
: The weird thing: the CHS numbers don't match either what CMOS says
: (under MSD in DOS) or what I pass to the kernel at the boot
: prompt, i.e. hd=1010,12,55. (The drive is a WD Caviar 340 MB.)
Try passing the geometry at the boot prompt:
hda=1010,12,55
The help on the boot floppy is wrong, you can't say hd=...; you must
say hda, hdb, or whatever.
We intsalled on a Tandy machine the other dau that refused to work at
all unless we passed the drive's geometry with hda=... and also
specified hdb=none
You should get the Bootprompt-HOWTO. It addresses many problems of this
type.
--
Nathan Norman
MidcoNet 410 South Phillips Avenue Sioux Falls, SD
mailto:[EMAIL PROTECTED] http://www.midco.net
finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9)
Re: Second try--can someone interpret these install boot messages?
On Thu, Sep 17, 1998 at 04:09:06PM -0500, Nathan E Norman wrote: Drive looks toasted. However ... Yes, it does boot DOS and Windows. : The weird thing: the CHS numbers don't match either what CMOS says : (under MSD in DOS) or what I pass to the kernel at the boot : prompt, i.e. hd=1010,12,55. (The drive is a WD Caviar 340 MB.) Try passing the geometry at the boot prompt: hda=1010,12,55 Unfortunately I tried that too. The help on the boot floppy is wrong, you can't say hd=...; you must say hda, hdb, or whatever. According to the kernel sources, for the old hd drivers (not enhanced IDE) you need to use hd=. We intsalled on a Tandy machine the other dau that refused to work at all unless we passed the drive's geometry with hda=... and also specified hdb=none You should get the Bootprompt-HOWTO. It addresses many problems of this type. I gave that a good looking over, believe me. But thanks anyway. Best regards, Curt
