asahilinux / linux Goto Github PK

Im trying to install asahi on my 2020 Macbook air. It's not working as intended.

Your APFS Container resize request is below the APFS-system-imposed minimal container size

installer.log

This is a tracker bug for general GPU issues, like:

• Apps that crash after startup
• Rendering glitches
• GPU fault/timeout errors

When making a comment on this bug, please run the asahi-diagnose command and attach the file it saves to your comment. Please tell us what you were doing when the problem happened, what desktop environment and window system you use, and any other details about the issue.

The purpose of this bug is to collect reports of app issues in one place, so we have somewhere to look when figuring out what to work on. Since the driver is still a work-in-progress and lots of things are not expected to work, please don't expect a timely response to reports. We're working on it!

Before reporting something, please check that the issue has not been reported already. Duplicate reports just clutter up the bug and will be marked as duplicate. --marcan

• If you are having shader errors with Chromium/Electron-based apps after an update, delete your shader cache: rm -rf ~/.config/chromium/Default/GPUCache (or similar paths for other apps). Upstream bug. This is not a driver bug.

• If you run into a GPU lockup or crash (all GPU apps stop working, but you can still SSH into the machine), please open a new bug in this repo, tell us what you were doing when the GPU locked up, and attach the asahi-diagnose log.

• If you get GPU fault or GPU timeout messages in dmesg (probably together with rendering issues), but the GPU keeps working in general, this tracker bug is the right place to report that.

• If you have linux-asahi-edge issues unrelated to the GPU, please report them here. This includes display output/controller related issues, like screen resolution switching and backlight control, which are unrelated to the GPU driver.

• If you are seeing single-pixel-wide glitches, please set your screen scale to 100%, log out and back in, and try to reproduce it again. These kinds of glitches are likely to be compositor/desktop environment bugs related to fractional scaling, rather than driver issues.

If you see magenta

Magenta is the error color on Apple GPUs. It is what you get when you sample an uninitialized compressed texture. This often happens with driver bugs that break rendering, but there are also many apps that have bugs that transiently display uninitialized buffer contents. These will often show up as black or transparent on other GPUs or with software rendering, which stands out less but it indicates the same bug.

If you see magenta glitches, please try running the app with ASAHI_MESA_DEBUG=nocompress. If you see the same problems but they are now black, try LIBGL_ALWAYS_SOFTWARE=true to force software rendering. If you get the same results (still black regions where previously there was magenta), then it is likely an app bug or an upstream Mesa bug, not a driver issue.

Another common issue is apps that have rendering feedback loops, which are undefined behavior in OpenGL. These often result in 4x2 pixel shaped corruption regions. You can work around this with ASAHI_MESA_DEBUG=nocompress, which should fix the issue (at least if it wouldn't normally break on all GPUs). This could also be caused by a driver bug, though, so please do report anything that is fixed with nocompress so we can take a look and determine whether it's an app bug or a driver bug!

Known issues

• When GPU timeouts/faults occur, rarely the firmware can lock up (see #79)
• Google Maps on Firefox is slow/jerky

Resolved issues

• System Monitor glitches in the History tab
• Plasmashell sometimes shows magenta areas or missing rendering
• Portraits render incorrectly or cause faults in Darwinia
• Geometry edges render poorly/jagged in Darwinia
• WebGL Aquarium faults above 10000 fish
• Xorg sometimes flashes black while switching windows in KWin
• gl_FragDepth is not implemented
• three.js scenes (and other complex renders) with MSAA glitch on Pro/Max/Ultra machines
• Discard regressed with the OpenGL 3.1 update (breaking Darwinia)
• MSRTT wrongly advertised when not properly supported (making Darwinia MSAA not work)
• Texture barriers wrongly advertised when not properly supported (X11/Emacs glitching)
• Water glitches near screen edges in Darwinia if you get up really close.
• (6.2/explicit sync regression) KWin flashes magenta rectangles when starting up, or right before going to sleep.
• Nautilus is pink with Adwaita
• Google Maps & PDF viewer on Firefox use too much memory
• Corrupted X11 apps on GNOME/XWayland
• Rendering with some render targets disabled regressed (Inochi2D, KiCad 3D glitching)
• Figma rendering is glitchy
• CSS transforms in Firefox render incorrectly
• Complex GTK apps (GIMP, etc.) under XWayland sometimes glitch magenta
• Register spilling is excessively slow (example)

Issues that aren't driver bugs

• gnome-terminal has a glitchy background (upstream bug from 2 years ago, they don't seem interested in fixing it...)
• Moving the mouse above blurred backgrounds in KWin/Wayland causes artifacts (upstream bug)
• KWin has single-pixel glitches when fractional scaling is enabled (Fixed in plasma 5.27.7)
• OBS screen sharing does not work (PipeWire regression, fixed in 0.3.62, plus KWin bug (merged for 5.26.5, ETA Jan 3), plus core Mesa bug)
• Some WebGL apps on Firefox (like Plex and QuakeJS) can hang/fail to render (upstream bug, fixed for Firefox 110)
• Firefox sometimes flashes magenta on startup (upstream bug)
• SuperTuxKart sometimes has rectangular black glitches (upstream bug) (worked around in driver for now)
• QuakeJS has jittery geometry (emscripten bug, fixed years ago but they need to update). Probably applies to any WebGL apps with similar issues too.
• Window corruption / magenta regions with Java OpenGL rendering enabled (Java does not double buffer its OpenGL visual so it will always tear/break on any modern system from this decade, just worse on Apple with compression.)
• Google Sheets gets blurry on scroll (Google Sheets bug Firefox bug) (workaround: ASAHI_MESA_DEBUG=no16)
• blender's gl version check is sketchy https://bugzilla.redhat.com/show_bug.cgi?id=2237821

This tracker issue is for reporting apps that fail to start with the GPU driver, likely because they require OpenGL features that are not supported yet.

• Please only report apps that are present in the Arch Linux ARM repository (installable via pacman on Asahi Linux).
• Try starting the app with the LIBGL_ALWAYS_SOFTWARE=1 environment variable, and make sure it works.
• Try starting the app from a terminal, and report any OpenGL-related messages you see.

If the app crashes or segfaults on startup, the problem could be related to OpenGL support, or an actual driver bug. If unsure, please report it here, and mention the segfault. We'll triage it later if it's actually a driver bug. If you know how to get backtraces with gdb, please try running the app under it and see whether the crash happens within the app's code or within Mesa. If it's within Mesa, please report it on issue #72 instead.

Hello, I have just installed Asahi Linux on my iMac (24-inch, 2021).

Chip: Apple M1
Memory: 8 GB

The installation went all fine and when I loaded the OS, it displayed the setup screen as expected. However, my Apple bluetooth mouse and keyboard that came with my iMac seem to be unresponsive. I can't move the cursor on the screen or anything like that? Is it a feature that isn't supported yet or was there a possible issue during installation I didn't know about? Any help appreciated.

there is any estimate for eGPU thunderbolt compatibility on m1 air?

Is there an estimated time for when speaker and mic are going to be supported? It's the only thing stopping me from switching to Asahi. Thanks

Wifi (wpa2 enterprise) always asks me to set up the config every time and then won't connect. it just won't connect.

Hello !

I am running Asahi Linux on my M2 Macbook Air, with an AZERTY keyboard.

Out of the box, the '@' key is swapped with the '<'. I had to enable "iso_layout=1" on apple_hid.

And now, I can't find a way to make a pipe. On MacOS it's shift + alt + L, but on Asahi it doesn't work :(

Any way to fix this ? I can provide you more infos if needed.

Thanks a lot !

tag:
mac m1 docker run AsahiLinux

Missed clicked. I didn't want to open the issue

[...]
[    0.000646] rcu: Hierarchical SRCU implementation.
[    0.000827] Remapping and enabling EFI services.
[    0.000839] ------------[ cut here ]------------
[    0.000840] UEFI Runtime regions are not aligned to 64 KB -- buggy firmware?
[    0.000843] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/efi.c:28 efi_create_mapping+0x7c/0x16c
[    0.000850] Modules linked in:
[    0.000852] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.0-rc6-asahi-next-20220301-4-asahi-ARCH #4
[    0.000854] Hardware name: Apple MacBook Air (M1, 2020) (DT)
[    0.000856] pstate: 60000009 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    0.000859] pc : efi_create_mapping+0x7c/0x16c
[    0.000861] lr : efi_create_mapping+0x7c/0x16c
[    0.000864] sp : ffff8000093bbd40
[    0.000864] x29: ffff8000093bbd40 x28: 0000000000000000 x27: 0000000000000000
[    0.000868] x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000
[    0.000870] x23: 0000000000000000 x22: 0000000000000000 x21: ffff8000092cc000
[    0.000873] x20: ffff800009270a20 x19: ffff0003731bd388 x18: 0000000000000050
[    0.000875] x17: 00000000aa9d7b42 x16: 000000003fc4a5b8 x15: fffffffffffc1488
[    0.000878] x14: 000000009f4d7c9d x13: ffff80000914e240 x12: 00000000000000de
[    0.000880] x11: 000000000000004a x10: ffff8000091fe930 x9 : ffff80000914e240
[    0.000883] x8 : 00000000ffffdfff x7 : ffff8000091fe240 x6 : 00000000000006f0
[    0.000886] x5 : 0000000000017ff4 x4 : 00000000ffffe04a x3 : 0000000000000000
[    0.000888] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000001e34040
[    0.000891] Call trace:
[    0.000891]  efi_create_mapping+0x7c/0x16c
[    0.000894]  arm_enable_runtime_services+0x12c/0x1e0
[    0.000897]  do_one_initcall+0x50/0x1c0
[    0.000899]  kernel_init_freeable+0x118/0x28c
[    0.000901]  kernel_init+0x28/0x140
[    0.000905]  ret_from_fork+0x10/0x20
[    0.000907] ---[ end trace 0000000000000000 ]---
[    0.001013] smp: Bringing up secondary CPUs ...
[    0.001091] Detected VIPT I-cache on CPU1
[... continues as normal]

This seems to happen everytime I boot the machine (t8103).
It’s not critical and works well otherwise but just in case it’s something to track I’m creating this issue here.

Feel free to close it if it’s not the right place for this. I can also link the entire dmesg output if needed.

Opening this to track the ongoing research into the safety envelope of the speakers (focusing mostly on testing; we can open other threads to discuss potential solutions once we have more data on what's needed).

The first target is an M2 MacBook Air, which is interesting because:

• macOS uses speaker protection (VI sense)
• It has 4 speakers
• It has funny grille-less speakers, which might need more EQ than usual to make sound good
• I have AppleCare on it

Initial testing done with povik's latest audio branch, including volume caps and tweeter HPF. Configured as follows:

• Tweeter HPF: 800 Hz
• Woofer HPF: 2 Hz
• Amp gain: 9 (15.5 dBV) (macOS: 15 / 18.5 dBV) for all speakers

No VISENSE support yet, that's in the works.

Testing using a sine sweep, 10-20kHz, 40 seconds, volume 0.8 (~-2dB). Initial testing was ad-hoc since I was not expecting damage this quickly, but a couple sweeps from Linux were enough to destroy the left tweeter and possibly damage the right one.

The failure mode for the tweeters seems to be a severe drop in volume, except for a small band of improved reproduction (that varies). My theory is that this is thermal damage, i.e. the tweeter melted itself and seized up. Left: dead tweeter; right: possibly-damaged but still functional tweeter.

In addition, there is rattling, which can be identified by the presence of sub harmonics. See the band in the middle of this sweep of the right tweeter:

It's not clear whether I actually damaged the woofers during this test. More controlled testing will follow. For now, my conclusion is that the tweeters are the major damage risk, and that damage occurs fairly quickly, even with just 40-second sweeps. If this is thermal, that suggests even short-term power excursions are dangerous.

After the initial testing, a follow-up with I Won The Loudness War successfully killed the right tweeter in the same way as the left one. I am sending the machine in for repairs.

Next steps:

• Add in/out capture to hypervisor tracer so we can see both what macOS sends to the speakers and what it gets back from VISENSE
• Capture impulse response of macOS EQ/DSP
• Find out whether macOS seems to do any kind of explicit power capping using VISENSE (e.g. by trying sine sweeps at varying volumes)
• Figure out maximum amplitude/power curves for macOS

For Linux testing:

• Get VISENSE working
• Switch to 5-second or shorter sweeps to reduce damage risk
• Do multiple sweeps at increasing power levels and note any appearance of damage
• Generate more controlled test files (e.g. 4ch sweeps) so we can more easily correlate things

A priori, it would seem that we have to set the tweeter amp gain much lower than we do now.

Bonus points once most of the work is done:

• Try to destroy the speakers from macOS, so we can point at that when people inevitably complain that our volume caps are lower than macOS' (I strongly suspect I Won The Loudness War on loop in macOS will cause damage with Apple's DSP).

This is a global tracker bug to group reports related to linux-asahi-edge. Since this is a bleeding-edge kernel, we know some things are broken and we make no promises that we'll get to reports in any amount of time. Please post any issues as comments on this bug, and we'll handle them or break them out into their own bugs as we deem appropriate. Please do not open new bugs for linux-asahi-edge issues that are not reproducible with the default linux-asahi kernel.

Only report issues here if they happen with linux-asahi-edge and NOT with linux-asahi. If you find a problem unrelated to the new features of linux-asahi-edge, you must test across at least 5 reboots on linux-asahi to make sure it never happens there and is truly a regression related to linux-asahi-edge.

Please make sure you have updated all your packages and have asahi-meta installed before reporting anything. Setups without asahi-meta installed are not supported and are expected to randomly break as we make changes to our packages. All Asahi installs since the first official alpha release come with asahi-meta preinstalled (and also asahi-desktop-meta for the desktop builds). If you choose to uninstall our infrastructure packages, you are on your own and we cannot provide support.

Known issues:

• USB: USB2/3 breaks after suspend/resume
• DCP: brightness is sometimes reported as 0 on boot, instead of the actual boot-time brightness
• DCP: brightness drops to min when the screen turns on (fixed by touching brightness keys)
• SPI+MTP: Keyboard/trackpad is not suspended properly (affects SPI/M1 and MTP/M2 differently)
• No backlight shutdown / screen-off on M2 (pending DCP support)
• General sleep excessive power consumption issues (this needs further debug)
• Xorg display scaling issues when changing display drivers. This is expected as Xorg is hopelessly broken when it comes to display scaling; we preconfigure new installs to work, but changes can and will break things. You should be able to get it fixed by manually changing the scale/DPI settings, but please don't report this, we can't do anything about it and upstream no longer supports Xorg.

When writing a comment, please run asahi-diagnose and attach the resulting logfile.

While working on this issue, @mixi found out that the switched °^ and <> could be because of the driver not setting it right.

This commit was the last update I found on this issue. But there doesn't seem to be a rule for the new Macbooks. The commit for the new device id's was created just 12 days ago, so it's probably not added yet.

That would mean that these macs would have this bug:

• APPLE_MACBOOK_AIR_2020
• APPLE_MACBOOK_PRO13_2020
• APPLE_MACBOOK_PRO14_2021
• APPLE_MACBOOK_PRO16_2021

Using kernel 5.18.0-asahi-00002-gec4e7c6fb519 all is well, however building the kernel from source 72eed51 (with the same config) there is no activity on the network device.

Is that the same for others who tried building with the latest revision?
my build is 5.18.0-asahi-00182-g72eed5179ad5.

Strangely I cannot find the commit that is referred to by ec4e7c6fb519.
I have installed the Debian version from https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/

Any thoughts on how to enable the AMX co-processor?

There are some references to handling the context switch here:
https://github.com/apple/darwin-xnu/blob/main/osfmk/arm/arm_init.c#L506

I'm getting this message every couple of seconds in dmesg:

[...]
[26220.193947] spi-hid-apple-of spi0.0: Read package crc mismatch
[26220.290068] spi-hid-apple-of spi0.0: Read package crc mismatch
[26224.392359] spi-hid-apple-of spi0.0: Read package crc mismatch
[26230.076770] spi-hid-apple-of spi0.0: Read package crc mismatch
[...]

Just wondering if it's a known issue or not.

Device: J316sAP
Distribution: Asahi Linux
Kernel version: 5.19.0-asahi-5-1-ARCH

I realize that a lot of apps/extensions won't work anymore, but thought a post would help with debugging.
The old extension is reported as not working on the new gnome shell.

I tried to install the git version by typing: yay -S gnome-shell-extension-pop-shell-git

Error in build is:

error: failed to run custom build command for glib-sys v0.14.0

Caused by:
  process didn't exit successfully: /home/bmentink/.cache/yay/pop-shell-shortcuts-git/src/shell-shortcuts/target/release/build/glib-sys-9a893ab86fa63848/build-script-build (exit status: 1)
  --- stdout
  cargo:rerun-if-env-changed=GLIB_2.0_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR
  cargo:warning=Failed to run `"pkg-config" "--libs" "--cflags" "glib-2.0" "glib-2.0 >= 2.48"`: No such file or directory (os error 2)
warning: build failed, waiting for other jobs to finish...
make: *** [Makefile:57: target/release/pop-shell-shortcuts] Error 101
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: pop-shell-shortcuts-git

I can post the full build logr if required ..
Cheers

If I use perf stat the cycles and instruction events show <not counted> about 99% of the time. Has anyone else had any luck with perf? Could something perhaps be wrong with the driver? I am on an M1 Mac Mini.

perf stat -e cycles,instructions ls

     <not counted>      cycles:u                                                      (0.00%)
     <not counted>      instructions:u                                                (0.00%)

       0.000535494 seconds time elapsed

       0.000555000 seconds user
       0.000000000 seconds sys

Hi,
I updated Asahi to the latest version, but now the device goes into bootloop if I have a usb-c hub connected

I get this error when booting

if I boot without connecting the hub then the device boots fine, then if I connect the USB hub after it was fully booted then the USB hub works fine.

Logs after connecting the USB hub:

[   38.407824] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[   38.407838] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[   38.407974] xhci-hcd xhci-hcd.1.auto: hcc params 0x0238ffcd hci version 0x110 quirks 0x0000000000010010
[   38.407988] xhci-hcd xhci-hcd.1.auto: irq 87, io mem 0x502280000
[   38.408054] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[   38.408057] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[   38.408060] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.1 Enhanced SuperSpeed
[   38.408122] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.19
[   38.408126] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   38.408129] usb usb3: Product: xHCI Host Controller
[   38.408131] usb usb3: Manufacturer: Linux 5.19.0-rc5-asahi-7-1-ARCH xhci-hcd
[   38.408133] usb usb3: SerialNumber: xhci-hcd.1.auto
[   38.408304] hub 3-0:1.0: USB hub found
[   38.408315] hub 3-0:1.0: 1 port detected
[   38.408432] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[   38.408468] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.19
[   38.408471] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   38.408474] usb usb4: Product: xHCI Host Controller
[   38.408475] usb usb4: Manufacturer: Linux 5.19.0-rc5-asahi-7-1-ARCH xhci-hcd
[   38.408477] usb usb4: SerialNumber: xhci-hcd.1.auto
[   38.408607] hub 4-0:1.0: USB hub found
[   38.408617] hub 4-0:1.0: 1 port detected
[   38.929711] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[   39.057594] usb 3-1: New USB device found, idVendor=2109, idProduct=2817, bcdDevice= 3.d3
[   39.057611] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   39.057617] usb 3-1: Product: USB2.0 Hub
[   39.057622] usb 3-1: Manufacturer: VIA Labs, Inc.
[   39.064313] hub 3-1:1.0: USB hub found
[   39.064444] hub 3-1:1.0: 5 ports detected
[   39.781710] usb 3-1.1: new high-speed USB device number 3 using xhci-hcd
[   39.931874] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=0306, bcdDevice= 7.00
[   39.931888] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   39.931894] usb 3-1.1: Product: USB3.0-CRW
[   39.931899] usb 3-1.1: Manufacturer: Generic
[   39.931903] usb 3-1.1: SerialNumber: 60000719201300000
[   39.935747] usb-storage 3-1.1:1.0: USB Mass Storage device detected
[   39.935956] scsi host0: usb-storage 3-1.1:1.0
[   40.993735] scsi 0:0:0:0: Direct-Access     Generic- SD/MMC           1.00 PQ: 0 ANSI: 4
[   40.995396] scsi 0:0:0:1: Direct-Access     Generic- SD/MMC/MS/MSPRO  1.00 PQ: 0 ANSI: 4
[   40.995674] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   40.995906] sd 0:0:0:1: Attached scsi generic sg1 type 0
[   40.997249] sd 0:0:0:0: [sda] Media removed, stopped polling
[   40.998050] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   40.998667] sd 0:0:0:1: [sdb] Media removed, stopped polling
[   40.998807] sd 0:0:0:1: [sdb] Attached SCSI removable disk
[   43.956705] usb 3-1.5: new high-speed USB device number 4 using xhci-hcd
[   44.034980] usb 3-1.5: New USB device found, idVendor=2109, idProduct=8888, bcdDevice= 0.01
[   44.034996] usb 3-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   44.035002] usb 3-1.5: Product: USB Billboard Device
[   44.035007] usb 3-1.5: Manufacturer: VIA Labs, Inc.
[   44.035011] usb 3-1.5: SerialNumber: 0000000000000001

I am brand new to Linux, and just installed Asahi Linux (which is based on Arch) on my M1 Mac Mini. My screen (an LG 49WL95C-WE) is an ultra-wide 5120x1440 (aspect ratio 32:9). I've run pacman -Syu to ensure everything is up to date.

My problem is that the system is treating my screen like a 1920x1080 display. When I go into Display Configuration under System Settings it indicates that this "is the only resolution supported by this display."

After some research, I tried setting a custom resolution:

$ cvt 5120 1440 60
# 5120x1440 59.96 Hz (CVT) hsync: 89.52 kHz; pclk: 624.50 MHz
Modeline "5120x1440_60.00"  624.50  5120 5496 6048 6976  1440 1443 1453 1493 -hsync +vsync

$ sudo xrandr --newmode "5120x1440_60.00"  624.50  5120 5496 6048 6976  1440 1443 1453 1493 -hsync +vsync

$ xrandr | grep -e " connected [^(]" | sed -e "s/\([A-Z0-9]\+\) connected.*/\1/"
None-1

$ sudo xrandr --addmode None-1 5120x1440_60.00

When I do this, the resolution now shows up as an option in Display Configuration. However, when I select it, the following vague error message appears: "Outputs could not be saved due to error."

I also tried the above steps with a 3840x1080 resolution. With this setting there is no error message. The screen flashes once, but there is no change in the aspect ratio.

Any help would be much appreciated as my system is unusable at the the current resolution.

Hey, I've tried writing a very basic kernel module for asahi that exposes EL1 system registers to userspace, but it always fails with reading the system registers as 0. I then found out that even EL0 registers such as CNTPCT_EL0 aren't accessible from EL0, while on the other hand, the preinstalled bare metal macOS on my mac does expose those system registers. Is there some kind of barrier between asahi and the hardware?

Thanks in advance for any type of help/guidance,
Adam.

Hi,
Trying to make the wifi chip to work in ap fails and the driver/firmware seems to fail at setting the beacon settings

running hostapd gives this error:

wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE 
Failed to set beacon parameters 
wlan0: Could not connect to kernel driver

and the driver threw this in the kernel log

ieee80211 phy0: brcmf_cfg80211_start_ap: Beacon Interval Set Error, -52

Is this issue specific to the wifi chips on the MacBook air (driver/firmware issue) or is this a general issue in the brcmfmac and should be reported to the brcmfmac maintainers?

Regards

Hello,
M1 devices use brcmfmac driver for wifi and AFAIK that driver had monitor mode support for quite some time now but it depends on the chip firmware, so my question is do the chips on these devices support monitor mode? and if so do we need to do anything to enable it in the kernel?

Regards

Thanks for the great works!
The 4K resolution and accelerated Gnome are awesome!🎉

And I'm wondering if we can do following for the Internal Display of MBP:

1. P3-1600nits Color profile
2. Linear adjustment for back light control (and I found the current display back light seems not as 'bright' as it in MacOS(up to 500nits in normal display mode))
3. 120hz support
4. Pro-display (1~120hz dynamic adjustment)
5. Full HDR support

4k page brcmfmac brcmf_pcie_init_dmabuffer_for_device dma_alloc_coherent fails

Device model

MacBook Pro 14-inch, 2021, M1 Pro, 10 core CPU, 16 GiB memory

macOS version

12.3.1

Kernel log

4k:

$ sudo dmesg | grep -E 'brcmfmac|jrydclleyafhlwt'
[    1.189418] usbcore: registered new interface driver brcmfmac
[    1.189690] brcmfmac 0000:01:00.0: Adding to iommu group 3
[    1.189695] brcmfmac 0000:01:00.0: Removing from iommu group 3
[    1.189713] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
[    1.298215] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4387c2-pcie for chip BCM4387/7
[    1.298966] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN-u-4.7-X2.bin failed with error -2
[    1.299976] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN-u-4.7.bin failed with error -2
[    1.299999] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN-u.bin failed with error -2
[    1.300014] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN.bin failed with error -2
[    1.300058] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-X2.bin failed with error -2
[    2.138005] jrydclleyafhlwt   CCCCCCCCCCCCCC 2560 0
[    2.138045] jrydclleyafhlwt   AAAAAAAAAAAAAA 2560
[    2.138074] brcmfmac 0000:01:00.0: brcmf_pcie_init_ringbuffers: Allocating ring buffers failed
$ sudo iwctl station list
                            Devices in Station Mode                            
--------------------------------------------------------------------------------
  Name                  State            Scanning
--------------------------------------------------------------------------------
No devices in Station mode available.

16k:

$ sudo dmesg | grep -E 'brcmfmac|jrydclleyafhlwt'
[    1.142057] usbcore: registered new interface driver brcmfmac
[    1.142515] brcmfmac 0000:01:00.0: Adding to iommu group 4
[    1.142558] brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
[    1.257236] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4387c2-pcie for chip BCM4387/7
[    1.257974] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN-u-4.7-X2.bin failed with error -2
[    1.257994] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN-u-4.7.bin failed with error -2
[    1.258008] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN-u.bin failed with error -2
[    1.258023] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-TPHN.bin failed with error -2
[    1.258058] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4387c2-pcie.apple,maldives-X2.bin failed with error -2
[    2.022143] jrydclleyafhlwt   CCCCCCCCCCCCCC 2560 ffff800009fb4000
[    2.022182] jrydclleyafhlwt   BBBBBBBBBBBBBB 2560
[    2.022214] jrydclleyafhlwt   CCCCCCCCCCCCCC 32768 ffff80000ab90000
[    2.022247] jrydclleyafhlwt   BBBBBBBBBBBBBB 32768
[    2.022279] jrydclleyafhlwt   CCCCCCCCCCCCCC 1536 ffff80000a478000
[    2.022313] jrydclleyafhlwt   BBBBBBBBBBBBBB 1536
[    2.022344] jrydclleyafhlwt   CCCCCCCCCCCCCC 24576 ffff80000abb8000
[    2.022377] jrydclleyafhlwt   BBBBBBBBBBBBBB 24576
[    2.022410] jrydclleyafhlwt   CCCCCCCCCCCCCC 40960 ffff80000abc4000
[    2.022443] jrydclleyafhlwt   BBBBBBBBBBBBBB 40960
[    2.083446] brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
[    2.084333] brcmfmac: brcmf_c_process_cal_blob: Calibration blob provided by platform, loading
[    2.094411] brcmfmac: brcmf_c_preinit_dcmds: Fi

$ uname -a
Linux localhost 5.19.0-asahi-5-2-4kpage-ARCH #2 SMP PREEMPT_DYNAMIC Mon, 22 Aug 2022 00:00:00 +0000 aarch64 GNU/Linux


--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
+++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c
@@ -1099,6 +1099,8 @@ brcmf_pcie_init_dmabuffer_for_device(struct brcmf_pciedev_info *devinfo,
 
        ring = dma_alloc_coherent(&devinfo->pdev->dev, size, dma_handle,
                                  GFP_KERNEL);
+
+       printk(KERN_EMERG "jrydclleyafhlwt   CCCCCCCCCCCCCC %d %lx\n", size, ring);
        if (!ring)
                return NULL;
 
@@ -1131,8 +1133,11 @@ brcmf_pcie_alloc_dma_and_ring(struct brcmf_pciedev_info *devinfo, u32 ring_id,
        dma_buf = brcmf_pcie_init_dmabuffer_for_device(devinfo, size,
                        tcm_ring_phys_addr + BRCMF_RING_MEM_BASE_ADDR_OFFSET,
                        &dma_handle);
-       if (!dma_buf)
+       if (!dma_buf) {
+               printk(KERN_EMERG "jrydclleyafhlwt   AAAAAAAAAAAAAA %d\n", size);
                return NULL;
+       }
+       printk(KERN_EMERG "jrydclleyafhlwt   BBBBBBBBBBBBBB %d\n", size);
 
        addr = tcm_ring_phys_addr + BRCMF_RING_MAX_ITEM_OFFSET;
        brcmf_pcie_write_tcm16(devinfo, addr, brcmf_ring_max_item[ring_id]);
`

I installed Asahi Linux on an Apple M1 Pro laptop and it worked like a charm.
I installed the latest branch of RonDB. This branch is 22.05.
I managed to compile after installing a few extra packages.
I executed a number of test cases using MTR (MysqlTestRun).
Most test cases failed in a method called set_direct_io which sets up the file to
use O_DIRECT using fcntl calls. These calls fail. So I presume that O_DIRECT is
not yet supported by the NVMe driver.

When I try to compile the package with our tools in a clean chrootbuild environment on Manjaro-ARM I get the following Rust errors for 6.1-rc8-asahi3-1 kernel:

  OBJCOPY arch/arm64/kernel/vdso/vdso.so
***
*** Rust compiler 'rustc' is too new. This may or may not work.
***   Your version:     1.65.0
1.65.0
***   Expected version: 1.62.0
***
***
*** Rust bindings generator 'bindgen' is too new. This may or may not work.
***   Your version:     0.63.0
***   Expected version: 0.56.0
***
  UPD     rust/target.json
  RUSTC L rust/core.o
warning: unused import: `crate::error::Error`
 --> /usr/lib/rustlib/src/rust/library/core/src/num/mod.rs:7:5
  |
7 | use crate::error::Error;
  |     ^^^^^^^^^^^^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default
warning: 1 warning emitted
  EXPORTS rust/exports_core_generated.h
  RUSTC P rust/libmacros.so
grep: warning: stray \ before #
grep: warning: stray \ before #
grep: warning: stray \ before #
  BINDGEN rust/bindings/bindings_generated.rs
  BINDGEN rust/bindings/bindings_helpers_generated.rs
error: Found argument '--blacklist-type' which wasn't expected, or isn't valid in this context
	Did you mean '--blocklist-type'?
	If you tried to supply `--blacklist-type` as a value rather than a flag, use `-- --blacklist-type`
USAGE:
    bindgen [FLAGS] [OPTIONS] <header> -- <clang-args>...
For more information try --help
make[3]: *** [/build/linux-apple-silicon/src/linux-asahi-6.1-rc8-3/rust/Makefile:343: rust/bindings/bindings_helpers_generated.rs] Error 2
make[2]: *** [/build/linux-apple-silicon/src/linux-asahi-6.1-rc8-3/Makefile:1276: prepare] Error 2
make[1]: *** [/build/linux-apple-silicon/src/linux-asahi-6.1-rc8-3/Makefile:362: __build_one_by_one] Error 2
make[1]: Leaving directory '/build/linux-apple-silicon/src/linux-asahi-6.1-rc8-3/build/base'
make: *** [Makefile:231: __sub-make] Error 2
==> ERROR: A failure occurred in prepare().
    Aborting...

The full build log can be found at our gitlab

I encountered this bug after downloading and trying to run telegram; the same outcome occurred by using both snap and pacman. I tried to run the executable from the terminal, and I got the following message:

<jemalloc>: Unsupported system page size
GLib (gthread-posix.c): Unexpected error from C library during 'malloc': Cannot allocate memory.  Aborting.
[1]    2988 IOT instruction (core dumped)  ./telegram-desktop

Do I see it correctly that KVM is enabled?

https://github.com/AsahiLinux/linux/blob/asahi/arch/arm64/configs/defconfig#L110

Or is this configuration overwritten somewhere?

Sry, I'm a bit out of kernel stuff since a few years. Need some time to get back to this business

Because if that works and qemu compiles and runs well (yeah, yeah, the 16k page size fun), we'd be able to run KVM acceleration enabled qemu on an M1?

https://community.arm.com/oss-platforms/w/docs/510/spawn-a-linux-virtual-machine-on-arm-using-qemu-kvm

this is crossposted from tonistiigi/binfmt, see there for details/reproducible example.
(Not repeating that here, because ... DRY).

It seems that asahi may be relevant, b/c @tonistiigi could not reproduce the issue on Apple M1 (under macOS).

Punting proper PM here to later.

It is possible to set the wifi card to monitor mode on the same device running macos. However, can not set to monitor mode in asahi.

Last login: Wed Apr 27 17:36:44 on ttys000
caiyanzhe@caiyanzhedeMacBook-Air ~ % cn.akinator.com
zsh: command not found: cn.akinator.com
caiyanzhe@caiyanzhedeMacBook-Air ~ % curl https://alx.sh | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1440 100 1440 0 0 794 0 0:00:01 0:00:01 --:--:-- 798

Bootstrapping installer:
Checking version...
Version: v0.3.28
Downloading...
curl: (7) Failed to connect to raw.githubusercontent.com port 443 after 13 ms: Connection refused
Error downloading installer_data.json. GitHub might be blocked in your network.
Please consider using a VPN if you experience issues.
Trying workaround...
Extracting...
Initializing...

The installer needs to run as root.
Please enter your sudo password if prompted.
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.101.2
Boot UUID: 1304A755-C43A-439A-A613-8167134907AE
Boot VGID: 1304A755-C43A-439A-A613-8167134907AE
Default boot VGID: 1304A755-C43A-439A-A613-8167134907AE
Boot mode: macOS
OS version: 12.3 (21E230)
System rOS version: 12.3 (21E230)
No Fallback rOS
Login user: caiyanzhe

Collecting partition information...
System disk: disk0

Collecting OS information...

Partitions in system disk (disk0):
1: APFS [Macintosh HD] (245.11 GB, 6 volumes)
OS: [B*] [Macintosh HD] macOS v12.4 [disk3s1, 1304A755-C43A-439A-A613-8167134907AE]
2: APFS (System Recovery) (5.37 GB, 2 volumes)
OS: [ ] recoveryOS v12.3 [Primary recoveryOS]

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

Using OS 'Macintosh HD' (disk3s1) 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] (245.11 GB, 6 volumes)
Total size: 245.11 GB
Free space: 154.88 GB
Minimum free space: 38.00 GB
Minimum total size: 128.23 GB (52.32%)

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 (min): 180GB

Resizing will free up 65.11 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 65,107,591,168 bytes and targeting a new physical store size of 179,999,604,736 bytes
Determined the minimum size for the targeted physical store of this APFS Container to be 93,281,320,960 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 snapshot 1 of 2 (com.apple.os.update-2289385E1A6FCCF05D444673FB1FEB06DDCF82A4C723EAD53AF1F3E08872CE0F)
Checking snapshot 2 of 2 (com.apple.os.update-MSUPrepareUpdate)
Checking the fsroot tree
Checking the file extent tree
Checking the extent ref tree
Verifying volume object map space
The volume /dev/rdisk3s1 appears to be OK
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 the fsroot 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 document ID tree
Checking the fsroot tree
error: doc-id tree: record exists for doc-id 39748, file-id 27209630 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/rdisk3s5 was found to be corrupt and needs to be repaired
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 39748, but no inode references this doc-id
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 179999604736
root : ERROR Process execution failed
Traceback (most recent call last):
File "/private/tmp/asahi-install/main.py", line 820, in
InstallerMain().main()
File "/private/tmp/asahi-install/main.py", line 672, in main
while self.main_loop():
File "/private/tmp/asahi-install/main.py", line 792, in main_loop
return self.action_resize(parts_resizable)
File "/private/tmp/asahi-install/main.py", line 612, 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', '179999604736']' 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
caiyanzhe@caiyanzhedeMacBook-Air ~ %

Some of my journalctl logs are going missing when I reboot, I am using this:

https://github.com/leifliddy/asahi-fedora-builder

with a realtime kernel:

https://github.com/ericcurtin/linux

with these config options:

https://github.com/ericcurtin/linux/blob/asahilinux-linux-rt-devel/config-m1.txt

Struggling to figure out why. I'm using a Mac Mini M1

Hey, was just wondering (I hope this is the right place to ask this), is there support for building and installing kernel modules? I tried installing the standard linux-headers for aarch64 and working with that, but as expected, it didn't really go well (compiling went fine, but installing it failed with invalid module format).

Thanks in advance for any type of help/guidance!
Adam

I've followed the guide and installed the mesa-asahi-edge and asahi-edge kernel. When I reboot the asahi linux, and choose Wayland to login, I only get a blinking blank screen and it goes back to the login screen after about three seconds. My macOS version is 12.6.1, and I installed asahi-linux about 3 months ago without enabling the expert mode. You can find the asahi-diagnose file below. Please let me know if you need any more details. Thanks!
asahi-diagnose-20221207-110359.txt

Hi,

I've just experienced a GPU lockup while moving a panel from the bottom to the top in Plasma (It appears I have also hovered over the 'Spacer' widget), after deleting a panel at the top. Before this, I was playing SuperTuxKart and SuperTux 2 while using the Falkon web browser. This was in a Wayland session. I cannot use Ctrl+Alt+number to change to a different TTY.

I was able to log into the system via SSH and run asahi-diagnose. Here is the output:

asahi-diagnose.txt

Here is how the screen looks:

I hope this helps.

I Would Like to find Asahi Linux desktop images but I can't find any and I can't compile the linux kernel so can someone help me

In my mac m1, I can't hear audio both headphones and without headphones.

Is that features is not supported for now or how can I fix that?

Please help!

Was wondering if Github Discussions could be setup for lesser issues that are separate from the normal kind seen here? 🤔 E.g.

- Questions (Whether or not it would track Linux:Next or Mainline Branch including prev rc's instead of stable for any Asahi Beta to get helpful features such as those implemented in 5.16/17

- Discussions about potential supplementary discord server or similar platform for easy way to communicate with community, has its benefits

- and discussing issues like this in itself would be better there as opposed to making an issue here and possibly being disruptive.

Just reporting, but it seems that the system doesn't want to let me use a static IP instead of the DHCP assigned IP.

I tried to follow a few different tutorials using both eth0 and enp3s0 interfaces with no luck.

I can use the system up to a few hours at a time. The longest was ~8 hours. The shortest was ~30 minutes.

Below is the journal of up to 10 minutes ago. 00:58:07 is the time it crashed. This time it crashed when I clicked on the Activities menu on Gnome. The action before the crash isn't consistent.

When it crashes, the system shows me the log in screen. I can log back in but the work I was doing is gone.

$ coredumpctl list
TIME                           PID  UID  GID SIG     COREFILE EXE                        SIZE
Sat 2022-07-02 02:32:11 AEST  6472 1001 1001 SIGTRAP none     /usr/bin/gnome-shell        n/a
Sat 2022-07-02 02:32:20 AEST  6538 1001 1001 SIGTRAP none     /usr/bin/gnome-shell        n/a
Sat 2022-07-02 02:33:04 AEST  6656  120  120 SIGTRAP present  /usr/bin/gnome-shell       4.4M
...
Tue 2022-07-05 00:58:07 AEST   855 1001 1001 SIGSEGV none     /usr/bin/gnome-shell        n/a

Jul 05 00:54:19 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:19 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:19 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:19 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:20 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:20 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:20 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:20 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:21 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:32 xxxxx-m1x14-asahi kernel: spihid_process_read: 1 callbacks suppressed
Jul 05 00:54:32 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:32 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:32 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:32 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:32 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:32 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:33 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:33 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:33 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:36 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:37 xxxxx-m1x14-asahi kernel: spihid_process_read: 7 callbacks suppressed
Jul 05 00:54:37 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:41 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:42 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:44 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:49 xxxxx-m1x14-asahi chromium.desktop[70185]: [70185:70191:0705/005449.968936:ERROR:socket_manager.cc(127)] Failed to resolve address for stun.services.mozilla.com., errorcode: -105
Jul 05 00:54:49 xxxxx-m1x14-asahi chromium.desktop[70185]: [70185:70191:0705/005449.968964:ERROR:socket_manager.cc(127)] Failed to resolve address for stun.services.mozilla.com., errorcode: -105
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:54:54 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:55:07 xxxxx-m1x14-asahi kernel: spi-hid-apple-of spi0.0: Read package crc mismatch
Jul 05 00:55:56 xxxxx-m1x14-asahi systemd[1]: run-docker-runtime\x2drunc-moby-239bae7fd5484b977e6a9aeb40888c61c464059e4709cb2857d6b2730fc3fc4a-runc.dVV9Q3.mount: Deactivated successfully.
Jul 05 00:56:11 xxxxx-m1x14-asahi dockerd[1833]: time="2022-07-05T00:56:11.618970045+10:00" level=warning msg="got error while decoding json" error="unexpected EOF" retries=0
Jul 05 00:57:30 xxxxx-m1x14-asahi dockerd[1833]: time="2022-07-05T00:57:30.863513786+10:00" level=warning msg="got error while decoding json" error="unexpected EOF" retries=0
Jul 05 00:58:07 xxxxx-m1x14-asahi audit[855]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-7" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi audit[855]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-1" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi audit[855]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-8" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi audit[855]: ANOM_ABEND auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-0" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1701 audit(1656946687.027:1823): auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-7" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1701 audit(1656946687.027:1822): auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-1" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1701 audit(1656946687.027:1824): auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-8" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1701 audit(1656946687.027:1825): auid=1001 uid=1001 gid=1001 ses=4 pid=855 comm="llvmpipe-0" exe="/usr/bin/gnome-shell" sig=11 res=1
Jul 05 00:58:07 xxxxx-m1x14-asahi audit: BPF prog-id=291 op=LOAD
Jul 05 00:58:07 xxxxx-m1x14-asahi audit: BPF prog-id=292 op=LOAD
Jul 05 00:58:07 xxxxx-m1x14-asahi audit: BPF prog-id=293 op=LOAD
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1334 audit(1656946687.044:1826): prog-id=291 op=LOAD
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1334 audit(1656946687.044:1827): prog-id=292 op=LOAD
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1334 audit(1656946687.044:1828): prog-id=293 op=LOAD
Jul 05 00:58:07 xxxxx-m1x14-asahi audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@6-129392-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 05 00:58:07 xxxxx-m1x14-asahi systemd[1]: Started Process Core Dump (PID 129392/UID 0).
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1130 audit(1656946687.045:1829): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@6-129392-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 05 00:58:07 xxxxx-m1x14-asahi systemd-coredump[129393]: Resource limits disable core dumping for process 855 (gnome-shell).
Jul 05 00:58:07 xxxxx-m1x14-asahi systemd-coredump[129393]: [LNK] Process 855 (gnome-shell) of user 1001 dumped core.
Jul 05 00:58:07 xxxxx-m1x14-asahi kernel: audit: type=1131 audit(1656946687.088:1830): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@6-129392-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 05 00:58:07 xxxxx-m1x14-asahi audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@6-129392-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 05 00:58:07 xxxxx-m1x14-asahi systemd[1]: [email protected]: Deactivated successfully.
Jul 05 00:58:07 xxxxx-m1x14-asahi gnome-shell[20444]: (EE) failed to read Wayland events: Connection reset by peer
Jul 05 00:58:07 xxxxx-m1x14-asahi terminator[1446]: Error reading events from display: Connection reset by peer

                   -`                    xxx@xxx-m1x14-asahi 
                  .o+`                   ----------------------------- 
                 `ooo/                   OS: Arch Linux ARM aarch64 
                `+oooo:                  Host: Apple MacBook Pro (14-inch, M1 Max, 2021) 
               `+oooooo:                 Kernel: 5.17.0-rc7-asahi-next-20220310-5-2-ARCH 
               -+oooooo+:                Uptime: 4 hours, 3 mins 
             `/:-:++oooo+:               Packages: 828 (pacman) 
            `/++++/+++++++:              Shell: bash 5.1.16 
           `/++++++++++++++:             Resolution: 3024x1890 
          `/+++ooooooooooooo/`           DE: GNOME 42.3 
         ./ooosssso++osssssso+`          WM: Mutter 
        .oossssso-````/ossssss+`         WM Theme: Adwaita 
       -osssssso.      :ssssssso.        Theme: Adwaita [GTK2/3] 
      :osssssss/        osssso+++.       Icons: Adwaita [GTK2/3] 
     /ossssssss/        +ssssooo/-       Terminal: terminator 
   `/ossssso+/:-        -:/+osssso+-     CPU: (10) @ 2.064GHz 
  `+sso+:-`                 `.-/+oso:    Memory: 15546MiB / 64284MiB 
 `++:.                           `-/+/
 .`                                 `/                           

                                                                 

I've decided to install the new OpenGL GPU update but after I reboot, my Asahi install wont boot; I've selected Arch from grub but after that it gets stuck on the screen after that and reboots. What can I do to troubleshoot this issue? Thanks.

Host: MacBook Air (M1, 2020)
OS: Arch Linux ARM

I just installed the new gpu driver and installed plasma wayland as recommended from the wiki but it won't launch

Followed the installer yesterday. All worked fine
Booted back to macOS to ensure things were working as intended over there still
Booted back to Asahi to find ethernet device missing
ifconfig only showed l0 and wlan0
lspci -v results showed no Ethernet Controller only:

01:00.0 Network controller: Broadcom Inc. and subsidiaries BRCM4378 Wireless Network Adapter (rev 03)
        Subsystem: Apple Inc. Device 4378
        Device tree node: /sys/firmware/devicetree/base/soc/pcie@690000000/pci@0,0/network@0,0
        Flags: bus master, fast devsel, latency 0, IRQ 128, IOMMU group 4
        Memory at 6c0c00000 (64-bit, non-prefetchable) [size=64K]
        Memory at 6c0000000 (64-bit, non-prefetchable) [size=8M]
        Capabilities: <access denied>
        Kernel driver in use: brcmfmac
        Kernel modules: brcmfmac

01:00.1 Network controller: Broadcom Inc. and subsidiaries BRCM4378 Bluetooth Controller (rev 03)
        Subsystem: Apple Inc. Device 4378
        Device tree node: /sys/firmware/devicetree/base/soc/pcie@690000000/pci@0,0/network@0,1
        Flags: bus master, fast devsel, latency 0, IRQ 127, IOMMU group 4
        Memory at 6c0c10000 (64-bit, non-prefetchable) [size=32K]
        Memory at 6c0800000 (64-bit, non-prefetchable) [size=4M]
        Capabilities: <access denied>
        Kernel driver in use: hci_bcm4377
        Kernel modules: hci_bcm4377

dmesg | grep atla returned no results

Rebooted again
Ran lspci -v and now the following showed:

01:00.0 Network controller: Broadcom Inc. and subsidiaries BRCM4378 Wireless Network Adapter (rev 03)
        Subsystem: Apple Inc. Device 4378
        Device tree node: /sys/firmware/devicetree/base/soc/pcie@690000000/pci@0,0/network@0,0
        Flags: bus master, fast devsel, latency 0, IRQ 128, IOMMU group 4
        Memory at 6c0c00000 (64-bit, non-prefetchable) [size=64K]
        Memory at 6c0000000 (64-bit, non-prefetchable) [size=8M]
        Capabilities: <access denied>
        Kernel driver in use: brcmfmac
        Kernel modules: brcmfmac

01:00.1 Network controller: Broadcom Inc. and subsidiaries BRCM4378 Bluetooth Controller (rev 03)
        Subsystem: Apple Inc. Device 4378
        Device tree node: /sys/firmware/devicetree/base/soc/pcie@690000000/pci@0,0/network@0,1
        Flags: bus master, fast devsel, latency 0, IRQ 127, IOMMU group 4
        Memory at 6c0c10000 (64-bit, non-prefetchable) [size=32K]
        Memory at 6c0800000 (64-bit, non-prefetchable) [size=4M]
        Capabilities: <access denied>
        Kernel driver in use: hci_bcm4377
        Kernel modules: hci_bcm4377

...

03:00.0 Ethernet controller: Aquantia Corp. Device 04c0 (rev 03)
        Subsystem: Apple Inc. Device 0223
        Device tree node: /sys/firmware/devicetree/base/soc/pcie@690000000/pci@2,0/ethernet@0,0
        Flags: bus master, fast devsel, latency 0, IRQ 116, IOMMU group 5
        Memory at 6c0e00000 (64-bit, non-prefetchable) [size=512K]
        Memory at 6c0e80000 (64-bit, non-prefetchable) [size=4K]
        Memory at 6c1000000 (64-bit, non-prefetchable) [size=4M]
        Capabilities: <access denied>
        Kernel driver in use: atlantic
        Kernel modules: atlantic

Ran dmesg | grep atla and now the following showed:

[    2.478726] atlantic 0000:03:00.0: Adding to iommu group 5
[    2.478776] atlantic 0000:03:00.0: enabling device (0000 -> 0002)
[    2.528622] atlantic: Detect ATL2FW 103000d
[    2.531107] atlantic 0000:03:00.0 end0: renamed from eth0
[    2.571464] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,atlantisb-RASP-m-6.11-X3.bin failed with error -2
[    2.571598] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,atlantisb-RASP-m-6.11.bin failed with error -2
[    2.571646] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,atlantisb-RASP-m.bin failed with error -2
[    2.571656] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,atlantisb-RASP.bin failed with error -2
[    2.571667] brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,atlantisb-X3.bin failed with error -2
[    9.889006] atlantic 0000:03:00.0 end0: atlantic: link change old 0 new 1000

If there is anything I can do to assist in the case of the missing PCI device after reboot bug outlined above. Please let me know!

After running sudo pacman -Syu My mac mini just boot loops until it reaches a recovery screen.

Machine: macbook air 2020

In a few cases the wifi pcie device is not detected by the kernel. There seems to be a common (rather odd) pattern:

• On the first boot after leaving the machine powered off for a few hours the behaviour appears
• On subsequent reboots, poweroff (even if I wait 15 minutes): the wifi device is detected.

This is rather odd but it happend on the two times I booted the machine after having left it for a few hours, but never in the 50-ish reboot or poweroff+wait+boot I tried during the couple of hours after the first time it happened.

Here is the diff of dmesg output between a boot which detected the wifi pcie device and a boot that did not:

--- dmesg-20220305-1.log	2022-03-05 22:44:35.000000000 +0000
+++ dmesg-20220305-4.log	2022-03-05 22:44:42.000000000 +0000
@@ -10,11 +10,11 @@
   Normal   empty
 Movable zone start for each node
 Early memory node ranges
-  node   0: [mem 0x0000000801cbc000-0x0000000802827fff]
-  node   0: [mem 0x0000000802828000-0x00000008028e7fff]
-  node   0: [mem 0x00000008028e8000-0x000000080437ffff]
-  node   0: [mem 0x0000000804380000-0x000000080439bfff]
-  node   0: [mem 0x000000080439c000-0x0000000bd9f6ffff]
+  node   0: [mem 0x0000000801cbc000-0x0000000802c3ffff]
+  node   0: [mem 0x0000000802c40000-0x0000000802cfffff]
+  node   0: [mem 0x0000000802d00000-0x000000080477ffff]
+  node   0: [mem 0x0000000804780000-0x000000080479bfff]
+  node   0: [mem 0x000000080479c000-0x0000000bd9f6ffff]
   node   0: [mem 0x0000000bd9f70000-0x0000000bd9f7bfff]
   node   0: [mem 0x0000000bd9f7c000-0x0000000bdefaffff]
   node   0: [mem 0x0000000bdefb0000-0x0000000bdefbffff]
@@ -85,12 +85,12 @@
 x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000
 x23: 0000000000000000 x22: 0000000000000000 x21: ffff8000092cc000
 x20: ffff800009270a20 x19: ffff0003731bd388 x18: 0000000000000050
-x17: 00000000aa9d7b42 x16: 000000003fc4a5b8 x15: fffffffffffc1488
-x14: 000000009f4d7c9d x13: ffff80000914e240 x12: 00000000000000de
+x17: 000000009e275909 x16: 00000000cefee570 x15: fffffffffffc1488
+x14: 000000006dd3b4dc x13: ffff80000914e240 x12: 00000000000000de
 x11: 000000000000004a x10: ffff8000091fe930 x9 : ffff80000914e240
 x8 : 00000000ffffdfff x7 : ffff8000091fe240 x6 : 00000000000006f0
 x5 : 0000000000017ff4 x4 : 00000000ffffe04a x3 : 0000000000000000
-x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000001e34040
+x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff000001e2e4c0
 Call trace:
  efi_create_mapping+0x7c/0x16c
  arm_enable_runtime_services+0x12c/0x1e0
@@ -207,7 +207,7 @@
 nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
 NET: Registered PF_ALG protocol family
 xor: measuring software checksum speed
-   8regs           : 13168 MB/sec
+   8regs           : 13199 MB/sec
    32regs          : 26794 MB/sec
    arm64_neon      : 27584 MB/sec
 xor: using function: arm64_neon (27584 MB/sec)
@@ -269,24 +269,24 @@
 apple-gpio-pinctrl 23c100000.pinctrl: No cache defaults, reading back from HW
 apple-gpio-pinctrl 23d1f0000.pinctrl: No cache defaults, reading back from HW
 macsmc-rtkit 23e400000.smc: RTKit: Initializing (protocol version 12)
-apple-gpio-pinctrl 23e820000.pinctrl: No cache defaults, reading back from HW
 nvme-apple 27bcc0000.nvme: RTKit: Initializing (protocol version 12)
-apple-gpio-pinctrl 24a820000.pinctrl: No cache defaults, reading back from HW
+apple-gpio-pinctrl 23e820000.pinctrl: No cache defaults, reading back from HW
 macsmc-rtkit 23e400000.smc: Initialized (1378 keys #KEY (0x234b4559)..zETM (0x7a45544d))
-OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
-OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
-OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
-OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
-OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
-OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
+apple-gpio-pinctrl 24a820000.pinctrl: No cache defaults, reading back from HW
 nvme-apple 27bcc0000.nvme: RTKit: syslog message: cmd.c:6025:  boot mode normal
 nvme-apple 27bcc0000.nvme: RTKit: syslog message: nvme_admin_ans2.c:2880: Invalid namespace 0
 nvme nvme0: Identify NS List failed (status=0xb)
 nvme-apple 27bcc0000.nvme: RTKit: syslog message: nvme_admin_ans2.c:2880: Invalid namespace 0
  nvme0n1: p1 p2 p3 p4 p5 p6
 spi-hid-apple-of spi0.0: spihid_apple_of_probe:74
+OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
+OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
+OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
+OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
+OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
+OF: Bad cell count for /soc/spmi@23d0d9300/pmu@f
 macsmc-rtc macsmc-rtc: registered as rtc0
-macsmc-rtc macsmc-rtc: setting system clock to 2022-03-05T13:25:28 UTC (1646486728)
+macsmc-rtc macsmc-rtc: setting system clock to 2022-03-05T22:15:50 UTC (1646518550)
 dwc3 382280000.usb: Adding to iommu group 0
 spi-hid-apple-of spi0.0: limiting the number of devices to mngt, kbd and mouse
 dwc3 502280000.usb: Adding to iommu group 1
@@ -298,7 +298,6 @@
 apple 001C:05AC:0281.0001: input,hidraw0: SPI HID v9.35 Keyboard [Apple Internal Keyboard / Trackpad] on spi0.0 (1)
 input: Apple Internal Keyboard / Trackpad as /devices/platform/soc/23510c000.spi/spi_master/spi0/spi0.0/001C:05AC:0281.0002/input/input6
 magicmouse 001C:05AC:0281.0002: input,hidraw1: SPI HID v9.35 Mouse [Apple Internal Keyboard / Trackpad] on spi0.0 (2)
-EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Quota mode: none.
 xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
 xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
 xhci-hcd xhci-hcd.0.auto: hcc params 0x0238ffcd hci version 0x110 quirks 0x0000000000010010
@@ -321,6 +320,7 @@
 usb usb2: SerialNumber: xhci-hcd.0.auto
 hub 2-0:1.0: USB hub found
 hub 2-0:1.0: 1 port detected
+EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Quota mode: none.
 xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
 xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
 xhci-hcd xhci-hcd.1.auto: hcc params 0x0238ffcd hci version 0x110 quirks 0x0000000000010010
@@ -346,8 +346,6 @@
 systemd[1]: systemd 250.3-4-arch running in system mode (+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unified)
 systemd[1]: Detected architecture arm64.
 systemd[1]: Hostname set to <alarm>.
-systemd[1]: Condition check resulted in Root Slice being skipped.
-systemd[1]: Condition check resulted in System Slice being skipped.
 systemd[1]: Queued start job for default target Graphical Interface.
 random: systemd: uninitialized urandom read (16 bytes read)
 systemd[1]: Created slice Slice /system/getty.
@@ -390,6 +388,7 @@
 systemd[1]: Starting Generate network units from Kernel command line...
 systemd[1]: Starting Remount Root and Kernel File Systems...
 systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
+fuse: init (API version 7.36)
 systemd[1]: Starting Coldplug udev Block Devices...
 systemd[1]: Mounted Huge Pages File System.
 systemd[1]: Mounted POSIX Message Queue File System.
@@ -397,30 +396,29 @@
 systemd[1]: Mounted Temporary Directory /tmp.
 systemd[1]: Finished Create List of Static Device Nodes.
 systemd[1]: [email protected]: Deactivated successfully.
-fuse: init (API version 7.36)
 systemd[1]: Finished Load Kernel Module configfs.
 systemd[1]: [email protected]: Deactivated successfully.
 systemd[1]: Finished Load Kernel Module drm.
-systemd[1]: Finished Load Kernel Modules.
 systemd[1]: [email protected]: Deactivated successfully.
+EXT4-fs (nvme0n1p5): re-mounted. Quota mode: none.
 systemd[1]: Finished Load Kernel Module fuse.
-systemd[1]: Mounting FUSE Control File System...
-systemd[1]: Mounting Kernel Configuration File System...
-systemd[1]: Starting Apply Kernel Variables...
+systemd[1]: Finished Load Kernel Modules.
 systemd[1]: Finished Generate network units from Kernel command line.
-systemd[1]: Finished Coldplug udev Block Devices.
-EXT4-fs (nvme0n1p5): re-mounted. Quota mode: none.
-systemd[1]: Mounted FUSE Control File System.
-systemd[1]: Mounted Kernel Configuration File System.
 systemd[1]: Finished Remount Root and Kernel File Systems.
+systemd[1]: Finished Coldplug udev Block Devices.
 systemd[1]: Reached target Preparation for Network.
+systemd[1]: Mounting FUSE Control File System...
+systemd[1]: Mounting Kernel Configuration File System...
 systemd[1]: First Boot Wizard was skipped because of a failed condition check (ConditionFirstBoot=yes).
 systemd[1]: Starting Grow File System on /...
 systemd[1]: Rebuild Hardware Database was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
 systemd[1]: Platform Persistent Storage Archival was skipped because of a failed condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
 systemd[1]: Starting Load/Save Random Seed...
+systemd[1]: Starting Apply Kernel Variables...
 systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
 systemd[1]: Starting Create Static Device Nodes in /dev...
+systemd[1]: Mounted FUSE Control File System.
+systemd[1]: Mounted Kernel Configuration File System.
 systemd[1]: Finished Apply Kernel Variables.
 EXT4-fs (nvme0n1p5): resizing filesystem from 23704490 to 23704490 blocks
 systemd[1]: Finished Grow File System on /.
@@ -433,35 +431,37 @@
 systemd[1]: Entropy Daemon based on the HAVEGE algorithm was skipped because of a failed condition check (ConditionKernelVersion=<5.6).
 systemd[1]: Starting Journal Service...
 systemd[1]: Starting Rule-based Manager for Device Events and Files...
+systemd[1]: Started Rule-based Manager for Device Events and Files.
+audit: type=1130 audit(1646518550.811:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1334 audit(1646518550.812:3): prog-id=12 op=LOAD
+systemd[1]: Starting Network Configuration...
 systemd[1]: Started Journal Service.
-audit: type=1130 audit(1646486728.775:2): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-systemd-journald[322]: Received client request to flush runtime journal.
-audit: type=1130 audit(1646486728.787:3): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1334 audit(1646486728.787:4): prog-id=12 op=LOAD
-audit: type=1130 audit(1646486728.811:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1130 audit(1646518550.819:4): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+systemd-journald[319]: Received client request to flush runtime journal.
 cfg80211: Loading compiled-in X.509 certificates for regulatory database
+audit: type=1130 audit(1646518550.856:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-journal-flush comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
 platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
 cfg80211: failed to load regulatory.db
-audit: type=1130 audit(1646486728.859:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1130 audit(1646518550.864:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-networkd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
 FAT-fs (nvme0n1p4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
-audit: type=1130 audit(1646486728.897:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=update-vendor-firmware comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1130 audit(1646486728.902:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-boot-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1130 audit(1646486728.925:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1334 audit(1646486728.926:10): prog-id=13 op=LOAD
+audit: type=1130 audit(1646518550.925:7): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=update-vendor-firmware comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1130 audit(1646518550.930:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-boot-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1130 audit(1646518550.954:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1334 audit(1646518550.955:10): prog-id=13 op=LOAD
 alg: No test for hmac(md4) (hmac(md4-generic))
-cs42l42 2-0048: No cache used with register defaults set!
-cs42l42 2-0048: supply VA not found, using dummy regulator
-cs42l42 2-0048: supply VP not found, using dummy regulator
-cs42l42 2-0048: supply VCP not found, using dummy regulator
-cs42l42 2-0048: supply VD_FILT not found, using dummy regulator
-cs42l42 2-0048: supply VL not found, using dummy regulator
+cs42l42 0-0048: No cache used with register defaults set!
+cs42l42 0-0048: supply VA not found, using dummy regulator
+cs42l42 0-0048: supply VP not found, using dummy regulator
+cs42l42 0-0048: supply VCP not found, using dummy regulator
+cs42l42 0-0048: supply VD_FILT not found, using dummy regulator
+cs42l42 0-0048: supply VL not found, using dummy regulator
+cs42l42 0-0048: CS42L42 Device ID (42A83). Expected 42A42
+cs42l42 0-0048: Cirrus Logic CS42L42, Revision: B0
 macsmc-gpio macsmc-gpio: First GPIO key: gP01 (0x67503031)
-cs42l42 2-0048: CS42L42 Device ID (42A83). Expected 42A42
 pcie-apple 690000000.pcie: host bridge /soc/pcie@690000000 ranges:
 pcie-apple 690000000.pcie:      MEM 0x06a0000000..0x06bfffffff -> 0x06a0000000
 pcie-apple 690000000.pcie:      MEM 0x06c0000000..0x06ffffffff -> 0x00c0000000
-cs42l42 2-0048: Cirrus Logic CS42L42, Revision: B0
 macsmc-reboot macsmc-reboot: Handling reboot and poweroff requests via SMC
 pcie-apple 690000000.pcie: Link up on /soc/pcie@690000000/pci@0,0
 pcie-apple 690000000.pcie: ECAM at [mem 0x690000000-0x690ffffff] for [bus 00-03]
@@ -472,64 +472,21 @@
 pci 0000:00:00.0: [106b:100c] type 01 class 0x060400
 pci 0000:00:00.0: PME# supported from D0 D3hot D3cold
 pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
-pci 0000:01:00.0: [14e4:4425] type 00 class 0x028000
-pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit]
-pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x007fffff 64bit]
-pci 0000:01:00.0: supports D1 D2
-pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
-pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:00.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
-pci 0000:01:00.1: [14e4:5f69] type 00 class 0x028000
-pci 0000:01:00.1: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
-pci 0000:01:00.1: reg 0x18: [mem 0x00000000-0x003fffff 64bit]
-pci 0000:01:00.1: supports D1 D2
-pci 0000:01:00.1: PME# supported from D0 D1 D2 D3hot D3cold
 pci_bus 0000:01: busn_res: [bus 01-03] end is updated to 01
-pci 0000:00:00.0: BAR 14: assigned [mem 0x6c0000000-0x6c0dfffff]
-pci 0000:01:00.0: BAR 2: assigned [mem 0x6c0000000-0x6c07fffff 64bit]
-pci 0000:01:00.1: BAR 2: assigned [mem 0x6c0800000-0x6c0bfffff 64bit]
-pci 0000:01:00.0: BAR 0: assigned [mem 0x6c0c00000-0x6c0c0ffff 64bit]
-pci 0000:01:00.1: BAR 0: assigned [mem 0x6c0c10000-0x6c0c17fff 64bit]
 pci 0000:00:00.0: PCI bridge to [bus 01]
-pci 0000:00:00.0:   bridge window [mem 0x6c0000000-0x6c0dfffff]
 OF: /soc/pcie@690000000: no iommu-map translation for id 0x0 on (null)
-pcieport 0000:00:00.0: enabling device (0000 -> 0002)
 pcieport 0000:00:00.0: PME: Signaling with IRQ 103
 pcieport 0000:00:00.0: AER: enabled with IRQ 103
-usbcore: registered new interface driver brcmfmac
-brcmfmac 0000:01:00.0: Adding to iommu group 2
-brcmfmac 0000:01:00.0: enabling device (0000 -> 0002)
-brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4378b1-pcie for chip BCM4378/3
-brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP-u-6.5-X3.bin failed with error -2
-brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP-u-6.5.bin failed with error -2
-brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP-u.bin failed with error -2
-brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-RASP.bin failed with error -2
-brcmfmac 0000:01:00.0: Direct firmware load for brcm/brcmfmac4378b1-pcie.apple,shikoku-X3.bin failed with error -2
-brcmfmac: brcmf_c_process_txcap_blob: TxCap blob found, loading
-brcmfmac: brcmf_c_process_cal_blob: Calibration blob provided by platform, loading
-brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4378/3 wl0: Oct 26 2021 16:10:41 version 18.20.310.15.7.8.120 FWID 01-5d6c3867
 random: crng init done
 random: 7 urandom warning(s) missed due to ratelimiting
-systemd-journald[322]: Time jumped backwards, rotating.
-kauditd_printk_skb: 21 callbacks suppressed
-audit: type=1100 audit(1646486729.772:32): pid=431 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty1 res=success'
-audit: type=1101 audit(1646486729.773:33): pid=431 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty1 res=success'
-audit: type=1103 audit(1646486729.773:34): pid=431 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty1 res=success'
-audit: type=1006 audit(1646486729.774:35): pid=431 uid=0 old-auid=4294967295 auid=0 tty=tty1 old-ses=4294967295 ses=1 res=1
-audit: type=1300 audit(1646486729.774:35): arch=c00000b7 syscall=64 success=yes exit=1 a0=4 a1=fffff4e29250 a2=1 a3=ffff87b4cc60 items=0 ppid=1 pid=431 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=1 comm="login" exe="/usr/bin/login" key=(null)
-audit: type=1327 audit(1646486729.774:35): proctitle=2F62696E2F6C6F67696E002D70002D2D
-audit: type=1130 audit(1646486729.791:36): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1101 audit(1646486729.796:37): pid=436 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1103 audit(1646486729.796:38): pid=436 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
-audit: type=1006 audit(1646486729.796:39): pid=436 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=2 res=1
-kauditd_printk_skb: 15 callbacks suppressed
-audit: type=1130 audit(1646487092.269:49): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1100 audit(1646487101.735:50): pid=509 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="kit_ty_kate" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty2 res=success'
-audit: type=1101 audit(1646487101.735:51): pid=509 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="kit_ty_kate" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty2 res=success'
-audit: type=1103 audit(1646487101.736:52): pid=509 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="kit_ty_kate" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty2 res=success'
-audit: type=1006 audit(1646487101.736:53): pid=509 uid=0 old-auid=4294967295 auid=1001 tty=tty2 old-ses=4294967295 ses=3 res=1
-audit: type=1300 audit(1646487101.736:53): arch=c00000b7 syscall=64 success=yes exit=4 a0=5 a1=ffffea2dc530 a2=4 a3=ffff22b6cc60 items=0 ppid=1 pid=509 auid=1001 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=1001 fsgid=0 tty=tty2 ses=3 comm="login" exe="/usr/bin/login" key=(null)
-audit: type=1327 audit(1646487101.736:53): proctitle=2F62696E2F6C6F67696E002D70002D2D
-audit: type=1130 audit(1646487101.742:54): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@1001 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1101 audit(1646487101.748:55): pid=511 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="kit_ty_kate" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
-audit: type=1103 audit(1646487101.748:56): pid=511 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="kit_ty_kate" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
-audit: type=1006 audit(1646487101.748:57): pid=511 uid=0 old-auid=4294967295 auid=1001 tty=(none) old-ses=4294967295 ses=4 res=1
+kauditd_printk_skb: 20 callbacks suppressed
+audit: type=1100 audit(1646518557.550:31): pid=427 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty1 res=success'
+audit: type=1101 audit(1646518557.552:32): pid=427 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty1 res=success'
+audit: type=1103 audit(1646518557.552:33): pid=427 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_securetty,pam_shells,pam_faillock,pam_permit,pam_faillock acct="root" exe="/usr/bin/login" hostname=alarm addr=? terminal=/dev/tty1 res=success'
+audit: type=1006 audit(1646518557.552:34): pid=427 uid=0 old-auid=4294967295 auid=0 tty=tty1 old-ses=4294967295 ses=1 res=1
+audit: type=1300 audit(1646518557.552:34): arch=c00000b7 syscall=64 success=yes exit=1 a0=4 a1=fffff1c9b820 a2=1 a3=ffff651ecc60 items=0 ppid=1 pid=427 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=tty1 ses=1 comm="login" exe="/usr/bin/login" key=(null)
+audit: type=1327 audit(1646518557.552:34): proctitle=2F62696E2F6C6F67696E002D70002D2D
+audit: type=1130 audit(1646518557.574:35): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1101 audit(1646518557.580:36): pid=429 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pam_unix,pam_permit,pam_time acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
+audit: type=1103 audit(1646518557.580:37): pid=429 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="root" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
+audit: type=1006 audit(1646518557.580:38): pid=429 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=2 res=1

"as expected" by such a diff, when this behaviour happens, lspci only returns:

00:00.0 PCI bridge: Apple Inc. Device 100c (rev 01)

Complete dmesg and diff here: https://gist.github.com/kit-ty-kate/348689e9b460b7267a5153bb12a5064b

xiaotaiyang@bogon ~ % curl https://alx.sh | sh
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1049 100 1049 0 0 969 0 0:00:01 0:00:01 --:--:-- 974

Bootstrapping installer:
Checking version...
Version: v0.3.26
Downloading...
xiaotaiyang@bogon ~ %