#archlinux-ports | Logs for 2025-10-22
Back
[02:02:59] -!- hrtk has joined #archlinux-ports
[02:12:11] -!- hrtk has quit [Ping timeout: 248 seconds]
[02:42:41] -!- hrtk has joined #archlinux-ports
[03:08:45] -!- hrtk has quit [Ping timeout: 256 seconds]
[03:55:19] -!- hcmb_ has joined #archlinux-ports
[03:55:19] hcmb is now known as Guest8648
[03:55:19] hcmb_ is now known as hcmb
[03:56:00] -!- Guest8648 has quit [Ping timeout: 252 seconds]
[04:50:56] -!- nl6720 has quit []
[04:52:34] -!- nl6720 has joined #archlinux-ports
[05:07:14] NoaHimesaka18733 is now known as NoaHimesaka1873
[05:37:31] -!- moabeat has quit [Ping timeout: 265 seconds]
[05:39:15] -!- moabeat has joined #archlinux-ports
[05:55:55] -!- hrtk has joined #archlinux-ports
[06:03:07] -!- hrtk has quit [Remote host closed the connection]
[08:21:13] <NoaHimesaka1873> Solskogen: Seemed fine at first, but it broke Mesa from asahi-alarm repo. Since it's all upstream now anyways for mesa, I just switched to mesa on extra repo.
[08:21:21] <NoaHimesaka1873> Thanks for your warning!
[09:39:01] <strit|M> <bschnei> "strit: everything you listed are..." <- Hm. ALARM builds for armv8, right? Why the difference?
[11:09:17] -!- rossy has quit [Ping timeout: 260 seconds]
[11:13:55] <Solskogen> NoaHimesaka1873: It might work now
[11:14:37] <Solskogen> I don't know what changes asahi does with Mesa, but all of the drivers should work
[11:15:01] <Solskogen> (with mesa from our repo)
[11:16:23] -!- rossy has joined #archlinux-ports
[11:22:15] -!- hrtk has joined #archlinux-ports
[11:28:17] -!- hrtk has quit [Remote host closed the connection]
[12:04:37] <NoaHimesaka1873> Solskogen: All the downstream Asahi changes are now merged to mainline so yeah it does work
[12:04:47] <NoaHimesaka1873> though quite recently
[12:05:16] <NoaHimesaka1873> The Asahi ALARM mesa was dependent on older LLVM so it broke lol
[12:19:57] <Solskogen> great news!
[12:55:31] -!- hrtk has joined #archlinux-ports
[13:07:49] -!- hrtk has quit [Ping timeout: 264 seconds]
[13:10:37] -!- hrtk has joined #archlinux-ports
[13:15:29] -!- hrtk has quit [Max SendQ exceeded]
[13:52:13] -!- solsTiCe has quit [Quit: The Lounge - https://thelounge.chat]
[13:53:30] -!- solsTiCe has joined #archlinux-ports
[13:57:06] -!- hrtk has joined #archlinux-ports
[14:04:03] -!- hrtk has quit [Ping timeout: 265 seconds]
[14:07:55] -!- solsTiCe2 has joined #archlinux-ports
[14:10:52] -!- solsTiCe has quit [Ping timeout: 244 seconds]
[14:10:52] solsTiCe2 is now known as solsTiCe
[15:37:10] -!- drathir_tor has quit [Remote host closed the connection]
[15:45:35] -!- drathir_tor has joined #archlinux-ports
[16:32:44] <Solskogen> gromit: I got rocm-llvm 7.0.2 to compile (with a little hack) - I guess there's a good reason why you haven't updated the PKGBUILD to 7.0.2 yet?
[16:53:33] -!- titus_livius has joined #archlinux-ports
[16:57:03] <tpkessler|M> Solskogen: that's mostly because ROCm 7 introduces a couple of breaking changes by removing deprecated behavior. So it's mostly an issue of third packages not building with newest rocm.
[16:57:36] <tpkessler|M> Furthermore, it's a big rebuild that will block staging for days, so other stuff has priority.
[17:06:14] <Solskogen> tpkessler|M: thanks for the info :-)
[18:54:35] -!- marmis has quit [Quit: Bye!]
[18:55:51] -!- marmis has joined #archlinux-ports
[20:19:56] -!- hrtk has joined #archlinux-ports
[20:29:47] -!- hrtk_ has joined #archlinux-ports
[21:02:01] -!- hrtk has quit [Ping timeout: 256 seconds]
[21:33:25] -!- hrtk has joined #archlinux-ports
[21:44:55] -!- hrtk has quit [Ping timeout: 244 seconds]
[21:46:35] -!- hrtk has joined #archlinux-ports
[22:00:01] -!- drathir_tor has quit [Remote host closed the connection]
[22:00:21] -!- drathir_tor has joined #archlinux-ports
[22:02:04] -!- hrtk has quit [Ping timeout: 244 seconds]
[22:05:14] -!- hrtk has joined #archlinux-ports
[22:09:19] -!- hrtk has quit [Ping timeout: 240 seconds]
[22:10:15] -!- titus_livius has joined #archlinux-ports
[22:19:42] -!- hrtk has joined #archlinux-ports
[22:34:55] -!- hrtk has quit [Ping timeout: 246 seconds]
[23:22:43] <bschnei> strit: because nobody has done the work needed to broaden support. We have a linux package that works on devices with ACPI or UEFI bootloaders where the device tree is provided to the kernel via UEFI, but not much else. That rules out nearly everything except cloud VMs which is where we primarily develop anyway. And cloud VMs seem to all be v8.2 and above. There are more pieces to the puzzle too: https://gitlab.archlinu
[23:22:44] <bschnei> x.org/archlinux/ports/aarch64/project-management/-/issues/6. So if you're interested in brining support to more devices, we'd welcome the help. Otherwise, we're simply at where we are at because none of us personally has found a need to prioritize this work over other work.
[23:25:58] <bschnei> I do own a v8 device and build my own packages for it but they are very limited in coverage, reliant on me building them whenever I feel like it/have the time. I'm happy to share my repo if you want to use them for testing on your devices or to help bring support to those devices, just bear in mind that if you are looking for something that is more of a daily driver you are much better off with ALARM than what I have.
[23:29:41] -!- hrtk has joined #archlinux-ports
[23:37:39] -!- hrtk has quit [Ping timeout: 244 seconds]