Re: more on scsi controllers
> -- using template mhl.format --
> Date: Tue, 24 Jun 97 20:54:15 EDT
> To: Rick Hawkins <rhawkins@iastate.edu>
> cc: debian-user@lists.debian.org
>
> From: Paul Wade <paulwade@greenbush.com>
> Subject: Re: more on scsi controllers
>
> X-Sender: paulwade@greenbush.greenbush.lan
> In-Reply-To: <[🔎] 9706250036.AA15926@pv3439.vincent.iastate.edu>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
>
> Try making a 1.3 rescue disk and booting it with the fdomain parameters.
> If you watch the screen (fast) during boot, you should see whether it got
> the scsi controller OK or not. If that works, then it's just a matter of
> configuring the kernel and LILO on your system.
I can't make the floppy at the moment; it seems not to work. However, I
now have an appropriate kernel on the machine. Answering lilo with
Linux fdomain=0x140,11
does not result in loading the module.
However,
insmod fdomain gives me (roughly; from another screen)
scsi0 <fdomain>: BIOS version 3.4 at 0xc8000 using scsi id 7
scsi0 <fdomain>: TMC-1830 chip at 0x140 irq 11
scsi0: Future Domain TMC-16x0 SCSI driver, version 5.44
scsi : 1 host
Vendor NEC Model: CD-ROM DRIVE:83 Rev: 1.0
Type: CD-ROM ANSI SCSI Revision: 01
Detected CD-ROM sr0 at scsi0, chanel 0, id0, lun0
is /dev/sr0 the correct device, then?
So I tried ./MAKEDEV sr0, which gave me the device.
Then
bash-2.00# mount /dev/sr0 /cdrom -t iso9660
mount: block device /dev/sr0 is write-protected, mounting read-only
which results in the cd making some noise, and the system hang.
a couple of things: should it be /dev/scd0, or /dev/sdc0? it seems to
be scd, but the howto referss consistently to sdc.
is it possible that it simply needs several minute to load? There's
another access a couple of minutes later.
I suppose I'll leave it runnning & see if it comes back by morning.
rick
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: