I’ve updated OSMC from a working 2022.08 release to fresh installation with current release (2025.03) without changing the hardware (except the SD card). The system is using a Pi4. I restored the OSMC backup to migrate ma existing configuration. (After some retries this worked flowlessly)
As the new system is based on a fresh installation I had to reinstall support for argonONE case. But after all installations I noticed the following problems:
fan control did not work
case did not switch off poer (Pi4 shut down normally, but power led at case staed on)
After some analysing the problem was caused by missi ng i2c support. Other than in previous release the current argonOn scripts need i2c support for ALL actiosn - including smooth shutdown.
So I did the following steps to enable i2c support:
edit file ‘/boot/config-user.txt’ and add the line ‘dtparam=i2c_arm=on’
edit file ‘/etc/modules’ and add the line ‘i2c-dev’
After a reboot you can check i2c functionality by issuing the command ‘sudo i2cdetect -y 1’
With these changes applied i2c is anabled and the argin case behaves as expected. Especially when shutting down it’s power led goes of (after pi is cleanly shutdown) enabling a normal start by pressing the backside button.
Hope this guide helps some others.
If you have any suggestion to solve the problem in a better way, plase respond.
And in addtion: If anyone kanows how to suggest an improvement please suggest that myOSMC gets a dedicated option ‘enable i2c’ to avoid editing base files for unexperienced users.
The manufacturer of the argonOne box simply suggests / requires to execute the installation script (argon1,sh) which can be downloaded at their website.
YES the script and the box work out of the box with standard PiOS installations (tested with Pi4 and the versions for Pi5 too.)
The installation script installs all additionally requires modules and configurations. The problem at OSMC installations is that OSMC invalidates the standard raspi-config script which is used by argon1 to activate i2c functionality.
As I see that OSMC block raspi-config for good reasons and tryes to avoid misconfigured systems (I assume) the standard argon scripts cannot work out of the box at OSMC. As running the script clearly states that i2c support is missing it should be possible for users with basic PiOS knowledge to fix i. But the suggestion to use myOSMC does not show an option to simply enable i2c. So one could use the edit possibility of myOSMC but this looked more confusing for me than directly checking / editing editing /boot/config*.txt.
So my suggesting as a improvemnet would be to extend myOSMC to allow enabling i2c and to do all steps required get get i2c up and running in a way controlled by OSMC.
P.S. not really related to this problem: I like this case as it has the benefit to allow a clean shutdown of Pi, switching off power if Pi is shut down and allow a restart / power on by simply pressing a button. Most Pi cases require manual / external power off / on actions.
My suggestion is that if the hardware vendor want this supported under OSMC, they provide a sample device or implement it themselves. OSMC is available freely at Download - OSMC, so it should not be difficult for them to implement this. You should contact them about this as I don’t even have their device to test. Manually editing /etc/modules and not using a modules.d approach (as a bare minimum) is bad.
You will also find that other Kodi distributions (i.e. LibreELEC) do not implement rpi-config because it does not make sense on an embedded media centre distribution.