When attempting to install FreeBSD 3.0-19980504-SNAP the installation locks up with the following error obtained by doing an ALT-F2 on the console. DEBUG: ioctl (3, TIOCCONS, NULL) = 0 (success) DEGUG: Found a network device named de0 DEBUG: Found a network device named lp0 cd0: NOT READY asc 3a:0 Medium not present ncr0:0 Error (0:41) (9-a9-0) (10/9d) @ (scripth 54c:19000000) ncr0: script cmd = 88080000 ncr0: regdump ca 10 80 9d 47 10 00 07 03 0a 80 a9 80 01 19 00. ncr0: have to clear fifos. ncr0: restart (fatal error). ncr0: timeout ccb = 107a1a00 (skip). Then the hard drive light says solid and the installation proceeds no further. How-To-Repeat: Install FreeBSD 3.0-SNAP on a machine with a Tekram DC-390F with a Fujitsu MAB3045SP UW SCSI HD. The problem did not occur until until I removed the previous hard drive and replaced it with the Fujitsu drive and attempted to install FreeBSD on it. The problem occurs consistantly with the current version of SNAP and the 3.0-980520-SNAP release.
Does this problem still exist in recent releases? (The new Tekram camified amd(4) ?)
The Tekram DC-390F is not an AMD based SCSI adapter, it's an LSI Logic 53C875 based adapter which uses the ncr driver. The problem only manifested itself with the Fujitsu drive at the time the bug report was submitted. It wouldn't even make it to the sysinstall menu. It would hang on the device probe with the error described. It does not manifest itself with the latest release. ALT-F2 shows that it finds the two MS-DOS partitions on the Fujitsu drive. It makes it to the sysinstall menu. Based on this behavior, I believe it's safe to close this bug report as being corrected in a later release.
Thus spake John C. Archambeau (nxiv@my-deja.com): > The Tekram DC-390F is not an AMD based SCSI adapter, it's an LSI Logic > 53C875 based adapter which uses the ncr driver. Yes, you're right, of course. I didn't notice the "F" :). > Based on this behavior, I believe it's safe to close this bug report as > being corrected in a later release. OK, thank you. Can someone close it, please? Alex -- I doubt, therefore I might be.
State Changed From-To: open->closed Submitter says the bug is fixed.