I have a new system that after the latest update will not reboot because is can't find the file intel-uucode or some such.
this is an AMD, for one thing and it has
The install/resue disk has an intel-ucode
I am lost here and never ran into anything like this. I've done updates with this machine in the recent past with no trouble rebooting.
FWIW
I needed to rerun grub-install after booting from the rescue disk and runing artix-chroot
I think it is a serious flaw in the package update, though. Somehow grub's configs were replaced with a dysfunctional form for AMD... and there are a lot of AMDs
FWIW - the pacman log
[2025-05-31T01:21:29-0400] [PACMAN] starting full system upgrade
[2025-06-04T00:54:37-0400] [PACMAN] starting full system upgrade
[2025-06-04T00:55:06-0400] [ALPM] upgraded libudev (257.5-2 -> 257.6-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded readline (8.2.013-1 -> 8.2.013-2)
[2025-06-04T00:55:06-0400] [ALPM] upgraded sqlite (3.49.2-1 -> 3.50.0-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded libarchive (3.8.0-1 -> 3.8.1-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded kbd (2.7.1-2 -> 2.8.0-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded udev (257.5-2 -> 257.6-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded libnghttp3 (1.10.0-1 -> 1.10.1-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded curl (8.13.0-2 -> 8.14.0-2)
[2025-06-04T00:55:06-0400] [ALPM] upgraded linux (6.14.6.artix1-1 -> 6.14.9.artix1-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded acpi_call (1.2.2-276 -> 1.2.2-279)
[2025-06-04T00:55:06-0400] [ALPM] upgraded bbswitch (0.8-744 -> 0.8-747)
[2025-06-04T00:55:06-0400] [ALPM] upgraded broadcom-wl (6.30.223.271-618 -> 6.30.223.271-621)
[2025-06-04T00:55:06-0400] [ALPM] upgraded esysusers (257.5-2 -> 257.6-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded etmpfiles (257.5-2 -> 257.6-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded iproute2 (6.14.0-1 -> 6.15.0-1)
[2025-06-04T00:55:06-0400] [ALPM] upgraded jq (1.7.1-2 -> 1.8.0-1)
[2025-06-04T00:55:07-0400] [ALPM] upgraded linux-headers (6.14.6.artix1-1 -> 6.14.9.artix1-1)
[2025-06-04T00:55:07-0400] [ALPM] upgraded qt6-base (6.9.0-1 -> 6.9.0-2)
[2025-06-04T00:55:07-0400] [ALPM] upgraded sdl3 (3.2.14-1 -> 3.2.16-1)
[2025-06-04T00:55:07-0400] [ALPM] upgraded tp_smapi (0.44-129 -> 0.44-132)
This was, I thought, a fairly high priority issue. A standard update shouldn't leave an AMD system in an unbootable state.
I think there's possibly more that was broken. I got a black screen after updating caused by SDDM failing to start properly. After disabling that and trying to start Plasma directly from startx I just get a black screen. Never had anything like this happen in 4 or so years of using this distro.
I just updated the system now and rebooted into black screen, only cursor showing without login screen. Had to startx directly to dwm. It seems like plasma not working
You may want to check if you have Mesa 25.1.1-3, which seems to break OpenGL. See https://forum.artixlinux.org/index.php/topic,8234.0.html
(Not sure if this is correct, but might be worth a shot)
With all due kindness... it has nothing to do with this.
Should have used the quoting tools the forum puts at my disposal. My response was to udidit, who seems to have a different issue (possibly Mesa-related, considering that was the date I had some similar issues with it and symptoms matched).
In your case, if it's really microcode-related, it could be useful to check what is loaded in your initramfs.
lsinitcpio --early <path_to_your_initramfs>And see if any microcodes are missing from it. (Or there are wrong paths, who knows)
Why highjack this thread? New topics are free as in beer.
I don't think I did, I saw udidit's post that seemed not to pertain the topic and directed them to a topic that (imho) was more fitting to their issue. In any case, we're now the ones veering off-topic here.
If you think the issue still needs addressing, we can get the devs here, if not I'd say the issue should be marked as solved.