2024-01-16.log

- jacobk (QUIT: *.net *.split) (~quassel@64.189.201.150)00:03
- Kooda (QUIT: *.net *.split) (~kooda@natsu.upyum.com)00:03
- skipwich (QUIT: *.net *.split) (~skipwich@user/skipwich)00:03
- Asmadeus (QUIT: *.net *.split) (~asmadeus@M014009140128.v4.enabler.ne.jp)00:03
- bkeys (QUIT: *.net *.split) (~Thunderbi@45.134.140.153)00:03
- arminweigl (QUIT: *.net *.split) (~arminweig@sourcehut/user/arminweigl)00:03
- theesm (QUIT: *.net *.split) (~theesm@2a01:4f9:c011:adc3::)00:03
- amk (QUIT: *.net *.split) (~amk@user/amk)00:03
- anzu (QUIT: *.net *.split) (~anzu@melkki.cs.helsinki.fi)00:03
+ jacobk (~quassel@64.189.201.150)00:04
+ Kooda (~kooda@natsu.upyum.com)00:04
+ skipwich (~skipwich@user/skipwich)00:04
+ Asmadeus (~asmadeus@M014009140128.v4.enabler.ne.jp)00:04
+ bkeys (~Thunderbi@45.134.140.153)00:04
+ arminweigl (~arminweig@sourcehut/user/arminweigl)00:04
+ theesm (~theesm@2a01:4f9:c011:adc3::)00:04
+ amk (~amk@user/amk)00:04
+ anzu (~anzu@melkki.cs.helsinki.fi)00:04
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)00:05
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)00:13
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7231c0042f3e3fdc37e189d.dip0.t-ipconnect.de)00:22
+ eibachd (~eibachd@p200300dcf7231c009561482ee4669dc6.dip0.t-ipconnect.de)00:22
* mjw -> Guest767700:27
- Guest7677 (QUIT: Killed (platinum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)00:27
* wielaard -> mjw00:27
+ Guest7677 (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)00:27
- experemental (QUIT: Read error: error:0A000119:SSL routines::decryption failed or bad record mac) (~experemen@ch7.telecom24.link)00:45
+ xktr (~xktr@user/xktr)00:51
- murph_nj (QUIT: Quit: Leaving) (~murph@ool-457bb02e.dyn.optonline.net)00:57
+ murphnj (~murph@ool-457bb02e.dyn.optonline.net)00:58
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.8.17)01:07
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c009561482ee4669dc6.dip0.t-ipconnect.de)01:07
+ eibachd (~eibachd@p200300dcf7231c0021c7f06e5458b44c.dip0.t-ipconnect.de)01:08
+ Ar|stote|is (~linx@149.210.8.17)01:10
- cow321 (QUIT: Ping timeout: 256 seconds) (~deflated8@50.39.247.54)01:20
- xktr (QUIT: Ping timeout: 268 seconds) (~xktr@user/xktr)01:21
+ experemental (~experemen@us127.telecom24.link)01:22
- experemental (QUIT: Read error: error:0A000119:SSL routines::decryption failed or bad record mac) (~experemen@us127.telecom24.link)01:24
+ cow321 (~deflated8@50.39.247.54)01:27
+ xktr (~xktr@user/xktr)01:33
+ klardotsh (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net)01:53
+ reform22504 (~sam@210.205.160.108.in-addr.arpa)01:54
- reform22504 (QUIT: Remote host closed the connection) (~sam@210.205.160.108.in-addr.arpa)01:59
- mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)03:14
- nsc (QUIT: Ping timeout: 260 seconds) (~nicolas@78-49-142-46.pool.kielnet.net)03:29
+ nsc (~nicolas@149-96-142-46.pool.kielnet.net)03:30
- jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@64.189.201.150)03:34
- f_ (QUIT: Read error: Connection reset by peer) (~f_@fases/developer/funderscore)03:56
+ f_ (~f_@fases/developer/funderscore)03:58
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)04:49
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)04:52
- Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66)04:53
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)05:00
- hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu)05:15
+ hairu (m-uotkmd@user/hairu)05:18
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)05:18
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)06:20
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)06:35
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)06:36
- colinsane (QUIT: Client Quit) (~colinunin@97-113-159-4.tukw.qwest.net)06:39
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)06:41
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)07:02
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)07:05
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)07:29
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)07:31
- eibachd (QUIT: Ping timeout: 246 seconds) (~eibachd@p200300dcf7231c0021c7f06e5458b44c.dip0.t-ipconnect.de)08:05
+ eibachd (~eibachd@2a01:599:30a:6402:acdd:a075:ed09:2b45)08:06
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon)08:19
+ jagtalon (~quassel@user/jagtalon)08:20
- jagtalon (QUIT: Client Quit) (~quassel@user/jagtalon)08:20
+ jagtalon (~quassel@user/jagtalon)08:20
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@2a01:599:30a:6402:acdd:a075:ed09:2b45)08:31
- _nrb_ (QUIT: Remote host closed the connection) (~nrbnrb@2a01:4f8:10a:10a2:290::100)08:46
+ _nrb_ (~nrbnrb@2a01:4f8:10a:10a2:290::100)08:49
- Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66)09:07
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)09:24
+ eibachd (~eibachd@p200300dcf7231c00c5a820581c16822e.dip0.t-ipconnect.de)09:33
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66)10:05
+ chomwitt (~chomwitt@2a02:587:7a12:5900:1ac0:4dff:fedb:a3f1)10:15
+ experemental (~experemen@ch9.telecom24.link)10:29
- experemental (QUIT: Remote host closed the connection) (~experemen@ch9.telecom24.link)11:45
* Guest7677 -> mjw12:30
- XYZ (QUIT: Ping timeout: 268 seconds) (~XYZ@37-48-16-253.nat.epc.tmcz.cz)12:33
- klardotsh (QUIT: Ping timeout: 260 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net)13:04
- chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@2a02:587:7a12:5900:1ac0:4dff:fedb:a3f1)13:38
minutemeh, work pc (intel i9-9900) became unstable, will freeze completely every few hours. display stays on. does not react to hard reset, needs power cycle14:03
joschmay be a hardware issue with caps getting old14:07
minutevddgfx is wildly fluctuating hmm14:07
joschminute: i have new input for the mb25 charging issue14:07
minutesometimes 731mV14:07
minutethat doesn't sound normal14:07
joschwith the same cable and the same two usb-pd 20V adapters I can successfully charge my reform by changing the usb-c wall adapter14:08
joschit works with an apple usb-pd adapter which claims to be able to provide 4.7 A at 20 V14:08
minuteaha?14:09
joschso that's an adapter close to 100 W14:09
joschwith the other two i tried that claimed to be 60 W and 65 W i ran into issues14:09
joschit would still be nice to be able to configure the charging speed so that charging also works with my 60 W usb-pd adapters14:11
joschi'll purchase a 100 W usb-pd adapter but use your slow-charging patch until then14:11
joschjust tried a second cable as well with the same results14:16
joschso switching out the power supply for a beefier one helped while the other components (20V usb-pd adapters and cabling) stayed the same14:17
joschminute: did other buyers of mb25 report similar observations?14:18
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c00c5a820581c16822e.dip0.t-ipconnect.de)14:37
+ eibachd (~eibachd@2a01:599:325:f1ca:a9b6:945d:654a:1e4a)14:50
sevanminute: it could be the PSU is on its way out15:02
minutesevan: bios update and disabling power mgmt seemed to help for now... lets see if it is stable15:10
- sundog2062 (QUIT: Quit: The Lounge - https://thelounge.chat) (~sundog@reclaim.technology)15:24
+ sundog2062 (~sundog@reclaim.technology)15:25
- sundog2062 (QUIT: Client Quit) (~sundog@reclaim.technology)15:27
+ sundog2062 (~sundog@reclaim.technology)15:27
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon)16:01
+ jagtalon (~quassel@user/jagtalon)16:02
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon)16:14
+ jagtalon (~quassel@user/jagtalon)16:14
+ mark_ (~mjw@gnu.wildebeest.org)16:31
AbortRetryFailI haven't had a chance to test the slow-charge patch yet. :(16:33
AbortRetryFailDoes anyone know if there's battery longevity consequences to charging LiFePO4 in pulses?16:34
minuteidk... i'm not 100% comfortable with that patch yet also16:35
minutefor me the "delayed start" patch just works TM16:36
minutewithout any pulsing16:36
AbortRetryFailYeah, I have a feeling some kind of delayed/soft start would fix it 16:36
AbortRetryFailACTION still needs to try the capacitor on RNG/SS16:36
AbortRetryFailI just haven't had the Reform apart since I've been using it a lot16:37
minuteAbortRetryFail: yup, so i implemented that now in a patch and it made the hiccups go away for me on the stock power supply16:37
minuteAbortRetryFail: great to hear you're using it a lot :316:37
AbortRetryFailWhich hiccup?16:37
minuteAbortRetryFail: the issue that the power supply would stop supplying power probably because of overcurrent (but this is not 100% scientifically validated)16:38
AbortRetryFailThis totally replaced my old HP 16:38
minuteAbortRetryFail: what were the rough specs of old hp?16:38
AbortRetryFailHuh mine has not done that yet. 16:38
minuteAbortRetryFail: ah. you had a different charging issue?16:38
AbortRetryFailIts an EliteBook 745 II, AMD Kaveri of some sort I think16:38
AbortRetryFailI had the grounding/noise issues with teh Mean Well adapter and overcurrent shutoff with USB trigger cables.16:39
minuteAbortRetryFail: here's the (sketch quality) charge delayed start patch http://dump.mntmn.com/mb25_lpc_charge_delay.patch16:39
minuteAbortRetryFail: ah ok.16:39
minuteAbortRetryFail: you're on LS1028A IIRC? or a311d?16:39
AbortRetryFailNormally I charge my Reform off an Astron smps for radios 16:39
AbortRetryFailimx8mq 16:40
minuteoh ok wow16:40
AbortRetryFailTbh teh fact that the Reform has batteries that work and don't self-discharge to death in 3 days makes it 1000% more useful than the HP :)16:40
minutehaha nice16:42
minutejosch: i haven't heard of these mb25 issues other than from you i think, and from myself with the stock power supply (but only at home, maybe that one is a bit weak)16:43
minutethe easiest solution would be to spec the psu current to 100W... :D16:43
minute(or sth between 60 and 100, don't know yet what supplies exist)16:44
sknebeltoo bad about the RNG/SS issues (did your testing back then include if thats generally a problem or only when using it to shut down the charging entirely as the original design did? I had a search but didnt find anything officially documented about these issues)16:44
sknebel(like could you still use it for a "weak charger" mode even if the original use case didnt work?)16:45
AbortRetryFailin my experience it hasn't been the Reform shutting down charging, but the charger turning itself off.16:49
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:325:f1ca:a9b6:945d:654a:1e4a)16:55
+ eibachd (~eibachd@p200300dcf7231c00f41a976e3f6d3d45.dip0.t-ipconnect.de)16:56
minutesknebel: the RNG/SS input does not reliably work17:08
minutewe had someone with connections to the manufacturer look pretty intensely into it and then gave up on it17:08
- eibachd (QUIT: Ping timeout: 264 seconds) (~eibachd@p200300dcf7231c00f41a976e3f6d3d45.dip0.t-ipconnect.de)17:08
minutefor reform next i will switch to totally different power chips17:08
minutefrom TI17:08
minutebut those didn't exist back then17:09
+ eibachd (~eibachd@p200300dcf7231c00f24f365a5c6ee343.dip0.t-ipconnect.de)17:09
sknebelright, I was just curious if that was "its totally unreliable" or "it didnt work for what we wanted to do", but I take it it's the former 17:09
AbortRetryFaili'm curious of the same thing. The Reform is not the only device I have that uses that chip.17:09
minutesknebel: it messes with the voltage regulation 17:09
minuteon a % of the ICs/boards17:10
minutethis was a huge headache during first batch testing until i found the workaround with the diagonal resistor bodge... 17:10
minuteso i soldered that into 100s of motherboards17:10
sknebelright. yeah, if using it at all breaks the overall voltage regulation thats of course no good17:12
- mark_ (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org)17:29
minutewe just did some tests and we found out that CUI CMS-18132-18SP sounds a bit better than the PUI speakers we used so far in reform17:36
minutethese are kind of a drop in replacement... they're not ~substantially~ better but a little bit more depth17:37
+ robin (~robin@user/terpri)17:47
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)17:53
joschminute: apart from a more beefy power supply, another fix would be to switch out the resistor you talked about at some point. You said there was a resistor that controlled the charging speed.18:41
minutejosch: yeah, but that is non trivial for people who already have the new mb18:42
minutewe've shipped it in lots of reforms18:42
minutealso the value hasn't really changed from the first mb... so idk why this happens now18:42
- _nrb_ (QUIT: Remote host closed the connection) (~nrbnrb@2a01:4f8:10a:10a2:290::100)18:43
+ _nrb_ (~nrbnrb@2a01:4f8:10a:10a2:290::100)18:44
joschminute: i'm more thinking along the line of giving my board and the schematics to a person who knows what they are doing :)18:44
+ jacobk (~quassel@64.189.201.150)19:19
+ mark_ (~mjw@gnu.wildebeest.org)19:48
+ klardotsh (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net)19:51
* mjw -> Guest611320:05
- Guest6113 (QUIT: Killed (cadmium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:05
* mark_ -> mjw20:05
+ Guest6113 (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)20:05
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)20:33
joschminute: more mb25 charging news. I'm still running your delayed charging firmware. I have an external powerbank which has a 12 V output rated at 15 A. PLugging the reform into that resets the power bank and i have to plug out all cables and hold the "on" button for a few seconds to restart it.21:19
josch(that powerbank had no issues with mb 2.0)21:21
+ XYZ (~XYZ@78-80-16-182.customers.tmcz.cz)21:29
minutejosch: weird21:30
minutei wonder if something is up with the inrush limiter21:30
minutedo you have an usb-c power meter?21:32
minutetomorrow i'll get one21:32
- XYZ (QUIT: Quit: Leaving) (~XYZ@78-80-16-182.customers.tmcz.cz)21:33
+ chomwitt (~chomwitt@2a02:587:7a12:5900:1ac0:4dff:fedb:a3f1)21:33
+ XYZ (~XYZ@78-80-16-182.customers.tmcz.cz)21:37
vagrantcjosch: i'm eyeing up a new u-boot-menu upload, curious if you have any further thoughts or patches on https://bugs.debian.org/105381422:01
- XYZ (QUIT: Quit: Leaving) (~XYZ@78-80-16-182.customers.tmcz.cz)22:07
+ XYZ (~XYZ@78-80-16-182.customers.tmcz.cz)22:08
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon)22:09
+ jagtalon (~quassel@user/jagtalon)22:09
joschminute: i don't have one (yet)22:15
joschvagrantc: i have no further thoughts22:17
joschvagrantc: is the fix not to just call u-boot-menu in postinst if the last version is "" and if /boot/extlinux/extlinux.conf.bak does not exist?22:17
joschminute: do you have a module that you are fairly confident could help me diagnose what is going on?22:18
josch*model22:18
minutejosch: nope, not yet22:18
minutetomorrow i'll get my first one ever22:18
vagrantcjosch: maybe? :)22:20
joschvagrantc: okay, you'll get a patch :)22:22
vagrantcjosch: i'm nervous about this sort of thing as flash-kernel does that sort of thing poorly and would love to not have the same mistakes.22:24
- XYZ (QUIT: Read error: Connection timed out) (~XYZ@78-80-16-182.customers.tmcz.cz)22:24
joschvagrantc: what kind of problem do you fear could arise?22:24
vagrantcjosch: just probably scared, is all. :)22:26
AbortRetryFailminute: make sure you get a USB-C power meter that doesn't need bus power to operate. Mine is useless for this because it resets when the charger drops out.22:26
minuteugh22:27
minuteok22:27
AbortRetryFailI wonder if something weird happens during the negotiation/switch from 5V to 20V?22:27
AbortRetryFaillike maybe the LTC4020 is trying to boost up the 5V by pulling a hell of a lot of current then the voltage changes abruptly and there's a surge before things are able to adjust. 22:28
+ XYZ (~XYZ@78-80-16-182.customers.tmcz.cz)22:42
- XYZ (QUIT: Client Quit) (~XYZ@78-80-16-182.customers.tmcz.cz)22:42
joschvagrantc: https://salsa.debian.org/debian/u-boot-menu/-/merge_requests/1422:44
joschvagrantc: not tested yet. I don't have time right now. Maybe you can test it or wait until i find time. :)22:44
+ XYZ (~XYZ@78-80-16-182.customers.tmcz.cz)22:51
vagrantcjosch: thanks! will test23:10
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon)23:11
joschminute: seems hard to find a usb-c tester that allows more than 5 A23:12
+ jagtalon (~quassel@user/jagtalon)23:12
joschah no wait at 20 V, 5 A are more than enough23:15
- f_[xmpp] (QUIT: Ping timeout: 260 seconds) (fffdb90022@fases/developer/funderscore)23:16
- Twodisbetter (QUIT: Ping timeout: 268 seconds) (2cc0e4ea1c@irc.cheogram.com)23:16
Aardyou get 100W, if you need more you'd probably go for 50V devices23:16
vagrantccan't imagine it would draw more than 20v@3a=60w23:17
vagrantcor are the newer boards significantly more power hungry?23:17
joschvagrantc: i have two 60 W usb-c pd adapters that both fail to power the reform motherboard 2.523:19
joschvagrantc: it worked well with a 100 W usb-c adapter23:19
vagrantcwow23:21
joschthe problem becomes more pronounced the more empty the batteries are23:24
joschmy 60 W adapters are able to keep the reform powered when the batteries are 99% or 100%23:24
joschand with the charge-delay patch, lower values were possible23:24
joschbut charge levels below 80% will fail without a proper strong power source23:25
minutejosch: it is a bit puzzling that the polyfuse doesn't catch this23:34
minutei mean, the real fusy fuse23:34
minute2 of them actually23:34
minutebut that would also not be very nice if it would burn the fuses23:35
joschmaybe it's just a spike at the very beginning of charging and the fuse is too slow to react?23:38
joschwell, it's just idle speculation23:38
joschminute: i found some usb-c testers that are able to just measure voltage and current -- but somehow i feel it would make sense to be able to also detect volatage and/or current spikes?23:39
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:7a12:5900:1ac0:4dff:fedb:a3f1)23:40
joschi mean in my case it's probably going to show values for a second or less and then back to zero23:48

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