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"
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
