#archlinux-ports | Logs for 2026-07-11

Back
[00:10:13] -!- Charon77|PC has joined #archlinux-ports
[00:20:49] -!- BrainDamage has quit [Ping timeout: 272 seconds]
[00:30:47] <greyltc> will how does linux-mainline work on rpi5 these days?
[00:31:19] <greyltc> s/will //
[00:54:52] -!- BrainDamage_ has joined #archlinux-ports
[01:37:03] -!- h|ignition has quit [Remote host closed the connection]
[01:37:37] -!- h|ignition has joined #archlinux-ports
[01:45:11] <greyltc> `run_archiso -A aarch64 -i ${img}` looks for `/usr/share/edk2/aarch64/QEMU_CODE.fd` but the edk2-aarch64 package does not provide it
[01:45:57] <greyltc> however, it does provide `/usr/share/AAVMF/AAVMF_CODE.fd`
[01:54:20] -!- lynxy has quit [Ping timeout: 245 seconds]
[01:54:35] -!- lynxy has joined #archlinux-ports
[01:58:59] -!- lynxy has quit [Ping timeout: 243 seconds]
[02:33:00] -!- Charon77|PC has quit [Ping timeout: 268 seconds]
[03:08:21] -!- hcmb_ has joined #archlinux-ports
[03:08:22] hcmb is now known as Guest8656
[03:08:22] hcmb_ is now known as hcmb
[03:08:39] -!- Guest8656 has quit [Ping timeout: 272 seconds]
[04:10:32] -!- hch129077 has joined #archlinux-ports
[04:12:58] -!- hch12907 has quit [Ping timeout: 248 seconds]
[04:12:58] hch129077 is now known as hch12907
[04:29:45] BrainDamage_ is now known as BrainDamage
[04:52:19] -!- drathir_tor has quit [Remote host closed the connection]
[04:52:27] -!- h|ignition has quit [Remote host closed the connection]
[04:52:41] -!- drathir_tor has joined #archlinux-ports
[04:52:53] -!- h|ignition has joined #archlinux-ports
[08:55:05] -!- drathir_tor has quit [Remote host closed the connection]
[08:55:40] -!- drathir_tor has joined #archlinux-ports
[10:05:35] -!- hcmb has quit [Remote host closed the connection]
[10:06:30] -!- hcmb has joined #archlinux-ports
[11:11:02] -!- lynxy has joined #archlinux-ports
[12:34:48] <solskogen|M> greyltc: I have no idea. Never tried. Perhaps someone else has?
[14:31:42] <greyltc> solskogen|M: do you have a script that puts your linux-rpi into a bootable image?
[14:32:19] <solskogen|M> I do, but I haven't tried it in a while.
[14:32:34] <solskogen|M> we don't publish images (yet)
[14:33:32] <greyltc> Would you be willing to share it with me for my personal testing?
[14:34:30] <greyltc> or can mkarchiso be coaxed to build a bootable image with linux-rpi?
[14:35:52] <solskogen|M> mkarchiso is the plan for non-pi at least
[14:36:05] <solskogen|M> but I don't think we have a proper plan for pi.
[14:36:15] <solskogen|M> Will publish the script shortly, I just need to make sure it works
[14:36:47] <greyltc> thank you. why shouldn't mkarchiso be suitable for the pi5?
[14:38:24] <greyltc> because it assumes proper UEFI support?
[14:39:40] <solskogen|M> As far as I know yes. I'm not the one working on that.
[14:41:39] <greyltc> also, i think i've noticed a bug in https://github.com
[14:41:40] <phrik> Title: linux-rpi5/linux-rpi5.install at 27da77e038f3e9e0f2dbb44a0aae080b00520514 · bschnei/linux-rpi5 · GitHub (at github.com)
[14:42:15] <solskogen|M> Yeah, I forgot to push the fix
[14:42:48] <solskogen|M> give me a couple of minutes
[14:43:05] <greyltc> :-)
[14:43:08] <greyltc> no worries
[14:44:39] <solskogen|M> https://bpa.st
[14:44:40] <phrik> Title: View paste LDNA (at bpa.st)
[14:45:01] <solskogen|M> that the script I've used. But I haven't checked that the image really boot as of late
[14:45:16] <greyltc> sweet. i will see how it works today
[14:47:11] <greyltc> i might also take a peak at what it might take to hack mkarchiso to generate images that can boot an rpi5 with your kernel package
[14:47:26] <solskogen|M> peak away!
[14:48:04] <greyltc> erm peek ;-)
[14:57:24] <greyltc> I think `cp /usr/lib/modules/${1%-*}-rpi5-${1##*-}/boot/config.txt boot/` just needs to become `cp /usr/lib/modules/${1}-rpi5/boot/config.txt boot/`
[14:57:38] <greyltc> does that look about right?
[14:57:59] <solskogen|M> the image the script creates work
[14:58:58] <solskogen|M> fix commited
[14:59:21] <solskogen|M> (and package it updated)
[14:59:26] <greyltc> oh weird. you don't get `cp: cannot stat '/usr/lib/modules/7.1.2-rpi5-2/boot/config.txt': No such file or directory` when linux-rpi5 runs its .install script?
[14:59:38] <greyltc> oh shit
[14:59:53] <greyltc> i see it's fixed
[15:00:12] <bschnei> greyltc: it's been a while (6 months?) since I last tried. device tree stuff is weird for rpi. they have all these overlays: https://github.com that are not in upstream and several drivers were missing the last time I looked. But it is worth trying...
[15:00:13] <phrik> Title: linux/arch/arm/boot/dts/overlays at rpi-7.2.y · raspberrypi/linux · GitHub (at github.com)
[15:00:30] <solskogen|M> try again (you have to redownload the package, I didn't change the pkgrel)
[15:02:59] <greyltc> bschnei: i'll give it a go and report back here
[15:03:16] <bschnei> <3
[15:06:05] <greyltc> here's me running a 461 line script from irc as root after only reading it for 3.5 minutes, heh
[15:12:41] <greyltc> solskogen|M: does your script pull the rpi kernel package from the forge repo on drzee.net?
[15:17:31] <greyltc> nevermind. i can see now it does not
[15:26:03] <solskogen|M> Eh, it does. Or at least, it should. Because that's the only place that kernel is located.
[15:26:49] <greyltc> where does the forge repo get enabled?
[15:27:04] <solskogen|M> It's in the default pacman.conf
[15:28:57] <greyltc> `Installing linux-rpi5 kernel...`
[15:29:06] <greyltc> `error: target not found: linux-rpi`
[15:29:57] <solskogen|M> it's supposed to be 'linux-rpi5' if I'm not mistaken
[15:31:34] <greyltc> sorry, that was an incomplete copy
[15:33:14] <greyltc> i'm running this on my x86_64 Arch Linux machine
[15:34:51] <greyltc> and here's the full output: https://bpa.st
[15:35:23] <solskogen|M> I've never tried that.
[15:35:41] <greyltc> you run it from itself I assume?
[15:36:03] <solskogen|M> yeah - I'm amazed that you got that far
[15:36:21] <greyltc> heh
[15:37:46] <greyltc> chicken/egg
[15:38:24] <solskogen|M> if you're trying to install, you're better off by just using our tarballs.
[15:38:45] <solskogen|M> partition, format, mount and untar the tarball. That you can do from x86_64.
[15:38:55] <solskogen|M> https://arch-linux-repo.drzee.net
[15:38:56] <phrik> Title: Index of arch/tarballs/os/aarch64/ (at arch-linux-repo.drzee.net)
[16:40:24] -!- bschnei has quit [Remote host closed the connection]
[16:42:28] -!- bschnei has joined #archlinux-ports
[18:14:02] -!- marmis has quit [Quit: Bye!]
[18:15:34] -!- marmis has joined #archlinux-ports
[18:30:57] -!- drathir_tor has quit [Remote host closed the connection]
[18:31:24] -!- drathir_tor has joined #archlinux-ports
[18:38:33] <greyltc> solskogen|M: I can confirm your script made an image that boots my pi5. networking works too. thanks for sharing that!
[18:40:00] <greyltc> I ended up making a (non-pi) aarch64 image with mkarchiso, running it via qemu with run_archiso and running your script to make the pi image in there
[22:10:13] -!- titus_livius has joined #archlinux-ports
[23:06:42] <greyltc> where is the PKGBUILD for linux-mainline/linux-mainline-dtbs packages found here https://arch-linux-repo.drzee.net
[23:06:43] <phrik> Title: Content of forge - aarch64 (at arch-linux-repo.drzee.net)
[23:41:31] -!- linkmauve has quit [Remote host closed the connection]
[23:44:15] -!- linkmauve has joined #archlinux-ports
[23:54:18] <greyltc> I haven't been able to get the prebuilt linux-mainline to boot on my pi5. I'm starting to think that package will need some pi5 specific mods
[23:56:44] <greyltc> here's the console from the failed boot: https://bpa.st
[23:57:15] <greyltc> I've come across this, but I'm not sure it's relevant: https://forums.raspberrypi.com