[261] in linux-scsi channel archive
Re: Pentium/Neptune, NCR 53C810, Fujitsu M2915S-512 Slackware 2.3
daemon@ATHENA.MIT.EDU (Drew Eckhardt)
Sun Jun 18 21:03:44 1995
To: Jeremy Anderson <jsa@TranSend.com.tw>
cc: linux-scsi@vger.rutgers.edu
In-reply-to: Your message of "Fri, 16 Jun 1995 11:02:25 +0800."
<Pine.SUN.3.91.950616105024.17372C-100000@keelung>
Date: Sun, 18 Jun 1995 18:28:49 -0600
From: Drew Eckhardt <drew@poohsticks.org>
In message <Pine.SUN.3.91.950616105024.17372C-100000@keelung>, jsa@transend.com
.tw writes:
>On Thu, 15 Jun 1995, Drew Eckhardt wrote:
>
>> In message <Pine.SUN.3.91.950615120118.18547A-100000@transend.com.tw>, jsa@t
>ran
>> send.com.tw writes:
>>
>> No idea what's going on there; like the SCSI-HOWTO says, you
>> should include the kernel revision when you're having a problem since
>> there's no way for the developers to keep track of what Slackware
>> revision X.Y corresponds to.
>
>kernel is 1.2.8 Sorry for the omission.
>
>> >Boot from Slackware 2.1 stock SCSI 1.44 boot disk:
>
>kernel here is 1.1.9 (I believe)
Very unlikely; Linux 1.1.12 was the first kernel for which patches
were made, Linux 1.1.19 the first kernel for which patches were publically
available, and 1.1.39 the first to include the NCR driver as standard.
>1) I can ONLY have one big partition. I don't WANT a single 2Gig
> partiton actually. If I try to do multiple partitions, any attempts
> to boot LILO result in:
>
>LI
>
>and then a hang (looks like it read the boot sector and then couldn't
>find the rest).
Note that you need to have your boot images BELOW what the BIOS thinks is
the 1024 cylinder mark. Run dparam.com under DOS to see where this is.
>2) For it to boot under LILO, I have to specify the hd parameter, which
> does go looking for an IDE drive which is not there.
>
>I want to thank everyone who's written in with advice so far. I'll be
>spending today reviewing what's been sent so far. If you need anything
>from Taipei (tea, incense... scary fast mainboards) please don't hesitate
>to call.
If LILO and the BIOS simulation code disagree over what the drive's
H/C/S mapping is, you can override what LILO thinks by editing /etc/disktab.
This won't have nasty side effects with LILO.
You can also use the LILO linear option.
