#
…

2026-10-04

00:13maettu102 has quit [Ping timeout: 480 seconds]
00:15maettu102 has joined #asahi-alt
00:25hightower4 has joined #asahi-alt
00:32hightower3 has quit [Ping timeout: 480 seconds]
02:53tobhe_ has joined #asahi-alt
03:00tobhe has quit [Ping timeout: 480 seconds]
05:01chadmed has quit [Read error: Connection reset by peer]
05:01chadmed has joined #asahi-alt
05:25vimproved has quit [Remote host closed the connection]
05:26vimproved has joined #asahi-alt
05:35Yushi has quit [Remote host closed the connection]
05:36Yushi has joined #asahi-alt
05:39chadmedmps: cannot repro here
05:41chadmed has quit [Quit: Konversation terminated!]
05:43MichaelReeves[m]I can, I think its dependent on LLVM version
05:46JamesCalligeros[m]>markdown in commit message
05:47JamesCalligeros[m]llvm 23 also explodes building wine so thats fun
05:51MichaelReeves[m]found there's already an open rustc issue for it, so that's good: https://github.com/rust-lang/rust/issues/163614
05:52MichaelReeves[m]apparently RUSTFLAGS="-C llvm-args=-disable-loop-idiom-wcslen" can fix it for now
06:02MichaelReeves[m]doesn't repro on nightly for me
06:11JamesCalligeros[m]so odd, i cannot repro at all even with llvm 23
06:12JamesCalligeros[m]which specific version are you using
06:12JamesCalligeros[m]i am already on 23.1.2
06:16MichaelReeves[m]rustc 1.99.0 (b940084d7) with llvm 23.1.1
06:16MichaelReeves[m]I think it depends on rustc version as well because you might have a fixed version if your toolchain is beta or nightly
06:17JamesCalligeros[m]oh my rustc is still 1.98.1
06:18JamesCalligeros[m]i just use the ::gentoo provided toolchain
06:20mpson alpine llvm is 23.1.2
06:20MichaelReeves[m]it requires both a buggy LLVM (>23.1) + buggy rustc (>1.99 stable but <1.100 beta) to happen
06:20MichaelReeves[m]does the env var fix it for you too?
06:21mpslet me check
06:24mpsno, still same error
06:24MichaelReeves[m]maybe its not propagating to LLVM right
06:24MichaelReeves[m]can you try rustc nightly?
06:25MichaelReeves[m]oh wait I just realised
06:25mpsoh, wait. if i run it manually it pass
06:28mpsyes, it builds now with RUSTFLAGS="-C llvm-args=-disable-loop-idiom-wcslen"
06:29MichaelReeves[m]perfect! so yeah you can use that or from the issue it looks like rust team will back port it to 1.99.1 point release in a few weeks
06:29mpsfine, thanks
06:38mattia013 has quit [Quit: mattia013]
08:44jannaubuzo2896[m]: the grub issue? you could boot directly from u-boot and reinstall grub. Does grub actually needs to be reinstalled or is it enough to replace EFI/BOOT/BOOTAA64.EFI with a working version on the ESP? The latter could be simply done via macOS (recovery) and I don't have to look for instructions on how to boot via u-boot
08:58hightower3 has joined #asahi-alt
09:05hightower4 has quit [Ping timeout: 480 seconds]
09:12mini has quit [Quit: The Lounge - https://thelounge.chat]
09:12mini has joined #asahi-alt
09:23mpssmall note, m1n1 license is now gpl but /dev/mtd0 have this: 'm1n1 v2.0.0' and 'Licensed under the MIT license'
10:06buzo2896[m]jannau: The root fs is btrfs. Can u-boot handle that, too?
10:07buzo2896[m]Or where can I find a working version of BOOTAA64.EFI?
10:08buzo2896[m]* The root/boot fs
10:12jannaudoes u-boot need to support btrfs? i.e. are the kernel and/or initramfs stored in btrfs?
10:13jannauBOOTAA64.EFI is created by grub-install and not part of the package so that doesn't help
10:13buzo2896[m]Yes, there is only one btrfs fs and the EFI fs (besides the MacOS volumes).
10:14jannauand kernel/initramfs are not stored in the EFI fs?
10:16mpsMichaelReeves[m]: thanks. (I like this checklist about llm there :) )
10:17MichaelReeves[m]chadmed set it up :)
10:17JamesCalligeros[m]Im going to add an issue template too
10:19jannaubuzo2896[m]: you can extract BOOTAA64.EFI from https://asahi-alarm.org/asahi-base.zip
10:22MichaelReeves[m]oh btw https://github.com/AsahiLinux/m1n1/pull/696 drops the "or later" bit from the README, probably an accident?
10:22MichaelReeves[m]would comment in there but its lock
10:23MichaelReeves[m]the SPDX headers still keep the + so it should probably be one or the other
10:23JamesCalligeros[m]It doesnt really matter because of the file headers
10:23JamesCalligeros[m]But i will add it back
10:33mpsfor alpine changed to 'license="GPL-2.0-or-later"' but not yet pushed
10:36mpswill take this patch and then push
10:50chadmed has joined #asahi-alt
11:55buzo2896[m]jannau: Welp, that leads to the grub rescue shell after “unknown filesystem”. Btrfs is not known there. :(
12:05mpsI have alpine rescue image with btrfs-progs, can upload it if someone needs such tool
12:06buzo2896[m]jannau: That worked finally, thank you very much! 😃🎉
12:33buzo2896[m]So why is grub needed at all? Afaik, u-boot can do that job equally well, if not better. And a simpler setup would reduce the amount of possible problems/pitfalls.
12:35mpsgrub (and limine) have edit option to change parameter if something goes wrong
12:36mpsthough agree, u-boot is simpler and less problematic
12:38jannaudistro's choice and the main reason is it's similar to x86 PC boot (m1n1+u-boot replacing the EFI firmware) and the tooling already exists to support multiple platforms
12:39jannauin your case: u-boot has no btrfs support. it's already questionable that grub supports btrfs though
12:43mpsif the vmlinuz is on efi partition and if kernel have btrfs in-kernel then only u-boot can be used
12:43chadmedyeah but it's a decision for users/distros
12:43chadmedi use sd-boot with my ESP also being /boot
12:45mpsalpine have ext4 and btrfs in-kernel for asahi-linux (my decission)
12:46buzo2896[m]I try to avoid grub on x86 PC too, because of its complexity. I've been using refind there for years.
12:49mpsbuzo2896[m]: grub complexity was reason I switched to limine
12:50mpsnot that I'm advocating it
12:51mattia013 has joined #asahi-alt
13:01buzo2896[m]U-Boot does have [btrfs support](https://git.u-boot-project.org/u-boot/u-boot/-/tree/main/fs/btrfs?ref_type=heads) though, it just needs to be enabled at build time maybe.
13:02mpsyes, but don't know if any distro enabled it
13:12revadam has joined #asahi-alt
13:13revadam has quit []
14:31hightower4 has joined #asahi-alt
14:38hightower3 has quit [Ping timeout: 480 seconds]
14:40meow676767676 has quit [Read error: Connection reset by peer]
14:50meow676767676 has joined #asahi-alt
15:43Guest1217 has quit [Quit: Bridge terminating on SIGTERM]
15:43rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
15:47Jamie has joined #asahi-alt
15:48Jamie is now known as Guest1658
15:48rhysmdnz has joined #asahi-alt
16:23hightower3 has joined #asahi-alt
16:29bdmg_ has joined #asahi-alt
16:30hightower4 has quit [Ping timeout: 480 seconds]
18:46chadmed has quit [Remote host closed the connection]
18:46chadmed has joined #asahi-alt
18:54chadmed has quit [Read error: Connection reset by peer]
18:54chadmed has joined #asahi-alt
18:55mini has quit [Quit: The Lounge - https://thelounge.chat]
18:55mini has joined #asahi-alt
19:38ipatch has joined #asahi-alt
19:38ipatch_ has quit [Read error: Connection reset by peer]
19:41ipatch has quit [Read error: Connection reset by peer]
19:41ipatch has joined #asahi-alt
20:07chadmed has quit [Quit: Konversation terminated!]
20:08chadmed has joined #asahi-alt
20:10chadmed has quit [Read error: Connection reset by peer]
20:10chadmed has joined #asahi-alt
20:47ipatch has quit [Quit: WeeChat 4.10.1]
20:48ipatch has joined #asahi-alt
21:13hightower3 has quit [Ping timeout: 480 seconds]
21:18hightower2 has joined #asahi-alt
21:40mini has quit [Quit: The Lounge - https://thelounge.chat]
21:40mini has joined #asahi-alt
23:00integralpilot has joined #asahi-alt
23:10integralpilot has quit [Remote host closed the connection]
23:33Mayanico13 has joined #asahi-alt
23:35Mayanico13 has quit []
…