| Summary: | Installing Yocto on EFI systems | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Runtime] Installation | Reporter: | tomasz.meresinski | ||||
| Component: | Installation | Assignee: | Alejandro Hernandez <alejandro.hernandez> | ||||
| Status: | RESOLVED NOTABUG | QA Contact: | |||||
| Severity: | minor | ||||||
| Priority: | Medium | CC: | alejandro.hernandez, benjamin.esquivel, kevin.tian, sgw | ||||
| Version: | 2.1.2 | ||||||
| Target Milestone: | 2.4 M1 | ||||||
| Hardware: | x86 | ||||||
| OS: | x86_64 | ||||||
| Whiteboard: | |||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||
| Attachments: |
|
||||||
(In reply to comment #0) > Created attachment 3435 [details] > Patches > > Hi, > I had some difficulties during installing my image by init-install-efi.sh. > After some research I found out, that on my platform it was necessary to > invoke grub-install. Patch resolving it is in attachments. > The second bug was incorrect location of grub.cfg file after install. I > patched it too. > > I'm not sure if it is a good idea to apply those patches because they may > break on other platforms but I think you should know that there are some EFI > firmware which doesn't like your current script. Maybe it would be a good > idea to copy EFI handling from other distros? What platform are you using? /sys/devices/virtual/dmi/id# for file in bios* board*; do echo $file; cat "$file"; done
bios_date
02/02/2016
bios_vendor
FUJITSU // American Megatrends Inc.
bios_version
V5.0.0.11 R1.11.0 for D3402-B1x
board_asset_tag
board_name
D3402-B1
board_vendor
FUJITSU
board_version
S26361-D3402-B1
Hey Tomasz, I was taking a look at your patches and I do believe they work for your specific platform, but I dont think this can be classified as a bug, I believe its more related to the specific configuration that you choose. It looks that the EFIVAR should be set to what you are setting it to already, I am unsure whether this should be done by you or automatically, like I said, it looks like this is related to your specific configuration. Also you are mentioning efivar, efibootmgr, etc. Which are part of meta-oe and technically they are not part of the core distribution, you may want to send these by email to the meta-oe list, using the tag [meta-oe]: openembedded-devel@lists.openembedded.org |
Created attachment 3435 [details] Patches Hi, I had some difficulties during installing my image by init-install-efi.sh. After some research I found out, that on my platform it was necessary to invoke grub-install. Patch resolving it is in attachments. The second bug was incorrect location of grub.cfg file after install. I patched it too. I'm not sure if it is a good idea to apply those patches because they may break on other platforms but I think you should know that there are some EFI firmware which doesn't like your current script. Maybe it would be a good idea to copy EFI handling from other distros?