Talk:Kernel/Gentoo Kernel Configuration Guide

Note
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (~~~~), and indent successive comments with colons (:). Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.

SATA is no longer under SCSI settings

Talk status

This discussion is done.

This guide is saying to enable SATA under the SCSI low-level drivers menu ... it is no longer there, and is in it's own menu in Device Drivers. -- Jessetaylor84 (talk) 08:42, 21 September 2014 (UTC)

Changed in a previous edit. --Grknight (talk) 14:19, 8 November 2018 (UTC)

some paragraph should be modified to a new contents using a latest template

Talk status

This discussion is done.

most of part, explaining to set a kernel configuration, are using a kernel template but little bit part is still using a "Code" template. so It's better to check again and update for buggy part. -- Darkcircle (talk) 11:47, 2 January 2015 (UTC)

Changed in a previous edit --Grknight (talk) 14:20, 8 November 2018 (UTC)

Enabling compression support for kmod

Talk status

This discussion is done.

I put a second box "Enabling compression support for kmod" and just double-labelled it as 116. I don't know the appropriate way of labeling new content in the middle of a section/document. Please advise. DavidC (talk) 17:43, 19 November 2017 (UTC)

DavidC You should just add your content and not worry about the translation markers. Don't add new ones or delete old ones. They are adjusted automatically. --Grknight (talk) 14:23, 8 November 2018 (UTC)

Firmware in kernel section is outdated

Talk status

This discussion is still ongoing.

The section Built-in vs modular has incorrect information regarding the support of in-kernel firmware blobs for recent versions of Linux. Specifically, the location of the options in the config has changed, and the CONFIG_FIRMWARE_IN_KERNEL option has been dropped completely. A more up-to-date example of this setup is shown at Linux firmware#Kernel, though it's also incorrect.

Relevant commit: firmware: Drop FIRMWARE_IN_KERNEL Kconfig option

Partusman (talk) 00:35, 1 September 2020 (UTC)

In the kernel box For kernels beginning with 4.18 I cannot find anything wrong. Just checked against 4.19.141

--Charles17 (talk) 06:08, 1 September 2020 (UTC)

I agree with Charles17 , it looks like the change doesn't remove support for built-in kernel firmware, it merely makes defining it more straightforward by placing the definition in one kconfig file (instead of many) and does rename the option to EXTRA_FIRMWARE. I believe this closes the case, but perhaps Charles can double check my work here. We can rename the option to the current name and perhaps make a reference to the older name in case certain systems are still running older kernels. --Maffblaster (talk) 16:28, 1 September 2020 (UTC)

In 4.19.141 the CONFIG_FIRMWARE_IN_KERNEL ( Include in-kernel firmware blobs in kernel binary ) has gone. I guess this is the reason why Linux_firmware#Kernel shows two kernel boxes, one before and one after that change.

I just replaced this article's kernel box with a link to the other article.

--Charles17 (talk) 18:32, 1 September 2020 (UTC)

GRUB Menu Auto-Selection may not advanced due to Lexical Misorder May Occur during Kernel Configuration

Talk status

This discussion is done.

I've also noticed that when adding additiona `vmlinuz` to the `/boot` directory, the naming convention found in `VERSION`, `LOCALVERSION`, and EXTRALOCALVERSION` all contribute to the final name of the `vmlinuz` being stored into the `/boot` directory.

If you insert a later lexical in the middle of this kernel version, then that kernel version will no longer come out on top as the floating default; in fact, it would stay stuck on the latest overall lexical ordering of `vmlinuz-*` naming convention.

Some examples are:

   /boot/vmlinuz-alpha-001    (first timestamp)
   /boot/vmlinuz-midway-550   (second timestamp)
   /boot/vmlinuz-zeta-999     (third timestamp)

And for the next kernel version, you inserted a new value in between 'a'(lpha) and 'z'(eta) such as:

   /boot/vmlinuz-no-longer-the-auto-selected-ones-but-the-latest

Next time you do `grub-mkconfig`, the last lexical will still be your auto-selected kernel ones (vmlinuz-zeta-999). -- Egberts (talk) 19:45, 3 August 2022 (UTC)