> This is the stack trace of the interrupt thread for the keyboard handler. > What you want to do is type in "trace 1" to see what init is doing. Also, > the output of the ddb ps command would be useful. Oops. I wanted to get a "trace 1", but after touching not even a single bit of the configuration, it boots just fine today. The only thing I did was boot the laptop into Windows XP yesterday (XP and RedHat share the laptops disk), but did not touch the FreeBSD config. I have no idea what is going on here. > > The kernel is GENERIC with options BOOTP, BOOTP_NFSROOT and BOOTP_COMPAT > > added. > > I can do PXE using GENERIC without any special options -- do you need the > options? Just tried PXE booting GENERIC, it fails like this: ... Mounting root from nfs: NFS ROOT: 192.168.176.1:/ exec /sbin/init: error 70 exec /sbin/oinit: error 70 exec /sbin/init.bak: error 70 exec /stand/sysinstall: error 70 init: not found in path /sbin/init:/sbin/oinit:/sbin/init.bak:/stand/sysinstall panic: no init and then drops me into DDB. When I compile the kernel with the BOOTP options, it requests the parameters from the DHCP server once again before trying to run init: Sending DHCP Discover packet from interface fwe0 (02:02:3f:ff:99:cc) Sending DHCP Discover packet from interface fxp0 (00:02:3f:36:ef:8b) Received DHCP Offer packet on fxp0 from 192.168.176.1 (accepted) (no root path) Sending DHCP Request packet from interface fxp0 (00:02:3f:36:ef:8b) Received DHCP Ack packet on fxp0 from 192.168.176.1 (accepted) (got root path) DHCP timeout for interface fwe0 fxp0 at 192.168.176.10 server 192.168.176.1 server name DHCPserver boot file pxeboot subnet mask 255.255.255.0 router 192.168.176.1 rootfs 192.168.176.1:/ hostname test.home.inlimbo.org Shutdown interface fwe0 Adjusted interface fxp0 Mounting root from nfs: NFS ROOT: 192.168.176.1:/ and here is start to boot: Interface fxp0 IP-Address 192.168.176.10 Broadcast 192.168.176.255 mount_nfs: can't update /var/db/mounttab for 192.168.176.1:/etc Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point. ... Not sure why you are able to boot a stock GENERIC, can you send me a description of your setup (DHCP server configuration, boot server configuration)? I'm sure it's pilot error on my side, I'm not really sure where the wings are on this plane :-)Received on Fri May 02 2003 - 22:13:09 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:06 UTC