Hyperpixel 4 with Raspberry Pi 5

Newbie1 · January 16, 2024, 12:03pm

I am a Newbie to this wonderful world of tech and would very much appreciate it if any of the talented creators on this forum can provide a bit of advice please?

I am having difficulty connecting a Hyperpixel 4 to a Raspberry Pi 5. I would like to use it for an art project, to show a continuous MPEG-4 video loop.

I have flushed a microSD card with Raspberry Pi 5’s latest OS (Bookworm) 64-BIT, but the instructions to connect the Hyperpixel 4 to the Raspberry PI 5 on Pimoroni’s website, seem to be outdated.

I don’t know what code should be entered in the config.txt folder on the microSD card either. Here is the config.txt as it is at present:
(upload://nGfUoegs1b98jcsZE7ibCVX2cKb.jpeg)

And I also don’t know what I should type in Terminal to activate the Hyperpixel 4 and which display settings on the Pi 5’s preferences panel should be switched off so that it doesn’t interfere with the Hyperpixel 4?

If there is someone that can provide some step-by-step instructions to make this work, or have an easier way to connect a Hyperpixel 4 to a Raspberry Pi 5, I would very much appreciate it.

It is my first time that I’m trying this, so forgive my ignorance.

gadgetoid · January 18, 2024, 9:34am

The only additional line in config.txt should be:

dtoverlay=vc4-kms-dpi-hyperpixel4

for rectangular, or:

dtoverlay=vc4-kms-dpi-hyperpixel4sq

For newer square.

Newbie1 · January 18, 2024, 4:53pm

Thank you @gadgetoid for the reply.
Please would it be possible to advise what code should be entered in the Terminal screen of the Pi 5?

alphanumeric · January 19, 2024, 7:05pm

You want everything off, as far as interfaces go, i2c, SPI, etc. They should all be off by default.
It’s unclear to me what you want to do in terminal? Are you connected via SSH, or working directly from the Hyperpixel Screen?

Newbie1 · January 22, 2024, 11:45pm

Hi @alphanumeric

Thank you for the reply.

I swopped the Pi 5 for a Pi 4 (Model B/8 GB) and uploaded Raspberry Pi OS (Legacy 64-bit) Debian Bullseye through Pi Imager on a 32GB micro SD card via my MacBook.
I added the following script to the config.txt folder on the 32GB Micro SD card:

dtoverlay=vc4-kms-dpi-hyperpixel4

(I have a Hyperpixel4 Touch Screen.)

After that, I connected and HDMI to an external monitor and to the Pi 4, including a Pi mouse and keyboard with the 32 GB micro SD inserted in the Pi 4.

I checked that the i2c, SPI and other interfaces were switched off.

I typed the following script into the Terminal window of Pi OS (via the HDMI monitor and Pi keyboard and mouse) to download the Hyperpixel4 software:

curl https://get.pimoroni.com/hyperpixel4.com

I received a message that the install process has changed and that Pi 4 users should consult the following page:

github.com/pimoroni/hyperpixel4

PSA: HyperPixel 4 (Square & Rectangular) on Raspberry Pi OS 64bit 2022-04-04

opened 05:25PM - 11 Apr 22 UTC

Gadgetoid

notice

:warning: PSA: Make sure you disable i2c, SPI and any other interfaces since the…se will cause a conflict in device-tree with HyperPixel :warning: :warning: A fresh image is recommended, but otherwise make sure you also disable the `hyperpixel4-init` system service! :warning: Pi 3B and Pi 4 users running the latest and greatest Raspberry Pi OS should forego our installer and use the instructions below. > :information_source: If you're tied to an older OS and you want to install the legacy drivers, use: > `curl -sSL get.pimoroni.com/hyperpixel4-legacy | bash` This new OS can currently be found in Raspberry Pi Imager under "Raspberry Pi OS (Other)" ![image](https://user-images.githubusercontent.com/1746967/162789702-0c95f165-e482-4d47-a179-d841b903985c.png) Once installed you need only one line in `/boot/config.txt`: * Rectangular: `dtoverlay=vc4-kms-dpi-hyperpixel4` * Square: `dtoverlay=vc4-kms-dpi-hyperpixel4sq` You can rotate these in config.txt by adding the `rotate=` parameter, like so: ``` dtoverlay=vc4-kms-dpi-hyperpixel4sq,rotate=90 ``` This supports rotation in console, too, for all you CyberDeck builders! ## HyperPixel 4 Rectangular Rotations Ensure rotation is set to "Normal" in "Display Configuration" And that the dtoverlay is in `/boot/config.txt`: ``` dtoverlay=vc4-kms-dpi-hyperpixel4 ``` Finally use one of the following `dtparam` lines immediately underneath to set the parameters: * The default is portrait with header on the right, no extra line needed * `dtparam=rotate=90,touchscreen-swapped-x-y,touchscreen-inverted-y` - Landscape with header on the bottom * `dtparam=rotate=180` - Portrait with header on the left * `dtparam=rotate=270,touchscreen-swapped-x-y,touchscreen-inverted-x` - Landscape with header on the top ## HyperPixel 4 Square Rotations HyperPixel 4 Square does not correctly swap or invert touch input, so you may want to use the Xorg config method below. Ensure rotation is set to "Normal" in "Display Configuration" And that the dtoverlay is in `/boot/config.txt`: ``` dtoverlay=vc4-kms-dpi-hyperpixel4sq ``` Finally use one of the following `dtparam` lines immediately underneath to set the parameters: * Default is header on the top * `dtparam=rotate=90` - Header is on the left (wonky touch, see below) * `dtparam=rotate=180` - Header *still* on the top (doesn't work? Same as default) * `dtparam=rotate=270` - Header is on the right (wonky touch, see below) :warning: The `touchscreen-swapped-x-y` parameter does not seem to work with Square. You may need to use the script below for Raspberry Pi OS with Desktop. ## On the fly rotation Rotating the display via "Screen Configuration" ("arandr") results in inverted touch input and other weirdness- use the dtoverlay params. If you want to rotate on the fly you can use the below bash script to rotate either display and persist settings into Xorg configuration files. :warning: Note: You *must* remove the `rotate=` argument from `/boot/config.txt` for these to make sense. You can remove the rotation config by deleting the `/usr/share/X11/xorg.conf.d/88-hyperpixel4-touch.conf` and `/usr/share/X11/xorg.conf.d/88-dsi-1-rotate.conf` files. ```bash #!/bin/bash UTILITY="hyperpixel4-rotate (Rectangular)" XORG_TOUCH_CONF_FILE="/usr/share/X11/xorg.conf.d/88-hyperpixel4-touch.conf" XORG_CONF_FILE="/usr/share/X11/xorg.conf.d/88-dsi-1-rotate.conf" OVERLAY_S="vc4-kms-dpi-hyperpixel4sq" OVERLAY_R="vc4-kms-dpi-hyperpixel4" function success() { echo -e "$(tput setaf 2)$1$(tput sgr0)" } function inform() { echo -e "$(tput setaf 6)$1$(tput sgr0)" } function warning() { echo -e "$(tput setaf 1)$1$(tput sgr0)" } function set_xorg_conf { if [ "$DISPLAY" == "" ]; then inform "No DISPLAY variable set, trying :0.0" export DISPLAY=:0.0 fi inform "Rotating display $1"; xrandr --output DPI-1 --rotate $1 MATRIX="$2 $3 $4 $5 $6 $7 $8 $9 ${10}" inform "Setting libinput Calibration Matrix: 1 0 0 0 1 0"; xinput set-prop "pointer:$DEVICE" "libinput Calibration Matrix" 1 0 0 0 1 0 0 0 1 inform "Setting Coordinate Transformation Matrix: $MATRIX"; xinput set-prop "pointer:$DEVICE" "Coordinate Transformation Matrix" $MATRIX inform "Saving xorg touch config to $XORG_TOUCH_CONF_FILE"; sudo tee $XORG_TOUCH_CONF_FILE > /dev/null <<EOF # Auto generated by $UTILITY, edit with care! Section "InputClass" Identifier "HyperPixel4 $DEVICE" MatchProduct "$DEVICE" Option "CalibrationMatrix" "1 0 0 0 1 0 0 0 1" Option "TransformationMatrix" "$MATRIX" EndSection EOF inform "Saving xorg rotate config to $XORG_CONF_FILE"; sudo tee $XORG_CONF_FILE > /dev/null <<EOF # Auto generated by $UTILITY, edit with care! Section "Monitor" Identifier "DPI-1" Option "Rotate" "$1" EndSection EOF } printf "HyperPixel 4: Display & Touch Rotation\n" printf "This utility requires the Raspberry Pi OS desktop or an *Xorg-based* alternative.\n\n" ORIENTATION=$1 grep -e "^dtoverlay=$OVERLAY_S.*" /boot/config.txt > /dev/null if [ $? -ne 0 ]; then grep -e "^dtoverlay=$OVERLAY_R.*" /boot/config.txt > /dev/null if [ $? -ne 0 ]; then warning "Rotation requires hardware support on the Pi 4 or Pi 400" warning "Ensure your HyperPixel4 is enabled in /boot/config.txt" printf "\nSquare: dtoverlay=$OVERLAY_S\n" printf "Rectangular: dtoverlay=$OVERLAY_R\n\n" exit 1 else inform "Detected HyperPixel 4 Rectangular (found \"$OVERLAY_R\" in config.txt)" DEVICE="Goodix Capacitive TouchScreen" fi else inform "Detected HyperPixel 4 Square (found \"$OVERLAY_S\" in config.txt)" DEVICE="EP0110M09" fi case $ORIENTATION in "right") set_xorg_conf $ORIENTATION 0 1 0 -1 0 1 0 0 1 ;; "left") set_xorg_conf $ORIENTATION 0 -1 1 1 0 0 0 0 1 ;; "inverted") set_xorg_conf $ORIENTATION -1 0 1 0 -1 1 0 0 1 ;; "normal") set_xorg_conf $ORIENTATION 1 0 0 0 1 0 0 0 1 ;; *) printf "Unsupported orientation: $ORIENTATION\n\n"; printf "Usage:\n" printf " $0 <orientation>\n\n" printf "Where orientation is one of: left, right, normal, inverted.\n" exit 1 esac ```

On that page, instructions were provided to disable the hyperpixel-4 init system service. I am sorry but I don’t know how to do this? If you could advise, I’d appreciate it.

Instructions were also given to change the screen rotation settings. I prefer the default option, so I ignored this.

The script in the Pi OS Terminal window gave me only one option to continue with the installation process, which was:

‘If you’re sure you want to install the legacy drivers, use:’

curl -sSL get.pimoroni/hyperpixel4 - legacy | bash

I entered the script and it seemed that the software was installed.

I was asked if I’d like to reboot the Pi.

I rebooted it, but removed the HDMI screen, Pi keyboard and mouse, because I was expecting the Hyperpixel4 to show the Pi OS Homepage as it should.

I saw a brief flash of the homepage and then the screen of the Hyperpixel4 went black. Nothing happened after this.

If I connect the HDMI screen and keyboard and mouse to the Pi 4, the Home screen shows up fine.

Apologies for my long description, but hopefully it will make it easier to pinpoint why the Hyperpixel4 screen turns black.

I’d very much appreciate your help. Thank you for your time.

ahnlak · January 23, 2024, 9:50am

The page you linked to explicitly says that, from Bullseye, no drivers are required because it’s built into the kernel - and that all you need is the dtoverlay line.

Continuing on to force the installation of the legacy drivers is unlikely to have positive results.

I would suggest starting again with a clean install of Bullseye, and just add the dtoverlay entry to your config.txt - that way you will be in a known state, and if you continue to have problems we might be able to come up with other suggestions.

(to head off the standard questions… what PSU are you using?)

Newbie1 · January 23, 2024, 10:52am

Hi @ahnlak

Thank you for the reply. I agree that the installation of the legacy drivers won’t have positive results.

To make sure that I follow the installation procedure correctly, please can you tell me what I should do once I’ve done a clean install of Bullseye and added the dtoverlay entry to the config.txt?

Lastly, If I understand your question about the Power Supply Unit that I am using correctly, the Pi 4/Hyperpixel4 combination is powered by a Raspberry Pi USB-C Power Supply.

Looking forward to your response, thank you.

ahnlak · January 23, 2024, 12:10pm

Official PSU should be fine.

AIUI, clean install, edit config.txt and reboot should Just Work™ - if nothing else, it gives Hyperpixel experts a known “good state” to start diagnosing your problems…

Other common thing to check is that the Hyperpixel is fully installed onto the Pi header.

Newbie1 · January 23, 2024, 1:37pm

Thank you @ahnlak for the reply.

I made sure that the Hyperpixel is fully installed on the Pi header.

I am at a loss as to how to solve this. I hope the Hyperpixel experts might be able to provide some help.

Pilou75 · February 14, 2024, 10:57am

Hello, looking at the answsers, I don’t see anyone about the compatibility of the Hyper Pixel 4.0 and the Raspberry Pi 5. There is no Branch in GitHub for the PI 5 and information abouting using it with the Bookworm OS. All branches and documents refer to previous models and systems. Anyway, I just bought an Hyperpixel Touch rectangular. I will test it on my PI 5 with NVME Base using a Samnsung 980 Pro 1 TO. I’ll give my feedback. As a remark the NVME base works just perfectly.

Newbie1 · February 14, 2024, 11:24am

Your feedback would be much appreciated, @Pilou75.
I have resorted back to a Raspberry Pi 4/ Hyperpixel 4 which is working, but couldn’t find information regarding compatibility with the Pi 5.

ahnlak · February 14, 2024, 12:01pm

FWIW I have definitely seen reports of Hyperpixels working with the Pi5 - although sadly not going into any details about what hoops they had to jump through.

I’ve seen enough people with problems to suggest it’s not always plain sailing, however. I think the successful users have been using a Lite OS instead of the full one, but I’m not sure how much difference that makes (not personally owning either a Hyperpixel OR a Pi5…!)

Pilou75 · February 25, 2024, 6:29pm

Hello, it took me some time to give my Feedback, I was on another Pi5 project. A Picade console with Pi 5 and player X running on a Bookworm OS Lite Attract Mode plus wth Mame. It works perfectly and very smoothly. Performance are great.

So for now, I just installed my NVME base with a Samnsung 980 Pro 1To. It worked fine. so I continue and installed the HyperPixel rectangulat on top of it. I folllow the procedure explaine in GitHub for hyperpixel4 and also applied the additional configuration as explained in the issue 177.

It works directly after reboot including the touch.

I made a small picture.

So I confirm, the Hyperpixel works fine on a Pi 5 with the NVME base.
The question now is about colling the Pi. The active coolor is great but I’m affraid that won’t be sufficient space to evacuate the hot air. I will see. but for the moment with no colling system I have

pi@pi5:~ $ cpufreq
Clock Speed=2400 MHz
pi@pi5:~ $ cputemp
temp=58.2'C
pi@pi5:~ $

Newbie1 · February 26, 2024, 9:29am

Hi @Pilou75

That is great news, thank you for sharing the process.

Qvedo · June 25, 2024, 7:58am

can someone help me i have octoprint and octopi on raspberry pi 5 with hyperpixel 4.0. I installed octodash but it can’t be started and it says it can’t be found

dtoews · July 24, 2024, 10:24pm

i have the same problem! (Octodash+hyperpixel 4+raspberry pi 5). I’ll post here if i figure out why x11 is seg faulting…

update: here is the contents of the Xorg.0.log file on the pi 5 :

:/var/log $ cat Xorg.0.log
[    17.922]
X.Org X Server 1.21.1.7
X Protocol Version 11, Revision 0
[    17.925] Current Operating System: Linux octoprint 6.6.31+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64
[    17.925] Kernel command line: reboot=w coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe  smsc95xx.macaddr=2C:CF:67:1F:DA:E0 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  console=ttyAMA10,115200 console=tty1 root=PARTUUID=bbb341df-02 rootfstype=ext4 fsck.repair=yes rootwait
[    17.926] xorg-server 2:21.1.7-3+rpt2+deb12u7 (https://www.debian.org/support)
[    17.926] Current version of pixman: 0.42.2
[    17.927]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    17.927] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    17.929] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 16:07:27 2024
[    17.930] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    17.930] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    17.930] (==) No Layout section.  Using the first Screen section.
[    17.931] (==) No screen section available. Using defaults.
[    17.931] (**) |-->Screen "Default Screen Section" (0)
[    17.931] (**) |   |-->Monitor "<default monitor>"
[    17.931] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    17.931] (**) Option "Debug" "dmabuf_capable"
[    17.931] (==) Automatically adding devices
[    17.931] (==) Automatically enabling devices
[    17.931] (==) Automatically adding GPU devices
[    17.931] (==) Automatically binding GPU devices
[    17.931] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    17.931] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[    17.931]    Entry deleted from font path.
[    17.931] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[    17.931]    Entry deleted from font path.
[    17.931] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[    17.931]    Entry deleted from font path.
[    17.931] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[    17.931]    Entry deleted from font path.
[    17.931] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[    17.931]    Entry deleted from font path.
[    17.931] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[    17.931]    Entry deleted from font path.
[    17.931] (==) FontPath set to:
        /usr/share/fonts/X11/misc,
        built-ins
[    17.931] (==) ModulePath set to "/usr/lib/xorg/modules"
[    17.931] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    17.931] (II) Loader magic: 0x555599d30ef0
[    17.931] (II) Module ABI versions:
[    17.931]    X.Org ANSI C Emulation: 0.4
[    17.931]    X.Org Video Driver: 25.2
[    17.931]    X.Org XInput driver : 24.4
[    17.931]    X.Org Server Extension : 10.0
[    17.931] (--) using VT number 2

[    17.931] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    17.932] (II) xfree86: Adding drm device (/dev/dri/card2)
[    17.932] (II) Platform probe for /sys/devices/platform/axi/1000120000.pcie/1f00148000.dpi/drm/card2
[    17.934] (II) xfree86: Adding drm device (/dev/dri/card0)
[    17.934] (II) Platform probe for /sys/devices/platform/axi/1002000000.v3d/drm/card0
[    17.934] (II) xfree86: Adding drm device (/dev/dri/card1)
[    17.934] (II) Platform probe for /sys/devices/platform/axi/axi:gpu/drm/card1
[    17.935] (II) no primary bus or device found
[    17.935]    falling back to /sys/devices/platform/axi/1000120000.pcie/1f00148000.dpi/drm/card2
[    17.935] (II) LoadModule: "glx"
[    17.935] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    17.936] (II) Module glx: vendor="X.Org Foundation"
[    17.936]    compiled for 1.21.1.7, module version = 1.0.0
[    17.936]    ABI class: X.Org Server Extension, version 10.0
[    17.936] (==) Matched modesetting as autoconfigured driver 0
[    17.936] (==) Matched fbdev as autoconfigured driver 1
[    17.936] (==) Assigned the driver to the xf86ConfigLayout
[    17.936] (II) LoadModule: "modesetting"
[    17.936] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    17.936] (II) Module modesetting: vendor="X.Org Foundation"
[    17.936]    compiled for 1.21.1.7, module version = 1.21.1
[    17.936]    Module class: X.Org Video Driver
[    17.936]    ABI class: X.Org Video Driver, version 25.2
[    17.936] (II) LoadModule: "fbdev"
[    17.936] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[    17.937] (II) Module fbdev: vendor="X.Org Foundation"
[    17.937]    compiled for 1.21.1.3, module version = 0.5.0
[    17.937]    Module class: X.Org Video Driver
[    17.937]    ABI class: X.Org Video Driver, version 25.2
[    17.937] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    17.937] (II) FBDEV: driver for framebuffer: fbdev
[    17.967] (II) modeset(0): using drv /dev/dri/card2
[    17.967] (WW) Falling back to old probe method for fbdev
[    17.967] (II) Loading sub module "fbdevhw"
[    17.967] (II) LoadModule: "fbdevhw"
[    17.968] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    17.968] (II) Module fbdevhw: vendor="X.Org Foundation"
[    17.968]    compiled for 1.21.1.7, module version = 0.0.2
[    17.968]    ABI class: X.Org Video Driver, version 25.2
[    17.968] (II) modeset(G0): using drv /dev/dri/card1
[    17.968] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    17.968] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    17.968] (==) modeset(0): RGB weight 888
[    17.968] (==) modeset(0): Default visual is TrueColor
[    17.968] (II) Loading sub module "glamoregl"
[    17.968] (II) LoadModule: "glamoregl"
[    17.968] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    17.971] (II) Module glamoregl: vendor="X.Org Foundation"
[    17.971]    compiled for 1.21.1.7, module version = 1.0.1
[    17.971]    ABI class: X.Org ANSI C Emulation, version 0.4
[    18.230] (II) modeset(0): glamor X acceleration enabled on V3D 7.1
[    18.230] (II) modeset(0): glamor initialized
[    18.230] (==) modeset(0): VariableRefresh: disabled
[    18.230] (==) modeset(0): AsyncFlipSecondaries: disabled
[    18.230] (II) modeset(0): Output DPI-1 has no monitor section
[    18.230] (II) modeset(0): EDID for output DPI-1
[    18.230] (II) modeset(0): Printing probed modes for output DPI-1
[    18.230] (II) modeset(0): Modeline "480x800"x60.1   32.00  480 490 506 565  800 815 928 943 -hsync -vsync (56.6 kHz eP)
[    18.230] (II) modeset(0): Output DPI-1 connected
[    18.230] (II) modeset(0): Using exact sizes for initial modes
[    18.230] (II) modeset(0): Output DPI-1 using initial mode 480x800 +0+0
[    18.230] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    18.230] (==) modeset(0): DPI set to (96, 96)
[    18.230] (II) Loading sub module "fb"
[    18.230] (II) LoadModule: "fb"
[    18.230] (II) Module "fb" already built-in
[    18.230] (==) modeset(G0): Depth 24, (==) framebuffer bpp 32
[    18.230] (==) modeset(G0): RGB weight 888
[    18.230] (==) modeset(G0): Default visual is TrueColor
[    18.230] (II) Loading sub module "glamoregl"
[    18.230] (II) LoadModule: "glamoregl"
[    18.230] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[    18.230] (II) Module glamoregl: vendor="X.Org Foundation"
[    18.230]    compiled for 1.21.1.7, module version = 1.0.1
[    18.230]    ABI class: X.Org ANSI C Emulation, version 0.4
[    18.470] (II) modeset(G0): glamor X acceleration enabled on V3D 7.1
[    18.470] (II) modeset(G0): glamor initialized
[    18.471] (II) modeset(G0): Output HDMI-1-1 has no monitor section
[    18.472] (II) modeset(G0): Output HDMI-1-2 has no monitor section
[    18.474] (II) modeset(G0): EDID for output HDMI-1-1
[    18.475] (II) modeset(G0): EDID for output HDMI-1-2
[    18.475] (==) modeset(G0): Using gamma correction (1.0, 1.0, 1.0)
[    18.475] (==) modeset(G0): DPI set to (96, 96)
[    18.475] (II) Loading sub module "fb"
[    18.475] (II) LoadModule: "fb"
[    18.475] (II) Module "fb" already built-in
[    18.475] (II) UnloadModule: "fbdev"
[    18.475] (II) Unloading fbdev
[    18.475] (II) UnloadSubModule: "fbdevhw"
[    18.475] (II) Unloading fbdevhw
[    18.486] (==) modeset(0): Backing store enabled
[    18.486] (==) modeset(0): Silken mouse enabled
[    18.500] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[    18.500] (==) modeset(0): DPMS enabled
[    18.500] (II) modeset(0): [DRI2] Setup complete
[    18.500] (II) modeset(0): [DRI2]   DRI driver: drm-rp1-dpi
[    18.500] (II) modeset(0): [DRI2]   VDPAU driver: drm-rp1-dpi
[    18.505] (==) modeset(G0): Backing store enabled
[    18.505] (==) modeset(G0): Silken mouse enabled
[    18.505] (II) modeset(G0): Initializing kms color map for depth 24, 8 bpc.
[    18.505] (==) modeset(G0): DPMS enabled
[    18.505] (II) modeset(G0): [DRI2] Setup complete
[    18.505] (II) modeset(G0): [DRI2]   DRI driver: vc4
[    18.505] (II) modeset(G0): [DRI2]   VDPAU driver: vc4
[    18.505] (II) Initializing extension Generic Event Extension
[    18.505] (II) Initializing extension SHAPE
[    18.506] (II) Initializing extension MIT-SHM
[    18.506] (II) Initializing extension XInputExtension
[    18.506] (II) Initializing extension XTEST
[    18.506] (II) Initializing extension BIG-REQUESTS
[    18.506] (II) Initializing extension SYNC
[    18.506] (II) Initializing extension XKEYBOARD
[    18.506] (II) Initializing extension XC-MISC
[    18.506] (II) Initializing extension SECURITY
[    18.506] (II) Initializing extension XFIXES
[    18.506] (II) Initializing extension RENDER
[    18.507] (II) Initializing extension RANDR
[    18.507] (II) Initializing extension COMPOSITE
[    18.507] (II) Initializing extension DAMAGE
[    18.507] (II) Initializing extension MIT-SCREEN-SAVER
[    18.507] (II) Initializing extension DOUBLE-BUFFER
[    18.507] (II) Initializing extension RECORD
[    18.507] (II) Initializing extension DPMS
[    18.507] (II) Initializing extension Present
[    18.507] (II) Initializing extension DRI3
[    18.508] (II) Initializing extension X-Resource
[    18.508] (II) Initializing extension XVideo
[    18.508] (II) Initializing extension XVideo-MotionCompensation
[    18.508] (II) Initializing extension SELinux
[    18.508] (II) SELinux: Disabled on system
[    18.508] (II) Initializing extension GLX
[    18.736] (II) AIGLX: Loaded and initialized drm-rp1-dpi
[    18.736] (II) GLX: Initialized DRI2 GL provider for screen 0
[    18.736] (II) Initializing extension XFree86-VidModeExtension
[    18.736] (II) Initializing extension XFree86-DGA
[    18.736] (II) Initializing extension XFree86-DRI
[    18.736] (II) Initializing extension DRI2
[    18.737] (II) modeset(G0): Damage tracking initialized
[    18.737] (II) modeset(0): Damage tracking initialized
[    18.737] (II) modeset(0): Setting screen physical size to 127 x 211
[    18.767] (II) config/udev: Adding input device 11-005d Goodix Capacitive TouchScreen (/dev/input/event5)
[    18.767] (**) 11-005d Goodix Capacitive TouchScreen: Applying InputClass "libinput keyboard catchall"
[    18.767] (**) 11-005d Goodix Capacitive TouchScreen: Applying InputClass "libinput touchscreen catchall"
[    18.767] (II) LoadModule: "libinput"
[    18.767] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    18.769] (II) Module libinput: vendor="X.Org Foundation"
[    18.769]    compiled for 1.21.1.3, module version = 1.2.1
[    18.769]    Module class: X.Org XInput Driver
[    18.769]    ABI class: X.Org XInput driver, version 24.4
[    18.769] (II) Using input driver 'libinput' for '11-005d Goodix Capacitive TouchScreen'
[    18.769] (**) 11-005d Goodix Capacitive TouchScreen: always reports core events
[    18.769] (**) Option "Device" "/dev/input/event5"
[    18.771] (II) event5  - 11-005d Goodix Capacitive TouchScreen: is tagged by udev as: Keyboard Touchscreen
[    18.771] (II) event5  - 11-005d Goodix Capacitive TouchScreen: device is a keyboard
[    18.771] (II) event5  - 11-005d Goodix Capacitive TouchScreen: device is a touch device
[    18.771] (II) event5  - 11-005d Goodix Capacitive TouchScreen: device removed
[    18.792] (II) libinput: 11-005d Goodix Capacitive TouchScreen: needs a virtual subdevice
[    18.792] (**) Option "config_info" "udev:/sys/devices/platform/i2c@0/i2c-11/11-005d/input/input3/event5"
[    18.792] (II) XINPUT: Adding extended input device "11-005d Goodix Capacitive TouchScreen" (type: TOUCHSCREEN, id 6)
[    18.792] (**) Option "AccelerationScheme" "none"
[    18.792] (**) 11-005d Goodix Capacitive TouchScreen: (accel) selected scheme none/0
[    18.792] (**) 11-005d Goodix Capacitive TouchScreen: (accel) acceleration factor: 2.000
[    18.792] (**) 11-005d Goodix Capacitive TouchScreen: (accel) acceleration threshold: 4
[    18.792] (II) event5  - 11-005d Goodix Capacitive TouchScreen: is tagged by udev as: Keyboard Touchscreen
[    18.793] (II) event5  - 11-005d Goodix Capacitive TouchScreen: device is a keyboard
[    18.793] (II) event5  - 11-005d Goodix Capacitive TouchScreen: device is a touch device
[    18.793] (II) config/udev: Adding input device 11-005d Goodix Capacitive TouchScreen (/dev/input/mouse0)
[    18.793] (II) No input driver specified, ignoring this device.
[    18.793] (II) This device may have been added with another device file.
[    18.793] (II) config/udev: Adding input device pwr_button (/dev/input/event0)
[    18.793] (**) pwr_button: Applying InputClass "libinput keyboard catchall"
[    18.793] (II) Using input driver 'libinput' for 'pwr_button'
[    18.793] (**) pwr_button: always reports core events
[    18.793] (**) Option "Device" "/dev/input/event0"
[    18.794] (II) event0  - pwr_button: is tagged by udev as: Keyboard
[    18.794] (II) event0  - pwr_button: device is a keyboard
[    18.794] (II) event0  - pwr_button: device removed
[    18.812] (**) Option "config_info" "udev:/sys/devices/platform/pwr_button/input/input0/event0"
[    18.812] (II) XINPUT: Adding extended input device "pwr_button" (type: KEYBOARD, id 7)
[    18.812] (**) Option "xkb_model" "pc105"
[    18.812] (**) Option "xkb_layout" "us"
[    18.812] (II) event0  - pwr_button: is tagged by udev as: Keyboard
[    18.812] (II) event0  - pwr_button: device is a keyboard
[    18.813] (II) config/udev: Adding input device vc4-hdmi-0 (/dev/input/event1)
[    18.813] (**) vc4-hdmi-0: Applying InputClass "libinput keyboard catchall"
[    18.813] (II) Using input driver 'libinput' for 'vc4-hdmi-0'
[    18.813] (**) vc4-hdmi-0: always reports core events
[    18.813] (**) Option "Device" "/dev/input/event1"
[    18.813] (II) event1  - vc4-hdmi-0: is tagged by udev as: Keyboard Pointingstick
[    18.814] (II) event1  - vc4-hdmi-0: device is a pointer
[    18.814] (II) event1  - vc4-hdmi-0: device is a keyboard
[    18.814] (II) event1  - vc4-hdmi-0: device removed
[    18.832] (II) libinput: vc4-hdmi-0: needs a virtual subdevice
[    18.832] (**) Option "config_info" "udev:/sys/devices/platform/soc/107c701400.hdmi/rc/rc0/input1/event1"
[    18.832] (II) XINPUT: Adding extended input device "vc4-hdmi-0" (type: MOUSE, id 8)
[    18.832] (**) Option "AccelerationScheme" "none"
[    18.832] (**) vc4-hdmi-0: (accel) selected scheme none/0
[    18.832] (**) vc4-hdmi-0: (accel) acceleration factor: 2.000
[    18.832] (**) vc4-hdmi-0: (accel) acceleration threshold: 4
[    18.833] (II) event1  - vc4-hdmi-0: is tagged by udev as: Keyboard Pointingstick
[    18.833] (II) event1  - vc4-hdmi-0: device is a pointer
[    18.833] (II) event1  - vc4-hdmi-0: device is a keyboard
[    18.833] (II) config/udev: Adding input device vc4-hdmi-0 HDMI Jack (/dev/input/event2)
[    18.833] (II) No input driver specified, ignoring this device.
[    18.833] (II) This device may have been added with another device file.
[    18.834] (II) config/udev: Adding input device vc4-hdmi-1 (/dev/input/event3)
[    18.834] (**) vc4-hdmi-1: Applying InputClass "libinput keyboard catchall"
[    18.834] (II) Using input driver 'libinput' for 'vc4-hdmi-1'
[    18.834] (**) vc4-hdmi-1: always reports core events
[    18.834] (**) Option "Device" "/dev/input/event3"
[    18.834] (II) event3  - vc4-hdmi-1: is tagged by udev as: Keyboard Pointingstick
[    18.834] (II) event3  - vc4-hdmi-1: device is a pointer
[    18.834] (II) event3  - vc4-hdmi-1: device is a keyboard
[    18.835] (II) event3  - vc4-hdmi-1: device removed
[    18.852] (II) libinput: vc4-hdmi-1: needs a virtual subdevice
[    18.852] (**) Option "config_info" "udev:/sys/devices/platform/soc/107c706400.hdmi/rc/rc1/input4/event3"
[    18.852] (II) XINPUT: Adding extended input device "vc4-hdmi-1" (type: MOUSE, id 9)
[    18.852] (**) Option "AccelerationScheme" "none"
[    18.852] (**) vc4-hdmi-1: (accel) selected scheme none/0
[    18.852] (**) vc4-hdmi-1: (accel) acceleration factor: 2.000
[    18.852] (**) vc4-hdmi-1: (accel) acceleration threshold: 4
[    18.852] (II) event3  - vc4-hdmi-1: is tagged by udev as: Keyboard Pointingstick
[    18.853] (II) event3  - vc4-hdmi-1: device is a pointer
[    18.853] (II) event3  - vc4-hdmi-1: device is a keyboard
[    18.853] (II) config/udev: Adding input device vc4-hdmi-1 HDMI Jack (/dev/input/event4)
[    18.853] (II) No input driver specified, ignoring this device.
[    18.853] (II) This device may have been added with another device file.
[    18.867] (**) 11-005d Goodix Capacitive TouchScreen: Applying InputClass "libinput keyboard catchall"
[    18.867] (**) 11-005d Goodix Capacitive TouchScreen: Applying InputClass "libinput touchscreen catchall"
[    18.867] (II) Using input driver 'libinput' for '11-005d Goodix Capacitive TouchScreen'
[    18.867] (**) 11-005d Goodix Capacitive TouchScreen: always reports core events
[    18.867] (**) Option "Device" "/dev/input/event5"
[    18.867] (II) libinput: 11-005d Goodix Capacitive TouchScreen: is a virtual subdevice
[    18.867] (**) Option "config_info" "udev:/sys/devices/platform/i2c@0/i2c-11/11-005d/input/input3/event5"
[    18.867] (II) XINPUT: Adding extended input device "11-005d Goodix Capacitive TouchScreen" (type: KEYBOARD, id 10)
[    18.867] (**) Option "xkb_model" "pc105"
[    18.867] (**) Option "xkb_layout" "us"
[    18.867] (**) vc4-hdmi-0: Applying InputClass "libinput keyboard catchall"
[    18.867] (II) Using input driver 'libinput' for 'vc4-hdmi-0'
[    18.867] (**) vc4-hdmi-0: always reports core events
[    18.867] (**) Option "Device" "/dev/input/event1"
[    18.867] (II) libinput: vc4-hdmi-0: is a virtual subdevice
[    18.867] (**) Option "config_info" "udev:/sys/devices/platform/soc/107c701400.hdmi/rc/rc0/input1/event1"
[    18.867] (II) XINPUT: Adding extended input device "vc4-hdmi-0" (type: KEYBOARD, id 11)
[    18.867] (**) Option "xkb_model" "pc105"
[    18.867] (**) Option "xkb_layout" "us"
[    18.867] (**) vc4-hdmi-1: Applying InputClass "libinput keyboard catchall"
[    18.867] (II) Using input driver 'libinput' for 'vc4-hdmi-1'
[    18.867] (**) vc4-hdmi-1: always reports core events
[    18.867] (**) Option "Device" "/dev/input/event3"
[    18.867] (II) libinput: vc4-hdmi-1: is a virtual subdevice
[    18.867] (**) Option "config_info" "udev:/sys/devices/platform/soc/107c706400.hdmi/rc/rc1/input4/event3"
[    18.867] (II) XINPUT: Adding extended input device "vc4-hdmi-1" (type: KEYBOARD, id 12)
[    18.867] (**) Option "xkb_model" "pc105"
[    18.867] (**) Option "xkb_layout" "us"
[    18.918] (II) event0  - pwr_button: device removed
[    18.944] (II) event5  - 11-005d Goodix Capacitive TouchScreen: device removed
[    18.972] (II) event1  - vc4-hdmi-0: device removed
[    18.992] (II) event3  - vc4-hdmi-1: device removed
[    19.017] (II) UnloadModule: "libinput"
[    19.017] (II) UnloadModule: "libinput"
[    19.018] (II) UnloadModule: "libinput"
[    19.018] (II) UnloadModule: "libinput"
[    19.018] (II) UnloadModule: "libinput"
[    19.018] (II) UnloadModule: "libinput"
[    19.018] (II) UnloadModule: "libinput"
[    19.135] (II) Server terminated successfully (0). Closing log file.

Qvedo · September 8, 2024, 5:36pm

I already have an octodash on a raspberry PI5 with a hyperpixel 4 display, but I can’t rotate the displayProcessing: 1000029379.jpg…

alphanumeric · September 8, 2024, 5:53pm

Preferences > Screen Configuration
Layout > Screens > (select the entry for the Hyperpixel) > Orientation > Then find the one that works.

Qvedo · September 8, 2024, 7:25pm

Unfortunately, there is no such offer in octodash. I did it via ssh on the pi4, but it doesn’t work on the pi5

waysert · November 15, 2024, 8:50am

Hi, i’m exactly running the same issue. My pi setup: Pi5, RaspbianOS, Octoprint installed und running, but octodash won’t load, i have the same segmentation fault. what was your solution? i tried the get it running the last 5 days with no success…

Topic		Replies	Views
Hyperpixel 4, Pi4 - no clear image Support	3	359	October 11, 2021
Pi5 and Pimoroni HyperPixel 4.0 (GPIO) Support	0	206	March 10, 2024
Hyperpixel 3.5, Buster, Pi 4 how? Support	11	1502	December 3, 2020
Hyperpixel 4.0 not work at all Support	7	2403	January 11, 2019
Hyperpixel4 No Image Support	17	859	May 2, 2020

Hyperpixel 4 with Raspberry Pi 5

dtoverlay=vc4-kms-dpi-hyperpixel4

Related topics