similar to: Syslinux 6.03, kernel not relocatable.

Displaying 20 results from an estimated 1000 matches similar to: "Syslinux 6.03, kernel not relocatable."

2014 Nov 17
0
Syslinux 6.03, kernel not relocatable.
On 16/11/2014 18:33, Didier Spaier wrote: > Hi all, > > I have requested tests of this USB installer: > http://slint.fr/testing/slint64-14.1_syslinux.6.03.img > in both BIOS and UEFI modes. > > A test in UEFI mode: > http://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 > > leaded to this message: >
2014 Nov 17
2
Syslinux 6.03, kernel not relocatable.
> > On 16/11/2014 18:33, Didier Spaier wrote: > > Hi all, > > > > I have requested tests of this USB installer: > > http://slint.fr/testing/slint64-14.1_syslinux.6.03.img > > in both BIOS and UEFI modes. > > > > A test in UEFI mode: > >
2016 Apr 02
4
Changes to get CD to boot on EFI System.
Hi, Ady wrote: > I very much doubt that there is any ISO image, publicly > available or not, that can boot optical media in UEFI mode by means of > Syslinux for EFI as of today. I hope this status will change at some > point. > [...] > I doubt that syslinux.efi (renamed as "EFI/BOOT/BOOT<arch>.EFI") > is capable of booting optical media in UEFI mode at
2016 Apr 02
2
Changes to get CD to boot on EFI System.
Hi, Didier Spaier wrote: > http://slint.fr/testing/slint64-14.1_syslinux.6.03/slint64-14.1_syslinux.6.03.img This looks like the content of an EFI system partition. Exactly what i need for experiments. Thanks a lot. (slint64-current-goofiboot.iso and slint64-current-efi-stub.iso were already in my collection.) It boots to "Slint installer for Slackware64-14.1" by:
2014 Nov 10
4
Boot fails in a VMware player VM - syslinux 6.03
Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to
2014 Nov 10
0
Boot fails in a VMware player VM - syslinux 6.03
Hi, i downloaded http://slint.fr/misc/testing/slint64-14.1_syslinux.6.03.iso Inspection by xorriso-1.3.8: xorriso -indev slint64-14.1_syslinux.6.03.iso \ -report_el_torito plain \ -report_system_area plain yields El Torito catalog : 46 1 El Torito cat path : /isolinux/isolinux.boot El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El
2014 Nov 11
0
Boot fails in a VMware player VM - syslinux 6.03
> > You are probably imitating / following some procedure used by > > Slackware to create EFI-compatible ISO images. The problem, as > > mentioned in a recent email this last week, is the particularities of > > the documents regarding, in this case, grub2 as EFI bootloader (as > > oppose to documents covering EFI bootloaders in general and clearly > >
2014 Nov 10
2
Boot fails in a VMware player VM - syslinux 6.03
On 10/11/2014 04:02, Ady wrote: > >> Hi there, >> >> I failed to boot an installer in a VMware player (Version6.0.3 >> build-1895310) >> using syslinux 6.03, be it off an hybrid ISO image and an USB stick. >> >> Booting succeeds if the VM is set to use a BIOS firmware with both media, >> but fails using an efi firmware. >>
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi, On 29/07/2014 21:34, Thomas Schmitt wrote: > Nevertheless i advise Didier to simply try with 0xef rather than Mac. At least the ISO will then have MBR, GPT and APM entries for the file macboot.img. I did that, and also tried the xorriso command you posted. I uploaded both ISO images on http://slint.fr/misc/MacBoot resp. renamed: slint64-14.1-Thomas_mkisofs.iso
2014 Jul 29
2
isohybrid: slint64-14.1.iso: unable to find mac efi image
HI, In http://slint.fr/misc/MacBoot/ you'll find all context information. All files referenced here are stored there. Long story short: once dd-ed on an USB stick the ISO image can boot on a BIOS or EFI machine, but I want it to be able to boot on most x86_64 Macs with an EFI firmware. Unfortunately I get the error message: isohybrid: slint64-14.1.iso: unable to find mac efi image The
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi, > I don't understand why you say "*But* the El Torito...". I don't see > a difference with what the mkisofs manual says. The manual announces "Mac" for Apple Mac. The program obviously writes Platform Id 1 in this case. The El Torito specs say "Platform ID 0 = 80x86 1=Power PC 2=Mac". In the sum this does not match. A bug in mkisofs would be the
2016 Mar 25
2
Changes to get CD to boot on EFI System.
Hi, H. Peter Anvin wrote: > Look for a "legacy boot" option; otherwise you need the CD-ROM to have > the EFI version of Syslinux or another bootloader on it The "another bootloader" is clear to me. But what are the prescriptions for preparing a SYSLINUX EFI System Partition that boots out of a CD ? (Those built according to
2014 Jul 29
3
isohybrid: slint64-14.1.iso: unable to find mac efi image
> Hi, > > Ady wrote: > > cdrtools.sourceforge.net/private/man/cdrtools-3.01axx/mkisofs.8.html > > Mac Boot entries for the Apple Mac platform. > > Interesting feature. But the El Torito specs of Phoenix and > IBM of 1994 state that "Mac" would be Platform Id 2. > http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf > Page
2014 Nov 17
0
Syslinux 6.03, kernel not relocatable.
On 17/11/2014 08:45, Ady wrote: > The Slackware Documentation Project wiki also mentions > "CONFIG_RELOCATABLE" in: > <http://docs.slackware.com/howtos:slackware_admin:linux_kernel_options_f > or_uefi_and_elilo> I've seen this page a while age (of course... I'm a Slackware user) and now remember that I was a bit surprised because the kernel shipped in DVD
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi, > Unfortunately I get the error message: > isohybrid: slint64-14.1.iso: unable to find mac efi image This is probably due to El Torito Platform id "Mac" in -eltorito-alt-boot -no-emul-boot -eltorito-platform Mac \ -eltorito-boot isolinux/macboot.img \ This caused in the image http://slint.fr/misc/MacBoot/slint64-14.1.iso platform id 1 with the third image. (I would
2016 Apr 02
3
Changes to get CD to boot on EFI System.
Hi, Ady wrote: > http://www.syslinux.org/archives/2015-October/024526.html I still have it in my mailbox: ADY4UEFI.IMG in ADY4UEFI.ZIP. The test results are the same as with Didier's partition image. Wrapped in an ISO and presented as -cdrom it reboots in cycles. Presented as -hda it boots as naked disk image and as part of a GPT enhanced ISO 9660. > the wiki page needs
2016 Jun 01
3
About 4.xx and 6.xx. WAS: Making a 6.04
> On 01/06/2016 00:28, H. Peter Anvin via Syslinux wrote: > > There seem to be a bunch of bug fixes in the 6.04 branch that people > > really need. Do we know of any current regressions? Otherwise we > > really ought to just push the button... > > I am a user of syslinux 4.0.7 to boot installers on BIOS aka Legacy. > > Knowing that 4.0.7 has been released on
2013 Nov 01
2
isohybrid fails with: seek error - 3
On 01/11/2013 05:36, Ady wrote: > >> That is with syslinux 4.05 on Slackware-14.0: >> >> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >> catalogue offset: 561 >> ve[0]: 1, cs: 1 >> ve[1]: 0, cs: 1 >> ve[2]: 0, cs: 1 >> ve[3]: 0, cs: 1 >> ve[4]: 0, cs: 1 >> ve[5]: 0, cs: 1 >> ve[6]: 0, cs: 1 >> ve[7]: 0, cs: 1
2014 Jul 29
0
isohybrid: slint64-14.1.iso: unable to find mac efi image
Hi, Didier Spaier: > I uploaded both ISO images on http://slint.fr/misc/MacBoot A good opportunity to brag with xorriso's boot inspection features (since xorriso-1.3.8): xorriso -indev slint64-14.1-Thomas_mkisofs.iso \ -report_el_torito plain \ -report_system_area plain yields (block size is 2048): El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz
2020 Jun 18
3
[PATCH] efi/main: add retry to exit_boot()
Hi, Le 18/06/2020 ? 22:24, Tom Huibregtse via Syslinux a ?crit?: > I am a UEFI/BIOS developer. We UEFI PXE boot dozens of times per night. We have run into this error more than a couple of times. We have also done thousands of UEFI PXE boots with debug statements to prove that the patch works. <snip> As far as I can tell, the development of Syslinux has stalled since more than one