[SOLVED] Raspberry Pi 5 graphics not working

[HuskyDog]

Can I ask about the experience others are having getting Gentoo to work on a Raspberry Pi 5 and in particular getting the display to work.

I received my Pi 5 on Monday and am trying to move my copy of Gentoo over from my Pi 4. The operating system is on a USB SSD and works just fine on the Pi 4.

I compiled a new kernel on the 4 using the latest version from the Raspberry Pi GIT repository (6.1.63) as I wasn't sure if raspberrypi-sources was up to date with the required Pi 5 patches. I put this into the boot partition as kernel_2712.img and the Pi 5 seemed to boot just fine. It connects to the network via Ethernet perfectly and I can emerge updates without a problem (and significantly faster than on the 4).

However, no matter what I do I can't get X to start. I've upgraded to the latest testing version of Mesa (23.3.0) as I read that there had been some Pi 5 specific patches but this didn't help.

I can post some diagnostics, but to start with I'd just like to hear that others have been successful and if so what package versions, config.txt options, kernel config settings, use flags etc they might be using that I could try.

I want to add that my Pi 4 still works just fine if I move the SSD back again.

[Logicien]

In concern of Xorg you must check that your kernel configuration have framebuffer support for the console and create /dev/fb0. This framebuffer is use by some Xorg modules like modeset and fbdev. Some other modules like fbturbo are also avilable. I use the modeset module with a tinkerboard s and an odroid xu4 and it work. So you have to create a basic Xorg configuration to force the Xorg video module to use and test all of them to find one who work.

Of course your kernel framebuffer must be Xorg compatible. You can try vesa support on both kernel and xorg. I do not use the Raspberry Pi.

[hdcg]

Hi HuskyDog,

are you sure about the kernel version? Looks too old for me.

While I am still on RPI4, I use the kernel from https://github.com/raspberrypi/linux and noticed the introduction of the RPI5 stuff around 6.1.54. E.g. the bcm2712 defconfig (arch/arm64/configs/bcm2712_defconfig) was added during this time. And also https://github.com/raspberrypi/rpi-eeprom received bcm2712 support during the same time frame.

Best Regards,
Holger

[NeddySeagoon]

HuskyDog,

Try the Pi Foundation kernel under your Pi4 install. Like this.
I did the migration you are trying to do.

My config.txt is missing the kms overlay, so I only get Xorg to run with the fbdev driver.
The Pi5 default kernel uses a 16k page size but the rest of the world uses 4k. That matters for swap

[HuskyDog]

Hi HuskyDog,

are you sure about the kernel version? Looks too old for me.

Apologies, I was looking at the wrong folder on my Pi 4. My actual Kernel version is 6.1.63-v8-16k. I have edited my original post to correct this.

[NeddySeagoon]

HuskyDog.

Share the /boot/config.txt and the Pi 5 command line at the top of dmesg, when the Pi5 has booted please.

I get

Code: Select all

[    0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=D8:3A:DD:BA:45:A0 vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=tty root=/dev/mmcblk0p4 rootfstype=ext4 rootwait cma=256M@256M net.ifnames=0

[HuskyDog]

HuskyDog.

Share the /boot/config.txt and the Pi 5 command line at the top of dmesg, when the Pi5 has booted please.

[/code]

Thanks for your suggestion regarding the Pi Foundation kernel. The page you pointed to is very helpful but it hasn't solved the problem. Here is the information you asked for:

config.txt

Code: Select all

dtparam=audio=on
display_auto_detect=1
arm_64bit=1
dtoverlay=vc4-kms-v3d
max_framebuffers=2
[pi4]
gpu_mem=128
kernel=kernel8-p4.img
over_voltage=7
arm_freq=2000
gpu_freq=750
[all]
os_check=0

Command Line

Code: Select all

Kernel command line: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=D8:3A:DD:C3:28:6F vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  usb-storage.quirks=152d:0578:u dwc_otg.lpm_enable=0 root=/dev/sda2 rootfstype=ext4 fsck.repair=yes usbhid.mousepoll=0 rootwait cma=256M@256M net.ifnames=0

And some more diagnostics which might be useful:
uname -a

Code: Select all

Linux percy_pi 6.1.64-v8-16k+ #1702 SMP PREEMPT Wed Nov 29 14:26:42 GMT 2023 aarch64 GNU/Linux

dmesg | grep v3d

Code: Select all

[    5.606948] [drm] Initialized v3d 1.0.0 20180419 for 1002000000.v3d on minor 0

dmesg | grep vc4

Code: Select all

[    6.058590] vc4-drm axi:gpu: bcm2712_iommu_of_xlate: MMU 1000005200.iommu
[    6.062983] vc4-drm axi:gpu: bound 107c580000.hvs (ops vc4_hvs_ops [vc4])
[    6.065474] rc rc0: vc4-hdmi-0 as /devices/platform/soc/107c701400.hdmi/rc/rc0
[    6.065589] input: vc4-hdmi-0 as /devices/platform/soc/107c701400.hdmi/rc/rc0/input4
[    6.067490] vc4-drm axi:gpu: bound 107c701400.hdmi (ops vc4_hdmi_ops [vc4])
[    6.071286] rc rc1: vc4-hdmi-1 as /devices/platform/soc/107c706400.hdmi/rc/rc1
[    6.071336] input: vc4-hdmi-1 as /devices/platform/soc/107c706400.hdmi/rc/rc1/input5
[    6.076957] vc4-drm axi:gpu: bound 107c706400.hdmi (ops vc4_hdmi_ops [vc4])
[    6.077254] vc4-drm axi:gpu: bound 107c500000.mop (ops vc4_txp_ops [vc4])
[    6.077406] vc4-drm axi:gpu: bound 107c501000.moplet (ops vc4_txp_ops [vc4])
[    6.077526] vc4-drm axi:gpu: bound 107c410000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.077622] vc4-drm axi:gpu: bound 107c411000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.134607] [drm] Initialized vc4 0.0.0 20140616 for axi:gpu on minor 1
[    6.209803] vc4-drm axi:gpu: [drm] fb0: vc4drmfb frame buffer device
[    7.864120] elogind-daemon[1347]: Watching system buttons on /dev/input/event4 (vc4-hdmi-0)
[    7.864222] elogind-daemon[1347]: Watching system buttons on /dev/input/event5 (vc4-hdmi-1)

Xorg.0.log

Code: Select all

[    62.079] (--) Log file renamed from "/var/log/Xorg.pid-2366.log" to "/var/log/Xorg.0.log"
[    62.081] 
X.Org X Server 1.21.1.9
X Protocol Version 11, Revision 0
[    62.081] Current Operating System: Linux percy_pi 6.1.64-v8-16k+ #1702 SMP PREEMPT Wed Nov 29 14:26:42 GMT 2023 aarch64
[    62.081] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1  smsc95xx.macaddr=D8:3A:DD:C3:28:6F vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000  usb-storage.quirks=152d:0578:u dwc_otg.lpm_enable=0 root=/dev/sda2 rootfstype=ext4 fsck.repair=yes usbhid.mousepoll=0 rootwait cma=256M@256M net.ifnames=0
[    62.081]  
[    62.081] Current version of pixman: 0.42.2
[    62.081]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    62.081] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    62.081] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec  1 23:35:36 2023
[    62.085] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    62.086] (==) No Layout section.  Using the first Screen section.
[    62.086] (==) No screen section available. Using defaults.
[    62.086] (**) |-->Screen "Default Screen Section" (0)
[    62.086] (**) |   |-->Monitor "<default monitor>"
[    62.086] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    62.086] (==) Automatically adding devices
[    62.086] (==) Automatically enabling devices
[    62.086] (==) Automatically adding GPU devices
[    62.086] (==) Automatically binding GPU devices
[    62.086] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    62.088] (WW) The directory "/usr/share/fonts/misc" does not exist.
[    62.088]    Entry deleted from font path.
[    62.088] (WW) The directory "/usr/share/fonts/TTF" does not exist.
[    62.088]    Entry deleted from font path.
[    62.088] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    62.088]    Entry deleted from font path.
[    62.088] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    62.088]    Entry deleted from font path.
[    62.088] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    62.088]    Entry deleted from font path.
[    62.088] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    62.088]    Entry deleted from font path.
[    62.088] (==) FontPath set to:

[    62.088] (==) ModulePath set to "/usr/lib64/xorg/modules"
[    62.088] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    62.088] (II) Module ABI versions:
[    62.088]    X.Org ANSI C Emulation: 0.4
[    62.088]    X.Org Video Driver: 25.2
[    62.088]    X.Org XInput driver : 24.4
[    62.088]    X.Org Server Extension : 10.0
[    62.089] (++) using VT number 7

[    62.089] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[    62.091] (II) xfree86: Adding drm device (/dev/dri/card0)
[    62.091] (II) Platform probe for /sys/devices/platform/axi/1002000000.v3d/drm/card0
[    62.091] (II) xfree86: Adding drm device (/dev/dri/card1)
[    62.091] (II) Platform probe for /sys/devices/platform/axi/axi:gpu/drm/card1
[    62.108] (II) no primary bus or device found
[    62.108]    falling back to /sys/devices/platform/axi/1002000000.v3d/drm/card0
[    62.108] (II) LoadModule: "glx"
[    62.117] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    62.130] (II) Module glx: vendor="X.Org Foundation"
[    62.130]    compiled for 1.21.1.9, module version = 1.0.0
[    62.130]    ABI class: X.Org Server Extension, version 10.0
[    62.130] (==) Matched modesetting as autoconfigured driver 0
[    62.130] (==) Matched fbdev as autoconfigured driver 1
[    62.130] (==) Assigned the driver to the xf86ConfigLayout
[    62.130] (II) LoadModule: "modesetting"
[    62.130] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[    62.135] (II) Module modesetting: vendor="X.Org Foundation"
[    62.135]    compiled for 1.21.1.9, module version = 1.21.1
[    62.135]    Module class: X.Org Video Driver
[    62.135]    ABI class: X.Org Video Driver, version 25.2
[    62.135] (II) LoadModule: "fbdev"
[    62.135] (WW) Warning, couldn't open module fbdev
[    62.135] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    62.135] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    62.142] (WW) Falling back to old probe method for modesetting
[    62.142] (WW) Falling back to old probe method for modesetting
[    62.157] (II) modeset(G0): using drv /dev/dri/card1
[    62.157] (EE) No devices detected.
[    62.157] (EE) 
Fatal server error:
[    62.157] (EE) no screens found(EE) 
[    62.157] (EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
[    62.157] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    62.157] (EE) 
[    62.226] (EE) Server terminated with error (1). Closing log file.

[NeddySeagoon]

HuskyDog,

I can reproduce your symptoms here.
It works, for a low value of works, with the fbdev driver but not with the real -kms- or -fkms- overlays.

-- edit --

I've tried the live mesa now. Still 'negative function'.

[HuskyDog]

Mr Seagoon,

Thank you very much for your efforts on this problem. Your ability to reproduce the symptoms is good news in that it suggests that I am not being completely senile (an increasing problem these days) but it also suggests that perhaps the solution isn't immediately obvious.

Can you just explain exactly what you did to enable the partially functioning fbdev driver?

I have been looking very carefully at the log files and comparing the Pi 5 and Pi 4 versions and I notice a couple of differences which may or may not be relevant.

If we look at the Xorg log file for the Pi 5 it includes the following lines:

Code: Select all

[    62.108]    falling back to /sys/devices/platform/axi/1002000000.v3d/drm/card0
...
[    62.157] (II) modeset(G0): using drv /dev/dri/card1

Note how it "falls back" to card0 and then tries to modeset using card1

On the Pi 4 I have the following equivalent lines:

Code: Select all

[    40.528]    falling back to /sys/devices/platform/gpu/drm/card1
...
[    40.607] (II) modeset(0): using drv /dev/dri/card1

The other difference which may be significant is that on the Pi 5 there is frequent reference to AXI connections (as in the log above) whereas this isn't present at all on the Pi 4. See for example the vc4 lines from dmesg in my previous post. If I do dmesg | grep axi on my Pi 4 I don't get any output at all.

[NeddySeagoon]

HuskyDog,

Add fbdev to VIDEO_CARDS are rebuild everything affected.

Remove vc4 v3d from VIDEO_CARDS or make a file called /etc/X11/xorg.conf.d/video.conf
with the following content ,,,

Code: Select all

Section "Device"
        Identifier "Pi5"
#        Driver "modesetting"
       Driver "fbdev"
EndSection

The automatics will choose modesetting, if its available.
That file says to use the fbdev driver anyway.
It makes testing modesetting easy too.

I have VIDEO_CARDS="fbdev vc4 v3d"

The Pi4 and Pi5 have different GPUs. The Pi range, up to and including the Pi4 use the VC4.
The Pi5 has a more powerful VC6.

Both the kernel and mesa need patches for the VC6. The kernel patches are in the Pi kernel but not yet in mainline.
The mesa patches are supposedly in mesa-23.3.0 and its earlier _rcX testing versions.
That's in ~arm64. If you don't have testing mesa, you need to keyword it and emerge the testing mesa.
It doesn't work here, so its required but not sufficient.

[NeddySeagoon]

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..

[HuskyDog]

Mr Seagoon,

Again, thank you for your reply.

Unfortunately I can't seem to get fbdev working, but since I can't get it to work on either the Pi4 or Pi5 it is no doubt due to my incompetence.

When I added 'fbdev' to VIDEO_CARDS and entered "emerge -aDU world" there was nothing which needed emerging which sounds unlikely. I emerged xf86-video-fbdev anyway, but it still doesn't seem to work. When I start sddm as I usually do, I get three lines of which the last is "DAEMON: Logind Interface found" and then nothing else. No login screen (or indeed any other graphics) appears at all. I do have a /dev/fb0.

I already have the testing version of Mesa installed.

Code: Select all

rs@percypi ~ $ equery l mesa
 * Searching for mesa ...
[IP-] [  ] media-libs/mesa-23.3.0:0

My key question however is this: Does one of us need to create a bug report about this problem for the attention of the Mesa packagers?

[HuskyDog]

Mr Seagoon,

It looks like we were both typing posts at the same time. :lol:

I will start looking into Wayland but I've never used it and I hear that it is a bit complicated (but that might just be bad publicity).

[NeddySeagoon]

HuskyDog,

It probably means one of us has made a pigs ear of it somewhere if fbdev does not work.
We don't yet know its a mesa problem. It may be Xorg, so a bug report is premature.
All we know is that end to end, it fails.

Code: Select all

$ eix fbdev
[I] x11-drivers/xf86-video-fbdev

Adding fbdev to VIDEO_CARDS should have pulled in x11-drivers/xf86-video-fbdev. Is it installed now?
If not, for testing do

Code: Select all

emerge -1av xf86-video-fbdev

since you don't want it in your world set.

fbdev will not use mesa. It won't even use the GPU. The CPU has to plot every pixel.
If you have a long memory, like the original Hercules graphics card for the PC.

My Pi5 make.conf is

Code: Select all

# These settings were set by the catalyst build script that automatically
# built this stage.
# Please consult /usr/share/portage/config/make.conf.example for a more
# detailed example.

CPU_FLAGS_ARM="edsp neon thumb vfp vfpv3 vfpv4 vfp-d32 aes sha1 sha2 crc32 v4 v5 v6 v7 v8 thumb2"

COMMON_FLAGS="-mcpu=cortex-a76+crc+crypto -O2 -pipe -mtune=cortex-a76"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"

# WARNING: Changing your CHOST is not something that should be done lightly.
# Please consult https://wiki.gentoo.org/wiki/Changing_the_CHOST_variable before changing.
CHOST="aarch64-unknown-linux-gnu"

# NOTE: This stage was built with the bindist Use flag enabled

ACCEPT_KEYWORDS="~arm64"
ACCEPT_LICENSE="linux-fw-redistributable"


# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C.utf8

GENTOO_MIRRORS="http://www.mirrorservice.org/sites/distfiles.gentoo.org/ 
                http://ftp.free.fr/mirrors/ftp.gentoo.org/ 
                http://ftp.snt.utwente.nl/pub/os/linux/gentoo 
                http://mirrors.soeasyto.com/distfiles.gentoo.org/ 
                http://gentoo.mirror.root.lu/ 
                http://mirror.bytemark.co.uk/gentoo/ 
                http://ftp.belnet.be/pub/rsync.gentoo.org/gentoo/ 
                http://mirror.netcologne.de/gentoo/"

FEATURES="buildpkg" 

MAKEOPTS="-j5"

USE="cddb gtk3 lvm thin
     gles2 wayland"

L10N="en en-GB en-US"

VIDEO_CARDS="fbdev v3d vc4"
INPUT_DEVICES="evdev libinput"

[HuskyDog]

Mr Seagoon,

It is more than likely that I am the one with the pig's ear!

I definitely have xf86-video-fbdev installed.

Code: Select all

# equery l xf86-video-fbdev
 * Searching for xf86-video-fbdev ...
[IP-] [  ] x11-drivers/xf86-video-fbdev-0.5.0-r1:0

Yes, I do just about remember the Hercules cards.

It turns out that I have had the wayland use flag set for some time. I just haven't been using Wayland. I had a quick go at getting Wayland to start on my Pi4 by adding DisplayServer=wayland to /etc/sddm.conf.d/01gentoo.conf, but when I tried to run sddm I just got a bunch of errors. Perhaps there is something else I need to install or turn on.

Code: Select all

# qlist -I wayland
dev-libs/plasma-wayland-protocols
dev-libs/wayland
dev-libs/wayland-protocols
dev-qt/qtwayland
dev-qt/qtwaylandscanner
dev-util/wayland-scanner
kde-plasma/kwayland
kde-plasma/kwayland-integration
x11-base/xwayland

[NeddySeagoon]

HuskyDog,

You are the Wayland expert here. My experience goes back as far the post when I said it was emerging, just over 2 hours ago :)
I have managed to start Sway but Xorg is still installed, so I don't know what graphics drivers its using.
I don't even know where to find a useful log file yet either.

[HuskyDog]

You are the Wayland expert here. My experience goes back as far the post when I said it was emerging, just over 2 hours ago

The blind leading the blind!

[NeddySeagoon]

HuskyDog,

With sway running lsof shows

Code: Select all

sway      7024 7028 sway:disk        roy mem       REG              179,4  13517416 23608957 /usr/lib64/dri/vc4_dri.so

and lots of

Code: Select all

sway      7024 7027 sway:disk        roy  10u      CHR              226,1       0t0      529 /dev/dri/card1

which took me by surprise, as I was expecting card0

That vc4_dri file is owned by mesa

Code: Select all

Pi5 ~ # equery b /usr/lib64/dri/vc4_dri.so
 * Searching for /usr/lib64/dri/vc4_dri.so ... 
media-libs/mesa-23.3.0 (/usr/lib64/dri/vc4_dri.so)

which suggests that mesa works on the VC6 GPU.

I have no idea how to use sway but its not using any xorg-server or drivers as I ripped those out.
They don't show in lsof either.

I think that means mesa is in the clear. I don't want to use Wayland but using fbdev is like driving a Ferrari stuck in 2nd gear. It may not be that good.

[HuskyDog]

Mr Seagoon,

I am pleased to be able to report some partial success. I am typing this in Firefox running on my Pi5 and the graphics so far seem to be OK. I can watch videos on YouTube and MP4s in VLC so it is as least doing something.

I also get mentions of vc4_dri and card1 when I run lsof.

I don't know exactly what I did to make it go and I need to do some more experiments, but the key step which worked for me was to install "weston". I couldn't get this to work with sddm, but on an off chance I just typed "weston" on the console and a GUI screen appeared. I don't seem to have an proper window manager as there is only one button which opens a terminal. However, if I then type "firefox" or "vlc" then the programme appears and seems to work. There is window decoration and I can change the size of the windows and move them about etc. If I minimise a window then I can't figure out how to get it back again.

The key point however is that I have at least got the GUI working and apparently accelerated.

If I discover more then I'll post again later.

[NeddySeagoon]

HuskyDog,

Weston is the reference implementation of Wayland.
That's cheating :)
Sway is another Wayland thing. That worked for me too.

I want to replace an old AMD E-350 (ASUS E35M1-I DELUXE) with a Pi 5.
The replacement needs to be silent and self contained. The Pi5 with the M.2 HAT that fits in the case would do nicely.
Its also got to run exactly the same software (that implies Xorg), so my technophobe wife can't tell the difference :).
The user interface cannot change.

That E-350 is so old it used to net-boot to comply with the silent requirement because SSDs were small and expensive.

As the Pi Foundation have given up supporting Xorg from the Pi5 on, I expect sympathy from official sources to make Xorg work will be minimal or less.

[HuskyDog]

Mr Seagoon,

I feel your pain!

I've been doing a bit more research and have the following observations:

On this page https://www.raspberrypi.com/news/bookwo ... rry-pi-os/ we find the following statement:

...the Advanced Settings menu in raspi-config includes options to re-enable the old X11/Openbox display system...

This suggests to me that all of the patches required to get X to run at least reasonably well on the Pi5 are out there somewhere. Perhaps we just have to be a bit more patient for them to come through.

Raspberry Pi OS apparently uses the "Wayfire" compositor which is available on Gentoo so perhaps I'll try it. I suspect that the issue will still be one of getting it to work with a desktop environment.

Personally I have been using Plasma on my Pi4 and am keen to stay with it. I read that Plasma 6 is supposed to have better support for Wayland and be designed to use it in preference to X11 where possible. I note that this isn't even in testing yet for Gentoo.

I suspect that the best plan for me is probably going to be to wait a little while for the remaining Mesa patches to bubble through to Gentoo and stick with X at least until Plasma 6 stabilises and I can switch relatively painlessly to Wayland.

My final observation is to note that we are practically the only contributors to this thread. It seems unlikely that we are the only two trying to get Gentoo working properly on the Pi5 so I wonder what experience others are having.

[NeddySeagoon]

HuskyDog,

I've spent an evening on IRC in #raspberrypi with clever.
He's helped me find lots of things that don't work.

I plan to try PiOS after I've slept.
Being old and cynical, I expect that PiOS won't work either and it fakes something with xwayland, or something like that.

Plasma6 will be in an overlay.
It won't get moved to the ::gentoo repo until its ready for ~arch almost.
Maybe that's not the right overlay but its the same idea.

[NeddySeagoon]

HuskyDog,

PiOS has working Xorg but I don't know how. Yet ...

[NeddySeagoon]

HuskyDog,

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

Code: Select all

# Shamelessly copied from PiOS

Section "OutputClass"
  Identifier "vc4"
  MatchDriver "vc4"
  Driver "modesetting"
  Option "PrimaryGPU" "true"
EndSection

That replaces the video.conf which I was suggesting earlier.

That gets me working Xorg on the Pi 5.

I can't actually use it until I set up a dvorak-uk keyboard for Xorg but I know how to do that. :)

[pingtoo]

NeddySeagoon,

Does this mean the vc4 overlay is loaded?

I am under impression that you said /boot/config.txt does not have dtoverlay=vc4 or v3d

I don't have my pi5 yet. But not able use X make me a little bit of anxiety, I am not ready for wayland.