2022-07-31.log

- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf6815.dip0.t-ipconnect.de)00:12
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:dc12:b700:d6f4:2a4f:a8e:737)00:44
minutehttps://www.phoronix.com/news/FreeDesktop-GitLab-2022-Crash00:46
minuteah sorry, this was in june00:47
minuteis it down again? it is for me00:47
kfxminute: I get 502 errors00:52
kfxnow it just times out00:53
minuteyeah :/00:53
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)01:02
jfreddoes wifi work on plan9 on the reform?01:33
smjjfred, we currently have wired ethernet working.  I use an IOgear wired ethernet to wifi and power it off of one of the USB ports.  It works great when I need to be fully portable with the MNT reform.  wifi is coming. soon.01:39
jfred\o/01:40
smjAlso, we're working on audio.  Right now I use a Shure X2u USB audio interface for the microphone I'll use on the live stream01:41
- mtm (QUIT: Ping timeout: 244 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)02:04
nockoI hooked up a cheapie GL-iNET 6416 pocket router and it works very well for the reform (under 9front)02:48
nockoIt's a very nice experience (compared to Linux) on the reform.02:49
nockoIf you can live with (or prefer) the limitations of plan9 life.02:50
smjThankfully its very easy to try it out and it is a lot of fun.02:55
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)04:10
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)04:18
+ chartreuse (~chartreus@node-1w7jr9ql2247t9azo97sze19g.ipv6.telus.net)04:23
- qwer (QUIT: Ping timeout: 268 seconds) (~qwer@37.48.34.212)08:21
+ qwer (~qwer@37.48.16.15)08:23
- chartreuse (QUIT: Quit: Leaving) (~chartreus@node-1w7jr9ql2247t9azo97sze19g.ipv6.telus.net)08:25
+ chomwitt (~chomwitt@2a02:587:dc12:b700:9b5a:97ff:58b5:cbbb)09:11
- chomwitt (QUIT: Ping timeout: 240 seconds) (~chomwitt@2a02:587:dc12:b700:9b5a:97ff:58b5:cbbb)09:20
- qwer (QUIT: Ping timeout: 268 seconds) (~qwer@37.48.16.15)09:23
+ qwer (~qwer@78-80-98-239.customers.tmcz.cz)09:25
+ chomwitt (~chomwitt@2a02:587:dc12:b700:569a:41be:aae6:a6d5)10:20
- chomwitt (QUIT: Ping timeout: 240 seconds) (~chomwitt@2a02:587:dc12:b700:569a:41be:aae6:a6d5)10:33
+ Kooda (~kooda@natsu.upyum.com)11:04
+ Christoph_ (~Christoph@p54bf666b.dip0.t-ipconnect.de)12:26
+ MajorBiscuit (~MajorBisc@86-88-79-148.fixed.kpn.net)13:11
+ chomwitt (~chomwitt@2a02:587:dc12:b700:678b:e1a:f7b:532c)13:11
- chomwitt (QUIT: Remote host closed the connection) (~chomwitt@2a02:587:dc12:b700:678b:e1a:f7b:532c)13:13
+ chomwitt (~chomwitt@2a02:587:dc12:b700:3d3:74d8:b5ce:c91f)13:14
- cinap_lenrek (QUIT: Read error: Connection reset by peer) (~cinap_len@ns3076381.ip-147-135-136.eu)13:19
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:dc12:b700:3d3:74d8:b5ce:c91f)13:29
- mtm (QUIT: Ping timeout: 245 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)14:04
- buckket (QUIT: Ping timeout: 240 seconds) (~buckket@pdp8.buckket.org)15:12
+ buckket (~buckket@pdp8.buckket.org)15:13
- erle (QUIT: Ping timeout: 252 seconds) (~erle@ip5f5af7e0.dynamic.kabel-deutschland.de)15:25
+ erle (~erle@ip5f5af7e0.dynamic.kabel-deutschland.de)15:30
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)16:10
- sigrid (QUIT: Ping timeout: 272 seconds) (~sigrid@ftrv.se)16:38
+ sigrid (~sigrid@ftrv.se)16:41
- qwer (QUIT: Ping timeout: 252 seconds) (~qwer@78-80-98-239.customers.tmcz.cz)16:45
- sigrid (QUIT: Quit: leaving) (~sigrid@ftrv.se)16:47
+ sigrid (~sigrid@ftrv.se)16:48
+ qwer (~qwer@78-80-99-117.customers.tmcz.cz)16:53
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)16:58
bkeysminute: I got my Reform back and yes the charging circuitry is working as it was when it was brand new. They did a really really good job packaging the Reform so it was safe on it's way back18:30
bkeysThey completed the repair in 4 weeks which was what they originally told me to and it all cost me a little less than $280. I would recommend these people to anyone with a damaged Reform18:31
bkeysThe battery that was not showing on my OLED now shows. Once I have some time I'd like to get Fedora on this again, and I will also write a report about this and recommend them to the community18:31
bkeysjosch: So do you have updated steps to get the distroboot on here? I know things have progressed since I shipped this thing off to get repaired.18:32
bkeysI know I did saveenv and that seems to have messed stuff up. Is there a way I can flash a totally new uboot on here? Cause wiping the SD card doesn't seem to fix it.18:33
bkeysACTION is glad to have his Reform back.18:35
bkeysI like it a lot more than this pinebook pro. I just want to get Fedora working on the Reform18:35
vagrantcwiping the raw SD card? it's probably outside the partition tables18:36
bkeysI don't have the time at the moment to mess with it. I might get some tonight (I am in Eastern zone US)18:36
vagrantcbut yeah, saveenv is ... frustrating18:37
bkeysI just want the distroboot stuff so I can boot the EFI on mainline Fedora and get more mainline distro support for the Reform18:37
bkeysI didn't know saveenv was so bad when I did it18:38
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf666b.dip0.t-ipconnect.de)19:04
joschbkeys: i don't know how to get environment back from before you ran saveenv19:06
+ Christoph_ (~Christoph@p54bf666b.dip0.t-ipconnect.de)19:07
joschbkeys: essentially, this u-boot should give you distro_bootcmd: https://source.mnt.re/reform/reform-boundary-uboot/-/jobs/809/artifacts/browse19:08
vagrantcACTION would recommend disabling saveenv in the mnt/reform u-boot builds19:10
vagrantcthere are valid use-cases for it ... but ... it's easy to shoot yourself in the foot19:10
joschvagrantc: on the other hand, those who actively put effort in connecting to u-boot via serial are also most likely those who know what they are doing [tm]19:12
joschbkeys: make sure that your fedora boot partition has a /efi/boot/bootaa64.efi19:13
_nrb_normally env default -a or similar should reset everything to defaults, but it hasn't worked on my reform unfortunately. 19:13
vagrantcjosch: i've been maintaining u-boot in debian since ... 2012? 2013? and i don't trust myself with saveenv19:14
joschbkeys: the other thing you might have to set to make it work is the variable "fdtfile" which should point to the right *.dtb19:15
vagrantc_nrb_: well, it returns it to some conception of defaults, but not necessarily the same defaults as if you booted a system without running saveenv19:15
joschbkeys: after taking care of those two things I was able to boot the debian installer via efi19:15
vagrantcwhat did i say about saveenv being really complicated?19:15
joschvagrantc: maybe for bkeys to restore their default environment, somebody should dump theirs so that bkeys can copy that and save it?19:16
joschwould that work?19:16
_nrb_vagrantc: urgs, sorry I wasn't aware of that. weird. I have my uboot on the emmc in a somewhat messed up state now too... :/19:16
minutebkeys: great to hear, did you get any kind of diagnostic/report of what was wrong/what they fixed?19:17
vagrantcjosch: no, because you introduce the same problem that saveenv causes, just with a different saved environment19:19
vagrantcthe only way is to wipe where u-boot reads the environment ... which is different on every platform19:19
joschvagrantc: do you think an empty environment would be better?19:19
vagrantcu-boot has some built-in default environment that it uses if there is no environment stored in the boto media ... but it also typically sets some things in the environment at boot (which is why "env default -a" doesn't quite work the same)19:21
vagrantcfrom past attempts at resetting this, saving an empty environment gives you exactly that, an empty environment, not the built-in defaults19:21
joschoh dang :/19:22
vagrantcso, i suggest disabling saveenv as a "feature" if you can. :)19:22
vagrantcthose who know what they are doing can probably enable it. :)19:23
joschminute: what do you think about vagrantc's suggestion?19:23
minuteyes, disable in favor of boot scrs19:24
vagrantcthat said, wiping the whole SD *should* wipe out the environment ... unless it's saving to eMMC or SPI or something?19:24
minuteloading the env from emmc is too much of a footgun19:24
vagrantcACTION nods19:24
minuteif you are the person that needs saveenv you can reactivate this in uboot and compile/write your own19:25
vagrantcthe problem with saving the environment is reinstalling u-boot uses the old saved environment unless you manage to sucessfully wipe the sectors where the environment is being read from19:25
joschi thought the problem with saving the environment was the profit loss of large corporations! :D19:26
vagrantcACTION smiles contentedly19:27
joschvagrantc: this should do it, right? http://paste.debian.net/1248938/19:28
joschmaybe bkeys can try out if this really disables "saveenv" -- I'm too scared of trying that out as I want to avoid screwing up my u-boot env as well XD19:38
joschbkeys: https://source.mnt.re/reform/reform-boundary-uboot/-/merge_requests/819:39
dodospeaking of.. i can boot into my encrypted nvme, but need to decrypt it by hand in initramfs, and boot.. i think i know what went wrong..19:53
dodohm.. booting into the sd card again. so the normal boot process would be to boot the sd card into /usr/sbin/reform-init, and that switch over to the encrypted nvme? 20:18
dodothat switches20:19
joschdodo: the normal boot process used to be via sbin/reform-init but with sysimage-v3, full disk encryption works the same as in any other standard debian system via the initramfs20:26
dodohm, i have reform2-imx8mq off the main branch, that's not v3 is it?20:35
minutedodo: depends on how old that is20:36
dodobuilt it this week20:36
vagrantcjosch: that looks likely, yes20:44
vagrantcthere might also be a way to build a u-boot that doesn't even read the environment20:45
vagrantcthat would obviate the problem of a saved environment20:45
dodosuccess, booted into the nvme.. for some reason update-initramfs didn't seem to like that i had a keyfile configured for the device, removed that and it worked20:50
joschvagrantc: do you have any pointers on where to look so that it doesn't read the environment in the first place?21:05
vagrantcjosch: i had meant to look that up, but apparently got sidetracked with one of a a half-dozen other projects ... let me see :)21:06
vagrantcjosch: does it support CONFIG_ENV_IS_NOWHERE21:07
vagrantc?21:07
vagrantcrecent u-boot versions have that21:08
joschvagrantc: yup, it has that!21:08
- bleb (QUIT: Ping timeout: 272 seconds) (~cm@user/bleb)21:13
joschvagrantc: I think the culprit is CONFIG_ENV_IS_IN_MMC=y which results in board_late_mmc_env_init() getting called21:14
vagrantci see some weird conditional code so ENV_IS_NOWHERE might not be enough ... but it's worth a try21:16
vagrantcat least disabling saveenv will prevent/reduce future problems :)21:17
+ bleb (~cm@user/bleb)21:20
- bleb (QUIT: Ping timeout: 252 seconds) (~cm@user/bleb)21:37
joschbkeys: try building a u-boot with this patch before you copy mntreform-config to .config: http://paste.debian.net/1248948/21:44
joschbkeys: if it works, then this patch should result in your u-boot on sd-card not loading the environment from emmc and that in turn will ignore your bad environment after you used saveenv21:44
+ bleb (~cm@user/bleb)21:59
smjSetting up to stream from the MNT Reform now - details on https://9p.sdf.org/reform22:47
- buckket (QUIT: Remote host closed the connection) (~buckket@pdp8.buckket.org)23:12
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf666b.dip0.t-ipconnect.de)23:13
+ buckket (~buckket@pdp8.buckket.org)23:16

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