2025-01-17.log

- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)00:10
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)00:10
BoostisBetterminute: I had another incendent and I grabbed the logs from dmesg from journalctl in a file. Should I just email it to you?00:21
minuteBoostisBetter: pastebin or gist and post the link here would be best00:32
BoostisBetterminute: OK going to bed now, but will send it in the am. 00:35
BoostisBetterI have two files. One where the keyboard would not reconnect and then when it failed to connect all. 00:35
BoostisBetterShould be good info. 00:35
minutech: hm, i drained my pocket's battery and now it doesn't seem to be able to power up/charge anymore on current git tip sysctl fw00:39
BoostisBetterminute: I couldn't wait, so here is the pastebin to the first one00:45
BoostisBetterhttps://pastebin.com/JFuTSphh00:46
BoostisBetterand the second when things really took a dump00:47
BoostisBetterhttps://pastebin.com/3RAmnHSU00:47
BoostisBetterfrom that second one there was no recovery. No matter what I did the kb would not reconnect. 00:47
+ mtm_ (~textual@47.202.75.129)00:54
- mtm (QUIT: Read error: Connection reset by peer) (~textual@47.202.75.129)00:54
+ aloo_shu_ (~aloo_shu@85.51.17.211)00:59
minuteBoostisBetter: thx01:00
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.16.131)01:01
* aloo_shu_ -> aloo_shu01:01
- cobra (QUIT: Ping timeout: 276 seconds) (~cobra@user/Cobra)01:05
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)02:33
chminute: hmm, i need to look at that. however in the past (on my branch) i accidentally ran into that situation a number of times and it was always recovered nicely02:40
minutech: ok, maybe a hw issue then on my side, but can only look into it with proper tools tomorrow02:41
chyeah same, tonight nothing will happen02:41
- paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.71.33)03:19
- nsc (QUIT: Ping timeout: 252 seconds) (~nicolas@i5C74DF89.versanet.de)03:56
+ nsc (~nicolas@i5C74DC72.versanet.de)03:57
+ cobra (~cobra@user/Cobra)04:04
- sigrid (QUIT: Quit: Lost terminal) (~sigrid@ftrv.se)05:13
+ sigrid (~sigrid@ftrv.se)05:14
- Ar|stote|is (QUIT: Ping timeout: 252 seconds) (~linx@149.210.29.162)06:16
+ Ar|stote|is (~linx@149.210.28.210)06:20
+ aloo_shu_ (~aloo_shu@85.51.16.240)07:04
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@85.51.17.211)07:05
* aloo_shu_ -> aloo_shu07:05
+ _justin_kelly7 (~justinkel@user/justin-kelly/x-6011154)07:17
- _justin_kelly (QUIT: Ping timeout: 260 seconds) (~justinkel@user/justin-kelly/x-6011154)07:19
- _justin_kelly7 (QUIT: Ping timeout: 248 seconds) (~justinkel@user/justin-kelly/x-6011154)07:22
+ _justin_kelly7 (~justinkel@user/justin-kelly/x-6011154)09:24
+ aloo_shu_ (~aloo_shu@90.166.98.128)09:38
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.16.240)09:40
* aloo_shu_ -> aloo_shu09:40
chdo you know if sysctl booted in that state?10:00
minutech: not yet! overslept and not at the hq yet :D10:53
ch:)10:54
gordon1is there a way to connect spi device to CPU?11:03
grimmwaregood morning team11:10
chidk if 'team' has a positive ring to it (:11:18
gordon1*is there a way to connect spi device to CPU on reform classic?11:20
abortretryfailI'm sure you could do it, but Idk how hard it would be.11:26
sknebelthe hack the planet port has SPI on it afaik11:31
abortretryfailThat connects to the system controller (LPC), not the main CPU (iMX)11:31
gordon1but it is connected to EC not CPU if i recall correctly11:31
sknebelbut youd need to go through the LPC, yes11:32
gordon1well, that means i need to completely rewrite the linux driver then11:32
sknebelyou could check if the JTAG pins can be reconfigured to be SPI11:35
[tj]weather has cleared up at crowdsupply11:36
+ mjw (~mjw@gnu.wildebeest.org)11:39
+ gustav28 (~gustav@c-78-82-52-61.bbcust.telenor.se)11:48
+ paperManu (~paperManu@107.159.71.33)12:38
grimmwarech: I got into the habit of saying it kind of tongue in cheek and then at some point along the way I just got into the habit of saying it12:50
grimmwarech: it's really funny that in some channels I'm in other people started doing it too12:51
joschwe had a joke that my partner was super funny when i talked about the "sbuild-team" which, at that point the team was essentially just me, so my partner called them the sbuild ninjas because they are so good at hiding. :) Gladly today, there are more people than just me doing the work. I'm looking at you zeha :)12:52
[tj]grimmware: you had a wonderful explanation once that I can only half remember13:00
[tj]it might have been the first sentence of your last emf talk13:00
grimmware[tj]: what was it about?13:00
grimmwareI say a *lot* of things13:01
grimmwareI can't be expected to take any of them seriously enough to remember them hahah13:01
chjosch: i'm not really doing work on sbuild. more like bugging you about things13:12
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.98.128)13:15
joschch: you underestimate how immensely helpful it is to get feedback from people testing your stuff and telling you about problems :)13:16
minuteclassic reform status update https://mastodon.social/@mntmn/11384363298510802613:16
+ aloo_shu (~aloo_shu@90.166.99.14)14:04
- wickedshell (QUIT: Ping timeout: 248 seconds) (~wickedshe@2601:8c0:800:4baa:9344:f080:6c7d:42ef)14:15
BoostisBetterminute: good work. No rush on a kb update, but I was wondering if my logs were able make sense of what was going on? To me it just seems like there is a usb enumeration problem that is cascading14:16
chjosch: maybe i just have a too old viewpoint on these things14:28
- ericsfraga (QUIT: Remote host closed the connection) (~user@2a00:23cc:b43d:4b00::3ce)14:29
+ bkeys (~Thunderbi@173.16.175.75)14:39
+ ericsfraga (~user@2a00:23cc:b43d:4b00::3ce)14:53
minutedamn, i finally got the exploded U1 issue myself on my pocket reform charger board15:07
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@173.16.175.75)15:08
chuh, the mp2650 blows up?15:11
chthats why it didnt charge?15:11
minutech: yeah it's always the same failure mode... happened so far maybe on 5-10x boards15:11
L29Ahdid it damage any PCB traces?15:11
minuteL29Ah: not sure, didn't desolder it15:12
gordon1U1 is CPU socket, isn't it?15:12
minutegordon1: no. charger module15:12
minuteit's always around pins 29,30,1 of mps265015:12
gordon1i have a wrong schematics it seems15:12
minutegordon1: you're just looking at the wrong pcb i guess15:13
gordon1ah, there are more than one15:13
gordon1>classic reform status update15:16
gordon1awesome job, any ETA for this year's orders? 3 months stated on the shop page are still accurate?15:16
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)15:19
- antti (QUIT: Ping timeout: 246 seconds) (~antti@user/antti)15:50
+ antti (~antti@user/antti)15:52
* mjw -> Guest207916:00
- Guest2079 (QUIT: Killed (osmium.libera.chat (Nickname regained by services))) (~mjw@gnu.wildebeest.org)16:00
* Guest2961 -> mjw16:00
+ wickedshell (~wickedshe@2601:8c0:800:4baa:d70c:9024:1177:3ad1)16:20
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)17:20
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:20
- bkeys (QUIT: Client Quit) (~Thunderbi@38-146-94-247.echocast.zone)17:22
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:23
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)17:23
gsorayay classic reform update!17:28
+ bkeys1 (~Thunderbi@38-146-94-247.echocast.zone)17:38
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)17:38
* bkeys1 -> bkeys17:38
+ _justin_kelly71 (~justinkel@user/justin-kelly/x-6011154)17:41
- _justin_kelly7 (QUIT: Ping timeout: 244 seconds) (~justinkel@user/justin-kelly/x-6011154)17:43
* _justin_kelly71 -> _justin_kelly717:43
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)17:50
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:50
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)18:02
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)18:03
- bkeys (QUIT: Ping timeout: 272 seconds) (~Thunderbi@38-146-94-247.echocast.zone)18:07
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)18:13
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone)18:21
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)18:26
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)18:31
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)18:32
+ aloo_shu_ (~aloo_shu@85.51.17.165)18:36
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@90.166.99.14)18:38
* aloo_shu_ -> aloo_shu18:38
+ mark_ (~mjw@gnu.wildebeest.org)18:38
- bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@38-146-94-247.echocast.zone)18:41
hramrachcwebber: Sombody connected two position sensors to the sysctl, and did the calculation to determine the lid angle. don't remember the details, read about it like a month ago. So you can have lid switch without sensor in the hinges, sort of18:42
hramrachminute: I think it's more constructive to provide some libinput ot whatever configuration for the trackball than arbitrarily change the acceleration in the firmware18:44
gordon1i think with reform classic expansion port already has ADC and lid already has magnets so it should be extremely trivial to add hall effect sensor on hotsnot somewhere near the trackball to detect closed lid18:44
hramrachdo hall effect sensors trigger when you are walking down the hallway?18:45
gordon1well, it's up to you, you can trigger it when ADC is low and you know for sure you are not in the hallway18:47
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)18:49
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@38-146-94-247.echocast.zone)18:54
* mjw -> Guest942819:26
- Guest9428 (QUIT: Killed (tungsten.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)19:26
* mark_ -> mjw19:26
+ Guest9428 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c)19:26
+ aloo_shu_ (~aloo_shu@85.51.16.10)19:43
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@85.51.17.165)19:44
* aloo_shu_ -> aloo_shu19:44
gordon1what is the distance between the ball and the screen in reform classic when it is closed?21:44
joschit can become 0 mm21:45
gordon1scary21:47
gordon1especially for silicon nitride ball21:47
joschwhy?21:48
gordon1not sure screen will be happy to meet silicon nitride ball while it is bobbing along in my backpack21:49
gordon1s/it is/reform is/21:51
joschi tried out a silicon nitride ball for a few weeks including the backpack experience daily21:51
joschat least for me, nothing happened21:51
joschmy problem with the silicon nitride experience was, that in contrast to the original ball, it tracked much worse21:51
joschbut other participants in this chat had the opposide experience21:52
gordon1i have a plan to mitigate that21:52
gordon1involving gas torch an phosphoric acid, will report when i'll try21:52
gordon1*and21:52
joschcool!21:53
gordon1i also have a hypothesis why it actually work for some people while it is most certainly shouldn't21:54
gordon1josch: say, do you use bearing balls in your cup?21:54
joschyes, i do21:55
gordon1are those metal or plastic?21:55
joschmetal21:55
gordon1well, here my hypothesis goes out of the window21:56
gordon1i thought it actually wears those metal balls a bit to create tracks as if you scraped a plate with a metal fork, and that's enough for a sensor to detect, but it's probably something else then (finger grease?)21:57
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-61.bbcust.telenor.se)22:15
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)22:49
L29Ahgordon1: pretty sure the screen doesn't care about your ball, but might get upset about the sand and other abrasive particles that may get inbetween23:05
joschit does care a little bit. If I pull up a white image and then look very closely at the spot where my POM ball probably touches the screen, then there is a small faint dark shadow where the image is not as white as around it23:07
KoodaHi hi :3  Chonky Reform imx8mq user here. Sorry to barge in, I was wondering a few things.  1) Would it be possible to have a build of the kernels with RT patches/scheduler?  2) Is the display in Reform Next the same as in the original chonky one? Or at least compatible in shape and connectivity? Was just wondering if I could build my own and reuse some parts. ^^23:22
gordon1L29Ah: silicon nitride third hardest after diamond and cubic boron nitride, it is hard enough to wear out glass23:24
L29Ahgordon1: so?23:24
L29Ahdoesn't matter much if it is well polished23:24
gordon1it's a ball, there is a point contact between screen and a ball, probably enough to chip it23:25
L29Ahbut still will happily turn any speck of dust into a chisel23:25
L29Ahisn't screen covered with a plastic sheet?23:25
gordon1even worse for the screen then23:26
L29AhACTION stares at the footprint of a trackpoint nib at his screen23:27
L29Ahmnt reform should have an oled screen option23:27
gordon1yeah i would rather not have that, thank you very much23:28
L29Ahbut muh battery life23:28
L29Ahalso CLKREQ23:28
gordon1i'm about footprint of a trackpoint, not oled23:28
joschKooda: yes, we have it disabled as nobody saw evidence yet that it improves anything. Discussion here: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/1823:29
gordon1and with oled, it's just edp, isn't it? so just find oled with edp and replace it23:29
gordon1i think that should be pretty straightforward23:30
hramrachIn the near future it is expected that RT will be part of the mainline kernel so doing nothing you will likely get it in a few months23:30
gordon1isn't it already so?23:30
gordon1yeah, it is, starting from 6.1223:30
Koodajosch: ah! thanks for that!23:30
hramrachThere are some non-mainline patches still, IIRC23:30
L29Ahgordon1: it is easier to replace it with xreal air23:30
Koodahramrach: yeah the patches got merged mainline finally23:31
L29Ahhmmm i wonder if there's a screen-free option23:31
KoodaBut I’m still on Debian stable kernel, as dual display works there ^^'23:31
joschenabling the display on 6.12 might be trivial for somebody who knows how to modify the dts23:32
joschthe cadence patch stack changed and the dts has to change accordingly and nobody has done that yet23:33
KoodaIs it just a dts problem? I remember 6.10 was quite broken23:33
joschthe cadence patch has some examples that could be used by those who know what they are doing (not me)23:33
gordon1L29Ah: go with pocket reform then, it's smaller, optional screen could be used when you cannot be bothered to pull xreal air from the bag23:34
joschthe problem exists since 6.923:34
hramrachThe built-in display is actually higher resolution than current day glasses23:35
L29Ahhramrach: xreal air is 2*2Mpix23:36
hramrachit would be something like 2xFHD because one for each side and you get 1xFHD in the end but the built-in display is something like 4xFHD in one screen23:37
L29Ahyes, and you can feed different images to different eyes23:38
L29Ahand both reforms have 1xFHD23:39
hramrachno, the Pocket screen is much bigger23:39
L29Ahhttps://shop.mntre.com/products/mnt-pocket-reform > Full HD23:39
hramrachindeed, mixed it up with something else23:42
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@38-146-94-247.echocast.zone)23:48
+ aloo_shu_ (~aloo_shu@90.166.99.32)23:49
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.16.10)23:50
* aloo_shu_ -> aloo_shu23:50
hramrachwhat bugs me about the PD charging discussion is that there is apparenlt one resistor that acts as some sort of multiplier for a charging curve that decreases the charging carruen proportionally to the battery charge and the smallness of the resistor. However, there are two constraints: the charging curve that corresponds to recommended current for the battery chemistry, and the maximum current23:52
hramrachthe power supply can provide. To meet tle latter the former is adjusted.23:52
hramrachis there no IC that provide both knobs?23:52
gordon1it's usually constant current followed by constant voltage charge http://www.batterypoweronline.com/wp-content/uploads/2017/11/cadex1a.jpg, is it some advanced charging thing with current curve that you're talking about?23:58
L29Ahhow about picking IC that provides whatever current it is said to provide over I2C or so, and tell it what to do in EC?23:58

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