Syslinux - Jul 2008 - memdisk image problems on shuttle hardware

hpa,

Seeing your post about 3.71, I wanted to get a message out even though I 
don't have the stats right now.

I am having a problem with memdisk with a lot of shuttle computers, but 
also affects a variety of other hardware (low though, 5%? less?).

The image that I can most reliably test against is the Hitachi Drive 
fitness Test. 
(http://www.hitachigst.com/hdd/support/downloads/dft32_v413_b00_install.IMG)

It boots the image normally, then spits out Operating System not found 
(or some such, basically the image loads but doesn't work)

I think I saw at one point that an ancient version of syslinux/memdisk 
worked fine (2x era), but I am not positive. I will be sure to test that 
  asap to confirm.

I have tried the various raw/bigraw/safeint/edd/noedd without luck.

Any chance you would have access to a shuttle you can test against? 
otherwise I will investigate setting up a serial console to the box and 
getting you remote access.

I have tested against 3.70 and still have the same problem. By chance is 
there a way to set a pause or some such, as some of the output of 
memdisk scrolls off the screen too fast for me to read.

I will follow up hopefully tonight with what output I do see. (problem 
being it's away from my workstation, and I don't have a camera that I 
think would give a clear picture)

-Andrew

Andrew Stuart wrote:
> hpa,
> 
> Seeing your post about 3.71, I wanted to get a message out even though I 
> don't have the stats right now.
> 
> I am having a problem with memdisk with a lot of shuttle computers, but 
> also affects a variety of other hardware (low though, 5%? less?).
> 
> The image that I can most reliably test against is the Hitachi Drive 
> fitness Test. 
>
(http://www.hitachigst.com/hdd/support/downloads/dft32_v413_b00_install.IMG)
> 
> It boots the image normally, then spits out Operating System not found 
> (or some such, basically the image loads but doesn't work)
> 
> I think I saw at one point that an ancient version of syslinux/memdisk 
> worked fine (2x era), but I am not positive. I will be sure to test that 
>   asap to confirm.
> 
> I have tried the various raw/bigraw/safeint/edd/noedd without luck.
> 
> Any chance you would have access to a shuttle you can test against? 
> otherwise I will investigate setting up a serial console to the box and 
> getting you remote access.
> 
> I have tested against 3.70 and still have the same problem. By chance is 
> there a way to set a pause or some such, as some of the output of 
> memdisk scrolls off the screen too fast for me to read.
> 
> I will follow up hopefully tonight with what output I do see. (problem 
> being it's away from my workstation, and I don't have a camera that
I
> think would give a clear picture)
> 
Left off some useful information. I am using a matched pxelinux/memdisk, 
but the problem also occurs with isolinux/memdisk (also matched)

Andrew Stuart wrote:
> 
> Any chance you would have access to a shuttle you can test against? 
> otherwise I will investigate setting up a serial console to the box and 
> getting you remote access.
> 
I do have several Shuttle boxen, but I haven't seen this on any of these 
machines.
> I have tested against 3.70 and still have the same problem. By chance is 
> there a way to set a pause or some such, as some of the output of 
> memdisk scrolls off the screen too fast for me to read.
If you put "pause" on the command line, it will stop before booting.

	-hpa