Philip Howard

@herodk what do you see, in this case, when you run: `sudo i2cdetect -y 3` (where 3 is the i2c bus number revealed by listing enabled busses with: `ls /dev/i2c-*`...

### TLDR: I have a software workaround prepared for this issue This seems to work in my setup, but I'd appreciate any feedback. This splits the hyperpixel4.dtbo into 3 dtbo...

It's likely Volumio is built down to a size and thus lacks the drivers required for the touch screen- that's more an educated guess than reality, though. The good news...

Those warnings can be ignored. What changes did you make to the dtbo? If you're still running with a single dtbo file, it's possible you could be encountering the i2c...

The i2c dmesg errors regarding GPIO2 are fine, since that's presumably a side-effect of the system trying to set up the EEPROM i2c bus, which it can't do because those...

Did you modify your `hyperpixel4.dtbo` to use i2c address `0x5d` instead of `0x14`? Doesn't look like you're running the `pi4-i2c-fix` branch, so it's probably not picking up the touch. The...

In the absense of xinput you'll have to go with @gvolt's suggestion, which is to rotate things at the driver level. Between `touchscreen-inverted-x`, `touchscreen-inverted-y`, and `touchscreen-swapped-x-y` you should be able...

Curious `touchscreen-swapped-x-y` is a valid parameter, apparently, so I wonder if it's failing because the device-tree overlay is broken in some way, or because the driver isn't properly supporting it:...

This is what happens when a problem comes up and is solved 2 years ago, but you're juggling so many things you forget it even happened and waste an hour...

Ah- the instructions mention that the dpkg file is available in releases- you can grab it here: https://github.com/pimoroni/HyperPixel4TouchScreen/releases/download/v1.0/hyperpixel4-goodix-dkms_1.0_all.deb