2025-02-06.log

+ jackhill_ (~jackhill@kalessin.dragonsnail.net)00:18
- jackhill (QUIT: Ping timeout: 252 seconds) (~jackhill@kalessin.dragonsnail.net)00:19
* jackhill_ -> jackhill00:19
* jackhill -> KM4MBG00:20
- LainExperiments (QUIT: Quit: Client closed) (~LainExper@user/LainExperiments)00:28
- xktr (QUIT: Ping timeout: 260 seconds) (~xktr@user/xktr)00:30
+ xktr (~xktr@user/xktr)00:31
+ aloo_shu_ (~aloo_shu@85.51.18.98)00:34
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.16.12)00:37
* aloo_shu_ -> aloo_shu00:37
+ mark_ (~mjw@gnu.wildebeest.org)00:46
- Ar|stote|is (QUIT: Read error: Connection reset by peer) (~linx@149.210.12.110)00:51
+ Ar|stote|is (~linx@149.210.28.124)00:58
- mtm (QUIT: Ping timeout: 260 seconds) (~textual@47.202.75.129)01:02
+ mtm (~textual@47.202.75.129)01:05
+ aloo_shu_ (~aloo_shu@85.51.18.117)01:07
- aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@85.51.18.98)01:10
* aloo_shu_ -> aloo_shu01:10
* robin__ -> robin01:10
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)01:13
+ robin_ (~robin@user/terpri)01:45
- robin (QUIT: Ping timeout: 272 seconds) (~robin@user/terpri)01:48
- cobra (QUIT: Ping timeout: 276 seconds) (~cobra@user/Cobra)02:07
+ aloo_shu_ (~aloo_shu@90.166.98.117)02:25
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@85.51.18.117)02:26
* aloo_shu_ -> aloo_shu02:26
- pocketenjoyer (QUIT: Ping timeout: 240 seconds) (~pocketenj@bras-base-toroon0964w-grc-08-142-198-81-33.dsl.bell.ca)02:39
+ cobra (~cobra@user/Cobra)02:41
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)02:47
- paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@107.159.71.33)03:18
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)03:35
+ aloo_shu_ (~aloo_shu@90.166.98.46)03:57
- aloo_shu (QUIT: Ping timeout: 268 seconds) (~aloo_shu@90.166.98.117)04:00
* aloo_shu_ -> aloo_shu04:00
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)04:07
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)04:08
+ pocketenjoyer (~pocketenj@bras-base-toroon0964w-grc-08-142-198-81-33.dsl.bell.ca)04:11
pocketenjoyerI'm trying to update, and searching for the error got me this page: https://community.mnt.re/t/issues-when-charging-with-portable-battery/2631/4 However picotool reboot -f doesn't work, nor does powering the machine down with the battery disconnect switch and trying again. Any suggestions please/04:50
pocketenjoyer?04:50
- L29Ah (QUIT: Ping timeout: 268 seconds) (~L29Ah@wikipedia/L29Ah)05:02
+ aloo_shu_ (~aloo_shu@85.51.17.247)05:15
- aloo_shu (QUIT: Ping timeout: 268 seconds) (~aloo_shu@90.166.98.46)05:18
* aloo_shu_ -> aloo_shu05:18
pocketenjoyerUpdating the firmware(s) and everything seems like a process everyone has to go through on first setting up a Pocket. is there a page / guide that covers all the pieces, please?05:25
- mark_ (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)05:54
+ aloo_shu_ (~aloo_shu@90.166.98.200)06:18
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@85.51.17.247)06:20
* aloo_shu_ -> aloo_shu06:20
+ aloo_shu_ (~aloo_shu@85.51.17.251)06:35
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.98.200)06:38
* aloo_shu_ -> aloo_shu06:38
+ aloo_shu_ (~aloo_shu@90.166.193.139)07:08
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.17.251)07:11
* aloo_shu_ -> aloo_shu07:11
- pocketenjoyer (QUIT: Ping timeout: 240 seconds) (~pocketenj@bras-base-toroon0964w-grc-08-142-198-81-33.dsl.bell.ca)07:24
+ aloo_shu_ (~aloo_shu@90.166.98.41)07:26
- aloo_shu (QUIT: Ping timeout: 245 seconds) (~aloo_shu@90.166.193.139)07:28
* aloo_shu_ -> aloo_shu07:28
+ chomwitt (~chomwitt@2a02:587:7a26:9800:1ac0:4dff:fedb:a3f1)08:21
- chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:587:7a26:9800:1ac0:4dff:fedb:a3f1)08:49
+ chomwitt (~chomwitt@2a02:587:7a26:9800:1ac0:4dff:fedb:a3f1)08:49
+ aloo_shu_ (~aloo_shu@90.166.98.214)08:58
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.98.41)09:01
* aloo_shu_ -> aloo_shu09:01
fricklersounds like the charging stuff is really a hot topic. the delta between my cells doesn't look to be shrinking yet, either, and the charging stops at about 30% and then they start slowly discharging, despite the charger still being connected and delivering power09:01
+ aloo_shu_ (~aloo_shu@85.51.16.182)09:31
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@90.166.98.214)09:34
* aloo_shu_ -> aloo_shu09:34
[tj]daily crowdsupply check gave an update for once:09:34
[tj]Estimated to ship:09:34
[tj]Feb 28, 202509:34
fricklerdifferent topic: trying to switch font sizes in xterm via ctrl-rmb menu doesn't seem to take any effect, maybe some font pkg missing?09:42
+ aloo_shu_ (~aloo_shu@90.166.98.165)09:49
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.16.182)09:51
* aloo_shu_ -> aloo_shu09:51
+ jacobk_ (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
+ colinsane (~colinunin@97-113-133-107.tukw.qwest.net)10:07
hramrachfrickler: it is not good idea to use xterm in general (no Wayland support), and it's not the default terminal. You can use it, and complain about deficiencies to the maintainer. You may need to customize the configuration for this to work - the default is some fixed bitmap font IIRC, and you would need a scalable font to change font size.10:12
- colinsane (QUIT: Ping timeout: 272 seconds) (~colinunin@97-113-133-107.tukw.qwest.net)10:13
fricklerhramrach: which terminal would you suggest instead?10:19
hramrachSomething that supports Wayland natively. IIRC the default used is foot but if you do not like this one there are surely many others10:20
hramrachhttps://github.com/natpen/awesome-wayland?tab=readme-ov-file#terminal-emulators10:26
chfoot is still the default afaik10:33
hramrachmlterm is an old school style terminal that can be also built for wayland but no idea if a wayland build is in debian10:35
+ aloo_shu_ (~aloo_shu@90.166.193.216)10:36
- aloo_shu (QUIT: Ping timeout: 260 seconds) (~aloo_shu@90.166.98.165)10:39
* aloo_shu_ -> aloo_shu10:40
gordon1there's also https://github.com/marchaesen/st-wl which isn't on the list10:43
fricklerthx, I simply wasn't aware of non-metric terminals before, but that works fine for me ;-)10:52
frickleranother observation regarding the battery: if I run sensors BAT0-*, the voltage matches the oled display, but I always get 0 A while charging. when discharging, the current reading are matching, too, up to rounding errors10:55
chhow much power is your charger delivering and at which voltage?10:58
chi think the reporting to the linux host is not always right10:58
gordon1i can assure you that st-wl is fully metric, uses no inches or pounds and uses M3 torx screws11:00
fricklerch: I'm not sure, the oled says a maximum (miniumum) of about -1.7A and about -0.6A when it stops charging and ~ 8.3V. I'm currently using the charger from my framework notebook, I'll need to find a microscope to read the specs printed on it11:02
chjosch: did you preemptively send beverages to paultag or are they just slowly making their progress through NEW?11:02
chfrickler: i think if you start a serial console on the pocket and connect it to ttyAMA0 you should see debug output with more details11:03
chit switching to 0.6A doesnt sound great11:03
joschch: all the reform packages in NEW have been processed, no?11:04
joschunfortunately i cannot make it to debconf this year to personally do the beverage donation11:04
chjosch: i was wondering what i need to do for my packages in NEW :) (also the qca firmware is still in new)11:04
joschoh no! i forgot about qca firmware11:04
joschno worries, it has only been there for 7 months11:05
chunsure how to read that ;)11:05
joschit will probably be part of Duke :)11:06
+ mark_ (~mjw@gnu.wildebeest.org)11:08
fricklerch: # ON AC CHG chg=2 mps_flt=00 input=19650mV@543mA charge=0mA discharge=0mA p=10.38W ttempty=6143min11:12
fricklerthat's while the oled says -0.538A11:13
+ L29Ah (~L29Ah@wikipedia/L29Ah)11:16
- aard (QUIT: Ping timeout: 276 seconds) (~bwachter@217.11.60.132)11:23
chhm yeah, the charger ic thinks its doing fast charging11:24
chbut at 0mA, its probably not :>11:24
chreplugging doesnt help?11:25
fricklerreplugging does help for a couple of minutes or so, I can give it a try and get you the new debug output then11:25
chyeah, maybe get the debug output from when it works and when it stops. maybe there's also something interesting at the transition point11:26
fricklermeh, it scrolled away too fast when unplugged. replugged I now have: # ON AC CHG chg=2 mps_flt=00 input=19350mV@1556mA charge=1887mA discharge=0mA p=15.00W ttempty=6143min11:28
chchg= indicates the CHG_STAT field in REG13h ('Status Register'), and 10: Fast charging11:32
chso it still does fast charging11:32
ch'well'11:32
chmaybe you'll see mps_flt= change when it stops charging11:34
chthat'd be interesting11:34
fricklerch: here's the full log from unplug + replug + stopping charging at the end (only grep -v keyboard on the serial log) https://paste.opendev.org/show/b1aYIEVYdqh7t7fBRWxo/11:36
ch:(11:37
fricklerfyi the cell voltages in the oled are 3.5/3.9 when unplugged and 3.7/4.1 when plugged11:39
frickleralso the oled and dock agree about 25% charged, that also can't be seen in the debug log11:49
- buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org)11:50
fricklerch: are you sad about my charger or your software (iiuc you did the pd stuff)?11:50
chfrickler: both!11:50
frickleralso I'd have a dell xps charger to compare against ... unless that raises more sadness11:50
+ buckket (~buckket@vps.buckket.org)11:51
chyou can try changing the powerbrick, but i think it wont make a lot of difference11:51
chinput=19350mV@1556mA is pretty optimal11:51
- chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:587:7a26:9800:1ac0:4dff:fedb:a3f1)11:54
chhttps://source.mnt.re/reform/pocket-reform/-/merge_requests/32 if you can easily try this, it might be informative11:56
hramrachit says it's 60W charger on the framework web site11:57
hramrachI suppose I could try this charger as well, should have it somewhere11:58
hramrachis that supposed to produce firmware files eventually or is a local build needed?12:00
chyeah not sure whats up with the CI job, it should just build12:02
chah except now nothing builds because pico-sdk is uninstallable12:05
chsigh12:05
joschch: that job does not install pico-sdk though -- is that not the missing rebuild of src:libstdc++-arm-none-eabi aka #1055160?12:07
joschit specifically clones https://github.com/raspberrypi/pico-sdk12:08
chdoes it?12:08
chanyway, yes the error points to direct install of libstdc++-arm-none-eabi12:08
chand just because it clones sth doesnt mean it uses it :P12:08
joschtrue, but it also does not install pico-sdk12:09
chanyway, all moot12:10
+ aloo_shu_ (~aloo_shu@90.166.99.116)12:24
- aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@90.166.193.216)12:27
* aloo_shu_ -> aloo_shu12:27
+ paperManu (~paperManu@107.159.71.33)12:39
- mark_ (QUIT: Ping timeout: 246 seconds) (~mjw@gnu.wildebeest.org)12:40
+ chomwitt (~chomwitt@2a02:587:7a26:9800:1ac0:4dff:fedb:a3f1)12:40
+ aloo_shu_ (~aloo_shu@85.51.17.67)12:42
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@90.166.99.116)12:44
* aloo_shu_ -> aloo_shu12:44
+ mark_ (~mjw@gnu.wildebeest.org)12:44
+ gustav28 (~gustav@c-92-32-81-6.bbcust.telenor.se)13:02
- mtm (QUIT: Ping timeout: 272 seconds) (~textual@47.202.75.129)13:04
+ mtm (~textual@47.202.75.129)13:05
joschminute: plomlompom's changes from MR 107 and added a --force option to reform-setup-encrypted-nvme and reform-boot-config, so you can now run this to avoid any user interaction:13:07
joschecho my_luks_passphrase | sudo reform-setup-encrypted-nvme --force13:07
joschi think this is what you wanted for the reform-setup-wizard13:07
minutejosch: oh great, thank you13:19
joschprops go to BoostisBetter for his imx8mq classic reform13:21
joschwithout it, changing scripts like reform-setup-encrypted-nvme and reform-boot-config is *very* frustrating and slow13:21
+ aloo_shu_ (~aloo_shu@90.166.193.64)13:30
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.17.67)13:32
* aloo_shu_ -> aloo_shu13:32
- L29Ah (PART: !!unknown attribute: msg!!) (~L29Ah@wikipedia/L29Ah)13:50
+ L29Ah (~L29Ah@wikipedia/L29Ah)13:50
- L29Ah (PART: !!unknown attribute: msg!!) (~L29Ah@wikipedia/L29Ah)13:51
+ L29Ah (~L29Ah@wikipedia/L29Ah)13:51
+ aloo_shu_ (~aloo_shu@85.51.18.99)14:02
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@90.166.193.64)14:05
* aloo_shu_ -> aloo_shu14:05
- paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@107.159.71.33)14:14
- mark_ (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org)14:17
- wickedshell (QUIT: Ping timeout: 276 seconds) (~wickedshe@2601:8c0:800:4baa:f22d:cf1d:4ecc:80c5)14:39
- L29Ah (PART: !!unknown attribute: msg!!) (~L29Ah@wikipedia/L29Ah)15:03
+ aloo_shu_ (~aloo_shu@85.51.18.29)15:05
- aloo_shu (QUIT: Ping timeout: 245 seconds) (~aloo_shu@85.51.18.99)15:07
* aloo_shu_ -> aloo_shu15:07
fricklerhmm, seems it was a questionable idea to try and build the libstdc++ locally ... going for half an hour and still at the auto_configure stage ...15:24
+ L29Ah (~L29Ah@wikipedia/L29Ah)15:29
joschfrickler: be careful, the package takes 22 GB to build and 2.5 hours to build on the Debian buildds15:51
joschthe resulting binaries are also multiple GB large15:52
joschminute: if you want the libstdc++-arm-none-eabi issue solved quickly, then we can just make use of the MNT mirror15:52
joschbut we never built a package that large on the gitlab CI15:52
joschminute: should i try?15:53
minutejosch: i think it's not that mega urgent... what do you think is the timeline for resolving it in debian repos?15:57
joschminute: maintainer said yesterday "less than a week, probably only a few days"15:58
minutejosch: sounds good15:58
fricklerjosch: the only thing I'm afraid of is that it might fry something from overheating, not sure how long I'll wait for progress before I give up ;)16:04
+ aloo_shu_ (~aloo_shu@85.51.17.5)16:08
joschfrickler: as far as i know, there has not yet been any frying because the cpu was kept very busy for a long while16:08
- aloo_shu (QUIT: Ping timeout: 268 seconds) (~aloo_shu@85.51.18.29)16:11
* aloo_shu_ -> aloo_shu16:11
+ aloo_shu_ (~aloo_shu@255.pool85-51-18.dynamic.orange.es)16:40
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.17.5)16:43
* aloo_shu_ -> aloo_shu16:43
+ wickedshell (~wickedshe@2601:8c0:800:4baa:1d38:4930:7016:5ea1)16:44
- ericsfraga (QUIT: Remote host closed the connection) (~user@2a00:23cc:b43d:4b00::3ce)17:00
+ aloo_shu_ (~aloo_shu@85.51.16.92)17:13
- aloo_shu (QUIT: Ping timeout: 245 seconds) (~aloo_shu@255.pool85-51-18.dynamic.orange.es)17:16
* aloo_shu_ -> aloo_shu17:16
+ ericsfraga (~user@2a00:23cc:b43d:4b00::3ce)17:20
+ aloo_shu_ (~aloo_shu@85.51.18.109)17:46
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.16.92)17:49
* aloo_shu_ -> aloo_shu17:49
minutein case you're curious about a long-standing bug in our shop system https://github.com/friendlycart/solidus_configurable_kits/issues/817:55
minutethis took a few hours to figure out...17:56
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:7a26:9800:1ac0:4dff:fedb:a3f1)18:02
+ mark_ (~mjw@gnu.wildebeest.org)18:09
- midfavila (QUIT: Quit: Lost terminal) (midfavila@freeshell.org)18:18
- murphnj (QUIT: Quit: Lost terminal) (murph@freeshell.org)18:18
choh wow18:19
joscha reminder to never install software you cannot fix or to only install software without bugs18:21
joschoh wait...18:21
minute:D18:34
jfredoh my!18:36
* jacobk_ -> jacobk18:42
- mark_ (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)18:58
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)19:04
+ mark_ (~mjw@gnu.wildebeest.org)19:28
gordon1good point, we all need to get rid of browsers then19:33
+ chomwitt (~chomwitt@2a02:587:7a26:9800:1ac0:4dff:fedb:a3f1)19:43
joschgordon1: count me in!19:45
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)19:53
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)19:53
* mark_ -> mjw19:56
+ aloo_shu_ (~aloo_shu@85.51.18.165)20:03
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.109)20:06
* aloo_shu_ -> aloo_shu20:06
BoostisBetterminute: just wanted to let you know that if you haven't already sent me the replacement keyboard for the pocket that you can hold off on it. It seems moving to Debian stable has resolved a bunch of the issues, and the hooks for resetting the kb have basically got the keyboard more stable. I am not really having issues and when I do it is possible to get the kb back. 20:58
+ pocketenjoyer (~pocketenj@142.198.81.33)21:32
+ aloo_shu_ (~aloo_shu@90.166.193.102)21:36
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.165)21:39
* aloo_shu_ -> aloo_shu21:39
+ nybble (~sprang@user/csprng)21:41
- pocketenjoyer (QUIT: Quit: Client closed) (~pocketenj@142.198.81.33)21:46
- Zaba (QUIT: Ping timeout: 252 seconds) (80b9b4b35e@2a03:6000:1812:100::116)21:53
- larme (QUIT: Ping timeout: 276 seconds) (22544863b6@user/larme)21:53
+ Zaba (80b9b4b35e@2a03:6000:1812:100::116)21:54
+ larme (22544863b6@user/larme)21:58
+ aloo_shu_ (~aloo_shu@85.51.17.75)22:09
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@90.166.193.102)22:11
* aloo_shu_ -> aloo_shu22:11
- gustav28 (QUIT: Quit: Quit) (~gustav@c-92-32-81-6.bbcust.telenor.se)22:15
- mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)22:23
+ mjw (~mjw@gnu.wildebeest.org)22:30
- bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@38-146-94-247.echocast.zone)22:31
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)22:51
+ colinsane (~colinunin@97-113-75-98.tukw.qwest.net)22:56
+ aloo_shu_ (~aloo_shu@90.166.99.105)22:57
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@85.51.17.75)22:58
* aloo_shu_ -> aloo_shu22:58
+ Guest43 (~Guest43@86-90-49-229.fixed.kpn.net)22:59
fricklerch: I managed to build your new sysctl fw now, but I'm a bit worried since mine seems to have a different usb id than what update-sysctl-firmware.sh expects? I have 1209:6d07 and not 2e8a:000a?23:01
minutefrickler: 1209:6d07 is the "new" good one that is actually reserved for us. the script expected the old one before we rolled out fwupd support23:06
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:10
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:10
fricklerminute: ok, I amended the script, but now I get: No accessible RP2040/RP2350 device in BOOTSEL mode was found at bus 2, address 2.23:10
minutefrickler: ah yes. picotool can't recognize this vid/pid. you can use reform-mcu-tool to put the sysctl in bootsel mode.23:12
minute(it should be installed)23:12
joschit is if you have reform-tools >= 1.6323:17
fricklerand in bootsel mode it now has the old id, but I can't change the script anymore, since it has made the u sysrq already. so I ended up calling picotool manually. didn't shut the system down though as it has promised?23:19
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:21
frickleralso no change in the charger log, still no fault to be seen on the transition to no charging23:21
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:21
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:31
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:31
- GNUmoon (QUIT: Ping timeout: 264 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)23:41
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:42
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:42
- Guest43 (QUIT: Quit: Client closed) (~Guest43@86-90-49-229.fixed.kpn.net)23:43
fricklerch: so I guess we'll need to come up with some further debugging ideas. I'm also wondering how confident you are that this is a software issue and not possibly something with (one of) the cells or the charger board. charging does seem to work fine for most others after all. or does it?23:44
chfrickler: shut down only happens if you upgrade from a very old sysctl firmware, so its good it didnt!23:46
chfrickler: i'm not confident at all its a software issue. it might very well be a problem with the cells or the charger board. my hope was that the new sw would show an mps_flt, indicating some feedback from the charger board23:46
chfrickler: but if it doesnt... i'd try a few more plug cycles to see if you can get it to charge to more than whatever % you are at maximum now23:47
chcould also read the charger ic datasheet if there's some relevant (default) setting that could explain this behaviour23:47
+ paperManu (~paperManu@107.159.71.33)23:49
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)23:52
+ bkeys (~Thunderbi@50.96.248.167)23:53
fricklerhmm, it seems that after doing a reboot, the sysctl somehow got stuck, the display went dark and the oled showed "T" instead of the new version in the system status. I did a full power-off which seems to have recovered it. I'll try some more plug cycles tomorrow and let you know the result23:56

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