ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | Non-development talk: #asahi | General development | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Logs: https://alx.sh/l/asahi-dev
<marcan>
try that "sudo installer" thing first I guess, let me know if it works :)
<marcan>
alternatively you could work directly on 13.2 for *now*, but you'll have to figure out what changed since the trace_isp experiments were written. it's highly likely 13.2 will be our next supported firmware release, so a camera driver will have to support both ABIs (and 12.4 for M2).
<marcan>
13.2 does work under the hypervisor fwiw (as long as you have a matching version)
<marcan>
you cannot use a tethered boot asahi install for booting macOS, you need to manually install m1n1 on top of an existing macOS install
<marcan>
whatever kernel you boot from that m1n1 needs to match the underlying macOS versino
<marcan>
also you don't need any of that debug kernel stuff
<marcan>
that's optional
<marcan>
you can use the retail kernel
<t>
wdym matching version? i did sudo ./proxyclient/tools/run_guest.py -m proxyclient/hv/trace_all.py -s kernel.development.t8103 dev.kc.macho.development -- "debug=0x14e serial=3 apcie=0xfffffffe -enable-kprintf-spam wdt=-1"
<t>
i was using debug since it could not build img4tool on linux or macos
<marcan>
what kernel version is that and what is the machine booting when you run that?
<t>
uname -a root:xnu-8792.81.2~2/RELEASE_AMD64_T8103 arm64
<t>
MacBook Air M1
<marcan>
how did you boot macos if you have m1n1 installed on top?
<marcan>
I meant what kernel version is kernel.development.t8103
<t>
oh this is for regular macos i guess the m1n1 is a different version?
<t>
*m1n1 proxy
<marcan>
again, if you installed m1n1 using the asahi linux installer, you *cannot* use that to boot macOS
<marcan>
you are trying to boot macOS on top of an Asahi install
<marcan>
that's never going to work
<marcan>
macOS is macOS, if you want to run macOS inside the hypervisor you need to install m1n1 as a *replacement* for the macOS kernel (which means macOS will no longer boot by itself, it will boot m1n1 instead and *then* you can run the macOS kernel under the hypervisor)
<marcan>
for machines where I also use macOS normally I just usually have multiple macOS installs (which is useful anyway since I need to pin RE/development versions to specific ones)
<t>
oh sorry thanks i was doing things from both pages
<marcan>
yeah they're separate docs for a reason :p
<marcan>
you *can* use the macOS-overlaid m1n1 to boot Linux (so you don't have to keep switching the actual boot OS to test Linux driver things) as long as you manually specify the root partition and all that, since Linux doesn't (yet) particularly care about which underlying OS container you're booting from
<marcan>
but the converse isn't true, not sure if it could be made to work but probably not well
<marcan>
but macOS will pull its root partition UUID from the ADT and we don't do anything with that right now, so if you try you'll just get an instant panic as it can't mount root (since there is no real root on an Asahi container)
<marcan>
anyway, if you're on 13.2 feel free to continue there, but we'll have to backport to 12.3 at some point (but that can happen later)
<t>
how do i remove a partition from recoveryOS? and identify from the hashes/UUID?
<t>
oh nm i can just use disk utility right
<marcan>
don't use the graphical disk utility, it's utterly broken
<marcan>
use the command line `diskutil`
<t>
too late 😟️
<marcan>
for identifying stuff it's probably easiest to just run the asahi installer and look at the output (you can just quit)
<marcan>
I mean the graphical diskutil probably won't make a complete mess but it cannot handle nonstandard partitioning *at all* and gets confused in all kinds of ways, so best avoid it
<t>
ok i think the graphical disk messed something up i can't boot into anything now i just get sent into recovery then from there i can't install a new one since all the partitions are taken or too small
<t>
do i do this in recoveryOS or in macOS: diskutil apfs addVolume disk4 APFS macOSTest -mountpoint /Volumes/macOSTest - im not able to do it
<t>
is tipd driver only current todo?
t has quit [Quit: t]
cylm_ has joined #asahi-dev
eiln has quit [Remote host closed the connection]
hexafox has joined #asahi-dev
<chadmed>
t: tipd and the imac speaker codecs are both unclaimed
roxfan has quit [Ping timeout: 480 seconds]
<jannau>
I have at least 2 small dcp subtask which should be fairly standalone:
<jannau>
1. CTM and gamma support. the former is used by nightshift on macos, gamma tables are used by other night color shift applications on macos and there's functionality in Quartz to set them
<jannau>
2. figuring out if it is enough to use timestamps in the swap struct for 120Hz/vrr, requires a macbook pro 14"/16"
<jannau>
shouldn't it be safe to read from the mailbox in m1n1's afk implementation if the rx ringbuffer has data?
<jannau>
without the read the tracer's output becomes confusing since rx and tx are out of order
<sven>
... and here I thought thunderbolt was stable but I just got another obscure assert_id=whatever crash after the first connection :(
Dementor1 has quit [Quit: Ping timeout (120 seconds)]
compassion3 has joined #asahi-dev
jluthra_ has joined #asahi-dev
jluthra has quit [Ping timeout: 480 seconds]
compassion has quit [Ping timeout: 480 seconds]
compassion3 is now known as compassion
Dementor1 has joined #asahi-dev
Dementor1 has quit [Quit: Ping timeout (120 seconds)]
Dementor1 has joined #asahi-dev
<sven>
ah, no, i'm just dumb and accidentally reverted the hotplug fix while rebasing *sigh*
leitao has joined #asahi-dev
Dementor1 has quit [Quit: Ping timeout (120 seconds)]
Lightsword has quit [Read error: Connection reset by peer]
Dementor1 has joined #asahi-dev
<j`ey>
sven: better than something else being broken!
chadmed has quit [Remote host closed the connection]
<sven>
true
bluetail89482210 has quit []
bluetail89482210 has joined #asahi-dev
Lightsword has joined #asahi-dev
chadmed has joined #asahi-dev
bluetail89482210 has quit []
bluetail has joined #asahi-dev
Lightsword has quit [Quit: ZNC]
<marcan>
OK, merged the pending stuff we had into asahi-soc
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
hexafox has quit [Ping timeout: 480 seconds]
Lightsword has joined #asahi-dev
Lightsword has quit []
Lightsword has joined #asahi-dev
<jannau>
dptx in m1n1 seems to finally work but still no hdmi output on the m2 mac mini
<sven>
ugh, looks like plug tbt device -> manual pci bus rescan -> unplug device confuses something in the pci subsystem and crashes the kernel eventually :/
<sven>
but only with the more complex topology created by the thunderbolt display. just the ethernet adapter seems to be fine
<marcan>
jannau: probably the dp2hdmi needing init (or a gpio reset) at this point?
<jannau>
as far as I can see dcp speaks with dp2hdmi, there's a reset gpio but I think macos doesn't use it
<jannau>
still a little chaotic on my part since I have the dptx-phy initialization and smc enable gpios in python and the rest in m1n1 triggered by a proxy display_configure after that
<sven>
urgh.. the rescan->unplug leaves stale buses around in e.g. /sys/class/pci_bus/
<sven>
this is going to be 'fun' to debug
leitao has joined #asahi-dev
<jannau>
macos doesn't use the dp2hdmi-gpio.function-reset gpio
<jannau>
dptxport handling is probably incomplete but dcp stopped sending messages for that endport. in the macos trace everything is dcp initiated though
seeeath has joined #asahi-dev
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
axboe has quit [Remote host closed the connection]
<sven>
for some reason everything ends up in the same iommu group though
<sven>
hotplug on the downstream port of the caldigit dock also works so I assume that there's just something wrong with the apple thunderbolt display in general where hotplug doesn't work
<sven>
(that connection also contains load-bearing duct tape on the caldigit connector since that thing only works as long as there's some pressure on it :>)
leitao has joined #asahi-dev
Dementor1 has quit [Ping timeout: 480 seconds]
seeeath has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
seeeath has joined #asahi-dev
leitao has joined #asahi-dev
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi-dev
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi-dev
yrlf has joined #asahi-dev
leitao has quit [Remote host closed the connection]
leitao has joined #asahi-dev
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
seeeath has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
seeeath has joined #asahi-dev
salimterryli has joined #asahi-dev
SalimTerryLi_ has quit [Ping timeout: 480 seconds]
seeeath has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
seeeath has joined #asahi-dev
jd20 has joined #asahi-dev
seeeath has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi-dev
seeeath has joined #asahi-dev
___nick___ has quit [Ping timeout: 480 seconds]
jd20 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cylm_ has quit [Ping timeout: 480 seconds]
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Dementor1 has joined #asahi-dev
seeeath has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
seeeath has joined #asahi-dev
jd20_ has joined #asahi-dev
jd20_ has quit [Ping timeout: 480 seconds]
<jannau>
"syslog: [nifiedPipeline.cpp:6906]VideoInterface::Plug callback: AP not ready yet, mark hot-plug pending" doesn't sound nice
<jannau>
dcp logs that after a dptx hpd with the dcp iboot powered on and m1n1 waiting on hpd from dcp iboot
stipa is now known as Guest3053
stipa has joined #asahi-dev
Guest3053 has quit [Ping timeout: 480 seconds]
hertz has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]