#asahi · 2026-11-02 12:28
svenhttps://codon.org.uk/~mjg59/blog/p/epics-eac2-v2-seems-fairly-easily-bypassable/ lol#asahi · 2026-11-02 12:27
chadmedthe way multiplayer shooters are written is baggage from 30 years ago and no one's really bothered to do anything different because it would be slightly more expensive for whoever's running the servers#asahi · 2026-11-02 12:26
chadmedif theyre going to implement kernel anticheat its the least insane way to do it, but as above they should just not have to do this bs in the first place if their games werent abysmal dogshit#asahi · 2026-11-02 12:25
chadmedits basically JITted kernel code with limited access to some kernel subsystems/APIs#asahi · 2026-11-02 12:25
chadmedmonthebiff: it uses ebpf which hooks the kernel #asahi · 2026-11-02 12:25
svendoes it trust secure boot via any TPM? just hook up a TPM via some usb-to-spi(?) bridge and fake everything :D#asahi · 2026-11-02 12:24
monthebiffi thought their linux implementation wasn't ussing kernel level stuff?#asahi · 2026-11-02 12:20
chadmedi saw a shooter recently that implemented server authoritative netcode properly and i remember just being really sad that this is an actual unique selling point in 2026 #asahi · 2026-11-02 12:19
chadmedwhy pay for compute when you can make the client do everything#asahi · 2026-11-02 12:19
chadmedmuch like microslop deprecating memberOf from Graph, kernel anticheat is a crutch used by multiplayer game devs to avoid spending server cycles on running authoritative netcode#asahi · 2026-11-02 12:18
chadmedi dont particularly care either, fuck epic and fuck kernel (and kernel-ish) anticheat#asahi · 2026-11-02 12:18
chadmedwhich is just straight up never going to happen #asahi · 2026-11-02 12:18
chadmedthe problem is not emulating/replicating tpm features, its convincing sw vendors to trust our implementation #asahi · 2026-11-02 12:11
monthebiffi figured the kernel stuff it could do, even as an alternative at boot time. but the sep stuff caught my eye: wasn't sure how that looks on apple hardware. but at the same time... uefi boot environment as part of the boot chain? TPM ish stuff as part of bootchain?#asahi · 2026-11-02 12:06
AnEagle[m]Not happening for a very long time, if ever. Can SEP even match the features of TPM 2.0?#asahi · 2026-11-02 11:59
monthebiffany thoughts on the fortnight linux support and related requirements in respect to Asahi Linux?#asahi · 2026-11-02 03:18
nyr[m]chaos_princess: that's great to hear! thanks#asahi · 2026-11-02 01:36
twbI guess I can get some per-component wattage out of "upower --dump" -- that tells me 2.3W for the display, can't see the radio#asahi · 2026-11-02 01:31
twbhttps://github.com/fenrus75/powertop/tree/master/src/measurement mentions both acpi and sysfs, but both files are pretty empty#asahi · 2026-11-02 01:25
twbThe missing owner execute permission looks dumb, but powertop runs as root so CAP_DAC_OVERRIDE should make that irrelvant#asahi · 2026-11-02 01:25
twbhttps://paste.debian.net/hidden/06494f27 is thinkpad; https://paste.debian.net/hidden/4bab5360 (ran twice to get it up to minimum length on that pastebin)#asahi · 2026-11-02 01:21
twbDon't know to be honest. It does report *some* data on m2, it just seems to be unable to create it's persistent state (so it rememers how much it was using last week)#asahi · 2026-11-02 01:21
JamesCalligeros[m]Does powertop rely on acpi#asahi · 2026-11-02 01:20
twbMy end goal is just to say "hey powertop, in Watts, what components are most profligate right now?"#asahi · 2026-11-02 01:19
twbon my thinkpad, powertop says "Loaded 750 prior measurements" but on my M2 (running Debian 14 Bananas) powertop says "Cannot load from file /var/cache/powertop/⋯ File will be loaded after taking minimum number of measurement(s) with battery only" and even if I leave it running for hours it never seems to make those files#asahi · 2026-11-01 21:59
chaos_princessa ton of work carries over#asahi · 2026-11-01 21:59
nyr[m]chaos_princess: would that mean some maybe significant amount of work on the previous generation chips carries over?#asahi · 2026-11-01 21:40
chaos_princessyou have two tracks, the t81XX chips (vanilla), and the t60XX (pro/max/ultra). In general, there are some differences, but not a lot, for m5 specifically, the pro/max laptops have a new wifi chip, while m5 vanilla still uses the brcm one#asahi · 2026-11-01 21:26
nyr[m]fl0_id: awesome, thank you#asahi · 2026-11-01 21:25
fl0_idnyr[m] historically, there's no different support between "tiers". but it can be that there are slight difference in say wifi or usb, and then those have to adressed separately. (but so far mostly minor things I think) With new hardware being released, as long as there are people actively working, there's not really an end. m1/m2 are however mostly future complete (but still see some improvements and updates for firmware etc)#asahi · 2026-11-01 20:32
nyr[m]* hello. I'm new here (to Asahi and Matrix, so sorry if this is the wrong place) and know very little about what goes into this sort of work---suffice it to say I'm sure everyone here is far more knowledgeable and capable than me, so... (full message at <https://matrix.org/oftc/media/v1/media/download/AWZlzNfRLD3gC5TwscbdzSFFnv27xRBuFB1k9ZXIG7S-DbW6MzdLGacqc_vyZjjJ-cA8R3hocKWKT4yihY9Nhg9Ceh4OmStQAG1hdHJpeC5vcmcvUlFCeldJR0VmeGpmU1JRQ3dXUE9HYVd6>)#asahi · 2026-11-01 20:32
nyr[m]hello. I'm new here (to Asahi and Matrix, so sorry if this is the wrong place) and know very little about what goes into this sort of work---suffice it to say I'm sure everyone here is far more knowledgeable and capable than me, so I... (full message at <https://matrix.org/oftc/media/v1/media/download/AS72J1FLaJ1Bsio0X-ra4ro2U06uCSZSUXVMkmGAeQYHtItKAppPBaLelaP-M5FREkQTYvDaCXqhSUKPP36CLB9Ceh4OkXZAAG1hdHJpeC5vcmcveHJVZ1l5V0FQSFRoZVVXdFVvVFloUFdx>)#asahi · 2026-10-30 02:05
monthebiffthat's*#asahi · 2026-10-30 02:05
monthebiffthat my original question#asahi · 2026-10-30 02:05
nicolas17does that command apply to all kernels currently installed, or also to all kernels installed in the *future*?#asahi · 2026-10-30 02:05
JamesCalligeros[m]nah the kernel updates should run update-m1n1 for you automatically, you shouldnt have to do anything#asahi · 2026-10-30 02:04
monthebiffthere a step that im missing during the update process? a manual post script I'm supposed to run?#asahi · 2026-10-30 02:03
JamesCalligeros[m]things it always is: dns, devicetrees#asahi · 2026-10-30 02:03
monthebiffhappens every now and then, figured it was a new kernel coming down.#asahi · 2026-10-30 02:03
JamesCalligeros[m]it was probably devicetrees#asahi · 2026-10-30 02:03
monthebiffno idea, just ran an dnf update and next reboot, notch was back#asahi · 2026-10-30 01:58
JamesCalligeros[m]did your devicetrees not get updated or something#asahi · 2026-10-30 01:57
JamesCalligeros[m]no its still appledrm #asahi · 2026-10-30 01:54
monthebiffbut has it changed a secod time?#asahi · 2026-10-30 01:54
monthebiff...but i did, unless it has changed again? like i know it changed a while back#asahi · 2026-10-30 01:54
JamesCalligeros[m]unless im feeling evil #asahi · 2026-10-30 01:54
JamesCalligeros[m]yeah just give that argument to all kernels, it is unlikely we will change it again#asahi · 2026-10-30 01:46
monthebiffany idea why it keeps resetting?#asahi · 2026-10-30 01:46
monthebiffshould make it so that ALL kernels in perpetuity have that argument configured by default?#asahi · 2026-10-30 01:46
monthebiff grubby --args=appledrm.show_notch=1 --update-kernel=ALL