search for: rdsoftware

On Fri, Aug 30, 2019 at 12:15 PM Erik Rull <erik.rull at rdsoftware.de> wrote: > Hello Greg, > > thanks a lot - I will try out your script next week. > I jut went through the script - there is a line containing: > bls1 include > > I would carefully assume that this line is only valid when patching > syslinux, > correct? What will happ...

...440 bytes from the drive into memory and copy the memory address that it was loaded to a CPU register. From there, it is up to that 440 byte program to decipher the partition table. If you use syslinux's gptmbr.bin, you should be fine. On Sat, Aug 31, 2019 at 4:47 AM Erik Rull <erik.rull at rdsoftware.de> wrote: > Gregory Bartholomew wrote: > > That is correct. "bls1 include" would cause errors without the patch. > The main > > parts of the script that would be relevant to you would be the parts > that create > > the partition, set its type codes, write t...

I just created something very similar for one of my own projects. I have a disk image that you can "dd" onto a hard drive or USB drive and a bash script demonstrating how it was done here: https://www.syslinux.org/archives/2019-July/026476.html You don't actually need the patch for the dual BIOS/UEFI support. The patch in the above link is just to enable the reading of config

Gregory Bartholomew wrote: > That is correct. "bls1 include" would cause errors without the patch. The main > parts of the script that would be relevant to you would be the parts that create > the partition, set its type codes, write the first-stage boot loader to the > first 440 bytes of the disk, and lay out the file system (e.g. it demonstrates > that a single

Hello Greg, thanks a lot - I will try out your script next week. I jut went through the script - there is a line containing: bls1 include I would carefully assume that this line is only valid when patching syslinux, correct? What will happen if this is read by a non-patched syslinux? Will it cause errors or will it simply be ignored? Best regards, Erik Gregory Bartholomew wrote: > I just

Hi all, I did my first steps on syslinux 6.03 with EFI... I prepared the disk with GPT, EFI system partition and formatted it FAT32. I added the files to EFI/BOOT including the syslinux libraries and syslinux.cfg The system starts booting, loads kernel and initrd (I see the loading output on the screen), but then the system resets and the loop restarts (infinitely). I took the same

Hi Ady, Ady Ady via Syslinux wrote: > > To me, it is not so clear what exactly is your goal. sorry for not being detailed enough. > Do you want to build an image for an internal HDD that could be capable > of booting in both, BIOS mode and UEFI mode? Yes. This would make us independent from the BIOS boot mode. > Or, is this for a portable (USB) device? Maybe - would be nice

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave

Thanks for the hints - I have NOT CONFIG_EFI enabled - do I need this actually? I do not know which variables I need to boot... The kernel APPEND parameters are sufficient for me... And the relocatable config is set already. .. I enabled the EFI kernel config parts - no change... the console prints: Booting System... Loading linux... ok Loading iramfs.gz...ok [then reboot] My syslinux.cfg is