| + paperManu (~paperManu@142.169.16.42) | 00:05 | |
| - Guest86 (QUIT: Quit: Client closed) (~Guest86@104.228.148.232) | 00:28 | |
| + Guest29 (~Guest29@104.228.148.232) | 00:29 | |
| ch | ohi | 00:40 |
|---|---|---|
| - paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@142.169.16.42) | 00:50 | |
| ch | josch: do you also have the 'not working' usb-c thingie with you? | 00:56 |
| + paperManu (~paperManu@107.159.15.124) | 01:17 | |
| - Guest29 (QUIT: Quit: Client closed) (~Guest29@104.228.148.232) | 01:23 | |
| + paperManu_ (~paperManu@107.159.15.124) | 01:33 | |
| - paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@107.159.15.124) | 01:43 | |
| - paperManu_ (QUIT: Ping timeout: 240 seconds) (~paperManu@107.159.15.124) | 02:47 | |
| - xktr (QUIT: Ping timeout: 250 seconds) (~xktr@user/xktr) | 04:03 | |
| + xktr (~xktr@user/xktr) | 04:04 | |
| + elb (~elb@2600:4041:6682:ea00:c6a7:e77f:1e0b:37ab) | 04:06 | |
| erle | > having the keys light up when you press them and trail your keypresses slightly is lovely | 05:00 |
| erle | password input just got a lot funnier :3 | 05:00 |
| - erle (QUIT: Quit: K-lined) (~erle@user/erle) | 05:01 | |
| jfred | yeah that's why I don't use keyboard lighting features like that haha | 05:01 |
| jfred | I do sometimes like some of the more flashy ones like ripples from each keypress. You could work it out if you look closely enough, but if someone's watching me type my password that closely I likely have problems anyway | 05:03 |
| - lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah) | 06:13 | |
| + lidstah (~lidstah@gateway/tor-sasl/lidstah) | 06:16 | |
| - timide (QUIT: K-Lined) (~timide@user/timide) | 06:24 | |
| josch | ch: what do you think? ;) | 07:10 |
| josch | (i'll have it in my backpack but as you say it only "not working") | 07:16 |
| josch | wait, it actually really works -- even after first attaching the hub and only then the cable to the AC | 07:50 |
| josch | it just takes over a minute for the power status to change to "charging" after pluggin AC into the hub... | 07:50 |
| josch | okay, this behaviour has nothing to do with the pocket -- same thing with the classic reform with ubb-pd to dc adapter in the middle | 07:57 |
| josch | good i checked :D | 07:57 |
| - _justin_kelly71 (QUIT: Quit: The Lounge - https://thelounge.chat) (~justinkel@user/justin-kelly/x-6011154) | 10:39 | |
| + _justin_kelly71 (~justinkel@user/justin-kelly/x-6011154) | 10:42 | |
| - _justin_kelly71 (QUIT: Client Quit) (~justinkel@user/justin-kelly/x-6011154) | 10:45 | |
| + _justin_kelly71 (~justinkel@user/justin-kelly/x-6011154) | 10:47 | |
| grimmware | minute: thinking about this rtos-for-sysctl thing, do you have any opinions on what you would *like* to use were it supported on the new sysctl? Reason I ask is because obviously it would be preferable that we don't further fragment the software stack, and it would be great to be able to get on and experiment with the target platform on the rp2040 if it's actually available | 10:55 |
| grimmware | if rtos is potentially the way to go for the low power states, on the pocket we're essentially going to be blocked by making this decision for the next which kinda sucks because the sysctl power draw is likely to become the biggest power issue given it will limit how useful suspend/hibernate are | 10:56 |
| grimmware | the runtime of this thing with bigger batteries is pretty incredible, I'd be thrilled if it didn't drain so much whilst turned off | 10:57 |
| josch | true but then my | 11:22 |
| josch | but then my thinkpay from work also does not surive two days in suspend so is proprietary hardware really that much better? | 11:23 |
| - rodion_goritskov (QUIT: Ping timeout: 246 seconds) (~rodion_go@mail.goritskov.com) | 11:25 | |
| + rodion_goritskov (~rodion_go@mail.goritskov.com) | 11:28 | |
| grimmware | My GPD P2 max lasts FOREVER | 11:31 |
| + gidzit (~gidzit@gidzit.org) | 11:37 | |
| Zaba | if your thinkpad doesn’t survive for two days then it’s probably not suspending fully correctly | 11:38 |
| - _justin_kelly71 (QUIT: Quit: The Lounge - https://thelounge.chat) (~justinkel@user/justin-kelly/x-6011154) | 11:51 | |
| amospalla | ch: how can I retrieve sysctl logs from my pocket? | 12:19 |
| ch | amospalla: see the command in here: https://community.mnt.re/t/battery-meter-only-goes-to-about-40/3937/6 | 12:20 |
| amospalla | I just powered it on, put it to charge (sysctl shows aggretated Voltage and negative current), a few minutes later I disconnected the charger, and sysctl shows 0.000A and 0.00V. | 12:20 |
| grimmware | minute: did you do much profiling for other gpu frequencies with the power saving stuff? | 12:25 |
| amospalla | ch: https://file.amospalla.es/misc/pocket_reform_sysctl_battery.txt, showing zero values, then attached the charger and showed real values, then disconnected the charger and went back to zero values. | 12:27 |
| + paperManu (~paperManu@107.159.15.124) | 12:28 | |
| ch | ok, thats a real proble | 12:28 |
| ch | m | 12:28 |
| amospalla | Just being curious, what does it mean? | 12:28 |
| ch | hmm | 12:28 |
| amospalla | Well, don't want to take you time, please ask if I can do anything else. | 12:31 |
| ch | i'll have to read the mp2650 datasheet how this can happen | 12:34 |
| ch | what the messages mean is that, on battery, the mp2650 doesn't report any data | 12:34 |
| ch | but clearly some communication with it works, otherwise charging wouldnt work | 12:34 |
| ch | amospalla: can you plug in a dumb power source that supplies 5V and no usb-pd? like an old usb "battery bank"? | 12:35 |
| ch | and see what the logs say then | 12:35 |
| amospalla | I should be able to, let me find the cables. | 12:35 |
| grimmware | are there any convenience ways of monitoring the gpu usage (preferably like top/htop/btop) | 12:36 |
| amospalla | ch: dumb power 1A 5V source: https://file.amospalla.es/misc/pocket_reform_sysctl_battery2.txt | 12:45 |
| ch | so weird. i'm missing the 'CHG' flag in the log (= chg_en=1), yet the mp2650 reports chg_stat=2 | 12:50 |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@107.159.15.124) | 12:52 | |
| ch | can you reset the sysctl? | 12:53 |
| amospalla | ch: mechanically right? | 12:55 |
| ch | either that or with reform-mcu-tool | 12:55 |
| amospalla | ch: done | 12:56 |
| ch | anything different? | 12:56 |
| amospalla | I'll repeat everything I did before, let me check. | 12:57 |
| amospalla | ch: it is behaving correctly now. | 13:01 |
| ch | ok. i guess there's a need to write the mp2650 config regularly or something | 13:02 |
| + gustav25 (~gustav@c-78-82-53-204.bbcust.telenor.se) | 13:02 | |
| amospalla | thank you for checking :). Ask if need anything. | 13:03 |
| minute | grimmware: RTOS does _not_ make PM easier. | 13:25 |
| minute | grimmware: if anything, RTOS will make things harder as there are more abstractions to deal with. it _could_ make things more stable and extensible, esp. if more features are added. | 13:26 |
| minute | grimmware: zephyr doesn't have any support for PM functions on rp2350 implemented yet, but one of their devs was immediately interested in implementing it when i told my usecase | 13:27 |
| minute | i experimented more with deep sleep functions yesterday and it was still crashing but i think i just need to vendor the pico-extras/sleep code and remove things like stdio_flush in there | 13:28 |
| minute | good that we already vendored usb stdio | 13:28 |
| minute | the tricky thing is to disable all background tasks that are implemented with timer IRQs, for example tinyusb doesn't have an API for _stopping_ it | 13:29 |
| minute | so we might need to implement that | 13:29 |
| minute | anyway, hope that today i'll be able to get to rp2350 deep sleep + reboot on wake (this should also mostly work on rp2040) | 13:30 |
| minute | grimmware: perfetto afaik @ gpu, or gallium hud | 13:34 |
| grimmware | ah fair | 13:48 |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 14:01 | |
| * Guest8453 -> mjw | 14:13 | |
| grimmware | Hmm, it appears that other people on the internet have been using /sys/class/devfreq/fb000000.gpu/load to monitor gpu load but it does not appear to be in the reform kernel | 14:28 |
| + paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 14:43 | |
| + behinus (~behinus@2a02:3030:665:5160:f905:d96d:e9d8:cdb7) | 14:58 | |
| - behinus (PART: !!unknown attribute: msg!!) (~behinus@2a02:3030:665:5160:f905:d96d:e9d8:cdb7) | 14:58 | |
| + jordi__ (~jordi@79.117.156.55) | 15:05 | |
| - pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0) | 15:06 | |
| grimmware | I really don't know enough to say for sure but the stuff around devfreq in this patch stack looks kind of promising despite being for an unrelated SoC | 15:07 |
| grimmware | https://lkml.org/lkml/2025/9/5/768 | 15:07 |
| - kxtells (QUIT: Ping timeout: 246 seconds) (~jordi@user/kxtells) | 15:07 | |
| - swivel (QUIT: Ping timeout: 260 seconds) (~swivel@shells.gnugeneration.com) | 15:48 | |
| + swivel (~swivel@shells.gnugeneration.com) | 15:49 | |
| + pomel0 (~pomel0@user/pomel0) | 16:29 | |
| + wielaard (~mjw@gnu.wildebeest.org) | 16:55 | |
| + FirefoxDeHuk (~FirefoxDe@user/FirefoxDeHuk) | 17:04 | |
| grimmware | ugh, I'm still getting the problem that one of my cells is higher voltage than the other so I can't charge beyond a certain % (12 in this case) because it causes the charger to drop to just supply the current draw and not charge the batteries | 17:04 |
| grimmware | I don't have the stuff with me to balance the cells :( | 17:04 |
| grimmware | mind you I haven't done a firmware update in a while | 17:13 |
| grimmware | I should do that thing | 17:13 |
| - f_ (QUIT: K-Lined) (16abab341f@postmarketOS/funderscore) | 17:14 | |
| + f_ (16abab341f@postmarketOS/funderscore) | 17:14 | |
| - FirefoxDeHuk (QUIT: Quit: Client closed) (~FirefoxDe@user/FirefoxDeHuk) | 17:15 | |
| minute | pocket keyboard standalone usb-c adapter is here https://mastodon.social/@mntmn/115628220278743490 | 17:22 |
| grimmware | that's very cute :) | 17:24 |
| grimmware | yeah firmware update hasn't changed anything. | 17:25 |
| josch | what could i try on pocket reform to get the speaker working with kernel 6.15 (trixie). i have run reform-hw-setup from reform-tools git and pavucontrol shows that output devices is set to speakers and the volume bar is moving, indicating that something should be played | 17:28 |
| grimmware | josch: alsamixer will likely expose some mute control that's hidden in pavucontrol | 17:32 |
| josch | but alsamixer should be set up fine by reform-hw-setup | 17:32 |
| grimmware | check it! | 17:32 |
| grimmware | cos there's a whole bunch of shit under the other sound cards that pavucontrol doesn't even touch | 17:33 |
| josch | nothing is muted (nothing is set to MM) | 17:34 |
| josch | yes but those controls are initialized (or at least should be) by reform-hw-setup. anyways, nothing is muted | 17:35 |
| minute | grimmware: this is with charger board v2 right? | 17:46 |
| grimmware | minute: yeah | 17:47 |
| grimmware | I had no problem charging it up to full overnight | 17:48 |
| grimmware | they are new batteries which I didn't check the voltage on beforehand but they've already been for a very long full discharge about twice | 17:48 |
| grimmware | well, not totally full but down to like 3% | 17:49 |
| + jogu (~jogu@user/jogu) | 17:53 | |
| + FirefoxDeHuk (~FirefoxDe@user/FirefoxDeHuk) | 18:05 | |
| - gidzit (QUIT: Ping timeout: 246 seconds) (~gidzit@gidzit.org) | 18:11 | |
| - FirefoxDeHuk (QUIT: Quit: Client closed) (~FirefoxDe@user/FirefoxDeHuk) | 18:12 | |
| - mjw (QUIT: Killed (copper.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 18:35 | |
| * wielaard -> mjw | 18:35 | |
| + Guest420 (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d) | 18:35 | |
| - buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org) | 19:03 | |
| + buckket (~buckket@vps.buckket.org) | 19:04 | |
| - jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu) | 20:38 | |
| + jogu (~jogu@user/jogu) | 20:39 | |
| + synnfynn (~synnfynn@user/synnfynn) | 20:52 | |
| jogu | Still been poking away at trying to pin down the USB instability on my V4 keyboard. Does anybody know how the crystal used in the RP2040 based schematics was chosen? Curious if that could be a contributing factor since it deviates from the reference design | 21:02 |
| jogu | I've been reading through a GitHub issue thread for another keyboard that sounds like a very similar issue: https://github.com/foostan/crkbd/issues/265#issuecomment-2474072286 | 21:06 |
| - sterni (QUIT: ) (~quassel@user/sterni) | 21:10 | |
| + sterni (~quassel@user/sterni) | 21:10 | |
| jogu | I'm testing out shielding with copper tape around the MCU, crystal, and USB traces near the top of the PCB to see if that helps as well | 21:11 |
| jogu | My initial impression is that the shielding is helping, but it's so sporadic it's hard to be certain | 21:12 |
| jogu | And even with it, I'm still seeing CRC errors/bus resets in the logs | 21:13 |
| jogu | Over on the rpi forums I see an engineer from there mentioned that the ESR max of 50R as being important https://forums.raspberrypi.com/viewtopic.php?t=314935 | 21:18 |
| jogu | Current crystal on the reform keyboard is 100R, not sure how much that matters | 21:20 |
| minute | have next motherboard current draw (from 1 of 2 bat packs) down to 2mA in rp2350 sleep mode now | 21:28 |
| minute | jogu: yes, the crystal is not ideal, do you want to try to replace it with the recommended one? | 21:29 |
| jogu | minute: yeah, I was thinking of trying the reference crystal + capacitors to see if there's any difference but I'm not able to do that kind of soldering haha | 21:39 |
| minute | jogu: ah ok. we recently did such experiments here on some pocket keyboards where the oscillator wouldn't start. it's quite rare though. most of the time the rp2040 has issues. but it's not known that this happens on the "big" keyboard | 21:40 |
| jogu | minute: Interesting, I did see that discussion on usb instability on the pocket reform keyboard disconnecting and it sounds identical to what I'm seeing | 21:50 |
| jogu | In the past, it used to be more of a "hard" disconnect that required I reset the MCU / re-plug the keyboard but lately it's manifesting as the last key repeating but it recovers without reseting | 21:51 |
| minute | jogu: do you have rk3588, and since when, and do you have up to date uboot? | 22:14 |
| - gustav25 (QUIT: Quit: Quit) (~gustav@c-78-82-53-204.bbcust.telenor.se) | 22:15 | |
| + leony (~leony@2a02:8109:f083:bb00::5ef2) | 22:34 | |
| - paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca) | 22:44 | |
| - pomel0 (QUIT: Ping timeout: 244 seconds) (~pomel0@user/pomel0) | 22:58 | |
| + pomel0 (~pomel0@user/pomel0) | 22:58 | |
| - pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0) | 23:05 | |
| + pomel0 (~pomel0@user/pomel0) | 23:06 | |
| - pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0) | 23:10 | |
| + pomel0 (~pomel0@user/pomel0) | 23:10 | |
| + paperManu (~paperManu@107.159.15.124) | 23:24 | |
| + paperManu_ (~paperManu@107.159.15.124) | 23:24 | |
| - pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0) | 23:45 | |
| + pomel0 (~pomel0@user/pomel0) | 23:50 | |
| - pomel0 (QUIT: Ping timeout: 256 seconds) (~pomel0@user/pomel0) | 23:54 | |
| - paperManu (QUIT: Quit: WeeChat 4.7.0) (~paperManu@107.159.15.124) | 23:57 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!