PXES 8 not working (but 5 did)

Chris <[email protected]>
Newsgroups gmane.linux.pxes.devel
Organization NAIC
Message-ID <[email protected]>
Hello.  I am trying to upgrade our workplace from 0.5.1-35 to .8.

I had good luck with 5.1, but I was interested in some of the new features.

I have tested my tftp, and it seems to work, I can pull the kernel image just 
fine.  I have increased by ramdrive size to 32M in lilo (for all options):

=====================<snip>==========================
.
.
.
label 1
   kernel vmlinuz-2.4.20-10pxes.i586
   append ramdisk_size=32768 ro video=vesa vga=771 console=null 
initrd=pxes-0.8.
squash root=/dev/ram

label pxes
   kernel vmlinuz-2.4.20-10pxes.i586
   append ramdisk_size=32768 ro initrd=pxes-0.8.initrd root=/dev/ram

label 2
   kernel vmlinuz-2.4.20-10pxes.i586
   append ramdisk_size=32768 ro video=vesa vga=771 console=null 
initrd=pxes-0.8.
initrd root=/dev/ram

label initrd
   kernel vmlinuz-2.4.20-10pxes.i586
   append ramdisk_size=32768 ro video=vesa vga=771 console=null 
initrd=pxes-0.8.
initrd root=/dev/ram
======================</snip>===========================

What happens is this:  I get my graphical lilo screen, and everything looks 
good.  I get a boot: prompt and all my lilo choices.  If I choose the 
default, I get the framebuffer pxes icon at the top of the screen with a 
cursor under it, then it just hangs.

If I choose the novesa option, then I get this:
"Uncompressing Linux... Ok, "
Then it just hangs.

I have rebuild my image a dozen times now, and have it stripped way down with 
X3 now and no fun options.  Nothing helps

Can someone help me please?

Thank you!

Chris


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.