dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
Ruen has joined #aarch64-laptops
<Ruen>
JensGlathe: On Fedora's 7.1, after the initial wall of text on boot GDM shows up but scaled improperly and then no matter what I do after 2-3 seconds the display dies completely. Even if I switch to TTY
<Ruen>
I enabled drm.debug=0x1e from grub and journalctl -b -1 | grep drm shows that "simple-framebuffer" gets used instead of msm
<Ruen>
And also a bunch of other stuff I don't know how to read through. Without that parameter it just says that simpledrm was initialized and systemd reported: systemd[1]: modprobe@drm.service - Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!drm
<Ruen>
I'll try your RPM build in a moment, I didn't even know you made them that's pretty cool. I was actually thinking of using your fork as a source to try compile it myself but I don't know how to compile the Linux kernel
Ruen has quit [Remote host closed the connection]
dc7800 has quit [Remote host closed the connection]
hexdump01 has joined #aarch64-laptops
dc7800 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]
ScentedFern has joined #aarch64-laptops
<valpackett>
Ruen: are you running in EL1 without the zap shader binary?
Ruen has joined #aarch64-laptops
<Ruen>
Okay jansglathe's kernel works, one minor hiccup was that I just had to disable stubble and point to the devicetree myself
<Ruen>
sorry, jensglathe's
<Ruen>
valpackett: I am running in EL1 yes and I think with the zap shader. I don't have any issues with Fedora's 6.19 kernel though, that's the one Fedora 44 comes with when you download from their website
<JensGlathe[m]>
The kernel I built was a dev one, no stubble at all. But good that it works
mbuhl has quit [Remote host closed the connection]
mbuhl has joined #aarch64-laptops
Ruen has quit [Remote host closed the connection]
Ruen has joined #aarch64-laptops
<Ruen>
Bug I noticed with your kernel is that apparmor is enabled but Fedora uses selinux, and that seems to make most things that run in a sandbox like google chrome and flatpaks just not work?
<steev>
july update for t14s bios but, even though my last installed update was in june... it says the rom is identical :(
<valpackett>
apparmor should be inert if you don't have rules for it (??) I have shoved an ubuntu kernel into my pmos install for testing and it didn't break anything like that
<Ruen>
Does Fedora have rules for it by default? It did not allow Chrome because of "Userns create restricted"
sri has joined #aarch64-laptops
<JensGlathe[m]>
I just did a make binrpm-pkg with my normal Ubuntu config, so not surprising. You could extract your desired config and do it again
<minecrell[m]>
The X13s has only 4 DSPPs, so night light on 3 displays is only possible if you can cover each screen on a single LM/DSPP, which depends on the display resolution IIRC. Or you would need a GPU fallback path, but I’m not sure if typical Linux desktops implement that
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
<Jadesheher[m]>
hmm is there any else way i can tell my wayland to do nightmode then?
<Jadesheher[m]>
(sway)
<misyl>
minecrell: they usually do
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
pbrobinson has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
SpieringsAE_sff has quit [Quit: SpieringsAE_sff]
SpieringsAE_sff has joined #aarch64-laptops
Gnappo has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
pbrobinson has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
<clover[m]>
just would have saved us some time to have the diff instead of editing files and creating the patch file from it. but now you know the workflow
dc7800 has joined #aarch64-laptops
<Jadesheher[m]>
does this mean it actually is being worked on?
Gnappo has quit [Quit: Connection closed for inactivity]
<clover[m]>
its an open issue with no assignee, so i don't think its being actively worked on
dc7800_ has quit [Ping timeout: 480 seconds]
<clover[m]>
what's more, the patch might not work. the OP wrote that it works well for GNOME, but caused KDE to crash
dc7800 has quit [Remote host closed the connection]
dc7800 has joined #aarch64-laptops
<Jadesheher[m]>
lets see what sway has to say to that
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800_ has quit []
dc7800 has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
Gnappo has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
sri has quit [Quit: Leaving]
<clover[m]>
Narrarator: things did not, in fact, go well
<JensGlathe[m]>
silently sweeping up the debris
<valpackett>
not surprising that it would cause problems, because it's a very cursed "solution" (you can't just overwrite `allow_modeset` to true when the compositor explicitly said no modeset in this commit)
<valpackett>
kinda surprising that it crashes *kwin* of all things, since kwin supports ctm which already went through that exact path
<valpackett>
but that entire path (for ctm too) should not exist, it's bad
<valpackett>
i can see why no one has anticipated anything like this, it's *such* a weird hardware quirk
<JensGlathe[m]>
Updating LUTs shouldn't reshuffle hardware blocks. So the update of LUTs vs hardware block management needs to be re-designed (?). The patch works for me as long as I stay in the 2 displays range.
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
sri has joined #aarch64-laptops
sri has quit []
ScentedFern has quit [Quit: WeeChat 4.10.0]
pbrobinson has quit [Ping timeout: 480 seconds]
Gnappo has quit [Quit: Connection closed for inactivity]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
ScentedFern has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Read error: Connection reset by peer]
FANTOM has quit [Ping timeout: 480 seconds]
FANTOM has joined #aarch64-laptops
jhovold has quit [Ping timeout: 480 seconds]
dc7800_ has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Ping timeout: 480 seconds]
dc7800 has joined #aarch64-laptops
dc7800_ has quit [Read error: Connection reset by peer]
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
dc7800 has quit [Read error: Connection reset by peer]
dc7800 has joined #aarch64-laptops
dc7800_ has joined #aarch64-laptops
dc7800 has quit [Remote host closed the connection]