On Sun, Dec 14, 2003 at 12:57:34PM -0800, Thor Anderson wrote:
> FreeBSD hangs without errors early in the install process on my computer.
> 
> I have downloaded and tested the CD ISO files for version 4.9 as well as 
> 4.6.2 (with intent of upgrading) and neither appears to boot.  In both 
> cases, my computer completes POST, accesses the CD drive and hangs without 
> any messages.
> 
> Worried that my ability to create a bootable CD-ROM, I purchased the 
> commercial boxed set of 5.1 (?Power Pac? with handbook).  While this 
> version still does not install properly, it does provide the following 
> message before it hangs:
> 
> >CD Loader 1.01
> >
> >Building the boot loader arguments
> >Looking up /BOOT/LOADER... Found
> 
> Having eliminated my options for CD install, I purchased a USB floppy drive 
> and attempted a floppy boot disk.  Again, the system hung without any 
> message.
> 
> The computer is able to boot other operating systems from CD.  Testing 
> shows Microsoft as well as Fedora project Linux boot and install properly.
> 
> The computer is an IBM NetVista 6645 W2U with an Intel Celeron 566MHz 
> processor, 128MB RAM, a 7.5GB hard disk, a 32x CDROM, and an Intel Express 
> Pro 10/100 PCI network adaptor.  What makes this system unusual is that it 
> is ?legacy free? which means it has none of the traditional I/O ports (no 
> serial, parallel, PS/2 or even floppy interface).  All I/O is via one of 
> the five USB ports on the case.  I have flashed the BIOS to the latest 
> version.
> 
> Since I can not install, I have no operating FreeBSD systems at my 
> disposal. Therefore, I can not customize my own kernel.

A friend of mine recently ran into this problem on an embeded system.
The solution for him on 5.x was to enter the following at the loader
prompt to disable the keyboard and floppy probes because they tend to
hang:

hint.atkbdc.0.disabled=1
hint.atkbd.0.disabled=1
hint.fdc.0.disabled=1

Unfortnaly, you can't do that since you don't have a serial port.  The
one hack I can think of would be to try to PXE boot the CD image from
another machine.  You could then modify the loader.conf on the pxe image
to force these settings.

These drivers are broken and need to be fixed since I'm sure this
problem will only become more common.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to