2025-10-03.log

+ yqshao (~yqshao@user/yqshao)00:01
- svp (QUIT: Read error: Connection reset by peer) (~svp@host-79-7-240-189.business.telecomitalia.it)00:01
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)00:02
- yqshao (QUIT: Client Quit) (~yqshao@user/yqshao)00:03
+ yqshao (~yqshao@user/yqshao)00:03
- wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa)00:10
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)00:23
- LainIwakura (QUIT: Quit: Client closed) (~LainIwaku@user/LainIwakura)00:24
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)00:32
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)00:44
joschminute: just to be sure: in my current setup i have the pocket reform connected to the classic reform with motherboard 3.0 via usb-c and am reading its serial output just fine. There is *no way* that the classic reform could be utilizing any electricity that the pocket reform could provide to power the classic reform, correct?00:51
joschi'm sceptical bewause the batteries discharge suspiciously slowly...00:52
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)00:56
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.0.217)01:00
+ Ar|stote|is (~linx@149.210.0.217)01:00
- mjw (QUIT: Ping timeout: 250 seconds) (~mjw@gnu.wildebeest.org)01:03
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)01:10
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)01:12
- Gooberpatrol_66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66)01:13
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)01:14
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)01:45
minutejosch: you can see that by turning the classic off and looking at the A number in battery screen, is it negative?01:52
minutejosch: it's totally possible that the pocket provides 5V power to the classic01:53
+ paperManu_ (~paperManu@64.58.44.160)01:59
- n_to (QUIT: Quit: quitidiquit) (~n_to@2a03:4000:6:3662:24b1:57ff:fec6:76c1)02:00
+ n_to (~n_to@2a03:4000:6:3662:24b1:57ff:fec6:76c1)02:00
+ aelius (~aelius@user/aelius)02:48
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.0.217)03:01
- jn (QUIT: Ping timeout: 244 seconds) (~quassel@user/jn/x-3390946)03:05
+ jn (~quassel@2a0a-a54b-1889-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)03:05
- jn (QUIT: Changing host) (~quassel@2a0a-a54b-1889-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)03:05
+ jn (~quassel@user/jn/x-3390946)03:05
+ Ar|stote|is (~linx@149.210.0.217)03:06
- nsc (QUIT: Ping timeout: 264 seconds) (~nicolas@38-98-142-46.pool.kielnet.net)03:14
+ nsc (~nicolas@i5C74DC98.versanet.de)03:15
- paperManu_ (QUIT: Ping timeout: 256 seconds) (~paperManu@64.58.44.160)03:15
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)03:21
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)03:33
- wstlr (QUIT: Ping timeout: 244 seconds) (~wstlr@5.13.169.217.in-addr.arpa)03:44
- paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@64.58.44.160)03:48
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)04:02
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)04:08
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)04:19
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)04:24
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)04:35
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)04:40
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)04:51
- wstlr (QUIT: Ping timeout: 244 seconds) (~wstlr@5.13.169.217.in-addr.arpa)04:56
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)04:58
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)05:02
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)05:29
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)05:34
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)05:52
- wstlr (QUIT: Ping timeout: 256 seconds) (~wstlr@5.13.169.217.in-addr.arpa)05:57
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)06:16
josch-0.04 A... :(06:44
joschthis explains why my rk3588 classic reform just managed to survive 12 hours "on battery" XD06:45
joschon the one hand it's kinda cool that the classic is able to slurp just a bit of power that way (think of charging emergencies)06:45
joschon the other hand this totally destroys my logging experiment :(06:45
joschi'll use logging via ssh then instead of logging via serial06:46
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)06:56
- aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@90.166.99.102)07:07
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)07:08
joschminute: on the plus side, i verified that this method still works: https://mntre.com/reform-irc-logs/2025-07-12.log.html#t23:07:1207:20
joschyou recently noted that it's suboptimal that there is no automatic login over serial and that made me think that you missed my messages above07:21
- wstlr (QUIT: Ping timeout: 244 seconds) (~wstlr@5.13.169.217.in-addr.arpa)07:22
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)07:23
- wstlr (QUIT: Ping timeout: 265 seconds) (~wstlr@5.13.169.217.in-addr.arpa)07:32
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)07:33
- wstlr (QUIT: Ping timeout: 265 seconds) (~wstlr@5.13.169.217.in-addr.arpa)07:37
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)07:38
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)07:47
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)08:01
joschminute: i just discharged rk3588 classic reform with motherboard 3.0 down to zero and then plugged in AC adapter again. It only started charging (red led lighting up on the board) after i unplugged and then re-plugged one of the battery pack (maybe needed some sort of reset?)08:01
- wstlr (QUIT: Ping timeout: 245 seconds) (~wstlr@5.13.169.217.in-addr.arpa)08:14
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)08:26
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)08:34
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)08:48
joschminute: on a completely different topic, gnome-icon-theme was abandoned upstream and will be removed from Debian. You added it to the system image five years ago in the commit "WIP new userland build process and config files". I just wanted to check in with you whether you might recall a reason why having this package is important for the system image? Otherwise I'd just replace it with 09:15
joschadwaita-icon-theme, yes?09:15
joschwhile browsing the history i also saw that there is another version of the rainbow in /etc/motd with somehow more colors -- why was that one abandoned? I mean this one:09:20
joschcurl https://mister-muffin.de/p/GO2w.txt09:20
- buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org)09:53
+ buckket (~buckket@vps.buckket.org)09:54
- GNUmoon2 (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)09:55
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon)09:55
- wstlr (QUIT: Ping timeout: 256 seconds) (~wstlr@5.13.169.217.in-addr.arpa)09:57
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)10:00
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)10:05
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)10:12
- wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa)10:16
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)10:28
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)10:35
+ mjw (~mjw@gnu.wildebeest.org)10:37
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)11:01
- lanodan (QUIT: Ping timeout: 265 seconds) (~lanodan@2a01:e0a:d6:9930::35)11:04
- wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa)11:07
+ lanodan (~lanodan@2a01:e0a:d6:9930::35)11:20
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)11:24
- robin (QUIT: Ping timeout: 264 seconds) (~robin@user/terpri)11:39
+ robin (~robin@user/terpri)11:49
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)11:54
minutejosch: oh yeah, gnome-icon-theme can go12:02
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)12:02
minutejosch: one rainbow is for desktop, the other for console12:02
+ svp (~svp@2002:4f07:f0bd:0:69b1:b463:d245:e861)12:09
- mjw (QUIT: Ping timeout: 250 seconds) (~mjw@gnu.wildebeest.org)12:10
- wstlr (QUIT: Ping timeout: 244 seconds) (~wstlr@5.13.169.217.in-addr.arpa)12:11
joschminute: yes, but the rainbow is different now12:20
joschit has fewer colors in a different order12:20
joschcompare /etc/motd with the output of that curl command above12:20
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)12:21
* laumann -> Guest691312:25
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)12:26
+ laumann (31d44fbb95@user/laumann)12:29
+ paperManu (~paperManu@64.58.44.160)12:37
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)12:38
joschminute: here a direct comparison https://mister-muffin.de/p/OPU2.png12:43
- wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa)12:43
joschunless of course you have an ancient system image because /etc/motd does not get changed by package updates12:43
+ gustav2 (~gustav@c-78-82-53-184.bbcust.telenor.se)13:02
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)13:03
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)13:11
abortretryfailch: +1 to boot to FORTH13:15
* Guest4270 -> mjw13:17
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)13:32
+ RandyK_ (~RandyK@user/randyk)13:51
- RandyK (QUIT: Ping timeout: 272 seconds) (~RandyK@user/randyk)13:51
* RandyK_ -> RandyK13:52
- paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@64.58.44.160)14:13
+ aloo_shu (~aloo_shu@90.166.99.102)14:18
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)14:41
+ wielaard (~mjw@gnu.wildebeest.org)14:42
- paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)15:02
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)15:04
d_mACTION perks up at the mention of OpenFirmware15:10
- casparvitch (QUIT: Ping timeout: 264 seconds) (~casparvit@user/casparvitch)15:18
- wielaard (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)15:18
- elb` (QUIT: Ping timeout: 264 seconds) (~elb@68.133.31.194)15:18
+ elb` (~elb@68.133.31.194)15:18
- chorc (QUIT: Quit: ZNC 1.9.1 - https://znc.in) (~chorc@user/chorc)15:19
- dodo (QUIT: Quit: dodo) (~dodo@user/dodo)15:19
+ animone (~animone@107.191.119.239)15:19
- animone (QUIT: Changing host) (~animone@107.191.119.239)15:19
+ animone (~animone@user/animone)15:19
+ chorc (~chorc@user/chorc)15:19
+ dodo (~dodo@user/dodo)15:19
+ casparvitch (~casparvit@user/casparvitch)15:21
- animone_ (QUIT: Ping timeout: 264 seconds) (~animone@107.191.119.239)15:23
+ wakest_ (m-a7d6fe@45.77.48.108)15:28
- wakest (QUIT: Ping timeout: 264 seconds) (m-a7d6fe@45.77.48.108)15:29
* wakest_ -> wakest15:33
+ erle (~erle@user/erle)15:49
- wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa)15:51
+ jjbliss (~jjbliss@2601:404:c102:a720:4fb6:108a:f5a3:565a)15:54
abortretryfailI can barely make the changes I want to MFORTH on an old 8-bit Tandy. Porting something like OpenFirmware to a modern ARM SoC is probably way outside my capabilities. :(15:58
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)16:02
+ chomwitt (~chomwitt@2a02:85f:9aa4:5100:1ac0:4dff:fedb:a3f1)16:03
- wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa)16:09
minutejosch: the fewer colors are because i wanted it to work OK on the very limited linux console, and someone told me back then that the colors are the wrong order for a rainbow so i changed it, but i guess i didn't change the high color res one in that way. afaik the high res one was included in reform-desktop-help.16:16
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)16:38
- wstlr (QUIT: Ping timeout: 248 seconds) (~wstlr@5.13.169.217.in-addr.arpa)16:42
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)17:05
- wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa)17:16
joschminute: thank you, you are right. Trying to render the version with the many colors on the framebuffer still looks super ugly for some reason :(17:26
+ ericsfraga (~user@2a00:23cc:b475:7c01:2109:5b9a:c01e:659c)17:35
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)17:42
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)17:46
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)18:06
- wstlr (QUIT: Ping timeout: 265 seconds) (~wstlr@5.13.169.217.in-addr.arpa)18:12
+ timide (~timide@user/timide)18:29
- timide (QUIT: Client Quit) (~timide@user/timide)18:29
- ericsfraga (QUIT: Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50)) (~user@2a00:23cc:b475:7c01:2109:5b9a:c01e:659c)18:34
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)18:43
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)18:47
+ LainIwakura (~LainIwaku@user/LainIwakura)18:58
+ LainIwakura38 (~LainIwaku@user/LainIwakura)19:01
- LainIwakura (QUIT: Ping timeout: 250 seconds) (~LainIwaku@user/LainIwakura)19:04
- LainIwakura38 (QUIT: Ping timeout: 250 seconds) (~LainIwaku@user/LainIwakura)19:06
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)19:07
+ wielaard (~mjw@gnu.wildebeest.org)19:09
* mjw -> Guest425019:10
- Guest4250 (QUIT: Killed (uranium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)19:10
* wielaard -> mjw19:10
+ Guest4250 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)19:11
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)19:11
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)19:42
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)19:46
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)19:56
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)20:01
- schalken (QUIT: Read error: Connection reset by peer) (~schalken@117-118-178-69.gci.net)20:07
+ schalken (~schalken@117-118-178-69.gci.net)20:11
- schalken (QUIT: Quit: Leaving) (~schalken@117-118-178-69.gci.net)20:20
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)20:25
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)20:30
+ schalken (~schalken@117-118-178-69.gci.net)20:40
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)20:44
joschminute: i just had a hang of the keyboard (this never happened to me before) and it was on the latest firmware20:47
erlejosch apropos keyboard firmware, did you get around to test my proposed neo2 bugfix patch? if so, i'll make an MR and assign you as a reviewer20:50
joschsorry, the timing was unlucky, that was the day where we had a load of other issues so it fell through the cracks20:51
joschanother lpc bug: when the capacity in /sys for the battery reaches zero, it wraps around and starts again at 1820300020:51
joschwhich is also funny because charge_full is 1800000020:52
erleunderflow battery charge exploit, just drain them to top them up20:57
erlein any computer game where the map is the territory it would get exploited fast20:57
- chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:85f:9aa4:5100:1ac0:4dff:fedb:a3f1)21:41
gordon1minute: so i have this usb-c charger that has an adverse semi-failure mode if you connect stuff to charge in wrong order, in this case it just keeps cycling my classic reform between 5V and 20V every second or so and looks like laptop can even draw some current on 20V before charger gives up for another cycle, i also poked oscilloscope at the power rail on the connector side and it seems there21:44
gordon1is no spikes or ringing going on, just voltage sagging from 20V to ~15V or so, my question is: i would really like to keep this charger and i usually remember to connect it in the right order, but in case i would forget and leave my reform for long period of time in that state, your gut feeling, will it be okay?21:44
gordon1sorry, that is an incredibly difficult question to answer, so just you best guess?21:45
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)21:46
+ LainIwakura (~LainIwaku@user/LainIwakura)21:56
joschi just had 11.9475 hours of battery runtime with rk3588 classic reform *if* everything is off and no processes are running21:58
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)21:59
- BoostisBetter (QUIT: Ping timeout: 252 seconds) (4a410829d7@irc.cheogram.com)22:02
- SavagePeanut (QUIT: Ping timeout: 252 seconds) (59eaa45ac7@irc.cheogram.com)22:02
gordon1josch: did you do something specific to achieve that or just power off all the backlight and pcie devices?22:03
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)22:03
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)22:05
- LainIwakura (QUIT: Quit: Client closed) (~LainIwaku@user/LainIwakura)22:11
- gustav2 (QUIT: Quit: Quit) (~gustav@c-78-82-53-184.bbcust.telenor.se)22:15
- wstlr (QUIT: Ping timeout: 250 seconds) (~wstlr@5.13.169.217.in-addr.arpa)22:33
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)22:37
- wstlr (QUIT: Ping timeout: 252 seconds) (~wstlr@5.13.169.217.in-addr.arpa)22:41
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)22:55
- paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)22:57
- wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa)23:07
joschgordon1: no backlight, no pcie devices -- otherwise just the normal system image. No twiddling with any settings.23:12
gordon1cool23:13
gordon1josch: did you try powertop --auto-tune ?23:13
gordon1(it will render your trackball unusable tho, you have to turn off autosuspend for it after that)23:14
+ paperManu (~paperManu@64.58.44.160)23:18
joschgordon1: no. my goal is not to squeeze as much runtime as possible out23:18
joschi just want a reproducible and comparible setup with the least amount of random influences23:18
gordon1right23:19
gordon1i see23:20
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)23:37
- wstlr (QUIT: Ping timeout: 252 seconds) (~wstlr@5.13.169.217.in-addr.arpa)23:43
+ SavagePeanut (59eaa45ac7@irc.cheogram.com)23:46
dormitoanyone know if the crowdsupply "reform pocket" come with cpu module, or is it just the chassis and other boards (I don't see any clear indicators on the crowd supply page either way)23:51
+ wstlr (~wstlr@5.13.169.217.in-addr.arpa)23:57

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