| + jackhill (~jackhill@kalessin.dragonsnail.net) | 00:47 | |
| + XgFgX (~quassel@2001:19f0:5001:1174:dc82:8500:c2c0:c061) | 01:18 | |
| - XgF (QUIT: Ping timeout: 256 seconds) (~quassel@2001:19f0:5001:1174:5400:2ff:fef2:1fa2) | 01:19 | |
| - Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66) | 01:35 | |
| - gachikuku (QUIT: Read error: Connection reset by peer) (~gachikuku@kamil.gr) | 01:48 | |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 02:58 | |
| - paperManu_ (QUIT: Ping timeout: 240 seconds) (~paperManu@64.58.44.160) | 02:59 | |
| + paperManu (~paperManu@64.58.44.160) | 03:23 | |
| - paperManu (QUIT: Ping timeout: 264 seconds) (~paperManu@64.58.44.160) | 03:29 | |
| + paperManu (~paperManu@79.127.134.42) | 03:31 | |
| + colinsane (~colinunin@97-113-89-123.tukw.qwest.net) | 03:37 | |
| - nsc (QUIT: Ping timeout: 240 seconds) (~nicolas@181-99-142-46.pool.kielnet.net) | 03:46 | |
| + nsc (~nicolas@181-96-142-46.pool.kielnet.net) | 03:48 | |
| - paperManu (QUIT: Read error: Connection reset by peer) (~paperManu@79.127.134.42) | 04:18 | |
| - jackhill (QUIT: Ping timeout: 245 seconds) (~jackhill@kalessin.dragonsnail.net) | 05:11 | |
| + jackhill (~jackhill@kalessin.dragonsnail.net) | 05:12 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 05:53 | |
| + plomtest (~plom@user/plomtest) | 05:55 | |
| - plomtest (QUIT: Remote host closed the connection) (~plom@user/plomtest) | 07:14 | |
| + plomtest (~plom@user/plomtest) | 07:18 | |
| + manis (01a66df340@185.72.67.185) | 07:20 | |
| - potash (QUIT: Quit: The Lounge - https://thelounge.chat) (~potash@user/foghorn) | 07:26 | |
| - plomtest (QUIT: Read error: Connection reset by peer) (~plom@user/plomtest) | 07:28 | |
| - robin (QUIT: Ping timeout: 264 seconds) (~robin@user/terpri) | 08:34 | |
| - svp (QUIT: Ping timeout: 245 seconds) (~svp@2002:4f07:f0bd:0:69b1:b463:d245:e861) | 08:36 | |
| + robin (~robin@user/terpri) | 09:00 | |
| + thelounge2784 (~thelounge@gidzit.org) | 09:01 | |
| + S0rin (~S0rin@user/s0rin) | 10:01 | |
| + Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66) | 10:03 | |
| - Gooberpatrol66 (QUIT: Read error: Connection reset by peer) (~Gooberpat@user/gooberpatrol66) | 10:03 | |
| + plomtest (~plom@user/plomtest) | 10:04 | |
| josch | minute: back in june i reported that my laptop would just freeze with openrgb effects running for a while: https://mntre.com/reform-irc-logs/2025-06-27.log.html Back then I had the keyboard v4 as an external keyboard on my a311d classic reform. | 10:27 |
|---|---|---|
| josch | With keyboard v4 in rk3588 classic reform, the keyboard will "only" refuse to display any further color after a while but otherwise work fine. | 10:28 |
| josch | Any then one can simply reset the keyboard and restart openrgb. | 10:28 |
| josch | So there is still a problem but it's not "that bad" it seems. | 10:28 |
| - plomtest (QUIT: Remote host closed the connection) (~plom@user/plomtest) | 10:47 | |
| + plomtest (~plom@user/plomtest) | 10:47 | |
| - plomtest (QUIT: Remote host closed the connection) (~plom@user/plomtest) | 11:02 | |
| + Ar|stote|is (~linx@149.210.0.217) | 11:25 | |
| - S0rin (QUIT: Quit: WeeChat 3.8) (~S0rin@user/s0rin) | 11:48 | |
| + S0rin (~S0rin@user/s0rin) | 11:59 | |
| minute | btw i've had no more watchdog resets since the weekend firmware on pocket. | 12:12 |
| minute | i've just had a brownout soc reset on 30% battery though. but the cell voltages showed 3.5V. it's actually not recommended to discharge lipo further than 3.5V. so it's probably actually the gauge that's wrong, and this voltage should be considered 0% | 12:13 |
| minute | gnome says "31 minutes to fully charged", not sure if it was able to do that before the charge current fix in reform2_lpc driver | 12:14 |
| minute | ch: the battery gauge/monitor actually has a lot of weird settings we should look into, also what is considered "empty" | 12:15 |
| + paperManu (~paperManu@64.58.44.160) | 12:25 | |
| + paperManu_ (~paperManu@64.58.44.160) | 12:31 | |
| casparvitch | josch: in case you are around & want to chat about it I got the reform.debian.net cert fix working 🥳 | 12:31 |
| - paperManu (QUIT: Ping timeout: 245 seconds) (~paperManu@64.58.44.160) | 12:37 | |
| josch | casparvitch: i saw your merge request -- did you successfully test it? | 12:46 |
| josch | i'm having the children over in 15 minutes so not much time on the computer left for me :) | 12:46 |
| ch | minute: ack. do you have a good datasheet? the one i have was a bit elusive | 12:46 |
| ch | minute: do you think the brownout is firmware triggered or something else? | 12:46 |
| ch | minute: ah like 'lipo stopped supplying power'? | 12:47 |
| ch | i'll discharge mine and see what 3.5V is | 12:48 |
| minute | ch: not firmware triggered, i think it might be triggered by the MAX momentarily, or by the polyfuse (amps rising with lower voltage?), or even the built in safety in the battery cells | 12:48 |
| minute | ch: i think due to higher current at lower voltage, the voltage can dip even more momentarily, under load, and that trips some safety along the path for a moment | 12:49 |
| ch | ok, makes sense to me | 12:52 |
| + gustav2 (~gustav@c-78-82-53-184.bbcust.telenor.se) | 13:02 | |
| minute | ch: i'll tag a new release in pocket-reform for the firmware, ok? | 13:03 |
| ch | minute: sure! | 13:04 |
| - ex-parrot (QUIT: Ping timeout: 250 seconds) (~fincham@user/ex-parrot) | 13:07 | |
| + ex-parrot (~fincham@user/ex-parrot) | 13:11 | |
| minute | ch: lvfs upload job doesn't seem to be scheduled for tag pushes | 13:14 |
| ch | hmm | 13:14 |
| minute | now manually running for main... not sure if that'll pick up the tag? | 13:15 |
| minute | manually running pipeline, that is | 13:15 |
| ch | it will if HEAD matches the tag | 13:15 |
| casparvitch | josch: no worries no rush at all! Yes I have it all up and running! | 13:16 |
| casparvitch | josch: probably faster for you to fix it manually than read the MR to be honest ~ | 13:16 |
| + svp (~svp@2002:4f07:f0bd:0:69b1:b463:d245:e861) | 13:16 | |
| minute | ok, 20251001 is up @ embargo | 13:28 |
| minute | ch: it worked! | 13:28 |
| ch | nice | 13:29 |
| ch | should figure out why the tag push doesnt trigger it | 13:29 |
| ch | i made a note about this as https://source.mnt.re/reform/pocket-reform/-/issues/6 | 13:30 |
| - ex-parrot (QUIT: Ping timeout: 245 seconds) (~fincham@user/ex-parrot) | 13:54 | |
| + mjw (~mjw@gnu.wildebeest.org) | 13:57 | |
| + ex-parrot (~fincham@user/ex-parrot) | 13:58 | |
| minute | ch: takes really long for new lvfs embargo fw to show up in fwupdmgr even with refresh --force, can it be? | 14:03 |
| ch | yes | 14:03 |
| ch | i think 14:06 earliest | 14:03 |
| minute | ah ok! | 14:03 |
| ch | the website claims it takes until the full hour, but IME it takes up to 10min more | 14:04 |
| ch | re voltage: battery status now says 3.5V/3.6V and 69% | 14:05 |
| ch | so if 3.5V is 'empty', then that seems very off | 14:05 |
| ch | i see it in gnome-firmware now | 14:07 |
| ch | note that the "Refresh metadata" action in gnome-firmware doesnt seem to refresh the list you are currently looking at, so have to click away from the selected device if any | 14:07 |
| ch | upgraded both | 14:09 |
| - thelounge2784 (QUIT: Quit: The Lounge - https://thelounge.chat) (~thelounge@gidzit.org) | 14:17 | |
| minute | ch: right | 14:21 |
| minute | ch: also tested, updates worked mega smoothly | 14:22 |
| minute | ch: but i have disp v1, needs to be tested on disp v2 as well soon | 14:22 |
| minute | ch: i'd expect the brightness to change for a moment on disp v2? | 14:23 |
| minute | moved both fws to Testing | 14:24 |
| ch | good q. probably? | 14:25 |
| josch | PSA: copper M2 screws look reeeally cool, especially together with the rcore copper heatsink -- unfortunately, the copper is so soft that with screws this tiny, the head nearly immediately wears down when trying to fasten them -- was a pain to remove them again... at least they all came out in the end... | 14:34 |
| josch | (tried philips and hex heads) | 14:34 |
| + paperManu (~paperManu@64.58.44.160) | 14:35 | |
| gordon1 | getting bunch of there on 6.16.9 kernel http://0x0.st/KMZF.txt | 14:42 |
| gordon1 | *these | 14:43 |
| gordon1 | but don't have any of those on my rock5b+ so i assume it has something to do with reform patches | 14:43 |
| josch | gordon1: you switched out the rk3588 patch stack for the 6.17 version from collabora, yes? https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/tree/rockchip-v6.17?ref_type=heads | 14:47 |
| gordon1 | hmm, i think i just took patches from reform-debian-packages from patches6.16 dir | 14:48 |
| gordon1 | i don't have 6.17 kernel yet | 14:48 |
| josch | oh wait sorry i misread XD | 14:50 |
| josch | sorry, brain | 14:50 |
| josch | i am distracted right now and should not be reading chat, sorry | 14:50 |
| gordon1 | i didn't notice any actual problems yet btw, just those dmesg messages, everything works just fine | 14:51 |
| josch | but the mnt repo also has 6.16.9, so the same messages should show up | 14:51 |
| ch | minute: now at 3.5V/3.4V, 54%. gauge thinks 104min to empty | 14:51 |
| josch | let me quickly check | 14:51 |
| gordon1 | but there's a lot of them | 14:52 |
| gordon1 | $ dmesg | grep -c swiotlb | 14:52 |
| gordon1 | 574 | 14:52 |
| gordon1 | ah btw there is a kernel command line parameter that is appended by u-boot and which is not in my boot config: swiotlb=65535 | 14:53 |
| gordon1 | (which is btw is outrageous, especially because u-boot has no env!) | 14:54 |
| gordon1 | ah nvm it is appended as ${bootargs} so i can choose to not include it | 14:56 |
| josch | gordon1: i now have 6.16.9 on my rk3588 classic reform | 15:08 |
| josch | gordon1: when i grep dmesg for swiotlb then i only see one line printing my kernel command line which also includes swiotlb=65535 | 15:09 |
| josch | gordon1: the value indeed comes from u-boot as intended: https://source.mnt.re/reform/reform-rk3588-uboot/-/blob/main/mnt-reform2-rk3588-dsi_defconfig?ref_type=heads#L70 | 15:09 |
| gordon1 | josch: maybe play something using mpv? i got first message 600 seconds after the boot | 15:11 |
| josch | okay, i can do that later tonight | 15:11 |
| josch | gordon1: the value was added to the cmdline by this commit https://source.mnt.re/reform/reform-rk3588-uboot/-/commit/61d9fec91bc9f7ec29ac698ef0f72c464d175863 | 15:11 |
| gordon1 | i don't think i have anything besides the browser and mpv running today | 15:11 |
| josch | unfortunately the commit message does not have more context as to *why* swiotlb size was increased | 15:12 |
| josch | you have to ask minute who committed this a year ago | 15:12 |
| gordon1 | i mean i doubt that this is what causes this issue, 6.16.7 had same cmdline and produced no dmesg output | 15:13 |
| gordon1 | but still it would be interesting to know why it is there | 15:14 |
| - mjw (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 15:22 | |
| gordon1 | ok i increases swiotlb to 131072 but after the reboot i immediately got those messages back: http://0x0.st/KMNJ.txt | 15:29 |
| gordon1 | and it probably has nothing to do with number of slots | 15:29 |
| * Guest9684 -> mjw | 15:31 | |
| gordon1 | oh, that's probably that patch https://raw.githubusercontent.com/armbian/build/a691fe095b02823e60a076ec593b9fcec7723cc8/patch/kernel/archive/rockchip64-6.14/general-drm-rockchip-Set-dma-mask-to-64-bit.patch | 15:43 |
| gordon1 | not sure if i lost it somewhere or why did i applied it previously... | 15:44 |
| gordon1 | i also wonder now why i don't have those messages on my rock5b+ | 15:47 |
| gordon1 | but i can confirm that this patch fixes the message | 15:48 |
| + synnfynn (~synnfynn@user/synnfynn) | 15:55 | |
| - synnfynn (QUIT: Quit: ..) (~synnfynn@user/synnfynn) | 16:37 | |
| ch | minute: while fwupd.org now says (for stable) 'Remote will be signed with new firmware in 2 hours' i think it was effectively visible only on the next day. maybe more luck this time or with stable (tested 'testing' with josch and it took "forever") | 16:37 |
| minute | ch: meeh :3 | 16:39 |
| josch | yeah, it was only visible the next day, around eight hours later | 16:40 |
| minute | interesting, "last" shows me a "crash" | 16:41 |
| minute | i wonder how that is detected | 16:42 |
| minute | ok my cell voltages are really bad though | 16:45 |
| minute | ch: what are your cell voltages at like 80%? | 16:46 |
| minute | huh now they went _up_ to 3.7 during use | 16:47 |
| minute | from 3.5/3.6 | 16:47 |
| minute | ok they just change a lot with cpu load | 16:48 |
| minute | perhaps we just need more capacitores | 16:51 |
| minute | -e | 16:51 |
| minute | ah apparently this is an issue on LiPo with aged cells | 16:53 |
| minute | they have higher internal resistance, which makes the voltage sag | 16:53 |
| minute | in any case i'm writing down to make some capacitor experiments | 16:56 |
| + wstlr (~wstlr@5.13.169.217.in-addr.arpa) | 17:27 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 17:36 | |
| - wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa) | 18:14 | |
| + wstlr (~wstlr@5.13.169.217.in-addr.arpa) | 18:14 | |
| - wstlr (QUIT: Ping timeout: 240 seconds) (~wstlr@5.13.169.217.in-addr.arpa) | 18:19 | |
| + AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net) | 18:48 | |
| + wielaard (~mjw@gnu.wildebeest.org) | 19:12 | |
| - klardotsh (QUIT: Quit: zzz) (~klardotsh@2601:600:c900:9443::72f) | 19:33 | |
| * mjw -> Guest7042 | 19:45 | |
| - Guest7042 (QUIT: Killed (uranium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 19:45 | |
| * wielaard -> mjw | 19:45 | |
| + Guest7042 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 19:45 | |
| + wstlr (~wstlr@5.13.169.217.in-addr.arpa) | 20:53 | |
| ch | can look tomorrow re 80% | 21:59 |
| - wstlr (QUIT: Ping timeout: 264 seconds) (~wstlr@5.13.169.217.in-addr.arpa) | 22:05 | |
| - gustav2 (QUIT: Quit: Quit) (~gustav@c-78-82-53-184.bbcust.telenor.se) | 22:15 | |
| + wstlr (~wstlr@5.13.169.217.in-addr.arpa) | 22:16 | |
| aloo_shu | more pronounced with age but they're all going down during charge and up during discharge | 22:40 |
| aloo_shu | one of the reasons to collect battery data, you don't want a device to hit the power off threshold when the charger is plugged | 22:42 |
| aloo_shu | more tricky with exchangeable individual cells than with a monolithic 'smart battery'.I think it's a great design decision to have individual cells, but it's implying more work for predicting the pack's charge- & discharge curves | 22:45 |
| - wstlr (QUIT: Ping timeout: 245 seconds) (~wstlr@5.13.169.217.in-addr.arpa) | 23:20 | |
| + wstlr (~wstlr@5.13.169.217.in-addr.arpa) | 23:38 | |
| - AnimaInvicta (PART: !!unknown attribute: msg!!) (~AnimaInvi@88-120-179-216.subs.proxad.net) | 23:41 | |
| + LainIwakura (~LainIwaku@user/LainIwakura) | 23:43 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!