Date: Wed, 1 May 1996 19:50:34 +0200 From: se@zpr.uni-koeln.de (Stefan Esser) To: Andrew Suessmuth <aks@interlog.com> Cc: scsi@freebsd.org Subject: Re: ASUS SP3G NCR problem Message-ID: <199605011750.AA12965@Sisyphos> In-Reply-To: Andrew Suessmuth <aks@interlog.com> "ASUS SP3G NCR problem" (May 1, 10:52)
next in thread | previous in thread | raw e-mail | index | archive | help
On May 1, 10:52, Andrew Suessmuth wrote: } Subject: ASUS SP3G NCR problem } Umm.... HELP! :-) } } I've just spent a futile night scouring the freebsd archives, looking = } for answers to my SCSI boot problems, and couldn't find an answer (that = } worked anyways. :-) ) } } I have a rev 1.8 PCI/I-SP3G ASUS motherboard with a rev 4 Saturn chip in = } it and a rev 2 NCR 53c810 chip. Fine. The development system for the NCR driver, BTW. } I'm trying to boot using the 2.1.0 boot = } floppy image. The devices on the SCSI chain are: Toshiba MK538FB hard = } drive, Hitachi DK516C hard drive, ARCHIVE Python DAT, and a Sony = } CDU-76S. All the PCI related BIOS settings are set to the BIOS = } defaults. The Toshiba has caused problems before, the other devices look fine. I'm not sure whether the Sony CDROM can be used with synch. transfers, though. } When FreeBSD reaches the point where it polls the NCR SCSI bus, it = } starts scrolling a bunch error messages. I haven't recorded all the = } messages it scrolls up the screen, but after correctly identifying the = } device (it prints the right name on screen) it receives an M_REJECT and = } a timeout for each device. One line in the middle of the scroll that = There is a M_REJECT for **each** device ? Please check again. I'd expect a single device to cause all these error messages. There is the SCSI ID in the error messages: % (ncr0:2:0): "TOSHIBA MK537FB 6257" is a type 0 fixed SCSI % sd0(ncr0:2:0): Direct-Access % sd0(ncr0:2:0): asynchronous % sd0(ncr0:2:0): M_REJECT received (2:8) (This is from an earlier problem report, which also was caused by some problem with synch. transfer negotiation between the NCR driver and the Toshiba drive.) } caught my eye might be helpful in IDing the problem: } } DEBUG: ioctl(3, TIOCCONS, NULL) =3D 0 (success) This seems unrelated. } Another cute effect occurs when I exit the install program, causing a = } reboot, my system reports a CMOS checksum error, and gets reset to the = } default BIOS settings. This should not happen, and I never heard about this before ... } I appologize in advance if this isn't the correct list to post this = } question in (it seemed most fitting to me). It definitely is the correct list, at least as far as the NCR+Toshiba problem is concerned. Could you please try the boot floppy from the latest SNAP release ? If you can disconnect the Toshiba for the time of the installation, you may be able to boot the 2.1.0 floppy and install to the other disk drive. Once the system is up, you can rebuild the kernel, and you could use the Toshiba with asynch. transfers, at least. I could then send patches for you to try, and to get the synch. transfer negotiation going ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605011750.AA12965>