gpxe and memdisk could not boot winpe disk image

Dear all

 

After failure of booting winpe 2.0 disk image in gpxe + memdisk with slam protocal. I have tried other protocol, tftp and http, the winpe boot still stuck before show the desktop(the pe image itself is loaded). Because pxelinux + memdisk works well, so I think it maybe a problem with gpxe or gpxe+memdisk.

 

Also I test with winpe 2005 disk image, it still failed, but with more information. First the desktop background could show partially without upper row(strip) 

Then BSOD happened with the following message:

<<

a problem has....

    framebuf

if this ...

The device driver got stuck in an infinite loop....

Please check you hardw...

Technical information : 

*** Stop: 0x000000EA (0x84c29a60,0x84F01c48,0x84c263e8,0x00000001)

framebuf
>>

 

I google it, someone says it is related to bad memory, others are graphics card.

 

I guest it may related to the memory management compatibility issue of gpxe with memdisk. 

So I want some hints to debug the issue, check e820 memory map, or ... ? 

 

BTW, occassionally, the boot may succeed one or twice one day. But most of them failed.

 

Anyone who want to get the winpe disk image for test, please contact me. 

 

Regards!

 

Paul


Date: Fri, 18 Sep 2009 20:55:21 +0000
Subject: Re: Re: [Etherboot-discuss] how to script for SLAM
From: [email protected]
To: [email protected]; [email protected]

Paul,

If you're able to use PXELINUX to load WinPE via MEMDISK but not from gPXE, you may want to try chainloading PXELINUX with your modified gPXE binary and then loading MEMDISK and WinPE from PXELINUX under gPXE, which at that point *should* support the SLAM protocol.

When PXELINUX is chainloaded with gPXE, gPXE's protocol support is extended to PXELINUX.

There's a DHCP option that you can set for PXELINUX that determines the "TFTP Prefix" you see when booting a client, which you can set to "x-slam://slamserver" to force use of the SLAM protocol. I don't know which option it is off the top of my head, though.

Also, someone else may be able to add some more information, as there may be some sort of issue with the use of SLAM itself. Though that's just a guess on my part.

Good luck, Paul.

-Andrew Bobulsky

On Sep 18, 2009 10:38am, ShenQiyu <[email protected]> wrote:
> 
> Dear Shao,
> 
>  
> 
> Thanks!
> 
>  
> 
> Following your guide, I have completed the test.
> 
>  
> 
> But I could only boot winpe 2.0 with MEMDISK in VMWare virtual machine with 512M or 1G memory .
> 
>  
> 
> When I use Lenovo T400 notebook, it failed .
> 
>  
> 
> The winpe image could be downloaded and the initial boot is successful. The windows boot loader started and shows that winpe.wim is loaded. But after that the screen will show nothing. And I tried tftp and http protocol to download the image, the result is the same. 
> 
>  
> 
> Then, I try it with PXELINUX and MEMDISK, the booting is successful into PE environment every time.
> 
>  
> 
> When break the MEMDISK before the actual boot, there could be found something different:
> 
> With gpxe, the ramdisk is at 0x8f800000, but with pxelinux, the ramdisk is a little higher at 0x966ae000.
> 
>  
> 
> The machine has 4G memory and the winpe image size is about 112M.
> 
>  
> 
> Could please anyone give me some hints for it?
> 
>  
> 
> Regards!
> 
>  
> 
> Paul
>  
> > Subject: RE: [Etherboot-discuss] how to script for SLAM
> > Date: Fri, 28 Aug 2009 11:29:20 -0400
> > From: [email protected]
> > To: [email protected]
> > CC: [email protected]
> > 
> > Good day Paul,
> > 
> > You asked about using gPXE to fetch and load a Windows PE environment
> > utilizing MEMDISK.
> > 
> > Your first question seemed to be concerning HTTP versus TFTP. In your
> > sample script, replace
> > 
> > http://webserver/
> > 
> > with
> > 
> > tftp://tftpserver/
> > 
> > and that should do the trick.
> > 
> > Your second question concerned the SLAM protocol, so you might enjoy a
> > look at the gPXE source code file gpxe/src/net/udp/slam.c It sort of
> > looks like you'd have to replace
> > 
> > http://webserver/
> > 
> > with
> > 
> > x-slam://slamserver/
> > 
> > as well as to enable the SLAM protocol in a gPXE compilation, by editing
> > gpxe/src/config/general.h and changing the line
> > 
> > #undef DOWNLOAD_PROTO_SLAM
> > 
> > to
> > 
> > #define DOWNLOAD_PROTO_SLAM
> > 
> > and then recompiling gPXE.
> > 
> > I hope this helps.
> > 
> > - Shao Miller
> 
> 毛好煤Ｃ没碌路煤碌禄盲隆拢 好煤Ｃ没碌隆拢
>

_________________________________________________________________
Messenger掳虏芦卤拢禄陇拢卢芒路赂麓得鲁漏露麓拢卢卤拢禄陇Messenger掳虏芦拢隆
http://im.live.cn/safe/

------------------------------------------------------------------------------
Come build with us! The BlackBerry&reg; Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9&#45;12, 2009. Register now&#33;
http://p.sf.net/sfu/devconf

_______________________________________________
Etherboot-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss