Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!news.mathworks.com!fu-berlin.de!news.belwue.de!news.uni-stuttgart.de!uniol!uni-erlangen.de!news.tu-chemnitz.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Initial Installation Problem Date: 22 Jun 1996 10:41:38 GMT Organization: Private BSD site, Dresden Lines: 35 Message-ID: <4qgil2$q31@uriah.heep.sax.de> References: <4phj3o$4ir@news.onramp.net> <31BE36B8.31DFF4F5@freebsd.org> <4q3qfa$i9k@news.onramp.net> <4q4nqm$5p8@news.onramp.net> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E rubin@sequel.com (Robert J. Rubin) wrote: > Kernel boots...swapon...fsck's filesystems...hangs. > > This just ain't gonna work in this box. I'd think it's plain vanilla: > 486/66, 16M RAM (AMI BIOS...btw....at what point does > FreeBSD stop using the BIOS?) Once the kernel is loaded. The bootstrap toggles between real mode (for using the BIOS -- disk reads, terminal IO) and protected mode (for accessing all the memory > 1 MB), and finally goes back into protected mode and jumps to the kernel entry point. Some valuable information as obtained from the BIOS has been dumped on the kernel stack before (so the kernel is called with a pointer to a structure as an argument), but once the kernel is running the (16 bit) BIOS is not used anymore. What makes me wonder is that your /etc/rc does check the file systems without problems. Can you boot the machine single-user (-s at the boot prompt)? Can you try to isolate which of the parts of /etc/rc might be the offender? In order to continue after booting single-user, run ``fsck -p'' manually, then ``mount -u -t ufs'', to get your disks read/write. At this point, you're able to use vi to edit the /etc/rc script. Btw., pressing ^T while /etc/rc is running should get you a one-line status summary. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)