January 20, 201313 yr Hey, first off, thanks to Tom for all the hard work! So, I've just upgraded from 5.0-rc3 to the latest rc-10 release, and everything went fine, except for the speed of my Intel Pro/1000 Nic seems to be stuck on 100, and I can't change it (using the eth0 command) to 1000? The reason I noticed was slow data transfer to Unraid across the network, and I initially thought it might have been the excess memory issue mentioned elsewhere (I had 8Gb RAM - though incidentally, despite showing up as 8Gb in rc3, since upgrading to rc10, it only showed as 4Gb - so I pulled out 4Gb, but it's made no difference). Please see the below - I'm not sure if the "Interrupt Throttling Rate" might be the culprit? Any ideas gratefully received! Jan 20 01:05:20 Fro-NAS kernel: e1000e: Intel® PRO/1000 Network Driver - 1.9.5-k Jan 20 01:05:20 Fro-NAS kernel: e1000e: Copyright© 1999 - 2012 Intel Corporation. Jan 20 01:05:20 Fro-NAS kernel: e1000e 0000:00:19.0: setting latency timer to 64 Jan 20 01:05:20 Fro-NAS kernel: e1000e 0000:00:19.0: (unregistered net_device): Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Jan 20 01:05:20 Fro-NAS kernel: e1000e 0000:00:19.0: irq 46 for MSI/MSI-X Jan 20 01:05:20 Fro-NAS kernel: usb 1-2: new high-speed USB device number 2 using ehci_hcd Jan 20 01:05:20 Fro-NAS kernel: scsi0 : usb-storage 1-2:1.0 Jan 20 01:05:20 Fro-NAS kernel: e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:23:7d:be:55:81 Jan 20 01:05:20 Fro-NAS kernel: e1000e 0000:00:19.0: eth0: Intel® PRO/1000 Network Connection Jan 20 01:05:20 Fro-NAS kernel: e1000e 0000:00:19.0: eth0: MAC: 8, PHY: 8, PBA No: FFFFFF-0FF Jan 20 01:05:20 Fro-NAS kernel: ata_piix 0000:00:1f.2: version 2.13
January 20, 201313 yr Bad cat 5e or cat 6 cable can cause this. (100Mbs uses only 4 wires-- 1000Mbs use all 8.)
January 20, 201313 yr Author Thanks - however changing the Cat cables makes no difference (and Unraid connected at a gig using the original cables in rc-03)....??
January 20, 201313 yr Author Ignore me - FIXED - turns out it was an issue with my network switch.... Cheers
Archived
This topic is now archived and is closed to further replies.