similar to: Bug report for SYSLINUX 3.53

Hi, I'm trying to boot Debian-Installer image from extlinux with chain.c32; i.e.: - I'm doing this from a loopback device (loop0) which later will be dumped to an USB stick. - GPT disklabel. - Partition 15 (loop0p15) contains extlinux info, and partition 12 contains Debian multi-arch installer image *dumped*[1], and its corresponding menu entry for extlinux is something like: LABEL

Hi, I''ve installed xen-2.0.5 from source on gentoo, but the xen dom0 kernel doesn''t find the root device: ############################# snip ###################################### Kernel panic: VFS: Unable to mount root fs on unknown-block (3,3) ############################# snap ###################################### grub.conf: ############################# snip

I have Windows 7 on /dev/sda and CentOS 6.4 on /dev/sdb. Here are the layouts: (parted) select /dev/sda Using /dev/sda (parted) print Model: ATA WDC WD10EZEX-00Z (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 374MB 373MB primary ntfs boot

3.75 is a bug fix release for 3.74. Changes in 3.75: * PXELINUX: fix the "keeppxe" option, which was broken in 3.74. * MEMDISK: correct the extraction of geometry information from the MBR of a hard disk image, again broken in 3.74. * extlinux(1) man page from Brian Pellin. * Simple menu: MENU SAVE is now controllable on a menu-by-menu

I have something very strange that occurred. After updating the kernel on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7 guest VMs will no longer boot... it just stops at the grub prompt (a second VM functions just fine). I have no idea why this problem occurred and have been unable to fix it. On google I have found several suggestions as to how to repair grub but so far

On Tue, Oct 20, 2015 at 1:08 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > >> Hello, >> >> We are experiencing a strange behaviour on an embedded system (i386 PC board). >> >> The structure of our disk is the following one : >> - A 2GB fat16 partition with DOS and syslinux >> - A 100GB Ext4 partition with Extlinux an several linux images

I never thought I'd say this, but I think it's easier to do this with GRUB 2. Anyway I did an installation to raid1's in CentOS 6's installer, which still uses GRUB legacy. I tested removing each of the two devices and it still boots. These are the commands in its log: : Running... ['/sbin/grub-install', '--just-copy'] : Running... ['/sbin/grub',

Well, here it is. This is a historic Syslinux release -- it's the first one in 15 years in which the majority of the work was not done by myself; mostly because of the *huge* effort Erwan and Pierre have put in on HDT. I also want to give a special thank you to my new(ish) employer, Intel Corporation, for letting me continue to work on Syslinux. :) From here, onward and upward. I

On 06/06/2015 13:14, Stoppa, Igor wrote: > On 6 June 2015 at 14:03, Didier Spaier via Syslinux <syslinux at zytor.com> wrote: >> >> >> On 06/06/2015 12:19, Stoppa, Igor via Syslinux wrote: >> >>> So I'd like to not put all the kernels/initrds in it, because when I >>> update one of the OSes, I would also have to update the corresponding

----- Forwarded Message ---- From: Geert Stappers <stappers at stappers.nl> To: syslinux at zytor.com Sent: Tuesday, November 14, 2006 5:07:55 PM Subject: Re: [syslinux] Localboot option in syslinux and extlinux Op 14-11-2006 om 21:25 schreef n schembr: > > First, my problems are on the edge of accepted use of most products. > I'm working in an aria that the average user will

Thanks for responses. I use GRUB as my bootloader in my hard disk now. I have a Windows in sda1, Ubuntu in sda3. If I want to install extlinux to boot Ubuntu, should I follow the steps below? 1. in Ubuntu, go to extlinux folder, run command ./extlinux --install /boot 2. create an extlinux.conf in/boot 3. cd ../mbr 4. cat mbr.bin > /dev/sda (or use dd if=mbr.bin of=/dev/sda bs=404 count=1)

Syslinux 3.85 is a bug fix and minor new feature release. The biggest change is undoubtedly that gPXELINUX is now considered feature complete, and should be able to be a drop-in for PXELINUX for all uses. Special thanks to Intel Corporation, my current employer, for their support for my Syslinux work. Changes in 3.85: * gPXELINUX: updated to gPXE 1.0.0. gPXELINUX can now do NBP

On 6 June 2015 at 14:03, Didier Spaier via Syslinux <syslinux at zytor.com> wrote: > > > On 06/06/2015 12:19, Stoppa, Igor via Syslinux wrote: > >> So I'd like to not put all the kernels/initrds in it, because when I >> update one of the OSes, I would also have to update the corresponding >> kernel in the EFI partition. > > > IIRC this is not

Hello, We are experiencing a strange behaviour on an embedded system (i386 PC board). The structure of our disk is the following one : - A 2GB fat16 partition with DOS and syslinux - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram - A swap partition The system boot on syslinux to choose among Dos and Linux boot using chain. When Linux is chosen, syslinux chains to

OK, this is probably long, and your answer will surely make me slap my forehead really hard... please help me understand what goes on. I intend to install CentOS 5.1 afresh over software RAID level 1. SATA drives are in AHCI mode. I follow basically [1] though I have made some mistakes as will be explained. AFAIK GRUB does not boot off LVM, so I: 1. Build a 100MB RAID-type partition on each

> Hello, > > We are experiencing a strange behaviour on an embedded system (i386 PC board). > > The structure of our disk is the following one : > - A 2GB fat16 partition with DOS and syslinux > - A 100GB Ext4 partition with Extlinux an several linux images to boot on ram > - A swap partition > > The system boot on syslinux to choose among Dos and Linux boot using

Hello everyone, I have just released SYSLINUX 3.70, which is the first version which includes gPXE for support of non-TFTP network scripts, as well as a large number of other enhancments. gPXE support is still somewhat experimental - in particular it still doesn't support chaining other NBPs. Very special thanks to: - rPath, Inc, my employer, for the uncountable hours I've spent

On Thu, Aug 6, 2015 at 2:57 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: > On 8/6/2015 4:39 PM, Chris Murphy wrote: >> >> On Thu, Aug 6, 2015 at 2:29 PM, Bowie Bailey <Bowie_Bailey at buc.com> wrote: >>> >>> On 8/6/2015 4:21 PM, Chris Murphy wrote: >>>> >>>> On Thu, Aug 6, 2015 at 2:08 PM, Bowie Bailey <Bowie_Bailey at

This is 100% functionally equivalent to 3.54-pre1, with only a few minor documentation changes. Changes in 3.54: * Add "menu separator", "menu indent", "menu disabled" (see README.menu). * vesamenu: fix handing of VESA modes with noncontiguous memory buffers. In particular, Qemu/KVM sets up such a mode when Cirrus

Syslinux 4.02 is a bug fix release, but also adds an experimental new Win64 installer (syslinux64.exe), extends the new syslinux installer CLI to all the installers. Changes in 4.02: * SYSLINUX: correctly handle the case where the -d option is specified with a non-absolute path, i.e. "syslinux -d syslinux" instead of "syslinux -d /syslinux".