[syslinux] Strange bug since 3.83 version [solution]

[Gene Cumm]

2010/11/12 Éric Seigne <eric.seigne at ryxeo.com>:
> Please forget me :)
>
> i've the solution: RTFM :d
>
>   default local
>       label local
>       localboot 0x80
>
>
> will became
>
>   default local
>       label local
>       kernel chain.c32
>       append hd0
>
>
> And everything is good !
>
> Éric

You may want to read doc/syslinux.txt on the different LOCALBOOT
options.  I believe 0x80 should only be used with ISOLINUX to boot
BIOS drive 0x80 (normally first hard drive).  I believe 0 and -1 are
the most common values used with PXELINUX.

Most of the time chain.c32 should work.  Within the last 1-1.5 years,
I know there were numerous bug fixes.  I had several machines that
previously couldn't use chain.c32 from PXELINUX but now can.

See also http://syslinux.zytor.com/wiki/index.php/Hardware_Compatibility#LOCALBOOT

Have you considered a PXE ROM upgrade or a BIOS upgrade?  For add-in
NICs, you should go through the brand name company if possible before
resorting to the OEM.  For LoMs (LAN on Motherboard), go to the brand
name company of the board/computer for a BIOS upgrade as most LoM PXE
ROMs are buried within the BIOS.  It's also possible that the BIOS is
misbehaving.

-- 
-Gene

> Éric Seigne a écrit :
>>    Hello,
>>    i've found a strange bug, here is my situation:
>>     - all of our computers makes a pxeboot request by default
>>    dhcp server is configured:
>>    option option-128 code 128 = string;
>>    option option-129 code 129 = text;
>>    option space PXE;
>>    option PXE.mtftp-ip code 1 = ip-address;
>>    option PXE.mtftp-cport code 2 = unsigned integer 16;
>>    option PXE.mtftp-sport code 3 = unsigned integer 16;
>>    option PXE.mtftp-tmout code 4 = unsigned integer 8;
>>    option PXE.mtftp-delay code 5 = unsigned integer 8;
>>    .../...
>>        host computer-01 {
>>            hardware ethernet 00:27:0e:0a:d2:73;
>>            fixed-address 192.168.100.35;
>>            if substring (option vendor-class-identifier, 0, 9) =
>>    "PXEClient" {
>>                filename "pxelinux.0";
>>            }
>>            else {
>>                filename "kernel-maui.nbi";
>>            }
>>            option root-path "192.168.100.1:/opt/ltsp44/i386";
>>        }
>>    .../...
>>     - if nothing to do with lan boot, server send a pxelinux.cfg/MACCADDR
>>    file with
>>    default local
>>        label local
>>        localboot 0x80
>>     - if i have a windows xp on my computer, this windows does not boot
>>    !!! i unplug my ethernet card, reboot, then windows boot-up correctly !
>>    I've constated this bug on several computers with theses network cards:
>>     - Computer A: RTL8101E
>> 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E P
>> CI Express Fast Ethernet controller (rev 02)
>> 03:00.0 0200: 10ec:8136 (rev 02)
>>
>>     - Computer B: Atheros AR8132 PCI-E
>>    This problem is present with pxelinux.0 since 3.83 version, 4.03
>>    included :( ... if i use pxelinux.0 from 3.82 everything is good (but
>>    some new hardware does not work damned !)
>>    Do you have some ideas (please say "yes") ?
>>    Thanks,
>>    Éric
>> --
>>         -- AbulEdu -- NouvaLinux -- Centre de Formation --
>>
>> Éric Seigne - Directeur                    | [1]eric.seigne at ryxeo.com
>> RyXéo SARL                                 | [2]http://www.ryxeo.com
>> 21 avenue M. et E. Dulout                  | tel +33 6 987 444 01
>> 33600 Pessac - FRANCE                      | fax +33 9 56 606 607
>>
>> References