Even with the failover option set in the Insyde BIOS, say if you type “exit” in the iPXE shell, you’ll get a popup saying boot failed and it’ll wait for input.
Framework, can you please ask Insyde to improve this?
You may like to ask Framework via official support as they may not see this topic.
@amoun I have done so, but I would really hope they peruse the forums sometimes.
Framework: it’d be good if there were ticket numbers we could share to track commonly reported issues.
How would that work.
Ticket number for support I’m sure you have but why share that?
“I logged xyz with support on yymmdd, ticket number was #123, if you’re also logging this with them you could mention that it seems like the same issue in that ticket number”
OK So if you have such numbers why haven’t you put them in the topic to be shared. Surely you don’t expect Framework to share such info?
No, I’m saying they don’t generate those kinds of numbers with the support tickets! Whatever tracking ID they use is internal to them!
1 Like
So are you thinking of
a) having a support number
and
b) either use that on the forum or
c) get other people to use to use it to prompt Framework
In the last case why bombard Framework with ideas? Do you think they don’t have enough on their plate?
I mean, this is really a bug but whatever.
What’s the full scenario here? If there is no iPXE on the network does it failover or also just fail to boot?
I’ve stopped testing for now but if there’s no boot info in DHCP or it can’t reach the server, you get “Failed to boot [OK]”
The IPv4 boot timeout is also extremely long. I haven’t done a packet capture yet but I think it’s a few retries plus a really long connection timeout.