ChanServ changed the topic of #panfrost to: Panfrost - FLOSS Mali Midgard + Bifrost + Valhall - Logs https://oftc.irclog.whitequark.org/panfrost
Daanct12 has joined #panfrost
Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #panfrost
Daanct12 has quit [Ping timeout: 480 seconds]
Daanct12 has joined #panfrost
pbrobinson has quit [Remote host closed the connection]
warpme has joined #panfrost
paulk has joined #panfrost
paulk-bis has quit [Read error: Connection reset by peer]
rasterman has joined #panfrost
warpme has quit []
warpme has joined #panfrost
simon-perretta-img has quit [Ping timeout: 480 seconds]
warpme has quit []
warpme has joined #panfrost
simon-perretta-img has joined #panfrost
digetx has quit [Read error: Connection reset by peer]
digetx has joined #panfrost
rasterman has quit [Quit: Gettin' stinky!]
rasterman has joined #panfrost
tomeu has quit [Quit: Bridge terminating on SIGTERM]
kusma has quit [Quit: Bridge terminating on SIGTERM]
nergzd723 has quit [Write error: connection closed]
pbrobinson has joined #panfrost
robmur01 has quit [Read error: Connection reset by peer]
robmur01 has joined #panfrost
disastroustwitch[m] has joined #panfrost
warpme has quit []
<jannh> is there a guide somewhere on how to run a mainline kernel you've built yourself on the rock 5b? (or is that a bad idea and I should be using another tree?)
<CounterPillow> Most stuff should be in 6.11, so just building the mainline kernel from kernel.org will work if you have all the right drivers enabled. But the debian images from collabora are definitely an easy way to run something close to mainline
Daanct12 has quit [Quit: WeeChat 4.4.3]
kusma has joined #panfrost
Net147 has quit [Remote host closed the connection]
Net147 has joined #panfrost
rasterman has quit [Quit: Gettin' stinky!]
rasterman has joined #panfrost
warpme has joined #panfrost
jenneron[m] has joined #panfrost
psydroid[m] has joined #panfrost
tomeu has joined #panfrost
warpme has quit []
pbrobinson has quit [Ping timeout: 480 seconds]
warpme has joined #panfrost
warpme has quit []
warpme has joined #panfrost
warpme has quit []
pbrobinson has joined #panfrost
rasterman has quit [Quit: Gettin' stinky!]
pbrobinson has quit [Ping timeout: 480 seconds]
<jannh> wow, that was easy, I just built an upstream kernel, installed it as normal, rebooted it, and the machine comes up. I did not realize running a custom kernel on an arm64 system could be this easy
intrigus has joined #panfrost
<jannh> magical
<jannh> well, not entirely magical, my display doesn't show anything, but that's fine, I really only need my ssh shell ^^
<jannh> (and the kernel is complaining that the collabora debian image doesn't have the firmware-realtek package from non-free-firmware)
<bluetail> CounterPillow jannh from 6.10 to 6.11 there are a couple regressions. I just faced https://forums.gentoo.org/viewtopic-p-8845746.html today. So now my server is on LTS.
<CounterPillow> why would that be relevant to rk3588
<bluetail> I tried to say, please start testing from the earliest supported kernel, then work your way up, recent kernels have regressions.
<CounterPillow> every kernel has regressions
<bluetail> Even the first kernel ever made? Sorry. This is too much what about for me :D
ahmubashshir has quit [Remote host closed the connection]
ahmubashshir has joined #panfrost
warpme has joined #panfrost
warpme has quit []
<linkmauve> bluetail, the point is, instead of staying on LTS forever, it’s much more helpful to run mainline and to report the regressions you find on the way.
<bluetail> Thanks for the clarification. Appreciate it.
<linkmauve> Although last time I did find a regression, it had already been fixed a few days before but not yet in mainline, only in drm-next or something.
<CounterPillow> bluetail: you won't get any less bugs running older kernels. Even LTS branches that just get fixes backported introduce new regressions (see, recent ext4 corruption bug). "But new kernel has some unrelated bugs to the platform at hand" is not useful information.
<bluetail> but when I used most recent one, my disk went into read-only state despite nothing wrong, I guess using the old kernel is better for me at the moment... I need to use the machine, maybe I should just upgrade very rarely on my server
<jannh> ah, my usecase is different, I just want to tinker with the newest panthor driver
intrigus has quit []
kinkinkijkin has joined #panfrost
samuelig_ has joined #panfrost
samuelig has quit [Read error: Connection reset by peer]
bluetail has quit [Quit: The Lounge - https://thelounge.chat]
bluetail has joined #panfrost
pbrobinson has joined #panfrost
kinkinkijkin has quit [Quit: Leaving]