00:00 <zzuzzz> so I was going to set it up in the compositor configs instead, after disabling elogind and acpid -- but the system still sleeps when I press the suspend button anyway

00:27 <ponies> what a pain. is it also that void uses arch packages?

00:27 <ponies> xbps

00:37 <abby> acpid handles various events that aren't all exactly acpi, iirc

00:42 <zzuzzz> xbps yeah... I like void for the most part and I'm learning a lot. Trying to build a system from the ground up where I really understand what's going on. The main reason I chose void over arch is the official support for asahi from void and its something new (to me). I chose macbook over linux laptop for this because that's the system I actually use, and also "fun". elogind (systemd-logind replacement)

00:42 <zzuzzz> worked almost perfectly but the lockscreen only shows on resume. Which would be fine for me, as would acpid's double wake, but I'm trying to make it as slick as possible and understand as much on the way. So I'm wondering why the system goes to sleep when neither acpid nor elogind are running, and if possible disable that so I can then configure it one of those three ways

00:45 <zzuzzz> (my particular problem with elogind was that there was only a pre sleep hook, not one for both lid close and sleep button. It worked on sleep button but crashed on lid open)

05:58 <mps> zzuzzz: i use busybox acpid on alpine with scripts to control suspend on asahi

06:05 <zzuzzz> I got it working: I set elogind up to ignore lid switch and button press, wrote two scripts for sleep and keybinds. Had to add a line to sudoers but that workaround was much better than what I had before.

08:15 <ponies> zzuzzz you could make a udev rule that would be much easier

13:10 <jannau> chadmed: dist-git cgit is still out. I've mirrored the fedora 6.13.5 config at the usual place with hash 5ca8d4a172185fa15170019fc0efe49c99677e9a

13:10 <jannau> I probably won't get to update asahi-kernel today

13:11 <chadmed> jannau: that's okay. thanks for keeping the mirror up :)

13:11 <chadmed> i can handle the package bumps tomorrow. 90% of the city is still out of commission so i'll be working from home again

13:13 <Tramtrist> chadmed still out of commission? Are you in EU?

13:14 <chadmed> Tramtrist: out of commission is a turn of phrase meaning the same as "decommissioned"

13:14 <chadmed> im in brisbane, australia and we just got hit by the first cyclone in ~50 years. wasnt as bad as it could have been but 1,000,000 people at one point had no power, the roads are carnage, transport is still down, and it's been raining nonstop for 3 days

13:14 <Tramtrist> Ya.. I heard the planes and trains were all on strike in EU last week or so

13:15 <Tramtrist> Ahhhh ok

13:15 <Tramtrist> Got it

13:15 <chadmed> brisbane should never ever have cyclones as we are quite far out of the tropics but thats climate change for you

13:15 <Tramtrist> I had coworkers stranded so thought it might still be goin on there

13:15 <Tramtrist> Yeah I saw it was a big event for Australia

13:15 <chadmed> it was a monster system. the cyclone itself was pretty weak. cat 2 dropping to a tropical low by the time it made landfall but it was huuuuuge

13:16 <chadmed> heavy flooding up and down a stretch of like 1000km of coast

13:18 <Tramtrist> yeah here in japan we get them so often i dont even notice often times.. but if youre not set up/prepared it can wipe you out

13:18 <Tramtrist> Be safe

13:19 <u154ss> "I heard the planes and trains were all on strike in EU last week or so.." Where did you get this shit/disinformation from?

13:20 <psykose> maybe the german airport strike from 2 days ago?

13:21 <psykose> as we all know germany is the best country in europe :P

13:25 <chadmed> chaos_princess: are you happy for me to merge the fex overlay too?

13:25 <chaos_princess> sure

13:26 <u154ss> HH tomorrow, best country in Europe for burocracy. Best cuisine in the world also. ;(

13:30 <psykose> food in germany is quite good tbh

13:34 <u154ss> @psykose speak for yourself.

13:36 <Tramtrist> u154ss a dutch guy in belgium who was stuck in munich and couldnt get a flight for 2 days when lufthansa stopped

13:36 <Tramtrist> Sorry if I offended you with what I heard

13:36 <Tramtrist> Its just someone I talk to daily

13:36 <Tramtrist> also this is off topic.. sorry bout that

13:37 <u154ss> Should have taken the train - they are always reliable and punctual.

13:37 <Tramtrist> he told me the trains also were down

13:37 <Tramtrist> because yeah .. i mentioned that..

13:37 <Tramtrist> dont remember which train system thoguh

13:37 <u154ss> Enough. No idea what down trains are.

13:37 <Tramtrist> Ill personally take a 6 hour train over a 1 hour flight any day

13:38 <chaos_princess> u154ss: deutsche bahn and "reliable and punctual" do not belong in the same statement

13:39 <u154ss> tounge in cheek perhaps..

13:41 <u154ss> tongue ye gads..

14:48 <abby> i wish germany were real

16:46 <vimproved> chadmed: hey so i noticed that alsa-ucm-conf-asahi is currently at version 5.0 but it's still fetching from the v4 tag

16:46 <vimproved> i'm guessing this is not intentional?

16:54 <chaos_princess> that certainly looks wrong

19:04 <dererk> Hi there! It seems that after a dist-upgrade including upgrades to m1n1 and kernel, either the EFI bootloader is broken or the grub part is not able to read any sort of filesystem. Anyone aware of a "live usb" or something that is asahi-ready to do this recovery from it?

19:07 <dererk> (Debian or Debian-based prefer, but at this point anything with a shell would suit me I think :'(

19:17 <cy8aer> dererk: https://git.g3la.de/repos/-/packages/generic/asahi-debian-live/20250102

19:20 <dererk> cy8aer, hi there! thanks a bunch! =D just by chance have you experience the issues mentioned or seen them mentioned here?

19:20 <dererk> seems strange that an upgrade corrupted the EFI image, but crowdsourcing it might be helpful xD

19:21 <dererk> (didn't find anything related at the IRC archive logs)

19:22 <dererk> Oh, I am starting to find something at the logs, heh, I suck at this apparently xD

19:24 <dererk> Uhm, doesn't seem to be strictly related to the same issue I'm experiencing. It looks like either the grub.lst got corrupted or some ability of grub mbr to read the initrd and/or modules on the regular extfs is

19:27 <cy8aer> grub is in the efi partition like the m1n1 stuff. I do not know about corruptions by system but because this is the vfat efi readable from linux and macOS there are many possibilities to corrupt the files by accident.

19:27 <dererk> Just for the record, leaving the log here for any casual sailer: Cannot persist EFI variables without system partition. *** Booting bootflow 'nvme@393cc0000.blk#1.bootdev.part_3' with efi. Using prior-state device tree. Booting /\EFI\BOOT\BOOTAA64.EFI. Welcome to GRUB! error: unknown filesystem. grub rescue>

19:28 <cy8aer> crazy.

19:29 <dererk> Yeap. Will try to see if I get something more to dig into from the live system, since it's a luks encrypted FS, so It's going to be a littlebit complicated to debug

19:29 <dererk> Thanks in advance my dude @cy8aer

19:30 <cy8aer> yep should be enough to make a grub install

20:13 <dererk> well, it seems it was not culprit of grub. What I now remember is that there was kind of a broken file after the 6.13 kernel installation. It was looking for a /usr/lib/u-boot/u-boot-nodtb.bin, but it appeared to be located at another location, under /usr/lib/u-boot-asahi/apple_m1/. I did a symlink and after a reboot this issue started to appear

20:18 <dererk> I did see something you mentioned in relation to this on the IRC logs, not sure if this could make EFI/grub broken though

20:22 <jannau> not sure that's the cuplrit as u-boot is there and appears to be working. from the error message I'd have guessed the issue are missing grub modules for the filesystem

20:22 <jannau> did you change the partitionen of the ssd in the same time frame?

20:23 <dererk> I agree, sounds strange. Nope, I did not change anything except for a dist-upgrade, which was kind of jumbo, to be honest.

20:23 <jannau> at least I think I saw that message after partition changes

20:24 <jannau> where is the u-boot file you linked to coming from? Is it build with the asahi aptches?

20:27 <dererk> the message about "uknown filesystem" on grub? yeah, Agreed. It sounds a dumb error on grub not being able to load it's modules, which from a liveusb I can confirm everything looks fine.

20:28 <dererk> the u-boot-nodtb.bin is coming from u-boot-asahi package. From what I've seen here https://oftc.irclog.whitequark.org/asahi-alt/2024-02-24#32956951 It looks like the path was indeed reallocated by @cy8aer, so looks like the symlink was not what broke this

20:40 <dererk> Uhm, it seems I have two EFI partitions, maybe the recent upgrade of grub-efi-arm64 install it on the wrong one and there's a mismatch somehow... gonna sync the two parts just to be sure

20:45 <dererk> well, it seems to be coming from that side. now the error changes, so definitely my fault at some point for having two EFI parts.

20:45 <jannau> where is the second one coming from? I'm not sure that syncing will fix it

20:46 <jannau> I'd try redo grub-install with the correct partition

20:46 <dererk> I vaguely remember having created a second one by mistake and never having it deleted. At some point It seems I've been upgrading over the wrong EFI part, until now, which both EFI loaders are incompatible

20:48 <chadmed> vimproved: oof good pick

20:48 <chadmed> that reminds me, i should push v7

20:49 <chaos_princess> i've sent the PR :P

20:58 <chadmed> for v7

20:58 <chadmed> i cant see it

20:58 <chaos_princess> no, for v5

21:01 <chadmed> oh yeah i already merged it :p

21:08 <dererk> Well, indeed, it was just me. I mean, I did have to symlink the u-boot file to the new path, but the whole thing was just a stupid EFI setup on my end. Thanks a bunch for the support @cy8aer @jannau ! <3

21:37 <yuka> Does anyone know why sway with WLR_RENDERER=vulkan fails with "Could not match drm and vulkan device"

22:03 <Calandracas_> I have the same thing (on void), haven't bothered to figure it out though