!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

206 Members
58 Servers

Load older messages

SenderMessageTime
9 Apr 2025
@k900:0upti.meK900Mainline or vendor kernel? How much CMA? Mesa enabled? 08:09:51
@k900:0upti.meK900Oh yeah, UEFI or uboot? If UEFI, ACPI or DT? 08:13:34
@eliasp:kde.orgeliasp

using the raspberry-pi-4 module from nixos-hardware - all other hardware customizations are only related to enabling fkms-3d and fixing 802.11/bluetooth, so:

  • Kernel: pkgs.linuxKernel.packages.linux_rpi4
  • CMA: 512
  • uboot
  • Mesa is enabled

kinfo output:

Operating System: NixOS 25.05
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.6.51 (64-bit)
Graphics Platform: Wayland
Processors: 4 × ARM Cortex-A72
Memory: 7.6 GiB of RAM
Graphics Processor 1: V3D 4.2.14.0
Graphics Processor 2: llvmpipe
Product Name: Raspberry Pi 4 Model B Rev 1.4�
U-Boot Version: 2025.01�
08:35:10
@eliasp:kde.orgeliasp

…and Alt+TAB crashes the kwin wayland compositor 😬

Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: KCrash: Application '.kwin_wayland-wrapped' crashing... crashRecursionCounter = 2
Apr 09 11:08:13 moria-rpi4 kwin_wayland[6714]: QRhiGles2: Failed to make context current. Expect bad things to happen.
Apr 09 11:08:13 moria-rpi4 kwin_wayland[6714]: Failed to create RHI (backend 2)
Apr 09 11:08:13 moria-rpi4 kwin_wayland[6714]: Failed to initialize graphics backend for OpenGL.
Apr 09 11:08:13 moria-rpi4 plasmashell[6727]: QQmlVMEMetaObject: Internal error - attempted to evaluate a function in an invalid context
Apr 09 11:08:13 moria-rpi4 plasmashell[6727]: file:///nix/store/5ffb7vi05bd0q774fmd5h0vmlpyj25hp-plasma-desktop-6.3.4/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:240: TypeError: Property 'modelIndex' of object Task_QMLTYPE_624(0x3011c00) is not a function
09:11:49
@eliasp:kde.orgeliasp I might temporarily switch to 24.11 to see whether this changes anything 09:50:35
@k900:0upti.meK900 Yeah don't do any of that 10:47:34
@k900:0upti.meK900Just run mainline10:47:36
@k900:0upti.meK900 With cma=256M or cma=512M on the command line 10:47:44
@k900:0upti.meK900 And linuxPackages_latest 10:47:53
@eliasp:kde.orgeliasp ok, so basically not following nixos-hardware in that regard... will give it a try! thanks! 10:48:48
@k900:0upti.meK900Throw out the entire nixos-hardware module10:50:03
@k900:0upti.meK900The vendor stack is more trouble than it's worth on that hardware10:50:09
@eliasp:kde.orgeliasp ok, wouldn't have thought that, since it pulls in quite a few customizations, but I'll trust your experience in this regard, since that's the first time I'm really trying to get something meaningful running on this RPi4 10:50:59
@eliasp:kde.orgeliasp

had to drop my devicetree overlay with the bluetooth fix, since otherwise device-tree-overlays.drv would crap its pants: libfdt.FdtException: pylibfdt error -1: FDT_ERR_NOTFOUND

but maybe, the mainline stuff will also just magically fix bluetooth - let's see!

12:15:47
@eliasp:kde.orgeliasp …this kills plymouth (just shows a black screen) and thereby the cryptsetup passphrase entry - will either have to figure out how to fix plymouth or get rid of it and stick with plain-text. 13:25:28
@k900:0upti.meK900 You probably need to add the vc4 and maybe v3d modules to initrd 13:29:54
@eliasp:kde.orgeliasp I already have vc4 in there, but no v3d (isn't that only for DRM?) - will give it a try nonetheless 13:35:52
@eliasp:kde.orgeliasp no success, will go for "no plymouth" instead - I don't really mind (in this case) having it. 13:47:25
@eliasp:kde.orgeliasp Meh, even without Plymouth the screen just turns black during initrd. And it's also not the case of "output is suddenly on the other HDMI port" 14:05:04
@eliasp:kde.orgeliasp

Ooh, but now after waiting a bit...

vc4_hvs fe400000.hvs: Couldn't get core clock

And then falling back to systemd maintenance mode.

14:06:30
@k900:0upti.meK900What kernel version are you using?14:08:30
@eliasp:kde.orgeliaspShould be fixable via DT: https://github.com/raspberrypi/linux/blob/rpi-5.15.y/arch/arm/boot/dts/bcm2711-rpi.dtsi#L5214:08:39
@eliasp:kde.orgeliasp
In reply to @k900:0upti.me
What kernel version are you using?
Latest from unstable, 6.14 		14:09:25
@k900:0upti.meK900And what boot chain are you using?14:09:35
@eliasp:kde.orgeliaspUboot14:09:47
@eliasp:kde.orgeliasp
  • extlinux
14:09:58
@k900:0upti.meK900Maybe update u-boot14:10:04
@k900:0upti.meK900If you haven't done that yet14:10:07
@eliasp:kde.orgeliasp Eeeprom + uboot are up-to-date, that was one of the first things I did trying to fix all this 14:10:51
@k900:0upti.meK900 Do you have any hardware.deviceTree config? 14:11:10

Show newer messages

Back to Room ListRoom Version: 9