[Garesu]

Using Kodi (OSMC) on a raspberry Pi 1 B, after the July update, the Ethernet stopped working. It still showed up as working, but was unable to obtain an IP address, nor did it work when assigned an IP address manually.
Tried a clean install of the latest version, and no difference.
Installed the June version and it works again.


Not sure where to report this, but I don't see anyone else with the same issue and searching so far has turned up nothing.

[Dangelus]

Well since you are using OSMC perhaps you should report it in the OSMC forums?

[Sam.Nazarko]

Hello

This is an issue we're not aware of. In the July update I made only one change to ConnMan (our connection manager) which was to fix an issue with nameservers being written to /etc/resolv.conf in the reverse order. Not much has changed on the networking side between these two releases.

Just to confirm -- are you using the Ethernet port that is physically affixed to the Raspberry Pi?

If you have a USB keyboard, we should be able to narrow down the issue quite quickly.

* Install the June update from osmc.tv/download
* Configure your Wired network appropriately, verify it's working.
* Update to the July release. You can do this by going to My OSMC -> Updates -> Manual Controls -> Check for Updates now.
* Verify that you've lost your connection. If you have, here are a couple of things we can try to work out what's going on:

1) Look up how to access the command line without network access: https://osmc.tv/wiki/general/accessing-t...mand-line/.
2) Run /sbin/ifconfig. Do you see eth0?
3) Run dmesg > /boot/dmesg_log. This will save a dmesg_log to your SD card's fat partition, which is mountable from Windows, OS X, Linux and you can upload the contents to paste.osmc.io.
4) Type 'sudo connmanctl'. Then type 'technologies'. Does ConnMan advertise Ethernet is available?

For future reference, you will get better support for OSMC related issues on https://discourse.osmc.tv. I keep an eye on this forum but not as frequently as the OSMC one.

Sam

[Garesu]

Thanks for quick response.
Yes its the Ethernet port that is attached to the Pi.

I'll do as advised and continue this on the OSMC forums.

[Sam.Nazarko]

Very welcome

I'll keep an eye out for your post.

[speedwell68]

Thanks for quick response.
Yes its the Ethernet port that is attached to the Pi.

I'll do as advised and continue this on the OSMC forums.

Does your ethernet port work with any other distro like LibreELEC or Raspbian?

[Sam.Nazarko]

Thanks for quick response.
Yes its the Ethernet port that is attached to the Pi.

I'll do as advised and continue this on the OSMC forums.

Does your ethernet port work with any other distro like LibreELEC or Raspbian?

Raspbian isn't particularly interesting here.

LE is.

LE bumped ConnMan as well as their kernel. I suspect if OP is having a problem with LE too it may be kernel based,as commits to ConnMan have been slow (Patrik is on holiday).

Sam

[speedwell68]

Thanks for quick response.
Yes its the Ethernet port that is attached to the Pi.

I'll do as advised and continue this on the OSMC forums.

Does your ethernet port work with any other distro like LibreELEC or Raspbian?

Raspbian isn't particularly interesting here.

Raspbian is very interesting here. It would prove whether there is a physical hardware fault or not. On one of my RPI 1Bs one day the ethernet socket failed.

[trogggy]

Raspbian is very interesting here. It would prove whether there is a physical hardware fault or not. On one of my RPI 1Bs one day the ethernet socket failed.

In the OP he says it works again if he rolls back.