2023-07-03.log

+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)00:00
joschvagrantc: can you confirm that SOURCE_DATE_EPOCH should make the u-boot build bit-by-bit reproducible? a simple rebuild seems to confirm that it does00:03
+ gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es)00:06
- ec0 (QUIT: Ping timeout: 240 seconds) (~ec0@vps-446f4f39.vps.ovh.ca)00:20
+ ec0 (~ec0@vps-446f4f39.vps.ovh.ca)00:22
vagrantcjosch: mostly. there is also a patch that never got accepted upstream to fix build path issues00:22
vagrantcjosch: it's in debian's u-boot.git debian/patches ...00:22
vagrantcjosch: possibly using gcc-13 will obviate the need for part of the relative path patches00:23
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org)00:37
- jjbliss (QUIT: Remote host closed the connection) (~jjbliss@1464766-static.elnsmiaa.metronetinc.net)01:03
+ jjbliss (~jjbliss@1464766-static.elnsmiaa.metronetinc.net)01:07
- mtm (QUIT: Ping timeout: 240 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)02:02
joschvagrantc: i hadn't tried varying the build path. when i tried, it wasn't reproducible anymore indeed02:37
joschvagrantc: now i applied your patch and it works! \o/02:37
joschhttps://source.mnt.re/reform/reform-boundary-uboot/-/merge_requests/1802:39
vagrantcnice! :)02:39
vagrantci proposed that patch upstream, but it seems to have gotten lost in the cracks somehow ...02:40
vagrantcshould probably prod it again02:40
joschyou should :)02:42
vagrantcah, it got lost with fixing a bug in gcc ... which has since been fixed. but still needs the rest of the patch (and depends on gcc-13 i think)02:44
- XYZ (QUIT: Ping timeout: 250 seconds) (~XYZ@78-80-115-59.customers.tmcz.cz)03:37
+ XYZ (~XYZ@78.80.115.59)03:58
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)04:08
+ yewscion (~yewscion@2601:547:a01:2900:d6fb:50b3:a4a3:e7af)04:30
- vagrantc (QUIT: Ping timeout: 246 seconds) (~vagrant@2600:3c01:e000:21:7:77:0:50)05:08
ex-parrothttps://img.hotplate.co.nz/DP88rfsQRv05:59
ex-parrothttps://img.hotplate.co.nz/KKJH8h3kRc06:00
ex-parrothttps://img.hotplate.co.nz/eMtFWzvGtf06:00
ex-parrotnew parts intact \o/06:00
noamAre the protected boards available in the US?06:01
ex-parrotI just received them in Aotearoa New Zealand so I’m sure you can get them shipped basically anywhere 06:02
+ bgs (~bgs@212-85-160-171.dynamic.telemach.net)06:15
- jryans (QUIT: Server closed connection) (~jryans@2001:470:69fc:105::1d)07:03
+ jryans (~jryans@2001:470:69fc:105::1d)07:04
joschex-parrot: nice haul! :D07:12
- gnou_liber (QUIT: Read error: Connection reset by peer) (~gnou_libe@223.pool85-50-3.static.orange.es)07:56
+ gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es)08:15
- Boostisbetter (QUIT: Ping timeout: 240 seconds) (4a410829d7@irc.cheogram.com)08:29
- XYZ (QUIT: Remote host closed the connection) (~XYZ@78.80.115.59)08:47
+ XYZ (~XYZ@78-80-115-59.customers.tmcz.cz)08:52
+ Boostisbetter (4a410829d7@irc.cheogram.com)09:16
BoostisbetterIf MNT would sell a battery pack based on lifepo I would buy it immediately! Seems like most of the work for that kind of thing has already been done. 09:17
AllieBoostisbetter: i mean, you can assemble your own from cells + a battery board09:18
BoostisbetterYeah, but for best results you need a spot welder. 09:19
BoostisbetterUsing MNT battery boards you wouldn't have to do that and it would be easy to replace batteries as they degrade. 09:19
BoostisbetterAll the components to make a quality pack are already present in the MNT wheel house. It is low hanging fruit in that regard. 09:20
+ mjw (~mjw@gnu.wildebeest.org)09:45
- klardotsh (QUIT: Ping timeout: 246 seconds) (~klardotsh@98.97.114.65)10:33
- gnou_liber (QUIT: Ping timeout: 246 seconds) (~gnou_libe@223.pool85-50-3.static.orange.es)10:49
+ gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es)10:55
- rafostar[m] (QUIT: Remote host closed the connection) (~rafostarm@2001:470:69fc:105::2:52da)11:06
BoostisbetterBrought the Reform into work today and the thing took a dump on me. I don't have a tool to open the bottom and disconnect the battery as my lpc is frozen. 11:26
BoostisbetterRats! 11:26
BoostisbetterGlad I have the newer battery holders. 11:26
vkoskivIs the lpc frozen or the keyboard? As in, can you bring up a menu when pressing circle?11:27
sevanI do have it where the lpc is non-responsive if I leave the system to charge switched off (I have the new battery boards), requiring the batteries to be disconnected and reconnected for the system to function. system apears dead when that happens, keyboard is non responsive & no menu on oled display11:49
vkoskivI have had the same thing happen, but I was under the impression that that was the missing pull up resistor on the kbd reset line?11:51
vkoskivIn fact, I recall resolving the issue by unplugging the keyboard usb + uart and plugging it back in11:52
vkoskivThough I don't know if it's a good idea to yank those cables with battery power present11:52
sevanoh, hadn't explored other aspects of the system. I can try the keyboard next time it happens and report back.11:54
sevangot into the habbit of disconnecting the batteries from when I built the laptop due to the original battery board11:55
minuteBoostisbetter: did you take a charger?12:04
- mjw (QUIT: Ping timeout: 246 seconds) (~mjw@gnu.wildebeest.org)12:09
* mark_ -> mjw12:09
Boostisbettervkoskiv: no the lpc is frozen. Happens sometimes when fully powering down the reform and then turning it back on. 12:27
Boostisbetterminute: no, sadly I do not. The batteries get me through the full work day so I don't bother with it. 12:27
Boostisbetterminute: would a charger have helped? 12:27
vkoskivI have tried plugging it in in that state, and it didn't change anything afaik12:28
- gnou_liber (QUIT: Read error: Connection reset by peer) (~gnou_libe@223.pool85-50-3.static.orange.es)12:32
+ gnou_liber (~gnou_libe@223.pool85-50-3.static.orange.es)12:41
minuteBoostisbetter: what exactly happens if the lpc is frozen? keyboard hangs at waking up lpc...?12:41
minuteBoostisbetter: what could happen after putting in new batteries is that the protected battery boards are not fully "open" i.e. the protection is on, and plugging the charger once "opens" them12:44
minutebut not sure if that's what happened there12:44
minutei put in a brownout reset in the lpc firmware at some point btw12:44
minutethis was in april12:46
minuteBoostisbetter: if you don't have LPC firmware R4 yet, it might help to upgrade 12:47
minutehttps://source.mnt.re/reform/reform/-/commit/7e64ff3ffa6b0283552d93ad2f2a15aeb29712e1#9dd41aa9fc12e43ceecc8a84ace96997e73160de_468_52612:47
Boostisbetterhttps://upload.im.boosterfive.com:5281/upload/W7m3TGCn2HbEA938kXQ8PtbT/Tm7BcHs1RkODrfZiizzkDg.jpg12:48
BoostisbetterYeah my lpc Software is from 2021. 12:49
BoostisbetterHow does one update it? Do I need a serial interface? 12:49
Boostisbetterminute: in the picture that screen is flickering and you cant do anything. It is just stuck there. 12:50
minuteBoostisbetter: hmm and which version is the keyboard fw?12:52
minuteBoostisbetter: the lpc fw can be updated with a micro USB cable12:52
minuteBoostisbetter: here is the newest firmware file https://source.mnt.re/reform/reform/-/jobs/1299/artifacts/file/reform2-lpc-fw/firmware-20_R3.bin12:54
minuteBoostisbetter: the process works like this: 1. you connect a microUSB cable to the motherboard on one end and at the other end a PC (windows is fine in this case) 2. you toggle the LPC programming switch to "on" and reset the lpc with LPC reset button 3. lpc's flash is presented as a USB disk on the PC 4. you overwrite the old firmware file on that disk with the new one (rename it to the same12:56
minuteold name first) 5. toggle programming switch back and reset lpc again, done12:56
minuteBoostisbetter: details https://mntre.com/reform2/handbook/parts.html#flashing-the-firmware12:57
sevanoooh, I'm running R312:58
Boostisbetterminute: seems strght forward enough. I got my Reform end of 2021, and I have never updated the firmware. 13:16
BoostisbetterSo I'll do that post haste when I get home. 13:16
Boostisbetterminute: so we are not using the flash.sh if we are just copying the new firmware over the old? 13:18
Boostisbetterminute: I have never had a problem with the keyboard. 13:19
minuteBoostisbetter: the OLED menu is rendered by the keyboard, so the problem could as well be there13:24
BoostisbetterAhh OK13:24
minuteBoostisbetter: flash.sh is recommended if your host computer is linux, as copying the file there in file manager could lead to problems13:24
minutebecause the weird virtual filesystem was designed for DOS/windows i thin13:25
minutethink13:25
BoostisbetterI am using Windows so it should be ok then. 13:25
minuteyep13:25
minutejust rename the file to firmware.bin before copying it13:26
minutewhat flash.sh does is copying the file with dd: dd if=bin/firmware.bin of="/mnt/firmware.bin" conv=nocreat,notrunc13:26
joschhm... maybe i should improve the lpc flashing script next and let Boostisbetter test it :)13:59
joschminute: could you create that git tag for the reform repo? because then the tag name will be part of the firmware and it will be clear what version is running14:00
- mlarkin (QUIT: Ping timeout: 240 seconds) (~mlarkin@047-036-115-056.res.spectrum.com)14:00
- mtm (QUIT: Ping timeout: 264 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)14:03
Boostisbetterminute: I run wsl on my machine and I can connect it to there or in a Linux vm. 14:22
BoostisbetterSo I'll up date it after work. 14:23
+ murdock (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)15:41
minuteBoostisbetter: just using windows file manager will be easier i think15:55
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)16:09
- gnou_liber (QUIT: Ping timeout: 246 seconds) (~gnou_libe@223.pool85-50-3.static.orange.es)16:14
+ gnou_liber (~gnou_libe@90.174.5.215)16:15
- bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@45.134.140.137)16:16
+ rafostar[m] (~rafostarm@2001:470:69fc:105::2:52da)17:10
Boostisbetterminute: thanks! 17:24
BoostisbetterDo any of the savy people here know about a signal client that will work on Linux 32 bit?17:25
noamQEMU, probably17:25
BoostisbetterQemu can run a 64 bit os on a 32 bit one? I would think perform would be atrocious. 17:26
BoostisbetterResources are scare on this platform. Hahaha17:26
Boostisbetterminute: btw, my keyboard is on R117:26
sigridthere is qemu but there is also qemu-user, which is much faster than full emulation17:31
- gnou_liber (QUIT: Read error: Connection reset by peer) (~gnou_libe@90.174.5.215)17:41
BoostisbetterOk, I can try qemu-user. 17:45
BoostisbetterI am trying to get it running on a Pi Zero 2 w17:46
Boostisbetterso I am not sure the resources will be enough to get that done. If I swap this thing out for the Radxa Zero then I will have 4gb and that will be awesome. 17:46
sigridsignal is an electron app? that's a bummer, I would not expect it to run with just 512Mb of ram in this case17:49
+ gnou_liber (~gnou_libe@90.174.5.215)17:49
q66yeah 64MB of RAM is pretty little17:49
sigridmaybe some other CLI alternative is available, I'd try that instead17:50
ethulhuthings like signald do exist17:51
minutejosch: you just need me to create a version (isodate) tag for https://source.mnt.re/reform/reform ?18:01
minutejosch: if that's the case, here you go https://source.mnt.re/reform/reform/-/tags18:02
- gnou_liber (QUIT: Read error: Connection reset by peer) (~gnou_libe@90.174.5.215)18:12
+ mark_ (~mjw@gnu.wildebeest.org)18:14
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)18:14
* mark_ -> mjw18:14
+ mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)18:14
noamAh yeah, the official signal client is terrible, I forgot about that :/18:18
noamSorry, I wouldn't have suggested that if I'd remembered18:18
Boostisbetterhonestly I at the point where I am just about done with Signal. 18:28
- murdock (QUIT: Ping timeout: 250 seconds) (~murdock@dhcp-68-142-57-54.greenmountainaccess.net)18:35
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)18:36
+ klardotsh (~klardotsh@98.97.35.74)18:45
joschminute: that was a useful test because if you tag a commit without also bumping the value of KBD_FW_VERSION and FW_STRING3 the pipeline fails: https://source.mnt.re/reform/reform/-/jobs/130919:24
joschminute: so if you want to create a tag you call 2023-07-03 then you have to set both strings to r 20230703 (because there seems to be an eight character limit)19:25
joschminute: should i prepare a merge request that does the right thing?19:29
joschunfortunately i cannot do tagging as part of a merge request otherwise i'd prepare the whole thing :D19:29
noamBoostisbetter: I was at that point immediately after being forced to install it for $DAYJOB tbh19:47
- yewscion (QUIT: Read error: Connection reset by peer) (~yewscion@2601:547:a01:2900:d6fb:50b3:a4a3:e7af)20:00
+ bkeys (~Thunderbi@45.134.140.137)20:46
- XYZ (QUIT: Ping timeout: 246 seconds) (~XYZ@78-80-115-59.customers.tmcz.cz)20:48
minutejosch: oh yes please :D sorry, i'm a bit under water because of part sourcing, it's a lot of work21:07
minutebut looking pretty good now...21:07
joschminute: https://source.mnt.re/reform/reform/-/merge_requests/4321:15
joschminute: though after merging you should fix the latest tag so that it points to this commit or otherwise version reporting in the firmware will still be broken21:15
minutejosch: yep, i did that now, hopefully correctly21:19
minutejosch: looks like it worked?21:22
joschminute: maybe... https://source.mnt.re/josch/reform/-/pipelines21:29
joschminute: according to that, 923ce4bf passed but the pipeline above is supposedly the tag and failed21:29
joschbut according to that page the tag is still at commit 5fc6871721:30
joschyeah this overview still shows the wrong tag: 21:31
joschhttps://source.mnt.re/josch/reform/-/tags21:31
joschmaybe you can delete the tag in the webinterface and then push the new tag?21:31
minutejosch: ok, i just left the office and will try from home later21:34
joschminute: if you don't manage today, you can just create a new release with a different name tomorrow ;)21:35
+ XYZ (~XYZ@37-48-42-26.nat.epc.tmcz.cz)21:47
minute:321:53
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)21:59
- XYZ (QUIT: Ping timeout: 246 seconds) (~XYZ@37-48-42-26.nat.epc.tmcz.cz)22:12
+ XYZ (~XYZ@78-80-114-131.customers.tmcz.cz)22:25
- Boostisbetter (QUIT: Ping timeout: 246 seconds) (4a410829d7@irc.cheogram.com)22:32
+ Boostisbetter (4a410829d7@irc.cheogram.com)22:33
- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net)22:38
jfredShiny new MNT sticker got a home on my cargo bike  https://usercontent.irccloud-cdn.com/file/Rvmg5oHj/IMG_20230703_172458_055.jpg23:26
josch:D23:32
minutejfred: nice23:43

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