2023-09-11.log

- stites (QUIT: Read error: Connection reset by peer) (~stites@2607:fb91:dc1:d690:17dd:ae60:28fd:17ef)00:09
+ stites (~stites@2601:19c:4180:2fa0:2f0a:960b:48ea:b731)00:09
- S0rin (QUIT: Ping timeout: 248 seconds) (~S0rin@user/s0rin)00:16
+ S0rin (~S0rin@user/s0rin)00:17
- mtm (QUIT: Ping timeout: 248 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)00:18
- mjw (QUIT: Ping timeout: 246 seconds) (~mjw@gnu.wildebeest.org)00:29
- stites (QUIT: Ping timeout: 245 seconds) (~stites@2601:19c:4180:2fa0:2f0a:960b:48ea:b731)00:32
+ stites (~stites@2607:fb91:dc1:d690:17dd:ae60:28fd:17ef)00:33
- stites (QUIT: Read error: Connection reset by peer) (~stites@2607:fb91:dc1:d690:17dd:ae60:28fd:17ef)00:49
+ stites (~stites@130.44.147.204)00:50
+ chomwitt (~chomwitt@2a02:587:7a0c:4d00:1ac0:4dff:fedb:a3f1)01:15
- XYZ (QUIT: Ping timeout: 240 seconds) (~XYZ@37-48-2-145.nat.epc.tmcz.cz)01:19
- chomwitt (QUIT: Ping timeout: 255 seconds) (~chomwitt@2a02:587:7a0c:4d00:1ac0:4dff:fedb:a3f1)01:22
- Gooberpatrol66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66)01:30
- flowy (QUIT: *.net *.split) (~flowy@2a01:4f8:c0c:1a8f::1)02:00
- hl (QUIT: *.net *.split) (~hl@user/hl)02:00
- sigrid (QUIT: *.net *.split) (~sigrid@ftrv.se)02:00
- ethulhu (QUIT: *.net *.split) (ethulhu@nora.ethulhu.co.uk)02:00
- sevan (QUIT: *.net *.split) (~sevan@user/venture37)02:00
- natalie (QUIT: *.net *.split) (~natalie@user/natalie)02:00
- Asmadeus (QUIT: *.net *.split) (~asmadeus@240b:13:8c80:d300::42:13)02:00
- minute (QUIT: *.net *.split) (~mntirc@softboy.mntmn.com)02:00
- pinoaffe (QUIT: *.net *.split) (~pinoaffep@2a01:4f9:c010:a00b:1337:1337:11be:10)02:00
- Boostisbetter (QUIT: *.net *.split) (4a410829d7@irc.cheogram.com)02:00
- qbit (QUIT: *.net *.split) (~qbit@h.suah.dev)02:00
- yankcrime (QUIT: *.net *.split) (~nick@193.16.42.83)02:00
- sknebel (QUIT: *.net *.split) (~quassel@v22016013254630973.happysrv.de)02:00
+ yankcrime (~nick@193.16.42.83)02:00
+ flowy (~flowy@2a01:4f8:c0c:1a8f::1)02:00
+ minute (~mntirc@softboy.mntmn.com)02:00
+ qbit (~qbit@h.suah.dev)02:00
+ pinoaffe (~pinoaffep@2a01:4f9:c010:a00b:1337:1337:11be:10)02:01
+ sknebel (~quassel@v22016013254630973.happysrv.de)02:02
+ natalie (~natalie@user/natalie)02:04
+ hl (~hl@user/hl)02:05
+ sigrid (~sigrid@ftrv.se)02:05
+ Asmadeus (~asmadeus@M014009140128.v4.enabler.ne.jp)02:05
+ sevan (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)02:20
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)02:24
- sevan (QUIT: Changing host) (~sevan@2001:470:1f1d:1d6:5a55:caff:fe24:ed4)02:31
+ sevan (~sevan@user/venture37)02:31
- laumann (QUIT: Remote host closed the connection) (~quassel@user/laumann)03:03
+ laumann (~quassel@2a0a-e5c0-2-2-0-c8ff-fe68-bef1.loves.ipv6.at.ungleich.ch)03:05
- mtm (QUIT: Ping timeout: 255 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)03:07
violetany considerations i need to make when upgrading the SSD in the reform?03:26
violetor can i just use anytihng03:26
sknebeltheres a thread on the forums where people have posted about specific models and their experiences03:28
violetoh i should check that out03:28
violeti guess il just get the transcend one that seems fine enough03:35
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)03:37
- truck (QUIT: Server closed connection) (truck@shell.suomiscene.fi)03:37
+ truck (truck@shell.suomiscene.fi)03:38
- vagrantc (QUIT: Ping timeout: 246 seconds) (~vagrant@2600:3c01:e000:21:7:77:0:50)04:38
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)05:13
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)05:38
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)05:38
+ Boostisbetter (4a410829d7@irc.cheogram.com)06:37
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)07:24
- wstlr (QUIT: Server closed connection) (~wstlr@504e1bef.host.njalla.net)07:26
+ wstlr (~wstlr@504e1bef.host.njalla.net)07:26
+ ethulhu (ethulhu@nora.ethulhu.co.uk)08:24
- laumann (QUIT: Changing host) (~quassel@2a0a-e5c0-2-2-0-c8ff-fe68-bef1.loves.ipv6.at.ungleich.ch)08:48
+ laumann (~quassel@user/laumann)08:48
noamFor what it's worth I picked up a random NVMe drive at a local store and it JustWorked, but I also never thought about it09:13
noamAnd that's hardly evidence that _any_ would work09:13
joschthere are some that definitely do not work (Samsung 970 Evo)09:14
joschyou could leave a comment with the working one here: https://community.mnt.re/t/confirmed-working-nvme-drives/22409:15
+ mjw (~mjw@gnu.wildebeest.org)09:33
+ ggoes_ (~gregf@ool-44c1517f.dyn.optonline.net)10:05
- ggoes (QUIT: Ping timeout: 246 seconds) (~gregf@fsf/staff/ggoes)10:08
* ggoes_ -> ggoes10:08
+ XYZ (~XYZ@89-24-49-225.nat.epc.tmcz.cz)10:38
- ec0 (QUIT: Ping timeout: 244 seconds) (~ec0@vps-446f4f39.vps.ovh.ca)10:57
+ ec0 (~ec0@vps-446f4f39.vps.ovh.ca)11:00
- mjw (QUIT: Ping timeout: 245 seconds) (~mjw@gnu.wildebeest.org)11:10
- jfred (QUIT: Server closed connection) (sid534649@libera/sponsor/jfred)11:30
+ jfred (sid534649@libera/sponsor/jfred)11:30
* mark_ -> mjw11:32
- XYZ (QUIT: Ping timeout: 255 seconds) (~XYZ@89-24-49-225.nat.epc.tmcz.cz)11:45
grimmwareIt strikes me that a community wiki would be a good idea for stuff like that11:47
joschor better maintanance of the handbook? i've had https://source.mnt.re/reform/reform-handbook/-/issues/2 open for a long time now because a *lot* of things changed with respect to how the reform is booted since the handbook was written11:49
+ XYZ (~XYZ@89-24-49-225.nat.epc.tmcz.cz)11:51
minutejosch: yes, and i'm sorry for that! we have a project of overhauling the handbook coming very soon. also because the first print is sold out12:16
minutejosch: we will need to rewrite the handbook to accomodate a bunch of changes, incl. the new modules etc12:17
minutealso, 14x LS1028A modules are here now12:17
joschwohoo! \o/12:21
grimmwareminute: A community wiki would probably be really helpful not only for having e.g. information on what third party hardware is compatible but as a good point to crowdsource errata and contributions for the handbook in between iterations12:21
grimmwareI appreciate that's additional overhead though.12:21
minutegrimmware: yes, there were several people who wanted to set one up but none of them kind of went through with it12:22
minuteif it were run by community member(s) then we wouldn't be the bottleneck12:23
grimmwareyeah that makes sense12:23
grimmwarewelp I might come back round to it when I get my pocket but realisitically I'm not going to maintain a thing I don't have any use for yet12:23
joschdoesn't gitlab provide some wiki thing?12:23
minutejust someone with server space and admin experience would need to step up, and appoint some other(s) for community management / making sure that there's no vandalism etc12:24
minutejosch: yes, we can also check how that works, but we would need to funnel people through our gitlab account approval12:24
erlei think wikis are where data goes to die lol12:24
joschyeah, there is this "add wiki" button in projects on source.mnt.re -- no idea how good that is12:24
violetrealy appreciate the power port being on the side instaed of the back, its like one of my biggest qualms with my thinkpad. 12:24
violetconstant paranoia about flexing th connector too hard12:25
minuteerle: except for the arch wiki!12:26
josch(and gentoo wiki in the past before it broke)12:26
grimmwareman I love the arch wiki12:26
joschso, just add a reform article on onto the arch wiki and the problem will solve itself? ;)12:27
violeti could definithely sysadmin a wiki. if someone else handled running it from a community point of view12:27
grimmwarehahah12:27
erlejosch genius idea12:27
violetalso gentoo wiki is still good12:27
violeti always check both arch and gentoo wiki to cross reference12:28
violetgentoo wiki is often more realistic about the limitations of software than the arch wiki i find12:28
violetand stability of the software12:28
violetthe thing is that i feel like the forum+handbook combination already works well enough for most things youd want out of a wiki, for something as small in scope as the reform 12:30
violetlike its not *small* small but compared to something like a full linux distro you know12:30
grimmwareyeah that's fair12:30
violeti usually just use duckduckgo to search the forum12:31
joschnow with the imx8mq AB, there is even more SoM variety (even if unintentional)12:31
violetin my experience i find the git fjorge wikis to be a lot harder to navigate than a mediawiki though so im kinda negative on those12:32
violetand they dont get indexed as well by search engines i think12:32
violetlike mediawiki is noot actually that hard to run, used to admin one for work12:33
violetthe setup is just annoying12:33
violetbut anyways if theres demand for it i have the server space i can put towards it in my friend's colocated hardware12:34
violetbut i havent found myself itching for one myself12:35
erleif your wiki for a project that uses git is not in git you have yourself found a data graveyard btw12:36
erlebeen there, done that12:36
violetthat doesnt reflect my experiences12:37
violetmy main concern in that regard in the context of mnt is that theres so many repos12:37
violetyou need a way for people to know which repo has the wiki, ifyou attach the wiki to a repo12:38
violeti feel like readthedocs is not a bad solution though12:39
violetalways happy to see a readthedocs12:39
violetand then the wiki data is all in git iirc12:39
joschbut before setting up a readthedocs you might as well just fix up the handbook instead as both are centrally maintained12:41
violetyeah that is true12:41
violetand i really appreciate the handbook being available offlinee12:42
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)12:53
grimmwaresounds like doubling down on the handbook is probably the way to go.12:53
grimmwarelike I say, I don't have a reform yet so everything I'm saying here is super speculative12:54
grimmwarealso sorry for asking what colour the bikeshed should be ;)12:56
joschminute: seems that https://github.com/rbz-embedded-logics/uboot_ls1028 is 404?13:02
- eschaton (QUIT: Server closed connection) (~eschaton@li541-49.members.linode.com)13:07
+ eschaton (~eschaton@li541-49.members.linode.com)13:07
joschi'm currently perusing the ls1028a-dev branch of reform-system-image13:08
joschi wanted to create a reform-ls1028a-uboot script in the same way as i have for reform-a311d-uboot but then got that 404 :(13:10
- tarxvf (QUIT: Server closed connection) (~tarxvf@mail.tarxvf.tech)13:19
+ tarxvf (~tarxvf@mail.tarxvf.tech)13:20
- XYZ (QUIT: Remote host closed the connection) (~XYZ@89-24-49-225.nat.epc.tmcz.cz)13:25
+ XYZ (~XYZ@89-24-49-225.nat.epc.tmcz.cz)13:28
- stites (QUIT: Ping timeout: 240 seconds) (~stites@130.44.147.204)13:31
+ stites (~stites@2607:fb91:dc8:870c:e6db:e0fc:e90f:d41c)13:32
minutewe need to solve this terrible caam problem in 6.513:42
minutejosch: sorry, i guess it's private, i will clone it to source.mnt.re13:44
joschoooh okay :)13:44
joschindeed, the first thing that turns up in google if i search for the caam_jr probe error is the thread in community.mnt.re XD13:49
minute> you can echo y > /sys/module/cryptomgr/parameters/notests to turn off testing noise. the crypto testing is in bad shape even on x86_64 – it used to misbehave if compiled into the kernel but work ok if loaded as a module.13:56
minutei wonder if we can turn off crypto testing in the kernel build13:56
joschminute: if it's a module option, can it not be added to /etc/modprobe.d/reform.conf14:02
joschoptions cryptomgr notests=y14:02
- mtm (QUIT: Ping timeout: 245 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)14:02
minutejosch: ah, do we know it's a loadable module?14:04
minute(didn't check yet)14:04
joschsorry, i don't know that out of the top of my head14:04
minutejosch: https://source.mnt.re/reform/reform-ls1028a-uboot14:05
minutejosch: https://source.mnt.re/reform/reform-ls1028a-atf14:05
minutejosch: i'm pretty sure we should be able to use mainline uboot, but we need the custom atf because there we set the memory timings14:05
minutejosch: on ls1028a, all DDR4 stuff is done in hardware and some code in atf just gives the hardware the parameters for the DDR4 chips14:06
minutejosch: see https://source.mnt.re/reform/reform-ls1028a-atf/-/commit/f92edf5175b20fc82d7d17b4461ce3e1b968925414:06
joschmainline u-boot would be nice -- something to evaluate14:07
joschthough probably sensible to start with a known-to-work fork first14:08
minuteyep14:08
minutealso the kernel used in that process is antique14:08
minute(5.8?)14:08
joschyour latest screenshots were 5.12 i think14:09
minuteso i had some in-between versions for local testing14:09
minuteideally we update to the newest stuff soon. 14:09
joschyup :)14:09
joschREADME says that the first partition has to be fat32 but that probably is not a hard requirement as u-boot can read ext2 just fine, no?14:10
minutenot sure if the script has fatload hardcoded14:10
joschah right, moving to flash-kernel boot.scr is another task14:11
minutejosch: during QA here we just tried `options cryptomgr notests=y`, but it doesn't work. cryptomgr is also not in lsmod. as a workaround on the testing SD card we've put in `blacklist caam_jr`14:18
- stites (QUIT: Read error: Connection reset by peer) (~stites@2607:fb91:dc8:870c:e6db:e0fc:e90f:d41c)14:44
+ stites (~stites@130.44.147.204)14:44
- jacobk (QUIT: Ping timeout: 246 seconds) (~quassel@64.189.201.150)14:53
+ jacobk (~quassel@129.110.242.224)15:05
unixpoetgrimmware: chartreuse, clearly15:09
grimmwareokay so we know what colour community documentation should be.15:16
+ mark_ (~mjw@gnu.wildebeest.org)15:18
+ marty_mcfly88 (~marty@2603-6000-8c01-0f3e-d548-2094-b4d8-68d6.res6.spectrum.com)15:32
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)16:09
- XYZ (QUIT: Remote host closed the connection) (~XYZ@89-24-49-225.nat.epc.tmcz.cz)16:12
+ chomwitt (~chomwitt@2a02:587:7a0c:4d00:1ac0:4dff:fedb:a3f1)16:15
joschminute: is that module not ever needed or is it needed when setting up luks encryption? Because then it would not be ideal if reform-migrate copies that blacklisting over into a partition that is supposed to be decrypted later, no?16:56
minutejosch: it is generally needed, it's just a workaround for us during testing, it's not affecting the user install17:05
joschah kk17:05
minutejosch: i'm thinking to prepare the a311d uboot repo now. how do you imagine it to be? at first just a copy of the current script hat yields flash.bin?17:13
joschminute: exactly like the reform-a311d-uboot branch of reform-system-image: https://source.mnt.re/josch/reform-system-image/-/tree/reform-a311d-uboot?ref_type=heads17:14
joschthat branch already built a flash.bin for a311d17:14
minuteah great.17:15
- bleb (QUIT: Server closed connection) (~cm@user/bleb)17:18
+ bleb (~cm@user/bleb)17:18
minutejosch: https://source.mnt.re/reform/reform-a311d-uboot/17:19
joschminute: nice! now you have to somehow un-stuck the CI pipeline :)17:36
minutejosch: will do! but first, one question about the label based mounting. currently, it defeats the boot device priority feature in uboot, which boots in order: usb0, mmc1, mmc017:44
joschoh?17:45
minutejosch: but i used reform-flash-rescue (well, a subset of it) to install the "unified" image to flash (mmc0). the problem is that this then also has the reformsdboot and -root labels17:45
joschhow does it defeat that?17:46
joschah17:46
minutejosch: so a linux booted from sd card will then mount its root partition from emmc17:46
minutejosch: because it finds the disk label there first17:46
joschi totally forgot that reform-flash-rescue literally just dd's the image to emmc17:46
minuteyeah, i guess the fs needs to be touched up afterwards17:46
joschi'll prepare a merge request for reform-flash-rescue17:47
joschthe fs needs its labels changed and /etc/fstab its entries17:47
minuteexactly17:47
joschah, reform-boot-config is also imx8mq specific17:48
joschminute: https://source.mnt.re/reform/reform-tools/-/merge_requests/5017:55
joschat the end of reform-flash-rescue, reform-boot-config will write /dev/mmcblk... entries into /etc/fstab, overwriting the LABEL=reformsdboot entries17:56
minutejosch: ahhhh, i think i didn't use that17:57
joschwhat did you use?17:57
minutejosch: basically only the dd part17:57
joschminute: if you just dd, then /etc/fstab on emmc will be wrong17:58
minutejosch: yeah, true17:59
joschyou at least need to run reform-boot-config --emmc emmc afterwards17:59
minutewill try to do that now after the fact17:59
joschminute: alternatively, the reform-system-image pipeline could build another set of images targeted at the emmc, then you could just dd without modifying anything afterwards18:12
- marty_mcfly88 (QUIT: Remote host closed the connection) (~marty@2603-6000-8c01-0f3e-d548-2094-b4d8-68d6.res6.spectrum.com)18:16
minutejosch: yeah, but that's quite resource intensive18:20
minutejosch: strangely my last reform image build timed out after 2h... weird18:20
- jacobk (QUIT: Ping timeout: 246 seconds) (~quassel@129.110.242.224)18:20
minuteyour unified build will help i guess 18:21
+ jacobk (~quassel@129.110.242.224)18:22
- jacobk (QUIT: Ping timeout: 246 seconds) (~quassel@129.110.242.224)18:34
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)18:47
* mark_ -> mjw18:47
+ mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)18:47
minuteSeattle MNT Reform meetup on Sep. 19! https://community.mnt.re/t/next-seattle-reform-meetup-september-19/165218:54
violetyoooo lets go19:13
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)19:25
+ jacobk (~quassel@utdpat242016.utdallas.edu)19:49
- jacobk (QUIT: Ping timeout: 246 seconds) (~quassel@utdpat242016.utdallas.edu)20:00
+ jacobk (~quassel@129.110.242.173)20:13
- leonardo (QUIT: Server closed connection) (leonardo@user/leonardo)20:56
+ leonardo (leonardo@user/leonardo)20:56
+ varke (~varke@149.102.240.81)20:56
* varke -> v4rke20:57
- jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@129.110.242.173)20:58
- v4rke (QUIT: Quit: WeeChat 3.8) (~varke@149.102.240.81)21:12
- Boostisbetter (QUIT: Ping timeout: 252 seconds) (4a410829d7@irc.cheogram.com)21:24
+ Boostisbetter (4a410829d7@irc.cheogram.com)21:50
+ cwebber (~user@user/cwebber)22:06
+ jacobk (~quassel@64.189.201.150)23:10
- stites (QUIT: Ping timeout: 245 seconds) (~stites@130.44.147.204)23:44
+ stites (~stites@2607:fb91:dc9:4b54:4710:ea16:819c:2384)23:44
- stites (QUIT: Ping timeout: 252 seconds) (~stites@2607:fb91:dc9:4b54:4710:ea16:819c:2384)23:49

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