ChanServ changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
zumi_ has joined #asahi
zumi has quit [Remote host closed the connection]
pb17 has quit [Ping timeout: 480 seconds]
<MasterDuke>
afk, but i'll check the logs if there are any answers
ddxtanx_ has quit [Remote host closed the connection]
pakupaku has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
<pakupaku>
Hi. I'm using Asahi Linux on a macbook pro m1 and am quite happy with it. However recently I've noticed a performance regression with the mesa-vulkan-drivers when playing Factorio (launched with box64): starting with mesa-vulkan-drivers-25.0.0~asahipre20241202.2-1.fc40.aarch64 the game runs at <20 FPS. I've downgraded the package to
<pakupaku>
mesa-vulkan-drivers-24.3.0~asahipre20241111-2.fc40.aarch64 and it's back to 60FPS.
<pakupaku>
Where should I report this problem? What can I do to help debugging/fixing it?
ten157237743246305066182150355 has quit [Remote host closed the connection]
ten157237743246305066182150355 has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
monthebiff has joined #asahi
desertedplanet has joined #asahi
desertedplanet has quit [Remote host closed the connection]
<monthebiff>
if i want to arbitrarily a command in muvm/ wine... is there a doc for how to do that? im thinking of running wow just with wine and seeing if anything get spat out other than failed.
<j`ey>
wine from fedora doesnt work yet
<monthebiff>
vague memory of this conversation...
<j`ey>
wine from arch works
<monthebiff>
yes... i remember this conversation from last month. something about an overlay of the files from arch?
shiggitay has quit [Ping timeout: 480 seconds]
<monthebiff>
oh it was you j`ey
<monthebiff>
we had this conversation :P
<j`ey>
yes :)
<monthebiff>
currently googling 'tar to erofs' stuff... feel free to short cut me :{
<monthebiff>
:)
<monthebiff>
oh before i do this, did wine defintely not get fixed as part of the asahi/fedora 41 release?
<j`ey>
yeah
<j`ey>
the erofs command isnt in my history :/
<j`ey>
but I untarred it and used mkfs.erofs
monthebiff has quit [Ping timeout: 480 seconds]
hyrumb has joined #asahi
dcavalca8569 has quit []
dcavalca8569 has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
Moprius has joined #asahi
sand4rt has joined #asahi
ten157237743246305066182150355 has quit [Remote host closed the connection]
ten157237743246305066182150355 has joined #asahi
monthebiff has joined #asahi
monthebiff has quit [Ping timeout: 480 seconds]
hightower2 has quit [Remote host closed the connection]
hightower2 has joined #asahi
zumi_ has joined #asahi
zumi has quit [Remote host closed the connection]
zumi_ is now known as zumi
Brainium has joined #asahi
monthebiff has joined #asahi
___nick___ has joined #asahi
___nick___ has quit []
hightower2 has quit [Read error: Connection reset by peer]
hightower2 has joined #asahi
___nick___ has joined #asahi
kettenis has quit [Ping timeout: 480 seconds]
kettenis has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
<monthebiff>
slightly confused by this erofs volume im mounting with muvm - doesn't seem to be doing anything
chadmed has quit [Quit: Konversation terminated!]
chadmed has joined #asahi
<monthebiff>
specifically, the wine binary doesn't appear to have been mapped to /usr/bin which i assume is what should happen?
<chaos_princess>
only when inside fex
<monthebiff>
ahhhhh
<monthebiff>
and if you run a windows binary... muvm is configured to use fex automatically?
<monthebiff>
but i can't run a windows binary without wine?
<monthebiff>
so... manually run fex?
<chaos_princess>
we do not configure binfmt_misc for windows exes, you need to manually run wine with fex
<monthebiff>
makes sense
<monthebiff>
kinda, im aware im garbling stuff together
<chaos_princess>
imo, don't bother with erofs for your own stuff, just put it somewhere on the host fs, and run it from there
<monthebiff>
that thought had occurred to me
<monthebiff>
ls
<monthebiff>
whoops
Calandracas has quit [Ping timeout: 480 seconds]
john-cabaj has joined #asahi
ephemera_ has quit [Ping timeout: 480 seconds]
__nick__ has joined #asahi
nightstrike has quit [Quit: Connection closed for inactivity]
<arryn>
Hello everyone, I'd like to poke at and learn about the m4 hardware, but when I install m1n1 as custom kernel my device bootloops *before* loading m1n1. I know that because I replaced the first instruction with a "b ." instruction. So I'm just trying to get the mac to load anything at all. Anyone have any pointers? My base is an install of 15.2 and I'm basically just booting into
<arryn>
recovery and executing kmutil, that should work or am I misunderstanding something?
<JamesB192>
arryn: my thoughts which are not necessarily the thoughts of the group or any reasonable member thereof are that at this point no work has been done porting Linux to that SOC, so you can probably only use it for remote debug of macOS, reverse engineering, or possibly working on bootloaders.
<nicolas17>
not sure how much work was even done in porting m1n1 to that SoC
<arryn>
Which is exactly what I am looking to do. I am aware of this and am looking to work on gaining knowledge about the platform so that I can possibly help out
<j`ey>
is the watchdog enabled maybe?
<j`ey>
so b. will eventually reset
<arryn>
nicolas17: It's not been ported at all yet. But here that shouldn't matter too much here because I'm just looking to first boot the thing.
pb17 has quit [Ping timeout: 480 seconds]
<arryn>
j`ey: yes could be but it chimes and immediately resets which strikes me as a very short watchdog timer if that's the case
<sven>
watchdog timer was a few minutes (2 iirc) by default on m1/m2
<arryn>
I don't even get early UART even after plugging in the EARLY_UART address
<j`ey>
arryn: ok yes doesnt sound like it then
pb17 has joined #asahi
Calandracas has joined #asahi
nst has quit [Quit: WeeChat 4.4.2]
<arryn>
Hmmm, how frustrating. The only things that come to mind is: Either I misunderstood/am missing something | Something changed on 15.2 that makes it not work | My mac is weird. You guys reckon a DFU restore would be worth a try?
nst has joined #asahi
* JamesB192
thinks it might require two copies of the same m1n1 (w/ diff payloads) and udev rules not generally available/installed.
ephemera_ has quit [Ping timeout: 480 seconds]
rvalue has joined #asahi
<jannau>
arryn: on m4 (t8132) the unconditional register accesses in cpu_init() causes reboots
<arryn>
jannau: I saw that in the chat logs here, but that is not the case here because it reboots way before it even gets to that point
<arryn>
I patched the first instruction at 0x800 (the mov x19, x0) to be a "b .", and even that reboots
<arryn>
I've got the same address for EARLY_UART, at least that seems to check out then... Maybe 15.2 is really the issue here then? I guess I'll try to go back to 15.1 and see what happens
__nick__ has joined #asahi
<arryn>
still not ruling out me doing something weird that I was not supposed to do: What I did was I installed a 2nd MacOS partition and then booted into 1TR on that partition and used the kmutil command as in the wiki with -v being the "Data" partition that has a folder on Preboot and has the "OS Can Be Installed:" flag set to Yes
sand4rt has quit [Ping timeout: 480 seconds]
<arryn>
which ends up being something like "kmutil configure-boot -c m1n1.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v /Volumes/Asahi\ -\ Data"
___nick___ has quit [Ping timeout: 480 seconds]
<jannau>
arryn: did you change the boot policy with bputil? it's not the data partition (not sure if that matters)
<arryn>
jannau: still same behaviour, chime starts rining and then it reboots immediately after
patrickm has quit [Ping timeout: 480 seconds]
patrickm has joined #asahi
<arryn>
And using the the non Data partition as argument for kmutil also does not help
<arryn>
I'm going to try 15.1 and see what happens
patrickm has quit [Ping timeout: 480 seconds]
sand4rt has quit [Quit: WeeChat 4.5.1]
sand4rt has joined #asahi
Xe has quit [Remote host closed the connection]
Xe has joined #asahi
nst has quit [Quit: WeeChat 4.4.2]
<jannau>
arryn: reproduced with macos 15.2
<arryn>
So macOS 15.2 is really the problem. That's good to know. At least now I can rest knowing that I (probably) can read. I spent the past 3 days doing nothing but reading the wiki and IRC logs trying to figure this out...
nst has joined #asahi
pb17 has quit [Ping timeout: 480 seconds]
pb17 has joined #asahi
vx has quit [Quit: G-Line: User has been permanently banned from this network.]
vx has joined #asahi
hightower4 has joined #asahi
sand4rt has quit [Quit: WeeChat 4.5.1]
sand4rt has joined #asahi
marvin24 has joined #asahi
hightower2 has quit [Ping timeout: 480 seconds]
<nicolas17>
wuh
<nicolas17>
bug in 15.2 kmutil?
vx has quit [Quit: G-Line: User has been permanently banned from this network.]