Networking issues with Haswell-based Linux increase Courvoisier consumption - Page 2

paulunderwood · 2013-06-29, 01:13

Dodgy cable, eh? Keep an eye on those LEDs.

I don't know why eth0 gets moved eth2. It would suggest you have 3 sockets. Perhaps you should disable the on-board ethernets in BIOS.

ewmayer · 2013-06-29, 03:03

Quote:

Originally Posted by paulunderwood

Dodgy cable, eh? Keep an eye on those LEDs.

I don't know why eth0 gets moved eth2. It would suggest you have 3 sockets. Perhaps you should disable the on-board ethernets in BIOS.

That was the very first thing I did, before attempting to install the NIC.

I feel in dire need need of a beer...

chalsall · 2013-06-29, 03:30

Quote:

Originally Posted by ewmayer

I feel in dire need need of a beer...

127.0.0.1/8...

Code:

[chalsall@burrow ~]$ ping 127.12.34.56
PING 127.12.34.56 (127.12.34.56) 56(84) bytes of data.
64 bytes from 127.12.34.56: icmp_seq=1 ttl=64 time=0.070 ms
64 bytes from 127.12.34.56: icmp_seq=2 ttl=64 time=0.069 ms
64 bytes from 127.12.34.56: icmp_seq=3 ttl=64 time=0.064 ms
^C

[chalsall@burrow ~]$ ping 127.255.255.254
PING 127.255.255.254 (127.255.255.254) 56(84) bytes of data.
64 bytes from 127.255.255.254: icmp_seq=1 ttl=64 time=0.093 ms
64 bytes from 127.255.255.254: icmp_seq=2 ttl=64 time=0.087 ms
64 bytes from 127.255.255.254: icmp_seq=3 ttl=64 time=0.069 ms
^C

For Christmas my girlfriend bought me a tee-shirt which says "There's no place like 127.0.0.1" (I'm not joking)....

paulunderwood · 2013-06-29, 03:33

I found this and other similar solutions. Comment out rather than delete!

Please post back the results of "cat /etc/udev/rules.d/70-persistent-net.rules" (or something similar) if you can't figure it out

( here is another solution )

xilman · 2013-06-29, 07:18

Quote:

Originally Posted by ewmayer

While trying the first, I noticed a 'cable unplugged' note in the mac's network-setup dialog ... that led me to discover the lack-of-LED cause, which is that the NIC's cable connector is bad - I have to manually jam the cable plug into the connector hard for the LEDs to come on and the above dialog's physical-connection-status message to change to the desired 'connected'.

[I say the NIC connector because the same cable worked just fine with the old mobo ... let's just say 'connection to the outside world is dodgy'.]

Anyhoo, even with one hand jamming the cable in while the other types 'shh...' ... no joy. Also reverted the netmasks on both sides to the previous values of 255.255.255.0 and retried (again keeping one eye on the connected-or-not status line in the macbook's dialog to make sure it read 'connected') - still nothing. Bloody hell.

BTW, I still have no idea what that 'rename eth0 to eth2' business is all about - can anyone explain why the old-setup eth0 wasn't OK?

Yeah, screwed me as well. Ethernet interfaces are now dynamically named specifically for the case of removable / re-configrable devices. Much the same as drives are to allow for USB and Bluetooth devices, so /dev/sdc can be different physical devices at different times. On a Gentoo box here, for instance, what used to be eth0 is now enp8s0 --- decoded as EtherNet Pci 8 Slot 0 or something like that. Just one link of many which may be useful to you: https://bbs.archlinux.org/viewtopic.php?id=157764

Paul

paulunderwood · 2013-06-29, 18:45

Ah yeah, Gentoo. I have a couple of Gentoo installations here. Configuring and compiling the kernel to add specific hardware is encouraged. I guess Ernst's on-board realtek network device would be a supported option

ewmayer · 2013-06-29, 19:38

FYI, I'll be in a position to fiddle with the system again in a couple hours.

Also, I'm running Debian, and my internet searches for drivers for the MSI mobo in question [cf. the Haswell preview thread in Hardware for exact specs] came up empty. How long does it typically take for such drivers to appear after a new mobo/cpu family hits market?

paulunderwood · 2013-06-29, 19:56

I think you have the same MSI Z87-G41 PC Mate mainboard as Prime95 has, which according to the manual from MSI has a Realtek® RTL8111G Gigabit LAN controller, the driver for which can be found here. Don't ask me how to install it

(ps: maybe that is not what you need as it is for a PCI-E NIC...)

Much easier is to "mv /etc/udev/rules.d/70-persistent-net.rules ~" and reboot

Ralf Recker · 2013-06-29, 20:12

Quote:

Originally Posted by ewmayer

FYI, I'll be in a position to fiddle with the system again in a couple hours.

Also, I'm running Debian, and my internet searches for drivers for the MSI mobo in question [cf. the Haswell preview thread in Hardware for exact specs] came up empty. How long does it typically take for such drivers to appear after a new mobo/cpu family hits market?

Kernel 3.10 might probably support it:

http://git.kernel.org/cgit/linux/ker...fcd4f16f78ccdf

http://git.kernel.org/cgit/linux/ker...8f4b95d9d48638

Kernel 3.9.6 is available at wheezy-backports. 3.10 should follow.

sdbardwick · 2013-06-29, 21:09

Uh oh, I might have started a sad series of events...

I assumed (incorrectly, as it turns out) that somehow MSI had used a "strange" chip on your [Ernst's] board like they did on my board.

Those Realtek 8111x chips are widely used; I'd be very surprised if recent (2007ish and later) Linux distros didn't support it out of the box.

So, if the jack on the Intel card really is dodgy (that would be...unusual) rather than the cable, you can just go back to the integrated LAN.

chalsall · 2013-06-29, 21:43

Quote:

Originally Posted by sdbardwick

So, if the jack on the Intel card really is dodgy (that would be...unusual) rather than the cable, you can just go back to the integrated LAN.

Just out of possible upside, he's an example (under a modern Linux) of what you can do which might help you:

Code:

[chalsall@backup ~]$ cat /proc/net/dev
Inter-|   Receive                                                |  Transmit
 face |bytes    packets errs drop fifo frame compressed multicast|bytes    packets errs drop fifo colls carrier compressed
    lo:39194972  466562    0    0    0     0          0         0 39194972  466562    0    0    0     0       0          0
   em1:521299157  950665    0    0    0     0          0    132872 38783350  417689    0    0    0     0       0          0
   em2:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
   em3:       0       0    0    0    0     0          0         0        0       0    0    0    0     0       0          0
   em4:2394583536 2076278    0    0    0     0          0    130086 83405122  995960    0    0    0     0       0          0

If you're willing to share your's, we might be able to assist further.

2013-06-29, 01:13	#12
paulunderwood Sep 2002 Database er0rr 3,739 Posts	Dodgy cable, eh? Keep an eye on those LEDs. I don't know why eth0 gets moved eth2. It would suggest you have 3 sockets. Perhaps you should disable the on-board ethernets in BIOS. Last fiddled with by paulunderwood on 2013-06-29 at 01:18

2013-06-29, 03:33	#15
paulunderwood Sep 2002 Database er0rr 7233₈ Posts	I found this and other similar solutions. Comment out rather than delete! Please post back the results of "cat /etc/udev/rules.d/70-persistent-net.rules" (or something similar) if you can't figure it out ( here is another solution ) Last fiddled with by paulunderwood on 2013-06-29 at 04:27

2013-06-29, 19:56	#19
paulunderwood Sep 2002 Database er0rr 7233₈ Posts	I think you have the same MSI Z87-G41 PC Mate mainboard as Prime95 has, which according to the manual from MSI has a Realtek® RTL8111G Gigabit LAN controller, the driver for which can be found here. Don't ask me how to install it (ps: maybe that is not what you need as it is for a PCI-E NIC...) Much easier is to "mv /etc/udev/rules.d/70-persistent-net.rules ~" and reboot Last fiddled with by paulunderwood on 2013-06-29 at 20:23

2013-06-29, 21:09	#21
sdbardwick Aug 2002 North San Diego County 5×137 Posts	Uh oh, I might have started a sad series of events... I assumed (incorrectly, as it turns out) that somehow MSI had used a "strange" chip on your [Ernst's] board like they did on my board. Those Realtek 8111x chips are widely used; I'd be very surprised if recent (2007ish and later) Linux distros didn't support it out of the box. So, if the jack on the Intel card really is dodgy (that would be...unusual) rather than the cable, you can just go back to the integrated LAN. Last fiddled with by sdbardwick on 2013-06-29 at 21:54 Reason: Clarify other party

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Increase in RAM requirement soon?	Jwb52z	PrimeNet	4	2013-05-24 09:42
power consumption	esakertt	Hardware	1	2012-10-09 20:19
Networking help	Prime95	Hardware	18	2011-05-29 22:16
Power consumption	dans	Hardware	7	2004-06-06 15:15
Power consumption	optim	Hardware	8	2003-12-06 04:13

2013-06-29, 18:45	#17
paulunderwood Sep 2002 Database er0rr E9B₁₆ Posts	Ah yeah, Gentoo. I have a couple of Gentoo installations here. Configuring and compiling the kernel to add specific hardware is encouraged. I guess Ernst's on-board realtek network device would be a supported option

2013-06-29, 19:38	#18
ewmayer ∂²ω=0 Sep 2002 República de California 26567₈ Posts	FYI, I'll be in a position to fiddle with the system again in a couple hours. Also, I'm running Debian, and my internet searches for drivers for the MSI mobo in question [cf. the Haswell preview thread in Hardware for exact specs] came up empty. How long does it typically take for such drivers to appear after a new mobo/cpu family hits market?