search for: multiboot2

On 30.10.2013 12:19, Daniel Kiper wrote: > Hi, > multiboot2 protocol requires some more changes. However, about 80% of code > is ready. In this case Xen and modules are loaded by GRUB2 itself. It means > that all images could be placed on any filesystem recognized by GRUB2. Options > for Xen and modules are passed separately which simplifies comman...

Following is one grub entry menuentry "Ubuntu, Linux 2.6.32.27" { insmod ntfs set root=''(hd0,2)'' search --no-floppy --fs-uuid --set 96f65c80f65c6313 loopback loop0 /ubuntu/disks/root.disk set root=(loop0) linux /boot/vmlinuz-2.6.32.27 root=/dev/sda2 loop=/ubuntu/disks/root.disk ro quiet splash initrd

...are initialized artificially by Xen EFI boot stuff. Additionally, due to that there is no place for extra boot info in multiboot_info_t e.g. ACPI data is passed via supplementary global variables. Now there is a requirement for boot Xen on EFI platform via GRUB. Due to that new boot protocol called multiboot2 should be supported. This means that in current situation another conversion to legacy multiboot_info_t structure and others should be implemented. However, due to limitations of multiboot_info_t structure not all arguments (e.g. ACPI data) could be passed via it. That leads to further code complic...

Hello guys, I wonder if and how can I boot my custom kernel (if at all) with pxelinux. My kernel stored in single 64bit ELF file and it has multiboot2 header. The closest module I've found was mboot.c32, but it seems not to work in my case. Thank you! -- *Best wishes,* *Alex*

Hi Ian, can we push multiboot v2 support for Xen/ARM still into 4.3? It looks like it can coexists with zImage in the same binary - the multiboot structure can be put just behind the zImage header and the code can determine how it has been started: zImage bootloaders clears r0, multiboot one''s would set r0 to the MB magic. I will sketch a patch tomorrow, just wondering if we can have

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

hi folks, after long trying i need some help from the big world :-) question ******** when I boot a guest system, tried debian 6.0.2 amd64 firmware, I get errors like: 1) after click install on debian 6.0.2 installer [0.642450] vbd vbd-5632: 19 xenbus_dev_probe on device/vbd/5632 [0.642911] vbd vbd-5632: failed to write error node for device/vbd/5632 (19 xenbus_dev_probe on device/vbd/5632) 2)

...386-efi\moddep.lst (4.7 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\morse.mod (2.4 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\mpi.mod (28.6 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\msdospart.mod (2.5 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\multiboot.mod (12 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\multiboot2.mod (13.3 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\nativedisk.mod (4.2 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\net.mod (46.9 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\newc.mod (3 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\normal.mod (117.8 KB) Extracting: F:\EFI\BOOT\grub\i386-efi\ntfs.mod (9.9 K...

On 3/3/2016 07:43, Pete Batard via Syslinux wrote: > [...] as far as I am concerned, 'A "version" such as "6.03" [is not] > enough'. [...] I'd like to help to improve Syslinux with regards to version-related concerns. Having typed that, perhaps we could discuss your (or Rufus') specific needs, in parallel? Do I understand correctly that the primary