2026-09-19.log

- ce (QUIT: Quit: Client closed) (~ce@163.252.102.62)00:06
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)00:29
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)00:29
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)00:33
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)00:33
- paperManu_ (QUIT: Ping timeout: 257 seconds) (~paperManu@173.206.254.242)00:43
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)01:00
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)01:00
- enwu (QUIT: Ping timeout: 240 seconds) (~enwu@user/enwu)01:21
+ enwu (~enwu@user/enwu)01:22
+ simba (~simba@148.56.62.122)01:22
+ spacematty (41cc4b39e0@irc.cheogram.com)01:26
- simba (QUIT: Ping timeout: 265 seconds) (~simba@148.56.62.122)01:26
- enwu (QUIT: Ping timeout: 248 seconds) (~enwu@user/enwu)01:29
+ enwu (~enwu@user/enwu)01:30
+ simba (~simba@148.56.62.122)01:53
- simba (QUIT: Ping timeout: 251 seconds) (~simba@148.56.62.122)01:58
+ bkeys (~Thunderbi@71.31.254.246)02:53
- vkoskiv (QUIT: Ping timeout: 244 seconds) (~vkoskiv@user/vkoskiv)03:00
- paperManu (QUIT: Ping timeout: 260 seconds) (~paperManu@173.206.254.242)03:41
- spew (QUIT: Quit: nyaa~) (~spew@user/spew)03:45
+ spew (~spew@user/spew)03:46
- loon (QUIT: Quit: ZNC 1.10.2 - https://znc.in) (~luna@user/loon)04:43
+ loon (~luna@user/loon)04:45
+ bkeys1 (~Thunderbi@h246.254.31.71.dynamic.ip.windstream.net)04:46
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@71.31.254.246)04:49
- bkeys1 (QUIT: Read error: Connection reset by peer) (~Thunderbi@h246.254.31.71.dynamic.ip.windstream.net)04:49
+ bkeys2 (~Thunderbi@71.31.254.246)04:49
* bkeys2 -> bkeys04:52
- bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@71.31.254.246)05:25
+ simba (~simba@148.56.62.122)06:11
- simba (QUIT: Ping timeout: 265 seconds) (~simba@148.56.62.122)06:16
- tomenzgg (QUIT: Ping timeout: 252 seconds) (~tomenzgg@user/tomenzgg)06:59
+ simba (~simba@148.56.62.122)08:14
- simba (QUIT: Ping timeout: 260 seconds) (~simba@148.56.62.122)08:18
- marty (QUIT: Ping timeout: 260 seconds) (~marty@static-23-234-100-205.cust.tzulo.com)10:34
+ marty (~marty@146.70.166.174)10:36
+ simba (~simba@148.56.62.122)12:18
- simba (QUIT: Ping timeout: 264 seconds) (~simba@148.56.62.122)12:22
+ paperManu (~paperManu@173.206.254.242)13:08
bremnerhow does unlocking LUKS on boot work with u-boot? Is there anything special, or cryptsetup in the initrd works like on the x86 PCs I'm used to?13:31
bremneroh, thinking about an NVME partition, if it matters13:32
minutebremner: all happens in initrd, so no difference there afaik13:37
bremnerthanks13:44
joschbremner: nothing special unless you start doing EFI stuff. The biggest difference to x86 is that instead of just vmlinuz and initrd, you also have to pass a device tree when booting. On x86 the latter isn't needed.14:16
bremnerack14:29
+ mjw (~mjw@gnu.wildebeest.org)14:41
+ bkeys (~Thunderbi@71.31.254.246)15:34
minuterecently i had some funky thoughts about it might be fun to try to code an auto hardware discovery thing for arm6416:02
minutelike, not seriously, more like hobby grade16:03
minuteotoh i'll need to read up on https://www.arm.com/architecture/system-architectures/systemready-compliance-program/systemready-band16:07
+ fizzo (~fizzo@81.56.178.209)16:11
bremnerDo I need to do something special to get u-boot to boot from nvme? I have u-boot-menu installed on emmc if that matters17:18
bremner(pocket reform)17:18
bremnerideally I'd like to be able to choose between emmc (Debian) and nvme (guix-sd), but I bet I need the serial console for that17:19
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)17:21
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)17:21
+ simba (~simba@148.56.62.122)17:22
stephanominute: Ah, Arm SystemReady. Good thing to read up on. Keep in mind though, SystemReady is an opt-in, self-declared boot-and-install contract, not the market-enforced hardware baseline x86 gives you. So one verifies each platform beyond boot. For example, EBBR permits UEFI runtime services that don't behave like x86. The API surface is UEFI, but the semantics are the subset EBBR chose, and the17:23
stephanodifferences only show up when a distro does something x86 taught it to expect.17:23
- simba (QUIT: Ping timeout: 256 seconds) (~simba@148.56.62.122)17:27
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)17:27
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)17:28
stephanoFor example, switching between an eMMC OS and an NVMe OS with efibootmgr -n needs writable UEFI variables at runtime, and under EBBR/U-Boot they often aren't writable.17:31
stephanoNot that I've spent long hours debugging things like this only to learn they were not implemented like x86 and that fact was burried deep inside documentation somewhere. That certainly never happened. :)17:36
- murphnj (QUIT: Ping timeout: 257 seconds) (~murphnj@user/murphnj)17:36
+ murphnj (~murphnj@user/murphnj)17:36
- voltaire28 (QUIT: Quit: WeeChat 4.6.3) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)17:46
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)17:48
- voltaire28 (QUIT: Client Quit) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)17:49
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)17:49
- voltaire28 (QUIT: Client Quit) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)17:49
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)17:52
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)18:02
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)18:04
- voltaire28 (QUIT: Quit: WeeChat 4.6.3) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:12
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:12
- voltaire28 (QUIT: Client Quit) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:13
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:14
- voltaire28 (QUIT: Client Quit) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:16
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:16
- voltaire28 (QUIT: Quit: WeeChat 4.6.3) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:24
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:25
- voltaire28 (QUIT: Client Quit) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:26
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:26
- voltaire28 (QUIT: Client Quit) (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)18:27
+ S0rin (~S0rin@user/s0rin)18:49
+ vkoskiv (~vkoskiv@109-204-186-7.cust.valoonet.fi)19:00
loonstephano: SystemReady isn't PC BIOS, for sure, but it's still a good place to start for a hobby project :)19:25
minutestephano: uff19:54
+ simba (~simba@148.56.62.122)20:25
- simba (QUIT: Ping timeout: 261 seconds) (~simba@148.56.62.122)20:30
stephano loon: oh certainly worth reading up on. Just fair warning, ymmv. :)20:43
+ voltaire28 (~jlafon@2001:4b98:dc0:43:f816:3eff:feb2:df85)20:46
- marty (QUIT: Ping timeout: 246 seconds) (~marty@146.70.166.174)21:12
+ marty (~marty@146.70.166.174)21:14
- spew (QUIT: Ping timeout: 249 seconds) (~spew@user/spew)21:14
+ g3ist (~geist@user/g3ist)21:25
+ spew (~spew@user/spew)21:31
+ kfx (~kfx@grendel.sciops.net)22:09
kfxminute: I heard you wanted to 'age out' ipset entries.  You can do this by adding 'timeout <number of seconds>' to the 'ipset add' command e.g. 'ipset add setname 127.0.0.1 timeout 86400' 22:11
kfxto update existing entries you can do 'ipset -exist add setname 127.0.0.1 timeout 6000'22:12
+ simba (~simba@148.56.62.122)22:22
- simba (QUIT: Ping timeout: 259 seconds) (~simba@148.56.62.122)22:29
- marty (QUIT: Ping timeout: 264 seconds) (~marty@146.70.166.174)22:33
+ simba (~simba@148.56.62.122)22:34
+ marty (~marty@static-23-234-100-205.cust.tzulo.com)22:41
- simba (QUIT: Ping timeout: 248 seconds) (~simba@148.56.62.122)22:51
+ simba (~simba@148.56.62.122)22:54
- simba (QUIT: Ping timeout: 245 seconds) (~simba@148.56.62.122)23:34
+ aloo_shu_ (~aloo_shu@85.51.16.47)23:39
- aloo_shu (QUIT: Ping timeout: 244 seconds) (~aloo_shu@90.166.99.93)23:40
* aloo_shu_ -> aloo_shu23:40

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