#
…

2025-04-26

00:04n3ph has quit [Read error: No route to host]
00:05zumi_ has joined #asahi-alt
00:05zumi has quit [Remote host closed the connection]
00:07Larwive has joined #asahi-alt
00:10zumi_ is now known as zumi
00:15Larwive has quit [Ping timeout: 480 seconds]
00:16chrisl has joined #asahi-alt
00:23Larwive has joined #asahi-alt
00:27chrisl has quit [Ping timeout: 480 seconds]
00:31Larwive has quit [Ping timeout: 480 seconds]
00:39Larwive has joined #asahi-alt
00:48Larwive has quit [Ping timeout: 480 seconds]
00:55chrisl has joined #asahi-alt
00:57Larwive has joined #asahi-alt
01:05Larwive has quit [Ping timeout: 480 seconds]
01:08chrisl has quit [Ping timeout: 480 seconds]
01:13Larwive has joined #asahi-alt
01:15chrisl has joined #asahi-alt
01:22Larwive has quit [Ping timeout: 480 seconds]
01:23chrisl has quit [Ping timeout: 480 seconds]
01:24Larwive has joined #asahi-alt
01:32Larwive has quit [Ping timeout: 480 seconds]
01:39Larwive has joined #asahi-alt
01:48Larwive has quit [Ping timeout: 480 seconds]
01:58Larwive has joined #asahi-alt
02:03tobhe_ has joined #asahi-alt
02:05andymandias has quit [Remote host closed the connection]
02:06Larwive has quit [Ping timeout: 480 seconds]
02:09tobhe has quit [Ping timeout: 480 seconds]
02:10andymandias has joined #asahi-alt
02:15Larwive has joined #asahi-alt
02:24Larwive has quit [Ping timeout: 480 seconds]
02:25Larwive has joined #asahi-alt
02:33chadmed has quit [Quit: Konversation terminated!]
02:33Larwive has quit [Ping timeout: 480 seconds]
02:34checkfoc_us9 has quit [Remote host closed the connection]
02:34HitokiriKincho has joined #asahi-alt
02:34chadmed has joined #asahi-alt
02:37checkfoc_us9 has joined #asahi-alt
02:39zerdox has joined #asahi-alt
02:42Larwive has joined #asahi-alt
02:50Larwive has quit [Ping timeout: 480 seconds]
02:58Larwive has joined #asahi-alt
03:04HitokiriKincho has quit [Quit: Leaving...]
03:06Larwive has quit [Ping timeout: 480 seconds]
03:16Larwive has joined #asahi-alt
03:25Larwive has quit [Ping timeout: 480 seconds]
03:26Larwive has joined #asahi-alt
03:34Larwive has quit [Ping timeout: 480 seconds]
03:42Larwive has joined #asahi-alt
03:51Larwive has quit [Ping timeout: 480 seconds]
03:58Larwive has joined #asahi-alt
04:07Larwive has quit [Ping timeout: 480 seconds]
04:14Larwive has joined #asahi-alt
04:19JayBeeFOSS has quit [Remote host closed the connection]
04:20JayBeeFOSS has joined #asahi-alt
04:22Larwive has quit [Ping timeout: 480 seconds]
04:24chrisl has joined #asahi-alt
04:27Larwive has joined #asahi-alt
04:32chrisl has quit [Ping timeout: 480 seconds]
04:35Larwive has quit [Ping timeout: 480 seconds]
04:36Larwive has joined #asahi-alt
04:38Larwive has quit [Remote host closed the connection]
04:38Larwive has joined #asahi-alt
04:39Larwive has quit [Remote host closed the connection]
04:39Larwive has joined #asahi-alt
04:40Larwive has quit [Remote host closed the connection]
04:40Larwive has joined #asahi-alt
04:41Larwive has quit [Remote host closed the connection]
04:42Larwive has joined #asahi-alt
04:42Larwive has quit [Remote host closed the connection]
04:42Larwive has joined #asahi-alt
05:27chrisl has joined #asahi-alt
05:35chrisl has quit [Ping timeout: 480 seconds]
06:04zumi_ has joined #asahi-alt
06:05zumi has quit [Remote host closed the connection]
06:09zumi_ is now known as zumi
06:11minecrell7 has quit []
06:11minecrell7 has joined #asahi-alt
06:33chrisl has joined #asahi-alt
06:41chrisl has quit [Ping timeout: 480 seconds]
07:17minecrell7 has quit []
07:17minecrell has joined #asahi-alt
07:20chrisl has joined #asahi-alt
07:28chrisl has quit [Ping timeout: 480 seconds]
08:04n3ph has joined #asahi-alt
08:19n3ph has quit [Read error: No route to host]
08:28chrisl has joined #asahi-alt
08:35aliasrush has quit [Remote host closed the connection]
08:36chrisl has quit [Ping timeout: 480 seconds]
08:42Larwive has quit [Ping timeout: 480 seconds]
08:43Larwive has joined #asahi-alt
08:52Larwive has quit [Read error: Connection reset by peer]
08:52n3ph has joined #asahi-alt
08:55Larwive has joined #asahi-alt
08:57n3ph has quit [Read error: No route to host]
09:03n3ph has joined #asahi-alt
09:18n3ph has quit [Read error: No route to host]
09:23n3ph has joined #asahi-alt
10:42aliasrush has joined #asahi-alt
11:19chaos_princess has quit [Quit: chaos_princess]
11:20chaos_princess has joined #asahi-alt
11:25chrisl has joined #asahi-alt
11:33chrisl has quit [Ping timeout: 480 seconds]
12:06zumi_ has joined #asahi-alt
12:06zumi has quit [Remote host closed the connection]
12:11zumi_ is now known as zumi
12:30chrisl has joined #asahi-alt
12:38chrisl has quit [Ping timeout: 480 seconds]
12:59mpsiiuc mainline kernel 6.15 will have UAPI headers for asahi GPU. and mainline mesa 25.1 have asahi dri module. So, we will not need mesa-asahi. Am I right
13:15svenI think the uapi header will only be merged for 6.16
13:27chadmedchaos_princess: that reminds me, ive pushed the new kernel and mesa to ~arm64 and ~amd64. could you please bump the fex rootfs? id like to open some cases at the iem grand final tomorrow :p
13:29chadmednvm passt is passting again
13:31mpssven: ah, thanks for info
13:33mattia013 has joined #asahi-alt
13:40chrisl has joined #asahi-alt
13:43jannaumps: upstream kernel doesn't matter much, it just unblocked the mesa driver. you still need the asahi kernel anyway for the driver + rust support (which can't build out of tree)
13:44mpsjannau: thanks, I understand
13:45mpsI mean to use linux-headers from mainline kernel to build mainline mesa
13:47mpsactually I did, but it doesn't work, because I used linux-headers from 6.15
13:47jannaumesa has drm uapi header copies, not sure if it would even use headers from kernel headers without patching
13:48chrisl has quit [Ping timeout: 480 seconds]
13:48aliasrush has quit [Remote host closed the connection]
13:48mpsidk, it is pulled during build, on alpine
13:52aliasrush has joined #asahi-alt
13:56chaos_princesschadmed: ack, but expect this to take a while for obvious reasons.
14:03n3ph has quit [Read error: No route to host]
14:04chadmedyeah no stress
14:04chadmedi would do it myself and do a PR but yknow hotel wifi and all that
14:05mpshm, GPU with kernel 6.14.4-1 and mesa-asahi 20241211 doesn't work for me
14:05noisycoil[mds]You need newer mesa
14:06chadmedmps: yes thats the whole point lol
14:06noisycoil[mds]6.14.4 only supports 20250425 and higher
14:06noisycoil[mds](Actually 20250424 too but that's buggy)
14:06mpsnoisycoil[mds]: i guessed this but i couldn't compile new on alpine
14:07noisycoil[mds]What issues did you have?
14:07noisycoil[mds](Just came from repackaging it for debian and yeah, I had to make quite a few changes)
14:08mpssome meson error about abort signal. reported this here about two months ago
14:11noisycoil[mds]Ah so you already had issues with 20250221, I guess
14:11mps12:18 ............. mps| ninja: job terminated due to signal 5: /work/aports/testing/mesa-asahi/src/mesa-asahi-20250221/output/src/compiler/spirv/vtn_bindgen2 src/asahi/libagx/libagx.spv src/asahi/libagx/libagx.cpp src/asahi/libagx/libagx.h
14:11mpsapr 12, but also earlier
14:12noisycoil[mds]I'm afraid I can't help you with that, never saw that failure :-(
14:13mpsnoisycoil[mds]: np, i'm waiting two months already
14:14mpsjust have to use older kernel
14:16jannauwaiting is unlike to fix anything. Are all other drivers building? other drivers use vtn_bindgen2 as well
14:16mpsjannau: yes, other builds fine
14:17mpswell, not sure, sorry
14:19mpswhen it fail nothing else will continue to build
14:20mpsit builds mesa 25.1-rc2 fine
14:20jannauasahi-20250425 is basically 25.1-rc2
14:21jannaucan you enable asahi in the alpine mesa 25.1-rc2 build
14:21mpswait, asahi-20250425 is released.? didn't noticed
14:22mpsjannau: yes, I did it
14:22jannauand that builds?
14:23mpsiiuc i can use mesa 25.1-rc2 with kernel 6.14.4-1
14:23mpsjannau: yrs, it builds
14:23mpss/yrs/yes/
14:24jannauyes, mesa 25.1-rc2 works with 6.14.4-1
14:24mpswill check right now. and report
14:25jannauit misses virtgpu native context support and misses a bugfix for a just discovered long standing bug
14:27mpsjannau: hah, yes, it works with mainline mesa 25.1-rc2 on kernel 6.14.4-1
14:28mpsvery fine
14:33mpsnice, just have to wait for stable mesa 25.1 release to enable all this in official alpine repo
14:36mpschaos_princess: why I didn't found your patch earlier? thanks
14:39mattia013 has quit [Ping timeout: 480 seconds]
14:40chrisl has joined #asahi-alt
14:48chrisl has quit [Ping timeout: 480 seconds]
14:59n3ph has joined #asahi-alt
15:07n3ph has quit [Ping timeout: 480 seconds]
15:07dererk has joined #asahi-alt
15:09dererkhi there! It seems that after (what I assume due to) an upgrade of the macos, uboot is crashing when going through the nvme subsytem. When manually triggering "nvme scan" I get no output.
15:11dererkIt appears to my untrained eye that It seems Mac's bootloader or something previous to uboot is preventing nvme access or something like that. If I go into Mac disk management stuff, when buttonpressing power, Startup Disk setup, I still see the, quoting "Security Policy for `Debian`" to be "Permissive Security". Which seems to me it is the one to be expected
15:12dererkAny clues or ideas I can use at my stage? :(
15:12chaos_princessdo you have some absolutely ancient install that is pre-fedora?
15:12n3ph has joined #asahi-alt
15:14dererkchaos_princess, hi there! I'm running Debian on this box (m1 pro) since a long time, like one year or so. I think I could have updated something since my previous successful boot but can't be 100% certain
15:14dererkdoes my answer help in any way? :-/
15:14chaos_princessif yes, run asahi-installer from macos, there should be an option that is sth like "update first stage m1n1" or "recover install", select that, follow the prompt
15:15dererknice! sounds like a good plan, thanks! will give it a try!
15:15chaos_princessnah, that won't help
15:15chaos_princesssince u-boot should have it's own drivers
15:16jannaudid you update macos from time to time or is this the first time since you installed debian
15:16chaos_princessi _think_ the move is to make a second install, and then try to update your debian u-boot from there
15:16dererkI'm 98% positive that I did not update macos, but m1n1 from the Debian system itself
15:17jannauchaos_princess: I think it might help. we had a change about m1n1 not shutting down the ssd after cainloading
15:17chaos_princesswait, didnt you say that you did a macos upgrade
15:17chaos_princessjannau: yea, would make sense
15:17chaos_princessanyway, it wouldn't hurt anything, so might as well try
15:18dererk@chaos_princess, I did, but at this point I'm in doubt, I regularly do dist-upgrades on the Linux machine way more frequently, so if in doubt I think it's more likely to be this due to an m1n1 or anything linux-related than macos
15:18dererk@chaos_princess, on my way, thanks!
15:18chaos_princesswell, it is kinda hard to update macos without noticing it :P
15:19dererkyeah, moreover since I almost never switch booting to mac lol
15:20dererkbtw, I'm at uboot ATM, if I do nvme scan, nothing shows up, but if I do nvme info, it does show the 3 devices, 0 being the full drive, and the other two the recovery o whatever macos uses for recovering
15:21chaos_princessmight want to go to macos and do a diskutil list
15:21dererkon my way
15:22jannauhmm, only changes from 2022 look related
15:23jannauI don't think `nvme scan` has any output
15:23n3ph has quit [Ping timeout: 480 seconds]
15:24dererkgotcha, I'm starting to think I might have, again, screwed up some partitions setup, since I had duplicated EFI and boots, and The last time I booted this machine I was messing around with ZFS, so for sure I picked one of those partitions
15:24jannaudoes `nvme part` after `nvme scan` shows the partitions?
15:24dererkchecking...
15:25jannauif yes, `boot` should work then assuming the partitions are not messed up
15:25dererkyeap, the full partitionset is shown with what It looks about right
15:25jannauif that does not work a picture / video of the u-boot output would be helpful
15:26dererkyeap, I had to record it with a camera in slow because the crashdump gets cleaned from the screenbuffer extremely quickly
15:26dererklet me type here what I can see from the crashdump
15:28dererk** Booting bootflow '<NULL>' with efi_mgr. | Booting: nvme 0 | "Synchronous Abort" handler, esr 0x86000005, far 0x0 .... and the rest is a large memory stack trace
15:29dererk(and then it restart by its own until the macos recovery is triggered)
15:30mpsjust for info, mesa-asahi 20250425 builds fine on alpine
15:31jannauif this was an u-boot update, you can restore the previous version by renaming m1n1/boot.bin.old to m1n1/boot.bin on the ESP. keep copies of both files
15:32jannauthe error is a NULL pointer dereference, so likely a bug in u-boot
15:33jannaudererk: as which version does u-boot identify itself?
15:33chrisl has joined #asahi-alt
15:36Larwive has quit [Ping timeout: 480 seconds]
15:36Larwive has joined #asahi-alt
15:40dererk@jannau, Hah, you hit the spot! 2025.04-g1c-4616dd38a-dirty (Apr 19 2025 - 23:42:25)
15:41chrisl has quit [Ping timeout: 480 seconds]
15:45mpsoh, I just wanted to update u-boot to v2025.04-1. and seeing this I will wait
15:52noisycoil[mds]cy8aer (IRC): ^ is that yours?
15:56cy8aerMine is 2025.04-1+cy8aer1
16:08m1openrc has joined #asahi-alt
16:12m1openrcHello. I am getting macsmc-ac: Failed to write 'add' to '/sys/devices/platform/soc/23e400000.smc/mac error on boot since I upgraded macOS to 15.4.
16:13m1openrcright after populating /dev with existing devices through uevents
16:14m1openrcI am also using openrc. maybe that's what's causing it. I noticed it's not getting all the latest updates from systemd for a while
16:15m1openrcany help appreciated. thanks
16:27aliasrush has quit [Ping timeout: 480 seconds]
16:33m1openrc has quit [Remote host closed the connection]
16:55tobhe_ is now known as tobhe
17:08dererkcy8aer, do you happen to know if there's a way to trigger a second uboot like a sideload or something like that? I don't remember uboot having the ability to do so... anything else other than having to rebootstrap a clean install to go back to a previous uboot would be awesome ;-(
17:09cy8aerNot really if you do not have a backup in the efi directory
17:12aliasrush has joined #asahi-alt
17:32cy8aerwhich is accessable from macOS.
17:33cy8aerthe "boot.bin" files.
17:37cy8aerin https://git.g3la.de/repos/m1-debian/src/branch/baer/doc/upgrade_stub.txt is described how to mount the partition (part Once the installation is finished).
18:05zumi_ has joined #asahi-alt
18:05zumi has quit [Remote host closed the connection]
18:09m1openrc has joined #asahi-alt
18:10zumi_ is now known as zumi
18:13m1openrcI may be not logged in but I will still read replies in logs. or you can gmail alexplsol999
18:14m1openrc has quit []
18:29n3ph has joined #asahi-alt
18:34chrisl has joined #asahi-alt
18:35n3ph_ has joined #asahi-alt
18:37n3ph has quit [Ping timeout: 480 seconds]
18:42chrisl has quit [Ping timeout: 480 seconds]
18:44andymandias has quit [Ping timeout: 480 seconds]
18:58cy8aereverything is written: Mount the efi directory in macos and look if there is a "boot.bin" backup file. Copy this to "boot.bin" and try again. It would be clever to backup the efi directory before of course.
19:30n3ph_ has quit [Read error: No route to host]
19:34chrisl has joined #asahi-alt
19:40checkfoc_us9 has quit [Remote host closed the connection]
19:42chrisl has quit [Ping timeout: 480 seconds]
19:50aliasrush_ has joined #asahi-alt
20:16n3ph has joined #asahi-alt
20:29chrisl has joined #asahi-alt
20:31aliasrush has quit [Quit: Konversation terminated!]
20:38chrisl has quit [Ping timeout: 480 seconds]
20:43Larwive has quit [Ping timeout: 480 seconds]
20:44Larwive has joined #asahi-alt
21:36waltmck has quit []
21:39waltmck has joined #asahi-alt
21:46waltmckel has joined #asahi-alt
21:51dererk has quit [Remote host closed the connection]
21:51dererk has joined #asahi-alt
21:51waltmck has quit [Ping timeout: 480 seconds]
22:00dererk has quit [Ping timeout: 480 seconds]
22:24chrisl has joined #asahi-alt
22:38chrisl has quit [Ping timeout: 480 seconds]
23:13chrisl has joined #asahi-alt
23:21chrisl has quit [Ping timeout: 480 seconds]
23:37n3ph has quit [Ping timeout: 480 seconds]
23:53aliasrush_ has quit [Quit: Konversation terminated!]
23:59andymandias has joined #asahi-alt
…