Mar 112010

If you visit the Custom kernel article on the CentOS wiki, you will see lots of warnings including the fact custom kernels are not supported by CentOS. If in doubt, just mention “custom…” in the centos IRC channel, you would be told to go away (if you are lucky enough to not get banned :-D).

In the CentOS forums, things are a little more relaxed. After usual warnings, you will receive some (or even extensive) help. As someone put it in a recent post, “… but there are *some* situations, where it [custom kernel] is desirable (usage on notebooks with HW that’s not supported by native kernels – which is e.g. my case or curious minds of young and restless geeks etc. )”.

I am far from ‘young and restless’ and I am not a geek. However, I did compile the latest mainline kernel — in an attempt to help those encountering trouble with installing newer kernels. The error was “mount: could not find filesystem”. I could reproduce it on my CentOS system.

As always, Alan and Ned engaged their brains and we tried several things to find a solution. We were getting nowhere when vanecka posted a fix in this forum thread.

Enable CONFIG_SYSFS_DEPRECATED_V2 in the kernel source configuration.
If you run “make menuconfig”, browse to:
General Setup —> enable deprecated sysfs features which may confuse old usersp, and enable this option.
Edit your .config file with a text editor and add/modify entry:

Genius! If you are interested in learning more details about this option, head for this web page.

  5 Responses to “Want a custom kernel on CentOS? NOooooo! (really?)”

  1. Thank you for the information. It has been useful.

  2. Thank you very much. Your information was very helpful

  3. edit:

    awesome, i tried adding Enable CONFIG_SYSFS_DEPRECATED_V2 in kernel config file it didnt work, so started from scratch and enabled the option using menuconfig and complied and installed worked

    awesome thnx m8

  4. Thanks, max, for reporting the success story. 🙂

    As you found out, direct editing of the kernel config file will not work if a change being made requires changes in other places. It is always a good idea to let menuconfig handle when enabling/disabling options.

  5. Thanks to the post my kernel also worked flawlessly with addition of this option.

Sorry, the comment form is closed at this time.