similar to: Boot kernel on a different drive/partition

I'm trying to get the head source so I can try the patch Ram mentioned in his email but without success. I have not used git/cogito before. The output below is from a cygwin session but I get similar results on Ubuntu as well (a bit more of the html ending with 'as an object to pull'). So whatever is wrong is common to my cygwin and Ubuntu setup. Thanks, Andrew $ cg clone -s

Hello, I cannot boot with GRUB and SYSLINUX from a logical partition on my USB drive. Here is the test setup: - 4GB Flash drive with the following partitions: sdb1 Primary fat32 ~ 800MB sdb2 Primary fat32 ~ 800MB sbd3 Primary fat32 ~ 800MB sdb4 Extended partition sdb5 Logical partition ~ 800MB sdb6 Logical partition ~ 600MB - Grub files were copied to /dev/sdb1/boot/grub (Stage

Hi, I have been attempting to set up a multi-boot USB stick (i.e. multiple bootable ISO images on the one stick) I have had good success by: - processing ISO with isohybrid (with "partok" flag) - dd'ing ISO to primary partitions on the USB stick (e.g /dev/sdc2, /dev/sdc3, /dev/sdc4) - installing grub to USB stick and configuring to chainload to these partitions To remove the limit

chain.c32 of SYSLINUX 3.82 does set the boot drive passed to the DL register to 0x80 and not to the boot drive (CD-drive). This can be a problem if you want to chainload grldr (grub4dos bootloader) from a CD and if you want to let grldr search for its menu.lst file on the CD. For more info: http://www.boot-land.net/forums/index.php?showtopic=8457 This 1 line patch fixes the issue (Thanks to

Hi It would be pretty useful to have syslinux in linux kernel format so it can be chainloaded easy and directly by other bootloaders such as grub4dos. related topics: http://www.boot-land.net/forums/index.php?showtopic=7013 http://www.boot-land.net/forums/index.php?s=&showtopic=6119&view=findpost&p=59236

Hi, I would like to chainload syslinux 3.86 after booting from pxelinux of syslinux 6.04 is it possible? I was checking chain.c32, but i was not very successful so far. on my tftproot? dir i has this: pxelinux.0 boot/isolinux/ pxelinux.cfg/ isolinux_3.86/pxelinux.0 isolinux_3.86/boot/isolinux/ isolinux_3.86/pxelinux.cfg/ Does anyone know how i can, after booting from the tftproot pxelinux.0

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

For reasons I won't get into, I need to use grub (not grub4dos, super grub, or any other variant) as multiboot loader on a USB thumb drive, but I also need some of the partitions to contain bootable content from syslinux-based ISOs. All of these syslinux partitions must be logical rather than primary partitions and they will not be the first partition on the drive. Porting the syslinux

Hi, i think i found the reason for the boot failure in the definition of Extended Boot Records. https://en.wikipedia.org/wiki/Extended_boot_record#Values "Starting sector = relative offset between this EBR sector and the first sector of the logical partition. Note: This is often the same value for each EBR on the same hard disk; usually 63 for Windows XP or older." So if

Hi! I am currently trying upgrade my bios pxe server with additional uefi support. My current using memtest86+ doesn't seem to support uefi, so I would have to use memtest86, as it supports this. But the memtest86 file itself is an *.efi file. When booting this one directly without syslinux, its working. But I want to launch it later from the syslinux menu. Can I chainload somehow another

I recently tried to install several distros on a usb stick, with the peculiarity of creating in it a GPT label rather than the usual dos label. Installed Grub2 using the parted bios_grub flag on a partition, I proceeded to copy several distros on the remaining partitions. Grub2 worked fine, chainloading syslinux on each of the partitions. Or rather it worked all fine until I reached the fifth

Hello list, any try the new memtest86 v3.2 with isolinux 3.11 cd and pxeboot? How is the proper way to chainload memtest86 I was tried: label memtest kernel memtest.bin but, nothing happens just a weird hang (my older versions of memtest hangs too). Anyway chainloading in a floppy image with memdisk on CD or pxeboot was fine but if I use memory to emulate a floppy I was not using this memory

Hi, I am having troubles with chainloading and hopefully someone can provide me with some guidance. Here's what I am trying to do: * the media is a USB key * I have created a GPT on it * I have created an EFI partition, where I have installed the EFI flavor of syslinux, the various .c32 files required for chainloading and the configuration file which tells syslinux what to chainload

Thanks for all the input everyone. I can understand the problem more clearly now. Didier Spaier wrote: > Sorry if this is a silly question: why not use a GUID partition > table instead of using logical partitions? Not a silly question, I had the same idea and had tried it out but it didn't work (same error msg). Ady Ady wrote: > The typical (modern) "MBR" supports 4

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

Inspired from a similar patch posted on grub-devel for Grub2 I immersed myself into the code of Grub Legacy and came up with this absurdedly simple patch to allow syslinux or other bootloaders residing in logical partition to be chainloaded from GRUB Legacy (0.9x). Hoping it to be of help, regards Fulvio Scapin -------------- next part -------------- A non-text attachment was scrubbed... Name:

> -----Original Message----- > Hi! > I am currently trying upgrade my bios pxe server with additional uefi support. > My current using memtest86+ doesn't seem to support uefi, so I would have to > use memtest86, as it supports this. > But the memtest86 file itself is an *.efi file. When booting this one directly > without syslinux, its working. > > But I want to

> No Syslinux variant can load items outside the current file system > space, yet. SYSLINUX can't load anything outside its current block > file system. ISOLINUX can't load anything outside its current ISO > image. PXELINUX can only load network files. Similar rules apply for > Syslinux EFI based on where it was loaded from. There's a patchset > that will be put

This bootloader is really nice, I'm getting closer to my goal ;) My CD currently boots the linux kernel with root fs somewhere on dev/hda, or you can select an initrd-based rescue/recovery partition on the CD. I would be more comfortable if I also could "chainload" or in any other way have "boot of hda MBR" as another option. Is this possible? How is it set up in

Hi, It is becoming a bad habit for big OEM vendors to sell computers & servers without floppy drives. Unfortunatly both Windows and Linux (RedHat) need a floppy drive to load storage drivers etc. during installation. This is what I was thinking: Use ISOLINUX and MEMDISK to load a floppy image of a driver disk into memory as a viritual floppy drive "A:"/"/dev/fda" And then