Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!agate!dog.ee.lbl.gov!hellgate.utah.edu!fcom.cc.utah.edu!gateway.univel.com!gateway.novell.com!thisbe!terry From: terry@thisbe.npd.Novell.COM (Terry Lambert) Newsgroups: comp.unix.bsd Subject: Re: More booting problems... (Bus mouse?) Message-ID: <1992Jul20.172313.13821@gateway.novell.com> Date: 20 Jul 92 17:23:13 GMT Article-I.D.: gateway.1992Jul20.172313.13821 References: <1992Jul20.084809.28082@cl.cam.ac.uk> Sender: terry@thisbe (Terry Lambert) Organization: Novell NPD -- Sandy, UT Lines: 89 Nntp-Posting-Host: thisbe.eng.sandy.novell.com In article <1992Jul20.084809.28082@cl.cam.ac.uk>, qs101@cl.cam.ac.uk (Quentin Stafford-Fraser) writes: |> Sorry, everyone, but I too have totally failed to get Tiny 0.1 to boot. |> |> I get the banner message with a line just before it saying |> something about too little RAM memory (I have 4 meg), and then the |> screen blanks before I can read it properly and is replaced with |> lots of flashing multi-coloured characters, and then the prompt |> |> ptdi 81061 |> > |> |> appears. Any key I press from here gives: |> |> trap type 12 code=fec00000 eip=fe04fdf0 cs=fdbf0008 eflags=10246 cr2 0 |> cpl ffffffff |> panic: trap |> hit reset please |> |> Please can anybody help? I have tried unplugging all the cards except |> the parallel/serial/HD card which also controls the floppies, and I've |> tried telling the CMOS that I have no hard disks. My system is |> |> HP QS/16 Vectra (16Mhz SX) |> 4 Meg RAM |> AT-style hard disk Were you able to boot 0.0 on this box? I have had *exactly* the same problem (I was unable to get 0.0 to run on the box either, hence the question). There was an initial keyboard reset timing latency that was a problem. I fixed this in the first place by removing the reset, but later put a small buzz-loop as a patch in the boot code, due to the fact that using X dorks up the keyboard so that a warm boot kernel can't find it correctly. I had this problem on 6 different 386 boxes. 4 of them still would not boot 0.0 (All AT&T boxes); two of them finally cooperated, but only with the 387-less code (even though one had a 387). The message following "Too little RAM memory" (I have 48 Meg on one box) was "(continuing? running?) in degraded mode". The rest is the standard copyright stuff. I suspect that, like my 4 flavors of AT&T boxes, your HP vectra has a built in bus mouse. This was the only thing I couldn't unplug and swap, given the fact that it's built onto the motherboard and has no cut-off. This seems to be the problem with a number of Compaq boxes at work, as well. Not suprisingly, 386BSD seems to hate single sigma chips; this means I'm back to exactly one box that will run 386BSD. Is there a particular reason 386BSD hates bus-mice? I would *really* like to run 386BSD on something with a decent clock rate. Where 386BSD won't run: Everex 386 Step/16 ATI Motherboard (with single sigma chip) AT&T 6386 WGS (with bus mouse on Intel motherboard) AT&T 6386/E WGS (with bus mouse on Intel motherboard) AT&T Starserver E (486 EISA with bus mouse on motherboard) AT&T 386/SX -- forget the actual model # (with bus mouse on motherboard) IBM PS/2-80 (386, with bus mouse and microchannel -- expected this to fail) Compaq (some deskpro -- supposed to be good for you) Where 386BSD will run: AST 386/16 Since there is 1 AST 386, several Compaq's, 1 PS/2, 6 ATI's, and nearly 70 AT&T boxes for the internals classes, my preference is obvious :-). So: *Anybody* have an idea why the extended Intel 386 motherboard with bus mouse would puke out 386BSD, when the previous release of the board was different only in the fact that it had 1 less memory board slot and 1 less 16 bit slot and no bus mouse? As I said, I suspect the bus mouse, considering the previous release of the Intel motherboard worked fine (but, alas, died a grim death recently!). 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.