#asahi · 2026-02-10 20:00
jannauMeleody: is this a Fedora Asahi Linux install? Fedora 42?#asahi · 2026-02-10 20:00
Meleodyaddendum to my message. Here's the correct link to the screenshot: https://meleody.nekoweb.org/sc3.png#asahi · 2026-02-10 19:59
cyberheadchaos_princess: the XNU kernel is quite flexible, so i'm not surprised#asahi · 2026-02-10 19:59
chaos_princessgpu-less - sure, macos even supports raspi 3 natively if you know where to look#asahi · 2026-02-10 19:58
cyberheadfor PowerPC MacOS, there existed such emulators#asahi · 2026-02-10 19:58
cyberheadchaos_princess: a Raspberry Pi or a x86 PC through tools like qemu#asahi · 2026-02-10 19:57
chaos_princesssuch as?#asahi · 2026-02-10 19:57
cyberheadchaos_princess: on non-Apple hardware#asahi · 2026-02-10 19:57
chaos_princesscyberhead: on what?#asahi · 2026-02-10 19:56
Meleodyissue happens without any custom wireplumber settings https://meleody.nekoweb.org/meleody.nekoweb.org/sc3.png#asahi · 2026-02-10 19:56
cyberheadgiven the level of reverse engineering done by Asahi devs, would it be possible to emulate Apple Silicon macOS?#asahi · 2026-02-10 19:51
MeleodyAll I can still say about the issue is that it looks fine on the login screen, only when I press the volume buttons in the session the inputs start to duplicate#asahi · 2026-02-10 19:33
Meleodybecause that didn't fix it#asahi · 2026-02-10 19:33
Meleodyis there anything I can do beyond restarting the service / rebooting?#asahi · 2026-02-10 19:32
MeleodyFYI I don't remember updating actually, this just started happening for literally no reason AFAICT#asahi · 2026-02-10 19:26
MeleodyI have dsp for my headphones but apparently macbook speakers have the same problem#asahi · 2026-02-10 19:25
Meleodyhttps://meleody.nekoweb.org/sc2.png#asahi · 2026-02-10 19:25
Meleodyhttps://meleody.nekoweb.org/sc1.png#asahi · 2026-02-10 19:25
Meleodyhi uh, did an update break wireplumber or is it just me?#asahi · 2026-02-10 09:19
jackm[m]okay, yep, i rubber duckied myself. Figured out how to do it, replaced boot.bin in finish installation app and rebooted to recovery to run that. Maybe not totally correct but worked enough to get to a liveusb :p#asahi · 2026-02-10 09:13
jackm[m]asahi installer didn't recognize that there was an existing install/broken install, so eventually ended up using diskutil to do it. I might've just rubber duckied myself, may have figured out how to update m1n1 stage1#asahi · 2026-02-10 09:10
k70@jackm: how did you recreate the EFI partition under macOS? If you use the Asahi installer to create it again (without resizing partitions) it'll update the chainload, then you'll need to hydrate the EFI partition with appropriate files.#asahi · 2026-02-10 09:03
jackm[m]there's no stage2 :p I've managed to recreate the EFI partition under macOS and my plan was to use the minimal UEFI images so I could boot a liveUSB to restore my original EFI contents + fix fstab, but I'm at a total loss as to how I update the partition UUID that m1n1 stage1 will chainload from. Any help would be appreciated, sorry for the trouble#asahi · 2026-02-10 09:03
jackm[m]Hey all, seems I've slightly screwed with my install a bit too much. Few days ago, I installed Asahi Fedora GNOME on a spare M1 Pro MBP of mine. I switched to systemd-boot (no real reason, just liked the sound of it + spare machine so why not try) and besides a few issues that went fine. However, I couldn't get the EFI partition to resize so I eventually backed it up and deleted it. I had to reboot to continue working... And can't boot because#asahi · 2026-02-10 01:08
kayliethe KDE image's graphics work fine#asahi · 2026-02-10 01:07
Yushium.. then I don't know :p#asahi · 2026-02-10 01:06
kaylieI had tried that and it didn't change anything #asahi · 2026-02-10 01:06
Yushikaylie: I have encountered similar issue and adding `debug { render-drm-device "/dev/dri/renderD128"; }` to niri config solve that#asahi · 2026-02-09 23:32
derzahlanyone ideas what im missing?#asahi · 2026-02-09 23:32
derzahlso i think everything is working but sound on my macbook m2 air, with my custom compiled 6.18.7 kernel. Ive compared modules loaded on the 6.17 kernel to make sure they are all in enabled in .config. Ive vimdiffed the configs as well. m1n1 is using the 6.18.7 device tree. But audio still wont initialize. per dmesg: https://pastebin.com/pWxGjA1U #asahi · 2026-02-09 21:59
kaylieheya, i installed fedora asahi minimal on my m1 macbook air and installed niri on top but it seems as if graphics aren't working? sddm doesn't show anything and running niri-session directly also doesn't do anything graphical#asahi · 2026-02-09 19:27
violettethis was using freebsd.py and modifying it to match linux.py uboot env filters and bootcmd#asahi · 2026-02-09 19:26
violettei've made progress: now with uboot build from asahi-releng, i get the u-boot version and a prompt (=>) but i cant type in it, and the tether link breaks #asahi · 2026-02-09 18:58
violetteill try on asahi's uboot in a few minutes, when it'll have finished compiled#asahi · 2026-02-09 18:57
violettei did, still nothing :(#asahi · 2026-02-09 18:52
jannaudid you modify the match for bootenv_start in freebsd.py? That string isn't in the u-boot env anymore#asahi · 2026-02-09 18:51
violettealso im a bit confused ; i dont think i can use run_guest or chainload, because freebsd uses multiple steps for booting?#asahi · 2026-02-09 18:49
violettei was already manually adding padding to the end of my u-boot binary. Also, i was using upstream u-boot from freebsd ports, ill try asahi's now#asahi · 2026-02-09 18:46
jannauviolette: you will likely need u-boot with https://github.com/AsahiLinux/u-boot/commit/4411224f218ee67526f74d10cd3b3a7cd70ff2ad because the u-boot env is too small with standard boot#asahi · 2026-02-09 18:43
jannautake a look at how I fixed that for linux.py in commit 6e8d7c012f84 ("tools/linux.py: Fix u-boot booting with standard boot")#asahi · 2026-02-09 18:42
jannauah, that is essentially what freebsd.py did. Switching u-boot to standard boot did break freebsd.py then as well#asahi · 2026-02-09 18:39
jannauviolette: linux.py can now boot efi binaries via u-boot. See commit a340aa629a74 "tools/linux.py: Add option to boot EFI stub linux payloads via u-boot"#asahi · 2026-02-09 17:57
chaos_princessyou may also want to run `python3 proxyclient/tools/chainload.py build/m1n1.macho` before that#asahi · 2026-02-09 17:55
violettealright ill try that thank you :D #asahi · 2026-02-09 17:54
chaos_princessyea, apparently that is a thing. if freebsd can run from efi (it should), try instead getting boot.bin from your ESP, then use `python3 proxyclient/tools/run_guest.py --raw boot.bin`#asahi · 2026-02-09 17:53
violetteit is in proxyclient/tools#asahi · 2026-02-09 17:52
chaos_princesswhere did you get freebsd.py from?#asahi · 2026-02-09 17:51
violettesame thing happens if i supply a loader and kernel#asahi · 2026-02-09 17:51
violette`python freebsd.py /usr/src/freebsd/u-boot-nodtb.bin /usr/src/freebsd/t8112-j413.dtb`#asahi · 2026-02-09 17:50
chaos_princessmind posting the command line you are using?