#asahi-alt · 2025-03-01 11:24
chaos_princessAs to why it is not packaged, different distros have different amounts of people working on them, and as such some things might be unfinished. It you want stuff to "just work", i suggest sticking to fedora. #asahi-alt · 2025-03-01 11:22
chaos_princessIt is not enough on its own, you also need the files from "asahi-audio" and bankstown. (All should be under asahi github org)#asahi-alt · 2025-03-01 11:17
poniesit still leaves open the question as to why it is not packaged#asahi-alt · 2025-03-01 11:16
poniesi just cloned the git and sudo make installed worked#asahi-alt · 2025-03-01 11:15
chaos_princess?#asahi-alt · 2025-03-01 11:15
poniesit works tho #asahi-alt · 2025-03-01 11:14
ponieschaos_princess: <3 <3 ty ty ty i got it #asahi-alt · 2025-03-01 11:14
chaos_princessIn that case the answer is no. They will need to package it and a few other things. #asahi-alt · 2025-03-01 11:13
poniesits not in the repos as far as i can tell although there is AsahiLinux git#asahi-alt · 2025-03-01 11:11
chaos_princessDoes alarm have a "speakersafetyd" package or similar?#asahi-alt · 2025-03-01 11:08
poniesis speaker output even supported in asahi alarm? it definitely works in fedora, but upon switching its a no#asahi-alt · 2025-02-26 12:07
userrI downgraded back to 0.2.0, it works now#asahi-alt · 2025-02-26 12:01
userrhost not found#asahi-alt · 2025-02-26 11:59
n3phdo you have dns resolution (`host domain.tld`)?#asahi-alt · 2025-02-26 11:58
userrI can't ping either so idek if I'm getting connection inside it, `ip a` shows my local ip tho#asahi-alt · 2025-02-26 11:38
n3phmuvm changed. But also, you should require it anymore, IIRC...#asahi-alt · 2025-02-26 11:30
userrHello, I'm now getting permission denied error on writing nameserver for /etc/resolv.conf and steam is not getting connection. It was working like a month ago, idk what changed#asahi-alt · 2025-02-25 08:30
leiochadmed: yes#asahi-alt · 2025-02-25 06:39
chadmedleio: youre using systemd yeah#asahi-alt · 2025-02-24 23:39
leiodon't think it'll help about the rootfs though; I did delete the old manual tries manually made fedora rootfs before all this, as it was really old, but there's no instructions on having to make a new one or anything; so maybe some leftovers still that don't let some automatic install kick in?#asahi-alt · 2025-02-24 23:38
leiosince https://github.com/FEX-Emu/FEX/commit/5ffc611d137ce992a0463a30dc3dcbe393f5cc2d#asahi-alt · 2025-02-24 23:37
leioI THINK the FEX build failure is in it requiring >=linux-headers-6.13 for DRM_IOCTL_SET_CLIENT_NAME, but it only having >=6.8 in ebuild#asahi-alt · 2025-02-24 22:58
leiohmm, maybe FEX-2501 instead of 2502 might be a problem, but the latter doesn't compile for me#asahi-alt · 2025-02-24 22:57
leioany thoughts on why steam-aarch64 on gentoo from the package (after ancient tries that I tried my best to fully remove) gives me this: https://bpa.st/SNVQ#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 22:00
Calandracasmaybe plymouth is starting before the keyboard firmware is loaded?#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:59
jannauzzUzz: which OS? notebook or desktop? can you log in via ssh? for notebook: have you tried connection an usb keyboard? for desktop: have tried a different usb port (switching between usb-c thunderbolt and usb-a/usb-c non thunderbolt)?#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-22 17:01
jannaubuilds in fedora https://copr.fedorainfracloud.org/coprs/g/asahi/mesa/build/8681745/#asahi-alt · 2025-02-22 17:00
mps_I've got this when trying to build latest mesa-asahi, 20250221#asahi-alt · 2025-02-22 16:59
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#asahi-alt · 2025-02-20 19:02
abbybecause asahi needs its own mesa fork to work#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:55
abbymesa-asahi-dri is installed?#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-20 00:19
Calandracasseriously, just stick with grub at this point :P#asahi-alt · 2025-02-20 00:09
Calandracasand seeing as you've mounted ESP to /boot/efi, systemd-boot will be unable to find them#asahi-alt · 2025-02-20 00:08
Calandracassystemd-boot requires the kernels and initramfs to be on the ESP partition (or XBOOT, which I assume you didn't create)#asahi-alt · 2025-02-20 00:08
Calandracasif grub is working for you don't bother though #asahi-alt · 2025-02-20 00:06
Calandracasthis is needed to generate the systemd "loader" entries #asahi-alt · 2025-02-20 00:06
CalandracaszzUzz, "xbps-reconfigure -f linux-asahi"#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"