[SOLVED] Raspberry Pi 5 graphics not working

[HuskyDog]

Mr Seagoon,

The missing incantation that PiOS has that Gentoo has just acquired is ..

IT WORKS!!!

Thank you very much for your efforts on this. I've no idea how long it would have taken me to figure this out!

I guess that someone (hopefully you) now needs to (a) add this to the "Gentoo Raspberry Pi Install Guide" and (b) get the developers to somehow add this to the xorg ebuild.

If I strike any more problems I will let you know, but for now I will mark this thread as "Solved".

I'll keep an eye on Plasma 6 and once it stabilises on arm64 I'll look to switch over to Wayland. Perhaps by then it will be rather less painful.

Cheers,

Huskydog

[NeddySeagoon]

pingtoo,

config.txt is

Code: Select all

# have a properly sized image
disable_overscan=1

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# There is also
# Enable DRM VC4 V3D driver
#dtoverlay=vc4-fkms-v3d
# which is fake kms. Its a wrapper arounh the blob driver

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Run in 64-bit mode
arm_64bit=1

Some of that I had already.

[pingtoo]

pingtoo,

config.txt is

Code: Select all

# have a properly sized image
disable_overscan=1

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2

# There is also
# Enable DRM VC4 V3D driver
#dtoverlay=vc4-fkms-v3d
# which is fake kms. Its a wrapper arounh the blob driver

# Don't have the firmware create an initial video= setting in cmdline.txt.
# Use the kernel's default instead.
disable_fw_kms_setup=1

# Run in 64-bit mode
arm_64bit=1

Some of that I had already.

Thank you very much for confirmation.

Not I am less worry, As long as firmware blob can be loaded there is a way to make driver work.

[Nsane457]

I installed minimal wayland-only plasma DE on my new RPi5 (i.e., kde-plasma/plasma-desktop only). I modified the SDDM ebuild to omit xorg-server. I setup sddm to use kwin instead of weston. And after frustratingly trying to start with sddm or startplasma_wayland for hours until stumbling on this thread, it seems all I had to do was add

Code: Select all

dtoverlay=vc4-kms-v3d

to config.txt and reboot.

[e8root]

HuskyDog,

PiOS has dropped Xorg support on the Pi5. Its Wayland only.

The next step is to try with Wayland. That's building now.
After that, if Wayland fails, its unpick PiOS..

I don't remember any such announcements.
Wayland is the default and you can easily change to X11 in Raspbian.

Not to mention total switch to Wayland would be a bit premature given very poor state of GPU drivers and given how Raspian is designed to run on multiple generations of RPi hardware it would be pointless to drop X11 support just to have to release separate image for RPi4 and/or RPi5 given RPi3 does not support Wayland and needs to ship with Xorg.

OpenGL/Vulkan side of things is even more stable/usable on Wayland than on X11 but Wayland performance is atrocious.
Given the limited hardware performance it cannot ever be "very good" but without proper scheduling that allows composition to start before other issued draw calls finished compositing quickly becomes extremely slow including choppy mouse cursor movement. Should this be fixedand we at most get some stuttering on heavy GPU load but otherwise at least workable compositing performance we might see support for X11 dropped. I would not expect such things happening in 2024.