Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 8 Feb 2006 09:53:58 -0500 (EST)
From:      "Andrew Bogecho" <andrewb@cs.mcgill.ca>
To:        freebsd-questions@freebsd.org
Cc:        Christopher Cowart <ccowart@rescomp.berkeley.edu>
Subject:   Re: pxeboot fails to load acpi.ko
Message-ID:  <4463.132.206.55.240.1139410438.squirrel@mail.cs.mcgill.ca>
In-Reply-To: <20060207215025.GA5318@rescomp.berkeley.edu>
References:  <20060207215025.GA5318@rescomp.berkeley.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

Have you had a look in /boot/device.hints?

hint.acpi.0.disabled="1"

I at the moment maintain 2 diskless images, the one for older hardware has
the above setting to disable acpi(machine would hang with it enabled). I
believe setting it to "0" or commenting it out could help you.

A.

> Hey-
>
>
> I've been working on a project to automate FreeBSD installations over
> the network, using PXE boot capabilities. I've been following the howtos,
> as documented starting here:
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/index.html
> and http://www.daemonsecurity.com/pxe/jumpstart.html
>
>
> I'm having a difficult time finding posts from other people who have
> experienced similar problems.
>
> Everything is setup. I'm using a tftpd that can handle large files.
> DHCPD is configured correctly. The client boots the PXE boot loader, as
> it should. It then begins loading the kernel. Upon loading the file
> acpi.ko, the boot hangs.
>
> Doing a tcpdump on the traffic, it looks like the machine receives the
> last packet of acpi.ko, and before it even has a chance to send an ACK,
> it's done. The twirly status bar stops spinning. The machine is doomed for
> a hard reboot.
>
> I've tried with two very different boxes to ensure it's not a hardware
> anomoly. The machines boot fine from the installation CDs -- loading
> acpi.ko. Further, I started with 5.3-REL, stepped up to 5.4-REL, and
> lastly, 6.0-REL. The problem occurs with all these versions.
>
> I'm not sure how to continue debugging this problem. Any tips in terms
> of troubleshooting or known workarounds would be great.
>
>
> Thanks,
> Chris
>
>
>
> --
> Christopher Cowart
> Unix Systems Administrator
> Residential Computing, UC Berkeley
> "May all your pushes be popped"
>
>





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4463.132.206.55.240.1139410438.squirrel>