Date: Wed, 9 Aug 1995 12:30:53 -0600 From: Nate Williams <nate@trout.sri.MT.net> To: bugs@FreeBSD.org Cc: micke@dynas.se Subject: FreeBSD Sony CD-ROM driver buggy Message-ID: <199508091830.MAA25456@trout.sri.MT.net>
next in thread | raw e-mail | index | archive | help
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. The CD and drive are fine (obviously) since I can read the data from the DOS partition on the same box, copy it to a floppy and read it on another FreeBSD box and the data is fine. Also, FreeBSD correctly recognizes and mounts the drive, and the directory structure looks fine, but when I read from it quickly the data gets corrupted. *Feature plea on* I'd like to track this down, but I don't have the disk space to create a 'fs-image' of a 2.0.5 install disk, and w/out that I can't even install the darn thing. We *really* need to provide a way for folks to build their own custom 'boot.flp' kernels, since I can't even debug the problem with a running system on the machine, and w/out the ability to build custom debuggable kernels I can't even track down the problem. I *could* build a custom kernel, but I can't even install it on my hard-drive with the current install tools. This is *not* to knock the installation tools, but a plea to make it easier for folks to build custom 'boot.flp'. IMHO, this requires access to the 'fs-image' file created during the install processes, which is the MFS image inside of the kernel. This file takes a large amount of space to build because of the current ordering of the intall tools, and most folks don't have access to that much space. All of the other tools are easily buildable or already exists in the default distribution. With an 'fs-image', all a person needs to do is create a custom kernel with the addition of a couple extra lines for the MFS stuff (I could grab it if needed), build /usr/src/release/write_mfs_in_image, and all is set. I don't suppose there ia a chance of a 2.0.5 fs-image file lying around, is there? *Feature plea off* In any case, if there is anything I can do to help debug the problem, let me know. I'm going to try and get a kernel on this thing to see if I can track down the problem myself. Also, having a fixit.flp would be really helpful, but building one of those also requires more disk space than I have available as well. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199508091830.MAA25456>