leifliddy / asahi-fedora-builder Goto Github PK

Hi,

Don't know if it's good to put this issue here, just upgraded 30 minutes ago on my macbook pro 16 with fedora and I had to boot with the Linux fedora 6.1.0-0.rc1.asahi2.1.fc36.aarch64 kernel to make things work again as the current latest makes the laptop unusable.

Thank you for your work.

Hi!

The latest kernel, (kernel-6.2.0-0.rc2.asahi1.1.fc37.aarch64.rpm) break suspend on MacBook Air M2. (Probably M1 too...)
Computer is totaly freeze when close laptop lid, or enter to suspend mode manualy.
Please keep old kernel (kernel-6.1.0-100.asahi2.1.fc37.aarch64.rpm) in repo to possibble downgrade!

rob

This is more of a question than issue.
I was just wondering whether I could switch to rawhide repos after install ? Or you don't recommend it ?

Any answer appreciated.

I did notice that there's a Fedora 38 repo so I upgraded immediately after a fresh install (kernel version is still the same b/w 37 and 38 though).

Not sure if it's related to the upgrade or not but built-in camera, Macbook Pro 14", doesn't work. Firefox doesn't detect anything. Do you know if there's a package that I can install or maybe some sort of a config?

Also what info would you need in order to troubleshoot?

I had noticed this for some time. Basically, it's like a shutdown but it's still drawing power. If I open it after a day.... the battery is at 0 although I did a shutdown. Anyone else experiencing this. I think I started to notice around 1 month ago. I'll be more attentive on how to reproduce it. Anyone else exhibits this? Nothing is connected to it.

If I shutdown from macos there's no issue.

Hi!

First Congrats for you fantastic work!
One small observation.
The boot Fedora logo is too big for my eyes.
Possibly to make smaller, like apple logo on boot?

Thanx!

Is it possible to extend this builder to support installing Silverblue or Kinoite? Maybe that deserves its own project because it's too far afield, but thought it was worth asking.

Hi!

The gnome-online-accounts add gmail or other acc for need WebKit, is not work :|
Empty page only and always display: "Loading..."

GDK is not able to create a GL context, falling back to glReadPixels (slow!): Unable to create a GL contextGLib-GIO: _g_io_module_get_default:

Epiphany browser too.

"(epiphany:5362): epiphany-WARNING **: 09:18:47.236: Web process crashed"

continously...

This is a WebKit - Mesa problem, i think.

In the Asahi linux distro, works good... Same machine.

rob

Here's a quick and dirty guide on how to transition from this project to ---> Asahi Fedora Remix
https://www.asahi-fedora-remix.org/

Note: You must be running Fedora 37 in order for this to work.

1. install the fedora-remix-branding repo

rpm --import https://download.copr.fedorainfracloud.org/results/@asahi/fedora-remix-branding/pubkey.gpg
curl https://pagure.io/fedora-asahi/asahi-repos/raw/main/f/group_asahi-fedora-remix-branding.repo --output /etc/yum.repos.d/group_asahi-fedora-remix-branding.repo

2. remove this project's repo

rm /etc/yum.repos.d/asahi-linux.repo

3. install the Asahi Fedora Remix common and edge repos

dnf install asahi-repos-common asahi-repos-edge

4. Install the Asahi Fedora Remix mesa rpms

because the rpms in the Asahi Fedora Remix repo have a slightly different versioning scheme
ie they use a tilde in the version mesa-libglapi-23.1.0~asahipre20230321-1.fc37.aarch64
then we need to "downgrade" in order to switch over to the remix version

dnf downgrade $(dnf list installed | grep mesa | grep pre2023 | awk '{print $1}')

6. keep fedora logos (optional)
   if you'd rather keep fedora-logos (vs replacing them with the asahi-fedora-remix-logos variant)
   then I would add this exclude statement to that repo config.

echo 'exclude=asahi-fedora-remix-logos asahi-fedora-remix-release*' >> /etc/yum.repos.d/group_asahi-fedora-remix-branding.repo

7. dnf upgrade

dnf upgrade

8. Switch packages over to the Asahi Fedora Remix versions

run the following command to see which installed packages originated from my repo: @asahi-linux

[root@fedora ~]# dnf list installed | grep @asahi-linux
asahi-firstboot.noarch                               20230128-1.fc37                     @asahi-linux                                                     
kernel.aarch64                                       6.2.0-100.asahi11.1.fc37            @asahi-linux
...
m1n1.aarch64                                         1.2.6-1.fc37                        @asahi-linux                                                     
m1n1-tools.noarch                                    1.2.6-1.fc37                        @asahi-linux                                                     
uboot-images-armv8.noarch                            2023.01-3.fc37                      @asahi-linux  

You can remove the asahi-firstboot package if you want (it was only needed for the first boot)
I would recommend reinstalling anything other then the asahi-firstboot and kernel packages.
That way, are using the official versions of those packages

examples

[root@fedora ~]# dnf reinstall uboot-images-armv8
Last metadata expiration check: 0:22:24 ago on Sat Mar 25 15:04:28 2023.
Dependencies resolved.
======================================================================================================================
 Package                 Arch        Version             Repository                                              Size
======================================================================================================================
Reinstalling:
 uboot-images-armv8      noarch      2023.01-3.fc37      copr:copr.fedorainfracloud.org:group_asahi:u-boot       15 M

Transaction Summary
======================================================================================================================

[root@fedora ~]# dnf reinstall m1n1
Last metadata expiration check: 0:23:01 ago on Sat Mar 25 15:04:28 2023.
Dependencies resolved.
======================================================================================================================
 Package                 Architecture               Version                          Repository                  Size
======================================================================================================================
Reinstalling:
 m1n1                    aarch64                    1.2.6-1.fc37                     updates                    150 k

Transaction Summary
======================================================================================================================

9. Fedora 38

From here you should be able to transition to F38 (if you want to)

dnf install dnf-plugin-system-upgrade
dnf system-upgrade download --releasever=38

10 . Remove exclude statements
Early versions of my build used these exclude statements:
If you see this line:

exclude=kernel kernel-core kernel-devel kernel-headers kernel-modules kernel-modules-extra

in these files:

/etc/yum.repos.d/fedora.repo
/etc/yum.repos.d/fedora-updates.repo

Then please remove them. These exclude statement are no longer needed as priority is used now.

Please let me know if you run into any issues.

Howdy. I'm trying to make an external USB boot drive to set up LUKS encryption as per:

https://davidalger.com/posts/fedora-asahi-remix-on-apple-silicon-with-luks-encryption/
The process has a few snags. First it kept saying "you have to run this script as root and not as sudo." I was actually running as root. I opened a terminal in my user account and did $sudo -i as well as $sudo su root and each time the script kept giving that error. I commented out the check and the install ran fine and appeared to succeed without any error messages.

When I tried to boot from the drive by cancelling the boot process and trying "env set boot_efi_bootmgr" and "run usb_boot", it was saying no usb devices found.

When I tried to boot from the drive by adding an entry in the Grub boot menu, it did show the apparent install to the device, but there doesnt seem to be a kernel. See screenshots.

When I boot from the internal drive I do see this file which is 1.7 GB

/run/media/user/fedora-usb-boot/vmlinuz-6.6.3-408.asahi.fc39.aarch64+16k.hmac

Is that the kernel sought?

There is also a file in that directory, initramfs-6.6.3-408.asahi.fc39.aarch64+16k.img

Could you offer any advice? Thank you. This is a MBP 16" with an M2 pro max chip.

I thought it was the kernel at first, but I started looking at the dnf history and I uninstalled gnome-shell-extension-user-theme-43.0-1.fc37.noarch and that fixed the freeze.

I do have some strange artifacts when logging in but everything is stable.

Somehow controlling the screen brightness doesn't work anymore, I restarted to older kernel to no avail. Still looking to the dnf history and trying to downgrade the culprit. Just FYI. I actually didn't expected the shell extension to be a problem.

The aim is to create an installer identical to this one, except CentOS Stream 9 based. I'll probably create another one after that which is also CentOS Stream 9 based but with the PREEMPT_RT patchset, to sort of replicate our new AutoSD distro https://autosd.sig.centos.org/AutoSD-9/

I'm trying to populate https://github.com/ericcurtin/asahi-centosstream-builder/tree/main/root-www to be like https://leifliddy.com/ and put everything in the one git repo for simplicity.

May I ask what were the manual edits to files and what were the more scripted steps you took to generate the necessary files in leifliddy.com ?

And if you'd rather do this in the https://github.com/leifliddy namespace and maintain that's fine with me too 😄

I don't want to take credit for this cool installer you created. I just want to create unofficial best-effort images for CentOS Stream 9 and AutoSD 9 for personal usage (although I'm sure a few others will end up using too).

As far as I see, sleep is only supported on asahi-edge and this is linux-asahi. Today, I left my MacBook in sleep for a night and lost 20%. I think, this means sleep doesn't work correctly. Is there a way to install asahi-edge here or any other way to fix sleep?

Ever since I've installed Fedora on my 2020 M1 Air, I've noticed that opening preinstalled applications (or some other applications) such as settings, files, and calendar load in about 2-4 seconds, whereas they would load almost instantly on tobhe's Ubuntu version of Asahi, or the vanilla Asahi distro. After a while, it gets extremely annoying. By far, this is the biggest problem I have with Fedora on these machines. Like I said, it's specific to Fedora, not any other distro I have tested on these machines. Any suggestions? If this is fixed it would allow for a faster and more productive workflow for me, and a less annoying one as well.

Peace be upon all of you.

asahi-diagnose-20230319-221917.txt

Hi @leifliddy,

First of all thanks very much for your working porting this to fedora, it's running on my M1 Mac Mini and is running very well. Thanks for sharing this info:

The Fedora kernel config used is nearly identical to the kernel config used by the Asahi Linux project:
**only a few Fedora-specific modifications were made
https://github.com/AsahiLinux/PKGBUILDs/blob/main/linux-asahi/config

Did you build a fedora kernel, an asahi kernel or an upstream kernel here, just wondering what kernel it is specifically?

Chromium does not start, writes an error:

Illegal instruction (core dumped)

Don't know what the reason is?

Hi! Yesterday, I updated my Asahi'd Fedora 37 system to have the newest version of all packages. I rebooted since I didn't see all the kernel packages, and I really didn't expect it to boot. It did boot, though, so I ran dnf check-update to see if any new packages were available. I saw another kernel package, so I updated again and rebooted. No idea how it booted again, but it did.

And for that reason, I now have a weird kernel package that's newer/different than the others:

Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
barrett@canopy ~> sudo dnf update -y
[sudo] password for barrett: 
Copr repo for bottom owned by atim        16 kB/s | 3.3 kB     00:00    
ProtonVPN Fedora Stable repository       1.4 kB/s | 659  B     00:00    
RPM Fusion for Fedora 37 - Free - Update 4.7 kB/s | 2.9 kB     00:00    
RPM Fusion for Fedora 37 - Nonfree - Upd  13 kB/s | 5.8 kB     00:00    
Visual Studio Code                        11 kB/s | 1.5 kB     00:00    
Dependencies resolved.

 Problem 1: package kernel-modules-core-6.2.7-200.fc37.aarch64 requires kernel-uname-r = 6.2.7-200.fc37.aarch64, but none of the providers can be installed
  - cannot install the best update candidate for package kernel-modules-core-6.2.0-100.asahi6.1.fc37.aarch64
  - package kernel-core-6.2.7-200.fc37.aarch64 is filtered out by exclude filtering
 Problem 2: package kernel-modules-core-6.2.7-200.fc37.aarch64 requires kernel-uname-r = 6.2.7-200.fc37.aarch64, but none of the providers can be installed
  - cannot install the best update candidate for package kernel-modules-core-6.2.0-100.asahi10.1.fc37.aarch64
  - package kernel-core-6.2.7-200.fc37.aarch64 is filtered out by exclude filtering
 Problem 3: package kernel-modules-core-6.2.7-200.fc37.aarch64 requires kernel-uname-r = 6.2.7-200.fc37.aarch64, but none of the providers can be installed
  - cannot install the best update candidate for package kernel-modules-core-6.2.0-100.asahi11.1.fc37.aarch64
  - package kernel-core-6.2.7-200.fc37.aarch64 is filtered out by exclude filtering
=========================================================================
 Package                Arch       Version              Repository  Size
=========================================================================
Skipping packages with broken dependencies:
 kernel-modules-core    aarch64    6.2.7-200.fc37       updates     39 M

Transaction Summary
=========================================================================
Skip  1 Package

Nothing to do.
Complete!

As you can see, I'm stuck on this one modern kernel package, but the others seem to be older..? Here's a listing of all my "kernel" packages:

Type help for instructions on how to use fish
barrett@canopy ~> dnf list --installed | grep "kernel"
kernel.aarch64                                     6.2.0-100.asahi6.1.fc37              @asahi-linux                               
kernel.aarch64                                     6.2.0-100.asahi10.1.fc37             @asahi-linux                               
kernel.aarch64                                     6.2.0-100.asahi11.1.fc37             @asahi-linux                               
kernel-core.aarch64                                6.2.0-100.asahi6.1.fc37              @asahi-linux                               
kernel-core.aarch64                                6.2.0-100.asahi10.1.fc37             @asahi-linux                               
kernel-core.aarch64                                6.2.0-100.asahi11.1.fc37             @asahi-linux                               
kernel-devel.aarch64                               6.2.0-100.asahi6.1.fc37              @asahi-linux                               
kernel-devel.aarch64                               6.2.0-100.asahi10.1.fc37             @asahi-linux                               
kernel-devel.aarch64                               6.2.0-100.asahi11.1.fc37             @asahi-linux                               
kernel-headers.aarch64                             6.2.0-100.asahi11.1.fc37             @asahi-linux                               
kernel-modules.aarch64                             6.2.0-100.asahi6.1.fc37              @asahi-linux                               
kernel-modules.aarch64                             6.2.0-100.asahi10.1.fc37             @asahi-linux                               
kernel-modules.aarch64                             6.2.0-100.asahi11.1.fc37             @asahi-linux                               
kernel-modules-core.aarch64                        6.2.0-100.asahi6.1.fc37              @asahi-linux                               
kernel-modules-core.aarch64                        6.2.0-100.asahi10.1.fc37             @asahi-linux                               
kernel-modules-core.aarch64                        6.2.0-100.asahi11.1.fc37             @asahi-linux                               
kernel-srpm-macros.noarch                          1.0-15.fc37                          @fedora                                    
kernel-tools.aarch64                               6.2.6-200.fc37                       @updates                                   
kernel-tools-libs.aarch64                          6.2.6-200.fc37                       @updates                                   
barrett@canopy ~> 

Is there any advice you can give on fixing this issue?

Thanks,
Barrett

While compiling and testing a different kernel, my kernel went into an unbootable state. I thought this was ok but grub does not recognise or allow my keyboard to change the kernel selected, it ignores my keyboard.

Very unofficial (but very true) news, fedora is likely moving away from grub to something like sd-boot. Wonder is it worth switching to sd-boot here?

Did a fresh install this morning of minimal, connected to wifi and ran dnf update and rebooted. Reinstalled again just to make sure it wasn't a one off, and it repeated. It tries to drop me into emergency mode but the keyboard doesn't work to try anything.

https://asahilinux.org/2022/12/gpu-drivers-now-in-asahi-linux/

Just FYI :). Thank you!

When launching Alacritty, this error gets shown

warning: queue 0xaaaad961a830 destroyed while proxies still attached:
  xdg_wm_base@19 still attached
  wl_surface@18 still attached
  wl_output@13 still attached
  wl_seat@12 still attached
  xdg_activation_v1@11 still attached
  zwp_text_input_manager_v3@10 still attached
  zwp_pointer_constraints_v1@9 still attached
  zwp_relative_pointer_manager_v1@8 still attached
  zxdg_decoration_manager_v1@7 still attached
  wl_subcompositor@6 still attached
  wl_compositor@5 still attached
  wl_shm@4 still attached
  wl_registry@2 still attached
Error: There was an error initializing the shaders: Failed compiling shader: 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, 1.00 ES, and 3.00 ES

and when launching Firefox, this error gets shown multiple times before it finally launches

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: DRM render node not clearly detectable. Falling back to using the only one that was found.

Additionally, videos in Firefox are extremely laggy and uses a ton of ram.

It seems like these apps are unable to use the GPU drivers in Asahi Fedora, but they work perfectly in the official Asahi ALARM image.

I'm using Sway, and the only thing that I've really done to my Fedora install is follow this to transition to the Asahi Fedora Remix.

The script seems to create / partition too small - just 1GB:
Device Start End Sectors Size Type
/dev/nvme0n1p1 6 128005 128000 500M Apple Silicon boot
/dev/nvme0n1p2 128006 19659269 19531264 74.5G Apple APFS
/dev/nvme0n1p3 19659270 20269573 610304 2.3G Apple APFS
/dev/nvme0n1p4 20269574 20397573 128000 500M EFI System
/dev/nvme0n1p5 20397574 20659717 262144 1G Linux filesystem
/dev/nvme0n1p6 20659718 120827397 100167680 382.1G Linux filesystem
/dev/nvme0n1p7 120827419 122138127 1310709 5G Apple Silicon recovery

Is there a way to fix it?

Fedora 37 release: Several packages have recently been added to the offical Fedora repo, which include:
asahi-fwextract asahi-scripts dracut-asahi m1n1 update-m1n1
So in order upgrade from Fedora 36 --> Fedora 37 please do the following

dnf remove uboot-asahi
dnf install dracut-asahi
dnf upgrade
# just to be safe as the latest kernel has selinux enabled and it hasn't been fully tested out yet
sed -i s/^SELINUX=.*$/SELINUX=permissive/ /etc/selinux/config
dnf install dnf-plugin-system-upgrade
dnf system-upgrade download --releasever=37
dnf system-upgrade reboot

An official Fedora release seems imminent. When that happens, this project will no longer be needed. When an official release happens, it'll be super-easy to transition over (I'll provide instructions of how to do that). At this point, all but a couple packages are official Fedora packages anyway. But....until that happens I'll continue to work on this project.

Providing Silverblue images would be useful for quick testing and rollbacks, as it's a simple rpm-ostree rebase to use a different Fedora deployment.

If Silverblue itself can be installed (and get to a TTY), then it should be possible to make a Docker workflow that generates an OCI image that rpm-ostree (experimental) can use to rebase to.

Hi, first of all - thanks so much for this project. I can't seem to get bluetooth to work, but it was added in the latest release. I've run sudo dnf upgrade and still can't get it. Is there an ETA on this?
Thanks

I am trying to build aircrack-ng's rtl8812au drivers here for a USB Wi-Fi antenna, but the typical Fedora method of installing kernel-devel doesn't work because some of the core packages of Asahi conflict with this package. Is there an alternative package that will provide what I need? Thank you!