Re: gPXE & vesamenu.c32
Jurgen Gunter Maulko <[email protected]> Sun, 27 Sep 2009 21:18:41 -0300
| Newsgroups | gmane.network.etherboot.user |
|---|---|
| Message-ID | <[email protected]> |
Shao, maybe the following is of interest to someone. I had (mark the past tense) the same problems as Iain and even his workaround (earlier versions) did not work for me. "Intuition" told me to fiddle around with the bios settings of the vga-adapter with the following results: 1) Power-on w/64 MB video ram: black screen with menu.c32, grey one with vesamenu.c32, no visible menu entries. 2) Power-on w/32MB video ram: same as 1) 3) Power-on w/16MB video ram: fully functional menu.c32 and vesamenu.c32. If I cold boot (power-on) with 16MB video ram and let the machine boot up to the menu and then do warm boot (Crt-Alt-Del), change the video ram in the bios to say 64MB menu.c32 and vesamenu.c32 will work. If I do a power-on with 64 or 32 MB set in the bios, menu.c32 and vesamenu.c32 won´t work. I tested and confirmed this behaviour several times. I use the pre-compiled binaries of syslinux-3.70 with the latest gpxe from rom-o-matic. Best Regards Juergen _________________________________________________________________ http://redirect.gimas.net/?n=M0906xWLM2009_WW Neu: Messenger 2009! Hier kostenlos downloaden! ------------------------------------------------------------------------------ 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