Just my small effort to return what I get from Linux
I have tried a few of your core2 kernels recently on my Mint10 partition and recently installed the 22.214.171.124-core2 (amd64 build) on my Natty partition. I've noticed that when simply installing with:sudo dpkg -i linux-headers-126.96.36.199-core2_14.00_amd64.deb linux-image-188.8.131.52-core2_14.00_amd64.debI have received the same symlink error with every kernel I have tried on both partitions."Setting up linux-image-184.108.40.206-core2 (14.00) ... Hmm. There is a symbolic link /lib/modules/220.127.116.11-core2/build However, I can not read it: No such file or directory Therefore, I am deleting /lib/modules/18.104.22.168-core2/build Hmm. The package shipped with a symbolic link /lib/modules/22.214.171.124-core2/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/126.96.36.199-core2/source"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.
can you try installing linux-headers-generic from synapticit 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
I had these already installed:linux-headers-generic (188.8.131.52.22)linux-headers-2.6.38-8-generic (2.6.38-8.42)
Okay. I checked those two files in the linux-image deb. The symbolic links are broken for: /lib/modules/184.108.40.206-core2/source/lib/modules/220.127.116.11-core2/buildbecause it is pointing to:"/home/sankaran/Downloads/2.6.38/linux-18.104.22.168"Which is not a valid link, since I am not you, and I am not on your computer. :)
Oh, that is bad, I will check how to resolve it:)
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.
Follow the new way of building kernel, http://duopetalflower.blogspot.in/2011/10/custom-64-bit-ubuntu-kernel-31.html
still hasn't tried to resolve the module hardcoded link while building, wasted time watching Naruto animation
I copied everything to /usr/src/ and now building 2.6.39with 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
The compiled debs are uploaded to dropbox, this does not have the said symlink problem. Thanks for pointingHere is the post regarding the dropbox links of newly built 2.6.39 packages optimized for core2 on 64 bit systemshttp://duopetalflower.blogspot.com/2011/05/custom-kernel-2639-ubuntu-amd64.html