Re: gpxe and memdisk could not boot winpe diskimage

Dear Andrew,

 

Thanks!

 

I followed your guide and try again. But it seems not work.

 

I could do any further test and try if you want to.

 

Regards!

 

Paul



Subject: Re: [Etherboot-discuss] gpxe and memdisk could not boot winpe diskimage
From: [email protected]
Date: Sun, 20 Sep 2009 21:14:46 -0400
CC: [email protected]
To: [email protected]


Paul,


Shao and I have done some work loading MEMDISK via gPXE.


If I recall correctly, you'll want to initrd your image, and then chain MEMDISK.


Something like:


initrd http://webserver/winpe.hdd
chain http://webserver/memdisk


Give that a try if you could.


Best of luck!


-Andrew Bobulsky




On Sep 20, 2009, at 8:55 PM, ShenQiyu wrote:

Dear Shao,
 
The disk image is not compressed. The size is about 111M. Actual, the WINPE itself is loaded correctly(winpe boot progress show it) but the system could not startup.
 
I use the MEMDISK version 3.82. MEMDISK is loaded first in gPXE, then the initrd.
 
Further, I have notice that MEMDISK shows the disk image is loaded in different address:
 
It is at 0x8f800000, length 0x06dd1c00 with gPXE -> MEMDISK is and 0x8f800000, length 0x06dd1c00 with gPXE -> PXELINUX -> MEMDISK.
The new int13 address is at 8fc0000a and 9340000a respectively.
 
So we could see the new int13 address 8fc0000a is obviously in the range of 0x8f800000, length 0x06dd1c00 which should be the disk image in the gPXE -> MEMDISK case. But the new int13 address is out of the range of disk image in the gPXE -> PXELINUX -> MEMDISK case.
 
Is this a potential problem the int13 address in the range of disk image?
 
Thanks!
 
Paul

> Subject: RE: [Etherboot-discuss] gpxe and memdisk could not boot winpe diskimage
> Date: Sun, 20 Sep 2009 14:34:41 -0400
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> 
> Good day Paul,
> 
> In regards to your "gPXE -> MEMDISK" issue, where "gPXE -> PXELINUX ->
> MEMDISK" seems to work:
> 
> Is your HDD image compressed, by any chance? I've noticed that "gPXE ->
> MEMDISK" seems to have troubles when decompressing large images. If it
> is compressed, could you please try a test without compression?
> 
> gPXE and PXELINUX certainly do provide different E820 maps, which is
> likely inevitable.
> 
> Which version of MEMDISK are you using?
> 
> Are you loading the initrd first or the MEMDISK kernel first in gPXE?
> 
> - Shao Miller



梅卤戮娄驴矛碌拢卢虏禄麓? 驴矛梅拢卢卤娄拢隆⒚铆隆鲁枚! 垄录麓拢隆 ------------------------------------------------------------------------------
Come build with us! The BlackBerry® 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-12, 2009. Register now!
http://p.sf.net/sfu/devconf_______________________________________________
Etherboot-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/etherboot-discuss


_________________________________________________________________
MSN庐锚矛碌盲拢卢虏茅驴麓MSN垄虏谩卤录盲拢卢庐隆帽麓贸陆卤
http://10.msn.com.cn

------------------------------------------------------------------------------
Come build with us! The BlackBerry® 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-12, 2009. Register now!
http://p.sf.net/sfu/devconf

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