#archlinux-ports | Logs for 2025-12-14

Back
[02:11:27] -!- h|weechat has quit [Ping timeout: 250 seconds]
[02:25:33] -!- h|weechat has joined #archlinux-ports
[02:59:59] -!- drathir_tor has quit [Remote host closed the connection]
[03:43:10] -!- drathir_tor has joined #archlinux-ports
[04:20:45] -!- hcmb has quit [Ping timeout: 245 seconds]
[04:21:03] -!- hcmb has joined #archlinux-ports
[08:57:33] -!- titus_livius has joined #archlinux-ports
[10:46:46] -!- SpieringsAE has joined #archlinux-ports
[10:53:29] <SpieringsAE> It seems only ARCH_QCOM is enabled on the arch port right now?
[10:54:27] <SpieringsAE> but the linux-dtbs package also contains rockchip broadcom and marvell
[10:54:41] <SpieringsAE> which is odd
[10:55:15] <solskogen|M> that is things are way over my head to answer. this must bschnei answer when he wakes up :)
[10:56:28] <SpieringsAE> it seems these pkgbuilds are not upstream, is there some other location that I should look for them?
[10:56:48] <SpieringsAE> trying to run this on my orange pi 5+ :)
[10:56:52] <solskogen|M> I'm running the same kernel on a Orion O6, and that works. So I must admit I don't quite understand what the CONFIG_ARCH_* really do
[10:57:07] <solskogen|M> https://gitlab.archlinux.org
[10:57:08] <phrik> Title: Files · aarch64 · Benjamin Schneider / linux · GitLab (at gitlab.archlinux.org)
[10:57:32] <strit|M> I believe they enable some things that are unique to the different SoC vendors. Like CLK and PWM stuff.
[10:57:34] <SpieringsAE> I asume you are running it in acpi mode
[10:58:00] <SpieringsAE> hmm I could actually try that, my board has uefi/acpi support I believe
[10:58:06] <solskogen|M> I'm 100% sure he would be glad if anyone could do a review of the config (and come up with a MR if anything is a miss)
[10:58:33] <solskogen|M> for instance, I cannot get my Odroid M2 to boot AT ALL with that kernel. It just halts after loading the initrd
[10:58:49] <SpieringsAE> I think a good start may be the archlinuxarm config, but that will also support a bunch of boards that arent armv8.2
[10:58:51] <solskogen|M> Yes, I'm using ACPI on my Orion
[10:59:03] <SpieringsAE> that may explain things, im going to try that
[10:59:25] <SpieringsAE> firmware takes care of those things then I believe
[10:59:35] <SpieringsAE> like clocks etc
[11:03:37] <SpieringsAE> yep my orange pi 5+ boots in ACPI mode, just need to set up my boot device a bit better
[11:04:00] <SpieringsAE> though it would be good to get devicetree boot working, that supports more things I believe
[11:12:48] <SpieringsAE> funny enough ARCH_CIX is also not set so no devicetree booting on the O6
[11:13:32] <SpieringsAE> though it is a barely functioning device on devicetree at this point I believe, the upstreaming effort seems to not be going very fast
[11:14:08] <SpieringsAE> hmm in the config on gitlab ARCH_ROCKCHIP=y
[11:17:14] <SpieringsAE> okay now I am confused, /proc/config.gz does show stuff enabled now
[11:17:19] <SpieringsAE> aaaaaaah
[11:18:06] <SpieringsAE> I read the config.gz on my main machine instead of the install because it was in a chroot
[11:19:05] <SpieringsAE> that makes much more sense, why didn't it boot in devicetree mode then though
[11:24:57] <SpieringsAE> does this channel have a matrix bridge? If so what is the room name thingy
[11:30:40] <solskogen|M> #ports:archlinux.org
[11:32:11] <SpieringsAE> hmm
[11:32:30] <SpieringsAE> "you do not belong to any of the required romms/spaces to join this room"
[11:33:06] <solskogen|M> what's your matrix account? I'll send a invite
[11:33:50] <SpieringsAE> @spierings_ae:matrix.org
[11:34:01] <SpieringsAE> I think thats what is needed?
[11:35:06] -!- spierings_ae|M has joined #archlinux-ports
[11:35:12] <spierings_ae|M> Awesome thanks!
[11:41:23] -!- SpieringsAE has quit [Quit: SpieringsAE]
[14:17:40] <spierings_ae|M> Pretty sure I am missing CONFIG_ROCKCHIP_DRM, panfrost also was disabled, recompiling now with those two options enabled
[14:20:23] <spierings_ae|M> Dangit I need panthor not panfrost
[16:43:43] -!- Antiz has quit [Quit: The Lounge - https://thelounge.chat]
[16:44:17] -!- Antiz has joined #archlinux-ports
[16:56:10] -!- Antiz has quit [Quit: The Lounge - https://thelounge.chat]
[16:56:58] -!- Antiz has joined #archlinux-ports
[16:57:02] -!- nie has quit [Quit: Lost terminal]
[17:06:20] -!- Antiz has quit [Quit: The Lounge - https://thelounge.chat]
[17:08:15] -!- Antiz has joined #archlinux-ports
[18:22:48] <jelle> solskogen|M: hope you are ready to rebuild 2700 packages soon
[18:23:14] <solskogen|M> oooo... 2700 you say? what has happened?
[18:25:29] <jelle> only 900 so far https://archlinux.org :p
[18:25:30] <phrik> Title: Arch Linux - Todo: Python 3.14 rebuild (at archlinux.org)
[18:26:46] <solskogen|M> ah, but we don't built any packages :-)
[18:26:52] <solskogen|M> *build
[18:28:35] <jelle> solskogen|M: they aren't all any :P
[18:29:06] <solskogen|M> oh, I know. But most of them are.
[18:30:05] <solskogen|M> A lot of python packages was rebuilt earlier this autumn, right? I don't remember it taking /that/ long.
[18:30:12] <solskogen|M> It's the cuda stuff that's the real killer
[18:30:15] <solskogen|M> (and rocm)
[18:32:30] <jelle> earlier this autumn? no
[18:36:37] <solskogen|M> I've must confused it with something else.
[18:37:04] <solskogen|M> Either that, or I rebuilt all of the python packages that weren't -any package
[18:37:18] <jelle> well at least once you did :)
[18:37:43] <jelle> solskogen|M: if you want a headsup I can give you signal when it leaves staging
[18:39:28] <solskogen|M> That would be very nice, thank you.
[18:40:10] <solskogen|M> And if there's anything I should be ready for, like the build order (if applicable)
[21:16:00] <bschnei> spierings_ae|M: something we are missing is a list of devices the linux package actually works on. ALARM supports ARMv7 devices and those are out of scope for Arch Ports (per the RFC). We could definitely use help with the general ARM problem of "supporting" more devices. Devices with ACPI/UEFI -- especially when the device tree has been baked into the UEFI bootloader -- should Just Work. Everything else I wouldn't expe
[21:16:00] <bschnei> ct to work.
[21:20:07] <bschnei> Device support should be interpreted to mean everything from fixing kernel config and/or maintaining a separate "AUR-style" kernel package (like we do for RPi5) to writing documentation for how to get Arch installed on devices with non-"standard" bootloaders (also like RPi 5)
[21:24:46] -!- bschnei has quit [Remote host closed the connection]
[21:26:31] -!- bschnei has joined #archlinux-ports
[23:00:34] -!- drathir_tor has quit [Remote host closed the connection]
[23:05:48] -!- drathir_tor has joined #archlinux-ports
[23:10:14] -!- titus_livius has joined #archlinux-ports