Calamares oem user setup removes /boot/amd-ucode.img

Support
1

calamares oem end user setup removes /boot/amd-ucode.img due to uninstalling calamares-oem-modules.
System is unbootable after reboot.
It is solvable, but not by the end user after delivery of pc.
log:

14:58:18 [6]: virtual Calamares::JobResult Calamares::PythonJob::exec()
    Job file "/usr/lib/calamares/modules/cleanupoem/main.py" 
    .. Job description from __doc__ "cleanupoem" = "Cleanup OEM files" 
    .. Running ("rm", "/etc/sudoers.d/g_oem") 
    .. Running ("pacman", "-R", "--noconfirm", "calamares-oem-modules") 
    .. Finished. Exit code: 0 output:
 checking dependencies...

Packages (1) calamares-oem-modules-20220412-3

Total Removed Size:  0.01 MiB

:: Do you want to remove these packages? [Y/n] 
:: Processing package changes...
removing calamares-oem-modules...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
    .. Running ("pacman", "-R", "--noconfirm", "calamares-oem-kde-settings") 
    .. Finished. Exit code: 0 output:
 checking dependencies...

Packages (1) calamares-oem-kde-settings-20220413-1

Total Removed Size:  0.73 MiB

:: Do you want to remove these packages? [Y/n] 
:: Processing package changes...
removing calamares-oem-kde-settings...
14:58:19 [6]: virtual void Calamares::JobThread::run()
    Starting job "postcfg" ( 13 / 13 ) 
14:58:19 [6]: virtual Calamares::JobResult Calamares::PythonJob::exec()
    Job file "/usr/lib/calamares/modules/postcfg/main.py" 
    .. Job description from __doc__ "postcfg" = "Misc postinstall configurations" 
    .. Running ("pacman-key", "--init") 
    .. Running ("pacman-key", "--populate", "archlinux", "manjaro") 
    .. Finished. Exit code: 0 output:
 ==> Appending keys from archlinux.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
==> Appending keys from manjaro.gpg...
gpg: public key DB323392796CA067 is 3037 days newer than the signature
==> Locally signing trusted keys in keyring...
  -> Locally signed 2 keys.
==> Importing owner trust values...
==> Updating trust database...
gpg: next trustdb check due at 2024-01-21
    .. Running ("pacman-mirrors", "-f3") 
    .. Finished. Exit code: 0 output:

    .. Running ("pacman", "-Syy") 
    .. Finished. Exit code: 0 output:
 :: Synchronizing package databases...
 core downloading...
 extra downloading...
 community downloading...
 multilib downloading...
    .. Running ("pacman", "-R", "--noconfirm", "amd-ucode") 
    .. Finished. Exit code: 0 output:
 checking dependencies...

Packages (1) amd-ucode-20231211.f2e52a1c-1

Total Removed Size:  0.08 MiB

:: Do you want to remove these packages? [Y/n] 
:: Processing package changes...
removing amd-ucode...

Moderator edit: Fixed formatting

1 Like
2

Try to solve it in analogues procedure:

3

again, the computer is shipped to customer. Cannot ask the customer (mostley first time manjaro user) to do this actions.

4

If this is a computer shipped by an OEM builder/reseller; with a pre-installed OS (a modified Manjaro); then the way forward is clear. The unit should be returned to the OEM, and all related complaints and queries should be directed to them.

The Manjaro Forum can help many Manjaro users with their issues. However, when you were offered a possible solution, your response was somewhat nonsensical for someone asking for support.

If you don’t actually want support and only wish to share your annoyance over the situation, this might not be the right forum.

That is all. Cheers.

5

@UBUNTUSHOP is one of our vendors who creates OEM install medias for his devices he sells with Manjaro pre-installed. AMD ucode gets normally removed also on regular install medias on pure Intel based systems. A call of mkinitcpio after the removal within postinstall module should fix that normally.

I’ve to check what is off with usr/lib/calamares/modules/cleanupoem/main.py. as a workaround a modified file with commented out lines of ucode removal could fix it. That file needs to be placed to the desktop overlay to the same structure to be copied over after Calamares got installed.

6

I was just reporting a bug.

1 Like
7

I thought is was me - due to my customisation.

I have actually had a similar issue but not with the OEM installer - that the init modules included amd-ucode - although it was not there - being an intel system - and on two differetn machines.

I have the idea it is around the same time as the update to Calamares 3.3 - not sure though.

8

there are no lines with ucode.
Just the oem-modules removal

9

postcfg module is doing the removal

10

Does the profile ship with update-grub package? If not, that is the issue.

11

update-grub was not in official profiles. I added it to packages-desktop, build the oem iso and all is working now.
thanks