Re: boot/pxeboot broken in freebsd-12?
Thanks Warner... On Tue, Mar 19, 2019 at 05:14:15PM -0600, Warner Losh wrote: > You need to set the NFS mount point properly. I think I have? The 12.0 environment was basically a copy of a functioning 11.0 PXE environment, and 12 worked fine with 11's pxeboot. Regardless, turns out neither 12 nor 13 will boot on my hardware under UEFI, so PXE woes are less of a concern now. I'm running J1900s; they seem to have a history. -Snow ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: boot/pxeboot broken in freebsd-12?
On Tue, Mar 19, 2019 at 4:53 PM James Snow wrote: > Hello -stable, > > We have a PXE environemt that builds FreeBSD-11 boxes. We've started > to dip our toes into the 12.x waters, but have had trouble getting > FreeBSD-12 to pxeboot. It would crash and burn like so: > > Startup error in /boot/lua/loader.lua: > LUA ERROR: cannot open /boot/lua/loader.lua: device not configured > > On a whim, I pulled the boot/pxeboot binary from our FreeBSD-11 > environment into the new FreeBSD-12 environment, and PXE clients started > coming right up. > > Is FreeBSD-12's pxeboot broken or have I missed something? > You need to set the NFS mount point properly. I've been able to boot the FreeBSD 12.0R installer with PXE (after fixing some issues downstream) and had that error before I had dnsmasq answering queries properly: dhcp-vendorclass=BIOS,PXEClient:Arch:0 dhcp-userclass=FreeBSD,FreeBSD dhcp-boot=net:BIOS,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-boot=net:BIOS,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=net:BIOS,option:root-path,10.0.0.5:/tftpboot/12.0R-i386-bootonly dhcp-host=mr_noodle,set:mr_noodle dhcp-boot=tag:mr_noodle,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=tag:mr_noodle,option:root-path,10.0.0.5: /tftpboot/12.0R-i386-bootonly dhcp-boot=tag:FreeBSD,12.0R-i386-bootonly/boot/pxeboot,10.0.0.5,10.0.0.5 dhcp-option=tag:FreeBSD,option:root-path,10.0.0.5: /tftpboot/12.0R-i386-bootonly is what I used in dnsmasq to get the job done. It was likely overkill (10.0.0.5 was the NFS, ftfpd and other servers for this exercise). I had to (a) create a blank /etc/fstab in the mdconfig mounted image and (b) create the proper /etc/resolv.conf in the F4 shell window just after I hit commit to make things work. And then configure the network by hand because the installer's config was wrong. So we've had some regression, just not the regression you are seeing. Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
boot/pxeboot broken in freebsd-12?
Hello -stable, We have a PXE environemt that builds FreeBSD-11 boxes. We've started to dip our toes into the 12.x waters, but have had trouble getting FreeBSD-12 to pxeboot. It would crash and burn like so: Startup error in /boot/lua/loader.lua: LUA ERROR: cannot open /boot/lua/loader.lua: device not configured On a whim, I pulled the boot/pxeboot binary from our FreeBSD-11 environment into the new FreeBSD-12 environment, and PXE clients started coming right up. Is FreeBSD-12's pxeboot broken or have I missed something? -Snow ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
pxeboot stuck
Hi, today’s latest 11.2 rev 341671, when booting off local disk all is fine, but pxeboot gets stuck after printing FreeBSD/x86 bootstrap loader. Revision 1.1 (Fri Dec 7 09:45:34 IST 2018 danny-pe-44) - older pxeboot get slightly further, but hang too. older root images work fine so what magic is now needed? thanks, danny ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: pxeboot with jumbo frame network
On Jul 23, 2012, at 1:58 PM, Bob Healey wrote: I know I have this working, however I don't remember what I did. I know I can pxeboot and install RHEL on a 9K frame network from a FreeBSD tftp server/NAT gateway. I do know the first thing in my RHEL install script is to set the MTU to 9K. If I have a chance later today, I'll dig into one of my install servers and try to figure out what options I used with DHCP to get it working. The trick is setting the boot time options on the client. The server side (TFTP server) is the easy part as it's already setup and running. But if the client boots and it's not jumbo frame enabled, TFTP will surely hang on getting the PXEboot as the server will be trying to send 9K UDP frames to a client that's probably defaulted to 1500. If there is a DHCP option to set the client MTU, I've not found it anywhere. -- Robert Blayzor INOC, LLC rblay...@inoc.net http://www.inoc.net/~rblayzor/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pxeboot with jumbo frame network
On 7/24/12 6:07 AM, Robert Blayzor wrote: On Jul 23, 2012, at 1:58 PM, Bob Healey wrote: I know I have this working, however I don't remember what I did. I know I can pxeboot and install RHEL on a 9K frame network from a FreeBSD tftp server/NAT gateway. I do know the first thing in my RHEL install script is to set the MTU to 9K. If I have a chance later today, I'll dig into one of my install servers and try to figure out what options I used with DHCP to get it working. The trick is setting the boot time options on the client. The server side (TFTP server) is the easy part as it's already setup and running. But if the client boots and it's not jumbo frame enabled, TFTP will surely hang on getting the PXEboot as the server will be trying to send 9K UDP frames to a client that's probably defaulted to 1500. If there is a DHCP option to set the client MTU, I've not found it anywhere. If it's isc-dhcpd, option interface-mtu works. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
pxeboot with jumbo frame network
Is it possible to PXEboot a diskless client with an MTU higher than 1500 (Ie: 9k) ? The network we currently boot several diskless machines from has a lot of NFS traffic and we'd like to enable them all for larger MTU's however the one thing stopping us is the issue with initial boot seemingly only supporting an MTU of 1500. I know we can set the MTU later (post boot) on the diskless machines, but it doesn't seem we can run a higher MTU on the TFTP server as we'd have TFTP UDP traffic with mis-matched frame sizes at that point. -- Robert Blayzor INOC, LLC rblay...@inoc.net http://www.inoc.net/~rblayzor/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: pxeboot with jumbo frame network
I know I have this working, however I don't remember what I did. I know I can pxeboot and install RHEL on a 9K frame network from a FreeBSD tftp server/NAT gateway. I do know the first thing in my RHEL install script is to set the MTU to 9K. If I have a chance later today, I'll dig into one of my install servers and try to figure out what options I used with DHCP to get it working. Sorry I can't be of more help than to say its possible. Bob Healey Systems Administrator Biocomputation and Bioinformatics Constellation and Molecularium hea...@rpi.edu (518) 276-4407 On 7/23/2012 1:31 PM, Robert Blayzor wrote: Is it possible to PXEboot a diskless client with an MTU higher than 1500 (Ie: 9k) ? The network we currently boot several diskless machines from has a lot of NFS traffic and we'd like to enable them all for larger MTU's however the one thing stopping us is the issue with initial boot seemingly only supporting an MTU of 1500. I know we can set the MTU later (post boot) on the diskless machines, but it doesn't seem we can run a higher MTU on the TFTP server as we'd have TFTP UDP traffic with mis-matched frame sizes at that point. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
btx/pxeboot problem
latest pxeboot (7.1): mother-boardNIC/LOM CPU - --- --- Intel SWV25 em xeonworks fine SUN X2200bgeamd works fine DELL PE 2950 bcexeonfailes 95% of the times hangs or goes into btx dump regs. mode :-) Intel SE7320VP21 mskxeonfailes 50% of the times - hangs pxeboot with btx.S 1.45 2008/02/27 23:35:39, works fine. so it seems that changes since 1.45 have fixed it for some, but it brakes for others :-). I can help testing, but btx is way out of my league. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: btx/pxeboot problem
On Tue, Dec 02, 2008 at 01:48:17PM +0200, Danny Braniss wrote: latest pxeboot (7.1): mother-boardNIC/LOM CPU - --- --- Intel SWV25 em xeonworks fine SUN X2200bgeamd works fine DELL PE 2950 bcexeonfailes 95% of the times hangs or goes into btx dump regs. mode :-) Intel SE7320VP21 mskxeonfailes 50% of the times - hangs pxeboot with btx.S 1.45 2008/02/27 23:35:39, works fine. so it seems that changes since 1.45 have fixed it for some, but it brakes for others :-). I can help testing, but btx is way out of my league. interesting, so this is the same problem i was seeing on the Asus/amd machines here... the commit log for 1.47 mention interrupt issues which are consistent with the random hangs or errors that I see while booting over the network. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/i386/btx/btx/btx.S.diff?r1=1.46;r2=1.47 I wonder if the hangs are related to interrupts coming in at the wrong time. I also wonder whether the same symptoms might also affect the standard loader and not just pxeloader, in which case the problem would be slightly more serious. I am afraid my ability to debug the problem isn't going much beyond this... cheers luigi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error while pxeboot setup FreeBSD 7.0
Hi, Hmm for what's worth: I just upgraded a 6.2 pxe box using cvs to 7.0 release and it boots and runs fine, it seems. The server (still) runs 6.2 . Cheers, Robert ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Error while pxeboot setup FreeBSD 7.0
I wander if pxeboot setup for FreeBSD 7.0 is different from pxeboot with 6.2?
I did sucessfully network pxeboot setup of Freebsd 6.2 using following
DHCP configuration, based mostly on this how to:
http://networking.ringofsaturn.com/Unix/pxeboot.php,
host host1
{
hardware ethernet 00:0c:29:1f:5e:3c;
fixed-address 192.168.0.114;
next-server 192.168.81.131;
filename /FreeBSD/boot/pxeboot; #
option root-path /usr/var/www/install/FreeBSD; # NFS path which
will be used as temp root partition.
}
where:
/usr/var/www/install/FreeBSD contains FreeBSD installation files,
Tftp root is set to / usr/var/www/install
With Freebsd 6.2 installation files, pxeboot executes and reads root
file system from network and loads kernel via NFS. An OS kernel
executes and starts installation process which can be finished
manually. If mfsroot contains proper install.cfg, then installation
can be completely unattended.
But with FreeBSD 7.0 installation files process fails somewhere after
pxeboot is started.
On Client screen it can be seen:
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x6fd45c ...
and after that, server reboots.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error while pxeboot setup FreeBSD 7.0
On Thu, Mar 27, 2008 at 12:44:25PM +0100, don Juan wrote: On Client screen it can be seen: Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x6fd45c ... and after that, server reboots. Please see this documentation, particularly step #10. http://jdc.parodius.com/freebsd/pxeboot_serial_install.html This should fix your problem. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Error while pxeboot setup FreeBSD 7.0
On Thu, Mar 27, 2008 at 05:17:23AM -0700, Jeremy Chadwick wrote: On Thu, Mar 27, 2008 at 12:44:25PM +0100, don Juan wrote: On Client screen it can be seen: Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x6fd45c ... and after that, server reboots. Please see this documentation, particularly step #10. ^^ Should have read Step #7 (Workaround for a bug in mfs_root). It's list item #10. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: possible bug in pxeboot with TFTP support
On Mon, Mar 26, 2007 at 03:16:15PM -0400, Ryan J. Taylor wrote: I compiled pxeboot with TFTP support by doing: cd /usr/src/sys/boot make -DLOADER_TFTP_SUPPORT I have clients booting via PXE and grabbing their root filesystem from a memory disk. However, there was a long delay in the boot sequence. tcpdump revealed that after downloading pxeboot, the client was sending RPC traffic, presumably looking for NFS. This caused the boot to stall for 30 seconds or so until the loader spit out NFS MOUNT RPC error: 60 and then continued booting via tftp. Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=91720 Regards, Brix -- Henrik Brix Andersen [EMAIL PROTECTED] pgpUeDGfq1ywv.pgp Description: PGP signature
possible bug in pxeboot with TFTP support
Hi all, I compiled pxeboot with TFTP support by doing: cd /usr/src/sys/boot make -DLOADER_TFTP_SUPPORT I have clients booting via PXE and grabbing their root filesystem from a memory disk. However, there was a long delay in the boot sequence. tcpdump revealed that after downloading pxeboot, the client was sending RPC traffic, presumably looking for NFS. This caused the boot to stall for 30 seconds or so until the loader spit out NFS MOUNT RPC error: 60 and then continued booting via tftp. I traced the error string back to /usr/src/sys/boot/i386/libi386/pxe.c and came up with a hack that skips the RPC probes and speeds the boot for me. pxe-server# diff -u sys/boot/i386/libi386/pxe.c.orig sys/boot/i386/libi386/pxe.c --- sys/boot/i386/libi386/pxe.c.origMon Mar 26 14:50:19 2007 +++ sys/boot/i386/libi386/pxe.c Mon Mar 26 14:46:02 2007 @@ -443,9 +443,10 @@ * ourselves. Use nfs_root_node.iodesc as flag indicating * previous NFS usage. */ - if (nfs_root_node.iodesc == NULL) - pxe_rpcmountcall(); - +/* XXX + * if (nfs_root_node.iodesc == NULL) + * pxe_rpcmountcall(); + */ fh = nfs_root_node.fh[0]; buf[0] = 'X'; cp = buf[1]; I'm wondering if someone with a clue can take a peek and confirm that things ought to behave differently. What I've stumbled across doesn't break PXE booting with a TFTP root filesystem, it just makes it much slower. Maybe I'm doing something wrong? Regards, RJ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless PXEboot crashes at kernel loading.
Hi all, I can't emphasise enough how useful running a TCPDUMP on the server in question is to find out what subtle thing it is that I missed. Generally speaking a quick-crash like that is a file not being found like the modules directory or something silly like that. If you dump the NFS traffic you will probably see the client asking for a file handle for file X and getting denied by the server. If you're not familiar w/ TCPDUMP, here are some handy commands: # Avoid SSH and dump everything to the screen... tcpdump -s 1500 -X udp # Write it to a file so you can open it in ethereal later... tcpdump -s 1500 -X -w nfs.dump udp # Read in the dump file and read it through less, should you not want to us # ethereal after the last step. :) tcpdump -X -r nfs.dump |less Note that if you have a slow or missing DNS entry, give these calls a -n to just get the data and not worry about the ND entries. Hope this helps! PXE boots are never kind. :) Sam Baskinger Software Engineer Lumeta - Securing the Network in the Face of Change Lumeta Corporation And the crash happens. Note that the crash occurs for whatever option 1 to 6 I choose from the FreeBSD boot menu. Does someone understand the crash messages? Not that I understand those messages but some time ago I've had a similar case. It took me some hours to realise that I try to load amd64 kernel to i386 diskless station... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Diskless PXEboot crashes at kernel loading.
On Thu, 15 Feb 2007 22:07:13 -0800 (PST) Rob wrote: I already described in detail what I've been doing with the FreeBSD server and the Compaq HP client PC here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-February/142116.html The Bootp exchange seems to be fine and the client gets the kernel from the server. However, during the kernel loading, the client PC implodes and starts from BIOS boot up again. The boot messages are given below. The crash messages scroll too fast over the screen to see the details with the bare eye. I recorded it with a digital camera and a snapshot of it is here: http://www.lahaye.dds.nl/pxeboot/crash.jpg The whole boot process in plain text goes as follows: -- Attempting Boot From Intel(R) Boot Agent Version 3.0.05 (PnP Device) Initializing Intel(R) Boot Agent Version 3.0.05 PXE 2.0 Build 078 (WfM 2.0), RPL V2.73 Intel(R) Boot Agent Version 3.0.05 Copyright (C) 1997-2000, Intel Corporation CLIENT MAC ADDR: 00 02 A5 93 F7 44 GUID: 67862AE2-117C-D511-BFE9-F3C48B4FB125 DHCP./ BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 PXE version 2.1, real mode entry point 09db8:8186 BIOS a573kB/268896kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 pxe_open: server addr: 192.168.123.1 pxe_open: server path: / pxe_open: gateway ip: 192.168.123.254 Welcome to FreeBSD! ;-) [ Boot option menu 1 to 7 ] FreeBSD-ascii-cartoon /boot/kernel/kernel text=0x4d568c / int=.. err= ef11= eip= -- And the crash happens. Note that the crash occurs for whatever option 1 to 6 I choose from the FreeBSD boot menu. Does someone understand the crash messages? Not that I understand those messages but some time ago I've had a similar case. It took me some hours to realise that I try to load amd64 kernel to i386 diskless station... WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Diskless PXEboot crashes at kernel loading.
Hi, I already described in detail what I've been doing with the FreeBSD server and the Compaq HP client PC here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-February/142116.html The Bootp exchange seems to be fine and the client gets the kernel from the server. However, during the kernel loading, the client PC implodes and starts from BIOS boot up again. The boot messages are given below. The crash messages scroll too fast over the screen to see the details with the bare eye. I recorded it with a digital camera and a snapshot of it is here: http://www.lahaye.dds.nl/pxeboot/crash.jpg The whole boot process in plain text goes as follows: -- Attempting Boot From Intel(R) Boot Agent Version 3.0.05 (PnP Device) Initializing Intel(R) Boot Agent Version 3.0.05 PXE 2.0 Build 078 (WfM 2.0), RPL V2.73 Intel(R) Boot Agent Version 3.0.05 Copyright (C) 1997-2000, Intel Corporation CLIENT MAC ADDR: 00 02 A5 93 F7 44 GUID: 67862AE2-117C-D511-BFE9-F3C48B4FB125 DHCP./ BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 PXE version 2.1, real mode entry point 09db8:8186 BIOS a573kB/268896kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 pxe_open: server addr: 192.168.123.1 pxe_open: server path: / pxe_open: gateway ip: 192.168.123.254 Welcome to FreeBSD! [ Boot option menu 1 to 7 ] FreeBSD-ascii-cartoon /boot/kernel/kernel text=0x4d568c / int=.. err= ef11= eip= -- And the crash happens. Note that the crash occurs for whatever option 1 to 6 I choose from the FreeBSD boot menu. Does someone understand the crash messages? Thanks, Rob. Looking for earth-friendly autos? Browse Top Cars by Green Rating at Yahoo! Autos' Green Center. http://autos.yahoo.com/green_center/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEboot fails at kernel (text) loading
On Sun, 11 Feb 2007 17:22:22 -0800 (PST) Rob wrote: I have a FreeBSD 6.1 PC as the server to a PXE boot of another Compaq Deskpro EN PC. The Compaq PC has the option of a Network Service Boot with the F12-key during BIOS boot up. On the server, tftpd, bootpd and dhcpd are all working well. For the diskless kernel config I have used the GENERIC one, but added: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT According to man diskless those options are not needed for PXE. Any idea what's wrong here or what I could do to further test what the actual problem is? You may consider re-reading man diskless -- all needed info is located there. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEboot fails at kernel (text) loading
Rob wrote: Is it OK to have a double kernel read at the last two lines? Any idea what's wrong here or what I could do to further test what the actual problem is? Argh. I had this same problem as recently as October, but I can't remember exactly what caused this. When I went back and re-did things according to 'man diskless' (and what Doug White told me in the first place), it all worked. Regards, BMS ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PXEboot fails at kernel (text) loading
Hi, I have a FreeBSD 6.1 PC as the server to a PXE boot of another Compaq Deskpro EN PC. The Compaq PC has the option of a Network Service Boot with the F12-key during BIOS boot up. On the server, tftpd, bootpd and dhcpd are all working well. For the diskless kernel config I have used the GENERIC one, but added: options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT When all this is in place, and I reboot the client PC, the PXE works fine and I get the Welcome to FreeBSD! window, that allows me to choose from a list of options: 1. Boot FreeBSD [default] 2. Boot FreeBSD with ACPI enabled 3. Boot FreeBSD in Safe Mode 4. Boot FreeBSD in single user mode 5. Boot FreeBSD with verbose logging 6. Escape to loader prompt 7. Reboot Now whatever option (1 to 5) I choose here, I always get: /boot/kernel/kernel text=0x4d568c / and the last slash is rotating for a very tiny while after which the system kind of implodes, blanks the screen and reboots from BIOS. Apparently something goes very, very wrong when loading the text part of the kernel. On the server, I've checked the /var/log/xferlog, which has entries like this: read request for //pxeboot: success read request for /boot/loader.rc: success read request for /boot/loader.4th: success read request for /boot/support.4th: success read request for /boot/beastie.4th: success read request for /boot/screen.4th: success read request for /boot/frames.4th: success read request for /boot/kernel/kernel: success read request for /boot/kernel/kernel: success Is it OK to have a double kernel read at the last two lines? Any idea what's wrong here or what I could do to further test what the actual problem is? Thanks, Rob. We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot with amd64 vs i386
I have my first SMP amd64 box at the office now to work with, and thought it was all going to be easy. Sadly not, or at least, not yet. :-) I configured dhcpd, tftpd, and nfs to export the 6.1 install CD from my notebook. All good so far. The problem is as follows: if I insert the 6.1 i386 release CD, it all works great. If I insert the amd64 CD, then I get the following after pxeboot has been going for a bit: ([EMAIL PROTECTED], Sun May 7 02:16:38 UTC 2006) Can't work out which disk we are booting from.Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' At that point, lsdev shows the disk devices, but not the pxeboot disk, which leaves me without a kernel, etc. So something is different between the i386 and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if anyone else had set up a similar configuration and had it work? Robert N M Watson I had similar experience, i recompiled a fresh pxeboot, and it's ok now. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot with amd64 vs i386
On Thu, 18 May 2006, Danny Braniss wrote: DB At that point, lsdev shows the disk devices, but not the pxeboot disk, which DB leaves me without a kernel, etc. So something is different between the i386 DB and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if DB anyone else had set up a similar configuration and had it work? DB DB Robert N M Watson DB DB I had similar experience, i recompiled a fresh pxeboot, and it's ok now. Hmm, would you please point me to the right pxeboot? I tried both i386 and amd64 versions from 6.1-R ISOs as well as i386 version from April's RC. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot with amd64 vs i386
On Thu, 18 May 2006, Danny Braniss wrote: DB At that point, lsdev shows the disk devices, but not the pxeboot disk, which DB leaves me without a kernel, etc. So something is different between the i386 DB and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if DB anyone else had set up a similar configuration and had it work? DB DB Robert N M Watson DB DB I had similar experience, i recompiled a fresh pxeboot, and it's ok now. Hmm, would you please point me to the right pxeboot? I tried both i386 and amd64 versions from 6.1-R ISOs as well as i386 version from April's RC. i compiled the one in the src of the 6.1-stable. /src/sys/boot/i386/pxeldr i took the easy road, cd /src; make buildkernel, and picked up pxeboot danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot with amd64 vs i386
On Thu, 18 May 2006, Danny Braniss wrote: DB DB At that point, lsdev shows the disk devices, but not the pxeboot disk, which DB DB leaves me without a kernel, etc. So something is different between the i386 DB DB and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if DB DB anyone else had set up a similar configuration and had it work? DB DB DB DB Robert N M Watson DB DB DB DB I had similar experience, i recompiled a fresh pxeboot, and it's ok now. DB DB Hmm, would you please point me to the right pxeboot? I tried both i386 and DB amd64 versions from 6.1-R ISOs as well as i386 version from April's RC. DB DB i compiled the one in the src of the 6.1-stable. DB /src/sys/boot/i386/pxeldr DB i took the easy road, cd /src; make buildkernel, and picked up pxeboot Hmm, which architecture? I just rechecked, and got the same error with mfsroot with all pxeboots and both i386 and amd64 distribs (I think boot/loader phase is the same for them though). Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot with amd64 vs i386
I have my first SMP amd64 box at the office now to work with, and thought it was all going to be easy. Sadly not, or at least, not yet. :-) I configured dhcpd, tftpd, and nfs to export the 6.1 install CD from my notebook. All good so far. The problem is as follows: if I insert the 6.1 i386 release CD, it all works great. If I insert the amd64 CD, then I get the following after pxeboot has been going for a bit: ([EMAIL PROTECTED], Sun May 7 02:16:38 UTC 2006) Can't work out which disk we are booting from.Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' At that point, lsdev shows the disk devices, but not the pxeboot disk, which leaves me without a kernel, etc. So something is different between the i386 and amd64 disks, or maybe there's a problem with my BIOS. I was wondering if anyone else had set up a similar configuration and had it work? Robert N M Watson ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot with amd64 vs i386
On Wed, 17 May 2006, Robert Watson wrote: RW I have my first SMP amd64 box at the office now to work with, and thought it RW was all going to be easy. Sadly not, or at least, not yet. :-) RW RW I configured dhcpd, tftpd, and nfs to export the 6.1 install CD from my RW notebook. All good so far. The problem is as follows: if I insert the 6.1 RW i386 release CD, it all works great. If I insert the amd64 CD, then I get RW the following after pxeboot has been going for a bit: RW RW ([EMAIL PROTECTED], Sun May 7 02:16:38 UTC 2006) RW Can't work out which disk we are booting from.Guessed BIOS device 0x RW not found by probes, defaulting to disk0: RW can't load 'kernel' RW RW At that point, lsdev shows the disk devices, but not the pxeboot disk, RW which leaves me without a kernel, etc. So something is different between RW the i386 and amd64 disks, or maybe there's a problem with my BIOS. I was RW wondering if anyone else had set up a similar configuration and had it work? Well, I can try connecting ATAPI CDROM to our DL145G2 not active yet tomorrow to give it a try. PXE did not work for me either, see previous threads. Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
Am Donnerstag, 25. August 2005 20:06 CEST schrieb John Baldwin: [...] I have no ideay why, but over night I recompiled my PXEROOT system (BETA3 now) and the problem vanished. I can't see any changes in the cvsweb, so I have absolutely no idea what the problem was. Hardware is exactly the same. What have I missed? Maybe you had a corrupted pxeboot binary somehow? I'm quiet sure that this can't be. I played arround with several CFLAG options (-Os, -marchi486 etc.) and with several -DPXELDR_ALWAYS_SERIAL etc. so I'm sure I had tested some dozends of different pxeboot binaries. And I can't imagine that corrupted source file can cause such an error, remember that all these pxeboot binaries worked fine on PIII boxes, just not with the Elan SC520. I'm glad that it works now, but it was really interesting what in the chain of libs/dependend boot/loader stuff was the reason... Thanks for your help, -Harry pgpVgTaiWXS5H.pgp Description: PGP signature
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
On Tuesday 23 August 2005 09:34 am, Emanuel Strobl wrote: Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Ok, I read som files and found -DBTX_SERIAL. This gives me the following dump before the box reboots: uilding the boot loader arguments Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: I have no ideay why, but over night I recompiled my PXEROOT system (BETA3 now) and the problem vanished. I can't see any changes in the cvsweb, so I have absolutely no idea what the problem was. Hardware is exactly the same. What have I missed? Maybe you had a corrupted pxeboot binary somehow? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Ok, I read som files and found -DBTX_SERIAL. This gives me the following dump before the box reboots: uilding the boot loader arguments Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: I have no ideay why, but over night I recompiled my PXEROOT system (BETA3 now) and the problem vanished. I can't see any changes in the cvsweb, so I have absolutely no idea what the problem was. Hardware is exactly the same. What have I missed? Thanks, -Harry 0F4FC2cmovg eax,edx 0003 A3C87D0300mov [0x37dc8],eax 0008 8D410Clea eax,[ecx+0xc] 000B C74104FD44FF55mov dword [ecx+0x4],0x55ff44fd 0012 8939 mov [ecx],edi 0014 C64439FFFEmov byte [ecx+edi-0x1],0xfe 0019 83C40Cadd esp,byte +0xc 001C 5Bpop ebx 001D 5Epop esi 001E 5Fpop edi 001F 5Dpop ebp I'm guessing that there's been a stack overflow or some such. Your eip is in the loader. You can try using the loader.sym from your loader binary to look up that eip address. In the loader here on my laptop it's in the write function: % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort ... 00023b9c T readdirfd 00023c14 T write 00023d18 T lseek If you want to be able to use gdb, then rebuild libstand with debugging (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make DEBUG_FLAGS=-g). You can then use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and you can do listings of the addresses for eip, etc. pgpj0zK68sjPU.pgp Description: PGP signature
BTX failure [Was: Re: pxeboot problems with BETA2]
Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Ok, I read som files and found -DBTX_SERIAL. This gives me the following dump before the box reboots: uilding the boot loader arguments Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Thanks for any help, -Harry pgpl6JElkfYOu.pgp Description: PGP signature
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Ok, I read som files and found -DBTX_SERIAL. This gives me the following dump before the box reboots: uilding the boot loader arguments Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: 0F4FC2cmovg eax,edx 0003 A3C87D0300mov [0x37dc8],eax 0008 8D410Clea eax,[ecx+0xc] 000B C74104FD44FF55mov dword [ecx+0x4],0x55ff44fd 0012 8939 mov [ecx],edi 0014 C64439FFFEmov byte [ecx+edi-0x1],0xfe 0019 83C40Cadd esp,byte +0xc 001C 5Bpop ebx 001D 5Epop esi 001E 5Fpop edi 001F 5Dpop ebp I'm guessing that there's been a stack overflow or some such. Your eip is in the loader. You can try using the loader.sym from your loader binary to look up that eip address. In the loader here on my laptop it's in the write function: % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort ... 00023b9c T readdirfd 00023c14 T write 00023d18 T lseek If you want to be able to use gdb, then rebuild libstand with debugging (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make DEBUG_FLAGS=-g). You can then use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and you can do listings of the addresses for eip, etc. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BTX failure [Was: Re: pxeboot problems with BETA2]
Am Mittwoch, 17. August 2005 21:29 CEST schrieb John Baldwin: On Wednesday 17 August 2005 10:43 am, Emanuel Strobl wrote: [*schnip*] Relocating the loader and the BTX Starting the BTX loader int=0006 err= efl=00010202 eip=00023c21 eax= ebx=000384e0 ecx=000384e0 edx=0001 esi=1000 edi=0029 ebp=00086770 esp=00086758 cs=002b ds=0033 es=0033fs=0033 gs=0033 ss=0033 cs:eip=0f 4f c2 a3 c8 7d 03 00-8d 41 0c c7 41 04 fd 44 ff 55 89 39 c6 44 39 ff-fe 83 c4 0c 5b 5e 5f 5d ss:esp=b4 7d 03 00 29 00 00 00-00 10 00 00 00 00 00 00 83 57 02 00 02 00 00 00-a0 67 08 00 98 1c 02 00 BTX halted Any clue? Regarding cvsweb nothing changed recently, and I had net4501 boxes pxebooting fine with FreeBSD 5.3. Hmm. Int 6 is an invalid opcode exception: 0F4FC2cmovg eax,edx 0003 A3C87D0300mov [0x37dc8],eax 0008 8D410Clea eax,[ecx+0xc] 000B C74104FD44FF55mov dword [ecx+0x4],0x55ff44fd 0012 8939 mov [ecx],edi 0014 C64439FFFEmov byte [ecx+edi-0x1],0xfe 0019 83C40Cadd esp,byte +0xc 001C 5Bpop ebx 001D 5Epop esi 001E 5Fpop edi 001F 5Dpop ebp I'm guessing that there's been a stack overflow or some such. Your eip is in the loader. You can try using the loader.sym from your loader binary to look up that eip address. In the loader here on my laptop it's in the write function: Thanks for your attention! It's late here, I'll try to understand and see what I can do tomorrow. Just for info, simply copying pxeboot from a 5.3-release (also real verified with 5.2.1 no 5.4 so far) DVD works. Bisides that I need sio support in pxeldr so I have to compile it my own. And of course I'd love to have the new comspeed config option :) % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort ... 00023b9c T readdirfd 00023c14 T write 00023d18 T lseek If you want to be able to use gdb, then rebuild libstand with debugging (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make DEBUG_FLAGS=-g). You can then use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and you can do listings of the addresses for eip, etc. Expect to here from me the next 48 hours, tommorow I'm too busy as I could just see :( Thanks again, -Harry pgpzBtA0HvYVp.pgp Description: PGP signature
pxeboot problems with BETA2
Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... Thanks, -Harry pgpQYJVX1MOKy.pgp Description: PGP signature
Re: pxeboot problems with BETA2
On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. -- 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 pgpxiAs9U7feW.pgp Description: PGP signature
Soekris 1.28 pxeboot problem [Was: Re: pxeboot problems with BETA2]
Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis: On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote: Hello, I just wanted to ask if somebody had success with providing pxe boot service under 6-BETA2. I have two clients, one NET4501 wich just reboots after fetching pxeldr via TFTP and a Laptop which just hangs when NFS-loading kernel. I'm about to investigate further, but maybe someone can confirm that in general PXE booting with BETA2 is working... Or not... I'm PXE booting systems with RELENG_6 as of 7/27. I'll probably do an update some time this week. Thanks for the info, I found that the problem is my NET4501 (soekris). Unfortunately my Laptop also seems to have broken PXE code, I got another box booting fine. Any experiences with a net4501 and BIOS versions higher than 1.24? Like mentioned, the box gets DHCP info, loads pxeboot and after this message immediately reboots: CLIENT MAC ADDR: 00 00 24 C0 33 70 CLIENT IP: 172.21.1.248 MASK: 255.255.0.0 DHCP IP: 172.21.0.1 GATEWAY IP: 172.21.0.1 PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader Thanks a lot, -Harry pgp9JzPn9UqIm.pgp Description: PGP signature
pxeboot, NFS and root-path: bug or documentation error?
I have been setting up a pxeboot jumpstart environment for FreeBSD 4.11, following the instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/ Rather than build pxeboot like this: # rm -rf /usr/obj/* # cd /usr/src/sys/boot # make # cp /usr/src/sys/boot/i386/pxeldr/pxeboot /usr/tftpboot I just copied /boot/pxeboot from the FreeBSD-4.11 CD-ROM. Otherwise I followed the instructions very closely. The pxeboot client machine is a Compaq ProLiant DL380. On first attempt, it got as far as pxeboot starting, and then: pxe_open: server addr: 192.168.0.1 pxe_open: server path: /pxeroot pxe_open: gateway ip: 0.0.0.0 Booting [kernel]... can't load 'kernel' can't load 'kernel.old' And my NFS server logs a failed attempt to mount /pxeroot: Jun 24 16:32:40 sr-mon-00 mountd[642]: mount request from 192.168.0.240 for non existent path /pxeroot Jun 24 16:32:49 sr-mon-00 last message repeated 59 times This is strange; I thought that at this stage pxeboot would be pulling across the kernel and ramdisk via TFTP from /usr/tftpboot, although the documentation is far from clear. pxeboot(8) says: pxeboot recognizes next-server and option root-path directives as the server and path to NFS mount for file requests, respectively, or the server to make TFTP requests to. (Erm, so exactly how do I choose whether to use NFS or to use TFTP for the next stage?) Anyway, assuming that I'm forced to use NFS at this point, I added another DHCP option: option root-path 192.168.0.1:/usr/tftpboot; This option is not shown in the example dhcpd.conf in pxeboot(8), nor in the article referred to above. However, if I also put an entry in the NFS server's /etc/hosts file for the client DHCP address, it then works properly. So the question is: when pxeboot runs on the client, is it able to fetch loader.rc, the kernel and ramdisk via TFTP, or only via NFS? If it's only NFS, then I think the pxeboot(8) manpage, and the pxeboot article, ought to be updated. If it *can* use TFTP, does anyone have any suggestions for what I was doing wrong? Regards, Brian Candler. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, NFS and root-path: bug or documentation error?
On Friday 24 June 2005 01:03 pm, Brian Candler wrote: I have been setting up a pxeboot jumpstart environment for FreeBSD 4.11, following the instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/ Rather than build pxeboot like this: # rm -rf /usr/obj/* # cd /usr/src/sys/boot # make # cp /usr/src/sys/boot/i386/pxeldr/pxeboot /usr/tftpboot I just copied /boot/pxeboot from the FreeBSD-4.11 CD-ROM. Otherwise I followed the instructions very closely. The pxeboot client machine is a Compaq ProLiant DL380. On first attempt, it got as far as pxeboot starting, and then: pxe_open: server addr: 192.168.0.1 pxe_open: server path: /pxeroot pxe_open: gateway ip: 0.0.0.0 Booting [kernel]... can't load 'kernel' can't load 'kernel.old' And my NFS server logs a failed attempt to mount /pxeroot: Jun 24 16:32:40 sr-mon-00 mountd[642]: mount request from 192.168.0.240 for non existent path /pxeroot Jun 24 16:32:49 sr-mon-00 last message repeated 59 times This is strange; I thought that at this stage pxeboot would be pulling across the kernel and ramdisk via TFTP from /usr/tftpboot, although the documentation is far from clear. pxeboot(8) says: pxeboot recognizes next-server and option root-path directives as the server and path to NFS mount for file requests, respectively, or the server to make TFTP requests to. (Erm, so exactly how do I choose whether to use NFS or to use TFTP for the next stage?) Anyway, assuming that I'm forced to use NFS at this point, I added another DHCP option: option root-path 192.168.0.1:/usr/tftpboot; This option is not shown in the example dhcpd.conf in pxeboot(8), nor in the article referred to above. However, if I also put an entry in the NFS server's /etc/hosts file for the client DHCP address, it then works properly. So the question is: when pxeboot runs on the client, is it able to fetch loader.rc, the kernel and ramdisk via TFTP, or only via NFS? If it's only NFS, then I think the pxeboot(8) manpage, and the pxeboot article, ought to be updated. If it *can* use TFTP, does anyone have any suggestions for what I was doing wrong? It uses TFTP to fetch the pxeboot binary itself. After that, it uses either NFS or TFTP. By default it uses NFS to access /boot/loader and friends. If you want it to just use TFTP and not use NFS at all, you need to recompile pxeboot with LOADER_TFTP_SUPPORT=yes defined in make. That is: % cd /sys/boot % make clean % make LOADER_TFTP_SUPPORT=yes % cp /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot /usr/tftpboot -- John Baldwin [EMAIL PROTECTED]http://www.baldwin.cx/~john/ Power Users Use the Power to Serve = http://www.FreeBSD.org -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve = http://www.FreeBSD.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot, NFS and root-path: bug or documentation error?
On Fri, Jun 24, 2005 at 01:50:37PM -0400, John Baldwin wrote: It uses TFTP to fetch the pxeboot binary itself. After that, it uses either NFS or TFTP. By default it uses NFS to access /boot/loader and friends. If you want it to just use TFTP and not use NFS at all, you need to recompile pxeboot with LOADER_TFTP_SUPPORT=yes defined in make. That is: % cd /sys/boot % make clean % make LOADER_TFTP_SUPPORT=yes % cp /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot /usr/tftpboot Thank you, that's very clear. Re-reading the manpage I do now see the phrase selectable through compile-time options; perhaps it would be worth also showing those options. Is there any fundamental reason why both couldn't be compiled in at once, e.g. limitations on the pxeboot binary size? Or is it just awkward to implement? I would have no objection to options root-path = tftp://192.168.0.1/usr/tftpboot; I would also have no objection to pxeboot.nfs and pxeboot.tftp being built :-) I'll try building the tftp version when back in the office next week. Thanks again, Brian. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. It's a sort of diskless machine with all the system on ram. There is a problem when the preloaded image is ~32MB. Kernel loads but it does not seem to find the files. It seems as if only part of the image is really there. With a small image (~32MB), no probleme. I use the same image, off course, same init etc... just more data for my application in the big image case. I use a classic mfs_root approche to make my image dd if=/dev/zero of=$MFS_FILE bs=1k count=$SIZE mdconfig -a -t vnode -f $MFS_FILE -u0 bsdlabel -w /dev/md0 newfs /dev/md0a mount /dev/md0a $MFS_FILE_MOUNT cp ... my content... umount $MFS_FILE_MOUNT fsck -t ufs /dev/md0a mdconfig -d -u 0 then I mount the $MFS_FILE_MOUNT . I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? It seems not. There seems to be a size limitation in the loader (and pxeboot since it is built using loader code). I've tried loading through pxeboot + TFTP : the tftp pxeboot client is limited to 32MB unfortunately (BTW : the one of the tftp port works fine). I tried to use pxeboot + NFS, kernel hangs because of loader limitation (BTW : you can use only NFS UDP since the pxeboot NFS client don't do TCP which means booting using this this technique using TFTP is not less reliable than NFS). I even tried pxegrub, but again it's the loader ... It seems the only reasonable solution is to make a small jumpstart mfsroot, make a md device (malloc / ..) with any size you want as long as you have enough memory (even 1GB+) and then fetch the mfsroot image using tftp/nfs/scp/.. and chroot to it. Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
On Tue, Apr 19, 2005 at 04:18:17PM -0700, David G. Lawrence wrote: I assume you saw this in the tftpd manual page? BUGS Files larger than 33488896 octets (65535 blocks) cannot be transferred without client and server supporting blocksize negotiation (RFC1783). Many tftp clients will not transfer files over 1678 octets (32767 blocks). There is a PR open with a patch to fix this: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/67550 -- Francois Tigeot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem
Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. It's a sort of diskless machine with all the system on ram. There is a problem when the preloaded image is ~32MB. Kernel loads but it does not seem to find the files. It seems as if only part of the image is really there. With a small image (~32MB), no probleme. I use the same image, off course, same init etc... just more data for my application in the big image case. ... Am I missing something obvious? I assume you saw this in the tftpd manual page? BUGS Files larger than 33488896 octets (65535 blocks) cannot be transferred without client and server supporting blocksize negotiation (RFC1783). Many tftp clients will not transfer files over 1678 octets (32767 blocks). -DG Yes. Saw it. My tftp client and pxe+tftp under linux works ok. The tftp client under FreeBSD seems to work fine (1,5GB tranfered, md5sum checked, no pb). BUT, maybe the tftp client in the FreeBSD pxeboot has a problem. I am actually trying to make the mfsroot go through NFS. If that works, it will indicate the FreeBSD pxeboot has indeed this problem with TFTP. Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PXEBOOT/TFTPBOOT + big MD_ROOT problem
Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. It's a sort of diskless machine with all the system on ram. There is a problem when the preloaded image is ~32MB. Kernel loads but it does not seem to find the files. It seems as if only part of the image is really there. With a small image (~32MB), no probleme. I use the same image, off course, same init etc... just more data for my application in the big image case. I use a classic mfs_root approche to make my image dd if=/dev/zero of=$MFS_FILE bs=1k count=$SIZE mdconfig -a -t vnode -f $MFS_FILE -u0 bsdlabel -w /dev/md0 newfs /dev/md0a mount /dev/md0a $MFS_FILE_MOUNT cp ... my content... umount $MFS_FILE_MOUNT fsck -t ufs /dev/md0a mdconfig -d -u 0 then I mount the $MFS_FILE_MOUNT . I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. Any reasons for not using NFS ? I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesystem. Marc pgpPpcYFwJ4OZ.pgp Description: PGP signature
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
Marc Olzheim wrote: On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. Any reasons for not using NFS ? I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesystem. Marc I assume that the PXE clients are diskless clients. If so, do they have enough memory to handle this extremely large image? As for tfpt, it uses UDP. UDP is usually used for transfer small datagrams, for instance DNS replies. It is also said to be an unreliable protocol. The client should repeat the request when no data receives. I doubt this solution is reliable and flexible enough. My idea for a workaround is creating a ramdisk from a small boot image, and transfer the less necessary userland binaries from the boot server to the ramdisk using normal ftp connection. Cheers, Gábor Kövesdán ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem
-Message d'origine- De : [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] De la part de Marc Olzheim Envoyé : mardi 19 avril 2005 21:06 À : Emmanuel Chriqui Cc : freebsd-hackers@freebsd.org; freebsd-stable@freebsd.org Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. Any reasons for not using NFS ? Yes. Mainly : similar system already working great under linux for two years, NFS heavy traffic problems making data loss so difficult to solve (at least under Linux), cheap memory, better server independence when he got his system (tftp server shut down after the client servers got theirs images). I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. TFTP linux-FreeBSD, FreeBsd-FreeBSD, FreeBSD-Linux ok for 500MB, 1GB, 1,5GB, works ok (well... at least on our servers..). A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesyste This is roughly how it works under our linux servers, webservers, etc... I was hoping to avoid that approach (less work.. less maintenance..). Am I the only one on earth to need a big MFSROOT ??? :) Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote: This is roughly how it works under our linux servers, webservers, etc... I was hoping to avoid that approach (less work.. less maintenance..). Am I the only one on earth to need a big MFSROOT ??? :) Hmm, I guess so. :-P Anyway, you might try http://pigseye.kennesaw.edu/~dyeske/freebsd/article.html Although I'm not sure the linker will allow you to link such a huge object into the kernel... I've used this patch on my netbooted FreeBSD 4.x servers, but never larger tham 10 MB. Another idea is to use NFS just to use the loader to 'load -t mfs_root' the mfsroot image. After that, you wouldn't depend on NFS anymore. Marc pgpcxPtjHJEO0.pgp Description: PGP signature
RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem
Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote: This is roughly how it works under our linux servers, webservers, etc... I was hoping to avoid that approach (less work.. less maintenance..). Am I the only one on earth to need a big MFSROOT ??? :) Hmm, I guess so. :-P Anyway, you might try http://pigseye.kennesaw.edu/~dyeske/freebsd/article.html Thx ! ... Another idea is to use NFS just to use the loader to 'load -t mfs_root' the mfsroot image. After that, you wouldn't depend on NFS anymore. Marc Very good idea. If my problem is related to TFTP + mfs_root than than this might work. Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: PXEBOOT/TFTPBOOT + big MD_ROOT problem
Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem Marc Olzheim wrote: On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote: Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. Any reasons for not using NFS ? I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT . (same pb with a 5.3). Am I missing something obvious? I'm not sure. tftp itself is able to handle 32MB+ files, but maybe the loader isn't. A workaround, no using NFS, could be to tftp a second filesystem image on boot and mount that from the root filesystem. Marc I assume that the PXE clients are diskless clients. If so, do they have enough memory to handle this extremely large image? As for tfpt, it uses YES, diskless. And enough memory. UDP. UDP is usually used for transfer small datagrams, for instance DNS replies. It is also said to be an unreliable protocol. The client should repeat the request when no data receives. I doubt this solution is You're right. However, pros : over 2 years this solution has proven to work *perfectly* for us, Reboots are rare and done using pools (~10 servers each time), NFS was horrible to handle and we lost data everytime traffic was intense. Cons : this was over linux. I believe NFS over FreeBSD works better (by I still have my linux servers... and they work great so..). reliable and flexible enough. My idea for a workaround is creating a ramdisk from a small boot image, and transfer the less necessary userland binaries from the boot server to the ramdisk using normal ftp connection. Yes. Thx. Emmanuel. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
Hi, I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No NFS. It's a sort of diskless machine with all the system on ram. There is a problem when the preloaded image is ~32MB. Kernel loads but it does not seem to find the files. It seems as if only part of the image is really there. With a small image (~32MB), no probleme. I use the same image, off course, same init etc... just more data for my application in the big image case. ... Am I missing something obvious? I assume you saw this in the tftpd manual page? BUGS Files larger than 33488896 octets (65535 blocks) cannot be transferred without client and server supporting blocksize negotiation (RFC1783). Many tftp clients will not transfer files over 1678 octets (32767 blocks). -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot
On Wed, Apr 13, 2005 at 07:06:32PM +0200, Helmut Allwang wrote: Hello, it was possible for me, to boot a bootable floppy-image over pxeboot. Is it possible to boot a CD-image over pxeboot? You mount the image (mdconfig + mount_cd9660) on your tftp server and off you go... ;-) load path_to_kernel load -t mfs_root path_to_mfsroot set vfs.root.mountfrom=ufs:/dev/md0c boot away... Marc pgpo1bxfCv4lB.pgp Description: PGP signature
pxeboot
Hello, it was possible for me, to boot a bootable floppy-image over pxeboot. Is it possible to boot a CD-image over pxeboot? Please cc me your answers. Thank you all, Helmut __ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
pxeboot with IBM x335: failure
Hello, I'm trying to boot an IMB x335 server via PXE. I succeeded with 4.11: it booted up to a timeout in mpt (onboard LSI SCSI) followed by a panic shortly after /stand/sysinstall starts and prints probing devices. Since RHEL3 boots just fine from a disk attached to the very same controller I wanted to give 5.x a try, and this is what I get from an attempt to boot 5.3-RELEASE floppies with 5.3-p5 pxeboot compiled with tftp support. Can anyone tell me what I'm doing wrong? I can provide part numbers, exact BIOS versions, whatever is deemed relevant. Transcribed from the console, I don't have serial console here: BIOS drive A: is disk0 BIOS drive C: is disk1 PXE version 2.1, real mode entry point @9856:00d6 BIOS 554kB/523184kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Mon Mar 21 ...) pxe_open: server addr: 10.0.0.6 pxe_open: server path: /var/run/tftpboot/5.3-RELEASE pxe_open: gateway ip: 10.0.0.1 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 554kB/523184kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 ([EMAIL PROTECTED], Mon Mar 21 ...) Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' Type '?' for... OK Also of interest, ls throws input/output error for / and lsdev reports no pxe devices. BTW, this is contents of the root-path directory: [EMAIL PROTECTED] run/tftpboot/5.3-RELEASE 1047:0 # pwd /var/run/tftpboot/5.3-RELEASE [EMAIL PROTECTED] run/tftpboot/5.3-RELEASE 1048:0 # find . -type f | sort ./acpi.ko.gz ./boot/beastie.4th.gz ./boot/defaults/loader.conf.gz ./boot/device.hints.gz ./boot/frames.4th.gz ./boot/loader ./boot/loader.4th.gz ./boot/loader.conf ./boot/loader.help.gz ./boot/loader.rc ./boot/pxeboot ./boot/screen.4th.gz ./boot/support.4th.gz ./kernel.gz ./kernel.gz.aa ./kernel.gz.ab ./kernel.gz.boot ./kernel.gz.split ./mfsroot.gz [EMAIL PROTECTED] run/tftpboot/5.3-RELEASE 1049:0 # -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pxeboot btx halted problem
On Wed, 23 Jan 2002, Michael Smith wrote: You can rebuild and reinstall just libstand; it is self-contained and has no particularly special issues. Thanks for the tip. I recompiled libstand and loader picked it up out of the /usr/src tree, so I didn't even need to install it. Glad to have helped track this one down. Thank you and everyone else who helped. I learned a few things with this adventure. :) -- Jason K. Fritcher [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d-() s+:++ a- C+++() UBS+++$ P++(-) L- !E W+(--) N++(+) o? K? w--() O M- V-- PS PE Y+ PGP(++) t+@ 5 X+ R+ tv+(--) b+++ DI+ D++ G e+++ h r+++ y+++ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pxeboot btx halted problem
On Tue, 22 Jan 2002, Danny Braniss wrote: im no expert in reading btx dump, but from past experience, upgrading the firmware of the BIOS/NIC solved the problem. Before I posted my first message, I flashed the last Boot Agent onto the NIC, and after seeing your message, I hunted down and flashed the last BIOS for the motherboard which was from mid 97. Unfortunately, it is still crashing with exactly the same halted message. For those that might be interested in the hardware, the system is a Pentium 166, on a Biostar 8500TUC MB with 32 MB of RAM. That particular MB uses the Intel 430HX chipset. Only expansion cards in the system are a Matrox Millenium video card, and the Intel PRO/100 S NIC. There are no hard drives or floppy drives in the system. This machine used to be my server until I replaced it a few months ago with a new machine. -- Jason K. Fritcher [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d-() s+:++ a- C+++() UBS+++$ P++(-) L- !E W+(--) N++(+) o? K? w--() O M- V-- PS PE Y+ PGP(++) t+@ 5 X+ R+ tv+(--) b+++ DI+ D++ G e+++ h r+++ y+++ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pxeboot btx halted problem
On Tue, 22 Jan 2002, Danny Braniss wrote: Before I posted my first message, I flashed the last Boot Agent onto the NIC, and after seeing your message, I hunted down and flashed the last BIOS for the motherboard which was from mid 97. Unfortunately, it is still crashing with exactly the same halted message. For those that might be interested in the hardware, the system is a Pentium 166, on a Biostar 8500TUC MB with 32 MB of RAM. That particular MB uses the Intel 430HX chipset. Only expansion cards in the system are a Matrox Millenium video card, and the Intel PRO/100 S NIC. There are no hard drives or floppy drives in the system. This machine used to be my server until I replaced it a few months ago with a new machine. ok, so till someone can shed some light from the BTX dump (hint hint), check 1) if the pxeboot is ok 2) try tcpdump/ethereal and see if all the file is laoded ok. i gather that the host you are trying to boot, actualy is in good health ? danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pxeboot btx halted problem
On Mon, 21 Jan 2002, Ladislav Kostal wrote: On Sun, 20 Jan 2002, Jason K. Fritcher wrote: I'm trying to get a machine to netboot with the pxeboot loader and a Intel PRO/100 S network card. I built pxeboot with tftp instead of nfs support, as I am only looking to load a kernel with a mfs filesystem in it. If you want, I can send you my setup. But it is for Scom 3c905C (what should make no difference). im no expert in reading btx dump, but from past experience, upgrading the firmware of the BIOS/NIC solved the problem. danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pxeboot BROKEN!
On Sun, Aug 05, 2001 at 08:39:56PM +0200, Hartmann, O. wrote: [...] But pxeboot in /boot/ seems still broken! We cn not boot any diskless station (AMD based systems) here with the most recent image of pxeboot. To make the stations working we have to use a backuped imag from the 31st Juky this year. Can anyone make a statement? Hope I'm not the only one who got in trouble playing with the newest stuff by simply doing a cvsupdate ... Although I am still using 4.3-RELEASE (no spare machines for playing with new toys or pre-releases) I did a cvsup to the recent 4-STABLE source code and compiled the boot code. The new pxeboot works pretty normally, no casualties there. Since I used the 4.3-RELEASE tool chain the problem may be located there. Also make sure not to use fancy compiler options like -O2 or -m486, etc. Björn Fischer -- -BEGIN GEEK CODE BLOCK- GCS d--(+) s++: a- C+++(-) UBOSI$ P+++(-) L---(++) !E W- N+ o+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: pxeboot problems with 4.0-stable (continued)
Gerhard Sittig [EMAIL PROTECTED] probably said: Listening on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0 Sending on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0 Sending on Socket/fallback/fallback-net I would expect the daemon to listen on and to send to a "real" address (i.e. 10.25.1.1) instead of the network address. No, dhcp listens on interfaces and also lists the networks assosicated with those interfaces. If you read that line, it's listening on fxp1 via BPF which has that ethernet address and that network associated with it. Startup messages like that are perfectly normal. P. -- pir [EMAIL PROTECTED][EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pxeboot problems with 4.0-stable
Here goes: / int=0006 err= efl=00010216 eip=00010216 eax= ebx=0fc08510 ecx=0002c4a0 edx=190d esi=0002e984 edi=000224a0 ebp=180ae850 esp=3420 cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 cs:eip: ff ff ff ff ff ff ff ff:ff ff ff ff ff ff ff ff ss:esp: 10 83 f8 ff 75 1a 83 fa:ff 75 15 83 c4 f4 68 40 System halted This happens after transfering about 64kb from the nfs server. I ran tcpdump on the nfs server and watched the nfs read packets. Is there a disassembler available for FreeBSD? Bill Fumerola wrote: On Wed, Jul 05, 2000 at 09:48:32AM -0500, Alan Edmonds wrote: Is anyone using pxeboot from 4.0-STABLE with the latest Intel PXE ROM (3.0.03)? I'm getting a register dump when it's loading the kernel. Speaking only as someone who saw what the people who wrote this used to debug it, you're going to actually have to give us the register dump if you expect anything to happen. Yes. This might actually mean transcribing it by hand, unfortunatly. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] -- Alan Edmonds Director of International Technology DigitalConvergence.:Com [EMAIL PROTECTED] Phone: +1-214-292-6040 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pxeboot problems with 4.0-stable
On Wed, 5 Jul 2000, Alan Edmonds wrote: Is anyone using pxeboot from 4.0-STABLE with the latest Intel PXE ROM (3.0.03)? I'm getting a register dump when it's loading the kernel. Where did you get this version? The new machines we have are all 0.X or 2.X, but no 3.X. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pxeboot problems with 4.0-stable
You need to tell me a bit more information.. I know for a fact that build 079 bootroms on the Intel Etherexpress cards (fxp) have no known issues. There are bugs in their older roms which corrupt the stack and cause our loader to trigger a fault. I need to know the card you are using, the Intel build version (07X). Build 079 is the latest build from Intel and it is the only PXE 2.0 rom that I know of which has no known bugs. Anything newer than 079, I have not tested myself.. paul Alan Edmonds ([EMAIL PROTECTED]) wrote: Is anyone using pxeboot from 4.0-STABLE with the latest Intel PXE ROM (3.0.03)? I'm getting a register dump when it's loading the kernel. Thanks, -- Alan Edmonds Director of International Technology DigitalConvergence.:Com [EMAIL PROTECTED] Phone: +1-214-292-6040 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: pxeboot problems with 4.0-stable
Sorry. Too many versions. It's PXE-2.0 build 078 but Intel Boot Agent 3.0.03. Doug White wrote: On Wed, 5 Jul 2000, Alan Edmonds wrote: Is anyone using pxeboot from 4.0-STABLE with the latest Intel PXE ROM (3.0.03)? I'm getting a register dump when it's loading the kernel. Where did you get this version? The new machines we have are all 0.X or 2.X, but no 3.X. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org -- Alan Edmonds Director of International Technology DigitalConvergence.:Com [EMAIL PROTECTED] Phone: +1-214-292-6040 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
