FYI updated yesterday and gnome x-org was freezing after restart about asahi-fedora-builder HOT 15 CLOSED

Thank you! You're doing a great job!

from asahi-fedora-builder.

from asahi-fedora-builder.

That's interesting. I can try installing GNOME later today and see if I can replicate that issue.
Does GNOME w/ wayland work better?

Can you control the screen brightness via the light command?
ie
light -s sysfs/backlight/apple-panel-bl -S 10

from asahi-fedora-builder.

[web@fedora ~]$ sudo light -s sysfs/backlight/apple-panel-bl -S 10
We couldn't find the specified device target at the path "sysfs/backlight/apple-panel-bl". Use -L to find one.

I'm using 6.2.0-0.rc3.asahi6.1.fc37.aarch64

from asahi-fedora-builder.

I should have asked this before, but which Apple silicon platform are you using?
And are you currently running 6.2.0-0.rc3.asahi6.1.fc37.aarch64 ?

from asahi-fedora-builder.

I'm on a MacBook Pro 16, CPU M1-Pro 6.2.0-0.rc3.asahi6.1.fc37.aarch64.

from asahi-fedora-builder.

Which version of m1n1 do you currently have installed?
You should be on version 1.2.4-1 as that's required for the latest kernel.

from asahi-fedora-builder.

It's in my repo
https://leifliddy.com/asahi-linux/37/aarch64/m1n1-1.2.4-1.fc37.aarch64.rpm

Although, it'll be in Fedora proper soon
https://bugzilla.redhat.com/show_bug.cgi?id=2164030

from asahi-fedora-builder.

Which version of m1n1 do you currently have installed?
You should be on version 1.2.4-1 as that's required for the latest kernel.

I am on this one, yes.

from asahi-fedora-builder.

Ok, can you run update-m1n1 and then verify boot.bin was actually updated

[root@fedora ~]# ll /boot/efi/m1n1/boot.bin
-rwxr-xr-x. 1 root root 2851445 Jan 24 16:22 /boot/efi/m1n1/boot.bin

and then reboot.

I just downgraded m1n1 to version m1n1-1.2.3-1 and confirmed that it breaks the screen brightness functionality.
I highly suspect that the issue you're experiencing is related to this.

from asahi-fedora-builder.

Everything works great now! Thank you! Interesting. I did the update like this, yesterday. I had to use sudo dnf update --best --allowerasing for m1n1 on account of the m1n1-tools-1.2.3-1.fc37.noarch

User           : Tudor Bărăscu <web>
Return-Code    : Success
Releasever     : 37
Command Line   : update --best --allowerasing
Comment        : 
Packages Altered:
    Upgrade  m1n1-1.2.4-1.fc37.aarch64      @asahi-linux
    Upgraded m1n1-1.2.3-1.fc37.aarch64      @@System
    Removed  m1n1-tools-1.2.3-1.fc37.noarch @@System

from asahi-fedora-builder.

damn....you know what I never uploaded the m1n1-tools package.
That's my fault, I'll upload it now.

from asahi-fedora-builder.

Ok, it's uploaded. Sorry about that.

from asahi-fedora-builder.

Thanks, same problem on Macbook Air M2 after update. Solve for me too with the following steps :

• Update m1n1 to m1n1.2.4-1 (or dnf remove m1n1, then dnf install m1n1, then dnf update --best--allowerasing)
• Install update-m1n1 (dnf install m1n1-update)
• Run update-m1n1 (needs root/sudo)
• reboot

Thank you very much for maintaining this project

from asahi-fedora-builder.

Thanks!
Once you've installed update-m1n1 -- it will automatically run whenever an rpm modifies any of the following directories. So it'll run automatically whenever you install a new kernel or update uboot (or m1n1 obviously)

[root@fedora ~]# rpm -q --filetriggers update-m1n1
transfiletriggerin scriptlet (using /bin/sh) -- /boot/dtb-, /usr/lib/m1n1, /usr/share/uboot/apple_m1
/usr/sbin/update-m1n1 || :

from asahi-fedora-builder.