search for: initrams

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

On 09/05/2013 01:55 AM, Gene Cumm wrote: > On Wed, Sep 4, 2013 at 2:34 PM, Piotr Karbowski > <piotr.karbowski at gmail.com> wrote: > >> With syslinux (extlinux) it will jump to last INCLUDE'ed menu always, with >> 5.01 it will display list of elements, then allow me to choose which one I >> want to enter. >> >> Even if the include part contain a

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

For the sake of the discussion. Screenshots not included due size limit. ----- Forwarded message from syslinux-owner at zytor.com ----- Date: Sun, 05 Apr 2015 17:09:50 -0700 from: syslinux-owner at zytor.com To: syslinux-owner at zytor.com Subject: Syslinux post from piranna at gmail.com requires approval List: Syslinux at zytor.com From: piranna at gmail.com Subject: Re:

Just to be clear on the topic, I decided to do some tests from scratch on my MacBook Pro. This are the steps and results: 1. I've pick my USB pendrive and zeroed 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

I'm developing my own Linux-kernel OS (https://github.com/NodeOS/NodeOS) and I have been able to build a live ISO using IsoHybrid. Point is, it doesn't work on my MacBook Pro (Quad-core, 2.66GHz, 8GB), only on BIOS-based PCs. rEFInd show a new "Legacy OS" entry for the pendrive, but after some seconds it shows the "Not found Operating System -- Insert boot disk and press any

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

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

> 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

Hi, OK. I build syslinux-6.02-pre6 from https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz on a Debian jessie/sid system (with gnu-efi_3.0u+debian-2 from experimental): root at jessie: ~# cd /tmp root at jessie:/tmp# wget https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.02/syslinux-6.02-pre6.tar.gz root at jessie:/tmp# tar xfz

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

> The third boot image is HFS+, not FAT. > I understand this is for pre-EFI Macs. Apple started usinf EFI when it switched to Intel x86 CPUs, previous to this ones it was using OpenFirmware in their PowerPC "new world" machines (IBM PowerPC G4 & G5). > Try a Debian amd64 ISO, e.g.: >

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

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

Hi, i wrote: > > http://mjg59.dreamwidth.org/11285.html piranna at gmail.com wrote: > There it says about creating a third El Torito image only for Macs, > since old ones could fail and this could be the problem I'm having. The third boot image is HFS+, not FAT. I understand this is for pre-EFI Macs. Try a Debian amd64 ISO, e.g.:

Subject of Hint: How to create a Bootable Live CD/DVD from your Linux From Scratch (LFS) build Good day from Singapore, I am Mr. Turritopsis Dohrnii Teo En Ming, based in Singapore. I have recently *successfully* created my own custom Linux distribution called Teo En Ming Linux 2020.03 (FINAL), which is based on Linux From Scratch 20200302-systemd book and Linux Kernel 5.5.7, on 12 March

I'm having issues with the ifcpu[64].c32 modules. I am building a menu system (as opposed to the command line only options I was previously using) to make it easier for my boss to use PXE. I discovered the modules for auto detecting the CPU and thought hey, that's great! However, I'm having an issue where when I select to boot say System Rescue CD, it drops me to the command line