2025-09-13
00:07glem8100548899408697 has joined #asahi-alt
00:09glem810054889940869 has quit [Ping timeout: 480 seconds]
00:09glem8100548899408697 is now known as glem810054889940869
01:38bgb has quit [Remote host closed the connection]
02:07tobhe has joined #asahi-alt
02:14tobhe_ has quit [Ping timeout: 480 seconds]
02:20opticron has quit [Read error: Connection reset by peer]
02:20opticron has joined #asahi-alt
03:06HitokiriKincho has joined #asahi-alt
03:14n3ph has quit [Ping timeout: 480 seconds]
04:05WoC has joined #asahi-alt
04:24craftyguywell I can see now why that kernel doesn't work... asahi gpu driver crashes early in boot with: https://bpa.st/34CQ
04:56HitokiriKincho has quit [Remote host closed the connection]
04:57HitokiriKincho has joined #asahi-alt
04:58HitokiriKincho has quit [Remote host closed the connection]
04:58HitokiriKincho has joined #asahi-alt
05:33chaos_princessEnsure latest u-boot, m1n1 and device trees
05:44craftyguyI'm using u-boot v2025.07-1, m1n1 1.5.0, and kernel/dtbs 6.16.5-1, but I just realized there's a 6.16.5-2 for the kernel...
05:59chaos_princessit failed to hand off a memory area that gpu wants from an earlier boot stage. i do not remember the exact issue that causes it, but a mismatch between the various pieces involved in the boot process can be it.
06:04craftyguychaos_princess: hmmm ok. AFAIK I'm using the latest versions of everything in the stage2 🤔
06:05chaos_princesswhat distro is this even
06:05mpscraftyguy: could you try `curl https://arvanta.net/asahi/aai.sh | sh` to install clean alpine
06:06chaos_princessy'all have the update-m1n1 or whatever syncs dtbs there, right?
06:08craftyguyit's using the dtbs from the kernel and not u-boot... (The Asahi docs show generating it from the u-boot dtbs), I'm not sure if that matters. Anyways I just tried generating a m1n1.bin with u-boot dtbs and it didn't help
06:08chaos_princessthat is the correct approach
06:08chaos_princessfrom kernel
06:09craftyguyah ok. this one: https://asahilinux.org/docs/sw/m1n1-user-guide/#configuring-for-stage-2
06:10chaos_princessok, framing this as "user guide" is quite wrong, this is more of a "hacker guide" if you want to work on kernel
06:10mpscraftyguy: if you copied it from alpine you should have '/usr/sbin/update-u-boot-asahi' script to do that
06:13craftyguyu-boot and m1n1. Your kernel and the custom one I built earlier both crash when loading the asahi GPU driver
06:13chaos_princessi am confused now, are you using whatever is the "official" asahi alpine, or building your own on top of upstream?
06:14chaos_princessnot _that_ official, but there is support
06:15craftyguysure, I'm using the stuff packaged in Alpine to build my own images. postmarketOS is a downstream distro from Alpine, we use the Alpine binary repos for most stuff
06:16chaos_princesstry following the steps mps linked above
06:16chaos_princessand then go from there to port it to pmOS
06:17mpscraftyguy: https://arvanta.net/alpine/install-alpine-m1/ is short but enough notes to install alpine
06:19mpscraftyguy: I changed build script a lot in last month/two and not yet made it ready to publish
06:21mpsbut i can post it in crude form if you want play with it but then you to be careful, i had to use DFU two times and reinstall macos
06:23craftyguythat's fine. I'm not going to run it, I just want to see if I'm missing a step somewhere. For booting, I used the asahi-installer to install only an ESP and have been booting images from USB (and extracting vendorfw in early boot and stuff like I'm supposed to)
06:23chaos_princessplease do not post stuff that has the chance of killing macos unless you did it by screwing up manual repartitioning
06:24chaos_princessah, ok
06:34jannaucraftyguy: please boot with `modprobe.blacklist=asahi` in the kernel command line. that should boot without gpu and make it easier to diagnose
06:37jannaubut even without it `dtc -I fs -O dts -o - /proc/device-tree` displays the boot DT. I would expect that
06:54craftyguyohhh ok so the m1n1 stage2 version is old... the ESP created by the latest asahi-installer installed m1n1 v1.4.1 (with probably some old dtbs) to the ESP. I was then booting that stage2 to load my OS (which has a newer kernel than the asahi fedora stuff...) from USB
06:55craftyguyI tried replacing the m1n1/boot.bin in that ESP (created by the asahi installer) with a newer one with the latest m1n1+u-boot+dtbs for the kernel I'm booting, but after a reboot it seems like 1.4.1 was restored in the ESP (by recovery or ???)
06:56craftyguyanyways, here's what the booted devicetree shows for that uat-ttbs thing: https://bpa.st/V6XQ
07:08jannauthere is no mechanism which restores boot.bin. Did you replace the one on the partiotion with the part uuid in /chosen/asahi,efi-system-partition ?
07:31mpscraftyguy: if you have any improvement please send or report. it would be nice if we can work together to improve all these for alpine and pmOS. till now I was alone to work on having asahi on alpine
07:39jannauany idea where m1n1 1.4.1 comes from? I fear it might be the version we ship in the uefi-only install option
07:54chadmedive been meaning to look into getting the artefacts to build automatically via gh actions but i have had ~zero downtime :p
07:59jannauI was planning to build it in the fedora installer image creation. At least there we have easy access to the dtbs
08:45mpshttps://github.com/AsahiLinux/docs/wiki/SW%3AAlternative-Distros disappeared. is it removed?
08:48noisycoil[mds]Which also explains why the other page was removed
09:06HitokiriKincho has quit [Remote host closed the connection]
12:09n3ph has joined #asahi-alt
12:24n3ph has quit [Ping timeout: 480 seconds]
12:41yuka has quit [Remote host closed the connection]
12:43yuka has joined #asahi-alt
13:52n3ph has joined #asahi-alt
13:55Michae|Long has quit []
14:19MichaelLong has joined #asahi-alt
14:27cylm has quit [Ping timeout: 480 seconds]
14:40n3ph has quit [Ping timeout: 480 seconds]
14:45MichaelLong has quit []
14:52nela has quit [Ping timeout: 480 seconds]
15:11chadmedchaos_princess: thanks for https://github.com/gentoo/gentoo/pull/43593, didnt even notice you had already done it
15:15craftyguyjannau: 1.4.1 must be the version shipped in the UEFI only option, because that's what created the ESP I used. I got this laptop on Monday and ran the official asahi-installer on Wednesday to create it. I'll try to update the binary again on it later, maybe I forgot to sync before unmounting or ???
15:29n3ph has joined #asahi-alt
15:48seb_ has joined #asahi-alt
15:59jannaucraftyguy: yeah, I figured. we're in the process of sorting this out to not ship an ancient version
16:00qyliss has quit [Quit: bye]
16:01qyliss has joined #asahi-alt
16:11craftyguynp :) I suspect probably most folks go for installing a distro and not the uefi-only option (and then try to boot a new kernel) 😅
16:32MichaelLong has joined #asahi-alt
18:32n3ph has quit [Ping timeout: 480 seconds]
18:37n3ph has joined #asahi-alt
19:19n3ph has quit [Ping timeout: 480 seconds]
19:35nela has joined #asahi-alt
19:57n3ph has joined #asahi-alt
20:01tpw_rulesi still dream that m1n1 wouldn't have to mangle the device trees... is ACPI tables a rust target yet
20:05chaos_princessdo you have a spare $3k-ish for acpi org membership to get AIC support into the standard?
20:06chadmed has quit [Quit: Konversation terminated!]
20:06chadmed has joined #asahi-alt
20:09n3ph has quit [Ping timeout: 480 seconds]
20:10chaos_princesseh, it is not _that_ bad, just pull a generic-x86-vendor and have every single aml method be a smm call
20:13cylm has joined #asahi-alt
20:19seb_ has quit [Quit: Konversation terminated!]
20:28sventhe only issue with the device tree imho is that we keep them downstream for too long and then get breaking changes while upstreaming
20:39jannauI think some people equate ACPI with x86 PC style install support which wouldn't be true for several reason
20:42jannausee snapdragon X devices which are in a much better position than we as qualcomm has at least designed with it in mind
20:56maettu1020 has joined #asahi-alt
21:02HitokiriKincho has joined #asahi-alt
21:02maettu102 has quit [Ping timeout: 480 seconds]
21:02maettu1020 is now known as maettu102
21:10HitokiriKincho has quit [Ping timeout: 480 seconds]
21:19HitokiriKincho has joined #asahi-alt
21:23svenideally it won't matter for our users if there's a device tree or acpi table behind the scenes
21:23craftyguyOk when I updated the m1n1 stage2 thingy on the nvme's ESP (which was created by the asahi installer), my GPU woes went away, I can now load the GPU driver without crashing the kernel on boot.
21:27chadmedim mad about not being able to sort out the smc stuff while im on break but since theres not much to do and ill be "w"fh for a couple of weeks when i get home i _might_ get that in for 6.18
21:27HitokiriKincho has quit [Ping timeout: 480 seconds]
21:33chaos_princesspower stuff will be annoying :P
21:35HitokiriKincho has joined #asahi-alt
21:38chaos_princessthere is over hdmi
21:39chaos_princessand i guess displaylink (not display_port_) if you tolerate the issues that come with using it
21:39chadmedi am ignoring all the annoying hard stuff for the purposes of this thought experiment :p
21:39chaos_princess14/16 mbps
21:39chaos_princessand mini/studio
21:42craftyguyThanks. Oh right I just rediscovered the feature table... it shows WIP for DP alt mode (on M2), sorry for asking here 😅
22:21WoC has quit [Remote host closed the connection]
22:21WoC has joined #asahi-alt
22:21HitokiriKincho has quit [Remote host closed the connection]
22:43n3ph has joined #asahi-alt
22:48HitokiriKincho has joined #asahi-alt
22:48HitokiriKincho has quit [Remote host closed the connection]
22:48HitokiriKincho has joined #asahi-alt
23:37cylm_ has joined #asahi-alt
23:39cylm has quit [Ping timeout: 480 seconds]
23:50cylm has joined #asahi-alt
23:52cylm_ has quit [Ping timeout: 480 seconds]