Bug 6533 - uEFI Network booting should be default to last priority
Summary: uEFI Network booting should be default to last priority
Status: RESOLVED MOVED
Alias: None
Product: MinnowBoard MAX
Classification: Hardware Platforms
Component: hw-minnowmax (show other bugs)
Version: 1C A1
Hardware: MinnowBoard Max x86_64
: Medium normal
Target Milestone: A1 Release
Assignee: John 'Warthog9' Hawley
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-07-14 19:58 UTC by John 'Warthog9' Hawley
Modified: 2017-06-13 18:03 UTC (History)
10 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
change names of EFI Network boot option (2.03 MB, application/x-zip-compressed)
2014-12-29 01:29 UTC, Lu_Shifei 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John 'Warthog9' Hawley 2014-07-14 19:58:57 UTC 
uEFI Network booting should be default to last priority, even below shell *UNLESS* a user explicitly changes the order (in which case that change takes precedent)

Currently network booting is preferred over shell
Comment 1 He, Tim 2014-08-28 07:18:34 UTC 
It is normal case that network booting is preferred over shell. Because it would be preferred over shell when system detect boot device. and user can press <F2> to enter bios menu to choose uefi shell if he want to boot shell.
Comment 2 John 'Warthog9' Hawley 2014-09-25 23:16:09 UTC 
need to double check / verify this
Comment 3 John 'Warthog9' Hawley 2014-11-20 23:11:12 UTC 
This is still an exhibited problem in the pre-release 0.75 firmware, both Darren and I have seen network being a higher priority by default than "last"
Comment 4 John 'Warthog9' Hawley 2014-12-15 22:42:27 UTC 
freshly installed 0.76 (preview) results in this being the boot order:

    Change the order                 <EFI Network>
                                     <EFI Network 1>                                                
                                     <EFI Internal Shell>                                           
                                     <EFI Misc Device>

Obviously not fixed yet
Comment 5 David_Wei 2014-12-17 03:07:10 UTC 
We will change to neames of network boot options to be
        - EFI Network IPv4
        - EFI NEtwork IPv6

For the boot order, as Tim described above, it is normal that network booting take precendence over shell. UEFI Shell is always by default treated as the lowest priority boot option. 

I assume Tim's above explanation is not what you want. You still want to force Netowrk to the last. Please confirm, so taht we could allocate resource to implement it.
Comment 6 Lu_Shifei 2014-12-29 01:29:32 UTC 
Created attachment 2308 [details]
change names of EFI Network boot option

John,we have changed names of Network boot option to be EFI Network IPv4 or EFI Network IPv6,can you try this test image on your side?Thanks a lot!
Comment 7 David_Wei 2015-01-15 05:09:02 UTC 
It is possible that there are multipl network cards exit on a signal MinnowBoard MAX. We are thinking a long-term solution for UEFI core to handle this case. 
One solution is displaying the network boot option as below: 

        - EFI Network <MAC Address> <IP version> 


It's appreciated if you provide suggestions on naming the network boot option.
Comment 8 David_Wei 2015-01-16 02:30:07 UTC 
Assign to David. Darren and John confirmed that customer prefer to move Network boot option to the default last priority.
Comment 9 Mang Guo 2015-03-06 06:11:12 UTC 
The fix will be in the 0.78 release.
Comment 10 David_Wei 2015-03-24 00:56:32 UTC 
Assign to John. V0.78 release has fixed this issue. Please review it.
Comment 11 Stephen K Jolley 2017-06-13 18:03:07 UTC 
We are no longer tracking in Yocto Project Bugzilla MinnowBoard and MinnowBoard-MAX HW and firmware bugs.