# HyperPixel 2.1 Round stopped working recently **URL:** \ **Category:** Support\ **Created:** [June 7, 2025, 12:12pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878 "2025-06-07T12:12:51Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![matt216](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@matt216](https://forums.pimoroni.com/u/matt216)\ **Post date:** [June 7, 2025, 12:12pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/1 "2025-06-07T12:12:51Z")
Hi all. Author of [this project](https://forums.pimoroni.com/t/sonos-now-playing-album-artwork-on-hyperpixel-2-1-round-display/26755) here. It’s been working well for months but a recent `sudo apt upgrade` seems to have broken it - nothing shown on the display (although you can see the display is powered) and SSH connectivity almost impossible. I’ve been trying to rebuild from scratch but every time I follow the instructions on the [pimoroni shop site](https://shop.pimoroni.com/products/hyperpixel-round?variant=39381081882707) it seems to render the system useless. > If you’re using a recent version of Raspberry Pi OS (Bullseye or later) then you’ll need to use the built in kernel drivers - just add the following line to the end of your `boot/firmware/config.txt` (and then reboot): > > `dtoverlay=vc4-kms-dpi-hyperpixel2r` > > You will need to have I2C disabled (`sudo raspi-config nonint do_i2c 1`). This is one of the first things to do to make the display usable with the pi, but it isn’t working for me at the moment. Anyone else with similar experience? Recent reviews of the product mention OS Buster version only works, but I’ve definitely had it with Bookworm… Thanks, Matt ---
**Author:** ![matt216](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@matt216](https://forums.pimoroni.com/u/matt216)\ **Post date:** [June 10, 2025, 2:12pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/2 "2025-06-10T14:12:39Z")
Little update. Tried rebuilding the pi/display several times now. Different OS versions, 64 and 32 bit… The pi zero builds fine and updates, but as soon as I get to the instructions quoted in the previous post I lose ssh connectivity to the pi, which I presume means it’s crashed… :( ---
**Author:** ![pboddie](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@pboddie](https://forums.pimoroni.com/u/pboddie)\ **Post date:** [June 10, 2025, 3:09pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/3 "2025-06-10T15:09:53Z")
I cannot offer any concrete advice, using neither the Raspberry Pi products nor the HyperPixel 2.1, but I did find this thread on the Raspberry Pi forums covering the driver support: [“The future of HyperPixel 4 / DPI on Bullseye and beyond”](https://forums.raspberrypi.com/viewtopic.php?t=324640). It [seems](https://forums.raspberrypi.com/viewtopic.php?t=324640#p1966039) that the panel controller is different between the HyperPixel 4 and the HyperPixel 2 Round, but subsequent to the commits accompanying the above discussion from 2022, in 2024 an [overlay](https://github.com/raspberrypi/linux/blob/rpi-6.6.y/arch/arm/boot/dts/overlays/vc4-kms-dpi-hyperpixel2r-overlay.dts) was added to the Raspberry Pi Linux repository for version 6.6 of the kernel. So, maybe it is a matter of having a new enough kernel. Bookworm seems to provide a version 6.1 kernel in its packages, potentially requiring a custom kernel to get this working. ---
**Author:** ![matt216](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@matt216](https://forums.pimoroni.com/u/matt216)\ **Post date:** [June 10, 2025, 3:33pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/4 "2025-06-10T15:33:19Z")
Thanks for the help @pboddie appreciate it. I’m pretty sure I originally built a working version a few months ago on the latest pi os available to download and my recent rebuild attempts have also tried the latest version. Instructions on the product page steer you to a new version: > If you’re using a recent version of Raspberry Pi OS (Bullseye or later)… No joy :( ---
**Author:** ![pboddie](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@pboddie](https://forums.pimoroni.com/u/pboddie)\ **Post date:** [June 10, 2025, 4:15pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/5 "2025-06-10T16:15:25Z")
I can’t see how the instructions can work, given what I’ve seen in the RPi Linux repository. The overlay is only available for Linux 6.6, as far as I’ve seen. Then again, I am not really familiar with the correspondence between RPi Linux and Debian. If there’s some kind of meaningful distinction in terms of package and kernel versions, then it would help if they didn’t use the same release codenames as Debian. I’m using [packages.debian.org](http://packages.debian.org) to look up version information. ---
**Author:** ![matt216](https://avatars.discourse-cdn.com/v4/letter/m/53a042/32.png) [@matt216](https://forums.pimoroni.com/u/matt216)\ **Post date:** [June 18, 2025, 7:39pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/6 "2025-06-18T19:39:13Z")
Solved by using the November 2024 raspios version from [Index of /raspios\_armhf/images](https://downloads.raspberrypi.com/raspios_armhf/images/) Something in the May 2025 version must have broken it. @pboddie I suspect you’re right… ---
**Author:** ![pboddie](https://avatars.discourse-cdn.com/v4/letter/p/ebca7d/32.png) [@pboddie](https://forums.pimoroni.com/u/pboddie)\ **Post date:** [June 18, 2025, 8:24pm UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/7 "2025-06-18T20:24:40Z")
Looking at the release notes, it looks like the [May 2025 release](https://downloads.raspberrypi.com/raspios_armhf/archive/2025-05-13-07:57/release_notes.txt) has a 6.12 kernel, whereas the [November 2024 release](https://downloads.raspberrypi.com/raspios_armhf/archive/2024-11-19-15:12/release_notes.txt) has a 6.6 kernel. But the overlay appears in both the [6.6](https://github.com/raspberrypi/linux/blob/rpi-6.6.y/arch/arm/boot/dts/overlays/vc4-kms-dpi-hyperpixel2r-overlay.dts) and [6.12](https://github.com/raspberrypi/linux/blob/rpi-6.12.y/arch/arm/boot/dts/overlays/vc4-kms-dpi-hyperpixel2r-overlay.dts) kernels. And the file contents are exactly the same. So maybe the breakage is in how they are applied. Still, it’s good that you got it to work again. I hate having to chase after technological churn, myself, just to make sure that all the effort I’ve put in won’t immediately go to waste. ---
**Author:** ![Akkie](https://sea2.discourse-cdn.com/flex016/user_avatar/forums.pimoroni.com/akkie/32/3095_2.png) [@Akkie](https://forums.pimoroni.com/u/Akkie)\ **Post date:** [December 17, 2025, 1:24am UTC](https://forums.pimoroni.com/t/hyperpixel-2-1-round-stopped-working-recently/27878/8 "2025-12-17T01:24:55Z")
Hello. Recently, HyperPixel 2.1 Round driver is supported for Kernel 6.12. > > > \### Describe the bug > > Upon adding the HyperPixel2 Round DeviceTree to the newly …installed Raspberry Pi OS 64-bit, I noticed that the screen was not displaying. > > Then I changed to Raspberry Pi OS with kernel 6.6, and it worked fine. > > Comparing the driver source code, it appears that changes made in kernel 6.6 have not been ported to 6.12. > https://github.com/raspberrypi/linux/commit/bf46a7be6f5355d9ea63fec37e283058a6679d2e > https://github.com/raspberrypi/linux/commit/93ae2b9f6c792d17b691e23e4ba3cf07867e1df1 > > > \### Steps to reproduce the behaviour > > \* Prepare new Raspberry Pi OS environment with kernel 6.12 > \* Add vc4-kms-dpi-hyperpixel2r device tree in config.txt > \`\`\` > dtoverlay=vc4-kms-dpi-hyperpixel2r > \`\`\` > \* Reboot OS > > \### Device (s) > > Raspberry Pi 5, Raspberry Pi Zero 2 W > > \### System > > \[raspinfo.txt\](https://github.com/user-attachments/files/23797604/raspinfo.txt) > > \### Logs > > \_No response\_ > > \### Additional context > > \_No response\_ Currently, running rpi-update enables HyperPixel2r functionality. Once Kernel 6.12.62 or later becomes available via apt, it should simply work following an OS update.