Here's my situation :? :
Installing latest release of Pluto Core - Hybrid. Everything looks good until trying to "Configure the Network with DHCP". Get the following error:
Quote
Network autoconfiguration failed
Your network is probably not using the DHCP protocol. Etc..
I recently purchased and installed 2 Realtek Semiconductor Co. RTL-8169 Gigabit Ethernet cards. Not sure if it's a compatibility issue.
I installed a recent release of Fedora and the network cards worked perfect, but once installing Pluto - nada.
Bear with me - new to networking. If anyone has any helpful info I would very much appreciate the help!
Thanks in advance!
~Jeffrey
Radu said he spoke to you and you're going to try Debian's newer installer, and if that works, we will upgrade our kick-start cd. Correct? Let us know what happens, please. Thanks.
Correct - I should have some time this evening to install - I'll post the results here.
Thanks for the help!
~J
Correct - I should have some time this evening to install - I'll post the results here.
Thanks for the help!
~J
Well, I tried installing the latest Debian release and am getting the same results..... Network still can't configure using DHCP....
Any other suggestions? Has anyone else had these issues?
Thanks again,
~J
Well, I tried the install on another machine and it went flawlessly. Still not sure what the issue was on the first box.
Thanks for the assistance Radu!
~J
I am having the same problem with the install.
"Network Autoconfiguration Failed"
This is the first time I have tried Pluto but I do currently use VDR with streamdev and VLC so I am not a total stranger to this stuff.
I have tried it on three out of the 5 's I have at home with the same results.
The PC's I have tried are custom home PC's, I do have in addition to the 3 already tested 2 Asus Pundit-R's but one is running VDR and the other 2003 Server and I dont really want to take them off-line.
Any Pointer would be apprecieated as this look a sweet project.
Regards
BoOtLoAdEr
08.26.2005
Build 2.0.0.28
Some cards seem to be problematic with Sarge's installer (especially Gigabit cards). I wish I had one of those 8169 cards here to play with, because it is supported (except for the recalled models which reported themselves as 8139 thus the wrong drivers were loaded). The cards that work here are: VIA Rhine II (on board), Broadcom BCM5705 (on board), Intel 82801BD PRO/100 (on-board), Intel eepro100 (PCI), Realtek 8139 (PCI).
I have the same problem. 7 different cards and 3 machines. Does anyone have a complete list of known cards, that work?
Another thought I had was compile the driver, but the "make" command doesn't seem to install with the Kick Start. I am open to any help here.
I'll probably compile a "supported network cards" list at some point in time according to what the modules report as "supported". Current kernel is 2.6.13.2.
In the mean time, which cards did you test?
Quote from: "radu.c"I'll probably compile a "supported network cards" list at some point in time according to what the modules report as "supported". Current kernel is 2.6.13.2.
In the mean time, which cards did you test?
Hi,
I'm not sure if related, but today I tried to network boot Asus Pundit for diskless MD (disabled on board network card, put int PCI 8139 and Etherboot CD ROM).
It gets kernel and image, but then cannot nfs mount, cause network is unreachable (I thought that 8139 is well supported card....).
Any idea ?
Thanks,
regards,
Rob.
I don't know Etherboot. Possibly it's doing something wrong. If you find a Boot ROM for the Realtek 8139 and it still doesn't boot, then I'm doing something wrong and I'll have to fix it.
Quote from: "radu.c"I don't know Etherboot. Possibly it's doing something wrong. If you find a Boot ROM for the Realtek 8139 and it still doesn't boot, then I'm doing something wrong and I'll have to fix it.
Hi,
I'll give some more info. I made bootable CD image for this card. It finds it on boot, the finds PXE server, gets kernel and initrd image and then starts linux system (but this is already part of diskless image)....
Then I guess it would need to nfs mount and there it stops cause network is not working. At that stage I cannot dmesg, ssh into it, to get more info...
Should diskless image work with 8139 card or can I somehow determine it to load proper kernel module (and what kernel module is for this card) ?
Regards,
Rob.
Quote from: "tinia"Quote from: "radu.c"I don't know Etherboot. Possibly it's doing something wrong. If you find a Boot ROM for the Realtek 8139 and it still doesn't boot, then I'm doing something wrong and I'll have to fix it.
Hi,
I'll give some more info. I made bootable CD image for this card. It finds it on boot, the finds PXE server, gets kernel and initrd image and then starts linux system (but this is already part of diskless image)....
Then I guess it would need to nfs mount and there it stops cause network is not working. At that stage I cannot dmesg, ssh into it, to get more info...
Should diskless image work with 8139 card or can I somehow determine it to load proper kernel module (and what kernel module is for this card) ?
Regards,
Rob.
You can mount the initrd in a temporary location and examine its contents: mount -o loop -t cramfs <initrd.img> /mount/point. Look in lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/net for 8139too. If it's not in there it means I missed it.
1. You'll have to uninstall the kernel from that image (easy way out):
chroot <diskless root> dpkg --purge kernel-image-2.6.13.2-vanilla-pluto-1-6862. Remove the /tftpboot/<ip> directory
3. Edit /usr/pluto/bin/Create_Diskless_FS.sh and add 8139too to the modules list
4. Run /usr/pluto/bin/Diskless_Setup.sh, which will call Create_Diskless_FS.sh, which will install the kernel back, which will create the initrd with that module in it
5. Should boot now.
Quote from: "radu.c"
You can mount the initrd in a temporary location and examine its contents: mount -o loop -t cramfs <initrd.img> /mount/point. Look in lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/net for 8139too. If it's not in there it means I missed it.
....
Hi,
I examined initrd image and module seems to be there....
dcerouter_260:~/mount/lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/net$ ls
3c509.ko b44.ko epic100.ko natsemi.ko sis900.ko via-rhine.ko
3c59x.ko e1000 fealnx.ko ne2k-pci.ko sk98lin yellowfin.ko
8139cp.ko e100.ko forcedeth.ko ne.ko tg3.ko
8139too.ko eepro100.ko hp100.ko pcnet32.ko tlan.ko
8390.ko eexpress.ko mii.ko r8169.ko tulip
dcerouter_260:~/mount/lib/modules/2.6.13.2-vanilla-pluto-1-686/kernel/drivers/net$
Can I somehow debug or trace what happens ?
Regards,
Rob.
The 8139too module is in your listing, so it's in there. I guess it doesn't get loaded automatically.
You can't easily trace what happens.
Here's how I do it:
1. rename the initrd.img to initrd.img.orig
2. mkdir i; mount -o loop -t cramfs initrd.img i
3. mkdir j
4. open mc and copy everything from i to j (cp -a complains about not being able to create hard links).
5. umount i
6. edit the scripts in the scripts/ directory: I but "set +x" for traces and "/bin/sh" as breakpoints
7. mkcramfs j initrd.img
8. boot diskless; repeat
Note: do this with the initrd in /tftpboot/<ip>. That's where the booting is done from.
Hi,
I found cause - non plug'nplay OS setting in Bios solved problem. But same PC worked ok under Suse ...
Thanks for help and sorry for inconvenience....
Regards,
Rob.
thats really handy to know - thanks for posting it, ill go check the setting on my machine. Was running fedora fine earlier, autodetected cards etc so i thought it was probably compatible.
Jason
Sorry getting back late.
As far as card manufactures go.. Dlink, 3Com, Kingston, Netgear and Intel. Some of them I have multiple models. I do have new info.
I was just given an old all intel P3 box. True intel board and processor. It only worked with the intel card, but it worked. After completing the Pluto install process, I have successfully tested two of the 3com's and the Kingston.
Just some thoughts here. It seems sarge has limited drivers and/or some mother boards with certain network cards don't work with sarge. The odd thing is they all seem to work with older versions on debain. I hope this helps.
I've had no joy - its a compaq D510 i'm running this on, and the BIOS is lacking in options!
I have some other NIC's I can try, looks like it is working though - link up, 100Mbps, downloaded some updates and sync'd the clock fine. I'm just getting this message on install... and its not letting pluto setup correctly.
Jason
I am trying to set this up with a single NIC, not sure if that would make any difference - I don't need this machine as a firewall, and the place its located has only one cable going to it!
Just enabled DHCP on my network, its gone through that part of the install fine, but I do want to use network boots!
Jason
I get the same message when trying to install Pluto. I've two NICs, one onboard (SiS I think)and a Realtek card. The install sees both of them and asks me to choose one. Regardless of which one I choose I get the error.
i.e"Network autoconfiguration failed Your network is probably not using the DHCP protocol"
If I choose the "Don't configure networking" option and carry on, Pluto installs, but won't load completely. It hangs at "Loading DCERouter"
However, if I connect the machine to an ADSL modem (which has it's own DHCP inbuilt) Pluto installs and starts perfectly.
Thinking I'd got around the error, I then connected it to a network switch along with another machine, but it is not accessible from the other machine on the network switch?
I'm going to try installing a diskless media director to see if that starts DHCP and also check the BIOS for non-PnP settings tonight.
I hope it works, I'm dying to get this thing going.
Paul