15:21 Enable U-Boot at Virtualbox to boot images thomas.mittelstaedt ^ raw reply related 11+ messages in thread # CONFIG_CMD_NFS is not -37,6 +36,9 CONFIG_MAC_PARTITION=y a/configs/efi-x86_payload64_defconfigĬONFIG_BOOTARGS="root=/dev/sdb3 init=/sbin/init rootwait ro" Here the discs at AHCI (scsi) bus are used to load the need boot data.Ĭonfigs/efi-x86_payload64_defconfig | 6 ++++-ġ file changed, 4 insertions(+), 2 deletions(-)ĭiff -git a/configs/efi-x86_payload64_defconfig b/configs/efi-x86_payload64_defconfig U-Boot at VirtualBox must load Linux and boot configuration from disk devices. 15:21 ` X86: pxeboot: bugfix: Set variable for size of initrd thomas.mittelstaedtĢ siblings, 0 replies 11+ messages in thread 15:21 ` X86: Add support for distro boot thomas.mittelstaedt 15:21 Enable U-Boot at Virtualbox to boot images 15:21 ` thomas.mittelstaedt X86: pxeboot: bugfix: Set variable for size of initrdĬonfigs/efi-x86_payload64_defconfig | 18 +++++. First patch was set with mtt2hi and Now set with my Unneccessary option CONFIG_CMD_SETEXPR no more set defconfig now handled with savedefconfig option at make So AHCI and IDE devices are not handled correctly without this patch. Images supporting distro boot capability.Ītm the patch "pci: coreboot: Don't read regions when booting" from Simon Glass The changes are needed to get U-Boot to be started at VirtualBox Marek Vasut, Manuel Traut, Heinrich Schuchardt, Bin Meng ` (2 more replies) 0 siblings, 3 replies 11+ messages in threadįrom: thomas.mittelstaedt 15:21 UTC ( / raw)Ĭc: Simon Glass, Niel Armstrong, Patrick Delaunay, Ramon Fried, 15:21 ` X86: Add support for SCSI devices thomas.mittelstaedt │ │ ├── │ ├── │ ├── │ ├── │ ├── eo.Enable U-Boot at Virtualbox to boot images archive mirror help / color / mirror / Atom feed * Enable U-Boot at Virtualbox to boot images 15:21 thomas.mittelstaedt I can take a picture of this error if this is useful. but I am afraid that it will mess up my existing setup even more overwriting GRUB. I had to change the path accordingly since they seem to be different in Windows 10, but the new menu entry does not work: I get an error saying that I should use the Windows disk and fix problems. I tried to do what is suggested here: … menu_entry Therefore I assume the problem is caused by having two drives.Īs you can see from the output above, I *do not* have an EFI system partition on the HDD, only on the SSD. I did the same thing on another PC except everything was on the same disk, and it worked, meaning os-prober was able to detect Windows. Sector size (logical/physical): 512 bytes / 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes
0 Comments
Leave a Reply. |