Hello everybody. I’ll be brief, i compiled a custom kernel getting rid of all the unnecessary drivers etc. I used this website Running / Using ext4 on openSUSE 11.1 | Ben Kevan’s Blog
Now the only problem is how can i compile kernel-source from my custom kernel to allow installing NVIDIA drivers for example?
What i used to make that kernel was a “make rpm”
What command would i have to use to create a kernel-source?
using make rpm in the /usr/src/<kernel> directory should make a symlink in /lib/modules/<kernel>/ called build & source that points to /usr/src/packages/BUILD/<kernel>
That is your kernel-source equivalent.
Oh… be sure you INSTALL the new kernel and not UPGRADE it… Also if you really want to get savvy you can create a .spec and create the kernel package (not priority for me)…
I certainly don’t want to make a spec file as it’s a work in progress 
I want to make my kernel as small as possible and with the least modules possible too:) And also to optimize for my CPU. I wonder if it wouldn’t be easier to run kernel from head repo as it is 2.6.29 but it’s kinda risky:) Thanks for the tip!!
Having things as modules doesn’t increase load time… Make sure you know what you’re doing when trimming down (or you may leave your computer bootless). Do a cloneconfig if you’re going to use a different config that you keep on changing.
But yeah… you should be good.
What i generally do is i use lsmod to list all the loaded modules at actual OS and check if any of these has been disabled in the config. That should leave me quite happy i think:)
Only thing i might miss are openSUSE specific patches:)??
There are some modules that aren’t listed in the new kernel (user mode modules?)
P.S. I can see that most modules are compiled as loadable but i still don’t want them (as a bonus compilation of the kernel is WAAAAAAAAYYY shorter;) )
BenderBendingRodriguez wrote:
> What i generally do is i use lsmod to list all the loaded modules at
> actual OS and check if any of these has been disabled in the config.
> That should leave me quite happy i think:)
> Only thing i might miss are openSUSE specific patches:)??
I run custom kernels almost exclusively and never apply the openSUSE specific
patches. There are no problems. I don’t have AppArmor and there is a missing
ioctl for the serial drivers, but I don’t miss either.
Once you have built a new kernel, you don’t need to mess around with an rpm.
Just run the command ‘sudo make modules_install install’. The resulting things
that are executed with copy the modules to the right place in /lib/modules,
build initrd, copy the new kernel to /boot, and update the GRUB menu by adding
the new kernel while still keeping the old one available.
Larry
Then i’m off to another customizing of the new (not so new but hell) and shiny 2.6.28 kernel