home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!psinntp!pool!ujlh
- From: ujlh@pool.info.sunyit.edu (James Henrickson)
- Subject: Re: New scsi code.
- Message-ID: <1992Nov22.205033.28837@pool.info.sunyit.edu>
- Organization: State University of New York -- Institute of Technology
- References: <By3383.Fs3@ra.nrl.navy.mil>
- Distribution: comp
- Date: Sun, 22 Nov 1992 20:50:33 GMT
- Lines: 23
-
- In article <By3383.Fs3@ra.nrl.navy.mil> eric@tantalus.nrl.navy.mil (Eric Youngdale) writes:
- >
- > Previously we were sending an INQUIRY command to each
- >target/lun combination at boot time, and we were using this to
- >determine what devices were available. Unfortunately, some devices
- >seem to respond with the same information to each lun, and the scsi
- >code was becoming confused.
- >
-
- It seems the SCSI code gets confused rather easily. :-)
-
- I'd like to pass a little info along to anyone checking out Linux for
- the first time: IF LINUX WON'T BOOT ON YOUR NON_SCSI SYSTEM, MAKE SURE
- YOU DON'T HAVE ANYTHING USING I/O PORT 300H. I had to change the address
- of my NE2000 card (easier than pulling the card), install Linux, and rebuild
- the kernel without SCSI support before I could change the address back
- to 300H.
-
- --
- Jim H.
- *
- * James L. Henrickson | "I don't need a signature, I need a job!"
- * ujlh@sunyit.edu | BSCS, December 1992
-