From owner-freebsd-bugs Wed Aug 9 12:07:39 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id MAA24160 for bugs-outgoing; Wed, 9 Aug 1995 12:07:39 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id MAA24154 for ; Wed, 9 Aug 1995 12:07:37 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id NAA24064; Wed, 9 Aug 1995 13:09:41 -0600 Date: Wed, 9 Aug 1995 13:09:41 -0600 Message-Id: <199508091909.NAA24064@rocky.sri.MT.net> To: bugs@FreeBSD.org CC: micke@dynas.se Subject: Re: FreeBSD Sony CD-ROM driver buggy In-Reply-To: <199508091830.MAA25456@trout.sri.MT.net> References: <199508091830.MAA25456@trout.sri.MT.net> Reply-To: nate@trout.sri.MT.net (Nate Williams) From: nate@rocky.sri.MT.net (Nate Williams) Sender: bugs-owner@FreeBSD.org Precedence: bulk Nate Williams writes: > I'm attempting to install FreeBSD onto a 486/66 box using the 2.0.5 CD. > Thanks to to the 'emergency holographic shell' on vty4, I was able to > track down the problem to corruption of data coming off the CD. I'm able > to partition and lable the disk successfully, but when 'sysinstall' attempts > to unpack '/cdrom/floppies/root.flp' it dies with an error. > > Thanks to the 'emergency holographic shell' on vty4, I am able to > determine that the data coming from the CD is bogus, though the lack of > tools at this point makes it extremely difficult to determine how far > into the file the corruption occurs. More information. I substituted the Live FS CD for the intall CD to see if I could use the binaries on it to help track down the problem. However, I get 'Memory Fault' or 'Bus Error' whenever I attempt to run any of the binaries, so I think it must be a driver bug of some sort. Also, none of the directories below /cdrom/usr even show up, so there is yet another problem. The CD is a Sony CDU-33A 'Sun Moon Star' I picked up at WalMart. (Hey, this is Montana, WalMart is the *only* store who carries CD-ROMs in stock). I had to configure the kernel to look at port 0x340 instead of the default at 0x230. My CD can't even go there, so I jumpered up much higher. I'm going to try re-jumpering it higher again, but I'm don't feel that it will help. Nate