Very Computer

I am trying to install Linux on a Pentium/60 that has
a Future Domain TMC-3260 PCI SCSI controller card.  The board
uses FD's TMC-36C70 on it.  When I try to load Slackware using
the SCSI boot disk, I get the following error:

scsi0 <fdomain>: BIOS version 3.4 at 0xc8000 using scsi id 7
scsi0 <fdomain>: TMC-18C30 chip at 0xf8000 irq <none> (PCI bus)
Kernel panic: fdomain *NO* interrupt level selected.

Does anyone know why this error occurs?  Looks like the boot disk is
trying to find a TMC-18C30 instead of a TMC-36C70.  Has anyone
successfully loaded from a SCSI CD-ROM using this SCSI controller?
If so, please help!!!

Thanks in advance!

School of Electrical Engineering              
  ___  _____  ____  _  _  ____  __    __  
 / __)(  _  )(  _ \( \( )( ___)(  )  (  )  
( (__  )(_)(  )   / )  (  )__)  )(__  )(__  
 \___)(_____)(_)\_)(_)\_)(____)(____)(____)

http://ukulele.ee.cornell.edu/EE320/MShoemake.html

Quote:> scsi0 <fdomain>: BIOS version 3.4 at 0xc8000 using scsi id 7
> scsi0 <fdomain>: TMC-18C30 chip at 0xf8000 irq <none> (PCI bus)
> Kernel panic: fdomain *NO* interrupt level selected.

> Does anyone know why this error occurs?  Looks like the boot disk is
> trying to find a TMC-18C30 instead of a TMC-36C70.  Has anyone
> successfully loaded from a SCSI CD-ROM using this SCSI controller?
> If so, please help!!!

Yes, I've seen exactly this error.  Basically, there is a list of
IRQ's allowed by the drivers that is designed for the TMC-18C30 and
doesn't include some of the possible ones that the PCI card will use.
It's not really a problem to use another one, except that the software
doesn't know how.

There are two solutions that I know of.

1) If your BIOS allows you to limit the interrupts available to the
PCI bus, try changing which ones are available using the BIOS setup
during the system boot.  You should be able to see which one the SCSI
controller is currently using by looking at the messages from the BIOS
when you boot the machine.

When you eliminate the one that it is currently using, it will migrate
to a new one.  You can repeat this process until you get to one of the
ones that works with the software.  I don't remember which ones these
are, I think 5 and 10 work, probably some others.

2) You can add the new interrupts to the list in the kernel sources
and recompile.  Obviously this is impossible if you can't get the
system to boot, and requires some knowledge of C programming and so
forth.  I recommend the former if you can get it to work.

Greg Nelson