Home page of this blog

Sunday, May 8, 2011

Compiled kernel with transparent hugepage support

Today I compiled linux kernel with transparent hugepage support enabled. Also changed the march and mtune in arch/x86/Makefile to native for CORE2

Enjoying the new kernel, will upload it tomorrow, feeling sleepy ...


  1. I have tried a few of your core2 kernels recently on my Mint10 partition and recently installed the (amd64 build) on my Natty partition. I've noticed that when simply installing with:
    sudo dpkg -i linux-headers- linux-image-

    I have received the same symlink error with every kernel I have tried on both partitions.

    "Setting up linux-image- (14.00) ...

    Hmm. There is a symbolic link /lib/modules/
    However, I can not read it: No such file or directory
    Therefore, I am deleting /lib/modules/

    Hmm. The package shipped with a symbolic link /lib/modules/
    However, I can not read the target: No such file or directory
    Therefore, I am deleting /lib/modules/"

    With the previous kernels I've tried, it seems to boot with that kernel and run without any major issue. I guess I'm just wondering if there's anything I might be missing with the install because of this, resulting in a kernel that works, but performs at a sub-optimal level.

  2. can you try installing linux-headers-generic from synaptic

    it might have the missing links, as far as I have tried, I did not find any missing links, so could not tell what it may be

  3. I had these already installed:
    linux-headers-generic (
    linux-headers-2.6.38-8-generic (2.6.38-8.42)

  4. Okay. I checked those two files in the linux-image deb. The symbolic links are broken for: /lib/modules/

    because it is pointing to:

    Which is not a valid link, since I am not you, and I am not on your computer. :)

  5. Oh, that is bad, I will check how to resolve it


    1. I am facing the same symbolic link error problem. I am building a kernel with xenomai patch. It works on the m/c in which it was compiled. When I install it in another m/c with the linux-image deb, I see this warning. Pls enlighten me on how you resolved it.

  6. still hasn't tried to resolve the module hardcoded link while building, wasted time watching Naruto animation

  7. I copied everything to /usr/src/ and now building 2.6.39

    with transparent hugepage support, autogroup scheduling, all natty narwhal config + 300 HZ

    optimized for core2 processor, will upload once build is finished and this should resolve the symlink problem

  8. The compiled debs are uploaded to dropbox, this does not have the said symlink problem. Thanks for pointing

    Here is the post regarding the dropbox links of newly built 2.6.39 packages optimized for core2 on 64 bit systems