last update: I got microcode for an Intelprocessor.

[Hans-Jürgen Schild]

But in my computer is a AMD ryzen 7.
Since that point virtual box doesn't work.

If there is a new version of microcode please supply, but for AMD processor.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-release-upgrader-core 1:19.04.16.4
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu May 23 12:06:33 2019
InstallationDate: Installed on 2018-05-14 (373 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to disco on 2019-04-19 (34 days ago)
VarLogDistupgradeTermlog:

[Brian Murray (brian-murray)]

Do you happen to know why you have both the amd64-microcode and intel-microcode packages installed?

[Dimitri John Ledkov (xnox)]

That's normal and expected. The kernel depends on both, and all microcode
for both Intel and AMD are available in the initrd, and on boot the right
one is loaded.

Could you please check dmesg to see if microcode is getting loaded?

E.g. dmesg | grep microcode

On Thu, 23 May 2019, 21:00 Brian Murray, <email address hidden> wrote:

> Do you happen to know why you have both the amd64-microcode and intel-
> microcode packages installed?
>
> ** Package changed: ubuntu-release-upgrader (Ubuntu) => intel-microcode
> (Ubuntu)
>
> ** Changed in: intel-microcode (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are a member of Intel
> Team, which is subscribed to intel-microcode in Ubuntu.
> Matching subscriptions: intel-microcode
> https://bugs.launchpad.net/bugs/1830189
>
> Title:
> last update: I got microcode for an Intelprocessor.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1830189/+subscriptions
>

[Hans-Jürgen Schild (hjschild)]

See my enclosed screenshot.

Am 23.05.19 um 22:25 schrieb Dimitri John Ledkov:
> That's normal and expected. The kernel depends on both, and all microcode
> for both Intel and AMD are available in the initrd, and on boot the right
> one is loaded.
>
> Could you please check dmesg to see if microcode is getting loaded?
>
> E.g. dmesg | grep microcode
>
> On Thu, 23 May 2019, 21:00 Brian Murray, <email address hidden> wrote:
>
>> Do you happen to know why you have both the amd64-microcode and intel-
>> microcode packages installed?
>>
>> ** Package changed: ubuntu-release-upgrader (Ubuntu) => intel-microcode
>> (Ubuntu)
>>
>> ** Changed in: intel-microcode (Ubuntu)
>> Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are a member of Intel
>> Team, which is subscribed to intel-microcode in Ubuntu.
>> Matching subscriptions: intel-microcode
>> https://bugs.launchpad.net/bugs/1830189
>>
>> Title:
>> last update: I got microcode for an Intelprocessor.
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1830189/+subscriptions
>>
--

Liebe Grüße

Hans-Jürgen

Tel.: [phone]

mobil: 0174 20 40 270
Fax: [phone]

[Brian Murray (brian-murray)]

Rather than including a screenshot it'd be helpful if you were to include the whole output of the command Dimitri asked you to run. One way to do that would be to pipe it to xclip and then paste it, using middle mouse, into the bug report. So:

dmesg | grep microcode | xclip

[Hans-Jürgen Schild (hjschild)]

[ 0.806382] microcode: CPU0: patch_level=0x08001129
[ 0.806387] microcode: CPU1: patch_level=0x08001129
[ 0.806389] microcode: CPU2: patch_level=0x08001129
[ 0.806394] microcode: CPU3: patch_level=0x08001129
[ 0.806400] microcode: CPU4: patch_level=0x08001129
[ 0.806404] microcode: CPU5: patch_level=0x08001129
[ 0.806410] microcode: CPU6: patch_level=0x08001129
[ 0.806415] microcode: CPU7: patch_level=0x08001129
[ 0.806422] microcode: CPU8: patch_level=0x08001129
[ 0.806428] microcode: CPU9: patch_level=0x08001129
[ 0.806434] microcode: CPU10: patch_level=0x08001129
[ 0.806441] microcode: CPU11: patch_level=0x08001129
[ 0.806447] microcode: CPU12: patch_level=0x08001129
[ 0.806453] microcode: CPU13: patch_level=0x08001129
[ 0.806459] microcode: CPU14: patch_level=0x08001129
[ 0.806465] microcode: CPU15: patch_level=0x08001129
[ 0.806487] microcode: Microcode Update Driver: v2.2.

[Hans-Jürgen Schild (hjschild)]

I've just done it.

Am 24.05.19 um 23:06 schrieb Brian Murray:
> Rather than including a screenshot it'd be helpful if you were to
> include the whole output of the command Dimitri asked you to run. One
> way to do that would be to pipe it to xclip and then paste it, using
> middle mouse, into the bug report. So:
>
> dmesg | grep microcode | xclip
>
--

Liebe Grüße

Hans-Jürgen

Tel.: [phone]

mobil: 0174 20 40 270
Fax: [phone]

[Launchpad Janitor (janitor)]

[Expired for intel-microcode (Ubuntu) because there has been no activity for 60 days.]