Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!newshost.telstra.net!act.news.telstra.net!psgrain!usenet.eel.ufl.edu!news.mathworks.com!uunet!in2.uu.net!news.new-york.net!ritz.mordor.com!news From: giff@mordor.com (David Gifford) Subject: SCSI problems on ASUS SC200 (NCR) X-Newsreader: Forte Free Agent 1.0.82 X-Nntp-Posting-User: giff Sender: news@ritz.mordor.com (Network News) Organization: Mordor International Message-ID: <Dno01r.J7u@ritz.mordor.com> X-Nntp-Posting-Host: ritz.mordor.com Date: Sat, 2 Mar 1996 23:57:07 GMT Lines: 46 SCSI experts, please read! System: ASUS P/I-P55TP4XE ASUS SC200 PCI SCSI (NCR) SEAGATE ST32550N 2-Gig SCSI Hard Drive ATI Graphics Xpression (Mach 64 DDRAM), PCI Texel (now Plextor) DM-3024 SCSI CD-ROM (NetwOrk card pulled to keep things simple.) I can't get this system to install the Walnut Creek CDROM distribution of 2.1. After reading about the Mach64-serial port conflict, I was able to start a Novice install OK, set up the drive geometry as 1023/128/32, select some options, and start copying files. But each time, the system starts acting up. Symptoms: CD "in use" (red) LED comes on and stays on. Get messages in VTY 2 about no inodes available. Install aborts after the installer realizes that a lot of chunks weren't installed. It's like the SCSI bus just went *crash*! I've tried 4 sets of SCSI cables and gone over termination several times. I am using pretty generic SCSI cables, however. Is this just a problem with SCSI interference? Or is there something I can look for which might indicate a faulty CD-ROM player? Why doesn't the SCSI bus get reset? This system installed and booted DOS and NT just fine. Any help appreciated. Even if its just to say "I've got that system and it works just fine." Thanks! =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=* David Gifford giff@mordor.com