Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # Notes from Asahi Fedora Upgrade process
- - Instructions conflicting with documentation?
- Following
- sudo dnf system-upgrade download --release=42
- The system hung a small amount of time testing some offline transaction, which made me worry, but is all well and good. Following that, it then output a message similar to `install reboot with some dnf5... command`.
- That step isn't anywhere to be found in the upgrade docs at https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-performing-system-upgrade
- I ignored it, correct?
- - Reboots, and asahi bless.
- I got rebooted into mac os once before manually fixing it, should the
- sudo dnf system-upgrade reboot
- command integrate with `asashi-bless` to prevent that? On final reboot it could restore the configuration for booting prior to running the command.
- - Post upgrade tasks.
- I followed upgrade instructions at https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-resolving-post-upgrade-issues and I basically had to make educated guesses as to which tasks i should follow.
- - Specifically, 99% sure that the GRUB bootloader BIOS step isn't required for Asahi (on Apple hardware anyway).
- - Retired packages/ old packages/ duplicates / extras / autoremove
- I basically ran all of these and backed out from any command that looked like it might remove something asahi specific... wasn't a very comfortable thing to intuit.
- Especially when seeing a bunch of stuff in autoremove with version numbers reference .fc42...
- - Return of the notch.
- I had to once again fix my notch display by running:
- sudo grubby --args=apple_dcp.show_notch=1 --update-kernel=ALL
- And reboot to restore that kernel arg. Requiring an extra reboot to the update process. I even attempted to pre-empt this situation by running that command after the kernel had been installed before running the reboot command. But it didn't work. How can I persist this between kernel releases? I'd have thought `--update-kernel=ALL` would have taken care of it across all installed kernels, but based on needing to run that command after i'd booted the new kernel... guess not.
Advertisement
Add Comment
Please, Sign In to add comment