1/2
I have migrated my HA install from a VirtualBox VM on a server, to use Home Assistant Operating System running on a RaspberryPi 4.

As I am using the Argon One case, I need to enable i2c-dev in order to use the case's fan and power button.

The current HA documentation talks about adding a /CONFIG directory on the hassos-boot partition.

#HomeAssistant

2/2
However, my install does not have the hassos-boot partition. The current install has -kernel, -overlay, -system, and -data.

Tried using hassos-overlay/CONFIG but it didn't work.

Which partition is one meant to use to enable kernel modules?

#HomeAssistant

@bigcalm Do you need to enable any device tree overlays? Or just the modprobe i2c-dev?

@bigcalm You need to enable the device tree overlays as step one. These are applied by the RPi bootloader, which uses the files: config.txt in the VFAT boot partition. Typically this file will have: `include extraconfig.txt`. So you can create a file in that boot partition named `extraconfig.txt` can add the lines: `dtparam=i2c_vc=on
dtparam=i2c_arm=on`. If you plug the SSD into your PC the boot partition will likely show up first.

Follow

@bigcalm it looks like the modprobe config is living in that same VFAT boot parition, and you need to create the directories.

@intrbiz Indeed, but I need to work out which of the available partitions is the boot :)

I've tried 1 of them, only another 3 to try.

Stating that it'll likely be the one to show up first may be key! I _think_ it might have been hassos-kernel...
I'll poke it after work today.

Ta.

@bigcalm it will be the first partition on the device. If it's mounted /proc/mounts will show it as VFAT.

@intrbiz nothing in /proc/mounts using VFAT. Maybe it's unmounted after the initial boot.

I'll unplug the drive in a bit and plug it into a laptop to snoop around.

@bigcalm very likely not mounted, it might well be /dev/sda1

Sign in to participate in the conversation
Mastodon

Time for a cuppa... Earl Grey please!