#4 Port asahi-scripts to Fedora
Closed: Fixed a year ago by dcavalca. Opened 2 years ago by dcavalca.

https://github.com/AsahiLinux/asahi-scripts

Of these we need:
- update-vendor-firmware - can probably be packaged as-is and should just work
- update-m1n1 - I think this should be turn into an rpm transfiletrigger
- update-grub - probably not needed
- initcpio/install/asahi - port to dracut config override
- systemd-udev-trigger-early.service - I have no idea why they have this in the first place


Metadata Update from @ngompa:
- Issue tagged with: Development, Installation

2 years ago

Put up a review for this, with just update-vendor-firmware for now: https://bugzilla.redhat.com/show_bug.cgi?id=2068554

And also filed a request to have it enabled by default: https://bugzilla.redhat.com/show_bug.cgi?id=2068555

@dcavalca According to Hector Martin in #asahi-dev on OFTC (timestamps are in US/Eastern):

3/26/2022, 12:09:28 PM - marcan: Eighth_Doctor: the udev trigger thing is to make udev trigger the nvme driver, *then* the firmware pull script runs, *then* normal udev trigger runs and loads the broadcom wifi driver
3/26/2022, 12:10:01 PM - marcan: without that you either end up with firmware not working on first boot / being out of step, or the firmware pull script blocking on nvme that won't come until it's done
3/26/2022, 12:10:22 PM - marcan: if you build the nvme driver and all its dependencies into the kernel you don't need it, of course
3/26/2022, 12:10:28 PM - marcan: or if you explicitly modprobe it some other way
3/26/2022, 12:10:42 PM - marcan: but I wanted to prove to myself we can do module autoloading "properly"

Metadata Update from @ngompa:
- Issue assigned to dcavalca

2 years ago

Issue status updated to: Closed (was: Open)
Issue close_status updated to: Completed

2 years ago

Issue status updated to: Open (was: Closed)

2 years ago

This is pretty much done. Two items left:

we don't have the update-grub command in Fedora, as far as I know?

We don't, and we likely shouldn't need it, but we do need to either workaround the 30_uefi-firmware bug or fix it.

Ah excellent, then we don't need to worry there.

These are working fine now and we have everything we need.

Metadata Update from @dcavalca:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

Login to comment on this ticket.

Metadata
Boards 1
Development Status: Done