2024-07-20.log

bkeysIf andy didn't leave I was gonna tell him he can already non-destructively install Fedora on there, funnily enough that was the easy part01:07
bkeysBuilding the custom kernel and packaging that as an RPM is what is the high learning curve. Once this is done though I think the community will find interest in it and use it, and I will be very pleased with myself01:07
bkeysMy kernel build failed cause I had an errant line in the dts Makefile, I fixed it now; after that the build should work.01:08
joschbkeys: nice! i think it's important to keep building this regularly or otherwise this will quickly get out-of-date as newer kernels come in01:09
bkeysI agree, I have a script written that does all the changes once the fork is downloaded. Right now the plan is to not maintain a fork of the kernel source rather maintain this script that clones, goes to branches applies the changes, and gives me src.rpm to upload which maybe can also be done automatically01:10
bkeysI'm trying to make this the least manual as possible because I know I will be the maintainer of this01:11
bkeysI plan to publish all of my work once it's complete01:11
joschbkeys: that script sounds like what linux/build.sh in reform-debian-packages is doing for the Debian kernel01:12
bkeysMost likely, I might also try to patch the arm-image-installer from Fedora to include the Reform uboot image so that I can integrate this process with their tools01:13
bkeysCause then it would also make the CentOS-Stream thing seamless when that comes to fruition01:13
- mtm (QUIT: Ping timeout: 276 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net)02:02
+ mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net)02:05
+ andypiper (~andypiper@45.148.12.75)02:25
- andypiper (QUIT: Remote host closed the connection) (~andypiper@45.148.12.75)02:26
bkeysThis is the furthest my build has gotten with the patches and all included03:44
bkeysMaybe it will actually make it this time03:44
- nsc (QUIT: Ping timeout: 248 seconds) (~nicolas@216-98-142-46.pool.kielnet.net)03:51
+ nsc (~nicolas@i5C74DC43.versanet.de)03:53
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66)03:53
- mjw (QUIT: Ping timeout: 248 seconds) (~mjw@gnu.wildebeest.org)03:57
bkeyshttps://copr.fedorainfracloud.org/coprs/bkeys/kernel-reform/build/7763319/04:03
bkeysYESSS YES MY BUILD SUCCEEDED WITH ALL THE PATCHES AND DTB TIME TO TEST IT ON MY REFORM04:04
swivelminute: i dunno how involved you are in the day to day orders processing, but i ordered some merch and stuff for my reform - I think one thing had like a month lead time mentioned, in case it's not obvious I'd like it to just al lcome in a single shipment... it can take awhile if needed.04:08
bkeysminute: I know you are a busy person (who is likely asleep right now), but are you able to interpret this dmesg output at all when you read this? https://paste.centos.org/view/47408d1104:20
bkeysMine as well ping josch04:24
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)04:43
+ chrcav (~chrcav@user/chrcav)04:49
- skipwich_ (QUIT: Quit: DISCONNECT) (~skipwich@user/skipwich)05:02
+ skipwich (~skipwich@user/skipwich)05:05
bkeysI wonder if it's a DTB issue05:07
swivelthe use after free?05:20
+ jacobk (~quassel@2601:380:837e:24e0:b413:1241:5e3:eebd)05:22
- gsora (QUIT: Ping timeout: 252 seconds) (~gsora@user/gsora)05:59
+ gsora (~gsora@user/gsora)06:05
- jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@2601:380:837e:24e0:b413:1241:5e3:eebd)06:20
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-150-69.tukw.qwest.net)06:25
+ colinsane (~colinunin@97-113-150-69.tukw.qwest.net)06:28
- Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66)07:41
joschbkeys: but your system is starting up, no?07:43
joschlooks like you even got to loading systemd stuff07:43
joschand zram!07:43
joschlooks like meson_dw_hdmi is causing trouble07:46
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)08:07
+ chomwitt (~chomwitt@2a02:587:7a0d:7000:1ac0:4dff:fedb:a3f1)08:54
- noam (QUIT: Ping timeout: 245 seconds) (81879d1ffa@2a03:6000:1812:100::dfc)09:25
- romi (QUIT: Ping timeout: 245 seconds) (bd30729973@user/romi)09:25
+ noam (81879d1ffa@2a03:6000:1812:100::dfc)09:27
+ romi (bd30729973@user/romi)09:28
+ andypiper (~andypiper@45.148.12.75)09:47
Zabathe use-after-free in mmc_start_request doesn’t seem related to meson_dw_hdmi09:51
joschright, there is that one in the middle of dmesg09:52
- andypiper (QUIT: Ping timeout: 245 seconds) (~andypiper@45.148.12.75)09:52
joschbkeys: in any case, this is the first time i've seen this09:52
- chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:587:7a0d:7000:1ac0:4dff:fedb:a3f1)10:21
+ chomwitt (~chomwitt@2a02:587:7a0d:7000:1ac0:4dff:fedb:a3f1)11:06
- chomwitt (QUIT: Ping timeout: 245 seconds) (~chomwitt@2a02:587:7a0d:7000:1ac0:4dff:fedb:a3f1)11:13
+ mjw (~mjw@gnu.wildebeest.org)13:23
+ chomwitt (~chomwitt@2a02:587:7a0d:7000:1ac0:4dff:fedb:a3f1)13:39
bkeysjosch: The system does start up, I'm thinking of PM'ing the interested parties a user account and giving SSH access to those willing to help investigate14:02
- mtm (QUIT: Ping timeout: 248 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net)14:04
+ mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net)14:06
+ reform18772 (~andypiper@89.36.117.58)14:11
bkeysjosch: Have you had issue with zram in the past?14:12
- reform18772 (QUIT: Remote host closed the connection) (~andypiper@89.36.117.58)14:13
bkeysI'm using the patches for kernel 6.9 in the reform-debian-packages repo, this is a 6.9.9 kernel; I'm not sure if the slight mismatch is a potential reason14:14
bkeyshttps://paste.centos.org/view/10e91a3514:20
bkeysThe bottom section of this shows all the commands you run on the branch to set this kernel up, eventually it will be part of a script; if that helps at all14:21
- chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:587:7a0d:7000:1ac0:4dff:fedb:a3f1)14:35
joschbkeys: why first cp the dts and then rm them?14:44
+ andypiper (~Srain@89.36.117.58)14:44
joschbkeys: display is still off?14:44
joschbkeys: don't forget to run all the things /usr/sbin/reform-hw-setup runs when booting14:46
bkeysYeah sorry about the rm, that was from when I was still working on it; it isn't used anymore14:50
bkeysjosch: Display is still off14:50
joschbkeys: so the list of what makes the reform debian linux different from vanilla is: device tree, kernel patches, hw-setup script, kernel cmdline14:50
joschbkeys: in your text it says "Internal display isn't lighting up"14:51
bkeysOkay, to all outward appearance I have the kernel patches and device tree all goo14:51
bkeysgood14:51
joschbkeys: also make sure, that your fedora has a similar /proc/cmdline14:51
bkeysDo you have the needed kernel cmdline handy?14:51
bkeysHow early does hw-setup run in boot?14:51
joschthey are collected in the machines/*.conf14:52
joschi'm currently running a311d and i have this: ro no_console_suspend cryptomgr.notests loglevel=7 ro no_console_suspend console=ttyAML0,115200 pci=pcie_bus_perf libata.force=noncq nvme_core.default_ps_max_latency_us=0 console=tty1 console=tty114:52
bkeysWhat do you mean *.conf?14:54
bkeysLike systemd?14:54
joschbkeys: have a look at this file: https://source.mnt.re/reform/reform-tools/-/blob/staging/machines/MNT%20Reform%202%20with%20BPI-CM4%20Module.conf?ref_type=heads14:54
joschlast line has $BOOTARGS14:54
joschbkeys: this directory "machines" contains *.conf files for each platform14:55
bkeysI see14:55
joschthey contain machine readable information about each of the reform modules14:55
joschso that we do not have to hard-code this information everywher14:55
bkeysSo the other thing I'm wondering is where does the hw-setup script live in the repo?14:55
joschbut have one central place with it14:55
joschbkeys: https://source.mnt.re/reform/reform-tools/-/blob/staging/sbin/reform-hw-setup?ref_type=heads14:55
bkeysI pray to God it isn't too debian specific14:56
bkeysIt doesn't look like it14:56
bkeysAm I able to run this post boot to test it?14:56
joschbkeys: yes, it's using the contents of /proc/device-tree/model to do the right thing14:57
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@45.134.140.153)15:00
- andypiper (QUIT: Remote host closed the connection) (~Srain@89.36.117.58)15:16
+ andypiper (~Srain@89.36.117.58)15:18
+ bkeys (~Thunderbi@45.134.140.153)15:18
- andypiper (QUIT: Remote host closed the connection) (~Srain@89.36.117.58)15:18
bkeysSorry about that, ethernet cord got shot somehow15:18
+ andypiper (~Srain@89.36.117.58)15:19
bkeysjosch: So I'll add kernel params and then run the hardware setup script post boot to test it out15:19
+ bkeys1 (~Thunderbi@45.134.140.153)15:20
- bkeys1 (QUIT: Client Quit) (~Thunderbi@45.134.140.153)15:22
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@45.134.140.153)15:23
- andypiper (QUIT: Remote host closed the connection) (~Srain@89.36.117.58)15:26
+ bkeys (~Thunderbi@45.134.140.153)15:27
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@45.134.140.153)15:32
+ bkeys (~Thunderbi@45.134.140.153)15:33
bkeysjosch: So what user do I run hw-setup as? I'm guessing root?15:34
bkeysOkay I'm rebooting with these options added to the kernel "pci=pcie_bus_perf libata.force=noncq nvme_core.default_ps_max_latency_us=0"15:37
bkeysNow my switch decides to die and it's hard to distinguish between the network being bad and if the kernel is panicing after those extra args got passed15:44
bkeysIt must have been the network, I'm back in15:44
bkeysOkay I'm fixing to serial into this because the network isn't being reliable and I'll manually put these configs in and see what happens15:46
bkeysjosch: So I just run the hw setup script as root as a bash script?16:05
bkeysI'm booted with new cmdline args16:05
- Gooberpatrol66 (QUIT: Read error: Connection reset by peer) (~Gooberpat@user/gooberpatrol66)16:10
bkeysRunning hw setup yields a bunch of errors and no fixed problems16:10
joschbkeys: yes, reform-hw-setup requires superuser privileges16:18
bkeysYeah, it didn't solve it and I don't know that much about these patches16:18
joschbkeys: what are the error messages?16:19
bkeysIt's not finding the sound card, I'm guessing it's not finding the sound card, the display or the ethernet card16:19
bkeys1 sec16:19
bkeysStill doesn't detect my WD nvme drive -_-16:20
bkeysjosch: https://paste.centos.org/view/d15c739916:21
bkeysHere is the output of reform-hw-setup on a fresh boot with the kernel command line16:21
bkeyshttps://paste.centos.org/view/efc2f2a216:21
bkeysHere is the dmesg output as well16:21
joschbkeys: my daughter is here -- i'll be back in irregular intervals, sorry16:22
bkeysIt's fine, I gotta take some final exams for my last semester of college today as well16:22
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)16:27
+ murdock (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)16:51
- murdock (QUIT: Ping timeout: 248 seconds) (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)17:14
+ murdock (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)17:14
+ reform11818 (~esther@p200300f1171fe30097a9e8b62460b5a4.dip0.t-ipconnect.de)17:28
- reform11818 (QUIT: Client Quit) (~esther@p200300f1171fe30097a9e8b62460b5a4.dip0.t-ipconnect.de)17:30
- murdock (QUIT: Ping timeout: 255 seconds) (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)17:30
+ murdock (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)17:31
- mjw (QUIT: Ping timeout: 248 seconds) (~mjw@gnu.wildebeest.org)17:32
- chrcav (QUIT: Quit: leaving) (~chrcav@user/chrcav)18:13
- murdock (QUIT: Ping timeout: 252 seconds) (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)18:14
+ murdock (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)18:14
+ chomwitt (~chomwitt@2a02:587:7a04:8c00:1ac0:4dff:fedb:a3f1)18:21
+ mjw (~mjw@89.205.130.31)18:21
- murdock (QUIT: Ping timeout: 252 seconds) (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)18:35
+ murdock (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)18:36
- kensanata (QUIT: Read error: Connection reset by peer) (~alex@user/kensanata)18:40
+ mark_ (~mjw@89.205.131.144)18:40
- mjw (QUIT: Ping timeout: 276 seconds) (~mjw@89.205.130.31)18:41
+ kensanata (~alex@user/kensanata)18:56
- mark_ (QUIT: Ping timeout: 255 seconds) (~mjw@89.205.131.144)19:00
- chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:7a04:8c00:1ac0:4dff:fedb:a3f1)19:15
+ mjw (~mjw@89.205.132.135)19:16
+ mark_ (~mjw@89.205.134.245)19:33
+ andypiper (~Srain@45.148.12.75)19:34
- mjw (QUIT: Ping timeout: 260 seconds) (~mjw@89.205.132.135)19:35
- andypiper (QUIT: Remote host closed the connection) (~Srain@45.148.12.75)19:41
+ andypiper (~andypiper@45.148.12.75)19:43
- kensanata (QUIT: Remote host closed the connection) (~alex@user/kensanata)19:46
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@45.134.140.153)19:50
+ kensanata (~alex@user/kensanata)19:53
- mark_ (QUIT: Ping timeout: 260 seconds) (~mjw@89.205.134.245)19:53
+ mjw (~mjw@89.205.135.91)19:56
- chartreuse (QUIT: Ping timeout: 255 seconds) (~chartreus@S0106908d78501d1d.cg.shawcable.net)20:07
- mjw (QUIT: Ping timeout: 260 seconds) (~mjw@89.205.135.91)20:07
+ chartreuse (~chartreus@S0106908d78501d1d.cg.shawcable.net)20:13
- xktr (QUIT: Ping timeout: 246 seconds) (~xktr@user/xktr)20:31
+ xktr (~xktr@user/xktr)20:32
- andypiper (QUIT: Remote host closed the connection) (~andypiper@45.148.12.75)20:44
+ mjw (~mjw@213-10-231-91.fixed.kpn.net)20:45
jfredHmm, got my Pocket today but I'm having trouble finding a PD charger that'll charge it (enough to keep it powered anyway, it does seem to at least trickle charge from most). Maybe I'll try the firmware update from the forum21:16
- murdock (QUIT: Ping timeout: 248 seconds) (~murdock@dhcp-209-99-199-172.greenmountainaccess.net)21:37
+ murdock (~murdock@2600:382:6601:3f39:8968:f2e7:9bc4:c21)21:38
- murdock (QUIT: Ping timeout: 248 seconds) (~murdock@2600:382:6601:3f39:8968:f2e7:9bc4:c21)21:47
- chartreuse (QUIT: Ping timeout: 276 seconds) (~chartreus@S0106908d78501d1d.cg.shawcable.net)21:53
+ chartreuse (~chartreus@S0106908d78501d1d.cg.shawcable.net)21:53
minutejfred: the firmware update is highly recommended in that case!22:35
joschminute: what is the final choice for boot device order for a311d nvme boot?22:49
joschonce you finish that up, we could tag that u-boot version just as i recently tagged a new imx8mq u-boot version and put both into a new reform-tools release22:50
+ andypiper (~andypiper@194.35.123.56)23:07
- theesm (QUIT: Quit: Gateway shutdown) (~theesm@2a01:4f9:c011:adc3::)23:09
+ theesm (~theesm@static.134.243.21.65.clients.your-server.de)23:10
* andypiper -> andypiper[afk]23:49
- andypiper[afk] (QUIT: Quit: My device has gone to sleep. Zzzz…) (~andypiper@194.35.123.56)23:49
+ andypiper (~andypiper@194.35.123.56)23:51
- andypiper (QUIT: Ping timeout: 248 seconds) (~andypiper@194.35.123.56)23:56

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