search for: initrd16

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 bytes long compressed, and 9...

...c64064178966b4' 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 --unrestricted $menuentry_id_option 'gnulinux-3.10.0-327.13.1.el7.x86_64-advanced-2a4bc862-eb7a-46b1-8979-d19c873dca3b'...

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 VHD image to ram disk and b...

...0 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: 5174 bytes Desc: S/MIME Cryptographic...

...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 right with normal boot setu...

...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 it has something to do...

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

...tility 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 list > Submissions to Syslinux at zyto...

.... 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 linux The cl...

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

...unately, 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_Fre >> eDOS_image >> >> >> _______________________________________________ >> Sy...

...e) != (LinuxFamily.RHEL, BootType.UEFI): return grub_config = g.read_file(self.config).decode('utf-8') write = False for old, new in [('linux16', 'linuxefi'), ('initrd16', 'initrdefi')]: if f'\t{old} ' in grub_config: debug(f'Replacing {old} with {new} in {self.config}') grub_config = grub_config.replace(f'\t{old} ', f'\t{new} ') write = True if write:...

Hi, I'm using libguestfs 1.42, When I run the following python3 commands on a rhel7.8: print(g.ls('/sys')) print(g.sh('ls /sys')) I get: [] block bus class dev devices 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

I had CentOS 6 installed on an MBR hard disk. I converted the disk to GPT (with UEFI) and installed CentOS 7 on a new partition. CentOS 7 itself seems to work properly. Grub from CentOS 7 automatically created an entry for CentOS 6, but I get an error if I try to boot CentOS 6. The menu entry is: menuentry 'CentOS release 6.10 (Final) (on /dev/sda7)' --class gnu-linux --class gnu