[2324] in linux-scsi channel archive
Re: PCI/SCSI AHA-2920 problems installing SW 3.2 - HELP!
daemon@ATHENA.MIT.EDU (Steffen Grunewald)
Thu Aug 21 12:07:21 1997
From: Steffen Grunewald <steffen@gfz-potsdam.de>
To: rumbalj@gov.on.ca (John Rumball)
Date: Thu, 21 Aug 1997 17:43:15 +0200 (MET DST)
Cc: linux-scsi@vger.rutgers.edu, jer@isys.ca, als@di.uminho.pt
In-Reply-To: <3.0.1.32.19970821104342.0069f918@govonca2.gov.on.ca> from "John Rumball" at Aug 21, 97 10:43:42 am
"John Rumball writes"
|>
|> This morning I was finally successful at getting Linux to recognize my
|> 2920 by using the following boot prompt command:
|>
|> boot: ramdisk fdomain=0x6100,10,7
|>
|> With this, it identified my internal Seagate SCSI HD, and my external
|> CD-ROM drive and Zip drive. The only problem is that is assigns /dev/sda
|> to my external ZIP drive and then complains that it cannot read the
|> partition table (ie. there was no ZIP disk in the drive!) when I run fdisk.
|>
|> My question now is, how do I get Linux to assign /dev/sda to the internal
|> HD instead of to the external ZIP? Or do I even need to wory about this?
|> I want to be able to boot Linux off my HD, not my ZIP.
|>
Do you have only one controller ? If so, check the SCSI target ID's of
both devices. Device names are assigned in 'lexicographic' order by
controller_number+target_id ... The internal HD should have a smaller ID
than the ZIP. (The ZIP has a SCSI interface, I read from the text above.)
If you've got two controllers in your system, change scsi.c so that the
controller holding your HD comes first.
Good luck !
--
Steffen Grunewald | email steffen@gfz-potsdam.de | fax (+49)-331-8877 520
GeoForschungsZentrum Potsdam, Telegrafenberg A17, D-14473 Potsdam, Germany
http://www.gfz-potsdam.de/
/* Disclaimer : I don't speak for my employers, they don't speak for me */
