2022-04-16.log

- chomwitt (QUIT: Remote host closed the connection) (~chomwitt@2a02:587:dc0f:ad00:3949:ab21:9834:ebc)00:00
mrusalright cool, then let's go for RHEL00:40
kfx_E: well, you know how the old saying goes.  resistance is futile.00:43
_Ekfx: ironically so, since I think R53's melting shorted it to ground00:44
_Ealmost tempted to clean up the melted solder and reseat it01:30
_Eit'd be interesting to see what still works -- if anything does01:33
ex-parrot_E: careful, I think that moved resistor might be the intentional board fix on early units?01:35
ex-parrotlet me compare with mine01:35
ex-parrotyes, confirmed, that R53 should be moved like that01:36
ex-parrotand was likely done by minute's own hand during manufacturing :)01:36
ex-parrotit would be pretty amazing if the CPU usage alone melted solder01:37
_Eex-parrot: what, not even a little yellow wire for the trouble?01:39
ex-parrotit had to be disconnected and moved01:40
ex-parrotso I'm not even sure it could be done with a bodge wire01:41
_Eall I know is a reliable IR thermometer clocked at least one part of the board at 210°F01:41
ex-parrotare you running from battery?01:41
_Eit was on battery for a while, but I plugged it in and nothing good has happened since01:42
ex-parrotthere is a known quirk with the balancing resistors where if e.g. a battery becomes disconnected during operation they can get very hot and burn up01:42
ex-parrotdue to an undesirable current path01:42
ex-parrotI've never managed to get the CPU on my unit above about 70 degrees even working it very hard intentionally, though I suppose a hundred degrees might be possible01:42
_Ethe 210°F reading was, as best I can tell, the right side battery connector01:43
ex-parrotthat's around where the balancing resistors are01:44
ex-parrotso I'd say it was a power issue 01:44
_Evarious parts of the board near the LPC and the battery controller were in the mid-to-upper 150°s01:44
ex-parrotthe balancing resistors are those bigger 4.7 ohm ones in a row near the board edge01:45
ex-parrota few people have reported instances of them overheating and cooking in some situations01:45
_EI don't recall them being terribly hot, but I can check the resistance later01:46
ex-parrotminute finally identified why recently, basically if a battery is removed the charge / discharge current can be directed through one of them, which exceeds their rating01:46
ex-parrot(someone correct me if I'm wrong)01:46
_Ethe batteries were solidly connected during the incident01:46
_Eat least physically01:46
ex-parrotyeah, hard to say really, I'm just guessing at the most likely thing to get hot over in that area of the board01:47
_Ecan the board run off just AC?01:47
_Eno batteries present, just the power adapter01:47
ex-parrotyes but there may be conditions you have to fulfill first that I don't remember, so probably best to check with minute or someone more familiar with that operation01:48
ex-parrotis your LPC still going, e.g. you can hit circle and get the little menu? you could check the cell voltages there if so01:48
_Eit wasn't at the time, but I could absolutely be convinced there was a thermal limit tripped01:49
ex-parrotI'm not sure there is much that would implement a thermal limit per se01:49
_EI would guess the LPC has an internal one?01:50
_EI saw mention of one on a datasheet recently, but I can't say if it was the LPC's01:50
ex-parrotthe LPC is just a microcontroller01:50
_Emust have been the iMX8's sheet then01:51
_Eyeah, that was it01:52
ex-parrotyeah the iMX has a thermal sensor on it01:52
_Eyeah, it was 5.4 in the manual01:53
_Ethat's definitely what I was looking at01:53
- mtm (QUIT: Ping timeout: 246 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)02:02
mruswait, so that means we can't blame Feodra on melting solder and burning PCBs?02:16
ex-parrotI'm skeptical 02:16
mrus:[02:16
_Ewell, I took it somewhere less flammable02:24
_Eit was back up to an unreasonably high temp almost as soon as I plugged the battery packs back in02:24
_Eup past 100°F within 30s02:25
_Ewith the laptop off02:25
ex-parrotright, sounds like you've got a fault in the balancing circuitry02:26
_Eby the time I got the plugs out it had already started emitting That Smell™02:26
ex-parrotyou can probably dribble some isopropyl alcohol on the board while cold02:26
ex-parrotto see which components are heating up02:26
ex-parrot(e.g. it'll evaporate fastest off the hot bits)02:27
ex-parrotare you using the stock batteries?02:27
_Eyep02:27
_Estraight from CS02:27
ex-parrotcool, that's a good start02:27
ex-parrotyou could check that they are all delivering a reasoable voltage in to the cell holders02:28
_Esure, one sec02:29
_Eright pack is all between 3.2-3.302:31
ex-parrotcool, in that case I'm out of good ideas for what might be heating up. I'd suggest try measuring it with some isopropyl alcohol if you can02:31
_Eleft pack is all 3.302:31
_EI have a thermocouple for my meter, but I can't exactly get the batteries unplugged quickly if something starts going very wrong02:32
_Eunless someone has an idea for speedy battery removal02:36
_Ecorrection: I found a pair of needle nose pliers02:39
_Ewhich is probably as good as I can hope to get02:39
_EI would like the record to state that this is a bad idea02:39
ex-parrotyeah, don't pull out individual cells 02:45
ex-parrotwhile the machine is on02:45
ex-parrotor you can burn the balancing circuitry02:45
_Eok no that's not a good idea, the batright connector was back up past 140°F within 10 seconds of being plugged back in02:45
_Efor reference, the ambient temp is roughly 66°F at the moment02:46
_Eex-parrot: I'm only using the connectors, not messing with cells02:47
ex-parrotok v good02:47
ex-parrotif the connector itself is getting hot02:47
ex-parrotI assume something is shorted02:47
_Eno obvious debris on the board02:48
_Egonna take off the peripherals and try again02:49
ex-parrot_b02:51
- alex4nder (QUIT: Ping timeout: 250 seconds) (~alexander@ip98-171-191-229.sb.sd.cox.net)02:55
_Eno change03:00
_Ebatright was up to 170°F before I got it out03:00
+ alex4nder (~alexander@ip98-171-191-229.sb.sd.cox.net)03:01
_Ethe resistors were also hot, but not as... violently so03:01
ex-parrotweird03:01
_EI wonder if it happens with only one battery pack?03:01
_E...it still happens with F2 gone03:06
_Ethat's somewhat unexpected03:09
ex-parrotthat is weirder!03:10
ex-parrotmaybe the connector itself is damaged in some way?03:10
_Ecould be?03:10
_EI don't know why it would have happened spontaneously like that03:10
ex-parrotas I've said, seems weird :P03:11
ex-parrothopefully someone with more experience on that bit of the hardware will show up and have some more ideas about trbouleshooting it03:11
_EI'm gonna look over the schematics a bit03:11
_Eunsurprisingly, that didn't help one bit03:39
_Ethough I am somewhat shocked at how little of a role F2 plays03:39
_EI thought it would have stood in the way of everything, battery control circuitry included03:40
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)04:08
+ xktr (~xktr@108.62.5.153)04:17
- GNUmoon (QUIT: Ping timeout: 240 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)04:30
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)04:42
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:40)06:03
- adjtm (QUIT: Quit: Leaving) (~adjtm@53.red-83-56-237.dynamicip.rima-tde.net)10:08
+ Christoph_ (~Christoph@p54bf6fc1.dip0.t-ipconnect.de)11:18
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)12:24
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)12:24
blueriseminute: so you have cm4 adapters ready? :P12:54
minutebluerise: only 1 that i'm still testing... i can make you another one if you agree to struggle with DSI again with me 12:55
blueriseI can agree to struggle with DSI again12:55
minutecool12:56
minutethe rcm4 in the tweet was made independently by jacqueline (from my files)12:56
minuteshe already cloned the rest of reform independently12:57
blueriseYeah, I remember she built her own reform already12:57
minuteyeah12:57
bluerisewith USB-C port12:57
minuteyeah12:57
blueriseI found it really impressing. So much work, all those tiny solderings12:57
minutei feel like this is kind of a big deal, actually reproducible oshw (and complex one)12:57
blueriseYeah!12:57
blueriseI have two other OpenBSD devs with an MNT Reform, one of them was already asking me about CM4 ;)12:58
ex-parrot\o/12:59
bluerisehttps://twitter.com/jcs/status/150414818197781708912:59
ex-parrotoh jcs got his13:00
ex-parrotthat's really good13:00
blueriseYeah13:00
blueriseLove that guy13:00
ex-parrotme too13:00
+ chomwitt (~chomwitt@2a02:587:dc0f:ad00:bf65:8d32:22b6:5d0b)13:14
minuteok, we'll assemble some more rcm4s next week then13:31
- mtm (QUIT: Ping timeout: 240 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)14:02
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)16:09
- GNUmoon (QUIT: Ping timeout: 240 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon)17:01
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)17:01
_Emrus: I still plan on blaming Fedora until there's something better to blame18:05
_E...like my kernel config18:05
_Eminute: can the reform run without any batteries connected?18:34
minute_E: yes, no problem18:34
_Eany special config needed compared to the default setup?18:35
minute_E: you can also power it with some usb-c powerbanks + an adapter18:35
minute_E: i don't believe a special config is needed18:35
minutewe're doing a bunch of testing without any batteries for each laptop18:35
_Etrying to troubleshoot some sort of power issue with a ~week old unit and I'd much rather do it without batteries in the mix18:35
minute_E: yes, good call 18:41
_Ewell, that was a short-lived test18:42
_EI don't think the outlook is good for this board18:43
_Esomething in the neighborhood of L1 and U12 is getting very, very hot, very, very quickly18:51
_Eex-parrot: I have a sinking feeling that it's more than just the battery system18:52
minute_E: hmm, that's bad. something shorted perhaps18:53
minute_E: which country are you in?18:53
_EUS18:54
minuteah, then it's a long haul to let me look at it18:54
_Esimilar symptoms during battery-only operation18:54
_Ethis is with absolutely nothing attached at this point18:55
_Ebesides the display cable, because it was a huge pain to get on18:55
_Eminute: it's not exactly lab-grade equipment, but I do have a multimeter and some solder in case there are tests I can do myself18:56
minute_E: yeah, stop testing with batteries for now, i would say 18:57
minute_E: would you be able to get a cheap lab power supply? that way you can limit the current 18:57
_Emaybe, but there would be quite a bit of emphasis on "cheap"18:58
alex4nderyou can get cheap buck/boost converters with current limiting for < $1519:03
alex4nder(e.g. off amazon)19:03
minuteyeah but you can also get an ok lab power supply for EUR 35 or so19:10
minuteok, these are $50-$60 in the US it appears https://www.amazon.com/Adjustable-HANMATEK-HM305-Variable-Switching/dp/B0852JZQZR19:11
_Ejust tried ex-parrot's isopropyl alcohol trick19:21
_Eit's looking like Q17 or something in it's very immediate vicinity19:21
_Eat least, as the heat source19:22
_Eand by that I mean it's getting hot enough for the alcohol to sizzle19:29
_Eabout 3-5s after having power applied19:29
_Eno peripherals or removable components, entirely extracted from the chassis19:31
mrus_E: I fully support this19:44
alex4nderminute: hey, am I remembering right that you do compilation on a honeycomb lx2?  how do you like it?19:45
minutealex4nder: i like it a lot, i also did 2 days of video editing on it19:47
minutebut i did the silent noctua fan mod and it doesn't cool well enough19:48
minuteso i ran into thermal shutdowns when a lot of cores were grinding19:48
alex4nderok, good to know19:48
minutei am using an old radeonsi card with it19:48
minutealso i'm using UEFI, debian, but with custom kernel build from boundary19:49
minutemainline is missing some smmu stuff which leads to pain19:49
minutesorry, not boundary, solidrun19:56
alex4ndersweet, using nvme as storage?19:56
minutealex4nder: yep19:56
_Emrus: you know, we could go further and blame poettering directly19:57
alex4nderminute: cool, did you go with ECC sodimms?  it looks like it supports them19:57
mrus_E: you mean for crimes against humanity (systemd)?19:58
minutedon't remember atm alex4nder19:58
_Emrus: why does no one remember he's also behind Avahi20:00
mrusI do remember, but avahi hasn't really become a crucial component of everyday Linux20:01
mrusit doesn't really impact people, no matter how good or bad it is20:01
minute_E, mrus: please refrain from personal attacks in this channel20:01
mrusminute: I'm obviously joking20:01
_Elennart started it20:02
_E/s20:02
mrusquote from Wikipedia: "In 2017, Poettering received the Pwnie Award for Lamest Vendor Response to vulnerabilities reported in systemd"20:03
mrusit's not even a personal attack in first place20:03
mrusit's raising awareness for the awards he received20:03
_Eminute: I can't say for sure if I'll be able to get an appropriate power supply any time soon20:03
_Eso if there are other tests that can be done in the interim20:04
minute_E: ok, i'm currently on vacation and sick, so i must not look at schematics etc right now, but can help from tuesday 20:04
minuteidk by heart what Q17 is20:05
alex4nder_E: where in the US are you located?20:05
_Ealex4nder: VA20:05
alex4nderah ok, I'm on the other side20:05
_Eminute: I'm impressed at your ability to schedule your recovery from an illness20:05
minute_E: easy20:06
minutethe rule is, i get sick as soon as i am on vacation20:06
minuteand recover in time for the end of it20:06
alex4nderperfect20:06
minuteperfectly tuned organism20:06
kfx_E: plenty of hackerspaces in virginia.  might see if a nearby one can lend gear to a troubleshootiung effort20:12
_Enot so much in my area20:13
_Eonly one I'm aware of is a few cities away, and of dubious open-ness20:13
alex4nderhmm, looks like ECC sodimms are not that expensive right now20:17
+ adjtm (~adjtm@53.red-83-56-237.dynamicip.rima-tde.net)21:16
- xktr (QUIT: Ping timeout: 240 seconds) (~xktr@108.62.5.153)21:20
+ alexande1 (~alexander@wsip-184-186-225-187.sb.sd.cox.net)21:28
alexande1ok.. reform nvme debootstrapped from upstream debian.. 21:38
alexande1and of course I've got broken X11 fonts21:38
* alexande1 -> al3x4nder21:42
minuteal3x4nder: x11?21:44
al3x4nderminute: yah, anything going through Xwayland is rendering fonts as blocked rectangles21:44
al3x4nderI've just derped something, but I'm not sure what yet21:44
minuteal3x4nder: i know what that is21:45
minuteal3x4nder: you need to set ETNA_MESA_DEBUG=nir in your profile21:45
minutekinda a running gag at this point21:45
al3x4nderah ok21:45
al3x4nderACTION tries that21:45
- al3x4nder (QUIT: Quit: brb) (~alexander@wsip-184-186-225-187.sb.sd.cox.net)21:47
+ al3x4nder (~alexander@wsip-184-186-225-187.sb.sd.cox.net)21:48
al3x4nderminute: rad, thank you.. I would have been searching for that forever21:49
minute> It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying "Beware of the Leopard"21:50
al3x4nderdude exactly21:50
scopshmmm if i want to replace the kernel for booting vom nvme, is it better to flash the emmc (V2-rescue is installed) or should i just replace initrd.img (Image on emmc) and dtb with the ones that comes with the sd card image?21:54
scopss/vom/of/21:55
scops+f21:55
minutehmm, i don't really have much experience with testing the v3 stuff with initrd on emmc yet, so i don't want to give false advice22:05
minutemaybe josch can weigh in22:06
joschscops: I'll test eMMC boot this weekend (we have an extra holiday due to easter) and will come back to you then.22:06
joschACTION hasn't yet changed the dip switch under the heatsink22:06
scopscheck 🙂 atm i booted into a fresh done encrypted nvme v3 image with the old v2 kernel on emmc22:07
scops(and making a backup of my old emmc data just for the case)22:08
minutecool!22:09
- al3x4nder (QUIT: Ping timeout: 246 seconds) (~alexander@wsip-184-186-225-187.sb.sd.cox.net)22:18
+ MajorBiscuit (~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net)22:46
scopshmmm another problem... i just flashed the lpc firmware. the keyboard can't wake up the lpc. any ideas?22:54
scopsok i think it was tools/lpcrc which isn't build with the main Makefile22:56
- MajorBiscuit (QUIT: Ping timeout: 240 seconds) (~MajorBisc@2a02-a461-129d-1-6d4c-38a4-18b7-4b48.fixed6.kpn.net)23:07
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)23:19
scopsah a suggestion; it would be nice if firmware updates doesn't require a whole compilation and >2gb compile tools (for the lpc firmware for example). providing the ready to use binaries like for the systemimages would be really nice, imho23:27
vagrantcscops: i put a little bit of work into packaging the firmware for debian: https://salsa.debian.org/vagrant/mnt-reform-firmware23:30
vagrantcbut it has been a while since i looked at it ... would be really helpful if the different firmwares were in separate repositories23:31
scopsyeah23:32
vagrantcbut i actually used the firmware produced from that on my mnt/reform ... at least the lpc and maybe one other23:32
vagrantcor at least all the firmwares were in a separate repository23:33
scopsi just updated my lpc and keyboard firmware (from official repo) since i haven't done it since i got my little black laptop 😉 (https://community.mnt.re/t/mnt-reform-recommended-lpc-and-keyboard-firmware-update-to-fix-battery-drain-in-off-state/559)23:34
vagrantcright, probably those are the two i updated23:36
scopsah and it wasn't noticed in the handbook that i had to install the package "gcc-arm-none-eabi" to compile the lpc firmware... and the tools/lpcrc stuff23:39
scopsthis should be added 🙂23:39
vagrantci prefer packaging to prose instructions, as it's easier to get right :)23:44
vagrantcand easy to test if it works or not (e.g. not making assumptions about what's already installed)23:46
scopsMe too, but the handbook should also have all important informations in it, if they are relevant. On the lpc flashing part nothing is mentioned about the tools you need to compile the stuff. On the keyboard files at least the readme.md lists the tools needed23:49

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