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
Visible links
1. mailto:eric.seigne at ryxeo.com
2. http://www.ryxeo.com/
Hidden links:
3.
https://secure.ryxeo.com/glpi/front/device.form.php?ID=10&device_type=5
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
?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
>
> Visible links
> 1. mailto:eric.seigne at ryxeo.com
> 2. http://www.ryxeo.com/
>
> Hidden links:
> 3.
https://secure.ryxeo.com/glpi/front/device.form.php?ID=10&device_type=5
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at zytor.com
> Unsubscribe or set options at:
> http://www.zytor.com/mailman/listinfo/syslinux
> Please do not send private replies to mailing list traffic.
>
>
--
-- AbulEdu -- NouvaLinux -- Centre de Formation --
?ric Seigne - Directeur | eric.seigne at ryxeo.com
RyX?o SARL | 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
On 11/12/2010 01:58 AM, ?ric Seigne wrote:> 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") ?What are the actual machines? There are some machines with mainboard BIOS problems which cause this, but I'm particularly interested in your case since you say 3.82 worked but 3.83 didn't. In particular, if you could try the 3.83-prereleases (or even better, if you feel comfortable with building from source, use "git bisect") it might be possible to narrow this to a specific change. However, first of all try "localboot 0" as Gene points out. -hpa