Mailing List Archive

Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:

>Op 20-09-2007 om 08:31 schreef Stéphane ARQUER:
>> "previous"
>> > [ 'elf.c32' booting a RTEMS ELF binary ]
>>
>> - P4 2GHz 512M with a 3c905c PXE v2.20
>> PXELINUX doesn't work with this one
>>
>> - P4 3GHz 2048M with an Intel 82573L gigabit eth PXE
>> PXELINUX works on this machine
>>
>> - HP kayak P3 866MHz with PXE v2.20
>> PXELINUX doesn't work with this one
>
>
>I wonder if PXELINUX also fails to boot a Linux kernel.
>
>Or should the 'works/works not' be read
>for 'KERNEL elf.c32' and 'APPEND rtems_executable' combination?
>
>In other words:
> There might be a "elf.c32 plus it's library" problem
> and _not a BIOS_ problem ...
>
>I suggest to start[1] a network install from
>http://ftp.debian.org/debian/dists/etch/main/installer-i386/current/images/netboot/netboot.tar.gz
>and begining with the working 3GHZ computer. When seeing the "select a
>language" dialog from Debian-Installer, one knows that PXELINUX did
>succesfull download the kernel and initial ramdisk, plus starting the kernel.

It's working I can see the choose language menu.

>
>
>Cheers
>Geert Stappers
>
>[1] just start, no need to do an actual install.
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX@zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Op 20-09-2007 om 15:37 schreef Stéphane ARQUER:
> Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:
> >
> >I wonder if PXELINUX also fails to boot a Linux kernel.
> >
> >Or should the 'works/works not' be read
> >for 'KERNEL elf.c32' and 'APPEND rtems_executable' combination?
> >
> >In other words:
> > There might be a "elf.c32 plus it's library" problem
> > and _not a BIOS_ problem ...
> >
> >I suggest to start[1] a network install from
> >http://ftp.debian.org/debian/dists/etch/main/installer-i386/current/images/netboot/netboot.tar.gz
> >and begining with the working 3GHZ computer. When seeing the "select a
> >language" dialog from Debian-Installer, one knows that PXELINUX did
> >succesfull download the kernel and initial ramdisk, plus starting the kernel.
>
> It's working I can see the choose language menu.

On _all three_ computers?



Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Hi,

Yes, I made the test on the three computers and it's working on all.

SA

Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:

>Op 20-09-2007 om 15:37 schreef Stéphane ARQUER:
>> Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:
>> >
>> >I wonder if PXELINUX also fails to boot a Linux kernel.
>> >
>> >Or should the 'works/works not' be read
>> >for 'KERNEL elf.c32' and 'APPEND rtems_executable' combination?
>> >
>> >In other words:
>> > There might be a "elf.c32 plus it's library" problem
>> > and _not a BIOS_ problem ...
>> >
>> >I suggest to start[1] a network install from
>> >http://ftp.debian.org/debian/dists/etch/main/installer-i386/current/images/netboot/netboot.tar.gz
>> >and begining with the working 3GHZ computer. When seeing the "select a
>> >language" dialog from Debian-Installer, one knows that PXELINUX did
>> >succesfull download the kernel and initial ramdisk, plus starting the kernel.
>>
>> It's working I can see the choose language menu.
>
>On _all three_ computers?
>
>
>
>Cheers
>Geert Stappers
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX@zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Op 24-09-2007 om 08:02 schreef Stéphane ARQUER:
> Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:
> >Op 20-09-2007 om 15:37 schreef Stéphane ARQUER:
> >>Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:
> >>>
> >>> There might be a "elf.c32 plus it's library" problem
> >>> and _not a BIOS_ problem ...
> >>
> >> It's working I can see the choose language menu.
> >
> >On _all three_ computers?
>
> Yes, I made the test on the three computers and it's working on all.

Mmmm, that means the failed boot of the RTEMS executable is
due an error in elf.c32, not in the BIOS the two failing computers.


Advice:
Compile elf.c with debug enabled and rerun the test with the new elf.c32.


Cheers
Geert Stappers
--
diff --git a/com32/modules/elf.c b/com32/modules/elf.c
index 3fb1ad6..e681c62 100644
--- a/com32/modules/elf.c
+++ b/com32/modules/elf.c
@@ -49,7 +49,7 @@
/* If we don't have this much memory for the stack, signal failure */
#define MIN_STACK 512

-#define DEBUG 0
+#define DEBUG 1
#if DEBUG
# define dprintf printf
#else

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

I rebuild the elf.c32 with DEBUG activated ine the elf.c
I can see the traces before the booting msg:
Final available map:

Movelist:

Booting...

and it's frozen



Le 24/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:

>Op 24-09-2007 om 08:02 schreef Stéphane ARQUER:
>> Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:
>> >Op 20-09-2007 om 15:37 schreef Stéphane ARQUER:
>> >>Le 20/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:
>> >>>
>> >>> There might be a "elf.c32 plus it's library" problem
>> >>> and _not a BIOS_ problem ...
>> >>
>> >> It's working I can see the choose language menu.
>> >
>> >On _all three_ computers?
>>
>> Yes, I made the test on the three computers and it's working on all.
>
>Mmmm, that means the failed boot of the RTEMS executable is
>due an error in elf.c32, not in the BIOS the two failing computers.
>
>
>Advice:
>Compile elf.c with debug enabled and rerun the test with the new elf.c32.
>
>
>Cheers
>Geert Stappers
>--
>diff --git a/com32/modules/elf.c b/com32/modules/elf.c
>index 3fb1ad6..e681c62 100644
>--- a/com32/modules/elf.c
>+++ b/com32/modules/elf.c
>@@ -49,7 +49,7 @@
> /* If we don't have this much memory for the stack, signal failure */
> #define MIN_STACK 512
>
>-#define DEBUG 0
>+#define DEBUG 1
> #if DEBUG
> # define dprintf printf
> #else
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX@zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Geert Stappers wrote:
>
> Mmmm, that means the failed boot of the RTEMS executable is
> due an error in elf.c32, not in the BIOS the two failing computers.
>
> Advice:
> Compile elf.c with debug enabled and rerun the test with the new elf.c32.
>

Not necessarily, but it is likely.

It would be interesting to know if linux.c32 works on this system.

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Hi,

With linux.c32, there is the following error message:

loadind /kernel/hello.exe... ok
kernel load failure (insuficient memory?)
boot:


SA

Le 24/9/2007, "H. Peter Anvin" <hpa@zytor.com> a écrit:

>Geert Stappers wrote:
>>
>> Mmmm, that means the failed boot of the RTEMS executable is
>> due an error in elf.c32, not in the BIOS the two failing computers.
>>
>> Advice:
>> Compile elf.c with debug enabled and rerun the test with the new elf.c32.
>>
>
>Not necessarily, but it is likely.
>
>It would be interesting to know if linux.c32 works on this system.
>
> -hpa
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX@zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Op 25-09-2007 om 07:49 schreef Stéphane ARQUER:
> Hi,
>
> With linux.c32, there is the following error message:
>
> loadind /kernel/hello.exe... ok
> kernel load failure (insuficient memory?)
> boot:

Thing I would like to see, is a complete version of this table:

Clock | 3 GHz | 2.4 GHz | .8 GHz
memory | | |
Vendor | | |
BIOS | | |
elf.c32 | OK | FAIL | FAIL
pxelinux.0| OK | OK | OK
linux.c32 | | |


Because it will show on which computers linux.c32 was tested.



Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Hi,

Please find the completed table:

Clock | P4 3GHz | P4 2GHz | P3 866MHz
memory | 2048 M | 512 M | 256 M
Vendor | none | DOLCH FlexPAC | HP Kayak XU800
BIOS | Intel BX97510J.86A.1334.2006.0714.1343 | Award
IB800-G3-CX3A-0129 | IA.11.08FR
elf.c32 | OK | FAIL | FAIL
pxelinux.0| OK | OK | OK
linux.c32 | FAIL | FAIL | FAIL
debian-installer | OK | OK | OK


Regards

Stephane ARQUER


Le 25/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:

>Op 25-09-2007 om 07:49 schreef Stéphane ARQUER:
>> Hi,
>>
>> With linux.c32, there is the following error message:
>>
>> loadind /kernel/hello.exe... ok
>> kernel load failure (insuficient memory?)
>> boot:
>
>Thing I would like to see, is a complete version of this table:
>
>Clock | 3 GHz | 2.4 GHz | .8 GHz
>memory | | |
>Vendor | | |
>BIOS | | |
>elf.c32 | OK | FAIL | FAIL
>pxelinux.0| OK | OK | OK
>linux.c32 | | |
>
>
>Because it will show on which computers linux.c32 was tested.
>
>
>
>Cheers
>Geert Stappers
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX@zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

> Hi,
>
> With linux.c32, there is the following error message:
>
> loadind /kernel/hello.exe... ok
> kernel load failure (insuficient memory?)
> boot:

>
~ CPU + Clock | P4 3GHz | P4 2GHz | P3 866MHz
> memory | 2048 M | 512 M | 256 M
> Vendor | none | DOLCH FlexPAC | HP Kayak XU800
> BIOS | Intel | Award | HP
versions dropped, latest available assumed
> pxelinux.0 | OK | OK | OK
> elf.c32 | OK | FAIL | FAIL
> linux.c32 | FAIL | FAIL | FAIL


All linux.c32 configs failing, strange ...

Has any one a working configuration for linux.c32?
( Is a special kernel needed? Or another special configuration? )



Cheers
Geert Stappers

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Geert Stappers wrote:
> Op 25-09-2007 om 07:49 schreef Stéphane ARQUER:
>> Hi,
>>
>> With linux.c32, there is the following error message:
>>
>> loadind /kernel/hello.exe... ok
>> kernel load failure (insuficient memory?)
>> boot:
>

You can't load your hello.exe with linux.c32, you have to load a Linux
kernel...

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Geert Stappers wrote:
>> Hi,
>>
>> With linux.c32, there is the following error message:
>>
>> loadind /kernel/hello.exe... ok
>> kernel load failure (insuficient memory?)
>> boot:
>
> ~ CPU + Clock | P4 3GHz | P4 2GHz | P3 866MHz
>> memory | 2048 M | 512 M | 256 M
>> Vendor | none | DOLCH FlexPAC | HP Kayak XU800
>> BIOS | Intel | Award | HP
> versions dropped, latest available assumed
>> pxelinux.0 | OK | OK | OK
>> elf.c32 | OK | FAIL | FAIL
>> linux.c32 | FAIL | FAIL | FAIL
>
>
> All linux.c32 configs failing, strange ...
>
> Has any one a working configuration for linux.c32?
> ( Is a special kernel needed? Or another special configuration? )
>

No, but I think this strengthens my belief that there is something
subtly wrong with the shuffle library (used by elf.c32 and linux.c32.)

To explain in more detail: after loading the kernel into memory, the
shuffle library takes a list of memory segments and a list representing
the final configuration, and computes a sequence of moves that makes it
possible to get from point A to point B. This depends in part on the
memory configuration of the system, as well, of course, as on random events.

It always works on my test machine, of course (2 GB RAM), but that's
probably as much selection effect as anything else. It's also possible
that having lots of memory makes it less likely to provoke failure.

It would be *extremely* interesting if you could recompile elf.c32 with
"#define DEBUG 0" in com32/lib/syslinux/movebits.c changed to "#define
DEBUG 1" and see what prints out.

-hpa



_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Op 25-09-2007 om 12:39 schreef H. Peter Anvin:
> Geert Stappers wrote:
> >
~ ~ RTEMS bootable | | |
~ ~--------------------+-----------+---------------+----------------
> >~ CPU + Clock | P4 3GHz | P4 2GHz | P3 866MHz
> >> memory | 2048 M | 512 M | 256 M
> >> Vendor | none | DOLCH FlexPAC | HP Kayak XU800
> >> BIOS | Intel | Award | HP
> > versions dropped, latest available assumed
> >> pxelinux.0 | OK | OK | OK
> >> elf.c32 | OK | FAIL | FAIL
> >> linux.c32 | FAIL | FAIL | FAIL
> >
> > All linux.c32 configs failing, strange ...

>From another posting:
| | With linux.c32, there is the following error message:
| |
| | loadind /kernel/hello.exe... ok
| | kernel load failure (insuficient memory?)
| | boot:
|
| You can't load your hello.exe with linux.c32,
| you have to load a Linux kernel...

Could be elaborated how the linux.c32 test was done?

> > Has any one a working configuration for linux.c32?
> > ( Is a special kernel needed? Or another special configuration? )
>
> No, but I think this strengthens my belief that there is something
> subtly wrong with the shuffle library (used by elf.c32 and linux.c32.)
>
> To explain in more detail: after loading the kernel into memory, the
> shuffle library takes a list of memory segments and a list representing
> the final configuration, and computes a sequence of moves that makes it
> possible to get from point A to point B. This depends in part on the
> memory configuration of the system, as well, of course, as on random events.
>
> It always works on my test machine, of course (2 GB RAM), but that's
> probably as much selection effect as anything else. It's also possible
> that having lots of memory makes it less likely to provoke failure.
>
> It would be *extremely* interesting if you could recompile elf.c32 with
> "#define DEBUG 0" in com32/lib/syslinux/movebits.c changed to "#define
> DEBUG 1" and see what prints out.

I wonder if it would make sense to run linux.c32 with the same modification.


Looking forward to see an update of the RTEMS bootable table.

Cheers
Geert Stappers
--
stappers@alpaca:/usr/src/syslinux/com32/modules
$ grep movebits *
elf.c:#include <syslinux/movebits.h>
Binair bestand elf.elf komt overeen
Binair bestand linux.elf komt overeen
stappers@alpaca:/usr/src/syslinux/com32/modules
$ LANG=C grep movebits *
elf.c:#include <syslinux/movebits.h>
Binary file elf.elf matches
Binary file linux.elf matches
stappers@alpaca:/usr/src/syslinux/com32/modules
$

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Le 26/9/2007, "Geert Stappers" <stappers@stappers.nl> a écrit:

>Op 25-09-2007 om 12:39 schreef H. Peter Anvin:
>> Geert Stappers wrote:
>> >
>~ ~ RTEMS bootable | | |
>~ ~--------------------+-----------+---------------+----------------
>> >~ CPU + Clock | P4 3GHz | P4 2GHz | P3 866MHz
>> >> memory | 2048 M | 512 M | 256 M
>> >> Vendor | none | DOLCH FlexPAC | HP Kayak XU800
>> >> BIOS | Intel | Award | HP
>> > versions dropped, latest available assumed
>> >> pxelinux.0 | OK | OK | OK
>> >> elf.c32 | OK | FAIL | FAIL
>> >> linux.c32 | FAIL | FAIL | FAIL
>> >
>> > All linux.c32 configs failing, strange ...
>
>>From another posting:
>| | With linux.c32, there is the following error message:
>| |
>| | loadind /kernel/hello.exe... ok
>| | kernel load failure (insuficient memory?)
>| | boot:
>|
>| You can't load your hello.exe with linux.c32,
>| you have to load a Linux kernel...

No, I replace the elf.c32 by linux.c32 in the corresponding pxelinux.cfg
file.
Effetively, it was not a linux kernel file but the hello.exe rtems exec
file.
There was a misunderstanding In the test asked for.
Sorry to waste your time.

SA

>
>Could be elaborated how the linux.c32 test was done?
>
>> > Has any one a working configuration for linux.c32?
>> > ( Is a special kernel needed? Or another special configuration? )
>>
>> No, but I think this strengthens my belief that there is something
>> subtly wrong with the shuffle library (used by elf.c32 and linux.c32.)
>>
>> To explain in more detail: after loading the kernel into memory, the
>> shuffle library takes a list of memory segments and a list representing
>> the final configuration, and computes a sequence of moves that makes it
>> possible to get from point A to point B. This depends in part on the
>> memory configuration of the system, as well, of course, as on random events.
>>
>> It always works on my test machine, of course (2 GB RAM), but that's
>> probably as much selection effect as anything else. It's also possible
>> that having lots of memory makes it less likely to provoke failure.
>>
>> It would be *extremely* interesting if you could recompile elf.c32 with
>> "#define DEBUG 0" in com32/lib/syslinux/movebits.c changed to "#define
>> DEBUG 1" and see what prints out.
>
>I wonder if it would make sense to run linux.c32 with the same modification.
>
>
>Looking forward to see an update of the RTEMS bootable table.
>
>Cheers
>Geert Stappers
>--
>stappers@alpaca:/usr/src/syslinux/com32/modules
>$ grep movebits *
>elf.c:#include <syslinux/movebits.h>
>Binair bestand elf.elf komt overeen
>Binair bestand linux.elf komt overeen
>stappers@alpaca:/usr/src/syslinux/com32/modules
>$ LANG=C grep movebits *
>elf.c:#include <syslinux/movebits.h>
>Binary file elf.elf matches
>Binary file linux.elf matches
>stappers@alpaca:/usr/src/syslinux/com32/modules
>$
>
>_______________________________________________
>SYSLINUX mailing list
>Submissions to SYSLINUX@zytor.com
>Unsubscribe or set options at:
>http://www.zytor.com/mailman/listinfo/syslinux
>Please do not send private replies to mailing list traffic.
>

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.

Geert Stappers wrote:
>>
>> It would be *extremely* interesting if you could recompile elf.c32 with
>> "#define DEBUG 0" in com32/lib/syslinux/movebits.c changed to "#define
>> DEBUG 1" and see what prints out.
>
> I wonder if it would make sense to run linux.c32 with the same modification.
>

Yes, it probably would. What I probably really need to do is to produce
debugging versions which dump the input to the shuffling algorithm; I
should be able to use that as synthetic input for debugging on my end.

Stay tuned...

-hpa

_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX@zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.