search for: initrdefi

...R.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 Bellefeuille <yan at s...

...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 could simply g...

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

...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-.pat...

...he 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 It's pr...

...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 storm.ca>

...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 unknown comman...

...v6.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 "Loading centos74/initrd.img" ??? initrdefi centos74/initrd.img ??? echo "Booting installation kernel" } Realy strange as I boot and autoinstall many other PC from these server. I also notice that network is set to 100MbFD even if I have Gigabit switch. May be something related to the e1000 driver provided at boot time. Patrick

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

...heb-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 sugges...

...d --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.5-300 is problematic with bootup and suspend and wake. Hardware: XPS 15 9560 Fedora 26: all the latest updates current as of 14 Aug 2017 -- You are receiving...

I'm trying to autoinstall a DELL 9030 desktop with CentOS7 using PXE and Kikstart. I fall in a strange problem (I have several other laptop or desktop using this install process without any problem, kernel and initrd are from a Centos 7.4 iso) - PXE boot start and the desktop load the kernel and the inirtd file - the kernel is booted and at this time the led of the network switch goes down

Does anyone know if it is possible to 'hide' a grub menuentry with CentOS 7 ? I have a custom menuentry that I don't want to be seen on the grub screen - but it needs to be selectable as the entry to boot via 'grub2-reboot' I've scanned the grub2 documentation - but I can't find anything obvious - so I'm guessing it can't be done - unless someone knows

...boot/vmlinuz inst.root=http://pxesrv.cmadams.net/pub/fedora/linux/releases/29/Server/x86_64/os/ inst.stage2=http://pxesrv.cmadams.net/pub/fedora/linux/releases/29/Server/x86_64/os/ repo=http://pxesrv.cmadams.net/pub/fedora/linux/releases/29/Everything/x86_64/os quiet BOOTIF=$net_default_mac initrdefi /pub/fedora/linux/releases/29/Server/x86_64/os/images/pxeboot/initrd.img } ******************** Hope this helps - at least show you some ways to do things. Here's my tftpboot setup script: ******************** #!/bin/bash # Set up a BIOS/UEFI PXE TFTP boot tree on a Fedora system set -e #...

Hello All Up until now we have been using standard PXE boot to do kick start installs of centos boxes. With recent machines however they come by default as EFI boot. We can set them to legacy but I would like to solve this before this option goes away. Just wondering if anyone has any experience setting up a net boot server that can be used to kickstart EFI machines? Thanks Grant

We have a working PXE setup. I've tried to adapt it to UEFI as per RHEL6 manual, but the client won't boot. Strangely, tcpdump shows that the client tries to download all files via tftp from the dhcp server rather than the tftp server (they are different). next-server is pointing to the tftp server. Any clues?