Hi, I (and Refi64) have been in the process of flatpakking the Asahi/Mesa fork for Flatpak on Asahi Linux, and it seems to be in a decent state now.

I'm making this issue so that we can test and make sure the updating works properly. Doing so would make sure that Flatpak on Asahi Linux will be an enjoyable experience, as Asahi tends to break uAPI where needed to push forward development.

All that's needed is for the PKGBUILD to get a small commit (or date) bump, and the flatpak should update (or, well, make a MR to update) within the hour.

cc @refi64

https://github.com/orowith2os/mesa-asahi-flatpak

@jannau: To install on a MacMini M1, sudo pacman -S qemu-system-aarch64 should work?
As it seems, there is currently a dependency error with edk2-armvirt , as posted in the ArchLinux Forum and in ArchLinux Bug Reports.
Do you have any tips for me how to proceed?

Originally posted by @wintifrosch in AsahiLinux/docs#21 (comment)

Found a patch for 4k kernel on internet https://tg.st/u/0001-4k-iommu-patch-2022-03-11.patch

Would be great if it could be added to official Ashai repo

Basically what the title says. Chromium doesn't render pages properly after mesa-asahi-efge update. It persists in both Xorg and Wayland. I also tried on two different desktop environments (KDE and Gnome), same issue. Screenshots of the same page in Firefox and Chromium included.

I realize the kernel package was recently updated and that the pkgbuild config is running a make olddefconfig to update the kernel config to 5.18.x

However, it would be nice if the linux-asahi kernel config was updated to reflect what the actual 5.18.x config looks like.
https://raw.githubusercontent.com/AsahiLinux/PKGBUILDs/main/linux-asahi/config

Or maybe someone could just post the asahi 5.18.x config somewhere so I can see what it looks like....either way.

Thanks.

Hello.
I've read in https://asahilinux.org/2022/03/asahi-linux-alpha-release/#known-broken-applications that Chromium has to be fixed

You can probably try what is done in ROSA:
https://abf.io/import/chromium-browser-stable/blob/2e1481c3ab/chromium-browser-stable.spec#lc-411

# Use native page size on aarch64 ("if (current_cpu == "arm64")"), otherwise:
# /lib64/ld-linux-aarch64.so.1 ./bytecode_builtins_list_generator
# ./bytecode_builtins_list_generator: error while loading shared libraries:
# ./bytecode_builtins_list_generator: ELF load command alignment not page-aligned
sed -i \
	-e 's!-Wl,-z,max-page-size=4096!!g' \
	build/config/compiler/BUILD.gn

ROSA kernel has CONFIG_ARM64_4K_PAGES=y on aarch64, I don't know whay this hack is needed and works for Chromium.

I didn't find it.

BTW, I am trying to add the binder module so that I can run WayDroid. I suggest including this module in your official build, as I think Apple Silicons are a great platform to run WayDroid, a great software that runs Android using linux namespaces.

I know 4k page kernel are negatively optimized, it's not worth too much effort. But ... I need to run some emulators on asahilinux, 4k page is required. Is 4k support still on the plan ??? Thanks.

I have recently tried enabling apparmor via the recommended parameters on the arch linux wiki. aa-enabled informs that the kernel does not support apparmor since it probably wasn't compiled with the necessary env vars. Could we have an apparmor enabled kernel?

I want to use some DKMS things and not having it work on linux-asahi-edge is disappointing. I think the kernel header package should either support both kernels by default or there should be another header package for the edge kernel in repos.

Installing pacman -S qemu-base on a MacMini M1 with ArchLinux (ASAHI alpha Installer Option 2) reports dependency issues:

$ sudo pacman -S qemu-base
    resolving dependencies...
    warning: cannot resolve "edk2-ovmf", a dependency of "qemu-system-x86"
    warning: cannot resolve "seabios", a dependency of "qemu-system-x86"
    warning: cannot resolve "qemu-system-x86", a dependency of "qemu-base"
    :: The following package cannot be upgraded due to unresolvable dependencies:
          qemu-base

    :: Do you want to skip the above package for this upgrade? [y/N]

In a comment of docs Issue #21 @jannau wrote:
My bad, I was in a hurry and didn't want to update. Reproduced with the restructured qemu 7.0 package. The qemu update in archlinuxarm/PKGBUILDs@dff79d9 missed to add the additional dependencies.

Originally posted by @jannau in AsahiLinux/docs#21 (comment)

The content of /usr/lib/modules/6.1.0-rc8-asahi-3-1-ARCH/build/Makefile is:

# Automatically generated by /home/marcan/asahi/git/PKGBUILDs/linux-asahi/src/linux-asahi-6.1-rc8-3/Makefile: don't edit
include /home/marcan/asahi/git/PKGBUILDs/linux-asahi/src/linux-asahi-6.1-rc8-3/Makefile

???

Not sure where to ask, but gdb is broken on Asahi Linux.
I'm on Asahi with an M1 Mac.

$ gdb --version
GNU gdb (GDB) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
$ uname -r
6.2.0-asahi-11-1-ARCH

To reproduce, pick any random executable, and run it under gdb:

gdb ls
GNU gdb (GDB) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
/home/chriselrod/.gdbinit:6: Error in sourced command file:
No symbol table is loaded.  Use the "file" command.
Reading symbols from ls...
(No debugging symbols found in ls)
(gdb) r
Starting program: /usr/bin/ls 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
../../gdb/thread.c:85: internal-error: inferior_thread: Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0xaaab12d60fef ???
0xaaab131c486f ???
0xaaab131c4b13 ???
0xaaab1335f8e3 ???
0xaaab1316b6b7 ???
0xaaab1316c0af ???
0xaaab13095e83 ???
0xaaab12c7c77b ???
0xaaab13163a2f ???
0xaaab1316406f ???
0xaaab13164123 ???
0xaaab1301c00f ???
0xffff37165937 ???
0xffff3716229f ???
0xaaab12f8d767 ???
0xaaab12f8f0b7 ???
0xaaab1316774f ???
0xaaab12f439d7 ???
0xaaab12f5448f ???
0xaaab1335fe07 ???
0xaaab13360a6f ???
0xaaab12fa303f ???
0xaaab12fa5263 ???
0xaaab12c70f1f ???
0xffff649d7b7f ???
0xffff649d7c5f ???
0xaaab12c78c6f ???
0xffffffffffffffff ???
---------------------
../../gdb/thread.c:85: internal-error: inferior_thread: Assertion `current_thread_ != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) 

Related:
https://www.cygwin.com/bugzilla/show_bug.cgi?id=30240
https://inbox.sourceware.org/gdb-patches/[email protected]/

For what it's worth, I tried both yay -S gdb-git and spack install git@master in hopes of easily installing the latest commit, but I haven't been able to get it to build, so for now I'm stuck with a broken gdb (and am sticking to developing on x64).

There are few packages that won't run with 16k pages. One in particular is FEX.

I realize that the proper solution would be to get these packages updated to support 16k pages. However, I also wonder what would be the downside of building with 4k pages instead.

Any thoughts?

Thanks
-Sebastian