search for: linuxefi

...linux... ok Loading iramfs.gz...ok [then reboot] My syslinux.cfg is pretty simple: DEFAULT linux LABEL linux SAY Booting System... KERNEL linux APPEND initrd=iramfs.gz apic=debug lapic acpi=ht consoleblank=0 vga=1 TIMEOUT 1 I didn't find any documentation on the syslinux page for "linuxefi" command - where is this documented? Or is there a "default" syslinux.cfg for efi that I could use as a template? I also moved the iramfs.gz to the separate INITRD command - still no change. Any further hints? How can I debug this? I also change the vga=1 to vga=0 - without and ef...

...rd_NO_MD LANG=fr_FR.UTF-8 SYSFONT=latarcyrheb-sun16 rd_NO_LVM rd_NO_DM crashkernel=auto initrd /boot/initramfs-2.6.32-754.3.5.el6.centos.plus.x86_64.img } When I try to boot, I get a message that "linux" and "initrd" aren't valid commands. If I change them to "linuxefi" and initrdefi", I get this error: error: kernel too old error: you need to load the kernel first The information in the entry seems correct (partition, UUID, etc.). I've searched on Google quite a bit, but didn't find anything useful. Are there any suggestions? -- Yves Belle...

Hi all, I did my first steps on syslinux 6.03 with EFI... I prepared the disk with GPT, EFI system partition and formatted it FAT32. I added the files to EFI/BOOT including the syslinux libraries and syslinux.cfg The system starts booting, loads kernel and initrd (I see the loading output on the screen), but then the system resets and the loop restarts (infinitely). I took the same

...firmware fs hypervisor kernel module power It seems that g.ls('/sys') is chrooted correctly. But g.sh('ls /sys') isn't. I came across this behavior when I used g.command(['grub2-mkconfig', '-o', '....']) on rhel7.8 and it didn't produce the correct linuxefi/initrdefi entries in grub, since in rhel7.8 the uefi detection algorithm is checking in bash '[ -d /sys/firmware/efi ]'. https://src.fedoraproject.org/rpms/grub2/blob/71e0fb4ea646071ec86e4a65bb24241e31c156bb/f/0106-Make-10_linux-work-with-our-changes-for-linux16-and-.patch I thought I coul...

...> > My syslinux.cfg is pretty simple: > DEFAULT linux > LABEL linux > SAY Booting System... > KERNEL linux > APPEND initrd=iramfs.gz apic=debug lapic acpi=ht consoleblank=0 vga=1 > TIMEOUT 1 > > I didn't find any documentation on the syslinux page for "linuxefi" command - > where is this documented? > > Or is there a "default" syslinux.cfg for efi that I could use as a template? > > I also moved the iramfs.gz to the separate INITRD command - still no change. > > Any further hints? How can I debug this? > I also ch...

Am 14.03.23 um 12:30 schrieb Rob Kampen: > OK, > > found out the problem as to why it doesn't boot any kernel except 36.2 > > the system reports that it cannot find > > vmlinuz-3.10.0-1160.88.1.el7.x86_64 > > or any one of the others, except for vmlinuz-3.10.0-1160.36.2.el7.x86_64 > > hence a manual selection from the grub menu when in front of the machine

Hi all - I'm not sure if it's appropriate to ask this here, but I don't see this question explicitly answered anywhere. Is there an EFI version of "pxelinux.0" that will function basically the same way and read the same pxelinux.cfg/default menu files? I've got a really dodgy grubx64.efi EFI PXE menu up at work, but it can't load the 1.2 gigabyte LiveCD that we use

...> It seems that g.ls('/sys') is chrooted correctly. > > But g.sh('ls /sys') isn't. > > > > I came across this behavior when I used g.command(['grub2-mkconfig', '-o', > > '....']) on rhel7.8 and it didn't produce the correct linuxefi/initrdefi > > entries in grub, since in rhel7.8 the uefi detection algorithm is checking > > in bash '[ -d /sys/firmware/efi ]'. > > https://src.fedoraproject.org/rpms/grub2/blob/71e0fb4ea646071ec86e4a65bb24241e31c156bb/f/0106-Make-10_linux-work-with-our-changes-for-linux1...

...ooting page?: https://wiki.syslinux.org/wiki/index.php?title=Common_Problems In particular, there is a section at the end that looks similar to your problem. I'm not familiar with the problem. You might try some variations on the command you are using to load the kernel (e.g. try using "linuxefi" instead of the "linux" or "kernel" command).

...9;t run the guest. > It seems that g.ls('/sys') is chrooted correctly. > But g.sh('ls /sys') isn't. > > I came across this behavior when I used g.command(['grub2-mkconfig', '-o', > '....']) on rhel7.8 and it didn't produce the correct linuxefi/initrdefi > entries in grub, since in rhel7.8 the uefi detection algorithm is checking > in bash '[ -d /sys/firmware/efi ]'. > https://src.fedoraproject.org/rpms/grub2/blob/71e0fb4ea646071ec86e4a65bb24241e31c156bb/f/0106-Make-10_linux-work-with-our-changes-for-linux16-and-.patch I...

...d ^X can be used to 'edit' and 'execute' boot statements, none of which works correctly or is obvious what to alter or enter. I also got into an interface with a 'grub>' prompt. I tried some of the grub commands, but had little clue what to do with that. E.g., "linuxefi /isolinux/isolinux.bin" returned "error: invalid magic number." Interesting, but not getting CentOS 7 booted. Any know what else is possible?

...d ^X can be used to 'edit' and 'execute' boot statements, none of which works correctly or is obvious what to alter or enter. I also got into an interface with a 'grub>' prompt. I tried some of the grub commands, but had little clue what to do with that. E.g., "linuxefi /isolinux/isolinux.bin" returned "error: invalid magic number." Interesting, but not getting CentOS 7 booted. Any know what else is possible?

...too old, but the latest centosplus kernel for CentOS 6, vmlinuz-2.6.32-754.3.5.el6.centos.plus.x86_64, apparently qualifies. The solution was to install the latest kernel-ml kernel from ELRepo, https://elrepo.org/ , to change grub.cfg to reflect the new versions, and to change linux and initrd to linuxefi and initrdefi. I'm surprised this has apparently never arisen before. Am I really the first person to dual-boot CentOS 6 and 7? Thanks to Lingzhu Xiang for his bug report, https://bugzilla.redhat.com/show_bug.cgi?id=894300 , which put me on the right track. -- Yves Bellefeuille <yan at s...

...They are all identical to the installed one (distributed with grub). I'm tantalizingly close. CentOS6 UEFI PXE is working, but the machine won't boot. It is best to use the CentOS7 BOOTX64.EFI loader. The "kernel too old" message is due to the fact that the PXE config file uses linuxefi and initrdefi directives. They need to be changed to linux/initrd, respectively. linux16/initrd16 may also work. The arguments to those directives need to adhere to CentOS6 legacy grub syntax (ks instead of inst.ks etc.). This will cause error messages on the client that both linux and initrd are...

...st to my server. I can see the DHCP request at PXE boot time, and it works, but none after dowlnoading vmlinuz and initrd.img. The only solution was to provide the network setup the grub.cfg file and a waitfornet instruction: set timeout=5 ? ? menuentry 'Centos7-UEFI-most-most8pc19' { ??? linuxefi centos74/vmlinuz *inst.waitfornet=30 ipv6.disable=1 ip=**/<desktop IP>/**::**/<gateway>/**:**/<mask>/**:**/<hostname>/**:em1:none *inst.repo=http:///<server IP>//centos74 inst.ks=http:///<server IP>//Kickstart7/optiplex9030_uefi_fr.cfg devfs=nomount ??? echo &quo...

...ned to me once grub.cfg 1.1MB was large, on fedora. If Grub2 is so installed that it looks for strange systems, a yum installation, because of grub2-mkconfig, also take a long time. It works as it is. The grub2 plugin needs a little bit work. But now analyse jet. I made ist failsafe for linux and linuxefi. For me, it was important to know whether such a thing under centos works, because yum-plugin-fs-snapshot is intended for several file systems. Can be helpful or not. Just something different for me. Fun work :-) Sincerely Andy

...ed separately which simplifies command line editing > in boot loader and parsing. multiboot2 protocol is very flexible and could be > easily extended in the future if a need arises. Support for secure boot and > shim loader could be added. However, it was not implemented yet. Probably > linuxefi module could be used as a reference or even as a base for development. > However, I do not know are there plans to support such solution by GRUB2 > community. Currently, support for native PE images signatures and GPG signatures > is under development for GRUB2 upstream. > GPG signatur...

Gordon Messmer writes: > On 10/21/19 6:38 AM, isdtor wrote: > > Booting with CentOS6 /boot/efi/EFI/redhat/grub.efi, and the older style pxe config file as per ... results in a grub (legacy) prompt on the target machine. > > > Have you tried using the file from the installation tree? > > http://centos.s.uw.edu/centos/6/os/x86_64/EFI/BOOT/ > > or with files

...t; SYSFONT=latarcyrheb-sun16 rd_NO_LVM rd_NO_DM crashkernel=auto > initrd /boot/initramfs-2.6.32-754.3.5.el6.centos.plus.x86_64.img > } > > When I try to boot, I get a message that "linux" and "initrd" aren't > valid commands. If I change them to "linuxefi" and initrdefi", I get > this error: > > error: kernel too old > error: you need to load the kernel first > > The information in the entry seems correct (partition, UUID, etc.). > > I've searched on Google quite a bit, but didn't find anything useful. >...

...============ load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root 46985d35-b7e3-41f9-9bc0-8ae6c11bc84c else search --no-floppy --fs-uuid --set=root 46985d35-b7e3-41f9-9bc0-8ae6c11bc84c fi linuxefi /vmlinuz-4.11.11-300.fc26.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap nouveau.runpm=0 rhgb quiet resume=/dev/dm-1 initrdefi /initramfs-4.11.11-300.fc26.x86_64.img ========================================================= Using the same boot sequence with 4.12...