In the past, a lot of people ask me how test a new kernel. This tip could help new arch tester.<\/p>\n
First, emerge the new sources ( 3.4.5 is just an example, replace it with your ${version} ): Now go to kernel directory, try to enable all modules and check if them compile: Might seem strange, but in the past, with allyesconfig, I found bug like this<\/a>, not reproducible with normal config.<\/p>\n The next step is clean the past build and make your custom kernel. Now try to boot with new kernel, and check if there are not bad message with: Now, try to reach a bit of uptime and if all is ok, please give a feedback.<\/p>\n This is a base guide to test {vanilla,gentoo}-sources. If you are testing a kernel with other\/special features ( e.g. hardened\/zen\/tuxonice ), make sure that these features work perfectly.<\/p>\n","protected":false},"excerpt":{"rendered":" In the past, a lot of people ask me how test a new kernel. This tip could help new arch tester. First, emerge the new sources ( 3.4.5 is just an example, replace it with your ${version} ): echo “=sys-kernel\/gentoo-sources-3.4.5” … Continue reading
\necho \"=sys-kernel\/gentoo-sources-3.4.5\" >> \/etc\/portage\/package.keywords
\nemerge -av =sys-kernel\/gentoo-sources-3.4.5<\/code><\/p>\n
\ncd \/usr\/src\/linux
\nmake allyesconfig
\nmake # don't forget to add '-j'<\/code><\/p>\n
\nmake distclean
\nmake menuconfig
\nmake
\nmake modules_install # if you use modules<\/code><\/p>\n
\ndmesg<\/code><\/p>\n