Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!gatech!news.byu.edu!cwis.isu.edu!fcom.cc.utah.edu!civil.utah.edu!match From: match@civil.utah.edu (Marvin Match) Subject: install problems (desparate) Message-ID: <match.17.735012627@civil.utah.edu> Sender: news@fcom.cc.utah.edu Organization: University of Utah Date: Sat, 17 Apr 1993 02:10:27 GMT Lines: 59 Help! OK. I thought I would be real cool and build a 486dx-50 to run 386bsd on, but for the life of me, I can't get it to run. Here's what's left of the hardware: 486dx-50 isa motherboard with "unichip" chipset. AMI bios OAK SVGA card, 512k, running in plain-Jane vga mode Adaptec 1542b SCSI controller Seagate ST1480 410MB hard drive 1.2M 5.25 floppy (drive a:) 1.44M 3.5 floppy (drive b:) 16 MB ram I pulled the bussmouse, soundblaster, serial/par. card, NE2000 clone, modem, and 16MB of ram. I originally built this machine with a Future Domain card, of course I found that there is no driver for the Future Domain card, and I got tired of waiting for one of you very clever fellows to write one. (Julian had a driver 80% finished for a long time). The Adaptec came available so I bought it. The box runs DOS just fine, after I slowed the buss down to 8MHz for one of the cards that I've since removed. I partitioned 110 MB for dos, leaving 300 for 386bsd. (Tried dos 5 and dos 6 BTW) Last time I had a chance to play with this installation Nate pointed me to some new boot floppies. I currently have the original 0.1 dist.fs, one labeled new dist.fs, one labeled dist.fs.pk0.2, and their fixit's. dist.fs and dist.fs.pk0.2 will boot once in a while. usually they just spin up, and I get a cursor. Nothing more. new dist.fs boots (says it's version 0.1.44 I think, or is it 0.1.24) and I can run install. Upon completion, the machine says to remove the floppy, and hit return to boot off the hard drive. When I do that, I get endless messages scrolling off of the screen, the likes of "386 bsd not installed" or "can't find 386bsd. trying vmunix" or some such. (hard to tell, it all goes by so fast) I've turned everything I can off (cache, shadowing, etc) to no avail. What now? It's possible that 386bsd simply won't run on this motherboard. But from reading other postings, seems to me alot of people are having problems with boot/install. Where do I begin? I need someone to hold my hand awhile while we determine if I need to peddle this motherboard to some DOS user, or we identify the snag. I probably haven't given you enough information, so ask me questions. (gotta start somewhere) And of course I'm a real newby. Please, please, please respond. Thanx, Marvin Match match@sky.civil.utah.edu