search for: initram

Hello, Long story short, example config: ### cut UI vesamenu.c32 MENU TITLE Multiboot USB MENU BACKGROUND #00000000 MENU COLOR sel 7;37;40 #e0ffffff #20ffffff all MENU COLOR unsel 37;44 #50ffffff #a0000000 std MENU COLOR tabmsg 31;40 #30ffffff #00000000 std MENU BEGIN MENU TITLE System Rescue CD 2.4.1 INCLUDE sysrcd-2.4.1.conf MENU END MENU BEGIN MENU TITLE

...0 none MENU color hotsel 1;7;37;40 #FF000000 #FFC0C0C0 all MENU color tabmsg 1;31;40 #FFFFFF00 #00000000 std MENU color help 1;31;40 #FFFFFFFF #00000000 none LABEL rescuecd_std MENU LABEL 1) SystemRescueCd: default boot options LINUX /sysrcd-2.4.1/rescuecd INITRD /sysrcd-2.4.1/initram.igz APPEND subdir=sysrcd-2.4.1 scandelay=1 TEXT HELP Boot standard 32bit kernel with default options (should always work) You should use this entry if you don't know which one to use ENDTEXT LABEL rescuecd_docache MENU LABEL 2) SystemRescueCd: all files cached to memory (docache)...

Hi, Curt Brune wrote: > At the risk of contributing to the 'urban legends' and the 'salads' I apologize to all communities who hand out correct info. :)) > http://lukeluo.blogspot.com/2013/06/grub-how-to-2-make-boot-able-iso-with.html Well, the excursion on CD-DA is off topic and i would describe many aspects in different terms. Nice to see that at least one person read

...MBR partition scheme with fdisk and a VFAT partition of 32MB. > Later I dd'd the file /usr/lib/syslinux/mbr/mbr.bin from SysLinux 6.03 > and set the boot flag on the partition, so it could be able to boot > SysLinux. > > 2. Copied all the files of my IsoHybrid image: > > - initram.gz > - isolinux.bin > - kernel.img > - ldlinux.c32 > - syslinux.cfg > > Obviously this would be booted by SysLinux MBR, so I've changed > isolinux.bin for syslinux.c32 (from /usr/lib/syslinux/modules/bios). > Now rEFInd show a new "Legacy OS" entry pointing to...

...it, and after that created a new MBR partition scheme with fdisk and a VFAT partition of 32MB. Later I dd'd the file /usr/lib/syslinux/mbr/mbr.bin from SysLinux 6.03 and set the boot flag on the partition, so it could be able to boot SysLinux. 2. Copied all the files of my IsoHybrid image: - initram.gz - isolinux.bin - kernel.img - ldlinux.c32 - syslinux.cfg Obviously this would be booted by SysLinux MBR, so I've changed isolinux.bin for syslinux.c32 (from /usr/lib/syslinux/modules/bios). Now rEFInd show a new "Legacy OS" entry pointing to the USB "whole device". Now I...

...ge. After that, I've tried with making the IsoHybrid EFI capable. I've followed the instructions at http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI and rEFInd show both the "Legacy OS" entry and another one for EFI. This last one goes to SysLinux and load the kernel and the initramfs, but after that it does nothing. What could I be doing wrong? If it's of info, I'm using SysLinux 6.03 from the Ubuntu Mate 15.04 packages and the syslinux.cfg config file. I have a plain filesystem structure both on the ISO partition and the EFI image, and they both have the same Linux...

Hi I have a weird early boot bug that most likely happens because of interaction between syslinux (6.03pre18), btrfs and initram generated by Linux Arch installer. For some reason boot fails. Syslinux prints some information and returns back to the menu. Unfortunately it clears all the messages from screen. I really want to know what boot process prints there. Looking at com32/elflink/ldlinux/execute.c (I believe it is wh...

Gene, I'm lurking on this issue. Just in general it's fascinating because I basically use syslinux in a monkey-see-monkey do manner. Can you explain why you used the menu entries that way? What they actually do? You mentioned logging... How is the enabled/configured? Inquiring minds want to know and links to docs will do :) On 10/03/2017 03:30 AM, Gene Cumm via Syslinux wrote: >

On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > alex lupu via Syslinux <syslinux at zytor.com> writes: > > ?>? > Obviously it would work IF I moved the vmlinuz > > and initramfs ?files from /dev/sdd2 to /dev/sdd1. > > > > I figured that would probably be considered non-standard Arch > ? ...? > > The standard solution is to have your boot partition (sdd1) mounted as > /boot in your Linux system, and then your kernel and initramfs files are > au...

> Anybody show me a pure SYSLINUX isohybrid ISO that boots via EFI > and i will be able to dissect it and hopefully derive knowledge > for the wiki. Well, besides the fact that after loading the kernel and the initram it didn't started the boot process (don't know why), this is what I achieved by using a disk image with syslinux.efi... :-) -- "Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton de sitios diferentes, simplemente escribe un sistema operativo Unix." ? Lin...

...0 TOTALTIMEOUT 6000 ONTIMEOUT local LABEL local MENU LABEL (local) MENU DEFAULT LOCALBOOT 0 LABEL Memtest86+ 4.20 MENU LABEL Memtest86+ 4.20 KERNEL memtest/420/memtest LABEL Sysresccd x86-64 3.7.0 MENU LABEL Sysresccd x86-64 3.7.0 KERNEL sysresccd/370/altker64 append initrd=sysresccd/370/initram.igz dodhcp=eth0 nonm nodmraid nomdadm scandelay=3 vga=791 netboot=http://10.82.0.1/images/sysresccd/370/sysrcd.dat (This cfg was working, excepted the Memtest86+ part, with syslinux-5.10) Build logs and network capture can be found here: https://www.dropbox.com/s/ekoth8nqdejk5iz/syslinux-6.02_p...

On Wed, Oct 4, 2017 at 11:10 AM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > FWIW, the _need_ to use linux.c32 is becoming more common (in the sense > that other loading methods are not always capable of loading > newer/current kernels+initrams+additional_files, considering their > sizes). Unfortunately, only a minority of users seem to be aware of > Syslinux's syntax and modules, while the Syslinux-related packages are, > generally speaking and IMO, not reaching the level of > maintenance/support that common users seem t...

...nce I found the IsoHybrid images I decided to combine both in just a CD ISO to don't confuse users about what one to download. Maybe I could deprecate the CDs at all and publish only "native" USB disk images instead, isn't it? >> SysLinux.efi loads the Linux kernel and its initramfs file but doesn't >> boot... :-/ As I put in the initial message I'm not using the >> /efi/boot/bootx64.efi path but instead just copied all files in the >> root directory of the FAT disk image, but since it already load the >> kernel and the initramfs maybe the can...

Hi all, I encountered a tricky problem. I am using ovs+DPDK on the host side to build the virtual network, so on the VM side , the virtio_net.ko module is used to drive the nic. But VM always freezes while insmod virtio_net.ko (I found virtio_net.ko is located in initrams.img by defualt, so I had to delete all virtio modules from initramfs.img and insmod then one by one after system is loaded to confirm that). After such freeze, virsh reset can not recover it due to cannot acquire state change lock (held by remoteDispatchDomainReset) so I have to use virsh destroy...

I have a need to have a live Linux (Debian or sysrescued ) to boot off a hard-drive so that the hard-drive ends up umounted after boot. (for running partimage ). I've gone down the memdisk iso route and read about the issues there - I've seen a way to do this by mounting over nfs (messy) - but I want to do this without the network. I'm thinking that there should be a way to loop

alex lupu <alupu01 at gmail.com> writes: > On Tue, Mar 17, 2015 at 4:16 AM, Ferenc Wagner <wferi at niif.hu> wrote: > >> alex lupu via Syslinux <syslinux at zytor.com> writes: >> >>?>? Obviously it would work IF I moved the vmlinuz >>> and initramfs ?files from /dev/sdd2 to /dev/sdd1. >>> >>> I figured that would probably be considered non-standard Arch >> >> The standard solution is to have your boot partition (sdd1) mounted as >> /boot in your Linux system, and then your kernel and initramfs files are &g...

...chain.c32, you can load a boot sector (MBR or VBR) located on another device. Since the list of files located in your boot stick did not include chain.c32, my assumption (and not only mine, if you carefully read some of the prior replies) is that the relevant "old" files (e.g. kernel, initrams, etc.) were also located in the same old (stolen) boot stick (while your root partition might have been located on a different device). But, since you have not provided any relevant information (not even the content of your old syslinux.cfg nor how exactly you were "editing" your bo...

...Hybrid disk image, but when dd'd to the USB pendrive, I meant a disk-only image. No ISO, no hybrid. Just an ESP and an operating system partition. Created by partition editor, filesystem formatter, and populated with files by you and SYSLINUX. > SysLinux.efi loads the Linux kernel and its initramfs file but doesn't > boot... :-/ As I put in the initial message I'm not using the > /efi/boot/bootx64.efi path but instead just copied all files in the > root directory of the FAT disk image, but since it already load the > kernel and the initramfs maybe the canonical path is n...

...otable Live CD/DVD" >id_label mkdir -pv mnt_init/{bin,boot} cp -v id_label mnt_init/boot cp -v /bin/busybox mnt_init/bin cp init.sh mnt_init/init sed -i "s/<ARCH>/$(uname -m)/g" mnt_init/init chmod +x mnt_init/init pushd mnt_init find . | ./bin/busybox cpio -o -H newc -F ../initramfs.cpio popd gzip -9 initramfs.cpio rm -rf mnt_init mv initramfs.cpio.gz /boot/initram.fs mv id_label /boot #------------ Cut and Paste end Step 6) Make a squashed version of your LFS. This step should be done on the HOST (not inside chroot). Do any needed cleanup and final tweaking of y...

...TEXT HELP * Boots System Rescue 3.4.2 ENDTEXT KERNEL ifcpu.c32 APPEND 64 -- rescuecd64 -- rescuecd32 LABEL rescuecd32 MENU LABEL System Rescue 32-bit MENU INDENT 4 MENU HIDE TEXT HELP * Boots System Rescue 3.4.2 in 32-bit ENDTEXT KERNEL http://****/rescue32 INITRD http://****/initram.igz APPEND rescue32 nomodeset vga=791 scandelay=1 setkmap=us netboot=http://****/sysrcd.dat LABEL rescuecd64 MENU LABEL System Rescue 64-bit MENU INDENT 4 MENU HIDE TEXT HELP * Boots System Rescue 3.4.2 in 64-bit ENDTEXT KERNEL http://****/rescue64 INITRD http://****/initram.igz...