[1149] in linux-scsi channel archive
TMC-1610M SCSI controller
daemon@ATHENA.MIT.EDU (andy-jacobson@psu.edu)
Sat Dec 21 12:15:07 1996
To: submit-linux-dev-scsi@yggdrasil.com
From: andy-jacobson@psu.edu
Date: 21 Dec 1996 12:13:29 -0500
Howdy, Folks-
So I just wanted to do a *good deed* for the holiday season,
you know, and introduce my bro to the glorious power of home
Linuxing. Unfortunately, his SCSI controller seems to have
an alternate agenda.
He's got a monster new PPro system from Gateway--(E?)IDE
disk, ATAPI CD-ROM, etc. Into this box he has installed an
old Future Domain TMC-1610M SCSI controller which runs the
disk on which we want to install Linux. Win95 has no problem
seeing the SCSI drive.
Neither Redhat 4.0's boot kernel, nor the Slackware 2.3.mumble
"idecd" image detect the SCSI host. Strange, since it appears
from all HOWTOs, docs, etc., that this is a "well-known" card.
We know the base mem address, I/O base and IRQ used by the card,
and I have tried many--but probably not all--syntax combinations
to tell the kernel at boot time about this card.
e.g.: tmc16x0=0xca000,10,0x140
tmc1610=0xca0,0x140,10
etc.
I have a suspicion. The card does not have a BIOS
chip installed in the socket apparently designated for it.
My brother's response: "No wonder it was so cheap." If this
were indeed the case, would this make us S.O.L.? How is it
that MS slothware can work this card, but dear ol' Linux
cannot?
I can't seem to find any examples of the kernel boot parameter
syntax for the tmc16x0 card. Is there help for this somewhere?
Thanks in advance. Let's try to save this one guy at least
from the horrible ignorance of a Win95-only existence!
Cheers,
Andy
--
andy-jacobson@psu.edu "When the only tool you own is a hammer,
Department of Meteorology every problem begins to resemble a nail."
Penn State University -- Abraham Maslow
