You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i still did not manage to get the screen to work with the Pi 5 in combination with the hyperpixel4 square.
what did i do?
i manually installed the rpi4 branch, and changed the install.sh script's config to the new config.txt location that the rpi5 has inside /boot/firmware. rebooted, and now the screen shows black. however, when i connect a screen to one of the micro hdmi ports, and touch the hyperpixel4's touch screen, the touch seems to move the cursor on the other monitor just fine.
i have had a similar issue with the rpi3b before and managed to fix it by commenting dtoverlay=vc4-kms-v3d in the config.txt. However, trying to do the same in the rpi5's /boot/firmware/config.txt it gets stuck on reboot.
note that the system consists of a rpi 5, hyperpixel4 square and a PIjuice hat, and that this combination worked for the rpi 3 and 4.
The text was updated successfully, but these errors were encountered:
trying the approaches listed here in issue 208:
#208
and
#177 (comment)
i still did not manage to get the screen to work with the Pi 5 in combination with the hyperpixel4 square.
what did i do?
i manually installed the rpi4 branch, and changed the install.sh script's config to the new config.txt location that the rpi5 has inside
/boot/firmware
. rebooted, and now the screen shows black. however, when i connect a screen to one of the micro hdmi ports, and touch the hyperpixel4's touch screen, the touch seems to move the cursor on the other monitor just fine.i have had a similar issue with the rpi3b before and managed to fix it by commenting
dtoverlay=vc4-kms-v3d
in the config.txt. However, trying to do the same in the rpi5's/boot/firmware/config.txt
it gets stuck on reboot.note that the system consists of a rpi 5, hyperpixel4 square and a PIjuice hat, and that this combination worked for the rpi 3 and 4.
The text was updated successfully, but these errors were encountered: