Mailing List Archive

Lindgren Daniel wrote:
>
> Could I be of assistance in finding the problem? I can't send any
> machines, but I'd be happy to run whatever tests needed to resolve this
> issue.
>

Unlikely. It's like finding a needle in a haystack since I have no way
of reproducing the problem.

Try reporting the problem to your vendor. It *might* cause some
activity, especially if you represent a sizable customer.

-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.

> Lindgren Daniel wrote:
> >
> > Could I be of assistance in finding the problem? I can't send any
> > machines, but I'd be happy to run whatever tests needed to resolve
> > this issue.
> >
>
> Unlikely. It's like finding a needle in a haystack since I
> have no way of reproducing the problem.
>
> Try reporting the problem to your vendor. It *might* cause
> some activity, especially if you represent a sizable customer.
>
> -hpa

OK, no point in trying debug builds? I have limited programming
knowledge and there does not seem to be any debug builds included in the
Syslinux distribution.

I have already been in contact with Fujitsu, if I could prove that the
problem is in the Yukon PXE firmware maybe I could convince them to send
you a test machine, but it is unlikely without some further evidence
that the problem isn't with PXELINUX.

Daniel Lindgren


_______________________________________________
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.

> -----Ursprungligt meddelande-----
> Från: Lindgren Daniel
> Skickat: den 26 april 2007 06:37
> Till: 'H. Peter Anvin'
> Kopia: syslinux@zytor.com
> Ämne: SV: [syslinux] Yukon NIC - again
>
>
>
> > Lindgren Daniel wrote:
> > >
> > > Could I be of assistance in finding the problem? I can't send any
> > > machines, but I'd be happy to run whatever tests needed
> to resolve
> > > this issue.
> > >
> >
> > Unlikely. It's like finding a needle in a haystack since I have no
> > way of reproducing the problem.
> >
> > Try reporting the problem to your vendor. It *might* cause some
> > activity, especially if you represent a sizable customer.
> >
> > -hpa
>
> OK, no point in trying debug builds? I have limited
> programming knowledge and there does not seem to be any debug
> builds included in the Syslinux distribution.
>
> I have already been in contact with Fujitsu, if I could prove
> that the problem is in the Yukon PXE firmware maybe I could
> convince them to send you a test machine, but it is unlikely
> without some further evidence that the problem isn't with PXELINUX.
>
> Daniel Lindgren

Found this on a Rembo Toolkit 4 forum, regarding Yukon and PXE problems:

---

The fix IS to to use "disable enhanced PXE". This card does not follow full y the PXE specification. So we have to call PXE code in "real mode" (like do the bios) instead of "protected mode".

---

<http://www-128.ibm.com/developerworks/forums/dw_thread.jsp?message=13913226&cat=15&thread=149941&treeDisplayType=threadmode1&forum=1068#13913226>

Daniel Lindgren


_______________________________________________
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.

Lindgren Daniel wrote:
>
> Found this on a Rembo Toolkit 4 forum, regarding Yukon and PXE problems:
>
> ---
>
> The fix IS to to use "disable enhanced PXE". This card does not follow full y the PXE specification. So we have to call PXE code in "real mode" (like do the bios) instead of "protected mode".
>

But PXELINUX *does* call PXE in real mode.

My personal guess is that the Yukon scribbles in areas of high memory it
isn't supposed to.

-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 26-04-2007 om 08:51 schreef H. Peter Anvin:
> Lindgren Daniel wrote:
> >
> > The fix IS to to use "disable enhanced PXE".
> > This card does not follow fully the PXE specification.
> > So we have to call PXE code in "real mode" (like do the bios)
> > instead of "protected mode".
> >
>
> But PXELINUX *does* call PXE in real mode.
>
> My personal guess is that the Yukon scribbles in areas of high memory
> it isn't supposed to.


Could pxelinux running with debug option enable this?


Another approach:

Add two functions to PXElinux:

- one function is overwriting high memory with 0x55
- the other function reports addresses in high memory that don't
contain 0x55

Could that prove unsupposed high memory usage?


HtH
GSt

_______________________________________________
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:
>
> Could pxelinux running with debug option enable this?
>

Enable what?

> Another approach:
>
> Add two functions to PXElinux:
>
> - one function is overwriting high memory with 0x55
> - the other function reports addresses in high memory that don't
> contain 0x55
>
> Could that prove unsupposed high memory usage?

Interesting thought. Not all that hard to do.

-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 28-04-2007 om 09:37 schreef H. Peter Anvin:
> Geert Stappers wrote:
> >
> > Could pxelinux running with debug option enable this?
Could pxelinux be run with debug option enabled ?
> >
>
> Enable what?

Debug options, assuming they are available.


> > Another approach:
> >
> > Add two functions to PXElinux:
> >
> > - one function is overwriting high memory with 0x55
> > - the other function reports addresses in high memory that don't
> > contain 0x55
> >
> > Could that prove unsupposed high memory usage?
>
> Interesting thought. Not all that hard to do.


Thanks for the compliment

To prevent getting lost in the list archive, I suggest

diff --git a/TODO b/TODO
index 93f3194..c5db6bd 100644
--- a/TODO
+++ b/TODO
@@ -4,6 +4,9 @@

- PXELINUX: Support changing the default server and boot file prefix?

+- PXELINUX wish: add function that writes 0x55 in highmemory
+- PXELINUX wish: add function that report addresses that not contian 0x55
+
- Support loading a new configuration file.

- Library support for "shuffle and boot" extension.



HtH
GSt

_______________________________________________
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.

HPA
I can probably manage send you a problem Fujitsu, We have a customer
with 1000 Fujitsu Lifebook P1610 units that refuse to boot the menu or
vesamenu, same thing happens with Dell Latitude D620 units (same Yukon
NIC). Would sending you a unit help fix the problem? The only way
around this right now is to use the boot.msg file as a text based menu

-----Original Message-----
From: syslinux-bounces@zytor.com [mailto:syslinux-bounces@zytor.com] On
Behalf Of H. Peter Anvin
Sent: Wednesday, April 25, 2007 11:18 AM
To: Lindgren Daniel
Cc: syslinux@zytor.com
Subject: Re: [syslinux] Yukon NIC - again

Lindgren Daniel wrote:
>
> Could I be of assistance in finding the problem? I can't send any
> machines, but I'd be happy to run whatever tests needed to resolve
this
> issue.
>

Unlikely. It's like finding a needle in a haystack since I have no way
of reproducing the problem.

Try reporting the problem to your vendor. It *might* cause some
activity, especially if you represent a sizable customer.

-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.



****************IMPORTANT--PLEASE READ*******************
This electronic message, including its attachments, is COMPANY CONFIDENTIAL and may contain PROPRIETARY or
LEGALLY PRIVILEGED information. If you are not the intended recipient, you are hereby notified that any use,
disclosure, copying, or distribution of this message or any of the information included in it is unauthorized and strictly prohibited.
If you have received this message in error, please immediately notify the sender by reply e-mail and permanently delete this
message and its attachments, along with any copies thereof. Thank you

_______________________________________________
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.

Matt Barbieri wrote:
> HPA
> I can probably manage send you a problem Fujitsu, We have a customer
> with 1000 Fujitsu Lifebook P1610 units that refuse to boot the menu or
> vesamenu, same thing happens with Dell Latitude D620 units (same Yukon
> NIC). Would sending you a unit help fix the problem? The only way
> around this right now is to use the boot.msg file as a text based menu
>

It might, however:

- I can't guarantee that I will have time to work on the problem.
- I can't guarantee I can find the source of the problem.
- I can't guarantee the problem is fixable.
- I usually don't accept hardware if you want it back.

I have to say all that, because even if you send me hardware, it's still
my spare time kind of thing. I of course want to see syslinux work as
well as possible, and I'd like to get this problem resolved, I just
can't make any promises.

-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.