October 27, 200619 yr Author Since you can login on the console, type this command: ifconfig This is alot like the Windows 'ipconfig' command. It will show the status of your network i/f's. You should see a block of information that looks something like this: root@Server:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:11:11:95:33:DD inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:39821291 errors:2 dropped:0 overruns:0 frame:1 TX packets:41990649 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3719547713 (3547.2 Mb) TX bytes:531858293 (507.2 Mb) Base address:0x9c00 Memory:ff800000-ff820000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3260 (3.1 Kb) TX bytes:3260 (3.1 Kb) In the info for 'eth0' look for 'inet addr' - this is your IP address (192.168.0.2 in above). You can try putting this address in your browser address bar to see if it can connect that way.
October 28, 200619 yr OK, I run the ifconfig, the local part returns a loopback address but no ethernet port, I guess that explains why I cannot log on from a browser or telnet. So how do I make the ethernet port start? It still works ok in the old version.
October 29, 200619 yr Author Type this command at the console: modprobe e1000 This will force-load the intel driver if the network h/w is detected. If this works and you get network connectivity, then first thing to do is capture your syslog so we can see why this doesn't happen at start-up. Never seen this before with the intel driver.
November 4, 200619 yr Finally got a chance to try that... modprobe 1000 returns an error, also tried modprobe 100 (in case mines only a 10/100 board). Odd that this doesn't work bu the old version does??
November 4, 200619 yr Author That's 'modprobe e1000' (you need the 'e' before the '1000'). 'e1000' is the name of the Intel network driver. The 'modprobe' command installs the driver and any code the driver depends on.
November 15, 200619 yr Author I believe there's an issue with the Intel driver in the 3.0 release - I'll be posting a new download soon that should fix this problem.
November 15, 200619 yr Author rhinoman- There's a new release available for you to try on the download page called "3.1-beta2". (The only changes so far in 3.1-beta2 vs. 3.0 are updates to Intel and Marvell network drivers, as well as an additional network driver for AMD-based nForce4 motherboards.)
Archived
This topic is now archived and is closed to further replies.