#
…

2024-11-30

00:05pb17 has joined #asahi-dev
00:11chrisl has joined #asahi-dev
00:17lynndotpy has quit [Quit: Ping timeout (120 seconds)]
00:17lynndotpy has joined #asahi-dev
00:20chrisl has quit [Ping timeout: 480 seconds]
00:22buroa2354 has joined #asahi-dev
00:23tbodt has quit []
00:24tbodt has joined #asahi-dev
00:27buroa235 has quit [Ping timeout: 480 seconds]
00:27buroa2354 is now known as buroa235
00:29tbodt_ has joined #asahi-dev
00:32tbodt has quit [Ping timeout: 480 seconds]
00:52svl has quit []
01:03chrisl has joined #asahi-dev
01:11chrisl has quit [Ping timeout: 480 seconds]
01:21sand4rt has quit [Ping timeout: 480 seconds]
01:55svl has joined #asahi-dev
02:03chrisl has joined #asahi-dev
02:11chrisl has quit [Ping timeout: 480 seconds]
02:14pb17 has quit [Ping timeout: 480 seconds]
02:23chadmed_ has quit [Quit: Konversation terminated!]
02:26pb17 has joined #asahi-dev
02:49svl has quit [Remote host closed the connection]
03:05hightower4 has joined #asahi-dev
03:05chrisl has joined #asahi-dev
03:11hightower3 has quit [Ping timeout: 480 seconds]
03:13chrisl has quit [Ping timeout: 480 seconds]
03:16tobhe_ has joined #asahi-dev
03:17HitokiriKincho has quit [Remote host closed the connection]
03:17HitokiriKincho has joined #asahi-dev
03:22tobhe has quit [Ping timeout: 480 seconds]
03:28HitokiriKincho has quit [Ping timeout: 480 seconds]
03:36pb17 has quit [Ping timeout: 480 seconds]
03:43pb17 has joined #asahi-dev
03:57HitokiriKincho has joined #asahi-dev
04:10nickchanmy cpufreq status on A11 (T8015): state switch in m1n1 works perfectly for pcore and ecore using the m1 logic, however, once booted into linux the same logic wouldn't work anymore, whether from linux or from an external debugger
04:11nickchanwouldn't work = APPLE_DVFS_CMD_BUSY never clears
04:11nickchandefault governor is set to userspace to make sure the kernel never does anything on its own
04:12nora has joined #asahi-dev
04:14nora_ has quit [Ping timeout: 480 seconds]
04:15jnn has joined #asahi-dev
04:18jn has quit [Ping timeout: 480 seconds]
04:25nickchanand I made sure I did not use any boost states as configured by iBoot
04:25nickchanonly the normal states
04:30nickchannotably 'ppt-thrtl' is in the apple device tree but i did not do anything about it
04:30nickchannot sure if it could cause wedging in this way
04:49chrisl has joined #asahi-dev
04:57chrisl has quit [Ping timeout: 480 seconds]
05:02HitokiriKincho has quit [Ping timeout: 480 seconds]
05:05chrisl has joined #asahi-dev
05:14chrisl has quit [Ping timeout: 480 seconds]
05:18HitokiriKincho has joined #asahi-dev
05:18JayBeeFOSS has quit [Remote host closed the connection]
05:20JayBeeFOSS has joined #asahi-dev
05:26jn has joined #asahi-dev
05:30jnn has quit [Ping timeout: 480 seconds]
05:34pb17 has quit [Ping timeout: 480 seconds]
05:36kokoschmoko has joined #asahi-dev
05:41pb17 has joined #asahi-dev
05:50kokoschmoko has quit [Ping timeout: 480 seconds]
05:50chrisl has joined #asahi-dev
05:58chrisl has quit [Ping timeout: 480 seconds]
06:21chadmedjannau: do you remember which igt test failures you were concerned about?
06:40chrisl has joined #asahi-dev
06:48chrisl has quit [Ping timeout: 480 seconds]
07:15chrisl has joined #asahi-dev
07:28jnn has joined #asahi-dev
07:31jn has quit [Ping timeout: 480 seconds]
07:35jn has joined #asahi-dev
07:39jnn has quit [Ping timeout: 480 seconds]
07:49MikeWyxttGot the build script for my M3 MBA going, i am stumped on 1 issue: line 244 of asahi-installer/src/stub.py throws an exception "Failed to locate a usable build identity for this device") upon attempting to match some values in BuildManifest.plist (i think thats what is going on anyways..). I don't see this file anywhere, the only reference to it is in this source file. I googled it
07:49MikeWyxttand most of what comes up is results pertaining to the IPSW files. I'm going to RTFM some more and search around, but does anyone know what causes this error/what is going on in the installl_files() method?
08:21chrisl has quit [Ping timeout: 480 seconds]
08:33MikeWyxtttraced it back to load_ipsw(), disregard
08:48chrisl has joined #asahi-dev
08:54pb17 has quit [Ping timeout: 480 seconds]
08:56chrisl has quit [Ping timeout: 480 seconds]
09:00yukais it allowed to share findings based on grepping through XNU source dumps here?
09:01yukaI'm not sure if the apple source license is giving any problems
09:01yukaI was looking at why the cpu_init function hangs the t8132
09:07pb17 has joined #asahi-dev
09:09jnn has joined #asahi-dev
09:12jn has quit [Ping timeout: 480 seconds]
09:15mps has quit [Ping timeout: 480 seconds]
09:42jn has joined #asahi-dev
09:46jnn has quit [Ping timeout: 480 seconds]
09:50chaos_princessHere - you probably shouldn't. But should be fine in #asahi-re
10:14chrisl has joined #asahi-dev
10:19MikeWyxttchaos, when you had mentioned to me earlier that the scripts need patching, did anyone ever go through and fully patch it? I have it patched now to use the 14.6.1 IPSW, added the device/cpu id stuff so it just runs and works. Well, it created a bootable USB stick with no errors that is
10:20MikeWyxttthis is regarding resolving the errors the script throws when attempting to run it on an M3 MBA
10:20chaos_princessit created a what?
10:21MikeWyxtti have a usb flash drive, i had the script use that as the target media
10:21MikeWyxttit booted up and the boot option is showing m1n1 proxy :)
10:21chaos_princessi am not sure as to how you installed it to usb, since you are only supposed to install to internal ssd, but sure?
10:22chrisl has quit [Ping timeout: 480 seconds]
10:22chaos_princessthe "installation method" that people are using for development, is to install a second copy of macos using a full installer, and then to "overwrite" the macos kernel with m1n1 using kmutil
10:22chaos_princessinstaller kinda does the same thing, but only installs macos firmware, instead of full macos
10:23MikeWyxtti dunno, i just had my fd plugged in and it gave me the option to so i tried it.. i am referring to the asahi-install util as a whole. i modified a few files to get it to run
10:23MikeWyxttnow that it runs i intened to follow the developer guide
10:23chaos_princessweird, it should not allow you to install to external, but sure
10:24MikeWyxttwhen it asks for a volume, i pressed 'd' and selected my drive
10:25chaos_princessi mean, if it is not due to you patching out a check or something - it is a bug, m1n1 does not have usb driver and will not be able to load stage 2
10:25chaos_princessalso, you did the part that is done after the reboot, right? the 1tr bit
10:26MikeWyxttpart of my goal today was to not remove anything as to make it something that would be accepted upstream
10:26MikeWyxttthe only things i added was a new IPSW_VERSION entry in main.py, the entry in DEVICES in main.py
10:26chaos_princessah, you are running expert mode
10:27chaos_princessok, its fine then
10:27MikeWyxttand to get the bootstrap.sh script to work in scripts/ i changed the https://localhost:5050 to file://
10:27MikeWyxttyeah i seen marcan said this kinda stuff has to be flagged expert only
10:27MikeWyxttso i set the boolean to true for everything i did
10:28chaos_princessi would suggest wiping and re-installing to internal, unless you like having more random issues than neccessary
10:28MikeWyxttno not at all lol, just wanted to see if it would do anything at all
10:28MikeWyxttit just says Running proxy... after it rebooted btw, not sure if that answered your question
10:30chaos_princessif it has the m1n1 logo, some debug spew and running proxy - it means it worked.
10:30MikeWyxttyes it does. says no valid payload found, some stuff about the serial link and then i believe its just waiting for me to attach my host device to it
10:31MikeWyxttidek how to use m1n1 so thats my next move digging into the wiki
10:31chaos_princesspretty much. you can now use proxyclient from another computer to poke at the hardware, or load a kernel under a debugger
10:32MikeWyxttyes. super excited for that. should i submit a PR for the changes i made to get the installer script to work like this? or no?
10:34chaos_princessunless it is something other than adding machines - no. if a machine is listed as a supported in the installer, it implies that it is ready to be used by a normal user, which is very much not the case for m3+
10:35chaos_princessalso, not quite sure, but you _might_ want to reinstall using specifically firmware 15.1
10:35MikeWyxtthow do you mean? i set it up so that unless the user is in expert mode it fails and says unsupported? Is that acceptanle? or this needs to sit in my github until a later date
10:36chaos_princesslets just say that expert mode is hidden for a reason, there are too many people who think of themselves as experts :P
10:37MikeWyxtti tried 15.1 but they removed the 'RestoreBundlePath' key from one of the plists in the IPSW so i just used 14.6.1 because i didn;t have to modify anything out of the ordinary
10:38chaos_princessdepending on what hw you want to poke at 14.6 might be fine
10:39MikeWyxttif that helps thats all i did
10:39MikeWyxttand ok sounds good
10:39MikeWyxttalso, the values in min SFR and iboot version are garbage no clue what to put there
10:40mps has joined #asahi-dev
10:42chaos_princessjust don't bother for now.
10:44chaos_princesswhen "official" support comes out, it will most likely be based on at least 15.2 (depends on whether apple does certain things in it, and when exactly it will be ready)
10:44MikeWyxttahh that makes sense. i wasn't really sure how the versions were picked, i assumed perhaps it was the version the device was shipped with or something
10:45MikeWyxttwell for what its worth they shuffled around the bootcaches plist in usr/standalone
10:46chaos_princessin fact - the version that is shipped with the device should to be avoided, since there are two revisions of 15.1 - the one for m4, and the one for everything else. it was previously done that way for m2, which had a special version of 12.4, and i think, people do not want to repeat that
10:48MikeWyxttyes i noticed that on mrmachintosh when i was picking thru the versions. some were marked M3 ONLY or M4 ONLY. very odd and way over my comprehension
10:48MikeWyxttmy logic doesnt make sense because i picked 14.6.1 so yeah ill just leave it lol
10:49chaos_princessits just apple being apple, and being secretive about specific changes in their new products even from other teams that work on their os
10:52MikeWyxttyes. the work thats been done so far in spite of that fact by people with no docs or anything to reference is fascinating
10:52opticron has quit [Read error: Connection reset by peer]
10:52opticron has joined #asahi-dev
11:07kokoschmoko has joined #asahi-dev
11:08MikeWyxtttethered boot setup is a go. last question, is there a particular branch of the asahi kernel fork i should clone and build? or just clone main and go?
11:09j`eyMikeWyxtt: there's tags made
11:10MikeWyxttok i think that makes sense. thx
11:13pb17 has quit [Ping timeout: 480 seconds]
11:14mpsjust for info, yesterday when building mesa-asahi 20241128 I've got this warning https://tpaste.us/oxvg
11:14mpsthough it works fine
11:20pb17 has joined #asahi-dev
11:21chrisl has joined #asahi-dev
11:29chrisl has quit [Ping timeout: 480 seconds]
11:43jannauMikeWyxtt: I'd recommend 14.x for m3 for now. It's easier for now since the SSD has a incompatible firmware change in 15.1. as long as you don't start working on firmware driven HW support (dcp, gpu, isp) 14.6 is fine
11:45MikeWyxttokay will do
11:48jannauthat tree boots on the m3 14" macbook pro. There is some issue with the display power domains. the display will stay on with "pd_ignore_unused" on the kernel command line and removing the power-domain from chosen.framebuffer in the device tree
11:50hightower3 has joined #asahi-dev
11:50MikeWyxttI see. I have a 13" M3 MBA
11:51jannauhas that still i2c hpm (usb-c PD/port controller (ACE)) or spmi ones?
11:53MikeWyxttlet me check
11:53hightower2 has quit [Ping timeout: 480 seconds]
12:01MikeWyxttjannau: How do you find that? i dont see that in system profiler or from dmesg
12:01jannauthe ADT, apple's devicetree
12:06MikeWyxttdumping it, one moment
12:12kokoschmoko has quit [Ping timeout: 480 seconds]
12:22MikeWyxtti have the adt dumped now from ioreg. not as suggestive as i would have liked, what im i searching for here specifically?
12:29chrisl has joined #asahi-dev
12:37chrisl has quit [Ping timeout: 480 seconds]
12:39chadmeddump it from m1n1
12:39chadmedyoull get more readable and useful information since m1n1 handily offsets addresses etc for you
12:39jannausearch for hpm or usbc,sn201202x,spmi which answers the question already
12:41chadmeddo we expect some m3 devices to still have the old i2c chip?
12:41jannauI was thinking of the adt from the device via `python3 -m m1n1.adt -r adt.bin` or the templates from the IPSW Firmware/all_flash/DeviceTree.j613ap.im4p
12:42jannauchadmed: not expect, j504 (14-inch M3 mbp) still has the i2c ones
12:42chadmedoh wow okay
12:43chadmedso we know which devices get finalised first in the product cycle :p
12:43jannauthat one shipped with macos 13.5
12:45chadmed[16:21] <chadmed> jannau: do you remember which igt test failures you were concerned about? <- also sorry for the bump but im not gonna have time to look at this again for a while
12:45chadmedthe failures i got are all red herrings (tests that should have been skips or tests that failed because igt tried to swap a 0x0 rect which we can never support)
12:48jannauI don't remember exactly. it was a basic overlay test and I was mostly concerned about the overlay parameters. iirc it well of a reasonable display area. and our off active area broke that obviously
12:48jannaudid I add the face CRC support to bits/200-dcp?
13:02chadmeddoesnt look like it
13:02chadmedlast bit of work was stabilising edid audio
13:02chadmededid and audio*
13:12sand4rt has joined #asahi-dev
13:19pb17 has quit [Ping timeout: 480 seconds]
13:23chrisl has joined #asahi-dev
13:24pb17 has joined #asahi-dev
13:31chrisl has quit [Ping timeout: 480 seconds]
13:40greguu has quit [Ping timeout: 480 seconds]
14:04greguu has joined #asahi-dev
14:12hightower4 has quit [Remote host closed the connection]
14:24V has joined #asahi-dev
14:25hightower2 has joined #asahi-dev
14:29hightower3 has quit [Ping timeout: 480 seconds]
14:32V has quit [Ping timeout: 480 seconds]
14:33yukaMary: with a few changes, like adding the early return to cpu_init, adding an appropriate code path for t8132 in mcc.c, and commenting out the gxf_init, the usb driver did "just work"
14:36jannauI think Daniel already skipped the i2c init for m3 pro/max devs with spmi usb-c prot controller and usb2 just works
14:38Marynice, well I guess the custom usb pd breakout board I just receive today will be useless then ^^
14:39Marynot too sure what to tackle anyway, maybe it would make more sense if I could help on m1 stuffs
14:40yukaI couldn't get chainloading another m1n1 to work yet
14:40yukaso the debug cycle is still very annoying
14:43yukaor rather
14:43yukathis - as I recall it - should "just work" up to the point of presenting the usb serials
14:43yukabut I won't touch the mac mini today
14:53lion328 has quit [Quit: Leaving]
14:55lion328 has joined #asahi-dev
14:56pb17 has quit [Ping timeout: 480 seconds]
14:58pb17 has joined #asahi-dev
15:12wyes has joined #asahi-dev
15:15chrisl has joined #asahi-dev
15:19V has joined #asahi-dev
15:23chrisl has quit [Ping timeout: 480 seconds]
16:08chrisl has joined #asahi-dev
16:16chrisl has quit [Ping timeout: 480 seconds]
16:32pb17 has quit [Ping timeout: 480 seconds]
16:36pb17 has joined #asahi-dev
17:10chrisl has joined #asahi-dev
17:10WindowPain has quit [Remote host closed the connection]
17:12WindowPain has joined #asahi-dev
17:18chrisl has quit [Ping timeout: 480 seconds]
17:45pb17 has quit [Ping timeout: 480 seconds]
17:47chefjacob has joined #asahi-dev
17:58pb17 has joined #asahi-dev
18:12chrisl has joined #asahi-dev
18:17kokoschmoko has joined #asahi-dev
18:20chrisl has quit [Ping timeout: 480 seconds]
18:20chefjacob has quit [Quit: chefjacob]
18:31chefjacob has joined #asahi-dev
18:49kokoschmoko has quit [Ping timeout: 480 seconds]
18:56chefjacob has quit [Quit: chefjacob]
19:04chefjacob has joined #asahi-dev
19:06MikeWyxtt has quit [Ping timeout: 480 seconds]
19:09mike has joined #asahi-dev
19:10pb17 has quit [Ping timeout: 480 seconds]
19:10mike is now known as Guest1652
19:12chrisl has joined #asahi-dev
19:20chrisl has quit [Ping timeout: 480 seconds]
19:25pb17 has joined #asahi-dev
19:36chefjacob has quit [Quit: chefjacob]
19:37chefjacob has joined #asahi-dev
20:04chrisl has joined #asahi-dev
20:09Sebastian2 has joined #asahi-dev
20:12chrisl has quit [Ping timeout: 480 seconds]
20:16Sebastian2 has quit [Quit: Sebastian2]
20:33tobhe has joined #asahi-dev
20:37tobhe_ has quit [Ping timeout: 480 seconds]
20:44pb17 has quit [Ping timeout: 480 seconds]
20:51pb17 has joined #asahi-dev
21:03chrisl has joined #asahi-dev
21:11chrisl has quit [Ping timeout: 480 seconds]
21:20PaulFertser has quit [Ping timeout: 480 seconds]
21:23PaulFertser has joined #asahi-dev
21:26john-cabaj has joined #asahi-dev
21:41mike has joined #asahi-dev
21:41mike is now known as Guest1662
21:42Guest1662 is now known as MikeWyxtt
21:42Guest1652 has quit [Ping timeout: 480 seconds]
21:43chefjacob has quit [Quit: chefjacob]
22:09chrisl has joined #asahi-dev
22:17chrisl has quit [Ping timeout: 480 seconds]
22:34john-cabaj has quit [Ping timeout: 480 seconds]
23:17chrisl has joined #asahi-dev
23:25chrisl has quit [Ping timeout: 480 seconds]
23:28darkapex has quit [Remote host closed the connection]
23:29darkapex has joined #asahi-dev
23:35sand4rt has quit [Ping timeout: 480 seconds]
23:54Extern has quit [Ping timeout: 480 seconds]
23:55Extern has joined #asahi-dev
…