similar to: Serious Bug with Syslinux 6.02

On 11/23/2013 09:35 AM, Carl Duff wrote: > -- Re-sent as original may be stuck at awaiting "authorisation" (originally > sent before I joined the mailing list) > > Hi All, > > It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or > DVD on older - non-UEFI - systems. Any attempt to do so will result in the > following error message: ISOLINUX

Hi there, since I didn't had the time to test, this might be the solution for the issue Arch-based distros faced: https://projects.archlinux.org/svntogit/packages.git/plain/trunk/syslinux-6.02-fix-chainloading.patch?h=packages/syslinux This is included in the latest syslinux package you find in testing/unstable at Manjaro. kind regards Phil On 11/23/2013 03:44 PM, Philip M?ller wrote:

Hi Ady, I'm the developer of manjaroiso, the tool we use to build our install medias for Manjaro Linux. During our testings we found out, that syslinux6 won't work on older hardware. I've a new Lenovo i7 notebook which booted up our images just fine. Even with syslinux6. On my other PCs I got similar error messages as Carl got. Here is the code I'm using for either syslinux6

-- Re-sent as original may be stuck at awaiting "authorisation" (originally sent before I joined the mailing list) Hi All, It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or DVD on older - non-UEFI - systems. Any attempt to do so will result in the following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = 4279, drive FE It is still possible to

On 11/24/2013 09:23 PM, Gerardo Exequiel Pozzi wrote: > On 11/23/2013 09:35 AM, Carl Duff wrote: >> -- Re-sent as original may be stuck at awaiting "authorisation" (originally >> sent before I joined the mailing list) >> >> Hi All, >> >> It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or >> DVD on older - non-UEFI -

It occured with every BIOS system I tested on (none of them Dell): 1. HP G62 laptop (i3) 2. Samsung RV520 (i3) Don't know what system Philip Muller uses; have copied him in as he has far more technical knowledge than I do. Syslinux tested from Arch and Manjaro (an Arch derivative). Basically found then when creating latest ISO images. I may be missing something as well about the FMs. Just

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

> It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or > DVD on older - non-UEFI - systems. Any attempt to do so will result in the > following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = > 4279, drive FE Is this happening on "every" system? Or are we talking about specific models or with specific characteristics? Is this behavior

On 11/21/2013 02:50 AM, Carl Duff wrote: > Hi All, > > It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via > CD or DVD on older - non-UEFI - systems. Any attempt to do so will > result in the following error message: ISOLINUX 6.02 ETCDisolinux: > Disk error 01, AX = 4279, drive FE > Error 01 is unsupported operation, 42xx is read, so something is really

Hi, Carl Duff wrote: > (at least some) OSs not using syslinux 6.02 won't > recognise ISOs that do. For example, the file managers of Mint 13, Windows > 7, and Windows 8 all wrongly "see" blank discs). > [...] > This is certainly not an issue with corrupted downloads, burning, or dodgy > computer disc-drives. You mean real CD or DVD with operating systems on real

Hi, Ady wrote: > I guess that being isolinux.bin 4.07 smaller than 32KiB (24KiB), > while isolinux.bin 6.02 being bigger (42KiB), and with the addition > of multiple alternative boot images in the same ISO, the chances of > isolinux.bin being located on a higher sector in the media seem to be > higher. > > So, perhaps the potential problem was always there, just that the

On 11/25/2013 08:40 AM, Thomas Schmitt wrote: > Hi, > > Ady wrote: >> I guess that being isolinux.bin 4.07 smaller than 32KiB (24KiB), >> while isolinux.bin 6.02 being bigger (42KiB), and with the addition >> of multiple alternative boot images in the same ISO, the chances of >> isolinux.bin being located on a higher sector in the media seem to be >>

> As stated earlier, the next version of xorriso will have > sort weight 2 for El Torito boot images by default. > But it will not harm to explicitely use --sort-weight > options with old and new versions of xorriso. FWIW, mkisofs is supposed to assign a +2 sort weight by default to the eltorito boot image and +1 to the boot catalog, at least when no sort file is provided. I

Hi Everyone, I downloaded the CentOS 6 x86_64 DVD ISOs and burned the first image to a rewritable DVD. When I tried to boot my new home server off it, it didn't, and then this was printed to the screen: ETCDisolinux: Found something at drive = EF No DEFAULT or UI configuration directive found! boot: The same disc works fine in my 4 year old HP laptop, and when installing CentOS 6 as a KVM.

Recently a patch by HPA was added to the elflink branch, "isolinux: Clear upper half of EDX before using..." http://git.zytor.com/?p=syslinux/syslinux.git;a=commit;h=870b84dd8714d dfccc9288025331423efa6d76b7 The patch was then applied to the firmware branch too. The patch solves an issue introduced by a prior commit "isolinux: Update LBA in getlinsec loop". Since the

On Sun, Jul 19, 2020 at 11:54:06AM +0100, Rui Correia wrote: > Greetings folks. > I've setup libvirtd on my manjaro linux laptop. > Got a couple of VM's running (Win10 and Debian10) through NAT without any > issues. > > This is what the current network diagram looks like and it works fine: > > +-----------------------------------+ >

On 2020-07-20 05:32, Daniel P. Berrange wrote: > On Sun, Jul 19, 2020 at 11:54:06AM +0100, Rui Correia wrote: >> Greetings folks. >> I've setup libvirtd on my manjaro linux laptop. >> Got a couple of VM's running (Win10 and Debian10) through NAT without >> any >> issues. >> >> This is what the current network diagram looks like and it works

Greetings folks. I've setup libvirtd on my manjaro linux laptop. Got a couple of VM's running (Win10 and Debian10) through NAT without any issues. This is what the current network diagram looks like and it works fine: +-----------------------------------+ | +---------------------+ | | |

On 7/23/20 6:14 PM, Rui Correia wrote: > > > On Thu, Jul 23, 2020 at 10:36 PM Rui Correia <rdscorreia74@gmail.com > <mailto:rdscorreia74@gmail.com>> wrote: > > > Thanks for the headsup. I'll ask the Manjaro guys about the nft. > Hopefully they'll know if nft is installed and running. > > Well, that was fast. > I've asked the

On 11/24/2013 09:56 AM, Ady wrote: >> The very early code that emits this message is *identical* between >> Syslinux 4 and Syslinux 6. The biggest difference is the size of >> isolinux.bin, so it is possible that that might be the source of the >> problem. >> >> -hpa > > I wonder if isolinux.bin should be limited to max. 16 sectors (of > 2KiB