search for: linux16

...n'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.mkdir_p('/sys/firmware/efi') - but that created a fake dir in my chrooted environment, where grub2-mkconfig somehow was inspecting the real /sys as demonstrated in the above 'ls' example. Any ideas on why sh jailbreaks the chroot? is /sys set...

Hello, I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: menuentry 'boot ISO image' { linux16 /memdisk iso initrd16 /my-image.iso.gz } When selected, this starts to boot and then fails with: Ramdisk at 0x37979000, length 0x0033b298 gzip image: decompressed addr 0x7f7f7000, len 0x00008f58: failed Decompression error: output buffer overrun FWIW, my-image.iso.gz is 3388055 by...

...re_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint='mduuid/84bbf877f8bd0f7aa0c64064178966b4' 2206a439-5490-46d0-8d5e-9da8962924df else search --no-floppy --fs-uuid --set=root 2206a439-5490-46d0-8d5e-9da8962924df fi linux16 /vmlinuz-3.10.0-693.17.1.el7.x86_64 root=/dev/md/2 ro nomodeset rd.auto=1 crashkernel=auto LANG=en_US.UTF-8 initrd16 /initramfs-3.10.0-693.17.1.el7.x86_64.img } menuentry 'CentOS Linux (3.10.0-693.11.6.el7.x86_64) 7 (Core)' --class centos --class gnu-linux --class gnu --class os --u...

...[1] to create a floppy image of 20 MB, so that the vendor update utility fits. Unfortunately, FreeDOS does not load, and it seems to hang loading the FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue is memdisk related? It?s started from GRUB with the commands below. linux16 /boot/memdisk floppy initrd16 /boot/freedos.img boot Kind regards, Paul [1]: https://wiki.gentoo.org/wiki/BIOS_Update#Create_a_custom_FreeDOS_image -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 517...

...; { echo `hello` insmod lvm insmod part_msdos insmod jfs insmod memdisk iso set root='(ssd-testing)' search --no-floppy --fs-uuid --set f9ae292b-b6a9-4f70-af7c-31987e766d37 # echo 'Loading memtest-Plus' linux16 memdisk initrd16 memtest-plus/memtest86+-4.20.iso # echo 'Loading initial ramdisk...' } I've done a lot of google searches and even downloaded the source trying to get a glimmer of the syntax - so far with out joy... I've verified the set root and lvm part is r...

I'll try that...I was using instructions I found on the internet for single-user/maintenance mode.?? From the grub screen you enter 'e' and modify the linux16 line...etc. Okay, I'll try that next. Thanks Simon! On 5/13/2020 7:28 AM, Simon Matter via CentOS wrote: > Hi, > >> Yeah, I tried that but ran into a problem.? It came up fine in >> single-user/maintenance mode. ? The mount command shows all of the >> mounted file sys...

I have tried 4 time unsuccessfully to install Xen 4 on Ubuntu Lucid (10.4) 64 bit version using the tutorial at http://bderzhavets.wordpress.com/2010/04/24/set-up-ubuntu-10-04-server-pv-domu-at-xen-4-0-dom0-pvops-2-6-32-10-kernel-dom0-on-top-of-ubuntu-10-04-server/ on a Lenovo thinkcentre workstation. When I boot I get a kernel panic. If I boot the Linux kernel that I compiled using the

...er/hdz<<EOT n p 1 t 6 a 1 w EOT kpartx -a /dev/mapper/hdz mkdosfs /dev/mapper/hdz1 Then I put a dosfloppy image and memdisk on the image: mount /dev/mapper/hdz1 /mnt/ mkdir -p /mnt/boot/grub cp dos622.IMA /mnt/boot/ cp /usr/lib/syslinux/memdisk /mnt/boot /mnt/boot/grub/grub.cfg contains: linux16 /boot/memdisk initrd16 /boot/dos622.IMA boot and I install grub: grub-install --root-directory=/mnt /dev/dm-0 This works perfectly on a virtualbox installation, I get a dos environment with a C: disk. On a live system it works till till the boot of the dos floppy. The machine resets. I believe...

...nuxefi/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 pretty unlikely that running grub can work. The libguestfs > appliance is sufficiently different from how the guest boots that > things like BIOS mappings are not related, and libguestfs doesn't use > EFI at all. > > There's unfortunately no goo...

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703586 Ideas how to move this forward? Debugging techniques? I''m guessing that it''s specific to my hardware, since I''m not seeing anyone else complaining. Anyone else succeed in doing this on an EliteBook?

> Hello, > > I'm having a problem booting a compressed ISO image using memdisk via grub2 (version 2.02). The entry in my grub.cfg looks like: > > menuentry 'boot ISO image' { > linux16 /memdisk iso > initrd16 /my-image.iso.gz > } > > When selected, this starts to boot and then fails with: > > Ramdisk at 0x37979000, length 0x0033b298 > gzip image: decompressed addr 0x7f7f7000, len 0x00008f58: failed > Decompression error: output buffer over...

Hi all, My computer is booted with UEFI and Grub2. I tried to load VHD files with memdisk and boot from there. memdisk is extracted from 'bios/memdisk' in syslinux 6.03 zip file. In Grub2, I executed: linux16 /memdisk harddisk initrd16 /Win10.vhd Then the system frozen at 'initrd16' line. The VHD file is 8192MB, fixed image. I also tried to boot a small floppy disk (FreeDOS), and no error reported from Grub2 or memdisk side. Is there anything wrong with my steps? How to properly load an fixed...

...of 20 MB, so that the vendor update utility fits. > > Unfortunately, FreeDOS does not load, and it seems to hang loading the > FreeDOS kernel. The original FreeDOS image boots. Do you know if that issue > is memdisk related? It?s started from GRUB with the commands below. > > linux16 /boot/memdisk floppy > initrd16 /boot/freedos.img > boot > > > Kind regards, > > Paul > > > [1]: https://wiki.gentoo.org/wiki/BIOS_Update#Create_a_custom_ > FreeDOS_image > > > _______________________________________________ > Syslinux mailing li...

...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 pretty unlikely that running grub can work. The libguestfs appliance is sufficiently different from how the guest boots that things like BIOS mappings are not related, and libguestfs doesn't use EFI at all. There's unfortunately no good way to run grub. syslinux/extl...

On 07/03/2017 02:41 PM, Gordon Messmer wrote: > On 07/03/2017 05:07 AM, Chris Olson wrote: >> A progress >> bar at the bottom of the start-up screen never reaches completion. > > > Press "alt+d" on the keyboard to disable the graphical (or text) > progress bar and view the console output of the startup sequence. Is there a place (configuration file) where

...xt) >> progress bar and view the console output of the startup sequence. Or just hit <esc> and after the low-level, it'll display. > Is there a place (configuration file) where this can be made the default? Edit the menu before booting. You'll want to put your parms on the linux16 line. Servers should be runlevel 3 anyway. And it's always annoyed me that a server install puts rhgb quiet in grub. mark

...ly 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 commands. The fix is to add the linux module to the PXE config file, insmod linu...

...(say iommu support). I have been told before to avoid using grub2-mkconfig because it would apply the changes to all currently available (to boot from) boot kernels. Instead, I should edit just the latest kernel entry in the grub.cfg file, adding the option to the line that used to start with "linux16" in centos6. This way, if it went boink, all I had to do is reboot, pick another kernel from the grub menu and off I went. And, it seems that every future kernel upgrade would incorporate this change. Looking at a centos7.7 setup, I take the equivalent line in /boot/grub/grub.conf is kernel...

Hi I would like to start a iso from my USB-Pendrive so I got a Hiren BootCD amd PartedMagic iso + GRUB 2 (1.98~20100115-1) on my USB-Pendrive. My problem it take up to 30sec until the ISO is booted my menu entry: linux16 /memdisk iso initrd16 /boot/iso/pmagic.iso Thanks for any hints M. Simon _________________________________________________________________ http://redirect.gimas.net/?n=M1003xIMVideochat2 Treffe Freunde im Messenger Videochat!

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