| Summary: | Timing of Netboot is different if UEFI does not pass through UEFI Shell | ||
|---|---|---|---|
| Product: | [Hardware Platforms] MinnowBoard MAX Firmware | Reporter: | Bill Mills <wmills> |
| Component: | minnowboard-uefi-firmware | Assignee: | chao zhang <chao.b.zhang> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | scott.a.garman, warthog9 |
| Version: | unspecified | ||
| Target Milestone: | Production Release | ||
| Hardware: | MinnowBoard | ||
| OS: | x86 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
MinnowBoard v1 has reached new feature EOL, FW development is done as are new hardware features. If you feel EXCEEDINGLY strongly about an issue please re-open it for discussion but be aware that we are recommending individuals migrate to the MAX platform. |
I am running Firmware version 1.0 If I change the boot order to immediatly boot to IPv4, the timing is quite a bit different than if I pass through the UEFI SHell. Shell Direct Initial delay 0 S 12 S Discover to Request delay 2 S 15 S UEFI Shell is boot option 0: Boot, esc, "exit", esc, "exit", choose IPv4 from boot menu "Start PXE over IPv4" comes out on HDMI and serial port Immediatly sends DHCP Discover packet and gets DHCP Offer waits *2* seconds Sends DHCP Request and process completes For Direct boot: "Start PXE over IPv4" comes out on HDMI and serial port waits *12* seconds Sends DHCP Discover packet and gets DHCP Offer waits *15* seconds Sends DHCP Request and process completes This makes me wonder if the timers are running on different rates in the two boot paths or similar init condition differences.