asahilinux / docs Goto Github PK

LUKS disk encryption would be a nice-to-have option with the installer. However, I can understand this potentially not being an option as the installer has to play nicely with the existing APFS filesystem.

Perhaps systemd-homed using LUKS as the storage mechanism could be considered as a compromise as the user's home directory (perhaps the most relevant part of the filesystem to keep private) would be LUKS encrypted. It wouldn't be full-disk encryption, but still could get some of the way there for user's hoping to have an additional layer of security. However, I could understand this being undesired as it can introduce some complexity and unforeseen complications.

P.S. thanks for all the work that's gone to Asahi. It's so well thought out and I appreciate how polished it is despite being in Alpha. I can't wait for the finished product.

EDIT:

I want to add that for users who want to convert their existing user's home directory to systemd-homed, there is a migration guide

However, there are some constraints on the partition that need to be met for systemd-homed to work with LUKS as the storage mechanism. I'm not sure if the way the partitions are setup in the installer would meet the requirements. I'm just adding this because I'm not sure if these constraints would invalidate the ability to use systemd-homed with Asahi's installer.

OS: Arch Linux ARM Minimal

Wifi Manager: iwctl

No error is outputted

Failed to run process: diskutil apfs resizeContainer disk0s2 289999421440
that issues appears every time i try to install
If you need to file a bug report, please attach the log file:
/private/tmp/asahi-install/installer.log
that is the log file that i get given at the end
please how do i fix it

Hi there.
I want to install asahilinux on my Mac m1 and all was good until...

Collecting firmware...
Installing OS...
  Copying from esp into disk0s4 partition...
\ 100.00% 
  Copying firmware into disk0s4 partition...
  Extracting root.img into disk0s7 partition...
| Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (1/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (2/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (3/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (4/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (5/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (6/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (7/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (8/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (9/10)
Error downloading data (<urlopen error [Errno 8] nodename nor servname provided, or not known>), retrying... (10/10)
Exceeded maximum retries downloading data.

After that installation exited. and I don't know how to resume the installation process and try again downloading data that is needed this time by VPN (because much of everything in my country is blocked :))) IRAN ).

The installer log file is attached.

This part of the docs might be saying no, but I don't know if PSCI is required for suspend to disk.

https://github.com/AsahiLinux/docs/wiki/Feature-Support#power

As per https://github.com/AsahiLinux/docs/wiki/Devices, j416sap (MacBook Pro (16-inch, M2 Pro, 2023)) should be supported, but when running curl https://alx.sh | sh the following message is printed:

Collecting system information...
  Product name: MacBook Pro (16-inch, 2023)
  SoC: Apple M2 Pro
  Device class: j416sap
  Product type: Mac14,10
  Board ID: 0x6
  Chip ID: 0x6020
  System firmware: iBoot-8419.80.7
  Boot UUID: E49A64EA-A378-4C50-B6A8-0C95C1780A38
  Boot VGID: E49A64EA-A378-4C50-B6A8-0C95C1780A38
  Default boot VGID: E49A64EA-A378-4C50-B6A8-0C95C1780A38
  Boot mode: macOS
  OS version: 13.2 (22D49)
  SFR version: 22.4.49.0.0,0
  System rOS version: 13.2 (22D49)
  No Fallback rOS
  Login user: redacted

This device is not supported yet!
Please check out the Asahi Linux Blog for updates on device support:

There is no mention of NVRAM in the Feature Support page.

Also, is there any technical reason why the nvram cannot be used as the efi variable store besides "read/writing from it is not supported yet"?

` % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1440 100 1440 0 0 793 0 0:00:01 0:00:01 --:--:-- 797

Bootstrapping installer:
Checking version...
Version: v0.4.1
Downloading...
Extracting...
Initializing...

The installer needs to run as root.
Please enter your sudo password if prompted.
/etc/sudoers:15:19: empty netgroup
Dafaults env_keep += "CHARSET LANG LANGUAGE LC_ALL LC_COLLATE LC_CTYPE"
^
Password:

Welcome to the Asahi Linux installer!

This installer is in an alpha state, and may not work for everyone.
It is intended for developers and early adopters who are comfortable
debugging issues or providing detailed bug reports.

Please make sure you are familiar with our documentation at:
https://alx.sh/w

Press enter to continue.

By default, this installer will hide certain advanced options that
are only useful for developers. You can enable expert mode to show them.
» Enable expert mode? (y/N): n

Collecting system information...
Product name: MacBook Air (M1, 2020)
SoC: Apple M1
Device class: j313ap
Product type: MacBookAir10,1
Board ID: 0x26
Chip ID: 0x8103
System firmware: iBoot-7459.141.1
Boot UUID: 4B1AA46A-D850-4983-9DA9-FADB8F471B5E
Boot VGID: 4B1AA46A-D850-4983-9DA9-FADB8F471B5E
Default boot VGID: 4B1AA46A-D850-4983-9DA9-FADB8F471B5E
Boot mode: macOS
OS version: 12.6 (21G115)
SFR version: 21.7.115.0.0,0
System rOS version: 12.6 (21G115)
No Fallback rOS
Login user: bearcampbell

Collecting partition information...
System disk: disk0

Collecting OS information...

Partitions in system disk (disk0):
1: APFS [Macintosh HD] (994.66 GB, 6 volumes)
OS: [B*] [Macintosh HD] macOS v12.6 [disk3s3, 4B1AA46A-D850-4983-9DA9-FADB8F471B5E]
2: APFS (System Recovery) (5.37 GB, 2 volumes)
OS: [ ] recoveryOS v12.6 [Primary recoveryOS]

[B ] = Booted OS, [R ] = Booted recovery, [? ] = Unknown
[ *] = Default boot volume

Using OS 'Macintosh HD' (disk3s3) for machine authentication.

Choose what to do:
r: Resize an existing partition to make space for a new OS
q: Quit without doing anything
» Action (r): r

We're going to resize this partition:
APFS [Macintosh HD] (994.66 GB, 6 volumes)
Total size: 994.66 GB
Free space: 832.28 GB
Minimum free space: 38.00 GB
Minimum total size: 200.38 GB (20.15%)

Enter the new size for your existing partition:
You can enter a size such as '1GB', a fraction such as '50%',
or the word 'min' for the smallest allowable size.

Examples:
30% - 30% to macOS, 70% to the new OS
80GB - 80GB to macOS, the rest to your new OS
min - Shrink macOS as much as (safely) possible

» New size (50%): 800GB

Resizing will free up 194.66 GB of space.

Note: your system may appear to freeze during the resize.
This is normal, just wait until the process completes.
» Continue? (y/N): y

Started APFS operation
Aligning shrink delta to 194,663,059,456 bytes and targeting a new physical store size of 799,999,524,864 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 166,698,418,176 bytes
Resizing APFS Container designated by APFS Container Reference disk3
The specific APFS Physical Store being resized is disk0s2
Verifying storage system
Using live mode
Performing fsck_apfs -n -x -l /dev/disk0s2
Checking the container superblock
Checking the space manager
Checking the space manager free queue trees
Checking the object map
Checking the encryption key structures
Checking volume /dev/rdisk3s1
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the document ID tree
Checking the fsroot tree
error: doc-id tree: record exists for doc-id 11889, file-id 105199 but no inode references this doc-id
error: doc-id tree: record exists for doc-id 11963, file-id 5122246 but no inode references this doc-id
Checking the extent ref tree
Checking the file key rolling tree
Verifying volume object map space
The volume /dev/rdisk3s1 was found to be corrupt and needs to be repaired
Checking volume /dev/rdisk3s2
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s2 appears to be OK
Checking volume /dev/rdisk3s3
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking snapshot 1 of 1 (com.apple.os.update-BF1DBCA6141B430194B034207E3FA291F4CA4BF9DB67777796325119C61D343F)
Checking the fsroot tree
Checking the file extent tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s3 appears to be OK
Checking volume /dev/rdisk3s4
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s4 appears to be OK
Checking volume /dev/rdisk3s5
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s5 appears to be OK
Checking volume /dev/rdisk3s6
Checking the APFS volume superblock
Checking the object map
Checking the snapshot metadata tree
Checking the snapshot metadata
Checking the fsroot tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s6 appears to be OK
Verifying allocated space
Performing deferred repairs
error: doc-id tree record exists for doc-id 11889, but no inode references this doc-id
Skipped 2/2 repairs of this type in total
Deferred repairs skipped
The container /dev/disk0s2 could not be verified completely
Storage system check exit code is 8
Error: -69716: Storage system verify or repair failed
Failed to run process: diskutil apfs resizeContainer disk0s2 799999524864
root : ERROR Process execution failed
Traceback (most recent call last):
File "/private/tmp/asahi-install/main.py", line 852, in
InstallerMain().main()
File "/private/tmp/asahi-install/main.py", line 704, in main
while self.main_loop():
File "/private/tmp/asahi-install/main.py", line 824, in main_loop
return self.action_resize(parts_resizable)
File "/private/tmp/asahi-install/main.py", line 635, in action_resize
self.dutil.resizeContainer(target.name, val)
File "/private/tmp/asahi-install/diskutil.py", line 208, in resizeContainer
self.action("apfs", "resizeContainer", name, size, verbose=2)
File "/private/tmp/asahi-install/diskutil.py", line 38, in action
subprocess.run(["diskutil"] + list(args), check=True)
File "/private/tmp/asahi-install/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['diskutil', 'apfs', 'resizeContainer', 'disk0s2', '799999524864']' returned non-zero exit status 1.
If you need to file a bug report, please attach the log file:
/private/tmp/asahi-install/installer.log`

Is it possible to use QEMU (in this case manager - https://virt-manager.org/)? I mean create virtual machines from the Host - which is Arch Linux on Apple M1.

Just wanted to share my notes / guide setting up GNOME from zero, in case anybody is searching for this info.
Note I'm opting for wayland options and some things could be done differently, just found this the most straightforward way.

• setup dance
  • login as root with password root
  • systemctl start iwd
  • iwctl
    • station wlan0 scan
    • station wlan0 connect *network name*
    • quit
  • ping archlinux.org
  • systemctl start dhcpcd
  • pacman -Syu
• reboot
• go through setup dance again
• pacman -S gnome followed with these non-defaults:
  • 1-60
  • pipewire-jack
  • wireplumber
• pacman -S networkmanager
• systemctl enable gdm
• shutdown
• login as alarm user, create new user through gnome settings & logout
• login as new user
• systemctl enable NetworkManager
• delete alarm user using gnome settings
• change root password
• lock the root user password with sudo passwd -l root
• disable root login with sudo usermod -s /usr/sbin/nologin root

I'm new to macOS and I want to run it on m1n1 hypervisor.
I follow the doc in SW:Hypervisor but the log looks like this:

My macOS version is Big Sur 11.5.2.

zec@zecdeMacBook-Pro KDK_11.5.2_20G95.kdk % kmutil create -z -n boot -a arm64e -B ~/dev.kc.macho -V development
-k System/Library/Kernels/kernel.development.t8101
-r /System/Library/Extensions
-r /System/Library/DriverExtensions
-x $(kmutil inspect -V release --no-header | grep -v "SEPHiber" | awk '{print " -b "$1; }')
Error Domain=KMErrorDomain Code=71 "Unable to resolve dependencies: 'com.apple.driver.AppleRTC' names a dependency on 'com.apple.iokit.IOACPIFamily', which was not found." UserInfo={NSLocalizedDescription=Unable to resolve dependencies: 'com.apple.driver.AppleRTC' names a dependency on 'com.apple.iokit.IOACPIFamily', which was not found.}

And I'm a little confused with "Switch into the KDK folder and run the following command:". The KDK folder here means the kernels directory?

Thanks~

Hello,

i successfully installed asahilinux minimal on 18,2 MacBook Pro.

But I need help switching the < key with the ` key so i have the pipe (~) sign (with shift of course) on the left side of 1 (i hope thats understandable). I havn't found anything in the docs. But feel free to prove me wrong ;)

Thank you in advance

Would it be possible to boot m1n1, or any other payload for that matter without altering whatever is currently on the internal ssd, including omitting the re-partitioning?
I am not yet very familiar with the limitations of kmutil and friends, but if they allowed for marking an image on an external volume as bootable, I don't see why not?

Obviously, once we jump to Linux, it's not a problem to run from an external storage medium, but I don't think there is any info about getting m1n1 on anything other than the internal drive on the wiki currently..

Hello !

I wanted to uninstall Asahi Linux (it's awesome, but I don't have enough space on my Mac right now so I will re-install it later) so I followed this

https://github.com/AsahiLinux/docs/wiki/Partitioning-cheatsheet

I ran the "stupidly dangerous script" and it didn't ask for a confirmation. It said "Press enter twice if you really want to continue." but ran anyway without me doing anything. I'm not sure that's the correct behavior.

It didn't break anything on my setup so everything's fine, but maybe this should get fixed ?

Thanks, and keep up the good work ! :)

https://github.com/AsahiLinux/docs/wiki/Tasks

Seems to be updated on may. Too old, I guess?

The page on Debian install tells to edit the file /etc/wpa/wpa_supplicant.conf. There is no such file.
Perhaps the author intends to talk about /etc/wpa_supplicant/wpa_supplicant.conf ?

On the feature support page, in the macbook air (2022) m2 column, in the touchbar row it says "asahi linux" but it should say "N/A"

Asahi Linux is interesting to many people, but most will not understand the technical details of the work needed to bring proper Linux support to the M1 Macs.

To attract more attention, support and sponsoring for the project from such parties, it would be useful to provide regular progress reports that are comprehensible to non-specialists. Take me as an example: I am a Asahi Linux sponsor because a I want proper Linux support on the M1 Macs. However, I don't really understand the process, and I am not sure I am sponsoring the right thing.

For example, weekly updates on the Asahi Linux website with a few lines highlighting the most relevant progress and how this is relevant in the big picture of getting proper Linux Support for M1 Macs would be great!

installer.log

Attempting to install Asahi to an external drive, as my Mac doesn't have a lot of storage. 500GB is all it has, and it's full. External thumb drive is 256gb with usb 3.0.

This is a question about current feature support.
I believe the 3.5 mm jack on the m1 macbook air supports TRRS,
namely audio in + out at the same time.
If this is the case, what is the status of mic support through this jack?
Thanks.

I can’t seem to install anything
sudo: app-get command not found
Pls help

Hi there,

Device: Macbook air M1, 16GB memory

I have a strange situation where if the wifi disconnects and is unable to reconnect (apparently) the plasmashell process will consume all the cores and heat up the laptop (and drain the battery).
Forcing the wifi to disconnect will restore normal CPU usage.

I cannot say if it's the fault of wifi driver or plasma (or else)

in journald i can see these messages:
Jul 11 13:04:55 zanfix-m1 plasmashell[694]: org.kde.plasma.nm.libs: Wireless scan on "wlan0" failed: "Scanning not allowed while unavailable"

Jul 11 13:05:03 zanfix-m1 plasmashell[694]: kf.quickcharts.deprecated: ValueHistorySource is deprecated (since 5.78): Use HistoryProxySource instead' Jul 11 13:05:03 zanfix-m1 plasmashell[694]: kf.quickcharts.deprecated: Note: Instantiated from "...plasma/plasmoids/org.kde.plasma.networkmanagement/contents/ui/TrafficMonitor.qml"

Did not see anything useful wil dmesg

^^Title. The vpn client doesn't install or run as an AppImage, probably due to lack of support of 16k pages.

Hello Friends,

I've added a bugreport on the vscode page due to a segmentation fault by launching the Visual Studio Code editor. Since it does rely on Electron its probably related to the lack of 16K page support that also affects Chromium in order to apply the same fix if possible.

The issue can be tracked at microsoft/vscode#153849

Is it theoretically possible to run Windows ARM with m1n1 + U-Boot on Apple Silicon?

If so, why hasn't anyone started doing this?

Hello. I am a fan of the Asahi project, and I can't help but marvel at how dedicated the team has been to get everything, even GPU drivers, reverse-engineered for the Linux kernel! However, I was wondering whether I could bootstrap Asahi to an external drive. This would really prove useful for advanced users who would like to use a live environment to do stuff like inspecting a broken installation. I know using u-boot can boot from USB. However, I still need to bootstrap a live environment to an external disk, preferably Arch Linux ARM. I have tried the Fedora USB Builder, but it kept failing.

Can we have a guide on how to bootstrap to an external disk?

What is the login ID and password for alert login?
I put admin ID and password but it was incorrect.

I tested Asahi Linux on my M1 Mini. Now I want to go back to macOS but that doesn't work. The Mac partition is 60GB in size (to small to instal macOS) and 940GB of empty space that I can no longer approach.

How can I format the disk in such a way so that I can install macOS again.

Anyone an idea how I can do that?

I've tried following the QuickStart instructions to the dot on a MacBook Pro with M1 Pro. The mac came with macOS monteray pre-installed.

However, I hit a snag when trying to use kmutil:

-bash-3.2# kmutil configure-boot -c m1n1.macho -C -v /Volumes/Linux
By setting a custom boot object, you will be putting your system into Permissive Security.

Are you sure you want to do this? (enter y or n) y
found valid Mach-O binary, deriving Mach-O boot properties...
Error Domain=KMErrorDomain Code=71 "Fileset Error: Invalid Mach-O boot properties" UserInfo={NSLocalizedDescription=Fileset Error: Invalid Mach-O boot properties}

Any ideas?

After installing Asahi minimal, switching to asahi-dev, and rebooting, the system cannot find the NVMe drive and refuses to boot. I am confused why we should switch to asahi-dev. I also asked marcan this on Reddit and he says that any guide which suggests to switch to asahi-dev is wrong.

Here's the output image:

• J274
• J293
• J313
• J314
• J316
• J456
• J457

unfortunately entry #44 is closed, but i still can't reach the 940GB no matter what I try with 'diskutil'. Can someone give me the correct instructions, so that I have access to the entire hard disk again? Due to a stupid mistake of my own, the mac mini has become unusable.

When I was installing Gentoo on an Apple Silicon thing, I decided to ignore the part that warned me not to alter the ESP. I know, it's stupid. But I kept all the EFI files intact with GNU tar's amazing capabilities. The update-m1n1 script ran functions.sh, which used the old PARTUUID at first, but I managed to change it in the script so that m1n1 would be updated properly. Everything went fine.

That is, until I rebooted.

I recognised the old PARTUUID in the u-boot screen, mocking me for being such a rebel. Now, I am here, begging for mercy. While I'm trying to stay sane at this, I still can't figure it out. I know how to boot into a Debian live environment, and I can chroot into my Gentoo installation from there. But right now, I'm frowning at this mess.

How do I fix the u-boot thingy using the old PARTUUID? I'd appreciate any help!

Resources

1. jannau/u-boot-1@53f0ad1

The "Zig" programming language does not have support for 16K page sizes; it defaults to 4K pages.

Tracking upstream at ziglang/zig#11308

Thanks to @gpanders for the report, I'll update the wiki.

https://github.com/AsahiLinux/docs/wiki/SW%3ALinux#linux-usb-keyboard
This part of doc seems out-of-date.

Sorry for trouble you，I met one unexpected problem.
I am using a mac mini with macOS13.2, in ITR's terminal
$ kmutil configure-boot -c m1n1.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v
Then i restarted the machine
The machine showed no payloads find， in proxy mode（which mode i want）
Now i use a USB-C to USB-A cable, with the C side on the m1n1 target. Host is an ubuntu22 on VMware Workstation on x86 windows 10.
But nothing happened, i coulden’t find /dev/ttyACM, and no devices change on windows10, too.
May i forget to do something? What should I do next?

I know this isn't an issue per se, but I didn't know where else to ask. macOS Ventura is coming out here soon, but I'm wary about installing it out of fear of breaking my Asahi install. Does anyone know the likelihood of such a thing happening?

This tool might provide some useful information regarding apples GPU hardware. @alyssarosenzweig

https://github.com/tellowkrinkle/mtl-gpu-asmcheck

Feel free to close this "issues", wether useful or not. ;)

The "tasks" wiki page hasn't been updated since May. A lot has happened since then and it'd be nice to be able to see what is still left.

Currently, there is no page for U-Boot feature support. It would be useful to have such a page in order to reduce confusion as there are some hardware useful in U-Boot like the SD card reader on the Macbook Pro 14-inch 2021 that does not work on U-Boot.

On macos ventura I constantly get:

» New size (min): 80%
Size is too small, please enter a value > 245.11 GB (100.00%)
» New size (min): 

I have had turned on tmbackups however after following the linked guide on how to delete tmbackups it still didn't work.
I even restarted the thing.

Have a look:

There's definitely free space here so it's either bad documented or an installer problem.

What can be done here?

Sincerely

I have just tried:

➜  ~ sudo diskutil apfs resizeContainer disk0s2 240GB
Started APFS operation
Aligning shrink delta to 5,107,195,904 bytes and targeting a new container size of 240,000,000,000 bytes
Determined the minimum size for the APFS Container to be 245,107,195,904 bytes
Error: -69521: Your APFS Container resize request is below the APFS-system-imposed minimal container size (perhaps caused by APFS Snapshot usage by Time Machine)
➜  ~ 

However, as I said already, deleting TM Backups didn't seem to work.

in this part, it says 1password is broken, but it's not.
by download this, I successfully installed the software and logged in, everything seems fully functioning.

Hello. I know that the speakers do not work. But headphones connected through the 3.5 mm jack should work, right? Well, mine is not working. I've tried following the other issue about this on the linux repository, but it did not work for me. What should I do?

suspect it came from wiping the whole ssd in recovery mode and creating a new partition and executing macos recovery to reinstall mac os on it affect the boot chain

Device: 2020 Macbook Pro M1, MacOS13, I've got the following errors:

Failed to load '/'
** Unable to read file ubootefi.var **
Failed to load EFI variables
BootOrder not defined
EF1 boot manager: Cannot load any image
Found EFI removable media binary EFI/boot/bootaa64.efi
192512 bytes read in 0 ms
Booting ref i\boot bootaa64.efi

Hello friends,

I don't know if this is the proper place to add it but it may help others and since theres no setup utility on the mac there's no visible way to change the functionality of the function keys, by default they will work as multimedia and screen control function and the F1-F12 keys are accessible via pressing fn.

I prefer the other way around making the F1-F12 by default and after some research and experiment I was able to identify that Asahi on the MacBook Air M1 uses the same hid_apple driver as the Intel MacBooks and to change that behaviour you need to change the fnmode option on that driver. That can be acomplished by editing /sys/module/hid_apple/parameters/fnmode for a temporary fix or adding options hid_apple fnmode=2 to a modprobe conf file for a permanent one.

The values available are:

• 0 -> Only the F1-F12 keys will work, the multimedia keys will be disabled and the fn key will do nothing
• 1 -> The default behaviour, the function keys will work as their multimedia parts and the F1-F12 will be acessible trought fn
• 2 -> The reverse behaviour (my desided option) the function keys will do their default F1-F12 and the multimedia keys will be acessible trought the fn key.

Reference

I don't think this is a bug, its a feature of the platform but it may help some people and maybe could be on some page on the wiki.

The wiki page at https://github.com/AsahiLinux/docs/wiki/SW%3ALinux recommends building the main branch of https://github.com/AsahiLinux/linux and using it with the initrd from Debian and config-marcan. However, there appears to be some incompatibility here, as attempting to boot this configuration will yield:

Failed to create socket: Function not implemented
Failed to initialize udev control socket
Failed to create manager: Invalid argument

It would be nice if the steps outlined in the wiki gave a bootable Linux system for people to play around with.