2023-12-01.log

+ jacobk (~quassel@utdpat241106.utdallas.edu)00:00
flowyit's freezing so if i wasn't building kernels i'd just be burning gas to heat the apartment00:00
joschhaha i was doing the same back before my build machine broke XD00:02
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.8.163)00:23
+ Ar|stote|is (~linx@149.210.8.163)00:28
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin)00:28
+ S0rin (~S0rin@user/s0rin)00:30
- jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@utdpat241106.utdallas.edu)00:32
- erle (QUIT: Read error: Connection reset by peer) (~erle@2a02:8109:da40:c4:3a02:c33e:bbab:b9ff)00:33
+ erle (~erle@2a02:8109:da40:c4:7c53:125e:e7e9:79ad)00:34
joschmhoye: things start becoming even more interesting. I just downloaded a new reform-system-image, flashed to sd-card, booted from it and /sys/module/kernel/parameters/consoleblank is 0 by default00:41
joschi waited a bit more than 60 seconds and as expected there is no blanking00:42
joschmhoye: so i wonder: what is the difference between the default configuration and yours00:43
- S0rin (QUIT: Ping timeout: 245 seconds) (~S0rin@user/s0rin)00:47
+ S0rin (~S0rin@user/s0rin)00:55
joschvagrantc: where are /etc/flash-kernel/ubootenv.d and /etc/flash-kernel/preboot.d documented? I don't see it in the man page of flash-kernel and it doesn't like to other docs.01:01
vagrantcjosch: it is distinctly possible they are undocumented. flash-kernel does not get much love.01:02
- mtm (QUIT: Ping timeout: 240 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)01:03
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net)01:24
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net)01:25
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)01:32
+ jacobk (~quassel@utdpat241106.utdallas.edu)01:44
- sevan (QUIT: Ping timeout: 260 seconds) (~sevan@user/venture37)01:51
mhoyejosch: this machine is pretty idiosyncratic in a lot of places, but I don't think I've spent a lot of time modifying boot params...01:51
joschmhoye: if you run the reform-check utility it will show you a few differences between your system and the recommended defaults -- maybe something shows up there?01:52
mhoyeoh, hah! I didn't know about that. One second.01:55
- lexik (QUIT: Ping timeout: 256 seconds) (~lexik@93.185.97.209)01:58
joschmhoye: are you running that now? Otherwise i'd go to bed. :D01:58
mhoyeI am, but I didn't see anything related to a timeout or the console01:59
joschokay01:59
joschmhoye: you ran it as root, right?01:59
+ lexik (~lexik@93.185.97.209)02:01
mhoyethe only thing it reports is that /etc/lib/alsa/asound.state doesn't exist and that /etc/flash-kernel/machine doesn't say "MNT Reform 2"02:02
joschmhoye: what does your /etc/flash-kernel/machine say?02:02
mhoyeit doesn't exist at all02:02
joschhuh o002:02
mhoyeAre we in "just back up and reinstall" territory here?02:03
joschit will not break anything because flash-kernel falls back to what is in /proc/device-tree/model but i wonder what removed it02:03
joschnono, this is fine02:03
joschit's just strange that it's missing02:03
joschit will be re-created next time you run reform-display-config02:04
mhoyeI don't think I've ever run that.02:04
mhoyehmmm02:04
joschanyways, bed for me now02:04
joschbye!02:04
mhoyethanks for your help so far.02:04
joschmhoye: also feel free to comment on my changes to boot.scr https://salsa.debian.org/installer-team/flash-kernel/-/merge_requests/53/diffs02:05
joschi hope this helps anybody in the future who attempts to change things in it02:05
+ sevan (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)02:06
- S0rin (QUIT: Ping timeout: 276 seconds) (~S0rin@user/s0rin)02:12
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)02:13
- jn (QUIT: Ping timeout: 252 seconds) (~quassel@user/jn/x-3390946)02:13
+ jn (~quassel@2a0a:a549:fbf2:0:20d:b9ff:fe49:15fc)02:13
- jn (QUIT: Changing host) (~quassel@2a0a:a549:fbf2:0:20d:b9ff:fe49:15fc)02:13
+ jn (~quassel@user/jn/x-3390946)02:13
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)02:14
mhoyejosch: for what it's worth, "unless you know what you are doing" warnings are something you really only see in software, and they're always interpreted as a challenge, instead of a warning.02:16
mhoyeLike, there are zero signs in a print shop that say, do not put your hand in the industrial paper cutter unless you know what you doing02:16
mhoyeSomething like "this file is automatically generated, including the CRC checksum in the header. Changes to this file are not durable and without updating the checksum can result in your device being unable to boot. To make changes to your boot options, instead do [the list of things you already mentioned]. When you run flash-update those changes will be reflected here with a correct CRC."02:19
- sevan (QUIT: Ping timeout: 276 seconds) (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)02:20
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@utdpat241106.utdallas.edu)02:20
mhoyeI'll add that to the bug.02:20
- mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org)02:32
+ jacobk (~quassel@utdpat241106.utdallas.edu)02:40
flowylooks like that information is already there02:53
flowyor anyways it looks good as i saw it now02:54
flowyi also wanted to edit bootscr at some point but was scared off by the binary bits02:54
+ sevan (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)02:55
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)03:09
- jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@utdpat241106.utdallas.edu)03:15
- nsc (QUIT: Ping timeout: 268 seconds) (~nicolas@240-48-142-46.pool.kielnet.net)03:58
+ nsc (~nicolas@37-99-142-46.pool.kielnet.net)03:59
+ jacobk (~quassel@utdpat241106.utdallas.edu)04:36
joschmhoye: you stopped reading after two lines? :)04:54
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@utdpat241106.utdallas.edu)05:49
- eibachd (QUIT: Ping timeout: 260 seconds) (~eibachd@p200300dcf73d8b0074380750dd4bc002.dip0.t-ipconnect.de)06:06
+ eibachd (~eibachd@p200300dcf73d8b001f37b9d71cee239b.dip0.t-ipconnect.de)06:09
+ jacobk (~quassel@utdpat241105.utdallas.edu)06:20
- jacobk (QUIT: Ping timeout: 268 seconds) (~quassel@utdpat241105.utdallas.edu)06:53
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf73d8b001f37b9d71cee239b.dip0.t-ipconnect.de)06:56
+ eibachd (~eibachd@2a01:599:312:f688:3524:3627:abdf:9a09)06:57
+ jacobk (~quassel@64.189.201.150)07:30
joschmhoye: to investigate the screen blankin thing, I moved my /usr/bin/setterm to /usr/bin/setterm.orig and wrote a shell script for /usr/bin/setterm and marked it with +x. All the script does is this:07:58
joschecho "executing setterm $@" >> /tmp/setterm07:58
joschexec setterm.orig "$@"07:58
joschmhoye: after booting, /tmp/setterm does not exist so at least on my system, nothing seems to call setterm during boot07:58
hramrachjosch: It's tempting to add the documentation into the boot.scr file whn it's missing in the man page but I think it's more constructive long-term to add the annotations for the included files, and only refer to the man page rather than duplicating it11:22
hramrachmhoye: when the reasons are provided that's completely fine challenge I think ;-)11:24
+ chomwitt (~chomwitt@ppp-94-67-191-45.home.otenet.gr)12:57
- mtm (QUIT: Ping timeout: 255 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)13:03
joschhramrach: a lot of information is missing from what I've put into boot.scr. My plan was to fix this first and then make a longer write-up for the man page later once i find the time and motivaition to do so. At that point I'll add a pointer from boot.scr to the man page, yes.13:44
+ S0rin (~S0rin@user/s0rin)13:53
- sevan (QUIT: Changing host) (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)14:01
+ sevan (~sevan@user/venture37)14:01
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:312:f688:3524:3627:abdf:9a09)14:05
+ eibachd (~eibachd@p200300dcf73d8b00c1d59559971f6a9b.dip0.t-ipconnect.de)14:05
BoostisBetterdo we need to make the lpc firmware. 14:38
BoostisBetterI have the lpc in flash mode now, but I can't seem to build or find the bin that needs to be flashed to it14:38
BoostisBetterI just cloned the reform2-lpc-fw folder14:38
BoostisBetterI am on a amd64 machine connected to the lpc micro usb14:39
BoostisBetterbecuase I'm striking out on trying to build it on the Librem 5 and my Framework running Ubuntu 22.0414:54
BoostisBetterThe keyboard firmware was really easy, but i have to be honest, I am a little disappointed on the LPC instructions. I have cloned the necessary source, but I cannot make the firmware, and there are not any pointers on dependencies or anything on how I would go further. In the instructions it is not mentioned that you need to make anything, but if you don't there are no binaries to flash. 14:59
joschBoostisBetter: do you want to compile the firmware yourself or do you want to download the firmware from mnt.re CI?15:00
BoostisBetterdownloading is fine with me. 15:01
BoostisBettersaves me from having to tinker with the build environment on my end. 15:02
joschBoostisBetter: concerning better documentation for how to compile it, there is this open MR that still needs some adjustments until it can be merged (see my comments to it): https://source.mnt.re/reform/reform/-/merge_requests/5615:03
joschBoostisBetter: concerning better documentation for how to flash it, there is this open MR that improves the flash.sh script: https://source.mnt.re/reform/reform/-/merge_requests/4515:03
joschBoostisBetter: you can download version  2023-11-24 of the firmware here: https://source.mnt.re/reform/reform/-/jobs/2612/artifacts/browse/reform2-lpc-fw/15:04
joschBoostisBetter: if you wonder which file you need, here is a table that maps the badge on your board to the firmware name: https://source.mnt.re/reform/reform-handbook/-/issues/415:05
- eibachd (QUIT: Ping timeout: 252 seconds) (~eibachd@p200300dcf73d8b00c1d59559971f6a9b.dip0.t-ipconnect.de)15:09
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)15:10
+ eibachd (~eibachd@p200300dcf73d8b0021b928a3353d7ccb.dip0.t-ipconnect.de)15:11
BoostisBetterthanks josch! All updated and good to go. 15:21
- eibachd (QUIT: Ping timeout: 246 seconds) (~eibachd@p200300dcf73d8b0021b928a3353d7ccb.dip0.t-ipconnect.de)15:21
BoostisBetterBy way of documentation improvement just pointing to the binary could also work. 15:22
BoostisBetterI would also mention that your Reform should be powered off for the LPC updating. If it is on, and you hit the reset switch the system is just turned off as power is cut. 15:22
joschBoostisBetter: good point -- it doesn't say that in the handbook either: https://mntre.com/reform2/handbook/parts.html#flashing-the-firmware15:23
joschand i think i remember others having asked the same question before15:23
+ eibachd (~eibachd@2a01:599:312:f688:3524:3627:abdf:9a09)15:26
joschBoostisBetter: thank you, I added the information that the motherboard should be off to https://source.mnt.re/reform/reform/-/merge_requests/4515:35
joschsevan: do you intend to fix up https://source.mnt.re/reform/reform/-/merge_requests/56? If you like, I can also create a new MR and do the work for you. Just tell me what works better for you. :)15:37
sevanjosch: if you're in the moment, feel free to go ahead, otherwise, I'll take a look later tonight.15:50
joschi'm not "in the moment" and would only schedule it to some time during the weekend :)15:50
sevanah, no worries then :)15:50
sevansaw the comment, suggetion makes sense, it would be helpful15:51
BoostisBetterSo I got my Reform in 2021, I believe. I had the firmware on it that came with it this whole time. Is there a place that kind of summarizes all of the change notes, or can we find that on the gitlab?15:53
joschBoostisBetter: i think currently only "git log" is there to tell you15:54
- eibachd (QUIT: Ping timeout: 255 seconds) (~eibachd@2a01:599:312:f688:3524:3627:abdf:9a09)16:22
- chomwitt (QUIT: Ping timeout: 245 seconds) (~chomwitt@ppp-94-67-191-45.home.otenet.gr)16:26
+ eibachd (~eibachd@2a01:599:306:b206:da76:1e1:21ab:5552)16:38
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)16:39
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:306:b206:da76:1e1:21ab:5552)16:51
+ eibachd (~eibachd@p200300dcf73d8b0015f84a5e9be57697.dip0.t-ipconnect.de)16:51
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf73d8b0015f84a5e9be57697.dip0.t-ipconnect.de)16:58
+ eibachd (~eibachd@2a01:599:306:b206:da76:1e1:21ab:5552)17:02
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:306:b206:da76:1e1:21ab:5552)17:05
+ eibachd (~eibachd@p200300dcf73d8b00fbf39dd192aef841.dip0.t-ipconnect.de)17:05
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf73d8b00fbf39dd192aef841.dip0.t-ipconnect.de)17:18
+ eibachd (~eibachd@p200300dcf73d8b00848722f71ebb9607.dip0.t-ipconnect.de)17:18
+ mjw (~mjw@gnu.wildebeest.org)17:31
- eibachd (QUIT: Ping timeout: 245 seconds) (~eibachd@p200300dcf73d8b00848722f71ebb9607.dip0.t-ipconnect.de)17:37
+ eibachd (~eibachd@p200300dcf73d8b00848722f71ebb9607.dip0.t-ipconnect.de)17:39
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)17:47
- jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@64.189.201.150)18:20
BoostisBetterso after updating the keyboard everytime I resume from suspend the keyboard backlight is on. Did it overwrite the suspend script or something?18:28
+ chomwitt (~chomwitt@2a02:587:7a09:c300:1ac0:4dff:fedb:a3f1)18:30
- chomwitt (QUIT: Remote host closed the connection) (~chomwitt@2a02:587:7a09:c300:1ac0:4dff:fedb:a3f1)18:34
+ chomwitt (~chomwitt@2a02:587:7a09:c300:1ac0:4dff:fedb:a3f1)18:34
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:7a09:c300:1ac0:4dff:fedb:a3f1)18:41
BoostisBetterin the past when this happened the rawhid changed, and so it is not properly handling that. 18:47
BoostisBetterI forget where to lock for the suspend service file though. Need to do some digging in that community thread. 18:47
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)19:02
- XYZ (QUIT: Read error: Connection reset by peer) (~XYZ@37-48-35-0.nat.epc.tmcz.cz)19:44
+ XYZ (~XYZ@37-48-35-0.nat.epc.tmcz.cz)19:49
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf73d8b00848722f71ebb9607.dip0.t-ipconnect.de)20:03
+ eibachd (~eibachd@p200300dcf73d8b0005c0b7fabda1b702.dip0.t-ipconnect.de)20:04
minuteBoostisBetter: maybe vkoskiv knows something about this, as he worked on the keyboard firmware20:04
joschminute: thank you for your toot about aerc -- i have been looking for new options for MUAs for a while now20:12
joschand maybe aerc does what i want better than what i have right now :)20:13
flowyjosch: confirmed gitlab ci build of reform-debian-packages w your patch20:23
joschnice :)20:24
- erle (QUIT: Quit: Just say no, then Putin can not legally invade your nation without your consent.) (~erle@2a02:8109:da40:c4:7c53:125e:e7e9:79ad)20:40
+ chaseadam (~achasen@2600:1700:e70:7f9f:cc6c:d0f5:78a1:52c0)22:09
chaseadamwhat is the expected behavior of CHG_LED1 and CHG_LED2? Should I expect them to turn off while external power is supplied?22:12
chaseadamI am having some difficulty tracking down where in the LPC, the STAT1 and STAT2 pins toggle. (been looking in reform/reform2-lpc-fw/src/boards/reform2/board_reform2.c)22:15
+ jacobk (~quassel@utdpat241106.utdallas.edu)22:15
+ chomwitt (~chomwitt@2a02:587:7a09:c300:1ac0:4dff:fedb:a3f1)22:45
minutechaseadam: lpc doesn't do it, they're ltc4020 status pins22:48
- Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66)23:10
- jacobk (QUIT: Ping timeout: 245 seconds) (~quassel@utdpat241106.utdallas.edu)23:22
+ jacobk (~quassel@129.110.242.224)23:44
- eibachd (QUIT: Remote host closed the connection) (~eibachd@p200300dcf73d8b0005c0b7fabda1b702.dip0.t-ipconnect.de)23:57
+ eibachd (~eibachd@p200300dcf73d8b0005c0b7fabda1b702.dip0.t-ipconnect.de)23:57

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