
SavvyBeardedFish
Initially just set it to anything, then the first time you run makepkg it will update to the correct/latest version according to your pkgver() function.
Something else I see a lot of people get wrong: you only need to manually push the latest pkgver string when you make changes to the PKGBUILD, otherwise just leave it as-is, since it will auto-update locally when people run makepkg
Bad at maths...You a history buff, perchance?
Damn, they giving out electromagnetic interference for free, how nice!
You could install linux-lts, I sometimes use that as a sanity check in case there is some kernel fuckery
Did you also update systemd at the same time? It might be worth reverting that update to see whether it's that causing the issues.
To me, this sounds more like an fstab/systemd-automount issue rather than a bootloader/initrd issue
broken features like FSR4 (it needs a DLL from the AMD drivers to work that this thing doesn’t provide)
I assume the LLM assume you are using either Proton-GE, Proton-EM or Proton-cachy, where this flag actually works 🤔
BTW, what actually is “Strix Halo” anyway? I’m confused about whether it’s what they’re calling all the latest-generation APUs, or just the high-end ones, or Asus co-branding, or what.
Strix Halo is the "high-end" ones (and currently the latest), in terms of gaming they are closer to previous gen discrete laptop GPU (hence they use the naming scheme Radeon 8XXX series).
There are smaller ones as well, the one that is "mid-tier" is Strix Point, which has the Radeon 800M series GPU, i.e. closer to what one had in previous generations of integrated GPUs.
In terms of gaming performance, you can compare using Notebookcheck, as an example; Kingdom Come Deliverance 2 on low preset at 1080P:
| CPU | GPU | APU | Average FPS |
|---|---|---|---|
| Ryzen AI 9 HX 370 | AMD Radeon 890M | Strix Point | 19.9 |
| Ryzen AI Max Pro 390 | AMD Radeon 8050S | Strix Halo | 76.6 |
| Ryzen AI Max+ 395 | AMD Radeon 8060S | Strix Halo | 101.7 |
So, there's a pretty big leap going from Strix Point (mid tier) to Strix Halo (high-end)
I would assume the total area is larger for the separate CPU+GPU die when compared a single unified chip, sure. But the cost per millimeter doesn't necessarily scale linearly either (larger chip, lower yields), so it might be cheaper to buy CPU+GPU rather than the unified chip even though the total area is larger.
For reference, TechPowerUp lists:
RX 7600M: 204 mm² @ TSMC 6 nm
Strix Halo: 308 mm² @ TSMC 4 nm
Not sure what kind of area one could expect for the CPU alone (without the integrated GPU) for this kind of process
Sure, that's true! However, typically (but not always!) in git packages there's usually a new commit whenever you need to bump the
pkgverso yourpkgrelwouldn't need a bump then.pkgrelbump is only when it's the same (exact) version :)