I just installed a new RPi 5 with 16GB. When booting, it doesn't show the splash screen. Without any changes, it started up in 5120x1440, which is the correct resolution. However, the screen is completely black except for the working mouse cursor.
By randomly clicking around the screen, I managed to hit the Pi logo and make the menu visible. I opened the settings and checked the screen resolution – it was correct. All mouse clicks are offset, behaving as if they are about 5cm to the right of where I actually intend to click.
When I change the resolution to anything smaller, such as 5120x720, it works just fine. After a reboot, it continues to work. Any resolution except the correct one seems to work properly.
I have a working RPi 5 8GB right next to this one. I copied all the display-related settings from its config.txt and wf-panel-pi.ini files. This made no change. I am even using the same HDMI cable, though for the new one I don't need the adapter I used previously.
The only differences between the two units are that the new one is the 16GB model and it's running in an Argon case with an M.2 adapter, booting from the NVMe drive.
What could be causing this issue?
By randomly clicking around the screen, I managed to hit the Pi logo and make the menu visible. I opened the settings and checked the screen resolution – it was correct. All mouse clicks are offset, behaving as if they are about 5cm to the right of where I actually intend to click.
When I change the resolution to anything smaller, such as 5120x720, it works just fine. After a reboot, it continues to work. Any resolution except the correct one seems to work properly.
I have a working RPi 5 8GB right next to this one. I copied all the display-related settings from its config.txt and wf-panel-pi.ini files. This made no change. I am even using the same HDMI cable, though for the new one I don't need the adapter I used previously.
The only differences between the two units are that the new one is the 16GB model and it's running in an Argon case with an M.2 adapter, booting from the NVMe drive.
What could be causing this issue?
Statistics: Posted by jussi_j — Fri Oct 17, 2025 11:33 am