Kernel panic amd-ucode

thanks for the reply
how to?.. add Manjaro initrd by the amd-ucode line

thanks for the reply
is there a way to fix this

Well, I fixed this after installing ubuntu along with Manjaro and Win10 (i knew it would happen) with simply using my Super Grub stick (Manjaro live stick will do as well) and boot into Manjaro. Issue

$ sudo grub-install
$ sudo update-grub

You will then be able to boot all OS's on your computer. Funny thing is, when I installed Ubuntu, it took over my Manjaro Grub Theme.

Edit: After you booted into your INSTALLED Manjaro, remove the stick before you run the grub commands. Otherwise there will be some things like booting a Mac Version. This is because it is supported by your boot stick.

Edit2: This is true at least for GPT partitioning.

Edit3: Yes, this happens to me too after updating ubuntu. This makes it more of a nuisance than win10 itself.


Awesome. I was having the issue after install Linux Mint. I have Win10 / Manjaro / Mint and I was having Mint bootloader popup and had to restart my computer so that it could see Manjaro. This fixed it.

To help with Win10 and Linux stuff, seperate drives do help which is how my setup is here.

This is because Mint is based on Ubuntu. There is just something with their boot process Manjaro does not do. For myself I call it "aggressive". @gohlip can surely tell us more about that. There is actually no need to run everything on seperate drives. In my box is actually no space for another drive (surface pro).

thanks for all the info.
removed amd-ucode ..will keep using ubuntu grub bootloader for now .
If system becomes unstable may be forced to use manjaro grub.

Au contraire, there is something that Manjaro (& Arch) does that others don't do.

And not because it has a newer version.

What ever. It's different.

For the heck of it, I installed amd-ucode in my intel-ucode enabled system,
Here's what I got in my initrd line of my grub.cfg

echo	'Loading initial ramdisk ...'
		initrd	/boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-4.19-x86_64.img

Boots fine.
But a devaju moment. From an old post.

I wonder when amd-ucode gets introduced, how is Arch and Manjaro going to handle this. Probably the same way.
initrd /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-4.55x86_64.img


1 Like

thanks for that .
reinstalled amd-ucode
added..... initrd /boot/amd-ucode.img /boot/initramfs-4.14-x86_64.img to grub.cfg
Don't know if amd-ucode is working properly..... but it boots ok

Check with

dmesg | grep microcode

dmesg | grep microcode
[ 0.620976] microcode: CPU0: patch_level=0x07030105
[ 0.620990] microcode: CPU1: patch_level=0x07030105
[ 0.621090] microcode: Microcode Update Driver: v2.2.

Did some reading, internet full of micrcode info.
still don't know if my system is patched properly,its beyond my pay grade
but computer runs great ,

➜  ~ dmesg | grep microcode
[    0.000000] microcode: microcode updated early to revision 0x20, date = 2018-04-10
[    0.875709] microcode: sig=0x306a9, pf=0x2, revision=0x20
[    0.875803] microcode: Microcode Update Driver: v2.2.

Wow, I understand nothing, too. :slight_smile:

I don't have amd processors anymore
and I think it is working because it does not have a message asking you to upgrade.
Though you do not have a "microcode updated early" message and I am not sure if it has been updated "early".
Perhaps @jonathon or others who have amd can confirm for you.


It is working fine. You have...

and you have intel.

1 Like


old AMD :wink: (2009)

~ >>> dmesg | grep microcode
[    1.284124] microcode: CPU0: patch_level=0x01000095
[    1.284131] microcode: CPU1: patch_level=0x01000095
[    1.284140] microcode: CPU2: patch_level=0x01000095
[    1.284148] microcode: CPU3: patch_level=0x01000095
[    1.284204] microcode: Microcode Update Driver: v2.2.

Okay, doesn't have "early" either, I see.
If in intel-ucode, we often say (here) the microcode are not updated "early".
And make the claim (untrue) that other distros do not update their microcodes "early".
I do not have amd cpu processors now, so I really cannot tell if that updates "early".
Hope we have more feedback from other amd (cpu) users.

Maybe amd users on other distros can see the output from these other distros.
Maybe they have "early" in their output? :rofl:

abc, you solution fixed a similar problem for me in another question. I wasn't aware of the issue with Ubuntu and GRUB. So thanks. A nice, simple fix.

BTW, consider editing the first command to: sudo grub-install /dev/sdx . That will safeguard against someone accidentally installing GRUB on a drive they didn't want to modify. :slight_smile:

It never occurred to me to run dmesg | grep microcode on the ubuntu partition.
it almost the same output.
Ubuntu. >$ dmesg | grep microcode
[ 1.794853] microcode: CPU0: patch_level=0x07030105
[ 1.794865] microcode: CPU1: patch_level=0x07030105
[ 1.794957] microcode: Microcode Update Driver: v2.01, Peter Oruba

Manjaro.>$ dmesg | grep microcode
[ 0.607806] microcode: CPU0: patch_level=0x07030105
[ 0.607824] microcode: CPU1: patch_level=0x07030105
[ 0.607919] microcode: Microcode Update Driver: v2.2.

So may be "early" on both distro's..I also read somewhere that its possible that there is no revision.
As you said "feedback from other amd (cpu) users." would be helpful.

1 Like

Yes, it certainly is. Thanks for the output from Ubuntu distro.
Yes, it is the same then.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by