Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 721668 - sys-boot/grub-2.04-r1: doesn't load firmware
Summary: sys-boot/grub-2.04-r1: doesn't load firmware
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-08 18:33 UTC by CaptainBlood
Modified: 2020-05-09 05:26 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description CaptainBlood 2020-05-08 18:33:59 UTC
Intel here.
-----------------------------------------------------------
Booting firmware unaware kernel motherboard firmware shows:
cat /proc/cpuinfo | grep code
microcode   : 0x39...	
--------------------------------------------
When booting firmware updated kernel here's:
cat /proc/cpuinfo | grep code
microcode   : 0xda...
--------------------------------------------------------------------------------
When booting with grub firmware aware configuration, signature turns to be from motherboard.
-----------------------------
ll /lib/firmware/intel-ucode/
total 104
-rw-r--r-- 1 root root 104448 mai    8 19:46 06-5e-03	
as one file is enough, the one working with firmware updated kernel.
-------------------------
ll /boot/early_ucode.cpio
-rw-r--r-- 1 root root 105472 mai    8 19:48 /boot/early_ucode.cpio	
slightly bigger than the previous for some reason.
------------------
cat /boot/grub.cfg
...
        echo    'Loading Linux 5.6.11-gentoo-test ...'
        linux   /boot/vmlinuz-5.6.11-gentoo-test root=/dev/sda1 ro  rootfstype=ext4 resume=/dev/sda5 quiet splash=silent,theme:livecd-2007.0 console=tty1 mitigations=off nosmt mds=full mitigations=auto
        echo    'Loading initial ramdisk ...'
        initrd  /boot/early_ucode.cpio
...
---------------------------
emerge --info sys-boot/grub
...
sys-boot/grub-2.04-r1::gentoo was built with the following:
USE="-device-mapper -doc -efiemu -fonts -libzfs -mount nls -sdl (-test) -themes -truetype" ABI_X86="(64)" GRUB_PLATFORMS="-coreboot -efi-32 -efi-64 -emu -ieee1275 -loongson -multiboot pc -qemu -qemu-mips -uboot -xen -xen-32 -xen-pvh"
CFLAGS=""
CXXFLAGS="-march=skylake -mtune=skylake -O2 -pipe"
FEATURES="sandbox news pid-sandbox parallel-fetch preserve-libs ipc-sandbox userfetch distlocks qa-unresolved-soname-deps ebuild-locks binpkg-logs merge-sync network-sandbox unmerge-logs assume-digests multilib-strict unknown-features-warn userpriv binpkg-docompress protect-owned strict usersandbox config-protect-if-modified fixlafiles sfperms usersync binpkg-dostrip split-elog unmerge-orphans"
LDFLAGS=""
...

Maybe I'm missing something, but I really can't see where it can be...

Thks 4 ur attention

Reproducible: Always
Comment 1 Tomáš Mózes 2020-05-09 05:26:44 UTC
What was the problem?