No wired network until I unplug and replug the network cable a few times

Hi everyone,

For some reason each time I reboot my RPi2 with OSMC, my network (fixed IP or dhcp) does not work. The only way it starts working is when I unplug and replug the network cable a few times.

When it finally works, it keeps working without problems, but if I reboot the RPi, sometimes the network keeps working and sometimes it doesn’t, and if I shutdown and power on the RPi, I always have to do the ‘unplug & replug’ process again… :sweat:

I’ve tried by disabling connman and installing ifupdown (/etc/network/interfaces), but I’m experiencing the same issue.

Also, I couldn’t find anything in the logs:

root@pandora:~# journalctl | egrep "(netw|eth)"
Jan 31 01:45:00 pandora kernel: smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:f3:5f:09
Jan 31 01:45:00 pandora systemd[1]: Starting LSB: Raise network interfaces....
Jan 31 01:45:02 pandora kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Jan 31 01:45:02 pandora networking[185]: Configuring network interfaces...done.
Jan 31 01:45:02 pandora systemd[1]: Started LSB: Raise network interfaces..
Jan 31 01:45:06 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Jan 31 01:45:38 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link down
Jan 31 01:45:40 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Jan 31 01:45:44 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link down
Jan 31 01:45:46 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Jan 31 01:45:52 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link down
Jan 31 01:45:55 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Jan 31 01:46:02 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link down
Jan 31 01:46:04 pandora kernel: smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC5E1
Jan 31 01:46:38 pandora ntpd[772]: Listen normally on 3 eth0 192.168.1.50 UDP 123

(the link down / link up means I’m unplugging and replugging the network cable)

Does this sound familiar to someone?

Thanks in advance!

You are now outside the reasonable scope of support that OSMC can provide.

Thanks ActionA,

I understand the point, but I’m experiencing this problem since I fresh installed OSMC. I only tried to replace connman as a last resort.

Then revert/reinstall and provide a more useful set of info for debugging your issue.

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload some logs. You can learn more about how to submit a useful support request here.

Thanks for your understanding. We hope that we can help you get up and running again shortly.

1 Like

Hello again everyone,

I’ve made an absolutely fresh install (2017.01-1) and the same problem still persists :sweat:

After I unplug and replug the network cable a few times, it starts working without problems and it will keep working until next reboot or shutdown/startup.

The only weird thing I see at the moment is that ifconfig shows 164 RX errors and 82 RX packages dropped (these values stay static):

eth0      Link encap:Ethernet  HWaddr b8:27:eb:f3:5f:09  
          inet addr:192.168.1.50  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST DYNAMIC  MTU:1500  Metric:1
          RX packets:11137 errors:164 dropped:82 overruns:0 frame:164
          TX packets:5432 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:13177701 (12.5 MiB)  TX bytes:977842 (954.9 KiB)

I’m not pretty sure what else I can do (maybe trying if same problem occurs with another distro?).

In case it helps, here are my logs: http://paste.osmc.io/ixisudeqit
Any help would be greatly appreciated!

Have you tried a different cable? Are you routed through any other hardware/switch?

It seems to be the cable… d****mn it!!! 15 meters of cable wired through the wall… :sob:
Thanks for your help ActionA!

It turned out that pin 4 and pin 6 of my cable were inverted. Fortunately I was able to repatch the cable and it seems to working ok now!! Thank you again!!