All,
Thanks for all your help. Now, I can compile the latest source code base on
RedHat 5.5 after update nasm(to 2.09) and binutil(2.17).
And *make spotless* before *make* under core/ directory. But with the new
pxelinux.0, the PXEClient can not bootup.
The error info,
No valid file system found!
And stuck in there. I think maybe the gcc cause the problem. My gcc version
is 4.1.2.
Thanks aaron
-----????-----
???: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] ??
syslinux-request at zytor.com
????: Thursday, December 02, 2010 4:00 AM
???: syslinux at zytor.com
??: Syslinux Digest, Vol 93, Issue 1
Send Syslinux mailing list submissions to
syslinux at zytor.com
To subscribe or unsubscribe via the World Wide Web, visit
http://www.zytor.com/mailman/listinfo/syslinux
or, via email, send a message with subject or body 'help' to
syslinux-request at zytor.com
You can reach the person managing the list at
syslinux-owner at zytor.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Syslinux digest..."
Today's Topics:
1. Re: Useful Info about Dell latitude E5510 (Gene Cumm)
2. Re: how to compile syslinux-4.03 (Gilles Espinasse)
3. Re: Syslinux Digest, Vol 92, Issue 25 (Gene Cumm)
4. Re: Syslinux Digest, Vol 92, Issue 25 (Aaron Luo)
5. Re: how to compile syslinux-4.03 (Aaron Luo)
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Nov 2010 15:27:11 -0500
From: Gene Cumm <gene.cumm at gmail.com>
To: "Cockburn, Beau" <beau.cockburn at st-clair.net>
Cc: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com>
Subject: Re: [syslinux] Useful Info about Dell latitude E5510
Message-ID:
<AANLkTimw55JjGhCJ7nCtFYw6H5crf8J6xDBHmwwD_u=r at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Fri, Nov 26, 2010 at 07:25, Gene Cumm <gene.cumm at gmail.com>
wrote:> On Thu, Nov 25, 2010 at 15:31, Cockburn, Beau
> <beau.cockburn at st-clair.net> wrote:
>> Hi Gene,
>>
>> 1 - Well I could try join the list. :)
>>
>> 2 - Yes pre-complied 4.03
>>
>> After reading your comment about the Append hd0, I checked my laptop
again and discovered something new myself. It doesn't work if you left USB
stick in it. :) ?Even thought I didn't include USB as part of boot list. It
will give me error "Remove any media and restart..." ?So now both HD0
and
HD0 0 will work on E5510 as long as you don't stick any USB sticks in
it.>>
>
> That gives me some tests to try Monday. ?I just hope that the E6410
> and E5510 are similar enough in their BIOS.
>
> This sounds to me that there's a bug in the BIOS (main or the PXE
> option ROM; both are integrated to the same chip and same upgrade
> application). ?Is the USB stick bootable? ?Have you noticed differing
> results with bootable versus non-bootable USB sticks?
What the? I get some interesting and confusing behavior. Dell
Latitude E6410 A04, Legacy boot list option (of course; not UEFI).
When booting from PXELINUX 4.03 with a USB drive attached, the USB is
assigned BIOS drive 0x80 while the internal HDD is 0x81, regardless of
if USB boot is enabled or disabled or where in the sequence the USB
boot is placed relative to internal HDD when the SATA controller is in
IRRT or AHCI mode. When in ATA mode, it's more complex. I'll report
this later.
The message "Remove any media and restart..." is probably on your UFD.
I have consistent results from "chain.c32 hd0" versus "chain.c32
hd0
0" on PXELINUX 4.03 (the issue in the initial report). Using "chain
hd1" boots the HDD fine when assigned to 0x81.
"LOCALBOOT -1" and "LOCALBOOT 0" with or without the UFD
just reboots
the system. Using int18.com also results in a reboot.
Erwan, Pierre: Thanks again for HDT.
--
-Gene
>> -----Original Message-----
>> From: Gene Cumm [mailto:gene.cumm at gmail.com]
>> Sent: November-24-10 8:53 PM
>> To: For discussion of Syslinux and tftp-hpa
>> Cc: Cockburn, Beau
>> Subject: Re: [syslinux] Useful Info about Dell latitude E5510
>>
>> On Wed, Nov 24, 2010 at 18:11, Cockburn, Beau
>> <beau.cockburn at st-clair.net> wrote:
>>> Hi Gene
>>
>> 1) If you join the list, continuing this conversation would be easier
>> in that others will more readily see your replies.
>>
>> 2) Could you provide version details? ?Are you using the pre-compiled
>> pxelinux.0 and chain.c32 from the Syslinux 4.03 package? ?If not, this
>> is probably my first suggestion. ?Of course, if you have any other
>> modules from Syslinux, they should come from the same package/package
>> set.
>>
>>> Yes that's right "Append HD0" failed. I'm not
sure why but it keeps
coming back to PXE.>>
>> This is indeed interesting. ?Using "chain.c32 hd0 0" works
while
>> "chain.c32 hd0" does not. ?(These are just the one-line
equivalent of
>> the LABEL you're probably using)
>>
>> "keeps coming back to PXE."? ?Do you mean that using
"chain.c32 hd0"
>> just restarts the PXE boot? ?If so, the BIOS is trying to be smart and
>> retry the boot rather than fail.
>>
>> I have access to E6410s at work that I can try to check Monday.
>>
>>> So I used append hd0 0 and it worked.
>>>
>>> Beau
>>>
>>> ****************************
>>> Sent from Beast's BlackBerry BOLD.
>>> Have a nice BOLD day!
>>> Beau Cockburn,
>>> Computer Technician, A+
>>> SCCDSB - Ursuline College
>>> ****************************
>>>
>>> ----- Original Message -----
>>> From: Geert Stappers <stappers at stappers.nl>
>>> To: Gene Cumm <gene.cumm at gmail.com>
>>> Cc: Cockburn, Beau
>>> Sent: Wed Nov 24 18:06:06 2010
>>> Subject: Re: [syslinux] Useful Info about Dell latitude E5510
>>>
>>> Op 20101124 om 16:53 schreef Gene Cumm:
>>>> On Wed, Nov 24, 2010 at 11:19, Cockburn, Beau wrote:
>>>> > Hi H. Peter Anvin,
>>>> >
>>>> > I wanted to thank you for sharing information about PXE, I
have used
>>>> > this a lot and I wanted to share something that may be
important for
you>>>> > and your readers.
>>>>
>>>> I think feedback, especially when a feature is new or there is
a
>>>> suspected bug, is always appriciated.
>>>>
>>>> > I have many different Dell model, they all worked well
with PXE
booting>>>> > however not for E5510. I noticed that using
"LocalBoot -1 or 0"
doesn't>>>> > work well. What I did use for Latitude E5510 (Bios A06)
was same to
>>>> > "LOCALBOOT on IBM x3850 X5"
>>>> >
>>>> > COM32 Chain.c32
>>>> > Append hd0 0
>>>> >
>>>> > Not "Append hd0"
>>>>
>>>> Does this mean you tried just "APPEND hd0" and it
failed or you never
>>>> tested this scenario? ?The two are supposed to be equivalent.
?If you
>>>> tested "APPEND hd0" and it didn't work, this is
probably a bug.
>>>>
>>>> > It works and boots to local disk without any problems.
>>>>
>>>> That's good to know.
------------------------------
Message: 2
Date: Tue, 30 Nov 2010 23:49:51 +0100
From: "Gilles Espinasse" <g.esp at free.fr>
To: "For discussion of Syslinux and tftp-hpa" <syslinux at
zytor.com>
Cc: Aaron Luo <luotanke at 163.com>
Subject: Re: [syslinux] how to compile syslinux-4.03
Message-ID: <367201cb90e0$e6e6cab0$f9b5a8c0 at pii350>
Content-Type: text/plain; charset="iso-8859-1"
----- Original Message -----
From: "H. Peter Anvin" <hpa at zytor.com>
To: "For discussion of Syslinux and tftp-hpa" <syslinux at
zytor.com>
Cc: "Aaron Luo" <luotanke at 163.com>
Sent: Tuesday, November 30, 2010 7:53 PM
Subject: Re: [syslinux] Syslinux Digest, Vol 92, Issue 25
> On 11/30/2010 04:14 AM, Aaron Luo wrote:
> > Sorry Gene,
> >
> > I got the version of binutils is 2.17.
> > I download the latest Binutils to make the *objdump* and *objcopy*.
with
> > both of these utilities to create new pxelinux.raw.
> > then, the error message shows me that,
> >
> > objcopy -O binary pxelinux.elf pxelinux.raw
> > ../lzo/prepcore pxelinux.raw pxelinux.bin
> > ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0)
> > make[1]: *** [pxelinux.bin] Error 1
> >
not simple to compile binutils properly
> > so, i thought maybe there is something wrong with the format of the
> > pxelinux.raw.
> > is that right?
> >
>
> Either that, or prepcore miscompiles on this platform.
>
> -hpa
>
I try full syslinux compilation with binutils-2.20.1, nasm-2.09.04,
gcc-4.4.5.
It compile entirely (except the win part) after unsetting LDFLAGS which
value was "-Wl,--hash-style=gnu"
After a make clean, it fail to compile again because I had not python
installed in that chroot.
Error is
python menugen.py --input=test.menu --output=test.c --template=adv_menu.tpl
make[2]: python: Command not found
Anyway on centos-5.5, 'make installer' work without special package
upgrade.
Gilles
------------------------------
Message: 3
Date: Tue, 30 Nov 2010 20:53:56 -0500
From: Gene Cumm <gene.cumm at gmail.com>
To: For discussion of Syslinux and tftp-hpa <syslinux at zytor.com>
Cc: Aaron Luo <luotanke at 163.com>
Subject: Re: [syslinux] Syslinux Digest, Vol 92, Issue 25
Message-ID:
<AANLkTimenG+g5ZW364uTAsafDQppUfHvC9fSGQLE2WWc at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Nov 30, 2010 at 13:53, H. Peter Anvin <hpa at zytor.com>
wrote:> On 11/30/2010 04:14 AM, Aaron Luo wrote:
>> Sorry Gene,
>>
>> I got the version of binutils is 2.17.
>> I download the latest Binutils to make the *objdump* and *objcopy*.
with
>> both of these utilities to create new pxelinux.raw.
>> then, the error message shows me that,
>>
>> objcopy -O binary pxelinux.elf pxelinux.raw
>> ../lzo/prepcore pxelinux.raw pxelinux.bin
>> ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0)
>> make[1]: *** [pxelinux.bin] Error 1
>>
>> so, i thought maybe there is something wrong with the format of the
>> pxelinux.raw.
>> is that right?
>>
>
> Either that, or prepcore miscompiles on this platform.
I tried someone's prepcore from CentOS 5.5 on a spotless extract of
4.03 and it worked. The sequence of execution for pxelinux.0 is nasm,
ld, objdump, perl, objcopy, prepcore. I used the make output to
backtrace one command at a time from his intermediate binaries and
found that redoing the ld step was what was needed to get it to work
on my build system.
Aaron, after changing to the latest binutils, did you either start
from a fresh extracted directory or clean it up (probably needs 'make
spotless', at least in core/, just to be sure)?
--
-Gene
------------------------------
Message: 4
Date: Wed, 1 Dec 2010 22:25:27 +0800
From: "Aaron Luo" <luotanke at 163.com>
To: "H. Peter Anvin" <hpa at zytor.com>, "For discussion of
Syslinux and
tftp-hpa" <syslinux at zytor.com>
Subject: Re: [syslinux] Syslinux Digest, Vol 92, Issue 25
Message-ID: <66ADCC2C4BAB41C2BAC3F771376D1A46 at d15fb1f705c642c>
Content-Type: text/plain; format=flowed; charset="ISO-8859-1";
reply-type=original
Hi Peter,
if so, how can I do? I need to figure out why the clients can recieve the
data from PXE server.
I means what can i do to compile the new pxelinux.0? should it need Fedora
13?
thanks aaron.
----- Original Message -----
From: "H. Peter Anvin" <hpa at zytor.com>
To: "For discussion of Syslinux and tftp-hpa" <syslinux at
zytor.com>
Cc: "Aaron Luo" <luotanke at 163.com>
Sent: Wednesday, December 01, 2010 2:53 AM
Subject: Re: [syslinux] Syslinux Digest, Vol 92, Issue 25
> On 11/30/2010 04:14 AM, Aaron Luo wrote:
>> Sorry Gene,
>>
>> I got the version of binutils is 2.17.
>> I download the latest Binutils to make the *objdump* and *objcopy*.
with
>> both of these utilities to create new pxelinux.raw.
>> then, the error message shows me that,
>>
>> objcopy -O binary pxelinux.elf pxelinux.raw
>> ../lzo/prepcore pxelinux.raw pxelinux.bin
>> ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0)
>> make[1]: *** [pxelinux.bin] Error 1
>>
>> so, i thought maybe there is something wrong with the format of the
>> pxelinux.raw.
>> is that right?
>>
>
> Either that, or prepcore miscompiles on this platform.
>
> -hpa
------------------------------
Message: 5
Date: Wed, 1 Dec 2010 22:28:49 +0800
From: "Aaron Luo" <luotanke at 163.com>
To: "Gilles Espinasse" <g.esp at free.fr>, "For discussion
of Syslinux
and tftp-hpa" <syslinux at zytor.com>
Subject: Re: [syslinux] how to compile syslinux-4.03
Message-ID: <AD0A9CB8C72C4E24B7F044D6AFA0214C at d15fb1f705c642c>
Content-Type: text/plain; format=flowed; charset="ISO-8859-1";
reply-type=original
thanks Gilles,
I will try it ASAP.
And if the error happen again, I need your help.
thanks aaron
----- Original Message -----
From: "Gilles Espinasse" <g.esp at free.fr>
To: "For discussion of Syslinux and tftp-hpa" <syslinux at
zytor.com>
Cc: "Aaron Luo" <luotanke at 163.com>
Sent: Wednesday, December 01, 2010 6:49 AM
Subject: Re: [syslinux] how to compile syslinux-4.03
>
> ----- Original Message -----
> From: "H. Peter Anvin" <hpa at zytor.com>
> To: "For discussion of Syslinux and tftp-hpa" <syslinux at
zytor.com>
> Cc: "Aaron Luo" <luotanke at 163.com>
> Sent: Tuesday, November 30, 2010 7:53 PM
> Subject: Re: [syslinux] Syslinux Digest, Vol 92, Issue 25
>
>
>> On 11/30/2010 04:14 AM, Aaron Luo wrote:
>> > Sorry Gene,
>> >
>> > I got the version of binutils is 2.17.
>> > I download the latest Binutils to make the *objdump* and
*objcopy*.
>> > with
>> > both of these utilities to create new pxelinux.raw.
>> > then, the error message shows me that,
>> >
>> > objcopy -O binary pxelinux.elf pxelinux.raw
>> > ../lzo/prepcore pxelinux.raw pxelinux.bin
>> > ../lzo/prepcore: pxelinux.raw: output too big (30165, max 0)
>> > make[1]: *** [pxelinux.bin] Error 1
>> >
> not simple to compile binutils properly
>
>> > so, i thought maybe there is something wrong with the format of
the
>> > pxelinux.raw.
>> > is that right?
>> >
>>
>> Either that, or prepcore miscompiles on this platform.
>>
>> -hpa
>>
> I try full syslinux compilation with binutils-2.20.1, nasm-2.09.04,
> gcc-4.4.5.
> It compile entirely (except the win part) after unsetting LDFLAGS which
> value was "-Wl,--hash-style=gnu"
>
> After a make clean, it fail to compile again because I had not python
> installed in that chroot.
> Error is
> python
> menugen.py --input=test.menu --output=test.c --template=adv_menu.tpl
> make[2]: python: Command not found
>
> Anyway on centos-5.5, 'make installer' work without special package
> upgrade.
>
> Gilles
>
>
------------------------------
_______________________________________________
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.
End of Syslinux Digest, Vol 93, Issue 1
***************************************