Hey All,
I have a working pxe/tftp environment that works great with Fedora27, and I am just now starting to test rawhide. But when I use the same setup, and to pxe boot rawhide, my client returns the following error:
"PXE-E23: Client received TFTP error from server"
I can see the logs on the server, and the client is pxe booting, and getting an IP address. But right afterwards, the client returns that error.
My dhcpd.conf entry for the client is as follows:
-------------------------- host mustang1 { hardware ethernet 00:01:73:02:36:10; fixed-address 192.168.1.93; next-server 192.168.1.2; # filename "linux-install/fedora27/BOOTAA64.EFI"; filename "linux-install/rawhide/BOOTAA64.EFI"; # filename "linux-install/rhel-alt-74/BOOTAA64.EFI"; # filename "linux-install/mustang/UpgradeFirmware.efi"; } -------------------------
And when I comment out the rawhide entry, and uncomment any of the others, the client proceeds to boot as expected.
I got all my boot files this time from the rawhide netinst iso: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aar...
Has anyone run into this issue in their testing yet?
Thanks!
Update... I downloaded the rawhide BOOTAA64.EFI from a different location and am now getting a different error.
I originally got my boot files out of the the netinst iso from the rawhide download site: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aar...
- The BOOTAA64.EFI file from this source gives me the original "PXE-E23" error.
Then, just for fun, I downloaded the BOOTAA64.EFI file directly: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aar...
And when I replace the original with this file, I get a different error on the mustang:
..dppath: path: Fetching Netboot Image Unable to fetch TFTP image: TFTP Error start_image() returned TFTP Error
Again, the logs on my server tell me the mustang is pxe booting and getting an IP address. And when I tell my dhcp service to serve out the Fedora27 BOOTAA64.EFI file instead, everything proceeds, and the system boots as expected. So I have to assume at this point there is a bug - or I am doing something dumb because I need sleep. :-)
Thanks!
Hi Chris,
----- Original Message -----
Update... I downloaded the rawhide BOOTAA64.EFI from a different location and am now getting a different error.
I originally got my boot files out of the the netinst iso from the rawhide download site: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aar...
- The BOOTAA64.EFI file from this source gives me the original "PXE-E23"
error.
Looks like an issue with the new shim[1], I don't think anyone's filed a bug on that yet if you want to that would be great, if not I can do so tomorrow. Thanks for finding it!
Paul
[1] - https://kojipkgs.fedoraproject.org/compose//rawhide/Fedora-Rawhide-20180315.... - https://koji.fedoraproject.org/koji/buildinfo?buildID=1054372
Then, just for fun, I downloaded the BOOTAA64.EFI file directly: https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Server/aar...
And when I replace the original with this file, I get a different error on the mustang:
..dppath: path: Fetching Netboot Image Unable to fetch TFTP image: TFTP Error start_image() returned TFTP Error
Again, the logs on my server tell me the mustang is pxe booting and getting an IP address. And when I tell my dhcp service to serve out the Fedora27 BOOTAA64.EFI file instead, everything proceeds, and the system boots as expected. So I have to assume at this point there is a bug - or I am doing something dumb because I need sleep. :-)
Thanks! _______________________________________________ arm mailing list -- arm@lists.fedoraproject.org To unsubscribe send an email to arm-leave@lists.fedoraproject.org
Hey Paul,
I think Ed from APM already opened a bug. He ran into issues with his beaker environment, but I think it may be related. I added my own experiences to his bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1557438
If you think I have stumbled across something different, let me know and I'll open another bug for you.
Thanks!