2026-03-07.log

+ pomel0 (~pomel0@user/pomel0)00:07
- pomel0 (QUIT: Ping timeout: 264 seconds) (~pomel0@user/pomel0)00:15
- johl (QUIT: Quit: leaving) (~johl@wikidata/Jens-Ohlig)00:18
+ pomel0 (~pomel0@user/pomel0)00:18
- pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0)00:20
+ pomel0 (~pomel0@user/pomel0)00:20
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)00:31
+ qbit (~qbit@user/qbit)00:32
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)00:32
+ qbit (~qbit@user/qbit)00:34
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.0.129)01:00
+ Ar|stote|is (~linx@149.210.0.129)01:00
+ siviq (~siviq@user/siviq)01:05
- siviq (QUIT: Client Quit) (~siviq@user/siviq)01:06
+ bkeys (~Thunderbi@98.19.131.29)01:33
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@98.19.131.29)01:33
- paperManu_ (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156)03:10
- paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@146.71.9.156)03:10
- nsc (QUIT: Ping timeout: 246 seconds) (~nicolas@i5C74DEE7.versanet.de)03:25
+ nsc (~nicolas@i5C74DC78.versanet.de)03:27
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)03:43
+ paperManu (~paperManu@146.71.9.156)03:46
aloo_shuI dimly remember things such as silver paint for fixing breakage on printed circuit boards04:01
- paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@146.71.9.156)04:09
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.0.129)04:16
+ Ar|stote|is (~linx@149.210.0.129)04:22
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.0.129)06:00
+ Ar|stote|is (~linx@149.210.0.129)06:00
- RandyK (QUIT: Remote host closed the connection) (~RandyK@user/randyk)08:53
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)08:53
+ RandyK (~RandyK@user/randyk)08:54
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)08:54
+ bpye (~bpye@user/bpye)10:07
bpyeHey folks - my Pocket Reform unfortunately killed another charger board earlier this week. I opened a support ticket on Tuesday, how long should it take to get a response?10:08
+ mjw (~mjw@gnu.wildebeest.org)11:30
+ andreas-e (~Andreas@2a02:8434:b6a3:e901:facc:8e87:8e54:890d)11:57
+ siviq (~siviq@user/siviq)12:06
- siviq (QUIT: Client Quit) (~siviq@user/siviq)12:08
+ aloo_shu_ (~aloo_shu@90.166.193.246)12:44
+ AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net)12:44
- aloo_shu (QUIT: Ping timeout: 248 seconds) (~aloo_shu@85.51.16.76)12:45
* aloo_shu_ -> aloo_shu12:45
+ vyvv (~vyvv@user/vyvv)13:28
+ paperManu (~paperManu@146.71.9.156)14:04
- pasta161 (QUIT: Quit: WeeChat 4.8.1) (~pasta161@user/xha)16:38
+ mntirc (~mntirc@softboy.mntmn.com)17:00
mntirchmm, looks like my bouncer exited all channels before17:01
* mntirc -> minute17:02
* ChanServ changed mode (+o, minute)17:03
minutegood to be back!17:09
minutewhat did i miss? :D17:09
joschminute: maybe something concerning which i left in the issue tracker so that it doesn't get lost:17:09
joschhttps://source.mnt.re/bugs/bugs/-/issues/5117:10
minutejosch: ah i see. this bug is well known to me, and it doesn't occur currently with kcxt's cleaned up panel driver on the quasar pocket (or very rarely? it might be stemming from missing panel hardware reset), but the privacy issue you're seeing is a type of ghosting17:13
minutejosch: i.e. the leftover pixel data is imprinted in the panel itself17:13
joschminute: and bpye opened a support ticket and was wondering when a response could be expected17:13
minutejosch: did bpye mention a ticket number?17:13
joschno17:14
joschminute: what do yo umean by "imprinted" -- as in: forever?17:14
minutejosch: no, for a while, until the ghosting disappears17:17
joschokay, so that's an orthogonal issue of that display17:17
joschi hadn't seen that before17:17
minutejosch: this issue is probably more common than is generally known (among displays), they are normally not exposing this issue though because it's not driven in this wrong way17:18
minutejosch: so that might be an interesting attack vector on devices with tft displays17:18
joschfun17:18
minutejosch: you can probably mitigate this by using different color schemes17:18
minutejosch: i.e. stuff that doesn't have certain contrasts probably17:19
joschminute: when at some point you have time, linux 6.19 got uploaded to Debian yesterday so this MR now becomes more interesting and would benefit from your review: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/16617:19
minutejosch: gray is afaik a problematic "color" where all kinds of strange issues can happen 17:20
minutehttps://lcd-mikroelektronik.de/en/news/image-sticking-bei-tfts/17:20
minutei wonder why the hell screen savers were abolished17:20
minutei really miss them in gnome...17:20
joschminute: thank you, i updated my comment with an edit at the top to not be misleading anymore17:21
minutei guess people were erroneously thinking that burn-in became a thing of the past when transitioning from CRTs17:21
minutejosch: https://forums.macrumors.com/attachments/tempimagei7pbzm-png.1690229/17:23
minute(example)17:23
joschoh wow o017:23
minutejosch: i experienced stuff like that with my retina macbook pro 2013 back in the day :D17:24
minutejosch: btw i'm using qcs6490 in this pocket reform at the moment, and running in EL2, no hypervisor, with gpu and sound and stuff17:25
minutejosch: we tested qemu-system-aarch64 with kvm yesterday and it worked!17:25
minutethis also means we don't need the ADSP for audio, one blob less17:25
rick_Wait its not only a crt issue? 0.0 Interesting17:26
joschminute: this is *really* really cool -- thank you to all involved!17:26
minutejosch: btw i just rediscovered there are applications and websites that attempt to remove tft burn-in17:27
minutejosch: by displaying certain sequences of full screen colors/patterns17:27
joschnow i'm looking forward to buying one of the qualcomm boards for myself as well :)17:28
joschminute: what i'm hearing is another reason to get this funky screensaver with the colorful pipes from windows 98 back :D17:30
minutejosch: absolutely. someone should write a gnome extension or so that can run the xscreensaver modules :D17:30
minutejosch: i think qcs6490 could be a worthy sequel to the a311d17:31
joschwhy not to rk3588? because of the connectivity?17:31
minutejosch: mostly because of RAM i think17:31
joschah kk17:31
minutejosch: the current chip crisis has the lucky side effect that the c6490p som is bumped to 8gb lpddr5 (from 6gb)17:32
joschoh more funny ghosting: https://mister-muffin.de/p/O63U.jpg17:32
minutejosch: ah yes, what you see here is a leftover from the previous glitch where it was driving the panel wrongly17:32
joschwhy would the chip crisis lead to a memory *bump*?17:32
minutejosch: because the hybrid 6gb+ufs chip they used before got discontinued suddenly, so thundercomm had to reengineer the module17:33
joschups17:33
joschminute: ah and another thing you may have missed is that johl tried to get their hdmi port repaired but got told that it cannot be repaired because one of the pads ripped off. In the forum there was another case where the hdmi port fell off. No idea whether that can be improved in the upcoming pocket reform motherboard design.17:37
minutejosch: right. i'll check if there's a better connector, but maybe it needs to be mechanically supported with some 3d printed attachment to the port cover or mb screws17:38
+ siviq (~siviq@user/siviq)17:51
minuteblender with cycles rendering in the editor on qcs6490 pocket https://mastodon.social/@mntmn/11618900736337170118:15
siviqIs it too early to ask for benchmark comparison with RK3588? :)18:20
joschonce i get my hands on it, i'll redo the power consumption benchmark with it :)18:26
siviqThat would be nice, TY josch.18:29
joschsiviq: what kind of benchmark would you like to see? there isually is glmark2 and 7z benchmarks on shop.mntre.com18:31
siviqjosch Yes, same comparison as a the website. I saw minute mention the QCS6490 is also more energy and temperature efficient, if those values can be compared with the rest of the CPUs, would be good too. Having options for MNT Reform is what bought me into it.18:41
- amospalla (QUIT: Quit: WeeChat 4.8.1) (~jordi@user/amospalla)18:45
minutesiviq: ok, can run the benchmarks18:47
siviqExciting, thank you!19:02
+ paperManu_ (~paperManu@142.169.16.105)19:08
minutesiviq: added qcs6490 benchmarks (taken on gnome on pocket reform on postmarketos) https://source.mnt.re/reform/reform/-/tree/master/reform2-benchmarks19:13
minutesiviq: in this 7z -b test, the qcs6490 is even a bit slower in total than rk3588. but the gpu perf is much better19:15
minutei'll need to repeat this on debian though, as there could be some effects here from the different libc etc19:18
siviqminute the GPU performance of the qcs6490 is ahead of rk3588 with 1000 points (nearly ~29% faster). It's really impressive, will allow more room for graphic intensive applications. The 7z -b test difference is negligible in decompressing (~4%) and around (~16%) compressing in favor of RK3588. Maybe there will be difference with other operating19:28
siviqsystems, but still I won't expect to be too much.19:28
orvaminute: Any guesses what kind of RAM options qcs6490 boards might have?19:31
siviqBoth CPUs are top tier compared to the others available for the MNT devices.19:31
minuteorva: we'll only be able to ship an 8GB version19:41
minutei'm also working on qcs8550 which will have 12GB and even more cpu+gpu perf, but it's not stable yet. also potentially hotter than qcs649019:42
minutei currently see qcs6490 as most interesting for lower cost, smaller systems (pocket, tablet, but also next probably) while still having great general performance. and 8550+8750 more interesting for the bigger laptops19:44
minute(i'm waiting for 8750 engineering samples, it'll be the first chip we can have to surpass 4GHz, but probably a while off to make it work, stable etc)19:45
- pomel0 (QUIT: Ping timeout: 248 seconds) (~pomel0@user/pomel0)19:45
minutein the meantime qcs6490+rk3588 are both good options i think, and rk3588 is still getting new features unlocked (sw video decompression, panvk geometry shaders and performance enhancements, etc)19:45
minutes/sw/hw19:46
+ pomel0 (~pomel0@user/pomel0)19:46
minutealso curious what rk3688 will bring :D19:46
siviqMaybe need to consider active cooling then for faster chip like 8750. Or throttle from factory with opportunity for overclocking :)19:46
minutei don't think that will be necessary @ active cooling. but lets see19:48
orvaIt is bit annoying that hearing 8gb causes instant "well that is too little reaction", it wasn't _that_ long ago when my desktop had that and it was plenty enough. Should probably try recalibrate that feeling at some point19:50
minuteorva: i'm on the 6GB version and it's relatively ok. 8GB will be fine for most mobile things19:53
- paperManu_ (QUIT: Ping timeout: 264 seconds) (~paperManu@142.169.16.105)19:59
joschorva: for those for whom such a reply is the immediate knee-jerk reaction, the reform is probably not for them...20:19
josch(not because the reform will never get "a lot" of ram but because the reason for having a reform should maybe be other things than "a lot of ram")20:19
orvaObviously. It it just annoying how well years of marketing has affected even myself and I kind of think I am quite resilient against that20:23
orvaBut still requires bit "hey cmon, reflect a little on that feeling" for calibration20:23
- andreas-e (QUIT: Quit: Leaving) (~Andreas@2a02:8434:b6a3:e901:facc:8e87:8e54:890d)20:28
orvaAnd TBF, only thing where I am actually conserned about memory usage is llvm based toolchains and their horrendeusly memory hungry linking process20:30
siviqTrue, but for most regular users, 8-16GB of RAM is plenty. That is why I went for 16GB RK3588 and don't consider downgrade not getting the 32GB option while was available. Only regret I have is, there are no more DIY Reforms. But that is also understandable why they took down the option.20:30
joschminute: system image with linux 6.19 if that's convenient for you to check the new kernel yourself: https://source.mnt.re/josch/reform-system-image/-/jobs/1909120:34
- tookmund (QUIT: Quit: WeeChat 4.6.3) (~jacob@2a01:4ff:f0:f7e3::1)20:48
+ tookmund (~jacob@2a01:4ff:f0:f7e3::1)20:52
- siviq (QUIT: Quit: Client closed) (~siviq@user/siviq)20:59
- AnimaInvicta (QUIT: Read error: Connection reset by peer) (~AnimaInvi@88-120-179-216.subs.proxad.net)21:40
+ siviq (~siviq@user/siviq)21:59
kfxjosch: does 6.19 need the aspm cmdline flag22:02
joschkfx: i'm not able to tell you because i have not seen the problems which the aspm=off flag worked around22:06
joschkfx: were you affected?22:09
bpyeminute: sorry about that, the ticket is 1214 22:14
minutejosch: oh neat, many thanks @ 6.1922:28
joschminute: could you enable the gitlab CI runner for this project: https://source.mnt.re/josch/pocket-reform-handbook/22:43
- vyvv (QUIT: Ping timeout: 264 seconds) (~vyvv@user/vyvv)22:57
- pomel0 (QUIT: Remote host closed the connection) (~pomel0@user/pomel0)23:15
- wickedshell (QUIT: Ping timeout: 264 seconds) (~wickedshe@2601:8c0:c7c:3572:6034:a8f7:ca75:637d)23:23
kfxjosch: no, and I'm hoping to keep it that way :)23:26
+ pomel0 (~pomel0@user/pomel0)23:48

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