Kernel 2.6.35 without debugging code

[lovenemesis]

Hello,

I have problem compiling nvidia 256.44 module with stock 2.6.35 kernel on F14. The error is like this:

http://forums.fedoraforum.org/showpo...4&postcount=43

After searching around the forum it looks like to be caused by the debugging code. So I downloaded the SRPM by

yum-downloader --source kernel

and installed it.

Then I use

rpmbuild --rebuild --without debug,debuginfo

to build the kernel RPM. However, the same error appears when attempted to compile nvidia.ko.

What should I do to get a vanilla kernel without debug so that the nvidia.ko could work?

Cheers,

[andrewthomas]

get the source from http://kernel.org/
and compile (make sure you alter .config to remove debug)

[lovenemesis]

thanks!

But I am kind of prefer the RPM way. So it would be better if I could generate the kernel RPM without debug.

Me RPM obsessive ;p

[chepioq]

And I have one question:
In kernel.org, kernel 2.6.35.3 is stable marked.
When will we have a 2.6.36.kernel without debugging?

[leigh123linux]

Originally Posted by chepioq

And I have one question:
In kernel.org, kernel 2.6.35.3 is stable marked.
When will we have a 2.6.36.kernel without debugging?

You could try asking the fedora kernel devs as no one here will know.

Originally Posted by chepioq

And I have one question:
In kernel.org, kernel 2.6.35.3 is stable marked.
When will we have a 2.6.36.kernel without debugging?

#freenode irc server and the #fedora-devel channel is your friend, ask in there

[droidhacker]

Originally Posted by lovenemesis

thanks!

But I am kind of prefer the RPM way. So it would be better if I could generate the kernel RPM without debug.

Me RPM obsessive ;p

You apparently aren't aware of this, but you can issue a "make rpm" from the kernel source directory and it will build you an RPM. You then install the rpm, manually run mkinitrd, and add an entry to grub.conf.

[lovenemesis]

thanks for the 'make rpm' hint. I guess I would try that.

[AdamW]

I haven't done it for a bit, but I think the simplest thing to do is 'install' the .src.rpm, edit the .spec file and change '%global released_kernel 0' to '%global release_kernel 1' and rebuild.

[lovenemesis]

Originally Posted by AdamW

I haven't done it for a bit, but I think the simplest thing to do is 'install' the .src.rpm, edit the .spec file and change '%global released_kernel 0' to '%global release_kernel 1' and rebuild.

No luck on that. It was set to 1 in stock F14 Alpha kernel.

[vallimar]

I don't use variant kernels, so at the top of the spec, I changed 'baseonly' to '1'.
Then under the baseonly build section, I manually define debug, debuginfo to '0'.
I also disable either docs or perf, whichever isn't already disabled. That should be
enough as I recall, but I also use a customized .config file where I strip out all the
fat of things I can't use or won't use. If you need i686 PAE, then you will need to
adjust accordingly. I only build a base x86_64 kernel so it works fine for me.

---------- Post added at 09:24 AM CDT ---------- Previous post was at 09:05 AM CDT ----------

Originally Posted by lovenemesis

No luck on that. It was set to 1 in stock F14 Alpha kernel.

Also, I just recalled.. there are a couple of "release" variables.. One indicates that the kernel is a release kernel as issued on kernel.org.. meaning it isn't an rc or git kernel, but an official release. The other indicates whether or not the kernel is being built under released or devel distro conditions. For example, it would be set to release for an F13 kernel now, but not F14. I am not at home, so I cannot tell you which is the correct one you need to toggle. It should be pretty easy to figure out by reading the comments though. The distro one should change the debug bits, the other modifies some uninteresting bits.

[AdamW]

oh, yeah, I think vallimar's hit it, I may have given the wrong variable name. Thanks.

[vallimar]

Got home and checked, the variable you need to toggle is debugbuildsenabled. Set it to 1 to build separate debug kernels. Should be able to set that, leave all else alone, and you'll have a kernel package usable for building Nvidia drivers.. at least.. after some long process of compiling. If you plan on making a habit of compiling kernels, I recommend you install ccache.

[lovenemesis]

Ah, that debugbuildsenabled variable makes the difference ! thank you, vallimar!

[Hansvon]

I've rebuilt the kernel 2.6.35.4-12. I've bumped "baserelease" from 12 to 13 and debugbuildsenabled from 0 to 1. I have obtained an extra kernel-debug package so it seems it's working. I'm running my homemade 2.6.35.4-13 kernel.

I then tried to build the kernel module following this guide: http://forums.fedoraforum.org/showthread.php?t=237118

It fails at the "rpmbuild -ba nvidia-kmod.spec --define "kernels $(uname -r)" --target $(uname -m)" stage:

FATAL: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 'debug_lockdep_rcu_enabled'

Hint?

Edit
OK, I should have googled before writing this message: http://www.nvnews.net/vbulletin/showthread.php?t=151258 . It seems LOCKDEP should be removed.
F14 kernels are built with

grep -i lockdep /boot/config-2.6.35.4-13.fc14.x86_64 
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_LOCKDEP=y
# CONFIG_DEBUG_LOCKDEP is not set

while F13

grep -i lockdep /boot/config-2.6.34.2-34.fc13.x86_64 
CONFIG_LOCKDEP_SUPPORT=y

I will try to disable config_lockdep thing...

---------- Post added at 10:06 AM CDT ---------- Previous post was at 07:56 AM CDT ----------

I can't disable the lockdep thing (tried to put CONFIG_LOCKDEP=n in config-generic) and rebuilt the rpm. Any help?