11:53 <JanKral[m]> Hello, I have found a little problem with the installer. Some time ago, I installed Debian (following instructions at https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ ) and the system worked with no problems. Today I have installed official Asahi using the installer. It shrinked the MacOS partion by 30 GB and installed into the free space. There are two little issues that I have found: 1) When installing, when I left the default

11:53 <JanKral[m]> option max to use maximum available space, the installer did not succeed and told me it cannot fit into the free space - I had to manually set 29GB to be used. 2) After install, Debian system is not reachable. Does not matter which startup disk I select, always the official Asahi is loaded. I made a quick fix and added manually the menuentry into /boot/grub/grub.cfg in the newly installed Linux to boot into Debian. Have I done something wrong

11:53 <JanKral[m]> during the installation? Do you have any clues why always the same grub menu is loaded regardless the selected startup disk? I attach my disk partitions. Thank you for your help.

16:17 <Glanzmann> JanKral[m]: In the Debian build I backed out jannaus patch which picks the right efi partition. As a result Debian will always boot from the first efi partition. https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blob/HEAD:/bootstrap.sh#l59 moving to #asahi-alt

19:27 <Swiftloke> Hi, I find it likely that this will be considered off-topic for this chat room, but I suspect that you all have some knowledge on what flag to set to enable 64K pages on aarch64. Could any of you enlighten me? A search isn't helping, though I'll freely admit that I know nothing about kernel configuration.

19:27 <Swiftloke> The objective is to allocate a 512MB huge page, which, as I understand it, can only be accomplished with the 64KB page granule.

19:30 <j`ey> CONFIG_ARM64_64K_PAGES

19:31 <Swiftloke> Thank you!

22:24 <bread_crumb[m]> when booting from usb asahi-base iwd "connects" but journal shows network deauthentication events (reason 2 + 3), network does not work, did anyone have this happen?

22:24 <bread_crumb[m]> the network in question does work

22:24 <bread_crumb[m]> * asahi-base iwd (wireless service) "connects" but

22:25 <ChaosPrincess> anything suspicious in dmesg?

22:42 <bread_crumb[m]> <ChaosPrincess> "anything suspicious in dmesg?" <- spi-apple-of-hid spi0.0 reports packages crc mismatch

22:42 <ChaosPrincess> thats keyboard

22:42 <bread_crumb[m]> ree

22:59 <bread_crumb[m]> ping is complaining that it is a name resolution issue

22:59 <bread_crumb[m]> tried both with systemd and resolv

23:00 <bread_crumb[m]> * and resolv, i will just try tomorrow by installing nm chrooted from the working asahi install then boot usb again and check