Repository navigation
[Enhancement] Auto-detect NVIDIA 580xx users & enforce DKMS + mkinitcpio MODULES during omarchy-update #6260
Replies: 4 comments
|
Cross-link for full context: the exact repro + fix path (nvidia-580xx-dkms install + prep script + reboot) that solved the emergency-mode boot is in the original report here -> #4781 (and my earlier comment with logs).\nThis enhancement would have prevented the whole issue automatically. Happy to help test or PR the guardrail! |
|
prepare-omarchy-update-nvidia-safe.sh Field-tested helper script from this incident (shared in case useful for upstream design/testing):
What it does:
Scope/safety notes:
Observed result on this hardware:
|
|
Everytime there is kernel bump I dread the omarchy update because of this - and it looks I am not the only one. |
|
I just got dropped into emergency mode with Is there any way to fix this and recover my working Omarchy installation? Unfortunately, my latest snapshot also boots into emergency mode, lol Is there another recovery option besides booting from a live USB and doing a chroot repair? |
Uh oh!
There was an error while loading. Please reload this page.
Enhancement request
After surviving the 3.4.x kernel bump (see #4781), the root cause was crystal clear:
Proposed fix (tiny & fully Oma-friendly):
omarchy-update: if anynvidia-*-utilsis present, auto-runomarchy-pkg-install nvidia-*-dkms(or prompt).nvidia nvidia_modeset nvidia_uvm nvidia_drm) toMODULES=()in /etc/mkinitcpio.conf (with timestamped backup).limine-mkinitcpioafter any kernel change.Zero breaking changes, respects existing hooks (omarchy_hooks.conf), and eliminates the #1 NVIDIA Pascal complaint.
Hardware example: Intel i7-5930K, ASUS X99-E, NVIDIA GTX 1070 Ti (580xx), LUKS/Btrfs/Limine.
My fix path (worked perfectly):
omarchy-pkg-install nvidia-580xx-dkmslimine-mkinitcpioomarchy-updateHappy to open a PR with the exact diff if wanted. Cross-ref: #4781 #4192 #3954.
All reactions