View previous topic :: View next topic |
Author |
Message |
pstickar n00b
Joined: 26 Nov 2006 Posts: 65 Location: Germany
|
Posted: Mon Oct 30, 2023 5:25 pm Post subject: Need help with genkernel (Microcode option for Intel) |
|
|
Hello,
I'm using genkernel to compile the kernel 6.6.0, intended to work on an Intel CPU, but I get the error message
Required kernel option 'CONFIG_MICROCODE_INTEL' which genkernel tried to set is missing!
The config files and output are below, but let me say a few words of my research on this problem.
It looks like that genkernel runs "make menuconfig" (as indicated in genkernel.conf), then successfully adds the line CONFIG_MICROCODE_INTEL=y, then runs "make oldconfig" again, and from that point onwards the newly added line is missing. In order to prove that, I edited the file "/usr/share/genkernel/gen_configkernel.sh", where I added a grep line "grep MICROCODE /usr/src/linux/.config" before and after the final "make oldconfig" and verified that the newly added line is there before, but not after. The line "CONFIG_MICROCODE=y" remains.
I suspect I'm doing something wrong, but I cannot find the error.
Thank you very much in advance!
Kind regards,
Pablo
-----------------------------------------------------------------------------------
My coomand line is "genkernel all && emerge @module-rebuild".
The output I get is:
Code: |
* Gentoo Linux Genkernel; Version 4.3.8
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: all
* Working with Linux kernel 6.6.0-gentoo for x86_64
* Using kernel config file '/usr/share/genkernel/arch/x86_64/generated-config' ...
*
* Note: The version above is subject to change (depends on config and status of kernel sources).
* kernel: >> Initializing ...
* >> Running 'make clean' ...
* >> --no-mrproper is set; Skipping 'make mrproper' ...
* >> Will ignore kernel config from '/usr/share/genkernel/arch/x86_64/generated-config'
* in favor of already existing but different kernel config
* found in '/usr/src/linux/.config' ...
* >> Running 'make oldconfig' ...
* >> Invoking menuconfig ...
* >> Re-running 'make oldconfig' due to changed kernel options ...
* ERROR: Something went wrong: Required kernel option 'CONFIG_MICROCODE_INTEL' which genkernel tried to set is missing!
* Please consult '/var/log/genkernel.log' for more information and any
* errors that were reported above.
*
* Report any genkernel bugs to bugs.gentoo.org and
* assign your bug to genkernel@gentoo.org. Please include
* as much information as you can in your bug report; attaching
* '/var/log/genkernel.log' so that your issue can be dealt with effectively.
*
* Please do *not* report kernel compilation failures as genkernel bugs!
*
|
The final part of the log file is:
Code: |
...
#
# configuration written to .config
#
* >> Invoking menuconfig ...
COMMAND: nice -n10 make -j9 -s -j1 ARCH='x86' AS='x86_64-pc-linux-gnu-as' AR='x86_64-pc-linux-gnu-ar' CC='x86_64-pc-linux-gnu-gcc' LD='x86_64-pc-linux-gnu-ld' NM='x86_64-pc-linux-gnu-nm' OBJCOPY='x86_64-p
* >> Ensure that required kernel options for genkernel's initramfs usage are set ...
* - Option 'CONFIG_BLK_DEV_INITRD=y' already set in '/usr/src/linux/.config'; Skipping ...
* - Option 'CONFIG_MMU=y' already set in '/usr/src/linux/.config'; Skipping ...
* - Option 'CONFIG_SHMEM=y' already set in '/usr/src/linux/.config'; Skipping ...
* - Option 'CONFIG_TMPFS=y' already set in '/usr/src/linux/.config'; Skipping ...
* - Option 'CONFIG_TTY=y' already set in '/usr/src/linux/.config'; Skipping ...
* - Option 'CONFIG_UNIX98_PTYS=y' already set in '/usr/src/linux/.config'; Skipping ...
* Determining 'BEST' compression method for initramfs using kernel config '/usr/src/linux/.config' ...
* Checking if we can use 'XZ' compression ...
* Will use 'XZ' compression -- all requirements are met!
* - Option 'CONFIG_RD_XZ=y' already set in '/usr/src/linux/.config'; Skipping ...
* >> Ensure that CONFIG_LOCALVERSION is set ...
* - Option 'CONFIG_LOCALVERSION="-x86_64"' already set in '/usr/src/linux/.config'; Skipping ...
* >> Ensure that required kernel options for early microcode loading support are set ...
* - Option 'CONFIG_MICROCODE=y' already set in '/usr/src/linux/.config'; Skipping ...
* - Adding option 'CONFIG_MICROCODE_INTEL' with value 'y' to '/usr/src/linux/.config'...
* >> Re-running 'make oldconfig' due to changed kernel options ...
COMMAND: nice -n10 make -j9 ARCH='x86' AS='x86_64-pc-linux-gnu-as' AR='x86_64-pc-linux-gnu-ar' CC='x86_64-pc-linux-gnu-gcc' LD='x86_64-pc-linux-gnu-ld' NM='x86_64-pc-linux-gnu-nm' OBJCOPY='x86_64-pc-linux
#
# configuration written to .config
#
* >> Checking if required kernel options are still present ...
* - 'CONFIG_TMPFS' is set to 'y'
* - 'CONFIG_TTY' is set to 'y'
* - 'CONFIG_UNIX98_PTYS' is set to 'y'
* - 'CONFIG_MICROCODE' is set to 'y'
* ERROR: Something went wrong: Required kernel option 'CONFIG_MICROCODE_INTEL' which genkernel tried to set is missing!
* Please consult '/var/log/genkernel.log' for more information and any
* errors that were reported above.
*
...
|
My genkernel.conf is
Code: | # Configuration file for genkernel
# This file is sourced by genkernel at startup and determines which options
# we will be using to compile our kernel. The order of precidence is simple,
# with the internal settings being least important, configuration file
# settings next, and command line options being most important.
# =========COMMON COMMAND LINE OPTION DEFAULTS=========
# Install to $BOOTDIR
#INSTALL="yes"
# Run 'make oldconfig' before compiling this kernel
#OLDCONFIG="yes"
# Run 'make menuconfig' before compiling this kernel
MENUCONFIG="yes"
# Run 'make gconfig' before compiling this kernel
#GCONFIG="no"
# Run 'make nconfig' (ncurses 'menuconfig') before compiling this kernel
#NCONFIG="no"
# Run 'make xconfig' before compiling this kernel
#XCONFIG="no"
# Run 'make mrproper' before compiling this kernel
MRPROPER="no"
# Run 'make clean' before compiling this kernel
# Only needed if MRPROPER is set to NO because
# MRPROPER implies 'make clean'.
CLEAN="yes"
# Mount BOOTDIR automatically if it isn't mounted
#MOUNTBOOT="yes"
# Make symlinks in BOOTDIR automatically
#SYMLINK="no"
# Save the new configuration in /etc/kernels upon
# successful compilation
#SAVE_CONFIG="yes"
# Enable color output in genkernel
NOCOLOR="false"
# Clear build cache dir on gernkernel start
#CLEAR_CACHEDIR="no"
# Clear all tmp files and caches after genkernel has run
#POSTCLEAR="no"
# Check for x MB free disk space in BOOTDIR
#CHECK_FREE_DISK_SPACE_BOOTDIR=0
# Check for x MB free disk space in kernel outputdir
#CHECK_FREE_DISK_SPACE_KERNELOUTPUTDIR=0
# Genkernel uses an independent configuration for MAKEOPTS, and does not source
# /etc/portage/make.conf . You can override the default setting by uncommenting
# and tweaking the following line. Default setting is set up by
# ${GK_SHARE}/${ARCH_OVERRIDE}/config.sh . The recommended value for -j
# argument is: <number of processors>*<number of cores per processor>+1
#MAKEOPTS="$(portageq envvar MAKEOPTS)"
# Run the kernel make at the following NICE level
#NICE=10
# Add bcache support
#BCACHE="no"
# Add LVM support
#LVM="no"
# Add LUKS support
#LUKS="no"
# Add GnuPG support
#GPG="no"
# Add keyctl support for loading LUKS passphrase into a keyring
#KEYCTL="no"
# Add in early microcode support: this sets the kernel options for early microcode loading
# Possible values: empty/"no", "all", "intel", "amd"
MICROCODE="intel"
# Include early microcode in generated initramfs.
# Only needed if system cannot load multiple initramfs.
# NOTE: >=sys-boot/grub-2 will detect and auto-load {amd,intel}-uc.img file
# provided by sys-firmware/intel-microcode[initramfs] or
# sys-kernel/linux-firmware[initramfs].
#MICROCODE_INITRAMFS="no"
# Add NFS support
#NFS="no"
# Add DMRAID support
#DMRAID="no"
# Add SSH support
#SSH="no"
# Add b2sum support
#B2SUM="no"
# Include busybox in the initramfs. If included, busybox is rebuilt
# if the cached copy is out of date.
#BUSYBOX="yes"
# Add MDRAID support
#MDADM="no"
# Specify a custom mdadm.conf.
# By default the initramfs will be built *without* an mdadm.conf and will auto-detect
# arrays during bootup. Usually, this should not be needed.
#MDADM_CONFIG="/etc/mdadm.conf"
# Add Multipath support
#MULTIPATH="no"
# Add iSCSI support
#ISCSI="no"
# Add e2fsprogs support
#E2FSPROGS="no"
# Include support for unionfs
#UNIONFS="no"
# Include support for zfs volume management. If unset, genkernel will attempt
# to autodetect and enable this when rootfs is on zfs.
#ZFS="no"
# Add BTRFS support
#BTRFS="no"
# Add xfsprogs support
#XFSPROGS="no"
# Install firmware onto root filesystem
# Will conflict with sys-kernel/linux-firmware package
#FIRMWARE_INSTALL="no"
# Include full contents of FIRMWARE_DIR
# (if FIRMWARE option below is set to YES).
#ALLFIRMWARE="no"
# Add firmware(s) to initramfs required by copied modules
FIRMWARE="yes"
# Specify directory to pull from
FIRMWARE_DIR="/lib/firmware"
# Specify a comma-separated list of firmware files or directories to include,
# relative to FIRMWARE_DIR (if FIRMWARE option above is set to YES
# and ALLFIRMWARE is set to NO).
FIRMWARE_FILES=""
# Add new kernel to grub
# Possible values: empty/"no", "grub", "grub2"
#BOOTLOADER="no"
# Use sandbox when building initramfs
#SANDBOX="yes"
# Embed and set font early on boot
# Possible values: empty/"none", "current", <PSF file>
#BOOTFONT="none"
# Add boot splash using splashutils
#SPLASH="no"
# Use this splash theme. If commented out - the "default" name theme is used.
# Also, SPLASH="yes" needs to be enabled for this one to work.
# This supersedes the "SPLASH_THEME" option in '/etc/conf.d/splash'.
#SPLASH_THEME="gentoo"
# Includes or excludes Plymouth from the initramfs. If "splash" is
# passed at boot, Plymouth will be activated.
#PLYMOUTH="no"
# Embeds the given plymouth theme in the initramfs.
#PLYMOUTH_THEME="text"
# Run "emerge @module-rebuild" automatically when possible and necessary
# after kernel and modules have been compiled
#MODULEREBUILD="yes"
# Run the specified command in the current environment after the kernel and
# modules have been compiled, useful to rebuild external kernel module
# (see MODULEREBUILD above) or installing additional
# files (use 'copy_image_with_preserve dtb path/to/dtb dtb <kernelname>')
#CMD_CALLBACK=""
# =========KEYMAP SETTINGS=========
#
# Force keymap selection at boot
#DOKEYMAPAUTO="no"
# Enables keymap selection support
#KEYMAP="yes"
# =========LOW LEVEL COMPILE SETTINGS=========
#
# Assembler to use for the kernel. See also the --kernel-as command line
# option.
#KERNEL_AS="as"
# Archiver to use for the kernel. See also the --kernel-ar command line
# option.
#KERNEL_AR="ar"
# Compiler to use for the kernel (e.g. distcc). See also the --kernel-cc
# command line option.
#KERNEL_CC="gcc"
# Linker to use for the kernel. See also the --kernel-ld command line option.
#KERNEL_LD="ld"
# NM utility to use for the kernel. See also the --kernel-nm command line option.
#KERNEL_NM="nm"
# GNU Make to use for kernel. See also the --kernel-make command line option.
#KERNEL_MAKE="make"
# objcopy utility to use for the kernel. See also the --kernel-objcopy command
# line option.
#KERNEL_OBJCOPY="objcopy"
# objdump utility to use for the kernel. See also the --kernel-objdump command
# line option.
#KERNEL_OBJDUMP="objdump"
# ranlib utility to use for the kernel. See also the --kernel-ranlib command
# line option.
#KERNEL_RANLIB="ranlib"
# readelf utility to use for the kernel. See also the --kernel-readelf command
# line option.
#KERNEL_READELF="readelf"
# strip utility to use for the kernel. See also the --kernel-strip command line
# option.
#KERNEL_STRIP="strip"
# Assembler to use for the utilities. See also the --utils-as command line
# option.
#UTILS_AS="as"
# Archiver to use for the utilities. See also the --utils-ar command line
# option.
#UTILS_AR="ar"
# C Compiler to use for the utilities (e.g. distcc). See also the --utils-cc
# command line option.
#UTILS_CC="gcc"
# C++ Compiler to use for the utilities (e.g. distcc). See also the --utils-cxx
# command line option.
#UTILS_CXX="g++"
# Linker to use for the utilities. See also the --utils-ld command line
# option.
#UTILS_LD="ld"
# NM utility to use for the utilities. See also the --utils-nm command line option.
#UTILS_NM="nm"
# GNU Make to use for the utilities. See also the --utils-make command line
# option.
#UTILS_MAKE="make"
# Target triple (i.e. aarch64-linux-gnu) to build for. If you do not
# cross-compile, leave blank for auto detection.
#CROSS_COMPILE=""
# Target triple (i.e. aarch64-linux-gnu) to build kernel for. Utilities will be
# built for the native target, not this target. If you do not cross-compile,
# leave blank.
#KERNEL_CROSS_COMPILE=""
# Override default make target (bzImage). See also the --kernel-target
# command line option. Useful to build a uImage on arm.
#KERNEL_MAKE_DIRECTIVE_OVERRIDE="fooImage"
# Override default kernel binary path. See also the --kernel-binary
# command line option. Useful to install a uImage on arm.
#KERNEL_BINARY_OVERRIDE="arch/foo/boot/bar"
# =========GENKERNEL LOCATION CONFIGURATION=========
#
# Variables:
# %%ARCH%% - Final determined architecture
# %%CACHE%% - Final determined cache location
# Set genkernel's temporary work directory
#TMPDIR="/var/tmp/genkernel"
# Set the boot directory, default is /boot
#BOOTDIR="/boot"
# Default share directory location
GK_SHARE="${GK_SHARE:-/usr/share/genkernel}"
# Location of the default cache
CACHE_DIR="/var/cache/genkernel"
# Location of DISTDIR, where our source tarballs are stored
DISTDIR="${GK_SHARE}/distfiles"
# Log output file
LOGFILE="/var/log/genkernel.log"
# Debug Level
LOGLEVEL=1
# =========COMPILED UTILS CONFIGURATION=========
#
# Default location of kernel source
DEFAULT_KERNEL_SOURCE="/usr/src/linux"
# Default kernel config (only use to override using
# arch/%%ARCH%%/kernel-config-${VER}.${PAT} !)
#DEFAULT_KERNEL_CONFIG="${GK_SHARE}/arch/%%ARCH%%/kernel-config"
# Specifies a user created busybox config
#BUSYBOX_CONFIG="/path/to/file"
# NOTE: Since genkernel 3.4.41 the version of
# busybox, lvm, mdadm, ... have been moved to
# /usr/share/genkernel/defaults/software.sh in order to
# reduce the merging you have to do during etc-update.
# You can still override these settings in here.
# =========MISC KERNEL CONFIGURATION=========
#
# Set kernel filename which will be used when kernel will be installed
# into BOOTDIR. See man page to learn more about available placeholders.
#KERNEL_FILENAME="vmlinuz-%%KV%%"
# Set kernel symlink name which will be used when kernel will be installed
# into BOOTDIR and SYMLINK option is enabled
#KERNEL_SYMLINK_NAME="kernel"
# This option will set kernel option CONFIG_LOCALVERSION.
# Use special value "UNSET" to unset already set CONFIG_LOCALVERSION.
#KERNEL_LOCALVERSION="-%%ARCH%%"
# This option is only valid if kerncache is
# defined. If there is a valid kerncache no checks
# will be made against a kernel source tree.
#KERNEL_SOURCES="yes"
# Build a static (monolithic kernel)
#BUILD_STATIC="no"
# Make and install kernelz image (PowerPC)
#GENZIMAGE="no"
# Archive file created using tar containing kernel binary, content
# of /lib/modules and the kernel config.
# NOTE: Archive is created before the callbacks are run!
#KERNCACHE="/path/to/file.tar.xz"
# Prefix to kernel module destination, modules
# will be installed in <prefix>/lib/modules
#KERNEL_MODULES_PREFIX=""
# =========MISC INITRAMFS CONFIGURATION=========
#
# Set initramfs filename which will be used when initramfs will be
# installed into BOOTDIR. See man page to learn more about available
# placeholders.
#INITRAMFS_FILENAME="initramfs-%%KV%%.img"
# Set initramfs symlink name which will be used when initramfs will be
# installed into BOOTDIR and SYMLINK option is enabled
#INITRAMFS_SYMLINK_NAME="initramfs"
# Copy all compiled kernel modules to the initramfs
#ALLRAMDISKMODULES="no"
# Copy selected modules to the initramfs based on arch-specific modules_load file
#RAMDISKMODULES="yes"
# Archive file created using tar containing kernel and initramfs.
# NOTE: No modules outside of the initramfs will be included!
#MINKERNPACKAGE="/path/to/file.tar.xz"
# Add additional modules to the initramfs using the module groups defined
# in /usr/share/genkernel/defaults/modules_load (see this file for
# more details). This would be used if, for example, you
# required an additional crypto module or network device at boot
# time and did not want to statically compile these in the kernel.
# Options take the form AMODULES_{group} where {group} is one of
# the groups in modules_load (which are in the form MODULES_{group}).
# Use this with caution.
#AMODULES_group="module-to-include another-module"
# Override the default modules in the initramfs, for a given group, as defined by
# /usr/share/genkernel/defaults/modules_load and the per-arch modules_load
# files. You PROBABLY want to use AMODULES_* above, and NOT MODULES_* here.
# If you use MODULES_* here, the default and per-arch modules will NOT be used.
#MODULES_group1="some-module"
#MODULES_group2="" # Load no modules for this group
# Override the default used linuxrc script.
#LINUXRC="/path/to/custom/linuxrc"
# Archive file created using tar containing modules after
# the callbacks have run
#MODULESPACKAGE="/path/to/file.tar.xz"
# Directory structure to include in the initramfs,
# only available on >=2.6 kernels
#INITRAMFS_OVERLAY=""
# Build the generated initramfs into the kernel instead of
# keeping it as a separate file
#INTEGRATED_INITRAMFS="no"
# Compress generated initramfs
#COMPRESS_INITRD="yes"
# Types of compression: best, xz, lzma, bzip2, gzip, lzop, lz4, zstd, fastest
# "best" selects the best available compression method
# "fastest" selects the fastest available compression method
#COMPRESS_INITRD_TYPE="best"
# wrap initramfs using mkimage for u-boot bootloader
# WRAP_INITRD=no
# Create a self-contained env in the initramfs
#NETBOOT="no"
# =========MISC BOOT CONFIGURATION=========
#
# Specify a default for real_root=
#REAL_ROOT="/dev/one/two/gentoo" |
_________________ p. |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 23062
|
|
Back to top |
|
|
pstickar n00b
Joined: 26 Nov 2006 Posts: 65 Location: Germany
|
Posted: Mon Oct 30, 2023 9:10 pm Post subject: |
|
|
Thank you for the prompt answer.
I modified genkernel.conf not to invoke "make oldconfig", and it works.
Kind regards,
Pablo _________________ p. |
|
Back to top |
|
|
gt_amd64 Apprentice
Joined: 02 Dec 2004 Posts: 181
|
Posted: Wed Nov 01, 2023 5:47 pm Post subject: |
|
|
Yes, genkernel needs an update.
However, you can use the --no-microcode option to fix this issue:
Code: |
genkernel --no-microcode --install all
or
genkernel --no-microcode --menuconfig all
|
|
|
Back to top |
|
|
sMueggli Guru
Joined: 03 Sep 2022 Posts: 534
|
Posted: Thu Nov 02, 2023 10:12 am Post subject: |
|
|
gt_amd64 wrote: | However, you can use the --no-microcode option to fix this issue:
|
Are you sure, that this option is fixing the issue? Or do you assume that this option is fixing the issue?
From "man 8 genkernel":
Code: | --microcode[=<all|amd|intel>]
Adds early microcode loading support for all, only AMD or Intel processors to kernel
configuration.
--no-microcode
Do not add early microcode loading support to kernel configuration. |
As far as I understand it, the first option is enabling early microcode loading support. But with the kernel 6.6 the way changed, so that genkernel is failing. I assume the goal is to have early microcode loading support enabled. |
|
Back to top |
|
|
Gentoopc Guru
Joined: 25 Dec 2017 Posts: 406
|
Posted: Thu Nov 02, 2023 10:57 am Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
pstickar wrote: | Hello,
I'm using genkernel to compile the kernel 6.6.0, intended to work on an Intel CPU, but I get the error message
|
your god Linus Torvalds in the new kernel versions accepted the impossibility of building without including microcode. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5354 Location: Bavaria
|
Posted: Thu Nov 02, 2023 12:11 pm Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
Gentoopc wrote: | your god Linus Torvalds in the new kernel versions accepted the impossibility of building without including microcode. |
No ... and ... No.
It was not Linus who changed this option.
You can have a kernel without a microcode-update even with 6.6 ... just have / give (*) no microcode file when you "make" your kernel
*) means: You dont configure it == let it empty into CONFIG_EXTRA_FIRMWARE:
Code: | Device Drivers --->
Generic Driver Options --->
Firmware Loader --->
-*- Firmware loading facility
(intel-ucode/06-5e-03) Build named firmware blobs into the kernel binary |
=>
Code: | () Build named firmware blobs into the kernel binary |
(If you are using an initramfs then you simply dont emerge the microcode files; or delete them if you already have it)
The effect of the change is only: IF there is a microcode THEN use it (automatically) WITHOUT the additional need to CONFIGURE the usage (until 6.6 you must configure the usage explicit). |
|
Back to top |
|
|
Gentoopc Guru
Joined: 25 Dec 2017 Posts: 406
|
Posted: Thu Nov 02, 2023 2:30 pm Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
pietinger wrote: | Gentoopc wrote: | your god Linus Torvalds in the new kernel versions accepted the impossibility of building without including microcode. |
No ... and ... No.
It was not Linus who changed this option.
You can have a kernel without a microcode-update even with 6.6 ... just have / give (*) no microcode file when you "make" your kernel
*) means: You dont configure it == let it empty into CONFIG_EXTRA_FIRMWARE:
Code: | Device Drivers --->
Generic Driver Options --->
Firmware Loader --->
-*- Firmware loading facility
(intel-ucode/06-5e-03) Build named firmware blobs into the kernel binary |
=>
Code: | () Build named firmware blobs into the kernel binary |
(If you are using an initramfs then you simply dont emerge the microcode files; or delete them if you already have it)
The effect of the change is only: IF there is a microcode THEN use it (automatically) WITHOUT the additional need to CONFIGURE the usage (until 6.6 you must configure the usage explicit). |
you take the kernel from the resource kernel.org ? |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5354 Location: Bavaria
|
Posted: Thu Nov 02, 2023 3:19 pm Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
Gentoopc wrote: | you take the kernel from the resource kernel.org ? |
Sorry, I dont understand your question ? Maybe explain what you think. |
|
Back to top |
|
|
Gentoopc Guru
Joined: 25 Dec 2017 Posts: 406
|
Posted: Fri Nov 03, 2023 8:57 am Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
pietinger wrote: | Gentoopc wrote: | you take the kernel from the resource kernel.org ? |
Sorry, I dont understand your question ? Maybe explain what you think. |
Code: | emerge --ask sys-kernel/gentoo-sources |
will have a difference from downloaded from kernel.org |
|
Back to top |
|
|
logrusx Advocate
Joined: 22 Feb 2018 Posts: 2662
|
Posted: Fri Nov 03, 2023 12:12 pm Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
Gentoopc wrote: | pietinger wrote: | Gentoopc wrote: | you take the kernel from the resource kernel.org ? |
Sorry, I dont understand your question ? Maybe explain what you think. |
Code: | emerge --ask sys-kernel/gentoo-sources |
will have a difference from downloaded from kernel.org |
https://packages.gentoo.org/packages/sys-kernel/gentoo-sources:
Quote: | Full sources including the Gentoo patchset for the kernel tree |
For one thing, OpenRC is developed by Gentoo developers and AFAIK it includes some modifications to the kernel.
But this is off topic, so please don't steer the thread away.
Best Regards,
Georgi
Last edited by logrusx on Fri Nov 03, 2023 8:42 pm; edited 1 time in total |
|
Back to top |
|
|
Gentoopc Guru
Joined: 25 Dec 2017 Posts: 406
|
Posted: Fri Nov 03, 2023 12:57 pm Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
logrusx wrote: | some modifications to the kernel.
|
That's what I'm trying to say. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5354 Location: Bavaria
|
Posted: Fri Nov 03, 2023 1:30 pm Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
Gentoopc wrote: | logrusx wrote: | some modifications to the kernel.
|
That's what I'm trying to say. |
Yes of course our gentoo-sources has a few (very few) patches compared to the vanilla version, but these have no effect / influence on the topic: Microcode. All patches used affect other areas of the kernel. |
|
Back to top |
|
|
Gentoopc Guru
Joined: 25 Dec 2017 Posts: 406
|
Posted: Sat Nov 04, 2023 7:20 am Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
pietinger wrote: |
Yes of course our gentoo-sources has a few |
there could be such differences. therefore, it was worth clarifying. |
|
Back to top |
|
|
pietinger Moderator
Joined: 17 Oct 2006 Posts: 5354 Location: Bavaria
|
Posted: Sat Nov 04, 2023 12:03 pm Post subject: Re: Need help with genkernel (Microcode option for Intel) |
|
|
Gentoopc wrote: | there could be such differences. therefore, it was worth clarifying. |
Yes, now I've understood you. Yes, it's always worth trying to check for any differences. But in this case it doesn't matter whether you use gentoo-sources or vanilla-sources. |
|
Back to top |
|
|
|