Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mips!mips!newsun!gateway.novell.com!terry From: terry@npd.Novell.COM (Terry Lambert) Subject: Re: Keyboard Message-ID: <1992Jul20.155018.5747@gateway.novell.com> Sender: news@gateway.novell.com (NetNews) Nntp-Posting-Host: thisbe.eng.sandy.novell.com Organization: Novell NPD -- Sandy, UT References: <IeO2l3y00WB3Eu60oZ@andrew.cmu.edu> Date: Mon, 20 Jul 1992 15:50:18 GMT In article <IeO2l3y00WB3Eu60oZ@andrew.cmu.edu> Tao Jiang <tj2n+@andrew.cmu.edu> writes: > >I just installed 386bsd0.1 yesterday. This morning, when I tried to >reboot the system, everything is OK, but after that,( after the prompt login appeared), I can not enter anything from keyboard. Then I tried to reboot, >things were the same till the 5th reboot. Is this a bug or I have done >something wrong when I installed 386bsd? Any clues? This is a bug. SCO had a similar bug, which had to do with 10 bit I/O path on single sigma 386's. Make sure yours is a double sigma. SCO also had another problem similar to this when they were booted on a 386 with a 387 present. On my Intel 386/16 mother board, this was alleviated by 1) putting in a patch that delayed the video reset after the initial boot message prior to takeover by the SCO console driver 2) removing the 387 (probably not an option here), and 3) Jumpering the memory bus for an additional wait state to cause the boot to proceed more slowly (with the wonderful side effect of everything else proceeding slowly from that point on). Jumpering the machine to a slower clock rate *did not help*! This is because the video reset was the result of execution of code from the card ROMs by the main processor, which means that the reset was also slowed by a reduced clock. I had the 8th Intel 386/16 motherboard manufactured. SCO said that the problem was a result of the old board. Intel said it was the result of the board being used out of spec, and that there was a reset signal that the boot code should have been waiting for... naturally, they recommended Intel UNIX as a soloution. 8-) 8-). Regards, Terry Lambert terry_lambert@gateway.novell.com terry@icarus.weber.edu --- Disclaimer: Any opinions in this posting are my own and not those of my present or previous employers.