PXE does not work with Porteus 5.0(.1)

[tobira]

Dear All,
I would like to supply 60 laptops with Porteus 5.01 and Google Chrome via PXE. I have made the respective installation for this purpose. I then started Porteus in PXE server mode. When I now boot a client in PXE mode, I initially get the following message:

Code: Select all

PXELINUX 4.06 2012-10-23 Copyright (C) 1994-2012 H. Peter Anvin et al 
!PXE entry point found (we hope) at 9DA9:0104 via plan A 
UNDI code segment at 9DA9 len 1A7F 
UNDI data segment at 9C19 len 1900 
Getting cached packet 01 02 03 
My IP address seems to be COA8B26C 192.168.178.108 
ip=192.168.178.108:192.168.178.83:192.168.178.83:255.255.255.0 
BOOTIF=01-08-00-27-e5-d4-ef 
SYSUUID=911f90be-9714-cc43-9946-51fe0676776a 
TFTP prefix: /
Trying to load: pxelinux.cfg/default                ok 
vesamenu.c32: not a COM3ZR image 
boot:

If I now enter "GUI" after boot., the process continues until I finally receive the following message:

Code: Select all

^ searching for porteus-v5.0-x86_64.cfg file 
udhcpc: started, v1.36.1 
udhcpc: broadcasting discover 
udhcpc: broadcasting discover 
udhcpc: broadcasting select for 192.168.178.108, server 192.168.178.83 
udhcpc: lease of 192.168.178.108 obtained from 192.168.178.83, lease time 429496 
7295
deleting routers 
adding dns 192.168.178.83 

Porteus data not found. 
You are maybe using an unsupported boot device (eg. SCSI or old PCMCIA). 
Workaround: Copy the directory /porteus from your boot device to an IDE/SATA 
disk, eg. to /mmt/sda1/porteus or C:\porteus. Then try to boot again. 
Make sure that your boot parameters (cheatcodes) are correct. 
In case of booting over network - check if the driver for your NIC 
is included in initrd image. 

Press space/enter to unmount all devices and reboot or any other key 
to drop to the debug shell.

What am I doing wrong? Everything worked in Porteus 4.9.

[Ed_P]

Which Porteus ISO did you install from?

Are you installing directly to the laptops or to USB drives? How are the drives formatted?

Post your porteus-v5.0-x86_64.cfg file so we can see your cheatcodes.

[i3slkiller]

Porteus-v5.01 bug reports (Post by emfer #98396)

[tobira]

Thank you so much, i3slkiller!

It works for me this way. The Porteus is installed in a virtual machine, so I had to change sr0 to sda1.