#
✕ nick:lm
#asahi · 2025-12-30 15:08
lmbgtlover[mds]: yes, here's the link https://media.ccc.de/v/39c3-asahi-linux-porting-linux-to-apple-silicon
#asahi · 2025-12-30 13:40
lmYeah it seems to work okay
#asahi · 2025-12-30 13:34
lmCompatibility can vary between wine and fex versions so I make many versions of each to give people options for testing
#asahi · 2025-12-30 13:33
lmbgtlover[mds]: the wine stuff is available for Fedora on my copr, should preface though it's pretty rough and versions after 2508.1 are very unlikely to work for anything on 16k kernels due to FEX changes https://copr.fedorainfracloud.org/coprs/lacamar/wine-arm64ec/
#asahi · 2025-12-30 13:30
lmchaos_princess: sounds cursed
#asahi · 2025-12-30 13:30
lmShiz: does this imply the existence of I3C
#asahi · 2025-12-29 11:50
lmThe asahi developer documentation is a good place to start https://asahilinux.org/docs/sw/tethered-boot/
#asahi · 2025-12-28 18:45
lmEarlier versions I mean
#asahi · 2025-12-28 18:45
lmAnd FEX dropped it's 16k page "support" from the DLL artifact some time around 2508 or 09 so those versions are needed
#asahi · 2025-12-28 18:44
lmYeah pretty much. 11.0-rc4 seems to work okay with this change from a little testing but it's still pretty flaky
#asahi · 2025-12-28 18:32
lmCaused by build errors from the LLVM version
#asahi · 2025-12-28 18:31
lmv10.19 up until v11.0-rc3 was impacted on F42
#asahi · 2025-12-28 18:29
lmYeah it was just this commit https://gitlab.winehq.org/wine/wine/-/commit/411ac59920ba6547b48bf71755ff40ee901df2e6
#asahi · 2025-12-28 18:27
lmWine wouldn't build for a few months there, only F43 and up
#asahi · 2025-12-28 18:26
lmWine 11.0-rc4 builds on F42 again
#asahi · 2025-12-25 11:34
lmMerry Christmas everyone 🎄
#asahi · 2025-12-25 08:33
lmHi
#asahi · 2025-12-13 21:16
lmCan only imagine the power management driver headache required to get down to that level
#asahi · 2025-12-13 21:15
lmhttps://device.report/energystar/2386179 This says MBP M1 Pro sleep power draw is between 0.1 and 0.3 W
#asahi · 2025-12-13 21:10
lmScreen (3 - 4 W) + keyboard (0 - 0.2 W) + Wifi/BT (0.5 - 1 W) leads to a 1.8 - 3.5 W window for a battery life on par with MacOS
#asahi · 2025-12-13 21:05
lm7W is where you want low impact use to hover around since that equates to ~10 hours of use (70 Wh battery)
#asahi · 2025-12-13 21:03
lmOn MBP M2 Max that is
#asahi · 2025-12-13 21:01
lmPro/max. From some basic testing I did, baseline SOC power draw was around 5 W, screen ranged from 3 to 11 W, keyboard backlight from 0.2 to 2 W
#asahi · 2025-12-13 20:57
lmAutomatically adjusting brightness to the ambient light, essentially reimplementing what MacOS already does or maybe a bit more aggressive for extra power savings
#asahi · 2025-12-13 20:56
lmThe screens and backlight use a lot of power compared to the silicon so I think there could be some good gains there from the userspace side once the ambient light sensor is available
#asahi · 2025-12-13 20:52
lmThe silicon is still hiding some secrets
#asahi · 2025-12-13 20:47
lmAre there reverse engineering blockers for that or is it more to do with problems getting it to work with the linux kernel?
#asahi · 2025-12-13 20:43
lmAh okay, that makes sense. Good to know it's already doing the best that's allowed
#asahi · 2025-12-13 20:36
lmMaybe this is an ignorant question, but is there a way with these CPUs to forcefully disable say all but 1 core when sleeping/closed lid/etc.? I tried some generic cpu commands but they didn't seem to have any impact
#asahi · 2025-12-01 15:14
lmIf you only need 1080p, displaylink might be good enough for your second display
#asahi · 2025-11-18 09:55
lmI also had another go around with opengoal and found out it's actually very easy to run in muvm if you avoid their dogshit launcher and use their CLI tools
#asahi · 2025-11-18 09:50
lmSeti_: Yeah the whole arm side of PCSX2 is a clusterfuck. Anyway, I remembered aethersx2, which was a closed source fork of pcsx2 for arm devices (including linux) that was unceremoniously deleted. It segfaults on the host's 16k but it works great inside muvm. You can download it here https://store.kde.org/p/2148513/
#asahi · 2025-11-18 09:37
lmtea_bag_inc: I might have run into a similar problem, I had to disable and reenable the broadcom kernel module to restore wifi function. sudo rmmod brcmfmac_wcc; sudo rmmod brcmfmac; sudo modprobe brcmfmac
#asahi · 2025-11-17 16:14
lmI don't believe there are any that work on aarch64 16k yet
#asahi · 2025-11-17 14:12
lmSo no muvm or FEX needed for that
#asahi · 2025-11-17 14:12
lmNo, I was using the native pcsx2 I had compiled already
#asahi · 2025-11-17 14:09
lmas a side note, opengoal is great and even playable inside muvm but it's a pain in the ass to set up
#asahi · 2025-11-17 14:08
lmI haven't got any other isos to test
#asahi · 2025-11-17 14:07
lmMaybe an especially light game might be playable on aarch64 but I haven't dug into that
#asahi · 2025-11-17 14:06
lmThere's this project as well that might be more functional but I haven't managed to build it yet https://github.com/ARMSX2/ARMSX2
#asahi · 2025-11-17 14:05
lmSeti_: yeah just tried x86 with the app image and got the same thing
#asahi · 2025-11-17 14:04
lmAnyway I'm playing jak and daxter at a buttery smooth 5 fps and 20% game speed
#asahi · 2025-11-17 14:03
lmchaos_princess: wouldn't surprise me
#asahi · 2025-11-17 13:54
lmI'm working on packaging the arm64 build of this but I'm pretty sure the arm performance is still shit compared to x86
#asahi · 2025-11-17 13:53
lmUsing the AppRun script didn't work when I tried that
#asahi · 2025-11-17 13:52
lmOnce it extracts, this should run it: muvm -- FEXBash -c "./squashfs-root/usr/bin/pcsx2-qt"
#asahi · 2025-11-17 13:50
lmSeti_: oops, add the "-c" flag... muvm -- FEXBash -c "/home/<me>/pcsx2.AppImage --appimage-extract"
#asahi · 2025-11-17 13:44
lmtry * muvm -- FEXBash "/home/<me>/pcsx2.AppImage --appimage-extract"
#asahi · 2025-11-17 13:44
lmtry muvm /home/<me>/pcsx2.AppImage --appimage-extract
#asahi · 2025-11-17 13:38
lmNo running as root inside muvm

plus ›