Talk:Kernel/Upgrade

Note
This is a talk page. Please add newer comments below older ones, and sign your comments using four tildes (~~~~). When adding a new section (at the bottom of the page), please mark it as "open for discussion" by using {{talk|open}} so it will show up in the list of open discussions.

About 'make modules_prepare'

Talk status

This discussion is done.

Someone who knows better, please clarify: When exactly should make modules_prepare be run? Lee (talk) 13:28, 14 February 2015 (UTC)

I'm also a bit confused as to the importance of the make modules_prepare command. I see from /usr/src/linux/Makefile that the target results in calls to other targets but once getting into the rabbit hole, I also started finding myself a tad confused. — The preceding unsigned comment was added by Cajacaliente (talk • contribs) 13 May 2015‎

"Me too": While I think I know when make modules_prepare should be run, I'm not sure when emerge @module-rebuild should be run relative to the building of the kernel. The article is unnecessarily confusing about this, since the order it presents the information is:

configure the kernel (section 5)
make modules_prepare "may be" necessary before building the kernel (6th section, 1st "Important" box)
don't forget to reconfigure the bootloader and initramfs (6th section, 2nd "Important" box)
follow the manual configuration article to build the kernel (6th section, only line of regular text)
"If the kernel has not been built", make modules_prepare before installing external modules (8th section, 1st "root" command box)
emerge @module-rebuild to rebuild kernel-module packages (8th section, 2nd "root" command box)

It would help immensely if the concepts were introduced strictly in the order the commands should actually be run.

I assume the proper order is:

configure the kernel
make modules_prepare if any kernel modules have already been installed via emerge (or whatever)
build and install the kernel using make, make modules_install, and make install
emerge @module-rebuild if step #2 was necessary
configure the bootloader and initramfs
(double-check everything, including what modules are autoloaded, and) reboot

Can someone who knows for sure please clarify this? Also, I know step #4 won't actually "do anything" if the command is run when it is not necessary; is that also true of step #2? Finally, should Kernel/Configuration also mention make modules_prepare? - dcljr (talk) 08:36, 26 October 2017 (UTC)

make modules_prepare is unnecessary if you are building the kernel anyway. It is strictly for when you are wanting to build modules without building the rest of the kernel. --Grknight (talk) 14:30, 8 November 2018 (UTC)

Add genkernel instructions

Talk status

This discussion is done as of October 26, 2017.

I originally used genkernel to install the kernel. The important part to me is updating the new config from the old kernel. I think there should be a section on updating to the new kernel using genkernel.--Moaxcp (talk) 18:09, 21 May 2015 (UTC)

Good point. I'll add this to my list of thing to do. Also, don't forget to use a signature following your commend on discussion pages! :) --Maffblaster (talk) 17:59, 21 May 2015 (UTC)

Have you read the Genkernel? Does it contain the information you are looking for? --Maffblaster (talk) 18:30, 21 May 2015 (UTC)

Automated installation currently broken

Talk status

This discussion is still ongoing.

The file block under Automated builds currently does not work because the architecture that the linux kernel is expecting (x86) is different from the portage set $ARCH (amd64).

I got around that by adding `export ARCH=x86` before any of the make commands to fix this, but I'm not sure if that's the best solution --Mjsir911 (talk) 22:16, 13 June 2018 (UTC)