[syslinux] Illegal Opcode,the 2.

artreader at gmx.net artreader at gmx.net
Fri Nov 30 10:38:29 PST 2012


Thanks again, Shao

To make sure there is no "foreing" code in partition table and MBR,
MBR was nulled with mbr-sys and partition table produced new with fdisk.
Cause it is a machine with HP Raid, the old-fashioned cciss driver aund the new one hpsa were tested. The FAT Partition created with parted and than syslinux install.

To make sure it is not a machine-specific problem, another HP RAID was borrowed - the same results. Additionally I visited some friends and tested the syslinux versions on some desktops and servers, partially with RAID controllers (non HP) - no single problem.

So, from the logical part, it should be syslinux, that makes the problem.

For the 4.06 release a tarball syslinux-4.06.tar.bz2 from http://www.kernel.org/pub/linux/utils/boot/syslinux/ was downloaded.
Before I tried 4.03, 3.86 etc from the same source.
For 5.00 pre 12 a snapshot from http://git.kernel.org/?p=boot/syslinux/syslinux.git was obtained.

Fred

-------- Original-Nachricht --------
> Datum: Fri, 30 Nov 2012 12:42:54 -0500
> Von: Shao Miller <sha0.miller at gmail.com>
> An: artreader at gmx.net
> CC: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com>
> Betreff: Re: [syslinux] Illegal Opcode,the 2.

> In the http://reboot.pro Syslinux forum, On 11/30/2012 12:17, 
> artreader at gmx.net wrote:
> > @Wonko the Sane: the MBR is correct and it is the syslinux one. With non
> HP threre is no problem.
> > @Shao: Syslinux is installed with linux sysinstall sucessfully and it is
> the _boot_ with syslinux, which makes a problem
> 
> Thank you for clarifying whether it was the install or the boot.
> 
> Perhaps we can determine if it is the MBR or if it's Syslinux that's 
> causing the problem.  If you leave the Syslinux MBR intact but use some 
> other boot code on the partition's boot sector (such as DOS or Windows), 
> does the red screen still occur?  If it does, then the Syslinux MBR 
> could be the problem.  If it doesn't, then it could be Syslinux that's 
> causing the problem.
> 
> If you cannot perform this test because you do not have DOS or Windows 
> involved, please let us know.  It's possible that someone can come up 
> with a diagnostic partition boot sector for you, if there isn't one
> already.
> 
> As far as understanding the red screen's output, I think we'd really 
> need an _exact_ version access to the corresponding files in the build 
> tree.  If you are using one of the downloads, then please specify 
> exactly which one (the download link).
> 
> However, if you are certain that the red screen has the _exact_ same 
> output regardless of 4.06 or 5.00, then perhaps we'll find that the MBR 
> is the problem.  Or not.
> 
> - Shao Miller



More information about the Syslinux mailing list