2026-01-24.log

joscheery: okay, can you tell me exactly the ssd model you have? If it's not too expensive then I can try to reproduce it.00:08
eeryjosch: it's a crucial CT1000P3SSD8 -- I can do some building/testing if it'd help, maybe bisect it on a rainy weekend? I also uploaded the pcie and nvme data, might be useful to compare with your own system: https://bananamud.com/trace/nvme.txt00:19
- timide_ (QUIT: Quit: WeeChat 4.7.2) (~timide@user/timide)00:31
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)01:21
+ pomel0 (~pomel0@user/pomel0)01:21
- paperManu_ (QUIT: Ping timeout: 244 seconds) (~paperManu@146.71.9.156)02:23
- paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@146.71.9.156)03:02
- nsc (QUIT: Ping timeout: 245 seconds) (~nicolas@i5C74DDCC.versanet.de)03:46
+ nsc (~nicolas@i5C74DCE3.versanet.de)03:48
- spew (QUIT: Read error: Connection reset by peer) (~spew@user/spew)03:57
+ spew (~spew@user/spew)03:57
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)04:36
+ pomel0 (~pomel0@user/pomel0)04:36
- spew (QUIT: Ping timeout: 265 seconds) (~spew@user/spew)04:40
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)04:47
+ pomel0 (~pomel0@user/pomel0)04:50
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)05:26
+ pomel0 (~pomel0@user/pomel0)05:26
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)05:32
+ pomel0 (~pomel0@user/pomel0)05:34
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)05:51
+ pomel0 (~pomel0@user/pomel0)06:03
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)06:42
+ pomel0 (~pomel0@user/pomel0)06:43
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)06:49
+ pomel0 (~pomel0@user/pomel0)06:52
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)06:56
+ pomel0 (~pomel0@user/pomel0)06:56
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)07:04
+ pomel0 (~pomel0@user/pomel0)07:04
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)08:02
+ pomel0 (~pomel0@user/pomel0)08:06
- pomel0 (QUIT: Ping timeout: 256 seconds) (~pomel0@user/pomel0)08:11
+ pomel0 (~pomel0@user/pomel0)08:22
- pomel0 (QUIT: Ping timeout: 245 seconds) (~pomel0@user/pomel0)08:27
+ pomel0 (~pomel0@user/pomel0)08:34
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)08:44
+ pomel0 (~pomel0@user/pomel0)09:12
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)09:28
+ pomel0 (~pomel0@user/pomel0)09:29
Svpoh right just in case i didnt understand the docs, when i use the rcm4 with a raspi i do NOT need to use the dsi connector, since it's using hdmi out, right?10:22
- kensanata (QUIT: Quit: OK) (~alex@user/kensanata)10:25
+ kensanata (~alex@user/kensanata)10:25
+ trypokarydos (~linx@149.210.3.83)10:39
- Ar|stote|is (QUIT: Ping timeout: 246 seconds) (~linx@149.210.3.83)10:40
+ AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net)11:46
- gianmarcogg03 (QUIT: Quit: https://quassel-irc.org - La chat diventa comoda. Ovunque.) (~quassel@user/gianmarcogg03)12:07
+ johl (~johl@wikidata/Jens-Ohlig)12:20
johlHi there, still trying to get my pocket reform unbricked :)12:23
johlI think I need some help.12:24
minutejohl: i can help!12:25
johlI am on the rescue system that I booted from an SD card12:25
minutei'm also back in berlin finally12:25
johl\o/12:25
minutebtw came here to post a related TIL https://mastodon.social/@kbm0/11594971402512897612:26
joschjohl: i wrote you an email about that12:26
minuteSvp: correct, back in the day i couldn't get dsi to edp work on the pi412:27
minuteSvp: but also i wasn't mega experienced then. iirc there was a hard limitation on the pi4 dsi clock rates that wouldn't match what the ti dsi to edp converter chip supports. thus came the dsi to hdmi converter module (which you hopefully have?)12:28
minuteSvp: sorry, not fully awake yet. hdmi to edp i mean12:28
Svpminute: yeah i do have it, i just wanted to make sure because there is no mention, positive or negative, about it in the rcm4 raspi leaflet12:29
joschminute: you might've learned about the dropbear-initramfs standard too late -- debian is currently switching the standard to dracut12:29
johljosch: I cannot find that :(12:30
minuteSvp: oh i see.12:32
joschjohl: this sounded like you so i wrote to one of the addresses in the metadata: https://www.johl.io/12:33
minutejosch: i need to read up on dracut then. afaik that's a different way to generate initramfs?12:33
joschminute: yes, debian is adapting what everybody else uses12:33
joschinitramfs-tools is a debianism12:33
joschit doesn't mean that initramfs-tools is unsupported -- it's a change of the default12:34
joschinitramfs-tools will be supported for as long as somebody cares as usual12:34
minutejosch: oh nice, i wonder if that'll make initramfs generation faster as well?12:34
joschyes12:34
minuteniiiice12:34
minutejohl: iirc josch made a rescue tool in the meantime12:35
joschoh this reminds me12:37
joschah never mind -- i thought the initramfs generator was already switched with 6.1812:38
joschoh it was12:39
joschso maybe the nvme problems with 6.18 are actually initramfs generation problems?12:39
joschmaybe a module didn't get included?12:39
lidstahfrom what I saw with a debian trixie VM, update-initramfs -u -v uses dracut under the hood, indeed - and it's way faster than before (to the point I was wondering if I made a mistake :p, hence the -v), and hi everyone!12:41
lidstah(the goal was just to add dropbear in order to run crypt-tools through ssh)12:42
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)13:32
+ pomel0 (~pomel0@user/pomel0)13:33
+ paperManu (~paperManu@146.71.9.156)13:37
minutejosch: hmm interesting. or new race conditions from different module load order13:59
minutejosch: unfortunately today is again not a good day for me to experience this breakage as i need my pocket in working order @ home this weekend :D (barebox is already a stunt). but monday i can expose myself13:59
- pomel0 (QUIT: Ping timeout: 255 seconds) (~pomel0@user/pomel0)14:02
+ pomel0 (~pomel0@user/pomel0)14:02
minutehi lidstah! what was the recipe to add ssh/dropbear to initramfs with dracut?14:04
- pomel0 (QUIT: Ping timeout: 245 seconds) (~pomel0@user/pomel0)14:17
+ pomel0 (~pomel0@user/pomel0)14:18
- pomel0 (QUIT: Ping timeout: 250 seconds) (~pomel0@user/pomel0)14:22
+ pomel0 (~pomel0@user/pomel0)14:43
johlJaaaaaaaaaaaaaa14:54
johlIt's alive!14:54
johlThank you @josh for all the help. 14:54
johlAhem, @josch14:55
josch\o/14:57
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)14:57
+ pomel0 (~pomel0@user/pomel0)14:57
joschminute: can barebox load /boot from nvme? Because the latest MNT u-boot for a311d and rk3588 can do that and it would be sad to have this feature regress with barebox.15:03
minutejosch: it can, buttt there is a big caveat, pcie3.0 phy might not be supported yet in bb (this could be outdated info though) so it wouldn't work on classic and next. but nvme is detected on pocket where nvme is on pcie2.015:13
minutejohl: oh great! what was the solution?15:13
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)15:14
minutejosch: but in worst case we can also try to port the pcie 3 phy stuff15:14
joschminute: i fear i know what you mean by "we" :D15:16
joschhrm... but here is a bit of a problem for users: when they upgrade their bootloader, they also need to make sure to install whatever installs the spec files or otherwise their system won't boot15:17
joschand we cannot roll that out ahead of time because flash-kernel *either* produces a boot.scr *or* a bootspec file15:18
joschonly users of u-boot-menu would be safe from having their system unbootable15:18
joschwe could talk with vagrantc about this when he comes online15:19
+ pomel0 (~pomel0@user/pomel0)15:19
joschor does u-boot maybe also understand the spec files?15:21
joschreform-tools should probably get into the business of generating spec files because it has to anyways or otherwise the reform-system-any images would not have spec files (unless the code to produce them lives in reform-system-image:mkimage.sh)15:24
- pomel0 (QUIT: Ping timeout: 245 seconds) (~pomel0@user/pomel0)15:33
+ siviq (~siviq@user/siviq)15:33
+ pomel0 (~pomel0@user/pomel0)15:33
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)15:44
+ pomel0 (~pomel0@user/pomel0)15:45
- siviq (QUIT: Quit: Client closed) (~siviq@user/siviq)15:50
+ paperManu_ (~paperManu@146.71.9.156)15:55
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)16:00
+ pomel0 (~pomel0@user/pomel0)16:00
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)16:04
+ pomel0 (~pomel0@user/pomel0)16:06
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)16:11
+ pomel0 (~pomel0@user/pomel0)16:11
+ siviq (~siviq@user/siviq)16:20
minutejosch: yeah, fortunately the format is easy16:21
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)16:22
+ gianmarcogg03 (~quassel@user/gianmarcogg03)16:24
joschminute: let me know once you have a spec file that works for you16:25
johlminute: There was more then one thing, I think. The upgrade didn't fully work and thus no kernel. The rescue-shell by josch helped, though. At some point I lost connection to the wifi card, but a reboot fixed that and eventually the upgrade went through 16:27
+ pomel0 (~pomel0@user/pomel0)16:28
- johl (QUIT: Quit: leaving) (~johl@wikidata/Jens-Ohlig)16:30
joschminute: the wifi card didn't show up for johl which also others with kernel 6.18 reported16:31
+ johl (~johl@wikidata/Jens-Ohlig)16:31
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)16:32
+ pomel0 (~pomel0@user/pomel0)16:35
+ spew (~spew@user/spew)16:39
chthe iwlwifi? in my pocket the iwlwifi driver crashed all the time on first reboot into 6.18. after a power cycle it was ok16:42
joschwhy did i never see this with 6.18?16:44
josch(on pocket with ax201 wifi )16:44
- spew (QUIT: Quit: zzz) (~spew@user/spew)16:54
- pomel0 (QUIT: Ping timeout: 245 seconds) (~pomel0@user/pomel0)16:55
+ pomel0 (~pomel0@user/pomel0)16:55
joschokay, we currently cannot deploy fixes in reform-debian-packages because mesa ftbfs because libclc is uninstallable because llvm-toolchain ftbfs (#1125733) because cmake 4 was uploaded to unstable a few days ago (#1113237) -- i love unstable17:01
minutejosch: i have a working one in the repo! since last night17:11
minutejosch: in the ci-202601 branch17:11
minutejosch: also added a bunch of random notes17:11
joschthagnk you i also found README-mnt.md17:12
minutejohl: ok, great to hear the tool was useful17:12
joschminute: looking at the bootspec i also wonder if this keeps platform-specific kernel cmdline args like it was done using ${bootargs} in u-boot17:15
joschlots of new things to learn :)17:15
joschi wonder if the answer is to move the device-specific knowledge from the bootloader into the bootspec files. Since barebox will select the right bootspec file, maybe the information should indeed be removed from the bootloader and moved into the /boot partition.17:20
joschwith u-boot we only had a single extlinux.conf so we had to rely on inheriting ${bootargs} for platform-specific info17:21
joschthis was not a problem with boot.scr because there we could script in board-specific bootargs with an if/else17:21
joschokay, yes, i think that should work -- somebody correct me if i'm wrong :)17:22
joschbut yes, i think us relying on u-boot populating ${bootargs} was because we wanted to use extlinux.conf and that one allowed no device specific conditionals17:22
lidstahminute: sorry for the late answer, but nothing really different from, let's say, bookworm dropbear initramfs installation: install dropbear-initramfs, configure it (/etc/dropbear/initramfs/dropbear.conf, DROPBEAR_OPTIONS="-I 120 -j -k -p 2222 -s -c cryptroot-unlock") + copy a valid pubkey (or more) in a authorized_keys file in the same path, add an IP= line in17:27
lidstah/etc/initramfs-tools/initramfs.conf, then update-initramfs -u (-v if you want verbose))17:27
lidstahreboot, ssh -p 2222 root@IP, unlock the drive, then ssh as usual :)17:28
+ spew (~spew@user/spew)17:29
lidstahbut now it's dracut-install doing the job17:29
lidstahbbl, playing with my son :)17:29
minutelidstah: very nice, thanks17:40
minutejosch: i think your train of thought is correct. 17:41
joschthank you for confirming!17:42
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)17:50
+ pomel0 (~pomel0@user/pomel0)17:51
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)17:56
+ pomel0 (~pomel0@user/pomel0)17:56
lidstahminute: it's great when you don't have hypervisor console/IPMI/iDRAC/iLO/OOB access but still want to use LUKS on a VM or baremetal server - might be useful too if you lose display on a machine with LUKS encrypted drives: as long as you can use dropbear ssh to unlock the root partition and then SSH into the machine… you can debug :)17:58
lidstahstill better than blindly typing the passphrase :)17:58
joschyup, i've been using dropbear ssh to unlock my VPS at hetzner for a decade17:59
+ murphnj (~murph@user/murphnj)17:59
lidstahthat's what we advise to our VM users at a local not-for-profit ISP here17:59
lidstahso they don't have to login into proxmox just for unlocking their drives :)18:00
- paperManu (QUIT: Ping timeout: 255 seconds) (~paperManu@146.71.9.156)18:01
lidstah(which means two less steps: no need to connect to the out of band vpn then login into proxmox then type their passphrase)18:01
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)18:31
- pomel0 (QUIT: Ping timeout: 244 seconds) (~pomel0@user/pomel0)19:09
joschhrm... a311d graphics keep blanking sometimes when i do swaymsg "output * dpms off" via swayidle and doesn't come back. Does somebody see something interesting from the last things sway wrote on stdout before this happened? https://paste.debian.net/hidden/554d704a19:09
+ pomel0 (~pomel0@user/pomel0)19:33
- pomel0 (QUIT: Ping timeout: 252 seconds) (~pomel0@user/pomel0)19:44
- siviq (QUIT: Ping timeout: 272 seconds) (~siviq@user/siviq)20:55
+ pomel0 (~pomel0@user/pomel0)21:04
- johl (QUIT: Remote host closed the connection) (~johl@wikidata/Jens-Ohlig)21:11
+ johl (~johl@wikidata/Jens-Ohlig)21:13
- johl (QUIT: Client Quit) (~johl@wikidata/Jens-Ohlig)21:16
+ paperManu (~paperManu@146.71.9.156)21:17
+ johl (~johl@wikidata/Jens-Ohlig)21:17
- johl (QUIT: Client Quit) (~johl@wikidata/Jens-Ohlig)21:17
+ siviq (~siviq@user/siviq)21:18
+ johl (~johl@wikidata/Jens-Ohlig)21:32
- johl (QUIT: Client Quit) (~johl@wikidata/Jens-Ohlig)21:34
+ johl (~johl@wikidata/Jens-Ohlig)21:35
- johl (QUIT: Client Quit) (~johl@wikidata/Jens-Ohlig)21:35
- pomel0 (QUIT: Ping timeout: 255 seconds) (~pomel0@user/pomel0)21:36
+ pomel0 (~pomel0@user/pomel0)21:39
- pomel0 (QUIT: Ping timeout: 260 seconds) (~pomel0@user/pomel0)21:44
+ pomel0 (~pomel0@user/pomel0)21:47
joschminute: does this look good? https://paste.debian.net/hidden/4eea44f721:54
joschThe kernel postinst hook which generates this is part of https://source.mnt.re/reform/reform-tools/-/merge_requests/15821:54
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)22:01
+ pomel0 (~pomel0@user/pomel0)22:04
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)22:08
- mjv (QUIT: Remote host closed the connection) (~matt@user/reform11910)22:09
+ pomel0 (~pomel0@user/pomel0)22:09
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)22:23
+ pomel0 (~pomel0@user/pomel0)22:23
- siviq (QUIT: Ping timeout: 272 seconds) (~siviq@user/siviq)22:27
- AnimaInvicta (QUIT: Ping timeout: 240 seconds) (~AnimaInvi@88-120-179-216.subs.proxad.net)22:42
+ AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net)22:44
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)22:44
+ pomel0 (~pomel0@user/pomel0)22:49
vagrantcwith 6.18.7 reform-debian-packages/linux/patches6.18/rk3588-mnt-reform2/0105-WIP-FRL-drm-bridge-dw-hdmi-qp-Add-HDMI-2.1-FRL-suppo.patch no longer applies and 0142-drm-bridge-dw-hdmi-qp-Fix-spurious-IRQ-on-resume.patch appears to be applied upstream ... building without either so far and will test at least basic functionality22:57
joschvagrantc: https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/16222:59
vagrantchah. obviously i should have checked first :)23:02
vagrantcwill check with that series too :)23:04
joschvagrantc: rk3588 might switch from u-boot to barebox and that means a switch from boot.scr/extlinux.conf to https://uapi-group.org/specifications/specs/boot_loader_specification/23:04
joschvagrantc: would you recommend flash-kernel as a good tool to generate bootspec files?23:04
vagrantcoh my23:04
vagrantci do not recommend flash-kernel for anything :P23:05
joschthank you :)23:05
joschi now wrote a small kernel hook for reform-tools which might be enough23:05
vagrantcflash-kernel needs a rewrite ... but nobody has managed the energy or enthusiam to do so ... but as far as i am conerned it should only be used for legacy things23:06
vagrantcbut because it is there people keep bolting more hacks onto it23:06
joschokay, i'll try hard not to use it going forward then23:07
vagrantci mean, maybe i'm wrong, and it's just fine :)23:08
joschmeh, generating these files might be easy enough :)23:08
joschand then we have flash-kernel to create boot.scr, u-boot-menu for extlinux.conf and reform-tools for /boot/loader/entries/*.conf23:08
joschand then wherever you put that image maybe the bootloader will understand one of them :)23:09
vagrantcright23:09
vagrantcdon't forget EFI support :)23:09
joschthere is a branch for that!23:10
vagrantcwhich u-boot implements to a large degree ...23:10
joschand it already boots23:10
joschbut i have no idea how to make efi support board-agnostic23:10
joschwhen i create an uki image it seems i have to bake in the dtb23:10
vagrantci *think* grub-efi can just take whatever device tree is already loaded by the bootloader23:11
vagrantcbut then you get into issues with kernel/device-tree mismatches ... which in theory should be ok, but ...23:12
joschit is not okay in practice23:12
vagrantcexactly :)23:12
joschi already have fedora booting via efi and i see it re-uses the dtb from u-boot23:13
joschbut the dtb is kernel version specific23:13
vagrantcwe're all holding it wrong, but at least we're all holding something23:13
vagrantcdefinitely curious to see how barebox goes ... heard some good news regarding mnt/pocket rk3588 ... would love to see it on the bigger sibling :)23:15
joschvagrantc: it works on the classic but display is not yet done there23:17
joschhat is, unless you use hdmi23:17
vagrantcoh, that's promising regardless :)23:19
- pomel0 (QUIT: Ping timeout: 240 seconds) (~pomel0@user/pomel0)23:32

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