ChanServ changed the topic of #asahi-dev to: Asahi Linux: porting Linux to Apple Silicon macs | General development | GitHub: | Wiki: | Logs:
Kalissaac[m] has joined #asahi-dev
mofux[m] has joined #asahi-dev
AlbertoBasaglia[m] has joined #asahi-dev
joerosenberg[m] has joined #asahi-dev
bluetail[m] has joined #asahi-dev
davidbachman[m] has joined #asahi-dev
clayscode[m] has joined #asahi-dev
dcavalca has joined #asahi-dev
nuh^ has joined #asahi-dev
dani0611[m] has joined #asahi-dev
Sebhl[m] has joined #asahi-dev
minkuu[m] has joined #asahi-dev
jluthra has quit [Remote host closed the connection]
jluthra has joined #asahi-dev
peer[m] has joined #asahi-dev
c10l has quit [Quit: Bye o/]
c10l has joined #asahi-dev
c10l has quit []
c10l has joined #asahi-dev
nuh^ has quit [Ping timeout: 480 seconds]
hnOsmium0001 has quit [Quit: ZNC 1.8.2+deb2build5 -]
hnOsmium0001 has joined #asahi-dev
PhilippvK has joined #asahi-dev
phiologe has quit [Ping timeout: 480 seconds]
<nik875[m]> i was following the m1n1 hypervisor documentation, and at the step where i have to create a custom m1n1 boot object for my second macos installation, i tried running this kmutil command:
<nik875[m]> kmutil configure-boot -c [path to m1n1.bin] --entry-point 2048 --lowest-virtual-address 0)
<nik875[m]> this gave me an error saying that the required argument --volume was missing, however when i specified the volume of my second macos installation it complained that the mount point couldn't be found. this problem persisted even after using diskutil mount to mount the volume. does anyone know what might be happening?
<nik875[m]> exact error: Error Domain=KMErrorDomain Code=71 "Could not find: Could not find mount point for disk4s8." UserInfo={NSLocalizedDescription=Could not find: Could not find mount point for disk4s8.}
<amarioguy> nik875[m] path to m1n1 bin is the path to the m1n1 binary
<nik875[m]> yep i set that
<amarioguy> also all macOS installs are mounted under /Volumes already
<nik875[m]> that's what i thought too, so idk why it's complaining
<amarioguy> that is admittedly my bad
<nik875[m]> nik875[m]: used scp to transfer the build from my second laptop
<amarioguy> forgot to add you needed to specify --volume /Volumes/[os volume name here]
<amarioguy> that just goes on the end of the command
<nik875[m]> lmao /Volumes?? i should've tried that lol
<nik875[m]> okay i'll reboot
<amarioguy> it's already mounted
<amarioguy> when rOS starts
<amarioguy> you don't need to mount it
<amarioguy> you just specify /Volumes/[os install volume name here]
<nik875[m]> Different error now, Fileset error: invalid Mach-O boot properties
<chadmed> paste the _exact_ command you are runnign
<nik875[m]> kmutil configure-boot -c m1n1/build/m1n1.bin —entry-point 2048 —lowest-virtual-address 0 —volume “/Volumes/macOS RE”
<chadmed> oh you need to also pass --raw
<chadmed> before --entry-point
<chadmed> otherwise it assumes youre passing it a macho
pyropeter1 has joined #asahi-dev
<nik875[m]> “Boot policy error: Error setting 3rd party kexts tag: code unknown boot policy error: 17”
<nik875[m]> Might be sip actually, I think I did that step in the wrong order
nuh^ has joined #asahi-dev
PyroPeter_ has quit [Ping timeout: 480 seconds]
<nik875[m]> Yep that was it, custom boot object is created successfully
<chadmed> new u-boot borks keeb on the m1 pro
doggkruse has joined #asahi-dev
<jannau> chadmed: confirmed with asahi linux. spihid keyboard is broken with u-boot in asahi-dev
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marcan> whoops, let me see what that's about
bisko has joined #asahi-dev
<chadmed> might have been too quick on merging that ebuild jannau :D
<jannau> nothing wrong with the ebuild, also it's ~arm64 keyworded for a reason
<jannau> although I can see the appeal of using ~arm64 in general. I'm using it so only where necessary but it's a little bit annoying
nuh^ has quit [Read error: Connection reset by peer]
<chadmed> i meant merging it on my system lol
nuh^ has joined #asahi-dev
<chadmed> i only noticed kb was broken because i needed it in grub after trying again to debug the module loading thing and couldnt switch kernels
<jannau> I tested it only on the m2 macbook as I assumed m1 would continue to work
<chadmed> glad that stage2 is on the esp, means fixing it was as easy as grabbing the previous version boot image off the cdn
CatDentures has joined #asahi-dev
emilytrau[m] is now known as emilytrausheher[m]
nicolas17 has quit [Ping timeout: 480 seconds]
eeqk[m] has joined #asahi-dev
MajorBiscuit has joined #asahi-dev
<kettenis> I'm keeping a backup m1n1.bin on my esp such that I can easily recover in recovery mode ;)
<sven> ^-- smart!
<_jannau_> we should update the update-m1n1 script to move the old version to m1n1.bin.old
nuh^ has quit [Remote host closed the connection]
<kettenis> that might make sense
<sven> sounds like a good idea, yeah
<marcan> yeah, I just had the same idea while writing that doc earlier :)
the_lanetly_052 has joined #asahi-dev
nehsou^ has joined #asahi-dev
<marcan> uboot on spi keyboards is fixed
<chadmed> new tag?
<_jannau_> asahi-v2022.07-2
<kettenis> marcan: what was the issue (I didn't spot it while looking at the diffs)
<chadmed> updating the ebuild now
<marcan> kettenis: didn't pass through the priv into leaf functions when I moved the kbd stuff to another file
<marcan> so they were getting the wrong pointer and casting it; it worked for MTP because the inner priv was the first member
<marcan> tl;dr C is evil let's move to rust
<kettenis> might make sense to make the priv the first member in the spi case as well
<marcan> maybe, but that's more fragile anyway. glad I didn't so this happened and we caught it :)
<kettenis> true
<chadmed> fixed on my machine :)
MajorBiscuit has quit [Quit: WeeChat 3.5]
TiangangYang[m] has joined #asahi-dev
dingodoppelt_ has quit [Quit: ZNC 1.9.x-git-170-9be0cae1 -]
dingodoppelt has joined #asahi-dev
CatDentures has quit [Quit: leaving]
MajorBiscuit has joined #asahi-dev
VinDuv_ has joined #asahi-dev
VinDuv has quit [Ping timeout: 480 seconds]
VinDuv_ is now known as VinDuv
Guest6943 has quit []
DragoonAethis has joined #asahi-dev
mini0n has joined #asahi-dev
nicolas17 has joined #asahi-dev
duban has quit [Ping timeout: 480 seconds]
nehsou^ has quit [Ping timeout: 480 seconds]
duban has joined #asahi-dev
doggkruse has joined #asahi-dev
PrasanthOmanakuttan[m] has joined #asahi-dev
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
doggkruse has joined #asahi-dev
MajorBiscuit has quit [Ping timeout: 480 seconds]
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
doggkruse has joined #asahi-dev
the_lanetly_052 has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi-dev
stinter has joined #asahi-dev
stinter has left #asahi-dev [#asahi-dev]
nehsou^ has joined #asahi-dev
<nik875[m]> i'm still following the m1n1 hypervisor documentation, and i did manage to successfully create the custom boot object. but connecting a second pc (running linux) via a usb-a to usb-c cable does not show anything in /dev on the host. this is true both when m1n1 is booted and when normal macos is booted. i tested all usb ports involved and they do work, and i tried two different cables (both of which are chargers that i've verified to
<nik875[m]> transfer power, though i couldn't check for data transfer since i don't have another device with a female usb-c port). anyone know what might be happening?
<nik875[m]> i have a theory that it might be because of a command that i didn't run yet from a different documentation page: "nvram boot-args=-v". i have no idea what that command does though
<nik875[m]> also i tried proxyclient/tools/, but no dice
<j`ey> did you build m1n1?
<nik875[m]> Yes, it boots correctly on the guest machine
<povik> does it say 'running proxy' on the last line?
<nik875[m]> Yes
<j`ey> then it isnt the nvram command
<povik> what mac device is the target? i am not sure if you can use just any usb-c port on it
<povik> i learned ports that work and haven't been trying other :-p
<nik875[m]> macbook pro 2021, i tried all three ports and none worked
<povik> i use left rear there, but maybe it's occultism
<nik875[m]> rear meaning towards the lid?
<nik875[m]> i used the left one towards the lid
<jannau> all usb-c ports should provide acm over usb except on mac studio m1 max (front ports don't work) and the 4 port imac (I think only the 2 ports closest to the power connector work)
<j`ey> my guess is the cable
<povik> nik875[m]: ah disregard what i said then
<nik875[m]> i'm also thinking the cable, as unlikely as it is i might have two broken ones lol
<j`ey> well not broken, but maybe charge only
<nik875[m]> i'll see if i can get my hands on a fresh one to be sure, but this is definitely unlikely.
<nik875[m]> are you supposed to be able to see anything in /dev when the cable is connected and the guest machine is fully booted into normal macos? because i didn't see anything there lol
<povik> no
<jannau> do you see anything usb releated in dmesg or lsusb after connecting the cable?
<j`ey> after booting to m1n1 ^
<jannau> and the cable being connected before booting m1n1
rosio has joined #asahi-dev
rosio has quit []
<j`ey> plug both sides of the cable, boot to m1n1, check dmesg/lsusb on host
<nik875[m]> it was probably the cable—still booted into macos, but lsusb shows "Apple MacBook Pro". that wasn't happening with the old cable. i'll boot into m1n1 to verify
<nik875[m]> Okay it was the cable, after switching out I was able to start booting the target macOS installation. Now I’m stuck on the rainbow apple logo though
mini0n has quit [Read error: Connection reset by peer]
doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<povik> puzzle of the day: on j413, is the cs42l84 codec on i2c1 or i2c3?
<povik> sending a bottle of asahi beer to whoever can settle it by looking at ADT alone :p
doggkruse has joined #asahi-dev
<povik> anyway i am going with i2c3 for the FDT i am writing, that's where the jack codec was on m1 air
<povik> the first person to test it on m2 will find out...
<jannau> maybe there are two? ask marcan to look at the iboot processed adt
<povik> ah right, could be iboot disables one of the nodes
<povik> unlikely there are two, but maybe there are variations from device to device
<povik> although i don't know what would prompt it
<jannau> it's on i2c3 for j493
<povik> in the end we may see dt_disable_missing_devs in kboot.c descend to i2cX
<povik> it's tad annoying we need to refer to the surviving node elsewhere in DT
<povik> (apple doesn't need that)
<jannau> did you check the 12.5 adt as well?
<povik> no, i have some early adt
<kettenis> what was the codec again that's similar to the cs42l84?
<povik> none
<povik> not to the level of regmap compatibility, but cs42l83/42 has been a good guide in reversing the regmap
<povik> not an exact match all of the time, but good enough
<povik> ^ this is what we got
Metroid has left #asahi-dev [Leaving]
<jannau> congrats povik
<jannau> macos 12.5 j413 template adt still has two identical cs42l84 codec nodes on i2c1 and i2c3
<jannau> one getting zapped by iboot is the only reason I can think of. still strange that there would be two logic board variants which differ in this aspect
<povik> yeah
MajorBiscuit has quit [Ping timeout: 480 seconds]
nsklaus_ has quit [Read error: Connection reset by peer]
nsklaus has joined #asahi-dev
nsklaus has quit [Read error: Connection reset by peer]
nsklaus has joined #asahi-dev
MajorBiscuit has joined #asahi-dev
MajorBiscuit has quit [Ping timeout: 480 seconds]
surgeon[m] has joined #asahi-dev