| murphnj | Oh, the second time? I'll try it now. | 00:00 |
|---|---|---|
| murphnj | It gave a different --ser xxxxxxxxxxxx number, and the number was lower. (20250521 this time, 20250608 this time.) | 00:02 |
| murphnj | So I assume that the 0608 one was the system that I flashed today, and the 0521 is the one that I did before all of this fell apart. | 00:03 |
| murphnj | But I haven't restarted this today. Maybe we've got it in there? | 00:04 |
| murphnj | and the command that you asked for said that found system controller on bus 1 address 3 | 00:05 |
| murphnj | last time was bus 3 | 00:05 |
| zeha | if you now see two "Raspberry Pi RP2 Boot" in lsusb, then one of them will be the keyboard | 00:06 |
| murphnj | Yep, that's how they both show up. | 00:07 |
| murphnj | should I try to flash the keyboard FW on bus1? | 00:11 |
| zeha | i'd give that a try | 00:11 |
| murphnj | looked like it worked. | 00:11 |
| murphnj | It did something, anyway. | 00:11 |
| - chomwitt1 (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 00:12 | |
| murphnj | What next, reboot, flip power switch off, and try to power back on? I did minute's suggested line uncommented to have the system turn on automatically. | 00:14 |
| murphnj | Sorry, not reboot, shut down...... | 00:15 |
| zeha | are both still listed as rp2 boot in lsusb? | 00:15 |
| murphnj | yes | 00:15 |
| zeha | run `reform-mcu-tool reset rp2040-boot` twice | 00:15 |
| zeha | then the oled menu should probably work | 00:16 |
| murphnj | Yes, I did it, got two different bus numbers, and the oled just lit up. Let me check versions. | 00:17 |
| murphnj | on the oled: error:syntax | 00:17 |
| murphnj | ThenL MNT_Pocket_Reform HID | 00:18 |
| murphnj | The version looks like the last one I did, ends in 250407 | 00:18 |
| zeha | i'd use https://mnt.re/update-pocket-sysctl and https://mnt.re/update-pocket-keyboard to flash the latest 'normal' builds now | 00:19 |
| zeha | just to be sure they match | 00:19 |
| murphnj | I'll work on that now. | 00:20 |
| murphnj | Just download those and execute them? | 00:20 |
| zeha | yeah (run them as root / using sudo) | 00:21 |
| + L29Ah (~L29Ah@wikipedia/L29Ah) | 00:23 | |
| murphnj | That seemed a whole lot easier. | 00:25 |
| murphnj | should I do: run `reform-mcu-tool reset rp2040-boot` twice again, and check on the oled? | 00:25 |
| murphnj | even before that, I see one as pocket reform input, and the other as system controller. | 00:26 |
| murphnj | oled shows no change from before. | 00:26 |
| murphnj | zeha, ? | 00:36 |
| zeha | still shows some error on the oled? | 00:37 |
| murphnj | Yes, same error as before. Should I do: run `reform-mcu-tool reset rp2040-boot` twice again, and check on the oled? | 00:37 |
| zeha | i guess poweroff and flip the standby power, so both rp2040's will reset at almost the same time | 00:38 |
| murphnj | Gotcha. | 00:38 |
| murphnj | it is powering up now. system startus shows them both at 0512 | 00:43 |
| murphnj | looks good. will be running updates, and rebooting again. | 00:44 |
| murphnj | zeha, Thank you for the invaluable help. I never would have gotten through this without you and potatoespotatoes | 00:45 |
| zeha | np | 00:45 |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.5.33) | 01:00 | |
| + Ar|stote|is (~linx@149.210.5.33) | 01:00 | |
| - L29Ah (QUIT: Ping timeout: 248 seconds) (~L29Ah@wikipedia/L29Ah) | 01:31 | |
| - mjw (QUIT: Ping timeout: 265 seconds) (~mjw@gnu.wildebeest.org) | 01:38 | |
| + arminweigl_ (~arminweig@sourcehut/user/arminweigl) | 03:19 | |
| - arminweigl (QUIT: Ping timeout: 248 seconds) (~arminweig@sourcehut/user/arminweigl) | 03:20 | |
| * arminweigl_ -> arminweigl | 03:20 | |
| - paperManu (QUIT: Ping timeout: 276 seconds) (~paperManu@107.159.213.145) | 03:27 | |
| + L29Ah (~L29Ah@wikipedia/L29Ah) | 03:34 | |
| - digitalrane (QUIT: Remote host closed the connection) (~digitalra@user/digitalrane) | 06:26 | |
| - L29Ah (QUIT: Read error: Connection timed out) (~L29Ah@wikipedia/L29Ah) | 07:57 | |
| + chomwitt1 (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 08:42 | |
| + wiedi_ (~wiedi@ip5f581498.dynamic.kabel-deutschland.de) | 09:17 | |
| - wiedi (QUIT: Ping timeout: 245 seconds) (~wiedi@2a01:138:a015:15:a173:8d9:2f2f:5ace) | 09:20 | |
| + digitalrane (~digitalra@user/digitalrane) | 09:30 | |
| + tuesdaaay (~Srain@159.196.168.242) | 09:41 | |
| + ruby_ (~ruby@159.196.168.242) | 09:46 | |
| - tuesdaaay (PART: Leave.) (~Srain@159.196.168.242) | 09:46 | |
| - ruby_ (QUIT: Client Quit) (~ruby@159.196.168.242) | 09:47 | |
| + ruby_ (~ruby@159.196.168.242) | 09:47 | |
| - ruby_ (QUIT: Quit: ruby_) (~ruby@159.196.168.242) | 09:54 | |
| + CephonAltera (~cephonalt@user/CephonAltera) | 11:12 | |
| + mjw (~mjw@gnu.wildebeest.org) | 11:12 | |
| - Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.5.33) | 11:35 | |
| + Ar|stote|is (~linx@149.210.5.33) | 11:41 | |
| josch | minute: wow, having the speed of the rk3588 but now with a *big* screen and keyboard is even more sick o0 | 11:45 |
| minute | josch: haha, i'm glad you can finally experience it :D | 11:46 |
| josch | using usb-c with my big reform feels a bit dirty for some reason but it works :D | 11:46 |
| josch | also, full rgb keyboard... wow | 11:46 |
| - chomwitt1 (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 11:46 | |
| josch | love the purple default :D | 11:46 |
| josch | minute: you said that i do *not* strictly have to change the pocket sysctl firmware before trying it out with the bigger cells? | 11:47 |
| josch | (i only had a mini fright earlier because it would not turn on -- turns out, this usb-c adapter doesn't work with it...) | 11:47 |
| gsora | oof my reform just suddenly powered off | 11:48 |
| gsora | batteries were at 3.1v though, maybe it just ran out of power | 11:48 |
| minute | josch: you don't have to do anything about the fw. | 11:48 |
| josch | nice, thank you -- then fingers crossed :) | 11:49 |
| josch | in the worst case, you get me as another customer for yet another charging board XD | 11:49 |
| minute | gsora: could be upower deciding to turn off? | 11:49 |
| gsora | minute: battery level on gnome was well over 80% | 11:49 |
| minute | gsora: hmm and cell voltages when turning it on again? anything under 3v? | 11:50 |
| gsora | it doesn't turn on again | 11:50 |
| gsora | i'm plugging it in a power outlet to see | 11:50 |
| minute | ohh ok | 11:51 |
| gsora | seems completely dead, the oled doesn't turn on at all | 11:51 |
| gsora | was about to migrate my system on nvme :') | 11:52 |
| gsora | if I plug it in a power outlet, will the oled react to anything? | 11:54 |
| josch | when you press the circle button, yes | 11:54 |
| josch | gsora: rk3588 classic reform, right? | 11:54 |
| gsora | yup | 11:54 |
| gsora | let me try a different power adapter | 11:54 |
| josch | gsora: i'm operating mine right now without the batteries connected and with the wrong power adapter, the oled did nothing when pressing and holding the circle key | 11:55 |
| gsora | tried with a mac charger, which AFAIK implement usb-pd in a sane way | 11:56 |
| gsora | no dice | 11:56 |
| gsora | i need an external battery charger don't i :') | 11:57 |
| CephonAltera | ive definitely had very different behavior with different power adapters | 11:59 |
| CephonAltera | so far my most successful one is weirdly my proprietary Dell laptop charger. I tried an apple one and it seemed to discharge slowly, while Dell keeps it alive longer | 12:00 |
| gsora | trying with a different one | 12:00 |
| CephonAltera | i also tried a xiaomi 67W charger and same result as with apple | 12:00 |
| gsora | ah, i see a red LED on the right side of the motherboard lit up | 12:02 |
| gsora | so power is definitely getting through the board | 12:06 |
| gsora | i guess my batteries are under 3v | 12:06 |
| gsora | nope, they're well over 3v! checked with a multimeter | 12:13 |
| gsora | ok after disconnecting the batteries and connecting it to power, the oled display popped back to life | 12:14 |
| gsora | minute: ever seen anything like this? | 12:14 |
| gsora | now the keyboard keep pressing "t" and the little display says weird things about the battery... https://files.catbox.moe/1vdm4n.mov | 12:24 |
| + chomwitt1 (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 12:27 | |
| minute | gsora: does the keyboard stop doing that when exiting the menu? also i wonder if by chance the keyboard "standalone" key is on (it shouldn't be) | 12:30 |
| minute | gsora: normally the laptop has no problem recovering from low battery | 12:30 |
| gsora | nope, keyboard just stops working | 12:30 |
| minute | gsora: it can take a while with charger connected though | 12:30 |
| gsora | the oled screen is still on though | 12:30 |
| gsora | still shows those weird numbers | 12:31 |
| minute | gsora: keyboard not reacting to circle key? | 12:31 |
| gsora | keyboard doesn't respond anymore | 12:31 |
| gsora | tried pressing the lpc reset button, no dice | 12:31 |
| minute | gsora: ok, sounds like keyboard crashed. can you check if maybe the standalone switch is on? | 12:31 |
| gsora | sure, how can I do that? | 12:31 |
| minute | gsora: remove the keyboard frame, then it's exposed (and also the reset button of the keyboard, which is on the left-hand side) | 12:32 |
| gsora | i have the reform bottom removed if you need photos | 12:32 |
| minute | gsora: standalone switch is on the right-hand side | 12:32 |
| minute | gsora: not bottom | 12:32 |
| minute | gsora: top, keyboard frame | 12:32 |
| gsora | right, checking as we speak | 12:32 |
| josch | gsora: don't forget to unplug the batteries before removing the keyboard frame | 12:32 |
| minute | josch: not needed anymore | 12:33 |
| josch | oh? | 12:33 |
| josch | what changed? | 12:33 |
| minute | josch: the battery boards have kapton tape | 12:33 |
| minute | on their pins | 12:33 |
| josch | minute: so do mine | 12:33 |
| josch | still there were visible sparks | 12:33 |
| minute | not sure what happened then :D | 12:33 |
| minute | but yeah, in general it is of course best to remove/unplug batteries | 12:34 |
| + L29Ah (~L29Ah@wikipedia/L29Ah) | 12:34 | |
| gsora | minute: okay, top removed | 12:35 |
| gsora | the two switches I see are both on the "1" position | 12:35 |
| + paperManu (~paperManu@107.159.213.145) | 12:39 | |
| minute | gsora: that's good then | 12:51 |
| minute | gsora: what happens if you press the reset button next to the left switch? | 12:51 |
| gsora | the keyboard resets, mntre logo shows up and then works | 12:53 |
| gsora | considering this behavior happened three times, smells like a bug? | 12:56 |
| minute | gsora: yes, wondering what's going on hm. is your system setup "stock"? | 13:00 |
| gsora | i just finished moving to nvme, but when those issues happened, yeah it was as it came out of the box | 13:01 |
| gsora | i did add an nvme ssd and a wifi card | 13:02 |
| + gustav28 (~gustav@c-78-82-55-148.bbcust.telenor.se) | 13:02 | |
| gsora | oddly enough i just rebooted four times, migrated to nvme ssd twice, all with the battery boards disconnected, no issues at all | 13:18 |
| gsora | (had to migrate twice because i'm using an OPAL encrypted drive, and had to figure out /etc/crypttab) | 13:18 |
| - chomwitt1 (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 13:41 | |
| gsora | minute: crashed again! | 13:43 |
| gsora | this time alongside the lpc/battery charging circuit maybe? the oled battery monitor shows all zeroes in place of the Ah count | 13:44 |
| gsora | resetting the keyboard fixes it, i'll go eat something leaving reform charging and see if it crashes again | 13:47 |
| minute | gsora: yeah, this sounds suspicious, like LPC communications thing. maybe you can try the WIP LPC driver from here, but i'll merge it soon anyway: https://source.mnt.re/reform/reform-tools/-/merge_requests/127 | 13:47 |
| minute | gsora: i also did some lpc fw simplification that you can try | 13:48 |
| minute | gsora: https://source.mnt.re/reform/reform/-/merge_requests/84 | 13:48 |
| minute | gsora: i don't know how much you would mind compiling + flashing some WIP firmware and drivers? | 13:49 |
| minute | still pending is keyboard4 fw rework / merging together with the stability improvements from pocket keyboard fw | 13:49 |
| minute | but there shouldn't be so many issues out of the box also... so i'm a little bit puzzled | 13:49 |
| minute | gsora: do the issues go away if you `rmmod reform2_lpc`? | 13:50 |
| josch | gsora: anything specific you do to trigger the issue? I just received a unit from the same batch with the same software on it, so maybe it would be useful to see if i have this too? I didn't flash anything else on it yet. | 13:56 |
| gsora | nothing out of the ordinary I’d say? maybe it’s the charger im using? | 14:00 |
| gsora | minute: I’m open to compiling/flashing, as long as there’s a way to recover if anything goes wrong | 14:01 |
| gsora | another behavior I’m seeing: the oled battery status sometimes drops one battery, and recovers it after 1s | 14:01 |
| gsora | drops as in it shows as 0v, then goes back to 3.4 | 14:01 |
| abortretryfail | Pocket reform with the standby switch OFF should not have battery drain, right? Is that a sign of a faulty charger board? | 14:31 |
| abortretryfail | (context: I am still helping my friend troubleshoot hers.) | 14:32 |
| gsora | fwiw, I left it charging with gnome booted for a while now, no issues | 14:36 |
| minute | gsora: this is a comms/timing issue between kbd and lpc | 14:38 |
| minute | gsora: the dropping to 0 i mean. they are not actually dropping to 0 and also not measured as 0. just the kbd doesn't wait long enough for the full response | 14:39 |
| minute | abortretryfail: this is yet to be analyzed, i don't know the exact drain of the charger and monitor chips alone | 14:39 |
| abortretryfail | okay thanks. | 14:40 |
| minute | gsora: you can recover both kbd and lpc always if you have another computer and usb-c cable | 14:40 |
| minute | gsora: do you have these? | 14:40 |
| gsora | minute: plenty of computers and usb-c cables :^) | 14:50 |
| gsora | also, spoke too soon, keyboard crashed again | 14:50 |
| gsora | minute: here’s what it looks like https://files.catbox.moe/rdjxqi.jpg | 14:52 |
| minute | gsora: i see, again the 00000 for amps | 14:54 |
| minute | gsora: do you always have this battery screen open when it crashes? sounds like the crash is related to that | 14:55 |
| minute | on the OLED i mean | 14:55 |
| gsora | good question, i'm not sure | 14:56 |
| minute | gsora: can you use the computer for a while without opening that battery display? | 14:56 |
| gsora | when it shut of all of the sudden, i'm 90% sure I didn't | 14:56 |
| gsora | for reference, this behavior shows up with no load applied, while idling in gnome | 14:56 |
| minute | that is a different issue i think | 14:56 |
| gsora | interesting | 14:56 |
| minute | so, you have at least 2 distinct issues: 1. sudden shutdown 2. keyboard crash in battery screen | 14:57 |
| gsora | new issue: after pressing reset on the keyboard button, input in the computer itself is sluggish, and sometimes letters are repeated | 14:57 |
| minute | gsora: known issue, fixed on pocket. it's because the keyboard thinks the computer is off and wants to display the "turning it on" hint over and over again | 14:58 |
| gsora | yup, matches what I'm observing | 14:58 |
| minute | gsora: you can do the power on sequence via the keyboard to fix that. i wonder if that will keep the computer on or not (fixed in later fw) | 14:58 |
| gsora | confirming the power sequence fixes it | 14:59 |
| gsora | a couple of very lucky days for me! :^) | 14:59 |
| minute | josch: why do we have clang-format in this again? https://source.mnt.re/reform/reform-tools/-/jobs/10682#L278 | 14:59 |
| josch | minute: to avoid contributors from making arbitrary formatting changes | 15:00 |
| minute | some of these formatting choices are annoying :D | 15:00 |
| minute | ok i see | 15:00 |
| minute | is that kernel coding style? | 15:00 |
| josch | minute: you can customize it to your liking in .clang-format | 15:00 |
| josch | minute: yes | 15:00 |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net) | 15:00 | |
| minute | josch: ok, i will bow to it | 15:00 |
| josch | the .clang-format is copypasted from the kernel git | 15:00 |
| minute | josch: ok thanks | 15:01 |
| josch | speaking of which... let me update it to the latest version | 15:01 |
| josch | (there were some changes in the copy in the kernel) | 15:01 |
| minute | josch: update what to the latest version? this formatting file? | 15:01 |
| josch | yes | 15:01 |
| josch | (the new version does not require any changes to lpc/reform2_lpc.c) | 15:02 |
| minute | josch: delays that worked for you on imx8mq were 50,50,50 right? | 15:03 |
| minute | josch: oh oof | 15:03 |
| josch | oh dear -- let me make sure by checking irc history, sec... | 15:03 |
| minute | josch: i think i remember correctly ^^ | 15:04 |
| + bkeys (~Thunderbi@66.110.201.50) | 15:04 | |
| josch | okay | 15:04 |
| minute | josch: ok so i will get the same .clang-format too, yes? i don't think you pushed it now? | 15:05 |
| josch | oh you are right at it | 15:05 |
| josch | one sec | 15:05 |
| minute | yeah i wanted to merge the driver in this repo | 15:05 |
| minute | driver changes | 15:05 |
| josch | minute: pushed | 15:05 |
| minute | thx | 15:05 |
| josch | minute: you remembered correctly: https://mntre.com/reform-irc-logs/2025-05-31.log.html#t14:47:51 | 15:06 |
| minute | josch: thx | 15:07 |
| - bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 15:08 | |
| + bkeys (~Thunderbi@66.110.201.50) | 15:08 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 15:12 | |
| + bkeys (~Thunderbi@66.110.201.50) | 15:13 | |
| minute | yay, pipeline green | 15:15 |
| minute | ok, driver update meregd | 15:15 |
| minute | merged | 15:15 |
| minute | gsora: ok step 1 is: `git clone https://source.mnt.re/reform/reform-tools.git`, then `cd lpc; make`. this requires current kernel header package, probably you already have it | 15:16 |
| minute | gsora: for clarification, this step should be done on the reform itself | 15:16 |
| minute | gsora: it will build a `reform2_lpc.ko`. before you can try it, you need to `rmmod reform2_lpc` (as root), then you can `insmod reform2_lpc` | 15:17 |
| minute | gsora: sorry, probably `insmod ./reform2_lpc` | 15:17 |
| minute | gsora: argh. typing enter too quickly. `insmod ./reform2_lpc.ko` | 15:17 |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@66.110.201.50) | 15:18 | |
| minute | actually, let me clamp the low percentage first, this will probably prevent any weird shutdowns | 15:18 |
| josch | yes, nice! | 15:18 |
| minute | josch: where was the shutdown action again, 2%? | 15:18 |
| josch | one sec, checking... | 15:19 |
| gsora | compiling as we speak! | 15:20 |
| josch | minute: yes: https://sources.debian.org/src/upower/1.90.9-1/etc/UPower.conf/?hl=4#L67 | 15:21 |
| minute | josch: interesting, debian sets UsePercentageForPolicy=true which is not the default | 15:21 |
| minute | heh, > CriticalPowerAction=HybridSleep | 15:22 |
| minute | i guess that does nothing now that hybrid sleep is masked? | 15:22 |
| josch | not so fast, because in gnome-settings there is this: | 15:22 |
| josch | https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/blob/main/plugins/power/gsd-power-manager.c?ref_type=heads#L459 | 15:23 |
| josch | so either the action is "PowerOff" or it is anything else in which case gnome is doing hibernate | 15:23 |
| minute | josch: eek ok | 15:23 |
| josch | but then units are masked | 15:24 |
| josch | so in my tests on the pocket with the latest sysimage v5 tag, the system was shutting down | 15:24 |
| minute | i think i'm gonna clamp to 6%-100% | 15:24 |
| gsora | ok, compiled and insmodded | 15:24 |
| gsora | i can see battery percentage in gnome, so that's great | 15:24 |
| minute | gsora: was this not the case before? | 15:24 |
| gsora | yeah it was, just to say the new module is inserted and performing as intended | 15:25 |
| minute | gsora: ah great, ok. | 15:25 |
| gsora | btw so far the keyboard has been working fine | 15:25 |
| minute | gsora: ok, i think the kbd crash has to do with the battery screen auto-refresh/communication then. | 15:26 |
| gsora | and another thing, remember the round dots i was talking about on saturday? they're not appearing anymore, as long as the display stays in a specific position | 15:26 |
| gsora | the display pcb is most definitely either bent or broken | 15:26 |
| gsora | minute: sounds like an edge case! | 15:26 |
| minute | gsora: ah, i don't remember if you showed a picture of the dots | 15:27 |
| minute | gsora: maybe the screws of the display panel are too tight? | 15:28 |
| minute | gsora: the display frame i mean | 15:28 |
| gsora | let me re-upload the files then! | 15:28 |
| gsora | i tried unscrewing the display frame already, did not fix it | 15:28 |
| minute | gsora: (sorry, i have to track too many things in my head and they get purged) | 15:28 |
| minute | gsora: ok | 15:28 |
| gsora | no worries at all, thank you for being available on here | 15:29 |
| gsora | i understand building a product is tiring and hard | 15:29 |
| minute | haha yeah and it's a few products in parallel :0 | 15:29 |
| minute | gsora: if you pull & build again, the driver now limits the reported gauge to 6%-100%, this should prevent the OS from taking any action | 15:30 |
| gsora | this is the display behavior: https://files.catbox.moe/z953m1.mov | 15:30 |
| minute | gsora: remember that the OS will default to the old driver on reboot though | 15:30 |
| gsora | yup | 15:30 |
| minute | i think we'll soon roll out the updated driver via debian packages though | 15:30 |
| gsora | happy to give it a test run in the meantime | 15:31 |
| gsora | those are the dots: https://files.catbox.moe/d73l4g.jpg | 15:31 |
| minute | gsora: ooooh ok so tapping on that pcb causes glitches | 15:31 |
| gsora | yup, not just that, even moving the display makes that issue apparent | 15:32 |
| gsora | like opening and closing the lid | 15:32 |
| minute | gsora: ok, so the driver pcb might be very loose (or it's our cable that's plugged into the back of the display, is that ok?) | 15:32 |
| gsora | the cable on the reform motherboard appears to be inserted properly | 15:33 |
| minute | in any case i'm currently sourcing a ton of displays like that | 15:33 |
| gsora | oh in the back of the display... hmm | 15:33 |
| minute | gsora: yeah. | 15:33 |
| gsora | i checked that, it appeared fine | 15:33 |
| minute | ok | 15:33 |
| minute | gsora: ok, we can hopefully send you a new display via support@mntre.com soon | 15:33 |
| josch | minute: in the oled menu of my rk3588 classic reform I get "Press CIRCLE for menu. Hold to power up." but that does not seem to be implemented. Is the feature just not done yet or is the message wrong? | 15:34 |
| josch | the holding is not implemented i mean | 15:34 |
| minute | josch: you mean holding? | 15:34 |
| josch | yes | 15:34 |
| gsora | also isn't the cable at the center of the display? the issue should present itself when pressing anywhere rather than just on the left side | 15:34 |
| minute | josch: ah right. it could be an unimplemented carry-over from pocket fw | 15:34 |
| gsora | as for support@, I already sent an email, no rush in the meantime! | 15:34 |
| minute | gsora: ok thx | 15:34 |
| josch | okay, i'll file a small issue so that it does not get forgotten | 15:35 |
| minute | josch: thanks. this would be part of merging pocket kbd fw fixes | 15:35 |
| minute | josch: i'm still thinking if pocket+kbd4 fw should be one codebase or 2. but feels a bit too heavy lift to unify these before GPN | 15:36 |
| minute | so i might just port a few quality of life fixes first | 15:36 |
| josch | in contrast to the other recent issues, at least that one is just cosmetic :) | 15:36 |
| - Asmadeus (QUIT: Ping timeout: 252 seconds) (~asmadeus@user/meow/Asmadeus) | 15:42 | |
| minute | gsora: the next thing to do would be to update the lpc firmware, this is a bit more involved, as you need to connect another computer via usb-c to the internal usb-c flashing port of reform's motherboard | 15:47 |
| + bkeys (~Thunderbi@66.110.201.50) | 15:49 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 15:50 | |
| + bkeys (~Thunderbi@66.110.201.50) | 15:50 | |
| minute | gsora: OTOH, lets see which version you have right now. can you do: `sudo cat /sys/devices/platform/feb10000.spi/spi_master/spi1/spi1.0/firmware` | 15:50 |
| gsora | sure, one sec | 15:50 |
| + bkeys1 (~Thunderbi@38-146-94-247.echocast.zone) | 15:51 | |
| gsora | MREF2LPC 30_R1 g08e5576 | 15:52 |
| minute | ah interesting | 15:52 |
| gsora | too old/new? | 15:52 |
| minute | that's from may 7 | 15:52 |
| minute | commit 08e5576ccc31ca7ed24218fcc167b46299e1098e | 15:52 |
| minute | it doesn't have the spi rework yet | 15:53 |
| minute | oh no, my CI build failed... | 15:53 |
| minute | ah. keyboard fw version tag | 15:54 |
| josch | in the pocket oled, when it's off and attached to power, will it ever show 0.0A? It keeps showing -0.10A even though it has been attached for hours | 15:54 |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@66.110.201.50) | 15:55 | |
| * bkeys1 -> bkeys | 15:55 | |
| minute | josch: maybe it's balancing or trickle charging | 15:55 |
| minute | josch: but... i honestly don't know | 15:55 |
| minute | gsora: this procedure is up-to-date, but we need to wait for the pipeline to be green https://mntre.com/documentation/reform-handbook/hardware.html#flashing-the-firmware | 15:56 |
| minute | gsora: the thing about removing the batteries is more of a warranty/safety thing, because you could touch a battery clip with the usb-c cable or sth | 15:57 |
| gsora | indeed | 16:01 |
| gsora | it looks like i'm flashing an rp2040 | 16:01 |
| gsora | because it probably is :^) | 16:01 |
| minute | gsora: no, it's an LPC. did you wait till the pipeline is green? | 16:02 |
| minute | ah, pipeline failed again | 16:02 |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@38-146-94-247.echocast.zone) | 16:02 | |
| minute | quite annoying | 16:03 |
| minute | ah, changelog | 16:03 |
| josch | minute: too annoying? My goal with these checks was: avoid making mistakes | 16:03 |
| minute | josch: no, good actually | 16:07 |
| minute | josch: would be convenient to be able to do these checks before CI (because CI takes long to set up every time... maybe that's the actual problem, the install times in CI) | 16:07 |
| minute | josch: i agree that these checks are useful, i would have forgotten about the changelogs otherwise | 16:08 |
| minute | gsora: the chip on reform motherboard is still lpc11u24, back when the original motherboard 2.0 was designed, there wasn't a rp2040 yet | 16:12 |
| minute | yay, reform pipeline is green again \o/ | 16:13 |
| minute | gsora: now the instructions for flashing the lpc can be followed (the download script will download the latest build from the CI) | 16:13 |
| josch | minute: would you like me to transfer what is currently in ~/.gitlab-ci.yml to a build-all.sh or similarly named shell script that you can run locally including the checks? | 16:15 |
| minute | josch: that would be great actually, yeah! | 16:15 |
| minute | now that reform and reform-tools/lpc are merged, i'm finishing pocket-reform-sysctl-fw... | 16:15 |
| josch | minute: you should once you'd like me to cut a new reform-tools release, yes? | 16:16 |
| josch | s/you should/you shout/ | 16:16 |
| minute | josch: cool, yeah. i'm testing the pocket fw now regarding, does shutdown work correctly again | 16:17 |
| gsora | minute: awesome, i'll get on it now | 16:21 |
| gsora | i only have a mac available at my disposal right now, I wonder, can you link me the latest CI artifact? I'll copy it manually | 16:23 |
| josch | gsora: https://source.mnt.re/reform/reform/-/jobs/10817/artifacts/browse | 16:30 |
| minute | gsora: you don't need to build anything | 16:31 |
| minute | gsora: the download-fw.sh script will download the build | 16:31 |
| minute | unrelated: my new pocket sysctl fw reliably goes into T mode after turning off via spi. no idea why, yet | 16:32 |
| - Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.5.33) | 16:35 | |
| gsora | ok, flashed | 16:35 |
| gsora | also insmodded the lpc driver | 16:38 |
| + Ar|stote|is (~linx@149.210.5.33) | 16:40 | |
| minute | gsora: nice. do you get some dmesg output from lpc? about api version? | 16:50 |
| - ZetaR (QUIT: Read error: Connection reset by peer) (~user@c-98-208-141-90.hsd1.fl.comcast.net) | 16:54 | |
| gsora | yup, says version g7d5f91f | 16:57 |
| - paperManu (QUIT: Quit: WeeChat 4.1.1) (~paperManu@107.159.213.145) | 17:05 | |
| + ZetaR (~user@c-98-208-141-90.hsd1.fl.comcast.net) | 17:11 | |
| minute | gsora: ok, that's not normal hm | 17:12 |
| minute | i probably messed something up in regards to tagging, again | 17:13 |
| minute | lets see if i can redo the git tag | 17:14 |
| minute | gsora: i hope you're ok with flashing that again soon. you did everything right on your end, but i had to redo the git tag to get it into the firmware revision, so it will report 20250609 instead of that git hash, otherwise the driver won't recognize the faster v2 api | 17:17 |
| minute | (CI needs to complete first though) | 17:18 |
| minute | meanwhile i found a solution for the new pocket reform sysctl fw. i removed 2 potential endless loops and added the watchdog reset feature from the keyboard (resets after 1 sec of stuck-ness) | 17:18 |
| - L29Ah (QUIT: Read error: Connection reset by peer) (~L29Ah@wikipedia/L29Ah) | 17:20 | |
| minute | gsora: pipeline done, good to reflash lpc one more time | 17:20 |
| minute | josch: ok, i'm requesting a reform-tools/lpc release :3 | 17:21 |
| gsora | ok! will do asap | 17:35 |
| gsora | also fwiw, macos doesn't recognize the lpc usb disk | 17:35 |
| gsora | i remember having the same issue when i was working on precursor's usb disk implementation | 17:35 |
| gsora | maybe it's too small for macos to care lol | 17:36 |
| gsora | huh, i just shut down the reform with gnome's "shutdown" button, but the keyboard stays ib' | 17:36 |
| gsora | s/ib'/on/ | 17:37 |
| minute | gsora: that's probably because of the lpc module re-insertion | 17:37 |
| gsora | ah! | 17:37 |
| minute | gsora: i also had this issue here on pocket today a few times when experimenting with lpc module | 17:37 |
| gsora | should i update now, or wait until reform-tools/lpc is released? | 17:37 |
| gsora | fyi i'm tempted to poke at the rust4linux thing and using lpc as my scape goat | 17:38 |
| minute | gsora: you can update now, the lpc release is just for the module/driver | 17:39 |
| josch | gsora: is that the issue with 000000 that you are seeing on your oled? https://mister-muffin.de/p/XDLh.jpg | 17:45 |
| gsora | yup | 17:45 |
| gsora | also wow, nice photo! | 17:45 |
| josch | nice? :D | 17:46 |
| gsora | minute: i'll start with the update asap, stuck in a work meeting atm | 17:46 |
| + L29Ah (~L29Ah@wikipedia/L29Ah) | 17:47 | |
| gsora | josch: yeah, it looks very detailed | 17:48 |
| josch | ah okay :) | 17:48 |
| gsora | how did you reproduce it? | 17:49 |
| gsora | flash completed, the oled shows the correct version! | 18:05 |
| gsora | but the battery capacity is gone | 18:07 |
| gsora | it worked with the old lpc driver, the new one has dmesg say "driver failed to report..." | 18:08 |
| gsora | the old driver works fine | 18:12 |
| - ericsfraga (QUIT: Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50)) (~user@2a00:23cc:b45c:9001::99e) | 18:13 | |
| + bkeys (~Thunderbi@66.110.201.50) | 18:13 | |
| minute | gsora: hmmm ok | 18:14 |
| minute | gsora: might be because of changing of lpc driver version in the middle etc | 18:14 |
| josch | minute: i now have an unresponsive rk3588 classic reform as well. oled menu is stuck, no keypress does anything. So I guess I can also flash things and test if it fixes things. :) | 18:17 |
| gsora | did you also leave the battery menu on when this happened? | 18:18 |
| josch | yes | 18:20 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50) | 18:20 | |
| + bkeys (~Thunderbi@172.56.71.178) | 18:21 | |
| minute | josch: aha, thanks for reproducing | 18:22 |
| minute | josch: gsora: it's still possible that this happens with the new lpc fw (and i'd like to know), keyboard4 fw fixes are still (urgently) todo | 18:22 |
| minute | but now i've released pocket fw https://source.mnt.re/reform/pocket-reform/-/releases/20250609 | 18:22 |
| minute | cc zeha | 18:23 |
| gsora | i'll leave mine on the battery view as we speak | 18:23 |
| minute | now, how to push this to fwupd... | 18:24 |
| spew | my reform classic is now in mexico, only about an hour away | 18:24 |
| gsora | as for the driver, I imagine a new release will be published on debian repos soon? | 18:24 |
| minute | spew: nice | 18:26 |
| minute | gsora: yeah, josch will make a new reform-tools and thus reform2-lpc release | 18:26 |
| gsora | great! | 18:27 |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@172.56.71.178) | 18:35 | |
| + bkeys (~Thunderbi@66.110.201.50) | 18:42 | |
| minute | zeha: weird, in lvfs upload i get > Upload Failed: File is not supported: Metadata is invalid: description has no value | 18:43 |
| minute | zeha: description in the xml looks medium-ok though, it's `<p>Release Build</p>` and then an empty line | 18:44 |
| minute | perhaps i need to add more stuff to description-release.html | 18:46 |
| gsora | wow, sway feels a lot better than gnome | 18:47 |
| minute | gsora: it does? | 18:47 |
| gsora | minute: i regularly see the 0000 bug happening | 18:47 |
| gsora | but the keyboard never locks, actually, i see it rebooting | 18:47 |
| gsora | so the watchdog is definitely working | 18:47 |
| gsora | as for sway, yeah, i feel the system to be faster, but i've been using i3 et similar foryears now | 18:47 |
| minute | gsora: ah yes. sway's rendering is faster than gnome's. | 18:48 |
| gsora | *by a lot* :D | 18:48 |
| minute | i wish gnome could just use wlroots... | 18:48 |
| + bkeys1 (~Thunderbi@172.56.71.178) | 18:48 | |
| minute | anyway. | 18:48 |
| minute | gsora: the keyboard doesn't lock up anymore? that's interesting, because we didn't update your keyboard fw | 18:49 |
| gsora | maybe it was the lpc? | 18:49 |
| minute | gsora: possible yeah | 18:49 |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@66.110.201.50) | 18:50 | |
| * bkeys1 -> bkeys | 18:50 | |
| gsora | it just did it again | 18:50 |
| minute | gsora: did what? the 0000 or the lockup? | 18:55 |
| gsora | 0000, i also noticed that for roughly 1s after the 0000 and subsequent reboot, the keyboard did not respond | 18:56 |
| minute | gsora: ok, so the keyboard did reboot and maybe set something like watchdog reboot? | 18:59 |
| minute | s/set/said | 18:59 |
| gsora | it said nothing, that';s the weird thing | 19:00 |
| minute | ok | 19:00 |
| gsora | i just noticed that when the 0000 happens, the keyboard stops responding for ~1s, then resumes as soon as the lpc starts reporting data again | 19:00 |
| gsora | all of this is with the battery view selected | 19:00 |
| minute | ah ok | 19:01 |
| minute | gsora: ok this is probably caused by the reform2_lpc driver | 19:01 |
| minute | gsora: because it blocks the lpc for quite a long time (a few hundred ms) when it polls | 19:01 |
| minute | gsora: meanwhile, the keyboard doesn't get the data it wants | 19:01 |
| minute | gsora: the new driver doesn't cause these huge delays anymore | 19:01 |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@172.56.71.178) | 19:04 | |
| gsora | ah wait, so the menu on the oled is drawn by the lpc driver? | 19:05 |
| minute | gsora: no | 19:09 |
| gsora | nvm then, my brain is fried after a long day at work :D | 19:10 |
| minute | gsora: but the content for the battery screen comes from the LPC over uart. the LPC has an event loop. it can service SPI or UART, but not both exactly at the same time. because of legacy reasons, the old reform2_lpc driver blocks the LPC for a while when querying. during that time, the keyboard can't get the content it needs for the battery screen | 19:11 |
| gsora | ahhh i see | 19:11 |
| minute | gsora: and there's no preemptive multitasking in the lpc fw | 19:11 |
| minute | (in the new pocket fw, there kind of is, because SPI servicing is now on a timer interrupt) | 19:11 |
| + bkeys (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net) | 19:15 | |
| gsora | i see! thanks for the explaination | 19:19 |
| - bkeys (QUIT: Ping timeout: 260 seconds) (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net) | 19:20 | |
| + bkeys (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net) | 19:20 | |
| minute | ok, almost an hour later > Upload Failed: File is not supported: Metadata is invalid: description has no value | 19:47 |
| minute | oh, wait a second | 19:48 |
| minute | the HTML in release/description should probably be escaped, like the one in the component/description? | 19:49 |
| minute | hmm > key: value if key == 'release_description' or value is None else escxml(value) | 19:51 |
| minute | ACTION is trying to read python | 19:51 |
| minute | zeha: why is 'release_description' verbatim and others are escxml()ed? | 19:52 |
| zeha | uhh | 19:53 |
| zeha | probably because you can use html in it | 19:53 |
| zeha | i dont think it should be escaped | 19:53 |
| zeha | description and release_description might be different things, not sure | 19:53 |
| minute | mhm > There are currently quite strict limits on the format of the release description included in the description part of the metainfo, or edited on the LVFS. For instance, OEMs are not allowed to include links within the text and have to adhere to a limiting style guide | 19:54 |
| minute | zeha: yeah, in the example the html is verbatim indeed, but it's also verbatim in the component/description | 19:55 |
| minute | zeha: i'll change it to also not escxml the firmware_description | 19:56 |
| zeha | kk | 19:56 |
| minute | mhm > The AppStream utility appstreamcli validate can validate all kinds of AppSteeam XML metadata | 19:57 |
| minute | interesting > I: com.mntre.pocket_reform.sysctl10.firmware:~: driver-firmware-description-missing | 19:58 |
| minute | also funny > W: com.mntre.pocket_reform.sysctl10.firmware:4: component-name-too-long | 19:58 |
| minute | (Pocket Reform System Controller 1.0 Firmware) | 19:58 |
| minute | but fwupd didn't complain about that | 19:58 |
| minute | ok, when not escaping the firmware_description, this output changes | 19:59 |
| minute | I: com.mntre.pocket_reform.sysctl10.firmware:7: description-first-para-too-short | 20:00 |
| minute | MNT Research Pocket Reform System Controller Firmware Update (Release Build) | 20:00 |
| minute | appstream wants at least 80 chars there | 20:00 |
| BoostisBetter | is there a recently released sysctrl that I can try? I got the one from this year already but if there is something newer I would love to give it a whirl. | 20:01 |
| BoostisBetter | the sysctrl firmware I have is from 12 May of this year | 20:02 |
| BoostisBetter | sorry for butting into the end of the conversation like this. Just thought I would try to jump on a new firmware release if that is what this is. | 20:04 |
| minute | zeha: ok, it was accepted now, will push my changes | 20:10 |
| minute | > The remote metadata will be rebuilt in 49 minutes. This firmware has not yet been included in the XML catalog. | 20:11 |
| minute | BoostisBetter: yeah you can test updating via fwupd once this is through their process | 20:12 |
| BoostisBetter | minute: thanks. I will wait for the all clear on that. | 20:12 |
| + AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net) | 20:14 | |
| zeha | minute: thanks | 20:14 |
| minute | wrote hughsie and asked what i have to do to get permission to use the "move to testing" button | 20:20 |
| minute | probably first i have to wait 40 minutes > The remote metadata will be rebuilt in 40 minutes. This firmware has not yet been included in the XML catalog. | 20:20 |
| + chomwitt (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 20:21 | |
| minute | ok... on to other topics in the meantime | 20:23 |
| - bkeys (QUIT: Ping timeout: 272 seconds) (~Thunderbi@h211.16.186.173.dynamic.ip.windstream.net) | 20:25 | |
| + bkeys (~Thunderbi@172.56.70.38) | 20:34 | |
| minute | ah, i got feedback from hughsie | 20:36 |
| minute | i have to solve the "problems" in the problems tab | 20:36 |
| minute | > Release urgency has not been set for ‘MNT Research Pocket Reform 1.0 Embedded Controller Update’ | 20:36 |
| + bkeys1 (~Thunderbi@66.110.201.50) | 20:36 | |
| minute | > Firmware protocol requires fwupd report for ‘MNT Research Pocket Reform 1.0 Embedded Controller Update’ | 20:37 |
| minute | ok, need a success report for the second one, that should be easy | 20:37 |
| minute | > All components should have an appropriate update urgency before a firmware is moved to stable. This also can be set in the .metainfo.xml file | 20:37 |
| - bkeys1 (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 20:38 | |
| minute | i was able to set the update urgency manually in the dashboar | 20:38 |
| minute | +d | 20:38 |
| - bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@172.56.70.38) | 20:39 | |
| - chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 20:39 | |
| minute | the other i can solve after 20 more minutes of waiting... | 20:40 |
| + bkeys (~Thunderbi@66.110.201.50) | 20:40 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 20:41 | |
| + bkeys (~Thunderbi@66.110.201.50) | 20:41 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50) | 20:51 | |
| + bkeys (~Thunderbi@66.110.201.50) | 20:51 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 20:54 | |
| + bkeys (~Thunderbi@66.110.201.50) | 20:54 | |
| + chomwitt (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 20:59 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50) | 21:03 | |
| + bkeys (~Thunderbi@66.110.201.50) | 21:04 | |
| - chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 21:07 | |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@66.110.201.50) | 21:09 | |
| + bkeys (~Thunderbi@66.110.201.50) | 21:14 | |
| - L29Ah (QUIT: Ping timeout: 248 seconds) (~L29Ah@wikipedia/L29Ah) | 21:16 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 21:17 | |
| + bkeys (~Thunderbi@66.110.201.50) | 21:17 | |
| + Asmadeus (~asmadeus@user/meow/Asmadeus) | 21:20 | |
| + bkeys1 (~Thunderbi@38-146-94-247.echocast.zone) | 21:25 | |
| - bkeys (QUIT: Ping timeout: 245 seconds) (~Thunderbi@66.110.201.50) | 21:28 | |
| - bkeys1 (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone) | 21:29 | |
| + bkeys (~Thunderbi@38-146-94-247.echocast.zone) | 21:32 | |
| minute | zeha: update mechanism doesn't seem to work, "failed to wait for detach replug: device ... did not come back" | 21:37 |
| minute | > Bus 005 Device 003: ID 2e8a:0003 Raspberry Pi RP2 Boot | 21:38 |
| minute | zeha: this made it come back > sudo reform-mcu-tool reset rp2040-boot | 21:39 |
| minute | yeah, also doesn't work on a second try, the "Restarting device" step seems to be borked | 21:40 |
| minute | updating fwupd... | 21:41 |
| minute | ok interesting, this works > fwupdmgr reinstall 377eb704f59a32dc0c615859a9e7bb66246a732d | 21:43 |
| minute | will try again with gnome firmware | 21:43 |
| minute | ok nice, now it works | 21:44 |
| minute | so one has to be on latest fwupd package | 21:44 |
| + bkeys1 (~Thunderbi@66.110.201.50) | 21:48 | |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@38-146-94-247.echocast.zone) | 21:50 | |
| * bkeys1 -> bkeys | 21:50 | |
| minute | success report uploaded, still no dice, "permission denied" to move to testing. frustrating experience | 21:54 |
| zeha | (i cant actually press approve btw) | 21:55 |
| minute | zeha: ah right. | 21:55 |
| zeha | (in gitlab) | 21:55 |
| zeha | so you have to wait for hughsie i guess? | 21:55 |
| minute | zeha: thanks for your lgtm! | 21:55 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@66.110.201.50) | 21:55 | |
| minute | zeha: yeah, i sent him a screenshot | 21:55 |
| + bkeys1 (~Thunderbi@66.110.201.50) | 21:55 | |
| - bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50) | 21:56 | |
| + bkeys (~Thunderbi@66.110.201.50) | 21:56 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@66.110.201.50) | 21:59 | |
| + bkeys (~Thunderbi@66.110.201.50) | 21:59 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50) | 22:00 | |
| + bkeys (~Thunderbi@66.110.201.50) | 22:01 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@66.110.201.50) | 22:03 | |
| + bkeys (~Thunderbi@66.110.201.50) | 22:04 | |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@66.110.201.50) | 22:08 | |
| minute | zeha: ah, they were missing the legal signoff document, sent now | 22:12 |
| zeha | ah | 22:13 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-55-148.bbcust.telenor.se) | 22:15 | |
| + CephonAltera_ (~cephonalt@mm-16-222-126-178.vitebsk.dynamic.pppoe.byfly.by) | 22:55 | |
| - CephonAltera (QUIT: Ping timeout: 252 seconds) (~cephonalt@user/CephonAltera) | 22:57 | |
| - CephonAltera_ (QUIT: Ping timeout: 252 seconds) (~cephonalt@mm-16-222-126-178.vitebsk.dynamic.pppoe.byfly.by) | 23:07 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 23:08 | |
| + L29Ah (~L29Ah@wikipedia/L29Ah) | 23:14 | |
| + CephonAltera (~cephonalt@mm-198-120-126-178.vitebsk.dynamic.pppoe.byfly.by) | 23:15 | |
| - CephonAltera (QUIT: Ping timeout: 252 seconds) (~cephonalt@mm-198-120-126-178.vitebsk.dynamic.pppoe.byfly.by) | 23:20 | |
| + chomwitt (~chomwitt@2a02:85f:9ace:3000:1ac0:4dff:fedb:a3f1) | 23:25 | |
| minute | zeha: ok i can finally press the buttons | 23:32 |
| minute | moved to testing, but not sure how people can see stuff from testing | 23:37 |
| + jackhill (~jackhill@kalessin.dragonsnail.net) | 23:37 | |
| minute | ah probably one has to set Enabled=true in /etc/fwupd/remotes.d/lvfs-testing.conf | 23:39 |
| minute | > fwupdmgr enable-remote lvfs-testing | 23:40 |
| minute | BoostisBetter: to test the new firmware on pocket, do the following: 1. make sure fwupd is up to date (`sudo apt update; sudo apt install fwupd`). 2. enable testing firmware remote: `fwupdmgr enable-remote lvfs-testing`. 3. check if you can see the update when you click on "MNT Research Pocket Reform System Controller" in the gnome-firmware GUI tool | 23:44 |
| minute | cc josch | 23:44 |
| + paperManu (~paperManu@107.159.213.145) | 23:53 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
