#
…

2025-04-12

00:25Tramtris1 has joined #asahi-alt
00:25Tramtrist has quit [Read error: Connection reset by peer]
00:51kraem has joined #asahi-alt
01:29kraem has quit [Ping timeout: 480 seconds]
02:00Tramtrist has joined #asahi-alt
02:01Tramtris1 has quit [Read error: Connection reset by peer]
02:01Tramtrist has quit [Read error: Connection reset by peer]
02:01Tramtrist has joined #asahi-alt
02:20tobhe_ has joined #asahi-alt
02:27tobhe has quit [Ping timeout: 480 seconds]
03:31chadmedonly thing im not sure about is the splitting of the LLVM deps. should i ask in #gentoo-desktop?
04:13kraem has joined #asahi-alt
04:18JayBeeFOSS has quit [Remote host closed the connection]
04:20JayBeeFOSS has joined #asahi-alt
04:25mattia013_ has joined #asahi-alt
04:47kraem has quit [Ping timeout: 480 seconds]
05:16zerdox has joined #asahi-alt
05:42mattia013_ has quit [Ping timeout: 480 seconds]
05:57chadmed has quit [Ping timeout: 480 seconds]
06:03chadmed has joined #asahi-alt
06:09chadmed_ has joined #asahi-alt
06:13chadmed has quit [Ping timeout: 480 seconds]
06:15chadmed_ is now known as chadmed
07:06n3ph has joined #asahi-alt
07:15n3ph has quit [Ping timeout: 480 seconds]
07:58n3ph has joined #asahi-alt
08:27n3ph has quit [Ping timeout: 480 seconds]
08:40JayBeeFOSS has quit [Remote host closed the connection]
08:41JayBeeFOSS has joined #asahi-alt
08:57leiochadmed: the REQUIRED_USE of vulkan looks wrong to me; does it fail to build something else when vulkan is disabled, like I assume is the case without opencl?
08:59maverick46 has joined #asahi-alt
09:00maverick46Is anyone online?
09:01maverick46 has quit [Remote host closed the connection]
09:15jannauvulkan is not required. neither is opencl but the driver needs the opencl dependencies as build deps
09:23beastd|2 has quit [Quit: KVIrc 5.2.6 Quasar http://www.kvirc.net/]
09:39chadmedso REQUIRED_USE asahi? ( llvm ) and then replicate the opencl deps in the llvm_gen_dep thing like we do currently in the overlay
09:54mpslatest mesa-asahi still fails to build on my alpine system
10:04Zeroine has joined #asahi-alt
10:05jannauhow is it handled for intel? does it simply dependen on externall build intel-clc for the build?
10:08jannaumps: specifically the asahi driver? what is latest mesa asahi-20250221?
10:10chadmedjannau: intel just pulls in libclc, but i thought we needed opencl at runtime too
10:15mpsjannau: yes, mesa asahi-20250221
10:18mpserror is
10:18mpsninja: 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
10:49jannauchadmed: I suspect we can add support to mesa_clc to build asahi_clc, not sure if it's worth adding asahi_clc as indepedent package
10:55chadmedi dont think a separate package makes much sense. id rather not contribute to the fragmented state of opencl-related tooling
10:55chadmedin the meantime ill just copy what we do in the overlay with the replicated llvm required use
10:55jannauthat's why I want to add it to mesa_clc
10:56chadmedthat requires changes to mesa upstream, yes?
10:57chadmedi fully agree with you btw, i just mean we do the overlay thing until mesa_clc has what we need
10:57jannauyes but minor ones
10:58jannauI want to get this into mesa 25.1-rc1
11:01jannauit might not need changes
11:02chadmeddid alyssa already do this with 3b1166da?
11:04jannauthat's not all. we still need asahi_clc
11:11chadmedso what do we need to do to integrate it with mesa_clc? it seems quite bespoke
11:54floklichaos_princess: I added a few pr_info! statements, it fails at the `data.patch_bootargs` call
11:55chaos_princesshow old is your install
11:55floklichaos_princess: old, I recall having to manually do something to get webcam to work
11:55floklior you mean which version of MacOS is installed?
11:56chaos_princesswhat firmware version is your install using
11:56flokliis that printed somewhere?
11:57chaos_princessit is somewhere in the device tree, probably under chosen
11:57flokliasahi,system-fw-version ?
11:57flokli"unknown"
11:58chaos_princesswhat other version-like things are there
11:59flokliasahi.iboot1-version iBoot-11881.81.2 / asahi.iboot2-version iBoot-7459.121.3 / asahi,os-fw-version 12.4
12:00chaos_princessasahi,os-fw-version 12.4 - the culprit
12:00chaos_princessBOOTARGS_OFFSET and BOOTARGS_SIZE are different on 12.4
12:00chaos_princessso, either update to 13.5 or patches welcome
12:01flokliI'd prefer updating I think :-D
12:03flokliso is this updating macos, or running asahi-fwextract?
12:03chaos_princessthis is re-installing the apfs stub
12:20chadmedZeroine: folks typically dont respond to "hi" or "anyone there" on irc
12:22ZeroineEh, depends on who you're talking to.
12:23ZeroineI wasn't born with IRC but I've been hanging out here for a few years now.
12:32n3ph has joined #asahi-alt
12:33floklichaos_princess: sorry for my stupidity, but I don't know how to do this, and looking around in the docs didn't help much. I ran the asahi-installer, and that upgraded m1n1 stage1 from 1.2.9 to 1.4.14, but didn't change asahi,os-fw-version
12:34jannauchadmed: you're right, we need clc/llvm at runtime. sorry
12:34chaos_princessyou have to completely remove the apfs and efi paritions, do a completely new uefi-only install, and then re-create whatever bootloader files are needed on new esp
12:35martinr has joined #asahi-alt
12:35jannaucopy the m1n1 and EFI folders from the old ESP
12:35jannauand everything else which is not firmware
12:36jannauthe installation log from the initial install m,ight be interesting as well but is essentially useless now
12:37flokliso backup contents from current apfs somewhere, use diskutil to delete that partition, run asahi linux installer, copy things back to new apfs partition
12:37jannauchadmed: I noticed only after I had everything in place
12:38chaos_princessfrom esp, apfs shouldn't contain anything of vault
12:38jannauI don't think we keep anything interesting on the apfs, just the ESP
12:39flokliok, but I delete both ESP and NixOS APFS, gotcha
12:40jannauif the nixos apfs has an customized volume icon that's could be saved. .Volume*.icns or so
12:42jannauplease do backups first, if you have enough space in the macos apfs partition you could resize that by 3GB and do a separate uefi-only install first
12:43chadmedjannau: no stress at all. ill sort out the MR tomorrow to just do what we do in the overlay for now
13:18floklichaos_princess: hello from asahi,os-fw-version 13.5
13:35chadmedflokli: mics should work now :)
13:36floklii still need to do the firmware dance, but working on it :-)
13:43flokliyes, with the new firmware aop probes properly, and I now see a microphone. I'll test if it actually records proper sound later. Thanks :-)
14:09chadmed has quit [Quit: Konversation terminated!]
14:10chadmed has joined #asahi-alt
14:16noisycoil[mds]chadmed: Probably documenting the firmware requirements for mics is a good idea. Fedora was never affected, but the fw thing keeps happening to most who installed alt distros earlier than that
14:17noisycoil[mds]We had 3 just in Debian
14:54n3ph_ has joined #asahi-alt
14:57n3ph has quit [Ping timeout: 480 seconds]
15:03ZeroineThanks for any answers in advance =)
15:03ZeroineI've got several questions about OpenBSD on the M1 Air so I made a paste https://bpa.st/FJVQ
15:32flokliIs there any hard-coding of esp partition uuids in the apfs stub?
15:33chaos_princessyes, the installed m1n1 stage 1 has a reference to the esp
15:33jannaunot in the apfs stub but in the installed 1st stage m1n1
15:34flokliI successfully deleted the old apfs container and esp, and now wanted to grow the "new" esp past the space freed by the old ones. But it seems fatresize crashes on Asahi (page size assumptions maybe?) and MacOS cannot grow vfat
15:34flokliAt least not the graphical disk utility app
15:35flokliIt ranted about something and told me I can still try if I'm desperate
15:35flokliI'm wasn't sure I wanted to be that desperate:-D
15:36jannaudo you have use for larger esp?
15:36flokliYes, NixOS stores different generations of initrd and kernels
15:36flokliAnd it runs out of space very quickly
15:37jannauah, fedora uses a separate /boot partition
15:39flokli"The information sector has the wrong signature (0). Select cancel for now, and send in a bug report. If you're desperate, it's probably safe to ignore"
15:40flokli/nix/store/zysnblhy9yakqj6v3n85f9pg47pn8x2d-gparted-1.7.0/bin/.gparted-wrapped: line 231: 6478 Segmentation fault (core dumped) $BASE_CMD
15:47tpw_rulesflokli: (been very busy with work sorry about the maintenance) you can set UUIDs with gdisk
15:47tpw_rulesm1n1 looks for the GPT one, not the FAT one
15:51floklitpw_rules: Ok, so I'll just copy things to a new vfat sized properly, and force the partuuid to the old one. Thanks.
15:51flokliAnd no worries, we all have IRL stuff :-)
15:53tpw_rulesflokli: bingo. you can also regenerate the necessary-for-boot parts of the ESP completely with nixos-install and a flash drive, but of course the asahi installer writes logs and firmware it would be annoying to lose
15:53tpw_rulesalso also you can limit the number of generations in your config and lessen the chance of filling it up
15:54flokliTrue, though I cannot really reclaim the space properly for MacOS either. So might as well use it for ESP ;-)
15:56floklitpw_rules: now I have you here, I'm wondering if we can make the UX a bit nicer and get NixOS to "discover" the firmware without looping it into evaluation
15:57flokliThere's a cpio archive, sd-boot can probably concatenate it to the initrd and we pass it on from there, rather than being forced to set hardware.firmware to it
15:57flokliI'll probably toy around with this a bit in the next few days. In addition to bumping some more PRs.
16:45Guest13178 has quit [Quit: Bridge terminating on SIGTERM]
16:45rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:47Jamie has joined #asahi-alt
16:48Jamie is now known as Guest13544
16:48rhysmdnz has joined #asahi-alt
18:06ahepp has joined #asahi-alt
18:09flokliPartition GUID surgery was successful, btw :-)
18:37mx08 has quit [Quit: WeeChat 3.8]
18:40mx08 has joined #asahi-alt
19:05n3ph_ has quit [Ping timeout: 480 seconds]
19:16n3ph has joined #asahi-alt
19:49n3ph has quit [Ping timeout: 480 seconds]
19:51n3ph has joined #asahi-alt
20:31martinr has quit [Ping timeout: 480 seconds]
21:31jannauchadmed: I'm using https://paste.centos.org/view/3b04f721 (running 6.14.2-1 with stable uapi patches on j314)
21:36Zeroine has quit [Quit: Connection closed for inactivity]
21:36chadmedyep awesome thats pretty close to the overlay
21:36chadmedill have coffee and sort out the MR :)
21:47chadmedstill have to figure out this dist-kernel mess too
21:48chadmedim kind of out of ideas apart from asahi profiles at this point but i really dont think thats a can of worms we want to open
21:51n3ph has quit [Ping timeout: 480 seconds]
21:58jannauI should update that. I don't think the lower minimum in the overlay actually works. I certainly don't test anything but Fedora's stable rust (possible trailing by a few days)
22:12tpw_rulesflokli: it's been posited, but i never liked it cause you have to have python in the initrd to extract it
22:12tpw_rulesor figure out how to detect that the python version changed and re-execute the extractor
22:15Zeroine has joined #asahi-alt
22:41n3ph has joined #asahi-alt
23:12ZeroineAnybody know how to get the bwfm interface working in OpenBSD? OpenBSD's install script should take care of this but apparently it's broken so I think I'd have to get it from firmware.tar on the EFI partition. On the OpenBSD mailing list there's complaints of bwfm not working and not appearing in dmesg since around the 14.5 MacOS version update. I don't see anything in dmesg either but I thought this was because I don't have the
23:12Zeroinefirmware installed.
23:12ZeroineI can give more details and links, just didn't wanna make the question too long.
23:13chadmedyou should have asahi-fwupdate or some analogue that installs the apple-specific firmware to wherever openbsd needs it to be
23:13chadmedthe firmware for the wifi/bt card comes from the system and is not redistributed in linux-firmware or anything like that
23:15Zeroinechadmed: yeah, that'd be fw_update but it doesn't seem to install it, I tried installing with ethernet connected as well but it only got the apple-boot-firmware
23:16chadmednot sure why kettenis isnt in #asahi-alt but he maintains the openbsd stuff afaik
23:17Zeroineyea, I've seen him chat about OpenBSD a lot while looking through IRC logs
23:18ZeroineI think the WiFi firmware is only installed once you're actually installing OpenBSD, there's a script that I think should do this https://raw.githubusercontent.com/openbsd/src/cb90b220d83d832a1df01974a385a7822a9a2fab/distrib/arm64/ramdisk/install.md
23:18ZeroineMaybe fw_update doesn't deal with the WiFi firmware then, I don't know
23:26chadmedjannau: dont we also need libclc at runtime, not just a BDEPEND?
23:30zerdox has quit [Ping timeout: 480 seconds]
23:45pthariensflame has joined #asahi-alt
23:45pthariensflame has quit []
23:46chadmedaaa we cant do "if use" outside of functions anyway
23:50n3ph has quit [Ping timeout: 480 seconds]
23:52tobhe_Zeroine: release or snapshot?
23:53Zeroinethe 6.7 release
23:53tobhe_there was a bug in 6.7, let me see if I find some info
23:53tobhe_I think snapshot works better
23:53tobhe_s/6.7/7.6/
23:53tobhe_or you wait a few days for 7.7 :)
23:54Zeroineoh yeah, my bad =D
23:54ZeroineI'll try a snapshot then
23:57tobhe_since we are in freeze the current snapshot is pretty much 7.7 anyway
23:58tobhe_this was the issue
23:59tobhe_something changed in the firmware, broke aplsmc and that broke the check in the installer to activate the asahi firmware extraction special sauce
…