2025-01-01.log

joschHappy 2025 everybody :)00:04
minutehappy 2025!00:05
BoostisBetterindeed! Let's go 2025!00:09
BoostisBetterin other news, the rolled back downgraded Sysctrl firmware, doesn't seem to have had a positive effect. I think this is a psuspend thing it would seem. 00:20
- mtm (QUIT: Ping timeout: 244 seconds) (~textual@47.202.75.129)01:03
+ mtm (~textual@47.202.75.129)01:04
mhoyeNo spoilers, europeans!02:13
- yankcrime (QUIT: Ping timeout: 248 seconds) (~nick@gw.tetromino.io)04:21
- mjw (QUIT: Ping timeout: 248 seconds) (~mjw@gnu.wildebeest.org)04:28
- paperManu (QUIT: Ping timeout: 265 seconds) (~paperManu@107.159.243.8)04:31
- jn (QUIT: Ping timeout: 252 seconds) (~quassel@user/jn/x-3390946)05:21
+ jn_ (~quassel@2001-4dd4-9638-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)05:21
- jn_ (QUIT: Changing host) (~quassel@2001-4dd4-9638-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)05:21
+ jn_ (~quassel@user/jn/x-3390946)05:21
murphnjHappy new years! (a litle early)05:36
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)05:41
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)06:53
- jacobk (QUIT: Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)07:40
+ ajr (uid609314@user/ajr)08:59
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.99.95)09:18
+ aloo_shu (~aloo_shu@90.166.193.242)09:21
- Gooberpatrol66 (QUIT: Read error: Connection reset by peer) (~Gooberpat@user/gooberpatrol66)10:03
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)10:03
- amospalla (QUIT: Ping timeout: 248 seconds) (~jordi@user/amospalla)10:47
+ amospalla (~jordi@user/amospalla)10:47
+ frickler (~jens@user/frickler)11:07
- staticbunny (QUIT: Ping timeout: 248 seconds) (~static@76-223-253-78.lightspeed.frokca.sbcglobal.net)12:51
+ static (~static@76-223-253-78.lightspeed.frokca.sbcglobal.net)12:52
- mtm (QUIT: Ping timeout: 265 seconds) (~textual@47.202.75.129)13:02
+ gustav28 (~gustav@c-78-82-52-90.bbcust.telenor.se)13:02
+ mtm (~textual@47.202.75.129)13:06
- ajr (QUIT: Quit: Connection closed for inactivity) (uid609314@user/ajr)13:08
ryukazouHappy new year13:17
- cobra (QUIT: Ping timeout: 245 seconds) (~cobra@user/Cobra)13:31
+ glu_ (~glu@user/glu)13:45
+ mjw (~mjw@gnu.wildebeest.org)13:46
- glu__ (QUIT: Ping timeout: 244 seconds) (~glu@user/glu)13:46
+ bkeys (~Thunderbi@173.16.175.75)13:56
- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@173.16.175.75)14:04
- yqshao (QUIT: Remote host closed the connection) (~yqshao@user/yqshao)14:06
+ yqshao (~yqshao@user/yqshao)14:09
+ paperManu (~paperManu@107.159.243.8)14:19
+ cobra (~cobra@user/Cobra)15:37
+ ZylonMaster (~hjcs@ool-ad02e01f.dyn.optonline.net)17:04
+ freepalestine (~freepales@82-132-217-251.dab.02.net)17:12
minuteany steam on reform experts here? :D https://mastodon.social/@mntmn/11375398170169879017:14
BoostisBettersorry not me, but hope someone pipes up!17:15
chugh :/17:16
freepalestinehello, is anyone attending https://2025.oshwa.org/ in Edinburgh?17:18
minutefreepalestine: some people from MNT might go17:19
- freepalestine (QUIT: Quit: Client closed) (~freepales@82-132-217-251.dab.02.net)17:24
+ freepalestine (~freepales@82-132-217-251.dab.02.net)17:26
- freepalestine (QUIT: Client Quit) (~freepales@82-132-217-251.dab.02.net)17:29
- paperManu (QUIT: Quit: WeeChat 4.1.1) (~paperManu@107.159.243.8)17:33
- ZylonMaster (QUIT: Quit: Leaving) (~hjcs@ool-ad02e01f.dyn.optonline.net)17:36
joschgrimmware: nice forum post on the daily driver thread! I agree that it's probably mostly about expectations. I come from the corner of mobile linux arm devices with *much* *much* *much* less working and much less support than the Reform offers which makes me excited for the Reform and ignore its quirks (or put the time in to fix them).17:48
joschgrimmware: you say that Debian unstable is one of your major gripes -- others are running Debian stable with backports kernel successfully on their rk3588 Pocket Reform -- want to give it a try and report bugs you find to me? :)17:48
minutenice, i can run wasteland 2 directly from the shell (after it was downloaded by steam)17:49
josch(for example, we already figured out that for rk3588 panthor needs mesa from backports)17:50
joschminute: your steam is not stuck anymore?17:50
+ paperManu (~paperManu@107.159.243.8)17:52
- aloo_shu (QUIT: Remote host closed the connection) (~aloo_shu@90.166.193.242)18:04
+ aloo_shu (~aloo_shu@90.166.193.242)18:05
+ ajr (uid609314@user/ajr)18:15
minutejosch: it is, but on the first launch i was able to download the game last night18:18
minutejosch: and now i am just running the game without steam18:18
joschah okay :)18:18
chthanks to minute i bought return to monkey island today18:19
chproductivity will tank ;)18:19
- sterni (QUIT: ) (~quassel@user/sterni)19:32
+ sterni (~quassel@user/sterni)19:32
BoostisBetterso the keyboard keeps disconnecting on my pocket. Sometimes I am able to reset it via the LPC, but sometimes I am able to do nothing. Only a power cycle works. 20:05
BoostisBetterWhat can I do about this, and is anyone else noticing the keyboard becoming disconnected?20:05
BoostisBetterdoes anything report why the LPC keeps showing me a T in the upper left corner of the display? 20:17
BoostisBetterI know that this means that it missed something from the syscrtrl20:17
BoostisBetterbut since I keep having keyboard disconnects, I'm wondering if the UART connection between the two could be to blame? 20:17
chT means timeout between keyboard and sysctl20:18
BoostisBetteryeah, this keeps happening20:18
BoostisBetterand since the keyboard is then being disconnected from the Debian kernel20:18
BoostisBetternot necessarily right when the T shows, but it seems that when the T starts showing then the keyboard disconnect will happen. 20:19
BoostisBetterI find that reseting the LPC helps20:19
BoostisBetterbut there is a serious stability issue here. 20:19
- aloo_shu (QUIT: Remote host closed the connection) (~aloo_shu@90.166.193.242)20:31
chmaybe the problems you have are actually on the keyboard side20:32
+ aloo_shu (~aloo_shu@90.166.193.242)20:33
- aloo_shu (QUIT: Remote host closed the connection) (~aloo_shu@90.166.193.242)20:58
+ aloo_shu (~aloo_shu@90.166.193.242)21:01
BoostisBetterI think so as well21:21
BoostisBetterI am not sure how to update the keyboard firmware21:21
BoostisBetterbut I know that on older sysctrl firmware I don21:21
BoostisBetter't seem to have the issue nearly as much21:22
BoostisBetterIf I could remember what firmware my pocket came with, that would be good. Because it was absolutely the most stable so far. 21:22
BoostisBetterbut I do appreciate all of the charging improvements and lower idle power21:22
+ wielaard (~mjw@gnu.wildebeest.org)21:32
minutehmmm, my pocket input stopped responding a while ago (no trackball or keyboard input). but! the backlight still times out and wakes up when pressing a key21:34
minuteso the main loop is still running21:34
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)21:34
minuteBoostisBetter: maybe we have a similar issue21:35
minutealso, Bus 008 Device 004: ID cafe:4004 MNT Pocket Reform Input is still there21:35
minutehidraw0 is gone though21:43
minutei guess something tinyusb related crashes21:43
- yqshao (QUIT: Remote host closed the connection) (~yqshao@user/yqshao)21:50
+ yqshao (~yqshao@user/yqshao)21:50
BoostisBetterminute: good find. So this would mean firmware related? As a dif this didn't use to happen. 22:13
minuteBoostisBetter: it is possible yeah22:14
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-90.bbcust.telenor.se)22:15
BoostisBetterminute: Awesome. I am real happy that we have found something, as it means we have a direction to go. 22:16
minuteah, i'm silly, the oled menu also still works. does that still work for you in this state BoostisBetter ?22:18
BoostisBetterminute: occasionaly, the keyboard will disconnect22:19
BoostisBetterand the oled screen will still work. Here I reset the keyboard, and things work, but can also get a little funky. Like the keyboard entering multiple hits, and delayed input22:20
BoostisBetterHowever, other times, the keyboard disconnects, and the LPC is functional. I can't even access it. 22:20
BoostisBetterThe only thing i can do is power cycle the whole pocket. 22:20
BoostisBetterThis seems to be exacerbated by using psuspend. 22:20
BoostisBetterminute: oh right now, that has happened in fact. 22:21
BoostisBetterthe keyboard is not responsive. No Oled22:23
BoostisBetterHave to power cycle to get it back up. 22:23
minuteBoostisBetter: ah, i can explain why the keyboard will get funky22:24
minuteBoostisBetter: because it thinks the system is off after reset. you can get it un-funked if you "power on" again via oled22:24
BoostisBetterminute: that wont power cycle the CPU though? 22:24
minuteBoostisBetter: it won't.22:24
BoostisBetterminute: then this might be why it is disconnecting. 22:24
BoostisBetterBecause I am never getting it out of this funky state22:25
BoostisBetterminute: I suspect there is something else though. Perhaps it is the idle power modification to the system controller. 22:25
minuteBoostisBetter: try power on in the oled menu after reset22:25
minute(this is only a workaround of course, we need to fix that bug as well)22:25
minuteBoostisBetter: after keyboard reset i mean22:25
BoostisBetterI will, hopefully this will lessen or stop the full on, no oled disconnect. 22:26
BoostisBetterminute: I saw what I am saying about the sysctrl, because ALWAYS before the keyboard disconnects it precluded with the OLED showing the T in the upper left corner. 22:28
BoostisBetterminute: I say what I am saying about the sysctrl, because ALWAYS before the keyboard disconnects it precluded with the OLED showing the T in the upper left corner. 22:29
- yqshao (QUIT: Remote host closed the connection) (~yqshao@user/yqshao)22:33
+ yqshao (~yqshao@user/yqshao)22:33
minuteBoostisBetter: interesting22:38
- yqshao (QUIT: Remote host closed the connection) (~yqshao@user/yqshao)22:39
minutei've found an easy way to disconnect+reconnect usb from inside the keyboard firmware on demand. now we just need to detect that the usb is not working anymore22:40
BoostisBetterminute: this is awesome news! I knew there would be a solution! 22:40
+ yqshao (~yqshao@user/yqshao)22:41
BoostisBetterminute: the oled is one of the coolest features of the MNT line22:42
minuteinteresting, i managed to crash the keyboard22:51
minutei think the main issue is that the hid_task is running cooperatively with the oled and uart stuff, and if something takes too long, it can disrupt usb22:53
minuteideally the usb should preempt the other stuff22:53
BoostisBetterRight, or at least fix itself when a problem is noticed22:54
BoostisBetterI do wonder why the desyncs are so much more popular now. I had none of these issues before upgrading the sysctrl firmware. 22:54
minuteBoostisBetter: did you also upgrade the keyboard firmware or is it an older version?22:57
BoostisBetterkeyboard is an older version. Not sure how to update the keyboard. 22:58
minuteok22:59
minuteredrawing (flushing) of the oled screen causes a short fill up of the usb pipeline23:03
minutei have a WIP firmware running here now that decouples USB reporting from the rest of the code with a timer interrupt23:34
BoostisBetterminute: you are awesome! 23:49

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