Date: Fri, 14 Apr 1995 18:07:51 -0400 (EDT) From: Marc Ramirez <mrami@mramirez.sy.yale.edu> To: hackers@FreeBSD.org Subject: aha driver no lonker kosher wrt. my 1542A rev D Message-ID: <Pine.BSI.3.91.950414173338.130B-100000@mramirez.sy.yale.edu>
next in thread | raw e-mail | index | archive | help
2.0-950412-SNAP: Problem: The kernel can read from my disks just fine, but writes get corrupted. Hardware: ??? 486DX/33 SiS Chipset, 20MB ram Cardex Cobra ET4000/W32i video Adaptec 1542A rev D - Conner CFA540S - target 0 Maxtor 7120SCS - target 1 SMC Elite16 (I think; it's ed1, anyway) ??? floppy controller 2 drive, Colorado Jumbo 250 2 serial, parallel Story: 1) Downloaded boot floppies and bindist. 2) Install on drive 0; Reboot from sd0 and kernel panics right after stating memory size. Reboot a couple of times; always get the same panic. 3) Reinstall on drive 0; get a different panic. Subsequent reboot cause the new and improved panic. 4) Install 2.0R (keeping SNAP bootblocks) and then install the SNAP bindist (which is on sd1). ON reboot, the kernel boots fine, /etc/rc runs, I get a login prompt. 5) Run do_cksum.sh on SNAP bindist on sd1. It runs with no errors. 6) Copy bindist from sd1 to sd0 and run do_cksum.sh on sd0 (copy) bindist. Half the files are corrupt. Re-run do_cksum.sh on the sd1 (original) bindist. All is well. 7) Reinstall 2.0R Maybe bounce buffers are not working properly? But then reads would also be corrupted, right? I am at a loss. I tried the 950322-SNAP just for kicks, and it has the same problem. I saw someone else post a similar problem on this list a couple of days ago. Marc. -- You couldn't get a clue during the clue mating season in a field full of horny clues if you smeared your body with clue musk and did the clue mating dance. - Edward Flaherty
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.91.950414173338.130B-100000>