March 22, 200719 yr I just upgraded to 4 and the NIC wont come up (no lights at all) Its a Dlink DGE-530T 10/100/1000 Gigabit Desktop Adapter http://www.dlink.com/products/?sec=1&pid=284 It worked just fine before. What can I do to bring it back to life? Rob
March 22, 200719 yr Ok, that card is problematic, see http://www.linuxcompatible.org/Driver_for_DLink_DGE-530T_Gigabit_PCI_on_FC4_t33856.html http://www.ubuntuforums.org/showthread.php?t=187770 I'll fix it, but probably will have to wait until tomorrow.
March 22, 200719 yr I have also upgraded to the Version 4 Beta and am having NIC problems too. (Different NIC) The NIC I have is on the mobo and is a Intel Pro/1000. This mobo/NIC combination works perfectly for the 3.0 and 3.1 Beta releases. The only error that shows in the syslog is: "Initialization complete, link beat not detected" Using "ethtool eth0" displays: Speed: unknown! Duplex: unknown! Link Detected: No Ip adresses and routes look normal, but the link does not function at all. Hope this helps with testing. Jerry
March 23, 200719 yr I have also upgraded to the Version 4 Beta and am having NIC problems too. (Different NIC) The NIC I have is on the mobo and is a Intel Pro/1000. This mobo/NIC combination works perfectly for the 3.0 and 3.1 Beta releases. The only error that shows in the syslog is: "Initialization complete, link beat not detected" Using "ethtool eth0" displays: Speed: unknown! Duplex: unknown! Link Detected: No Ip adresses and routes look normal, but the link does not function at all. Hope this helps with testing. Jerry We have several systems here which use Intel Pro/1000. Some questions: 1) Which motherboard? 2) In a telnet window, if you type command lsmod does it list 'e1000' module? 3) If answer to 2 is 'no', try command: modprobe e1000 and tell me what happens. 4) If answer to 2 is 'yes', try unpluging ethernet cable, wait a few seconds, plug back in & see if syslog messages result.
March 23, 200719 yr We have several systems here which use Intel Pro/1000. Some questions: 1) Which motherboard? 2) In a telnet window, if you type command lsmod does it list 'e1000' module? 3) If answer to 2 is 'no', try command: modprobe e1000 and tell me what happens. 4) If answer to 2 is 'yes', try unpluging ethernet cable, wait a few seconds, plug back in & see if syslog messages result. 1. Motherboard is ASUS P4C800-E 3.2G processor 1GB RAM. 2. Can't use Telnet as network does not function..... Logging in on console and running lsmod module size used by ======================= e1000 110848 0 3. N/A 4. Plugging and unplugging network cable does not create any entries in the syslog. Link lights are on (when cable connected) on both the motherboard and the ethernet switch I am using. Jerry
March 23, 200719 yr 2. Can't use Telnet as network does not function..... Logging in on console and running lsmod Doh! From console, type: ifconfig Do you see an entry in there for "eth0"? If so, try ifconfig eth0 up
March 23, 200719 yr 2. Can't use Telnet as network does not function..... Logging in on console and running lsmod Doh! From console, type: ifconfig Do you see an entry in there for "eth0"? If so, try ifconfig eth0 up ifconfig shows the eth0 NIC card UP and all addresses are correct. Netstat also shows all routes to be correct. But no traffic flows, the activity light never blinks. As a test of my setup, I installed a GA311 Netgear NIC card (uses a R8169 chip) and everything works perfectly. I just prefer the Intel NIC because it runs about 20% faster. So, I guess I am back to hoping the e1000 driver gets updated or patched. Jerry
March 23, 200719 yr PiDD - try 4.0-beta3 to see if your Dlink card is now recognized. JerryC - try 4.0-beta3 to see if your Intel Pro/1000 is now functional.
March 23, 200719 yr PiDD - try 4.0-beta3 to see if your Dlink card is now recognized. JerryC - try 4.0-beta3 to see if your Intel Pro/1000 is now functional. Sorry that I was not as fortunate as PiDD. The e1000 driver still does not work with the NIC on my ASUS motherboard.. I took some time and retested both the Netgear GA311 and Dlink DGE-530T and found them both to work perfectly. I can only guess that the newest e1000 driver has some incompatability with the Intel 82547EI chip that is used on the ASUS motherboard. I hope someone out there will be testing the Intel PRO/1000 PCI version to see if that works. The PCI card uses a different chip than the motherboard version. Thanks for the help. Jerry
March 24, 200719 yr Here's the link for the Intel driver that is in 4.0-beta3. It should support that chip. Perhaps if I can see the syslog, we can figure out what's going wrong. Here's a way you can capture if for me: 1. Boot server normally. 2. From console, type this: cp /var/log/syslog /boot/syslog 3. Now unplug flash from server, plug into your PC. You should see the syslog file on the flash. 4. Email the syslog file as an attachment to [email protected]
March 25, 200719 yr Mobo: Asus P5LD2-SE R2.0 (RTL8111B PCI-E Gb LAN controller) I'm getting REALLY slow speeds reading from this Mobo under beta4, I went straight from beta2 to beta4 and now can't watch anything. Xfer rate approx 0.36Mbps. Some info:- ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000033 (51) Link detected: yes ifconfig eth0 Link encap:Ethernet HWaddr 00:1A:92:09:A0:34 inet addr:10.0.0.10 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1713 errors:0 dropped:0 overruns:0 frame:0 TX packets:3379 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:177450 (173.2 KiB) TX bytes:3982875 (3.7 MiB) Interrupt:17 Base address:0xa000 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Transfers to this server are fine, pretty fast actually. Mark.
Archived
This topic is now archived and is closed to further replies.