Date: Wed, 24 Sep 2003 02:26:51 -0700 From: "Aaron Burke" <aburke@nullplusone.com> To: "Tim Hawes" <thawes@althusius.net>, <freebsd-config@freebsd.org> Subject: RE: Install Trouble Message-ID: <AMEMKJNMFLJCJDLFIEDBCEPCEGAA.aburke@nullplusone.com> In-Reply-To: <3F70BA35.5090002@althusius.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Subject: Install Trouble > > > I am a newbie in the FreeBSD world, but an old hat for Solaris and > Linux. I have an Intel box with Windows 2000 and Linux already on it. I > shrunk my Windows partition to allocate about 16 GB for a new FreeBSD > install. I have installed FreeBSD on VMware several times in the past, > so this is my first non-virtual install. > > The install completely halts shortly after it shows the "Probing > hardware (this may take a while...)" message. I look at vt1 to see what > debugging messages are there. I notice that it stops right after finding > the /dev/cua devices (serial devices???). Yes, cuaa0 is linked to the serial port code. Allthough I am not 100% sure about this, FreeBSD detects the device, then tells you about it. So that was probably telling you that the last device that it properly loaded was the serial ports. Have you booted with "boot -c -v", then typed visual? You should see a message that says "Hit [Enter] to boot immediatly, or any other key for a command prompt.". Then type "boot -c -v" (config, and verbose). Then a prompt labeled "config> " will appear. Type visual and try disabling any hardware that you dont have. Allthough the GENERIC kernel will usually fail to detect these devices (because they dont exist), its still worth disabling them. > > The console is not locked, I can switch back and forth from vt0 and vt1 > without trouble. It is just stopped. Thats actually a good thing. Its kind of nice when a the system is still at least partially running! > > It did this to me with both FreeBSD versions 4.8 and 5.1 That helps rule out some of the big differences between the two different branches of the FreeBSD source. > > This is a Walmart Os-less PC I bought just over a year ago. I am no > hardware guru, and I am not sure what info is pertinent, so tell me what > I need to tell you to help me. Well, that pretty much rules out SCSI, you may try disabling the scsi devices. The only things that you should need are as follows: Storage : ATA/ATAPI compatable disk controller ata0 14 0x1f0 ATA/ATAPI compatable disk controller ata0 15 0x170 Network : Only enable your network card. Communications : You are likely to have at least one serial port, but disable it for now. You can enable it later if you need it. The same goes for your parallel port. Input : Keyboard atkbd0 1 Syscons console driver sc0 Miscellaneous : Math coprocessor npx0 Most people recompile the kernel when they have the box up and running. Feel free to talk to freebsd-questions about this topic. We will be happy to forward you some links to some sites that give an overview of the process. > > Best regards, > > Tim Hawes Be sure to let us know if you have any luck. There are several people on this list that will have more advice to offer. But I would start by making sure your not going to attempt to load drivers for hardware that you dont have. Aaron Burke aburke@nullplusone.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AMEMKJNMFLJCJDLFIEDBCEPCEGAA.aburke>