I’m in a bit of a pickle. I recently installed OSMC on a Pi3 and I’m very happy with it (I had Kodi on an older system, and decoding highly compressed videos was becoming an issue).
However, I just realised that the MAC address of the eth0 adapter changes every time the Pi reboots (shown on the “System info” page and on my DHCP server).
Is that supposed to be the normal behaviour ? How is that helpful ? If this is a feature, how can I assign a fixed address, preferably HW ? And, if this is a bug, would anyone have any idea where I should start ?
When I try to set a manual IP address using OSMC settings, the setting reverts itself to DHCP upon next reboot (?).
What I’ve tried so far:
Adding to the end of the command line in “/boot/cmdline.txt” : smsc95xx.macaddr=xx:xx:...
Adding to the end of “/boot/config.txt”: smsc95xx.macaddr=xx:xx:...
uname -a: Linux dariboubare 4.9.29-10-osmc #1 SMP PREEMPT Mon Oct 9 02:18:18 UTC 2017 armv7l GNU/Linux
grep VERSION_ID /etc/os-release: VERSION_ID="2018.07-1"
This is not normal to have a MAC address changing. I’m thinking you may have a failing SD card, so try a new installation on a new SD card. If that doesn’t work, it could be that your Pi is failing.
Of course, logs could help figure out what’s happening.
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 logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
So, in summary:
activate the logging
reboot the OSMC device
reproduce the issue
upload the log set either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
I’ve update from deb http://apt.osmc.tv stretch-devel main due to a sound stutter issue, which was fixed.
While scanning the log, I stumbled upon this:
Hmm. There is a symbolic link /lib/modules/4.9.29-10-osmc/build
However, I can not read it: No such file or directory
Therefore, I am deleting /lib/modules/4.9.29-10-osmc/build
Hmm. The package shipped with a symbolic link /lib/modules/4.9.29-10-osmc/source
However, I can not read the target: No such file or directory
Therefore, I am deleting /lib/modules/4.9.29-10-osmc/source
which looks scary to me, but I’m not familiar with Linux. I wasn’t able to find anything else of interest.
I don’t even know if this is hardware or software related …
EDIT: this happens in a loop, with a different “ret =” value almost every time (seems to hang between -110 and -140). It also sometimes spurts what I assume are core dumps. Let me know if I can do anything to provide more info on this !
EDIT 2: OSMC is otherwise working like a charm, I’m baffled =)
Your ‘new’ SD card may have been a counterfeit card. Did you get it on e-Bay or a similar online store? Some of those cards are not the full capacity that they report to the OS, causing all kinds of strange problems.
Or you could have just gotten a bad card. You should be able to get it replaced under warranty.
Surely that commit came after the July Update so it is not part of the current available image. But as long as you are not using torrent or other heavy background services you should not have stuttering
Warning: Only 7455 of 7456 MByte tested.
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 4.08 MByte/s
Reading speed: 4.30 MByte/s
I feel silly, I expected it to throw at least an error or two … I have no clue what’s going on here, but at least I have it working now =)