2023-06-11
00:39nsklaus has quit [Ping timeout: 480 seconds]
00:54tobhe_ has joined #asahi-alt
00:58tobhe has quit [Ping timeout: 480 seconds]
01:21janrinze has quit [Quit: Leaving.]
01:43janrinze has joined #asahi-alt
02:41Mary has quit [Quit: The Lounge - https://thelounge.chat]
02:42Mary has joined #asahi-alt
03:06jnn has joined #asahi-alt
03:10jn has quit [Ping timeout: 480 seconds]
04:14SalimTer- has quit [Remote host closed the connection]
04:19salimterryli has joined #asahi-alt
04:28salimterryli has quit [Quit: ZNC - https://znc.in]
04:31salimterryli has joined #asahi-alt
05:22cylm_ has joined #asahi-alt
05:22cylm has joined #asahi-alt
06:55jannaujanrinze: I don't see artifacts with asahilinux and gentoo and kde/plasma (mbp 14" 3024x1890 and a 4k display)
06:58jannauthe google maps slowness is reproducible. most likely a driver issue whichs copies to much data on the CPU
06:59jannauthere might be issue with gnome software. see the nautilus report in https://github.com/AsahiLinux/linux/issues/72
07:07chadmedfwiw i got only one instance of purple and it was the first time i started firefox after upgrading mesa the other day. havent seen it at all anywhere else as of yet
07:08chadmedand that purple was just a flash for a few frames until the window filled with the firefox start page, never saw it again
07:14MichaelLongjannau, with a mbp 14" _and_ a 4k display? Have I missed something? :)
08:20MichaelLongjannau, ah ok
09:47janrinzejust for now i have switched monitors to reduce any problems. I noticed that if I resize a WebGL window to be larger than the screen it will create the purple blocks etc. Just move the window to the left making it partly offscreen and then adjust its size to become larger by pulling on the corner or side.
09:51janrinzeBefore switching to the latest mesa drivers I did not have this issue. I had self-built the mesa drivers and kernel but cleared out everthing when the announcement was made. The asahi/mesa repo has changed and it seems that i cant revert to that version.
10:07nsklaus has joined #asahi-alt
10:15janrinze has quit [Remote host closed the connection]
10:20janrinze has joined #asahi-alt
10:25janrinzeI just remebered that back then i added a patch from jannau on top of ashi-mesa that was 'Free low VA BOs correctly'. this lead me to reconstruct the asahi-mesa that worked well.
10:31janrinzeThe branch asahi/mesa works ok. no glitching. not even when I boot with a 4k monitor. So something is different between the main branch and the asahi/mesa branch that triggers the issue. unfortunately the branch asahi/mesa has diverged and I have no idea how to 'easily' find the culprit.
10:55hightower2 has joined #asahi-alt
11:04janrinzea diff of the source directory at src/asahi between branch asahi/mesa and tag asahi-20230606 is about 17265 lines..
11:58aafeke_ has joined #asahi-alt
12:13aafeke_ has quit [Quit: aafeke_]
12:15aafeke_ has joined #asahi-alt
12:20maria has quit [Remote host closed the connection]
12:21maria has joined #asahi-alt
12:25aafeke_ has quit [Quit: aafeke_]
12:26aafeke_ has joined #asahi-alt
12:43aafeke_ has quit [Quit: aafeke_]
13:55janrinze has quit [Quit: Leaving.]
14:14janrinze has joined #asahi-alt
16:03hightower2 has quit [Ping timeout: 480 seconds]
16:16possiblemeatball has joined #asahi-alt
16:41rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:41Guest2655 has quit [Quit: Bridge terminating on SIGTERM]
16:44Jamie has joined #asahi-alt
16:45rhysmdnz has joined #asahi-alt
16:45Jamie is now known as Guest2737
18:09janrinze has quit [Quit: Leaving.]
18:12janrinze has joined #asahi-alt
18:14cylm_ has quit [Quit: WeeChat 3.6]
18:14cylm has quit [Quit: WeeChat 3.6]
18:15janrinze has quit [Remote host closed the connection]
18:27hightower2 has joined #asahi-alt
22:10kujeger- has quit [Ping timeout: 480 seconds]
23:29stipa is now known as Guest2765
23:29stipa has joined #asahi-alt
23:30Guest2765 has quit [Read error: Connection reset by peer]