Dual 2940UW how do I specify which one kernal sees first?

Dual 2940UW how do I specify which one kernal sees first?

Post by Peter McArdl » Mon, 29 Dec 1997 04:00:00

I have Dual 2940UW cards. How do I specify which one the kernal sees
I would like linux to see the one with my primary hard drive attached
Instead it sees the one with my removable drive. This causes problems
I remove that device from my scsi chain. sda and sdb change and linux
becomes unhappy. (it won't boot)  I can't just switch which card I have
devices attached to because the one with my hard drive is on the
Any pointers would be appreciated.



1. Two SCSI controllers, one PCI (AHA-2940UW) and one ISA (Iomega's)

We have a Pentium Pro 200 that came with an internal Jaz drive on a Adaptec
2940UW PCI SCSI controller.  It shared this controller with an internal SCSI
CD-ROM and a 4gig W/F Seagate disk drive.  When we added some *external* SCSI
devices (a 4gig Micropolis A/V disk, a Yamaha CDR100 CDR), the Jaz drive
promptly blew its internal fuse.  And replacing it with several other Jaz
drives, which all blew their fuses with the external stuff connected, we decided
that the Jaz drive just does not like one (or more) of the external devices. So,
we are getting its own private SCSI controller.

Question: this controller is the standard, "cheap" ISA controller. It has not
arrived yet, but we are wondering:  will the system BIOS ROMs see this ISA
board before or after the PCI SCSI board?  If before, this will make the Jaz
drive /dev/sda and the system boot disk /dev/sdb.  I expect that LILO will be
most unhappy (if things in fact get that far, but I guess the BIOS can be told
to boot from A (floppy), then D (*second*) hard disk, then we have to have fun
with a boot/rescue floppy, diddle the fstab, fuss with lilo.conf, etc.

Random thoughts:

Linux is the *only* UNIX system that does NOT map SCSI controller# & IDs directly
to device names.  Instead it does a *first come, first served* drive assignment
game (ala the IntelPC BIOS & MS-*).  This can be a real pain in various
situations, esp. with portable (external) SCSI devices.  It would be *nice*
if there was a patch (or replacement SCSI module) that did a hard mapping from
controller# + SCSI ID to device name.  Iris for example has raw device names
that include the controller number and the device ID.  One can pull a bad disk
out and not have to edit fstab (except maybe to comment out the missing
partitions).  I realize that it is not possible to treat IDE devices this
way (or is it?), since IDE devices don't have ID numbers like SCSI devices.


http://vis-www.cs.umass.edu/~heller  ||FidoNet:    1:321/153
http://netmar.com/mall/shops/heller  /\

2. Axil-320 sparc & Data Access Exception?

3. First drive SCSI - not seen as first drive

4. SCSI recommends rewrite -- how?

5. Dual OS on one hdd: Win95 or Linux on the first partition?

6. web server user id in at.deny list?

7. Dual NIC, One Cable one for NT Network...

8. populating password field in passwd table using nispopulate?

9. Booting from two kernels one single-proc, one SMP: Dual Module Paths???

10. Dual setup questions(one small, one big)

11. Dual Hard drive -VS- One Partitioned one!!!

12. Dos/os2/Linux and 2 hd's one 850, and one 425

13. If you need AIX work done, this company is one of the better ones.