Who is excited for the Fedora Asahi Remix release?

im so excited for the release today/tomorrow! I’m hoping that speakers for m1 macbook air comes out! fingers crossed! What things are you hoping for?

I am waiting for speaker support and touch id and I have problems with NAT for iptables, maybe the problem is fixed there.

Official release has been delayed Conformant GPU drivers and Remix updates


You beat me to it by one minute!

It’s also worthwhile to note that - regardless of official release status - right now, Fedora Asahi Remix is in excellent shape for use as a daily driver :partying_face:



Agreed, if you don’t need the handful of hardware that isn’t working it’s working wonderfully

I have workarounds for these, but I’d be very happy to have either these two things:

  • bluetooth audio working with 2G wifi
  • webcam

Been waiting for this release for a long time, my computer has had a 41 day uptime just because of it!

It works great now, but 2 things are missing before I use it as daily driver.
-Bluetooth connection logitech mx master 3.
-Widevine for chromium or firefox.

The Bluetooth pairing issues with that mouse are starting to sound like a more generic issue, other people have reported trouble with that mouse in other systems [1] [2] [3]… unless someone who owns one can figure out what’s wrong I’m not sure there’s much we can do about it from our side in the short term. We just write the Bluetooth driver which just passes packets back and forth, it doesn’t handle details like pairing or anything device-specific, that’s down to firmware and Linux common code (BlueZ)…

Right now there are three Bluetooth known issues that are known to be in scope for us and we’re planning to investigate further: pairing key sharing with macOS, fixing/improving WiFi coexistence, and fixing sleep mode breaking Bluetooth.

As for Widevine, I have ideas to make it work, but really, you’re relying on obfuscated proprietary software that is intentionally not made available for these platforms in any kind of public, supported way. If we can get it working reasonably it will be despite zero collaboration from Google, and it will involve a giant pile of hacks. The “real” solution here is for Google to make Widevine available for Linux ARM64 platforms like they do for x86 ones. Please don’t expect us to bend over backwards to get it to work; there is only so much we can do when the vendor refuses to support us.


Thanks Hector.
Before I switched to the new fedora version I used this fedora GitHub - leifliddy/asahi-fedora-builder: Builds a minimal Fedora image to run on Apple M1/M2 systems
This is a minimal install. I installed KDE plasma on top and never had any problems connecting MX 3s. I also had chrominum with widevine. Cant remember if I installed it from repos or as an rpm I found.
I have the same problem connecting my MX 2 anywhere.
Thanks for all the great work you do! Linux is far better than macos!

The existing Widevine hacks rely on a patched glibc, which is not an acceptable solution to ship officially. I have ideas for working around that but it remains to be seen whether I run into any roadblocks.

Leif’s images use the same packages as the official ones these days, so there is no difference in Bluetooth stuff. If it used to work then it’s probably either a regression somewhere in upstream code (we certainly haven’t touched the driver recently), or it’s a problem caused by pairing too many times or something like that, or some weird issue related to the order in which you do things or exactly what packages are installed.

Speaking of Windevine on Linux ARM64, I noticed that recent Spotify client seems to “know” about an arm64 build for Linux:

jq '.platforms[]' < "$HOME/.config/spotify/User Data/WidevineCdm/4.10.2652.1/manifest.json"
  "os": "linux",
  "arch": "x64",
  "sub_package_path": "_platform_specific/linux_x64/"
  "os": "linux",
  "arch": "arm64",
  "sub_package_path": "_platform_specific/linux_arm64/"

OK :slight_smile: I am no expert by far!
Sometimes the mx master connects and works fine, but disconnects after a reboot.
But my experiance with linux after 15 years is that it will always be a solution thanks to dedicated people. I can get a new mouse, but netflix and plex is dependent of a working widevine.

I spent way too much time figuring out how to request updates, but unfortunately Google’s update server only returns Linux amd64 builds even if you tell it you’re on arm64. So it looks like if arm64 Linux builds exist, they’re not public.

It does, however, happily serve ChromeOS arm64 packages, which is probably a lot better than trying to pull them from those almost certainly unauthorized Raspberry Pi debs or huge Chrome OS images, so that’s useful (but still subjects us to the ChromeOS build issues).

1 Like

I installed Netflix addon to my LibreELEC install on Raspberry CM4. The Netflix addon detects updates, downloads whole Chrome OS Repair (IIRC) image, extracts Widevine to use it for playing content. There were no issues with this. Of course, that’s a hack/workaround, but It Ain’t Stupid If It Works ™ at least until permanent/better solution is found, maybe ?

I mean, here’s a link to grab just widevine (in funny squashfs format) direct from Google. At least that much I got out of spending hours poking at the Chrome update API :slight_smile:

I’m excited, i hope integrated touchpad on M2 mac 16 inch macbooks will work?

@torleif FYI the latest Asashi kernel version fixed the connectivity with my Logitech MX mouse and keyboard - so give your system an update and try again :grinning:

I believe this was the specific PR if you’re interested - Fix Bluetooth Low Energy Pairing in v6.4 and v6.5 by jannau · Pull Request #194 · AsahiLinux/linux · GitHub

1 Like

Releasing official fedora asahi remix very soon?