Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Kernel & Hardware
  • Search

[SOLVED] understanding changes with new install kernel

Kernel not recognizing your hardware? Problems with power management or PCMCIA? What hardware is compatible with Gentoo? See here. (Only for kernels supported by Gentoo.)
Post Reply
Advanced search
8 posts • Page 1 of 1
Author
Message
Dr_b_
n00b
n00b
Posts: 33
Joined: Sun Jan 18, 2004 10:39 pm
Contact:
Contact Dr_b_
Website

[SOLVED] understanding changes with new install kernel

  • Quote

Post by Dr_b_ » Sun Jan 28, 2024 6:57 am

After updating to the new installkernal, attempted to upgrade to 6.7.2

Running systemd, with grub

however, make install now installs files like this:

Code: Select all

/usr/src/linux # make install
  INSTALL /boot
Loading /usr/lib/kernel/install.conf…
layout=uki set via /usr/lib/kernel/install.conf
INITRD_GENERATOR (none) set via /usr/lib/kernel/install.conf.
UKI_GENERATOR (none) set via /usr/lib/kernel/install.conf.
Loaded /usr/lib/kernel/install.conf.
MACHINE_ID=e2aba522d37f4762bed099449a92f594 set via /etc/machine-id.
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Found container virtualization none.
/dev/nvme0n1p1: Partition has wrong PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b for XBOOTLDR partition.
Couldn't find an XBOOTLDR partition.
Failed to check file system type of "/efi": No such file or directory
Using EFI System Partition at /boot as $BOOT_ROOT.
Using entry token: e2aba522d37f4762bed099449a92f594
kernel version (6.7.2-gentoo) set via command line.
kernel image file (/usr/src/linux/arch/x86/boot/bzImage) set via command line.
Using ENTRY_DIR=/boot/e2aba522d37f4762bed099449a92f594/6.7.2-gentoo
so no longer do i get the typical :

Code: Select all

System.map-6.7.1-gentoo-r1*
config-6.7.1-gentoo-r1*
initramfs-6.7.1-gentoo-r1.img*
instead directories for loader, and the machine-id, within, which grub-cfg doesn't pick up

tried installkernel with and without systemd USE flag.

Is there a setting that can be made in installkernel config file to revert back to the default method

UPDATE: uninstalling kernelinstall, make install puts the files in the /boot dir correctly, run dracut as usual, creates correct initramfs, rename files vmlinuz and system map to match the current kernel version, and system boots ok
Last edited by Dr_b_ on Fri Feb 02, 2024 8:48 pm, edited 2 times in total.
Top
alamahant
Advocate
Advocate
Posts: 4032
Joined: Sat Mar 23, 2019 12:12 pm

  • Quote

Post by alamahant » Sun Jan 28, 2024 10:46 pm

If you run
man installkernel you get

Code: Select all

INSTALLKERNEL(8)                              System Manager’s Manual                              INSTALLKERNEL(8)

NAME
       installkernel - install a new kernel image

SYNOPSIS
       installkernel version zImage System.map [directory]

DESCRIPTION
       installkernel  installs  a  new kernel image onto the system from the Linux source tree. It is called by the
       Linux kernel makefiles when make install is invoked there.

       If systemd’s kernel-install is present on the system and the environment variable SYSTEMD_KERNEL_INSTALL  is
       set to 1, then it is called to install the kernel. The default setting for this environment variable is con‐
       trolled by the ebuild.  See the kernel-install manual for more information on how to configure it.

       If  the new kernel is an unified kernel image, it is installed into {directory}/vmlinuz-{version}.efi.  Oth‐
       erwise, the new kernel is installed into {directory}/vmlinuz-{version}.  If a symbolic link  {directory}/vm‐
       linuz  already  exists, it is refreshed by making a link from {directory}/vmlinuz to the new kernel, and the
       previously installed kernel is available as {directory}/vmlinuz.old.

       In addition to that, System.map passed on the command-line is installed using the same logic.  If the direc‐
       tory containing System.map contains .config file, it is also installed.  If the directory containing  zImage
       contains initrd file, it is also installed.

BUGS
       installkernel resides in /sbin only because the Linux kernel makefiles call it from there.  It should really
       be in /usr/sbin.  It isn’t needed to boot a system.

Try

Code: Select all

SYSTEMD_KERNEL_INSTALL=0
in /etc/env.d/99no-systemd-kernel-install
see also
https://wiki.gentoo.org/wiki/Installkernel
:)
Top
Nowa
Developer
Developer
User avatar
Posts: 522
Joined: Wed Jun 25, 2014 7:07 am
Location: Hilversum

Re: understanding changes with new install kernel

  • Quote

Post by Nowa » Mon Jan 29, 2024 11:13 am

Dr_b_ wrote:
tried installkernel with and without systemd USE flag.

Is there a setting that can be made in installkernel config file to revert back to the default method
Either:
- disable USE=systemd
- set SYSTEMD_KERNEL_INSTALL=0
- set layout=grub in /etc/kernel/install.conf

Note that emerge --config retains the environment from the initial emerge, so changing SYSTEMD_KERNEL_INSTALL (or disabling USE=systemd) has no effect on emerge --config. Unfortunately a full re-emerge is required.
OS: Gentoo 6.19.3-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400
Top
Dr_b_
n00b
n00b
Posts: 33
Joined: Sun Jan 18, 2004 10:39 pm
Contact:
Contact Dr_b_
Website

Re: understanding changes with new install kernel

  • Quote

Post by Dr_b_ » Fri Feb 02, 2024 1:58 am

Unfortunately a full re-emerge is required.

Do you mean of the entire system, or just installkernel?
Top
Nowa
Developer
Developer
User avatar
Posts: 522
Joined: Wed Jun 25, 2014 7:07 am
Location: Hilversum

Re: understanding changes with new install kernel

  • Quote

Post by Nowa » Fri Feb 02, 2024 7:13 am

Dr_b_ wrote:
Unfortunately a full re-emerge is required.

Do you mean of the entire system, or just installkernel?
Neither, a full re-emerge of gentoo-kernel is required, emerge --config retains the environment and is therefore not sufficient.

That being said, version 23 of installkernel should work better for you because it uses the "traditional" layout by default even when USE=systemd is enabled.
OS: Gentoo 6.19.3-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400
Top
Dr_b_
n00b
n00b
Posts: 33
Joined: Sun Jan 18, 2004 10:39 pm
Contact:
Contact Dr_b_
Website

Re: understanding changes with new install kernel

  • Quote

Post by Dr_b_ » Fri Feb 02, 2024 3:55 pm

Neither, a full re-emerge of gentoo-kernel is required, emerge --config retains the environment and is therefore not sufficient.
ohhh, i understand what you are saying now, using sys-kernel/gentoo-sources, and not gentoo kernel, the "emerge --config" and re-emerge didnt make sense


Code: Select all


# emerge -pv installkernel
[ebuild   R    ] sys-kernel/installkernel-19::gentoo  USE="-dracut -grub -systemd -uki -ukify" 0 KiB

# cat /etc/env.d/99no-systemd-kernel-install 
SYSTEMD_KERNEL_INSTALL=0

# cat /etc/kernel/install.conf
layout=grub
initrd_generator=
uki_generator=


make install:

  INSTALL /boot
Loading /etc/kernel/install.conf…
layout=grub set via /etc/kernel/install.conf
Loaded /etc/kernel/install.conf.
MACHINE_ID=e2aba522d37f4762bed099449a92f594 set via /etc/machine-id.
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Found container virtualization none.
/dev/nvme1n1p1: Partition has wrong PART_ENTRY_TYPE=c12a7328-f81f-11d2-ba4b-00a0c93ec93b for XBOOTLDR partition.
Couldn't find an XBOOTLDR partition.
Failed to check file system type of "/efi": No such file or directory
Using EFI System Partition at /boot as $BOOT_ROOT.
Using entry token: e2aba522d37f4762bed099449a92f594
kernel version (6.7.3-gentoo) set via command line.
kernel image file (/usr/src/linux/arch/x86/boot/bzImage) set via command line.
[size=18]Using ENTRY_DIR=/boot/e2aba522d37f4762bed099449a92f594/6.7.3-gentoo[/size]

Any suggestions?
Top
Nowa
Developer
Developer
User avatar
Posts: 522
Joined: Wed Jun 25, 2014 7:07 am
Location: Hilversum

  • Quote

Post by Nowa » Fri Feb 02, 2024 7:04 pm

It's a bit weird that the env var is not being picked up. Can you try:

Code: Select all

SYSTEMD_KERNEL_INSTALL=0 make install
Version 23+ of installkernel will use the more traditional layout even when USE=+systemd, so upgrading to this version should also fix your problem (and then you can remove /etc/kernel/install.conf, this should no longer be required).
OS: Gentoo 6.19.3-gentoo-dist, ~amd64, 23.0/desktop/plasma/systemd
MB: MSI Z370-A PRO
CPU: Intel Core i9-9900KS
GPU: Intel Arc A770 16GB & Intel UHD Graphics 630
SSD: Samsung 970 EVO Plus 2 TB
RAM: Crucial Ballistix 32GB DDR4-2400
Top
Dr_b_
n00b
n00b
Posts: 33
Joined: Sun Jan 18, 2004 10:39 pm
Contact:
Contact Dr_b_
Website

  • Quote

Post by Dr_b_ » Fri Feb 02, 2024 8:46 pm

# emerge -pv installkernel
[ebuild R ] sys-kernel/installkernel-24::gentoo USE="-dracut -grub -systemd -systemd-boot -uki -ukify" 0 KiB

# cat /etc/kernel/install.conf
layout=grub
initrd_generator=
uki_generator=

# cat /etc/env.d/99no-systemd-kernel-install
SYSTEMD_KERNEL_INSTALL=0

This works:

Code: Select all

 /usr/src/linux # SYSTEMD_KERNEL_INSTALL=0 make install
  INSTALL /boot
 /usr/src/linux # ll /boot
total 197140
drwxr-xr-x 4 root root    12288 Dec 31  1969 ./
drwxr-xr-x 1 root root      142 Sep 10 14:35 ../
drwxr-xr-x 5 root root     4096 Jan 27 23:44 EFI/
drwxr-xr-x 6 root root     4096 Feb  2 15:33 grub/
-rwxr-xr-x 1 root root 10585088 Feb  2 15:38 vmlinuz-6.7.3-gentoo*
-rwxr-xr-x 1 root root  4195419 Feb  2 15:38 System.map-6.7.3-gentoo*
-rwxr-xr-x 1 root root   138046 Feb  2 15:38 config-6.7.3-gentoo*
i also exited/reloged into the shell after updating installkernel, and its now picking up the var correctly. ver24 is working fine, thanks for the help!
Top
Post Reply

8 posts • Page 1 of 1

Return to “Kernel & Hardware”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic