#
…

2022-08-03

00:02Kalissaac[m] has joined #asahi-dev
00:06mofux[m] has joined #asahi-dev
00:11AlbertoBasaglia[m] has joined #asahi-dev
00:16joerosenberg[m] has joined #asahi-dev
00:22bluetail[m] has joined #asahi-dev
00:23davidbachman[m] has joined #asahi-dev
00:25clayscode[m] has joined #asahi-dev
00:27dcavalca has joined #asahi-dev
00:28nuh^ has joined #asahi-dev
00:31dani0611[m] has joined #asahi-dev
00:37Sebhl[m] has joined #asahi-dev
00:43minkuu[m] has joined #asahi-dev
00:47jluthra has quit [Remote host closed the connection]
00:47jluthra has joined #asahi-dev
00:49peer[m] has joined #asahi-dev
01:43c10l has quit [Quit: Bye o/]
01:43c10l has joined #asahi-dev
01:47c10l has quit []
01:51c10l has joined #asahi-dev
01:57nuh^ has quit [Ping timeout: 480 seconds]
02:18hnOsmium0001 has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
02:23hnOsmium0001 has joined #asahi-dev
02:37PhilippvK has joined #asahi-dev
02:40phiologe has quit [Ping timeout: 480 seconds]
03:15nik875[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:
03:15nik875[m]kmutil configure-boot -c [path to m1n1.bin] --entry-point 2048 --lowest-virtual-address 0)
03:15nik875[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?
03:16nik875[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.}
03:17amarioguynik875[m] path to m1n1 bin is the path to the m1n1 binary
03:17nik875[m]yep i set that
03:17amarioguyalso all macOS installs are mounted under /Volumes already
03:17nik875[m]that's what i thought too, so idk why it's complaining
03:17amarioguythat is admittedly my bad
03:17nik875[m]nik875[m]: used scp to transfer the build from my second laptop
03:18amarioguyforgot to add you needed to specify --volume /Volumes/[os volume name here]
03:18amarioguythat just goes on the end of the command
03:18nik875[m]lmao /Volumes?? i should've tried that lol
03:18nik875[m]okay i'll reboot
03:18amarioguyit's already mounted
03:19amarioguywhen rOS starts
03:19amarioguyyou don't need to mount it
03:19amarioguyyou just specify /Volumes/[os install volume name here]
03:27nik875[m]Different error now, Fileset error: invalid Mach-O boot properties
03:27chadmedpaste the _exact_ command you are runnign
03:30nik875[m]kmutil configure-boot -c m1n1/build/m1n1.bin —entry-point 2048 —lowest-virtual-address 0 —volume “/Volumes/macOS RE”
03:30chadmedoh you need to also pass --raw
03:30chadmedbefore --entry-point
03:31chadmedotherwise it assumes youre passing it a macho
03:33pyropeter1 has joined #asahi-dev
03:35nik875[m]“Boot policy error: Error setting 3rd party kexts tag: code unknown boot policy error: 17”
03:36nik875[m]Might be sip actually, I think I did that step in the wrong order
03:37nuh^ has joined #asahi-dev
03:40PyroPeter_ has quit [Ping timeout: 480 seconds]
03:53nik875[m]Yep that was it, custom boot object is created successfully
03:54chadmednew u-boot borks keeb on the m1 pro
04:01doggkruse has joined #asahi-dev
05:03jannauchadmed: confirmed with asahi linux. spihid keyboard is broken with u-boot in asahi-dev
05:32doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
05:39marcanwhoops, let me see what that's about
05:54bisko has joined #asahi-dev
05:55chadmedmight have been too quick on merging that ebuild jannau :D
06:32jannaunothing wrong with the ebuild, also it's ~arm64 keyworded for a reason
06:34jannaualthough 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
06:42nuh^ has quit [Read error: Connection reset by peer]
06:42chadmedi meant merging it on my system lol
06:42nuh^ has joined #asahi-dev
06:43chadmedi only noticed kb was broken because i needed it in grub after trying again to debug the module loading thing and couldnt switch kernels
06:44jannauI tested it only on the m2 macbook as I assumed m1 would continue to work
06:44chadmedglad that stage2 is on the esp, means fixing it was as easy as grabbing the previous version boot image off the cdn
06:52CatDentures has joined #asahi-dev
07:03emilytrau[m] is now known as emilytrausheher[m]
07:03nicolas17 has quit [Ping timeout: 480 seconds]
07:51eeqk[m] has joined #asahi-dev
08:13MajorBiscuit has joined #asahi-dev
08:24kettenisI'm keeping a backup m1n1.bin on my esp such that I can easily recover in recovery mode ;)
08:29sven^-- smart!
08:29_jannau_we should update the update-m1n1 script to move the old version to m1n1.bin.old
08:29nuh^ has quit [Remote host closed the connection]
08:29kettenisthat might make sense
08:30svensounds like a good idea, yeah
08:59marcanyeah, I just had the same idea while writing that doc earlier :)
09:00the_lanetly_052 has joined #asahi-dev
09:04nehsou^ has joined #asahi-dev
09:39marcanuboot on spi keyboards is fixed
09:48chadmednew tag?
09:48_jannau_asahi-v2022.07-2
09:48kettenismarcan: what was the issue (I didn't spot it while looking at the diffs)
09:48chadmedupdating the ebuild now
09:49marcankettenis: didn't pass through the priv into leaf functions when I moved the kbd stuff to another file
09:49marcanso they were getting the wrong pointer and casting it; it worked for MTP because the inner priv was the first member
09:49marcantl;dr C is evil let's move to rust
09:50kettenismight make sense to make the priv the first member in the spi case as well
09:51marcanmaybe, but that's more fragile anyway. glad I didn't so this happened and we caught it :)
09:57chadmedfixed on my machine :)
10:19MajorBiscuit has quit [Quit: WeeChat 3.5]
10:40TiangangYang[m] has joined #asahi-dev
10:41dingodoppelt_ has quit [Quit: ZNC 1.9.x-git-170-9be0cae1 - https://znc.in]
10:41dingodoppelt has joined #asahi-dev
11:27CatDentures has quit [Quit: leaving]
11:43MajorBiscuit has joined #asahi-dev
11:57VinDuv_ has joined #asahi-dev
12:00VinDuv has quit [Ping timeout: 480 seconds]
12:00VinDuv_ is now known as VinDuv
13:23Guest6943 has quit []
13:23DragoonAethis has joined #asahi-dev
13:33mini0n has joined #asahi-dev
13:35nicolas17 has joined #asahi-dev
14:48duban has quit [Ping timeout: 480 seconds]
14:51nehsou^ has quit [Ping timeout: 480 seconds]
14:52duban has joined #asahi-dev
14:59doggkruse has joined #asahi-dev
15:53PrasanthOmanakuttan[m] has joined #asahi-dev
16:32doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:33doggkruse has joined #asahi-dev
16:35MajorBiscuit has quit [Ping timeout: 480 seconds]
16:52doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:03doggkruse has joined #asahi-dev
18:17the_lanetly_052 has quit [Ping timeout: 480 seconds]
18:41MajorBiscuit has joined #asahi-dev
18:42stinter has joined #asahi-dev
18:47stinter has left #asahi-dev [#asahi-dev]
18:59nehsou^ has joined #asahi-dev
19:40nik875[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
19:40nik875[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?
19:42nik875[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
19:42nik875[m]also i tried proxyclient/tools/picocom-sec.sh, but no dice
19:43j`eydid you build m1n1?
19:43nik875[m]Yes, it boots correctly on the guest machine
19:44povikdoes it say 'running proxy' on the last line?
19:44j`eythen it isnt the nvram command
19:45povikwhat mac device is the target? i am not sure if you can use just any usb-c port on it
19:45poviki learned ports that work and haven't been trying other :-p
19:48nik875[m]macbook pro 2021, i tried all three ports and none worked
19:48poviki use left rear there, but maybe it's occultism
19:49nik875[m]rear meaning towards the lid?
19:49nik875[m]i used the left one towards the lid
19:49jannauall 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)
19:49j`eymy guess is the cable
19:50poviknik875[m]: ah disregard what i said then
19:51nik875[m]i'm also thinking the cable, as unlikely as it is i might have two broken ones lol
19:51j`eywell not broken, but maybe charge only
19:52nik875[m]i'll see if i can get my hands on a fresh one to be sure, but this is definitely unlikely.
19:52nik875[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
19:53jannaudo you see anything usb releated in dmesg or lsusb after connecting the cable?
19:54j`eyafter booting to m1n1 ^
19:54jannauand the cable being connected before booting m1n1
19:55rosio has joined #asahi-dev
19:55rosio has quit []
19:55j`eyplug both sides of the cable, boot to m1n1, check dmesg/lsusb on host
20:00nik875[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
20:18nik875[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
20:36mini0n has quit [Read error: Connection reset by peer]
21:09doggkruse has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:20povikpuzzle of the day: on j413, is the cs42l84 codec on i2c1 or i2c3?
21:21poviksending a bottle of asahi beer to whoever can settle it by looking at ADT alone :p
21:23doggkruse has joined #asahi-dev
21:26povikanyway i am going with i2c3 for the FDT i am writing, that's where the jack codec was on m1 air
21:26povikthe first person to test it on m2 will find out...
21:26jannaumaybe there are two? ask marcan to look at the iboot processed adt
21:26povikah right, could be iboot disables one of the nodes
21:27povikunlikely there are two, but maybe there are variations from device to device
21:27povikalthough i don't know what would prompt it
21:27jannauit's on i2c3 for j493
21:35povikin the end we may see dt_disable_missing_devs in kboot.c descend to i2cX
21:35povikit's tad annoying we need to refer to the surviving node elsewhere in DT
21:35povik(apple doesn't need that)
21:35jannaudid you check the 12.5 adt as well?
21:36povikno, i have some early adt
21:43ketteniswhat was the codec again that's similar to the cs42l84?
21:47poviknot to the level of regmap compatibility, but cs42l83/42 has been a good guide in reversing the regmap
21:47poviknot an exact match all of the time, but good enough
21:49povik^ this is what we got
22:02Metroid has left #asahi-dev [Leaving]
22:08jannaucongrats povik
22:09jannaumacos 12.5 j413 template adt still has two identical cs42l84 codec nodes on i2c1 and i2c3
22:10jannauone 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
22:18MajorBiscuit has quit [Ping timeout: 480 seconds]
22:44nsklaus_ has quit [Read error: Connection reset by peer]
22:44nsklaus has joined #asahi-dev
22:44nsklaus has quit [Read error: Connection reset by peer]
22:45nsklaus has joined #asahi-dev
22:49MajorBiscuit has joined #asahi-dev
23:11MajorBiscuit has quit [Ping timeout: 480 seconds]
23:46surgeon[m] has joined #asahi-dev
…