[SOLVED] pxe-boot: porteus data not found

[326bd935]

when i try to pxe boot it starts, (loads kernel, ramdisk... )
...

but then: porteus data not found
and all i get is an ash promt with a partially set up root (without porteus data)

So... this must be a fault in my modified settings, scripts etc...
but its not.
I tried to boot from the official original porteus 1.0 cd and same problem.

But what i don't get is how can it come this far and then fail... unless the original doesnt work, i mean it loaded the kernel, its connected so why does it stop at:

udhcpc: ioctl 0x8933 failed: no such device
httpfs: couldn't connect socket
?

is this a problem with tftp? -- its running, i checked.
is this a problem with firewalls? -- porteus firewall was off and router firewall also off.

so is this a problem with dhcp? but seeing as it got this far i wouldnt think so.

my set up:
porteus ---> router --> the computer im trying to boot
router has dhcp on 192.168.2.200-220 and is working its own adress is ...1
porteus 192.168.2.159 and it manages to connect to this point so whats the problem?

Posted after 22 minutes 47 seconds:
and now i´ve played around with it and realised it cant connect to tftp
the only devicce in /proc/net/dev is lo
i tried it the other way around and the same thing, it can't connect to the network once the kernel is loaded and the error messages are because it
cant find network device
cant mount /mnt/httpfs

why wouldnt it find network devices and especially since it works fine booting directly
what do i do now?

[fanthom]

initrd does not contain all the network drivers (we dont want it huge) so you must add yourself your NIC driver to it.
please follow FAQ (and read all other Q/A as well):
http://porteus.org/faq.html#19

if you want to increase size of the initrd to include more drivers please use this script which gonna do it automatically:
http://porteus.org/info/docs/51-develop ... -file.html

cheers

[326bd935]

o sorry i forgot about that faq.

anyway i made an initrdnet.xz size 16666 KiB, with all network dirvers which is only used when booted using pxe as in the default pxe config.

[ereinion]

Hi to all!
I'm experiencing troubles in getting Porteus work over PXE.
I did all as said in faq (made initrd.xz bigger - 17000KB and inserted all modules from .../kernel/drivers/net/).
Bit no result - I cannot boot. And cannot ping. However on same machine LiveCD starting normally.

[fanthom]

Welcome on board ereinion,

just to be sure: did you run 'depmod -b /path_to_unpacked_initrd' after adding new drivers?
if you have a direct access to the PC's which does not boot over PXE then please boot Porteus from cd/usb and post here an output of following command:

Code: Select all

lspci -knn | egrep 'Network|Ethernet'

[ereinion]

Thanks for quick answer, fanthom!
Yes, I ran depmod -b (exactly - depmod -b /mnt/mydir), and if I load module manually - it loads, but network does not responding.
I can not load form cd or usb stick - there is none of them around at this moment, but first stage of booting over PXE working, so I can run lspci.
If I run full command - there is no output. On "lspci -knn" one of output strings is:
"02:00.0 Class 0200: 14e4:167d tg3" (previously I ran modprobe tg3).
PC is Samsung Q40 laptop without HDD.

Добавлено спустя 3 минуты 2 секунды:
Strange thing - 1-2 minutes after i ran modprobe - eth0 interface appeared...but don't receive address over DHCP

[fanthom]

which Porteus version are you running?
tg3 driver seems to be buggy as per fondfire report:
http://porteus.org/forum/viewtopic.php?f=61&t=1037

i have updated tg3 for 64bit rc1 of Porteus-1.2 so if you are running any other version then please consider compiling this driver from sources and remastering initrd once again.
(i think fondfire meant driver and not firmware)

also - when you run 'modprobe tg3' manually then please try 'udhcpc' and check if you get an IP.
in case when eth0 appears with lag you may try to edit linuxrc and add some 'sleep' before udhcpc.

[ereinion]

My version of Porteus is 1.1. So will try to test 1.2-rc

I think my trouble is thah lan driver modules does not starting at boot, only manually - after udhcpc with tg3 loaded - I got working network!
What files I need to edit to modify list of loading modules?

[fanthom]

What files I need to edit to modify list of loading modules?

there is no such list.
linuxrc is flexible - every *.ko which is found in /lib/modules/`uname -r`/kernel/drivers/net gets loaded and unloaded if no /sys/class/net/eth0 is found.

please start porteus with 'debug' cheat and on first stop run 'pcimodules' command. let me know if you get 'tg3' as an output.
also - please run 'modprobe tg3 && ls /sys/class/net' . if you get nothing then tg3 driver needs extra time to initialize. probably that's why linuxrc unloads tg3 driver and you get a failure. please measure how long takes tg3 to create eth0 in /sys/class/net.

[ereinion]

Sorry, I found my mistake - I did not set ip= parameter in 'pxelinux.cfg/default' file...
When I fixed it - Porteus begins to start
But my new trouble:
Couldn't copy '/sbin/init' file - you need at least 100KB free space inside initrd!!
I resized initrd from 17000K to 20480K, but error remains.

[Hamza]

Oh! An error related to linuxrc..fanthom should be able to help you. Did you modified the original initrd.xz from official iso ?

[fanthom]

I did not set ip= parameter in 'pxelinux.cfg/default' file...

IP should be assigned automatically unless you are using other (than Porteus) linux as PXE server.

if this is really the case then please read following post about httpfs client limitations:
http://porteus.org/forum/viewtopic.php? ... 1090#p8227
(in short words: please make sure that you are using monkey httpd in 32bits or webfs in 64bits)

But my new trouble:
Couldn't copy '/sbin/init' file - you need at least 100KB free space inside initrd!!
I resized initrd from 17000K to 20480K, but error remains.

on the next failure please run following commands:

Code: Select all

ls /union/sbin
cat /tmp/modules

first command should revel if anything is inserted to aufs and second which modules are there.
if you get empty /tmp/modules then either you have nothing in /porteus/base folder on the server side or you are using http server incompatible with httpfs client included in Porteus.

if you have all modules listed in /tmp/modules and you get proper listing from 'ls /union/sbin' command then please upload your initrd to mediafire.com and i'll check it on my PC.

[ereinion]

ls /union/tmp - No such file or directory
/tmp/modules - no output

I think there are two troubles...
1)I use Porteus as PXE server only in VirtualPC - in this way I got similar fail (no IP of http in config), may be because of virtualization software.
2)On real pc as PXE/DHCP/HTTP server acts Windows Server/IIS (on work), OS/2 Warp Server for e-Business (at home) ))))))
So may be I need install some light linux distro with monkey http server in virtual machine, do I?

[fanthom]

So may be I need install some light linux distro with monkey http server in virtual machine, do I?

yes - i recommend you running Porteus 32bit in VirtualBox at start as it has 'PXE server' booting option and you dont need to configure anything.

[Hamza]

1)I use Porteus as PXE server only in VirtualPC - in this way I got similar fail (no IP of http in config), may be because of virtualization software.

It's normal as you didn't set the Network Virtual Adapters to allow VirtualPC to gain an access to your real network adapter.
Otherwise, VirtualBox should works too