Solved V12.1 Custom kernel not recognized after successful build and install

[John Watson]

After copying and customizing the GENERIC kernel, I run:

cd /usr/src && nohup make buildkernel KERNCONF=GWKERNEL
make installkernel KERNCONF=GWKERNEL
shutdown -r now

After the reboot I run:

sysctl kern.conftxt | grep ident

and still get GENERIC kernel.

During build and install there are no error messages and I can't find any reference to the custom kernel in any log files.

I have performed this on other installs up to v11 and this is the first time it has failed.

Thanks for any input.

 

[Bobi B.]

Installing custom kernel is not going to make loader to use it. Search for kernel in loader.conf(5) or interrupt loader(8) to be able to tell which kernel to use: boot mykernel. Or you can try with nextboot(8).

 

[olli@]

After copying and customizing the GENERIC kernel, I run:

cd /usr/src && nohup make buildkernel KERNCONF=GWKERNEL
make installkernel KERNCONF=GWKERNEL
shutdown -r now

After the reboot I run:

sysctl kern.conftxt | grep ident

and still get GENERIC kernel.

During build and install there are no error messages and I can't find any reference to the custom kernel in any log files.

What does the ident line in your GWKERNEL file say? Did you forgot to change it from „ident GENERIC“ to „ident GWKERNEL“?
Also, check the timestamp of the /boot/kernel/kernel file. Is it about the time when you installed the new kernel? If not, then the new kernel was not installed correctly.
Finally, check sysctl kern.bootfile. Does it say /boot/kernel/kernel? If it doesn’t, check your /boot/loader.conf for settings related to selection of the kernel file for booting.

 

[John Watson]

Thanks. My new kernel file was missing the
ident GWKERNEL
Now it's working as expected.

 

[Mjölnir]

It's polite to set the thread solved: Click on the 1st post "..."->edit thread->prefix: solved