mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 07:05:56 +03:00
[GH-ISSUE #1633] TFTP and ISO boot fails on old Z77X-UD3H, Atheros RT8151 #552
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#552
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Koli0842 on GitHub (Jun 3, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1633
[x]: This bug persists when memory is increased beyond 8GB.
Describe the bug
I have an old ~2012 Gigabyte Z77X-UD3H motherboard with Atheros RT8151 gigabit NIC, that has UEFI and supports PXE boot. When booting I get the NBP file downloaded succesfully, then
iPXE initialising devices..where my system hangs. There is also autoexec.ipxe not found, but from what I've gathered that's not an issue. I can also see messages suggesting a timeout in the logs:
2025-06-03 22:37:43 err dnsmasq-tftp[32]: error 8 User aborted the transfer received from 192.168.2.58I have tried all x86 files, both efi and kpxe to much of the same results.
I have tried the bootable ISO on a USB stick option, where I get to "Available devices..", get prompted for failsafe menu for a fraction of a second, then get a generic BIOS message of no bootable device detected, etc.
To Reproduce
Steps to reproduce the behavior:
Would probably require my set of hardware, as the hosted instance works fine on other machines
Expected behavior
A working menu like on my other PCs
Additional context
I host Netboot.xyz from TrueNAS, and use Ubiquiti's DHCP settings to point clients to a file. I have modern PCs that boot from PXE fine and work well. I encountered https://github.com/netbootxyz/netboot.xyz/issues/1198 where there was an extra character at the end of the filename and was able to get past that with a workaround. I work in tech, I know a fair bit of things, but I am clueless about what makes PXE tick. I am clueless here.
@JackHarckness commented on GitHub (Oct 2, 2025):
I have the same problem on ~2018 x99 based motherboard.