2023-12-13.log

- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)00:33
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)00:43
- eibachd (QUIT: Ping timeout: 245 seconds) (~eibachd@p200300dcf7231c008372b1ba5110887d.dip0.t-ipconnect.de)00:52
+ eibachd (~eibachd@p200300dcf7231c00cdab3831c9a3fcd1.dip0.t-ipconnect.de)00:53
- mtm (QUIT: Ping timeout: 260 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)01:04
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7231c00cdab3831c9a3fcd1.dip0.t-ipconnect.de)01:23
+ eibachd (~eibachd@p200300dcf7231c00cd9b3485f6b1f003.dip0.t-ipconnect.de)01:23
- nsc (QUIT: Ping timeout: 268 seconds) (~nicolas@154-121-142-46.pool.kielnet.net)03:08
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)03:10
+ nsc (~nicolas@i5E86127F.versanet.de)03:10
+ sevan (~sevan@user/venture37)03:12
- S0rin (QUIT: Ping timeout: 255 seconds) (~S0rin@user/s0rin)04:31
+ S0rin (~S0rin@user/s0rin)04:32
- jn (QUIT: Ping timeout: 256 seconds) (~quassel@user/jn/x-3390946)04:44
+ jn (~quassel@2001-4dd4-9317-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)04:44
- jn (QUIT: Changing host) (~quassel@2001-4dd4-9317-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de)04:44
+ jn (~quassel@user/jn/x-3390946)04:44
- jacobk (QUIT: Ping timeout: 268 seconds) (~quassel@utdpat241106.utdallas.edu)05:57
+ skipwich_ (~skipwich@user/skipwich)06:45
- skipwich (QUIT: Ping timeout: 252 seconds) (~skipwich@user/skipwich)06:46
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c00cd9b3485f6b1f003.dip0.t-ipconnect.de)07:16
+ eibachd (~eibachd@2a01:599:317:ed92:8011:393d:7348:549b)07:16
joschBoostisbetter: 6.6 is only in experimental right now so you should not have anything higher than 6.507:21
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin)07:48
+ S0rin (~S0rin@user/s0rin)08:14
- S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin)08:19
+ S0rin (~S0rin@user/s0rin)09:14
- mesaoptimizer (PART: !!unknown attribute: msg!!) (~mesaoptim@user/PapuaHardyNet)09:17
- S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin)09:19
Boostisbetterjosch: yeah I wasn't that worried really, but good to know. 09:31
+ S0rin (~S0rin@user/s0rin)09:44
- S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin)09:50
+ mjw (~mjw@gnu.wildebeest.org)09:53
f_josch: (off-topic) I run 6.6.4..does it have the issue?10:04
joschf_: I'm not quite sure what ext4 issue Boostisbetter was talking about. When searching online i only found a possible data corruption bug in 6.1.10:05
Boostisbetterjosch: sorry I was mistaken. https://twitter.com/debian/status/1733559140914749547 10:09
Boostisbetterjosch: it is about 6.1 as you said. I misread. 10:09
- pandora (QUIT: Quit: Connection closed for inactivity) (uid585533@id-585533.ilkley.irccloud.com)10:10
+ S0rin (~S0rin@user/s0rin)10:15
joschokay, that issue is apparently only affecting 6.1.64 and 6.1.6 which are the only ones that have commit 91562895f803 but not commit 936e114a245b and the corruption only happens with writes that are done with O_DIRECT so the "normal" case is not affected.10:17
joschsource: https://lore.kernel.org/stable/20231205122122.dfhhoaswsfscuhc3@quack3/10:18
- mjw (QUIT: Killed (NickServ (GHOST command used by wielaard!~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae))) (~mjw@gnu.wildebeest.org)10:35
* wielaard -> mjw10:35
- S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin)10:40
Boostisbetterjosch: that is good to hear, I didn't notice any issue, and I wasn't using 6.1 for very long at all to begin with. 10:42
BoostisbetterActually I think the Librem 5 from Purism is still on the 6.1 kernel. 10:42
+ S0rin (~S0rin@user/s0rin)10:45
- S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin)10:50
joschBoostisbetter: the purism 6.1 kernel is 6.1.66 which does not have the issue anymore11:31
Boostisbetterjosch: thanks! 11:32
+ S0rin (~S0rin@user/s0rin)11:46
- S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin)11:51
+ S0rin (~S0rin@user/s0rin)12:16
- S0rin (QUIT: Ping timeout: 276 seconds) (~S0rin@user/s0rin)12:22
- XYZ (QUIT: Remote host closed the connection) (~XYZ@37-48-11-13.nat.epc.tmcz.cz)12:27
vkoskivAnother absolute banger of a recommendation by youtube: https://youtu.be/5itQC-Ux62g12:44
vkoskivOff-topic, but I feel that a good portion of people here might enjoy it :]12:44
+ S0rin (~S0rin@user/s0rin)12:46
+ XYZ (~XYZ@37-48-11-13.nat.epc.tmcz.cz)12:48
- S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@user/s0rin)12:52
- XYZ (QUIT: Ping timeout: 256 seconds) (~XYZ@37-48-11-13.nat.epc.tmcz.cz)12:58
- colinsane (QUIT: Ping timeout: 264 seconds) (~colinunin@97-113-159-4.tukw.qwest.net)13:01
- mtm (QUIT: Ping timeout: 246 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)13:02
+ XYZ (~XYZ@37-48-34-95.nat.epc.tmcz.cz)13:11
+ S0rin (~S0rin@user/s0rin)13:17
- XYZ (QUIT: Ping timeout: 260 seconds) (~XYZ@37-48-34-95.nat.epc.tmcz.cz)13:40
+ mark_ (~mjw@gnu.wildebeest.org)13:51
+ XYZ (~XYZ@89-24-48-81.nat.epc.tmcz.cz)13:52
- S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin)14:28
+ S0rin (~S0rin@user/s0rin)14:48
abortretryfaillol, i like the cans of WD-40 and Deoxit in the background14:53
- S0rin (QUIT: Ping timeout: 264 seconds) (~S0rin@user/s0rin)14:53
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)15:08
+ S0rin (~S0rin@user/s0rin)15:18
- qbit (QUIT: Remote host closed the connection) (~qbit@mail.suah.dev)15:36
+ qbit (~qbit@mail.suah.dev)15:42
+ chaseadam (~achasen@2600:1700:e70:7f9f:cc6c:d0f5:78a1:52c0)16:25
chaseadamtrying to grok the battery management system on my Reform2 "R3" motherboard and was wondering why the discharge resistors are so low compared to the Application notes written for the LTC6803-4 (33Ω vs 4.7Ω)? Seems this necessitates the use of "cooldown" as I calculated the resistor heat dissipation as 3W vs 500mW?16:31
chaseadamminute: can you confirm the compromise of the R3 fix is that the batteries receive "full current" when "balancing"? I noticed the R3 fix was (primarily?) related to a "no batteries" scenario. I presume this fix is still recommended even in an "always battery" scenario due to the benefits listed in the post https://community.mnt.re/t/mnt-reform-r-2-motherboard-update-2021-04-19/177?16:41
- lexik (QUIT: Ping timeout: 260 seconds) (~lexik@93.185.97.209)16:47
+ lexik (~lexik@93.185.97.218)16:47
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)17:08
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:317:ed92:8011:393d:7348:549b)17:52
+ eibachd (~eibachd@p200300dcf7231c00af0084dfb9e57411.dip0.t-ipconnect.de)17:52
joschminute: in your recent mastodon post you suggest using imx8mplus with the big reform -- but a while ago you said you don't want to support that case to reduce complexity. Should we build big Reform system images for the imx8mplus? Or maybe at least provide the dtb and add a switch to reform-sytem-image that allows for building for non-default configurations?17:55
- eibachd (QUIT: Ping timeout: 246 seconds) (~eibachd@p200300dcf7231c00af0084dfb9e57411.dip0.t-ipconnect.de)17:57
+ eibachd (~eibachd@p200300dcf7231c000576eb0ce7ca59f4.dip0.t-ipconnect.de)17:59
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)18:00
minutejosch: it's mostly something for the future. i'm not sure if many people will actually do this18:03
minutechaseadam: R3 fix primarily works around a ltc4020 bug/instability that was leading to many boards not working at all or producing excess ripple18:05
minutechaseadam: we also switched to higher than 4.7 ohms resistors for balancing later, i think 10? 33 is just very slow18:06
- XYZ (QUIT: Read error: Connection reset by peer) (~XYZ@89-24-48-81.nat.epc.tmcz.cz)18:39
+ XYZ (~XYZ@89-24-48-81.nat.epc.tmcz.cz)18:54
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c000576eb0ce7ca59f4.dip0.t-ipconnect.de)19:03
+ eibachd (~eibachd@p200300dcf7231c00ca6a980ae23e5b09.dip0.t-ipconnect.de)19:05
+ jacobk (~quassel@utdpat241106.utdallas.edu)19:27
+ ajr (uid609314@user/ajr)19:52
- jacobk (QUIT: Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@utdpat241106.utdallas.edu)20:00
- XYZ (QUIT: Remote host closed the connection) (~XYZ@89-24-48-81.nat.epc.tmcz.cz)20:05
+ XYZ (~XYZ@89-24-48-81.nat.epc.tmcz.cz)20:10
+ jacobk (~quassel@utdpat241106.utdallas.edu)20:19
- V (QUIT: Ping timeout: 255 seconds) (~v@ircpuzzles/2022/april/winner/V)20:31
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:33
+ mjw (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:33
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:34
* mark_ -> mjw20:34
+ mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:34
+ V (~v@ircpuzzles/2022/april/winner/V)20:36
- S0rin (QUIT: Ping timeout: 245 seconds) (~S0rin@user/s0rin)20:55
+ S0rin (~S0rin@user/s0rin)20:57
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)21:08
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)21:09
- XYZ (QUIT: Remote host closed the connection) (~XYZ@89-24-48-81.nat.epc.tmcz.cz)23:30

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