| minute | wofi (launcher) is a bit strange noawadays, sometimes it opens off-center | 00:20 |
|---|---|---|
| minute | seems random | 00:20 |
| minute | https://www.ti.com/lit/wp/scaa124/scaa124.pdf | 00:23 |
| - ajr (QUIT: Ping timeout: 252 seconds) (~ajr@user/ajr) | 00:31 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.25.113) | 01:00 | |
| + Ar|stote|is (~linx@149.210.25.113) | 01:00 | |
| - mtm (QUIT: Ping timeout: 244 seconds) (~textual@47.202.75.129) | 01:04 | |
| + mtm (~textual@47.202.75.129) | 01:05 | |
| + ajr (~ajr@user/ajr) | 01:34 | |
| + jacobk (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 01:51 | |
| - ajr (QUIT: Ping timeout: 264 seconds) (~ajr@user/ajr) | 02:05 | |
| - Ar|stote|is (QUIT: Ping timeout: 265 seconds) (~linx@149.210.25.113) | 02:45 | |
| + Ar|stote|is (~linx@149.210.24.146) | 02:49 | |
| - kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:02 | |
| + kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:03 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 03:03 | |
| - kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:03 | |
| + kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:04 | |
| - nsc (QUIT: Ping timeout: 265 seconds) (~nicolas@160-97-142-46.pool.kielnet.net) | 03:09 | |
| + nsc (~nicolas@203-98-142-46.pool.kielnet.net) | 03:11 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 03:25 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 03:29 | |
| - simba (QUIT: Ping timeout: 252 seconds) (~simba@ppp-185-38-53-136.pool5.filstalnetz.de) | 03:29 | |
| + ajr (~ajr@user/ajr) | 03:45 | |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 03:48 | |
| + jacobk_ (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 03:48 | |
| + ajr_ (sid609314@user/ajr) | 04:06 | |
| - ajr (QUIT: Quit: ZNC 1.9.1 - https://znc.in) (~ajr@user/ajr) | 04:07 | |
| * ajr_ -> ajr | 04:07 | |
| - jacobk_ (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 04:10 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 04:36 | |
| - cobra (QUIT: Ping timeout: 265 seconds) (~cobra@user/Cobra) | 06:46 | |
| noam | minute: I don't know, I wasn't in the room. Here's everything I do know: it was plugged into a power supply that sometimes fails to supply the correct voltage and kicks itself in a cycle, which - when I'm present - isn't a big deal, because I can unplug it, give it a few seconds, plug it in, and it's fine | 06:50 |
| noam | I wasn't watching, but I do know there were probably well over a dozen brownouts yesterday due to a storm | 06:50 |
| noam | I walked back, the screen was off while it was plugged in, so I figured it might have died because the power supply failed | 06:51 |
| noam | The sysctl oled was on at the time - I unplugged it, the OLED shut off, and I've been unable to get it back on since | 06:51 |
| noam | If I plug in a power supply, I get the red light for a connection | 06:51 |
| noam | neither the power supply fuse nor the LiFePO fuse is blown | 06:51 |
| noam | Something smelled burnt. | 06:51 |
| noam | The cells are all fine, but were _horrendously_ imbalanced | 06:52 |
| noam | One of them was ~2V, the others were all over 3V | 06:52 |
| noam | I've been able to charge them all using an external circuit without issues | 06:52 |
| noam | Plugging into DC power supply, while turning on the red light, fails to power the system controller, I think - the OLED does not turn on | 06:53 |
| noam | jfred: I'll check it out | 06:53 |
| noam | It was plugged in, yes | 06:53 |
| noam | My suspicion is that the power supply handled the brownouts really, really, really badly. | 06:53 |
| noam | Potentially was wavering between undervolting and overvolting for a few seconds, I'm unsure | 06:54 |
| noam | jfred: ooh, interesting, I was also using a USB-C to barrel jack adaptor at the time! | 06:55 |
| noam | (from a sketchy USB-C power supply) | 06:55 |
| noam | iiiinteresting, following the foruim links through to https://community.mnt.re/t/laptop-unresponsive/749/11, I hve some ideas on what to test at least | 06:57 |
| noam | jfred: what repair shop? Any suggestions? | 06:59 |
| noam | Oh, and if I put the cells in and attach a power supply, they do not charge, and nothing changes; it's as if the cells aren't in anyways | 07:09 |
| noam | Haven't tried since using an external charger, I figure I should check the diode and heating issues noted in the prior forum pages first. | 07:09 |
| + glu__ (~glu@user/glu) | 08:19 | |
| - glu_ (QUIT: Ping timeout: 252 seconds) (~glu@user/glu) | 08:19 | |
| noam | minute: also,w as there another revision of the mainboard for reform classic coming soon? | 08:19 |
| BoostisBetter | noam: I think you will be able to use the Next innards in the Reform if you wanted. | 09:13 |
| ch | there is a new mobo version coming | 09:19 |
| ch | iirc in the finishing touches | 09:19 |
| noam | ^ that's what I was curious about | 09:21 |
| noam | More so than the Next stuff | 09:21 |
| josch | noam: yes, as far as i know, this is the latest status update on that topicd https://mastodon.social/@mntmn/113567763824202105 | 09:22 |
| noam | mmmm not bad at all, though it makes me wonder if new steel side ports iwll be needed? | 09:22 |
| noam | (since USB-C instead of barrel jack) | 09:23 |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| - aloo_shu (QUIT: Ping timeout: 245 seconds) (~aloo_shu@85.51.16.129) | 10:36 | |
| + aloo_shu (~aloo_shu@90.166.98.61) | 10:39 | |
| - aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@90.166.98.61) | 11:10 | |
| + aloo_shu (~aloo_shu@85.51.16.5) | 11:13 | |
| - aloo_shu (QUIT: Ping timeout: 260 seconds) (~aloo_shu@85.51.16.5) | 11:44 | |
| + aloo_shu (~aloo_shu@85.51.18.214) | 11:46 | |
| + cobra (~cobra@user/Cobra) | 11:59 | |
| + mjw (~mjw@gnu.wildebeest.org) | 12:05 | |
| - mtm (QUIT: Ping timeout: 244 seconds) (~textual@47.202.75.129) | 13:02 | |
| + gustav28 (~gustav@c-78-82-52-175.bbcust.telenor.se) | 13:03 | |
| + mtm (~textual@47.202.75.129) | 13:06 | |
| + chomwitt (~alex@2a02:587:7a09:1500:42b0:76ff:fe46:a5fd) | 13:13 | |
| - chomwitt (QUIT: Quit: Leaving) (~alex@2a02:587:7a09:1500:42b0:76ff:fe46:a5fd) | 13:44 | |
| - mjw (QUIT: Killed (zinc.libera.chat (Nickname regained by services))) (~mjw@gnu.wildebeest.org) | 13:52 | |
| * Guest5250 -> mjw | 13:52 | |
| - anzu (QUIT: Quit: WeeChat 3.5) (~anzu@melkki.cs.helsinki.fi) | 14:21 | |
| [tj] | Jan 3rd shipping date updated to Jan 10 | 14:34 |
| ericsfraga | [tj]: is that for pocket? I'm eagerly awaiting delivery but don't want to check for updates on the crowd supply website as it crashes my window manager (exwm) for some strange reason. | 14:52 |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 15:26 | |
| [tj] | yeah crowdsupply pocket reform | 15:26 |
| [tj] | that is an incredible crash | 15:26 |
| minute | there's a bug in the current main pocket sysctl fw state machine | 15:28 |
| minute | printf("# [pd] [ERROR] toggle wrong: %d\n", vbus_ok); | 15:29 |
| minute | pd_state->next_state = PD_STATE_CHARGER_DETECT; | 15:29 |
| minute | but then it goes on and measures CC and then in any case overwrites this state | 15:29 |
| minute | in PD_STATE_USB_DETECT | 15:29 |
| minute | ch: did you already rework this stuff? then i might be inclined to early merge things from your for | 15:30 |
| minute | fork | 15:30 |
| ch | minute: yeah all of that code is gone | 15:31 |
| minute | ok then it doesn't make sense i pull my hair about this | 15:32 |
| ch | ack | 15:32 |
| minute | currently i can't operate the device without batteries because it goes into some kind of reset loop | 15:32 |
| minute | the pd charger goes into a loop i mean | 15:32 |
| ch | right | 15:32 |
| ch | yeah i've seen that happen on the normal fw | 15:32 |
| minute | and that makes debugging of the hw very hard | 15:32 |
| minute | ok now how to merge your stuff... | 15:33 |
| ch | i can rebase my branch in a moment | 15:33 |
| minute | ah that would be mega awesome | 15:33 |
| ch | rebase is here: https://source.mnt.re/reform/pocket-reform/-/merge_requests/25 - i will test it in a moment | 15:42 |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone) | 15:45 | |
| minute | ch: niiice | 15:45 |
| minute | i finally did this https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_troubleshooting.html#check-out-locally-by-adding-a-git-alias | 15:48 |
| ch | ok seems to work for me | 15:49 |
| ch | found an interesting problem with a new charger, but i think that probably also doesnt work on 'main' | 15:49 |
| minute | ch: ok i also just flashed it, and it doesn't have the problematic looping behavior, so at least the board is now powered by 5V usb-c pd input (without charger board attached) | 15:50 |
| minute | (5.2V actually) | 15:50 |
| minute | ah, after replugging it goes to 20V | 15:50 |
| minute | indeed this works much better than the old code | 15:51 |
| ch | minute: do you have the 5v diode? | 15:51 |
| minute | no i don't have the diode | 15:51 |
| ch | heh | 15:51 |
| minute | (this PSU seems to give 5.2V though) | 15:51 |
| ch | if you can give it a test on a board with the diode, that'd be good | 15:51 |
| ch | especially with a psu that doesn't do more than 6V | 15:51 |
| minute | ch: sorry i misspoke. i _do_ have the original diode | 15:51 |
| ch | ah! | 15:51 |
| minute | i do not have the "hack" | 15:52 |
| minute | ok i will now connect a charger pcb | 15:52 |
| minute | (currently i had a power-in-out shim connected to pins 2+3 of charger port) | 15:52 |
| ch | ah you had no charger pcb altogether? | 15:52 |
| ch | good that it works :D | 15:52 |
| minute | yeah it's very good. | 15:52 |
| minute | then we can use this fw during production as well | 15:53 |
| minute | for flashing motherboards | 15:53 |
| minute | flashing soms i mean | 15:53 |
| minute | ACTION is jumbling up the nomenclature | 15:53 |
| ch | same | 15:53 |
| ch | :) | 15:53 |
| jfred | I appreciate all your work and troubleshooting because messing with the PD firmware would make me nervous ^^; | 15:54 |
| minute | aha, with charger pcb and _no batteries_ it doesn't work because of the diode drop i guess | 15:54 |
| minute | or some other drop on charger pcb | 15:55 |
| ch | maybe you can convince plom to send me a mobo [+charger pcb?], then testing these things would be a bit easier (: | 15:55 |
| ch | can you copy me the serial output? | 15:55 |
| minute | ch: we can do it! i need to convince greta only :D | 15:55 |
| minute | ch: serial output without batteries? | 15:55 |
| ch | minute: (look at ticket #4827) | 15:55 |
| minute | ch oh oh | 15:55 |
| ch | minute: yeah, like when it doesnt work | 15:56 |
| minute | ok | 15:56 |
| minute | ch: there's no serial then because the rp2040 can't be powered | 15:56 |
| ch | ah | 15:56 |
| ch | right | 15:56 |
| minute | but i can connect batteries and see what happens | 15:57 |
| ch | ugh, why does it not build in ci | 15:58 |
| minute | ch: maybe missing tag? | 15:58 |
| minute | i didn't really look though | 15:58 |
| ch | error: 'g2ec2936' undeclared | 15:58 |
| minute | ah | 15:58 |
| minute | yes my code expects MNTRE_FIRMWARE_VERSION to be an integer | 15:58 |
| minute | but in this case it's a string | 15:58 |
| minute | there's a way to wrap C defines in quotes after the fact but i forgot how/was too lazy yesterday | 15:59 |
| ch | yeah i'm sure i did -something- about this | 16:00 |
| ch | let me dig | 16:00 |
| minute | i.e. i just hacked the display of that constant into the main branch yesterday | 16:00 |
| ericsfraga | [tj]: Thanks and, yes, horrible crash but only now and again. Easy enough to avoid. | 16:00 |
| minute | charger works with batteries connected. now i'm inclined to try my old charger pcb that i think is busted | 16:02 |
| minute | or should i try to blow this working one up first with that anker supply... | 16:02 |
| ch | :D | 16:02 |
| minute | maybe that. then i can make sure it's really destructive | 16:02 |
| minute | but this time with usb-c power meter in series | 16:02 |
| ch | btw, the usb-pd meter (but also the debugger) sometimes change the behaviour of the connected components | 16:03 |
| ch | if in doubt, replug everything | 16:03 |
| ch | and plug in the pocket last, i think | 16:04 |
| minute | charger is fine | 16:05 |
| minute | i mean, this anker charger works fine with your firmware | 16:05 |
| minute | i tried with and without usb-pd meter | 16:05 |
| minute | maybe the old firmware created some kind of destructive fast on/off loop? we'll probably never know | 16:06 |
| ch | possible | 16:06 |
| ch | i did see chargers getting confused every now and then while i was working on my branch, so it wouldn't surprise me | 16:06 |
| minute | yeah... | 16:06 |
| minute | also the flickering of the usb-c pd meter display earlier did not inspire confidence | 16:06 |
| ch | haha yeah | 16:07 |
| ch | export PICO_SDK_PATH=/usr/src/pico-sdk adventure ahead! :D | 16:07 |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 16:10 | |
| minute | ch: ahaha | 16:12 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone) | 16:22 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 16:22 | |
| minute | ch: mega weird, my old broken charger pcb lives again | 16:24 |
| ch | well, nice? :) | 16:26 |
| ch | https://source.mnt.re/reform/pocket-reform/-/merge_requests/26/diffs i think this should fix the build then | 16:26 |
| ch | (maybe its even correct. how much i hate string handling in C) | 16:27 |
| minute | maybe there was a non-destructive latch-up or other event on the charger ic that made it hang/turn off until complete power cycle (removing batteries) | 16:27 |
| minute | ch: pipeline passed, thanks! | 16:28 |
| - Ar|stote|is (QUIT: Ping timeout: 245 seconds) (~linx@149.210.24.146) | 16:28 | |
| ch | lets see if the main build also works | 16:30 |
| ch | somehow this is more brittle than it should be | 16:30 |
| ch | it did | 16:31 |
| ch | nice | 16:31 |
| minute | ok, anker a2342 charger just came in the door as well | 16:31 |
| minute | power supply i mean m) | 16:31 |
| ch | the naming there is really confusing | 16:32 |
| ch | obviously i say 'charger' in all day life | 16:32 |
| ch | but are we then talking about the wall thing or the charger ic or the charger pcb | 16:32 |
| minute | works fine | 16:32 |
| minute | where does charger begin, where does it end | 16:33 |
| + Ar|stote|is (~linx@149.210.26.241) | 16:33 | |
| minute | ch: for the future we could do a manual usb device/charge toggle via the oled menu perhaps (or linux tool) | 16:34 |
| minute | i guess oled better because then you can toggle back if computer is off | 16:35 |
| ch | ah that would be a super interesting idea | 16:35 |
| minute | i.e. the uart api gets a command for that, but i don't know what you have to toggle in the pd code | 16:35 |
| ch | uh | 16:36 |
| ch | updating the kbd fw is weird | 16:37 |
| minute | depends | 16:37 |
| ch | it gave the reset hw watchdog on the oled | 16:37 |
| minute | ah yes that is "normal" | 16:37 |
| minute | because all resets go via the watchdog | 16:37 |
| ch | and Power on from the oled menu did reset the soc | 16:37 |
| minute | apparently | 16:37 |
| minute | oh | 16:37 |
| minute | that's weird @ power on | 16:37 |
| minute | btw one doesn't need to do that, opening battery status also updates the on status. buttt it's weird that it power cycles | 16:38 |
| ch | ah :) | 16:38 |
| ch | pretty sure it didnt power cycle in the past? | 16:38 |
| minute | yes it shouldn't have | 16:38 |
| minute | ch: maybe it sometimes gets just "p\r" and interprets that as "0p\r" | 16:41 |
| ch | ugh | 16:41 |
| ch | protocols without framing | 16:41 |
| minute | probably uart_state.cmd_number = 0; should really be -1 | 16:42 |
| minute | or something that is invalid by default | 16:42 |
| ch | the new apple charger i got is fun. it actually cares about the mA one sends! | 16:42 |
| minute | oh nice :D | 16:42 |
| ch | (ends in a loop where the charger rejects all requests, oh well) | 16:43 |
| minute | ew | 16:43 |
| ch | i feared we'll have to implement this properly one day | 16:44 |
| ch | the psu sends capabilities: 5V/1500mA, 9V/830mA, 15V/500mA, 20V/370mA | 16:45 |
| ch | my mac selects 15V/500mA | 16:45 |
| ch | so i -think- the charger ic has some way of setting a current limit... need to pick a good capability and set the limit | 16:46 |
| ch | wtf | 16:47 |
| ch | ah meh | 16:48 |
| ch | then there's some more handshaking and eventually it handshakes 20V/1700mA | 16:49 |
| ch | yeah that goes SOURCE_CAPABILITIES_EXTENDED | 16:49 |
| ch | but i think for that we have to accept messages from the psu when it notices it cant provide the current anymore | 16:50 |
| ch | not today(tm) | 16:51 |
| ch | minute: should the sysctl fw also turn on the watchdog? | 16:54 |
| minute | ch: i think so, but then you also have to regularly feed it :3 | 16:55 |
| ch | heh | 16:55 |
| minute | interesting, rp2040 is now hung again after reflashing via prog switch and resetting, like i2c is blocked again | 16:56 |
| amospalla | newer sysctl firmwares (newer than the August one) is not expected to use less battery, but keyboard firmware does, right? | 16:56 |
| minute | i'll try to power cycle my charger pcb again | 16:56 |
| minute | that worked! | 17:00 |
| minute | so disconnecting and reconnecting batteries from charger pcb unsticks it if it is in some bad state | 17:00 |
| ch | aha, the default input current limit is 1.5A | 17:00 |
| ch | that explains a few things | 17:00 |
| ch | oh and we set it to 2A | 17:01 |
| ch | ahem | 17:01 |
| minute | oh | 17:02 |
| minute | https://source.mnt.re/reform/pocket-reform/-/merge_requests/27 | 17:02 |
| ch | do you know what the batteries take at most as the charging current? | 17:02 |
| minute | afaik for lipo it should be "1C" so 4A? let me double check | 17:03 |
| minute | > A 1C charge rate means that the current will charge the entire battery in 1 hour | 17:03 |
| minute | batteries are https://www.eremit.de/p/eremit-3-7v-4-000mah-high-cap | 17:04 |
| ch | diff lgtm | 17:05 |
| minute | thx | 17:05 |
| - glu__ (QUIT: Ping timeout: 264 seconds) (~glu@user/glu) | 17:06 | |
| minute | on/off still works ;) | 17:07 |
| + mark_ (~mjw@gnu.wildebeest.org) | 17:07 | |
| minute | ok my pocket reform is healed again, i'll merge and roll this out to the first shipping (by mnt) pocket reforms here (they are for some universities) | 17:10 |
| minute | then we'll need to get everyone aboard the fwupd train... | 17:10 |
| minute | and then bring back usb-c dfp functionality via a oled menu toggle | 17:11 |
| ch | https://source.mnt.re/reform/pocket-reform/-/merge_requests/28/diffs just testing this | 17:11 |
| minute | ch: oh nice | 17:11 |
| ch | charge=2000mA yeah, i think its a good idea to not lie to the psu :D | 17:13 |
| ch | maybe that avoids bugs | 17:13 |
| ch | well, fried psus | 17:13 |
| ch | if it charges on fewer psus now, then so be it, but at least no magic smoke? | 17:14 |
| ch | # [keyboard] [ERROR] syntax error | 17:14 |
| minute | ch: ok, i can merge and test that too with some psus here | 17:14 |
| minute | ch: syntax error for which command? | 17:14 |
| ch | https://paste.debian.net/hidden/b6f17c37/ | 17:15 |
| ch | battery status | 17:15 |
| minute | hmm c 0 | 17:15 |
| minute | lemme double check | 17:16 |
| minute | haha now i get > # [keyboard] exec: c 65535 | 17:17 |
| ch | hah yes | 17:17 |
| minute | so my code might not be entirely right | 17:17 |
| ch | https://source.mnt.re/reform/pocket-reform/-/merge_requests/28 works for me; i think it'd be a good idea to have it in what you'll ship | 17:19 |
| ch | just quickly heading to the shop | 17:19 |
| minute | ch: ok, will do | 17:19 |
| minute | ah, number argument to c is ignored, so that's fine | 17:20 |
| minute | c command doesn't take a number | 17:20 |
| + glu_ (~glu@user/glu) | 17:20 | |
| ch | still resets though | 17:21 |
| ch | not always | 17:21 |
| minute | ch: do you see anything for that case in serial? | 17:21 |
| ch | no, i guess power is cut before it can show up in my minicom/ssh | 17:22 |
| minute | ahhh you're looking at it from the soc | 17:22 |
| minute | i have it connected to a pc | 17:22 |
| ch | :) | 17:22 |
| ch | also i think the reset that happens is wonky | 17:22 |
| minute | huh | 17:23 |
| ch | what i typed didnt arrive at the soc, etc | 17:23 |
| ch | but oled menu worked | 17:23 |
| minute | ok i need to reproduce that | 17:23 |
| ch | maybe i just have the weird hardware :) | 17:23 |
| minute | how do you trigger it? just power on via oled? | 17:23 |
| ch | ok, really shop now | 17:23 |
| ch | yeah | 17:23 |
| minute | ok | 17:23 |
| ch | this time the first time it did nothing, second power on did the wonky reset | 17:24 |
| minute | you have current kbd fw? | 17:24 |
| minute | (i can't reproduce it) | 17:24 |
| ch | yes | 17:27 |
| ch | just built from main | 17:27 |
| ch | oh i just remebered: the cabs need to go into the ci artifacts | 17:27 |
| minute | little bug: sysctl thinks charger is connected (but it's not) | 17:28 |
| ch | the charger ic? | 17:28 |
| minute | (after picotool reboot) | 17:28 |
| minute | sorry it says ON AC | 17:28 |
| ch | ah hm | 17:28 |
| minute | before the reboot it was ON BAT | 17:28 |
| ch | can you paste me before/after output? | 17:29 |
| minute | # [pd] PD_STATE_SETUP done, going to PD_STATE_UNATTACHED | 17:29 |
| minute | # [keyboard] exec: c 65535 | 17:29 |
| minute | # [keyboard] exec: c 65535 | 17:29 |
| minute | # ON AC chg=0 mps_flt=00 input=5000mV@50mA charge=0mA discharge=1250mA p=8.88W ttempty=1629min | 17:29 |
| minute | hmmm | 17:29 |
| minute | it still thinks ON AC | 17:29 |
| minute | after plugging + unplugging power supply | 17:29 |
| ch | eh. thats probably the internal 5V | 17:30 |
| minute | snippet https://gist.github.com/mntmn/fc732d9a9d1b0cf822f7ebd9e752720e | 17:30 |
| minute | but the (linux) UI doesn't show that charger is connected at least | 17:31 |
| minute | and linux ui correctly shows wall adapter icon when that's plugged in (after a minute) | 17:33 |
| minute | so no dealbreaker | 17:33 |
| - midfavila (QUIT: Remote host closed the connection) (midfavila@sdf.org) | 17:36 | |
| - murphnj (QUIT: Remote host closed the connection) (murph@user/murphnj) | 17:36 | |
| ch | ok | 17:37 |
| ch | needs better statemgmt of the 5v then | 17:37 |
| + murphnj (murph@user/murphnj) | 17:47 | |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone) | 19:04 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 19:18 | |
| amospalla | minute: I checked the battery depletion time with the sysctl firmware that reported lower amps. That firmware reported almost half the amps but the time it took to empty the battery was approximately the same. | 19:21 |
| minute | amospalla: hmm ok | 19:30 |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone) | 20:33 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 20:37 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 20:48 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 20:49 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 20:49 | |
| + simba (~simba@ppp-185-113-155-163.pool21.filstalnetz.de) | 20:59 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone) | 21:06 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 21:06 | |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone) | 21:25 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 21:29 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone) | 21:50 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 21:50 | |
| josch | errr.... i just ran into a problem with my a311d classic reform that i never have seen before | 21:54 |
| minute | josch: what happened? | 21:55 |
| josch | i watched some video with mpv when suddenly the video paused and it took a few seconds for it to continue | 21:55 |
| josch | when investigating this i found that systemd-journald was consuming 100% cpu | 21:55 |
| josch | and then, after half a minute not anymore but now /usr/libexec/rtkit-daemon did | 21:55 |
| josch | sudo would not do anything anymore so i cannot kill processes nor look at dmesg | 21:55 |
| josch | switching to another tty then gave me this once per second: https://mister-muffin.de/p/Q9lm.jpg | 21:56 |
| minute | josch: bpi wifi? | 21:57 |
| minute | josch: looks like a wifi driver bug | 21:58 |
| josch | i was connected to my access point via bpi wifi, yes | 21:58 |
| josch | odd... | 21:58 |
| josch | lets hope it doesn't happen again | 21:58 |
| josch | minute: also funny with the "kernel regression", right? This explains why this innocent commit broke things -- it just changed the /sys path... | 21:59 |
| josch | (for the imx8mq suspend/resume thing i mean) | 21:59 |
| - mjw (QUIT: Killed (erbium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 22:05 | |
| * mark_ -> mjw | 22:05 | |
| + Guest5378 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 22:06 | |
| minute | josch: yes! | 22:11 |
| josch | this should make reform-standby work for both paths: https://source.mnt.re/reform/reform-tools/-/merge_requests/108/diffs?commit_id=8124ebbcf4f4afd1d6e6f37ed94d66bc17deda85 | 22:12 |
| josch | well... i write should but i actually tried it and it works for both :) | 22:13 |
| josch | so no kernel change is necessary | 22:13 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-175.bbcust.telenor.se) | 22:15 | |
| minute | josch: very nice | 22:19 |
| josch | or... lets do what cambrian_invader suggested and use udevadm info instead :) | 22:21 |
| + midfavila (midfavila@freeshell.org) | 22:28 | |
| minute | nice | 22:30 |
| josch | minute: was a great tip to join that channel, thank you :) | 22:31 |
| josch | this is now actually future-proof https://source.mnt.re/reform/reform-tools/-/merge_requests/108/diffs?commit_id=1586267346b751d37e9fa5470df1aac9f2cbec71 | 22:37 |
| josch | oh we should do the same fix in sbin/reform-hw-setup | 22:42 |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 22:42 | |
| josch | oh no! | 22:43 |
| josch | https://source.mnt.re/reform/reform-tools/-/blob/main/sbin/reform-hw-setup?ref_type=heads#L136 | 22:43 |
| josch | we already knew about this change of ttymxc path in kernel 6.8 | 22:43 |
| josch | but i only fixed it in reform-hw-setup and missed that reform-standby *also* used that /sys path | 22:44 |
| josch | m( | 22:44 |
| BoostisBetter | I really am impressed with how far ARM SoCs have come in the last 5 years. | 22:48 |
| BoostisBetter | The pocket even with the imx8m+ could totally be someones only computer. | 22:48 |
| + jacobk (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 22:58 | |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 23:07 | |
| josch | minute: devices can be flagged with wakeup-source in the device tree? | 23:08 |
| minute | josch: sounds like! so we could do that | 23:09 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone) | 23:11 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 23:12 | |
| C-Keen | hi! Seems like I lost my wifi device after upgrading and rebooting... | 23:21 |
| josch | C-Keen: classic reform with imx8mq? | 23:22 |
| minute | interesting https://github.com/YaLTeR/niri/wiki/Xwayland#using-xwayland-satellite | 23:22 |
| C-Keen | josch: yes | 23:22 |
| C-Keen | has there been a change? | 23:22 |
| josch | C-Keen: did you already try rebooting a second time? does it remain gone? | 23:23 |
| C-Keen | josch: I may try | 23:24 |
| C-Keen | josch: hm, it is back. weird. that hasn't happened before | 23:26 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone) | 23:27 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 23:27 | |
| C-Keen | josch: and I see the driver output in the kernel log as it should... | 23:27 |
| josch | minute: I tried this but /sys/devices/platform/soc@0/30800000.bus/308?0000.serial/308?0000.serial:0/308?0000.serial:0.0/tty/ttymxc?/power/wakeup is still "disabled" | 23:32 |
| josch | C-Keen: i'm seeing the same here | 23:33 |
| josch | C-Keen: sometimes, on imx8mq, the wifi card does not show up -- a reboot fixes it | 23:33 |
| C-Keen | josch: interesting, that has never happened to me before but maybe I got lucky | 23:34 |
| C-Keen | (not anymore it seems) | 23:34 |
| josch | minute: ah sorry, forgot to paste the link to the patch: https://paste.debian.net/hidden/a976e22e/ | 23:36 |
| minute | josch: hmmmm | 23:38 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone) | 23:42 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 23:43 | |
| + chomwitt (~chomwitt@2a02:587:7a09:1500:1ac0:4dff:fedb:a3f1) | 23:54 | |
| - aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.214) | 23:55 | |
| C-Keen | idk if anyone in here is using freetube. it helps adding --ozone-platform=wayland to its command line to get rid of graphical rendering issues in newer versions (it is an electron application, so I guess their chrome underneath needs to get told to use wayland) | 23:56 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone) | 23:58 | |
| + aloo_shu (~aloo_shu@90.166.193.201) | 23:58 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 23:58 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
