Date: Tue, 5 May 1998 20:57:22 -0700 (PDT) From: Doug White <dwhite@gdi.uoregon.edu> To: Mike Smith <mike@smith.net.au> Cc: hardware@FreeBSD.ORG Subject: Re: 2.2.6 sysinstall probe problems with ST31621A Message-ID: <Pine.BSF.3.96.980505205605.9802J-100000@gdi.uoregon.edu> In-Reply-To: <199805052157.OAA00535@antipodes.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
limiting discussion to -hardware. > Just to clarify, it's not Sysinstall probing the drive (as such). What > happens is that sysinstall goes looking for stuff that the kernel has > found. The only way it can do this is by trying to open everything > that might exist and remembering which ones work. It's a pathetic > "poor brother" to DEVFS. indeed ... > Is the drive itself locking up? Are you certain that the system is > locked? Have you tried putting a disk in the Zip? It's possible that > the Zip is just timing out very slowly. > > Well, start pulling disks until it works. I'd start with the Zip drive; > > sysinstall does NOT like them. > > Sysinstall doesn't care one way or the other. The ATAPI code in the > FreeBSD kernel is a little grubby, and the ATAPI Zip shows up a few > problems with it. SCSI Zip drives work just fine. Well, then, I guess we know where to start. :-/ I know that the 'pull the Zip' advice has helped many people, so there is certainly a problem there. Why isn't wfd0 in the boot floppy kernel? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980505205605.9802J-100000>