Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unsupported client firmware type '0' (please file a bug!) #132

Open
coolty opened this issue Jul 29, 2021 · 5 comments
Open

unsupported client firmware type '0' (please file a bug!) #132

coolty opened this issue Jul 29, 2021 · 5 comments

Comments

@coolty
Copy link

coolty commented Jul 29, 2021

sudo pixiecore quick xyz --dhcp-no-bind
[DHCP] Offering to boot 08:00:46:45:c1:bf
[PXE] Unusable packet from 08:00:46:45:c1:bf (192.168.0.10:68): unsupported client firmware type '0' (please file a bug!)
[PXE] Unusable packet from 08:00:46:45:c1:bf (192.168.0.10:68): unsupported client firmware type '0' (please file a bug!)
[PXE] Unusable packet from 08:00:46:45:c1:bf (192.168.0.10:68): unsupported client firmware type '0' (please file a bug!)
[DHCP] Offering to boot 08:00:46:45:c1:bf
[PXE] Unusable packet from 08:00:46:45:c1:bf (192.168.0.10:68): unsupported client firmware type '0' (please file a bug!)
[PXE] Unusable packet from 08:00:46:45:c1:bf (192.168.0.10:68): unsupported client firmware type '0' (please file a bug!)

Trying to boot a Sony PCG-SRX3E/BD Laptop that originally ran Windows XP and has a Celeron CPU...

@PMunch
Copy link

PMunch commented Aug 19, 2021

Just faced the same issue trying to boot a Fujitsu Lifebook B2154 that also runs a Celeron but is intended for Windows 98 or 2000. Booting it yields the same message (with a different MAC address of course). The device itself says "Intel UNDI, PXE-2.0 (build 071)" and simply spins on the DHCP stage of the boot.

@frantisekhanzlikbl
Copy link

Just wanted to say that I have bumped into this as well, on two different devices. I am not sure what details are relevant, but one of them was ARM (RPI4) which, as I understand #72, is not supported, but the other one is a pretty normal x86-64 machine with an AMD CPU and an AORUS motherboard.

@RaitoBezarius
Copy link

Just run into that issue on a Proxmox VM, uncertain how to debug this further.

@Ognian
Copy link

Ognian commented Feb 27, 2023

Same problem, no Idea what to do

@mudler
Copy link

mudler commented Mar 2, 2023

hey @danderson 👋 anything we can do from our side to collect more logs and help?

Can you provide some guidance on how to debug so we can try to come up with a fix/PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants