#
✕ nick:zzUzz
#asahi-alt · 2025-03-03 17:36
zzUzzMorning folks
#asahi-alt · 2025-02-22 22:25
zzUzzI had "quiet loglevel=3" in my kernel commandlinux(?) -- removed that but it didn't seem to have any effect
#asahi-alt · 2025-02-22 22:19
zzUzzI also ran "xbps-reconfigure -fa linux-asahi"
#asahi-alt · 2025-02-22 22:13
zzUzzCalandracas: that's possible. I didn't see anything about setting module order with dracut, just module presence (add_dracutmodules+=), though when I tried to launch from grub with plymouth.blacklist=yes, nothing changes. Either my config is wrong, or the initramfs wasn't properly edited, or (more likely) both are incorrect. The firmware being loaded in the wrong order, That would make a lot of sense actually
#asahi-alt · 2025-02-22 21:27
zzUzz I could not get ssh to work. External keyboard does. I realized its not so much the keyboard works, its that anytime the login screen deals with typing, it repeats the prompt. TTY2 doesn't have this problem. Heres the visual: https://ibb.co/vC6dqx7V ... It looks like I tried to login a lot, but thats not true: I never hit enter at all...
#asahi-alt · 2025-02-22 21:03
zzUzzsorry, I didnt explain since Ive been here so much lately haha. void linux, m1 air, I'll try ssh and keyboard now....
#asahi-alt · 2025-02-22 20:44
zzUzzI can reinstall completely ( I don't have much installed), but It would be a hassle and less of a learning experience
#asahi-alt · 2025-02-22 20:44
zzUzzugh.. I messed something up :/ I was trying to enable plymouth just to sort of test it out. I've never used dracut before -- I added `add_dracutmodules+=" plymouth "` in /etc/dracut.conf.d/plymouth.conf, and then ran `dracut --force` and reboot -- now my keyboard does not work at all ;_;
#asahi-alt · 2025-02-20 18:58
zzUzzmay be a dumb question... . I looked around -- how did you know to install that?
#asahi-alt · 2025-02-20 18:57
zzUzzyeah I only had mesa-dri! Thanks...
#asahi-alt · 2025-02-20 18:54
zzUzz. I think it might have to do with some package I need to install? I haven't put much on my system yet https://0x0.st/8chU.txt
#asahi-alt · 2025-02-20 18:54
zzUzzSo I've been trying to get asahi void up and running, but I've ran into an issue while installing niri (wm). The logs show it trying to use each device in /dev/dri, (renderD128, card0, card1) failing each, until "None of the following EGL extensions is supported by the underlying EGL implementation, at least one is required: ["EGL_EXT_device_drm"]" sway and xfce work
#asahi-alt · 2025-02-20 02:53
zzUzzCalandracas: I tried 'xbps-recon...', I received the same error, probably because of the reasons you listed xD I'll stick with GRUB. I'm still interested, for the sake of it
#asahi-alt · 2025-02-19 04:14
zzUzzThe error I get from the U-Boot side is: basically "Booting: nvme 0 \ No loader found. Configuration files in \loader\entries\*.conf are needed." and then "Booting /\EFI\BOOT\BOOTAA64.EFI \ No Loader found. Configuration files in \loader\entries\*.conf are needed"
#asahi-alt · 2025-02-19 03:37
zzUzz```Copied "/usr/lib/systemd/boot/efi/systemd-bootaa64.efi" to "/boot/efi/EFI/BOOT/BOOTAA64.EFI"```
#asahi-alt · 2025-02-19 03:37
zzUzz``Copied "/usr/lib/systemd/boot/efi/systemd-bootaa64efi" to "/boot/efi/EFI/systemd-bootaa64.efi"```
#asahi-alt · 2025-02-19 03:28
zzUzzI tried --no-variables, and while it appeared to succeed, It ended up the same as ```bootctl install``` with no flags
#asahi-alt · 2025-02-19 03:25
zzUzzWait I think I found it
#asahi-alt · 2025-02-19 03:24
zzUzzIs that flag "--graceful"? Using it returns ```Failed to create EFI Boot variable entry: Read-only file system```
#asahi-alt · 2025-02-19 03:16
zzUzzSo I was able to get void running on a btrfs volume using GRUB!! but I would rather use systemd/gummi-boot (or rEFInd or something else! Im open to suggestions). I tried simply using bootctl install, which gave me ```Failed to write 'LoaderSystemToken' EFI variable: Read-only filesystem```
#asahi-alt · 2025-02-18 04:11
zzUzzI'm tempted to run ```grub-install --target=arm64-efi --efi-directory=/boot/efi --removable --bootloader-id="void"```
#asahi-alt · 2025-02-18 04:10
zzUzzI'm at the grub-install section now. Started off with `mount /dev/nvme0n1p4 (or whatever) /mnt/boot/efi/` ....now /boot/efi/ contains asahi, m1n1, and vendorfw.... /etc/default/m1n1-kernel-hook has PAYLOAD=uboot, and M1N1_T=/boot/efi/m1n1.......
#asahi-alt · 2025-02-18 03:10
zzUzzI had heard of void before I heard of musl xD
#asahi-alt · 2025-02-18 03:09
zzUzzI knew that about gummiboot bc I used it before it was renamed
#asahi-alt · 2025-02-18 02:59
zzUzzsystemd-boot?? for void??
#asahi-alt · 2025-02-18 02:59
zzUzzNot AFK, just working through it again. I think that (mount /dev/whatever on /mnt/boot) is one of the things that I did my first go around which was a f*stercl*ck. I'll isolate it though now
#asahi-alt · 2025-02-18 02:15
zzUzzHey yall --- I'm trying to install void on my m1 air. I think my question pertains to installing any os through the UEFI environment only though. Im stuck on https://docs.voidlinux.org/installation/guides/chroot.html#create-a-new-root-and-mount-filesystems ...How do I mount the boot partition before I chroot in? Do I need to update GRUB? I've heard GRUB cannot boot BTRFS systems... how does asahi fedora do it?