!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

206 Members
57 Servers

Load older messages


SenderMessageTime
9 Apr 2025
@eliasp:kde.orgeliasp ok, so basically not following nixos-hardware in that regard... will give it a try! thanks! 10:48:48
@k900:0upti.meK900 ⚡️Throw out the entire nixos-hardware module10:50:03
@k900:0upti.meK900 ⚡️The 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.meK900 ⚡️What 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.meK900 ⚡️And what boot chain are you using?14:09:35
@eliasp:kde.orgeliaspUboot14:09:47
@eliasp:kde.orgeliasp
  • extlinux
14:09:58
@k900:0upti.meK900 ⚡️Maybe update u-boot14:10:04
@k900:0upti.meK900 ⚡️If 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
@eliasp:kde.orgeliaspNot so far, tried to stick with the defaults so far, but I'll try to apply the fix linked above now to DT14:13:13
@athyfr:matrix.org@athyfr:matrix.org changed their profile picture.20:51:57
11 Apr 2025
@mjm:midna.devmjm changed their profile picture.22:23:13
12 Apr 2025
@amadaluzia:tchncs.deamadaluzia[tde] changed their profile picture.03:43:34
@ilsubyeega:matrix.org@ilsubyeega:matrix.org left the room.04:16:50
@adda0:matrix.orgAdda joined the room.08:56:51
@k900:0upti.meK900 ⚡️Frameworks 6.13 is delayed11:40:07
@k900:0upti.meK900 ⚡️https://kde.org/announcements/frameworks/6/6.13.0/21:15:12
@k900:0upti.meK900 ⚡️Frameworks 6.13 is here21:15:15

Show newer messages


Back to Room ListRoom Version: 9