I've got a working pxe environment, now with latest pxelinux, 6.01. I can boot pxe to a menu I prepared with several options. The Clonezilla stable 486 (2.1.2-43) boots and works, but I can't make the other version (686-pae) to boot. pxelinux tries to load vmlinuz, then initrd.img, then says something like "invalid arguments". But the arguments are the same between both versions!.
If I try a previuous version of pxelinux (4.04) the message is "invalid or corrupt kernel image". I don't think this is true.
I also have problems with gparted live, so I don't think is a Clonezilla live-specific problem, but maybe there is someone out there with the same issue.
By the way, thanks to the developers for their great work.
Any help would be appreciated.
Jesus.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, Steven. Thanks for your answer. It's embarrassing, but the machine was right: the kernel file was corrupted. I guess the proxy or antivirus scrambled the zip files somehow.
Sorry folks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I've got a working pxe environment, now with latest pxelinux, 6.01. I can boot pxe to a menu I prepared with several options. The Clonezilla stable 486 (2.1.2-43) boots and works, but I can't make the other version (686-pae) to boot. pxelinux tries to load vmlinuz, then initrd.img, then says something like "invalid arguments". But the arguments are the same between both versions!.
If I try a previuous version of pxelinux (4.04) the message is "invalid or corrupt kernel image". I don't think this is true.
I also have problems with gparted live, so I don't think is a Clonezilla live-specific problem, but maybe there is someone out there with the same issue.
By the way, thanks to the developers for their great work.
Any help would be appreciated.
Jesus.
I did not try PXELinux 6.01 here. However, I am sure PXELinux 5.10 work.
Did you try PXELinux 5.10?
Steven.
Hi, Steven. Thanks for your answer. It's embarrassing, but the machine was right: the kernel file was corrupted. I guess the proxy or antivirus scrambled the zip files somehow.
Sorry folks!
No problem. Enjoy!
Steven.