2026-05-23.log

+ siviq (~siviq@user/siviq)00:03
- siviq (QUIT: Client Quit) (~siviq@user/siviq)00:04
- digitalrane (QUIT: Server closed connection) (~digitalra@user/digitalrane)00:19
+ digitalrane (~digitalra@user/digitalrane)00:32
+ aloo_shu_ (~aloo_shu@90.166.98.94)00:45
- aloo_shu (QUIT: Ping timeout: 264 seconds) (~aloo_shu@90.166.98.235)00:46
* aloo_shu_ -> aloo_shu00:46
lidstahaah, exactly the same as described in this post: https://community.mnt.re/t/screen-ghosting-glitches-with-classic-reform-rk3588/348000:47
lidstahbut with more glitches00:47
lidstahand in specific circumstances (charging, or heat)00:47
- Ar|stote|is (QUIT: Ping timeout: 245 seconds) (~linx@149.210.0.44)00:52
+ Ar|stote|is (~linx@149.210.0.44)00:56
- mjw (QUIT: Ping timeout: 256 seconds) (~mjw@gnu.wildebeest.org)00:59
- bremner (QUIT: Remote host closed the connection) (~bremner@notmuch/developer/bremner)01:23
+ bremner (~bremner@notmuch/developer/bremner)01:24
- f_ (QUIT: Ping timeout: 245 seconds) (16abab341f@postmarketOS/funderscore)01:33
+ f_ (16abab341f@postmarketOS/funderscore)01:42
- Ar|stote|is (QUIT: Read error: Connection reset by peer) (~linx@149.210.0.44)02:34
+ Ar|stote|is (~linx@149.210.0.44)02:40
- paperManu (QUIT: Ping timeout: 272 seconds) (~paperManu@204.244.197.237)03:26
- paperManu_ (QUIT: Ping timeout: 252 seconds) (~paperManu@204.244.197.237)03:26
+ paperManu (~paperManu@79.127.134.36)03:39
+ robin (~robin@user/terpri)03:43
- paperManu (QUIT: Read error: Connection reset by peer) (~paperManu@79.127.134.36)04:22
- spew (QUIT: Quit: nyaa~) (~spew@user/spew)06:15
- RandyK (QUIT: Remote host closed the connection) (~RandyK@user/randyk)06:18
+ RandyK (~RandyK@user/randyk)06:18
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)07:08
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)07:08
- digitalrane (QUIT: Ping timeout: 248 seconds) (~digitalra@user/digitalrane)08:55
+ digitalrane (~digitalra@user/digitalrane)08:59
- digitalrane (QUIT: Ping timeout: 265 seconds) (~digitalra@user/digitalrane)09:04
+ digitalrane (~digitalra@user/digitalrane)09:06
+ jn (~quassel@2a0a-a54a-54d9-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)09:16
- jn (QUIT: Changing host) (~quassel@2a0a-a54a-54d9-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)09:16
+ jn (~quassel@user/jn/x-3390946)09:16
+ mjw (~mjw@gnu.wildebeest.org)11:22
- digitalrane (QUIT: Ping timeout: 272 seconds) (~digitalra@user/digitalrane)12:05
+ talos2 (~talos@2600:6c5d:f0:1fd0:7eca:1cae:4d61:aa9e)12:40
- talos (QUIT: Ping timeout: 250 seconds) (~talos@2600:6c5d:f0:1fd0:e23e:9d8a:ea7a:8d3)12:42
* talos2 -> talos12:42
joschminute: i rebased the patches onto linux 7.1: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/18313:10
joschlinux is already building13:10
joschi was just patching qcacld2 which also broke and am now running another build13:10
joschthis is a draft MR and requires linux 7.1-rc4 from experimental13:10
joschmaybe you can have a look at the patches which collabora dropped in the MR description13:11
+ paperManu (~paperManu@204.244.197.237)13:36
lidstahdisplay port reseating: check, this machine is so serviceable14:17
lidstahI moved the display cable away from the wifi card too14:17
lidstahnow, will I still have interference when it's warm/hot out there (exactly the same kind than in this post: https://community.mnt.re/t/screen-ghosting-glitches-with-classic-reform-rk3588/3480 , d_m video's glitches are identical to mine (kinda grey/green horizontal lines)14:20
+ digitalrane (~digitalra@user/digitalrane)14:20
lidstahmmh, seems better. tried charging+kotor2, got one glitch but i'm not sure if it's not a zink glitch xD15:02
+ siviq (~siviq@user/siviq)16:38
- siviq (QUIT: Quit: Client closed) (~siviq@user/siviq)16:46
+ paperManu_ (~paperManu@204.244.197.237)16:57
- paperManu_ (QUIT: Client Quit) (~paperManu@204.244.197.237)17:02
+ stephano (~stephano@71.238.14.13)17:16
- stephano (QUIT: Ping timeout: 256 seconds) (~stephano@71.238.14.13)17:21
+ stephano (~stephano@71.238.14.13)17:23
stephanoOne of the build machines I use cannot connecto to https://source.mnt.re/. Seems to be only that IP having the issue, as all my other build machines connect without issues.17:25
aloo_shucheck the usual suspects, dronebl, spamhsus?17:40
+ spacematty (41cc4b39e0@irc.cheogram.com)17:46
stephanoaloo_shu: checked that, just found 1 listing on Policy Block List (it's on a Comcast residential connection in the US)17:47
stephanoNothing on dronebl17:48
- talos (QUIT: Ping timeout: 246 seconds) (~talos@2600:6c5d:f0:1fd0:7eca:1cae:4d61:aa9e)18:13
+ talos (~talos@2600:6c5d:f0:1fd0:7d2d:a58b:3093:2886)18:16
minutestephano: sorry it's firewall automation due to recent ai crawler waves19:14
- f_ (QUIT: Ping timeout: 246 seconds) (16abab341f@postmarketOS/funderscore)19:14
stephanominute: oh no worries. the ai crawler insanity is everywhere, sadly.19:21
stephanominute: is there something I can do on my end?19:21
+ f_ (16abab341f@postmarketOS/funderscore)19:23
- S0rin (QUIT: Quit: WeeChat 4.6.3) (~S0rin@user/s0rin)19:24
+ S0rin (~S0rin@user/s0rin)19:32
+ FirefoxDeHuk (~FirefoxDe@user/FirefoxDeHuk)19:34
- FirefoxDeHuk (QUIT: Client Quit) (~FirefoxDe@user/FirefoxDeHuk)19:35
minutestephano: by any chance did you use an electron app to access the gitlab?20:26
stephanominute: possibly a while ago. i've been trying out new dev environments. as of now though I'm still just using vim. :)20:32
joschminute: this one is ready and builds fine for linux 7.1 and is now waiting for your review: https://source.mnt.re/reform/qcacld2/-/merge_requests/17 thank you!20:35
+ paperManu_ (~paperManu@104.163.176.82)21:08
- paperManu_ (QUIT: Ping timeout: 244 seconds) (~paperManu@104.163.176.82)21:13
+ paperManu_ (~paperManu@204.244.197.237)21:14
- paperManu_ (QUIT: Ping timeout: 252 seconds) (~paperManu@204.244.197.237)21:22
+ paperManu_ (~paperManu@104.163.176.82)21:24

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!