Newest Kernel for openSuSE 13.2
 

I'm following a more recent small short howto for compiling Kernel. https://lizards.opensuse.org/2014/04...ompile-kernel/

Some things in the procedure have changed compared to the 2000's.

Whatever, the procedure gets me (my chosen i386 default) Kernel code in version 4.5 which seems to be brand new kernel source from this morning.

When I install linux-source from Software Manager, like in the old days, it downloads kernel 3.16.7.

After menuconfig I just make my kernel 4.5, which also does work.

Can/should I install the 4.5 Kernel on OpenSuSE 13.2 or is that nonsense?

I found a reference that it is possible http://superuser.com/questions/95529...le-version-4-1

How I usually do it (and many others, I suppose, too):

1. Go to kernel.org
2. Download the source of wanted version
3. Extract the archive
4. Place config-x.y.z from /boot to the extracted folder, naming it .config
5. make oldconfig and usually say n to all, because I cut kernels as much as I can. I don't need additional drivers
6. make menuconfig if I need to cut even more, but usually skip it
7. make
8. make modules install
9. make install (GRUB automatically finds new entries). In case I don't have GRUB, I copy System.map, vmlinux.bin (from arch/x86/boot) and .config to /boot, renaming System.map-x.y.z, vmlinuz-x.y.z and config-x.y.z respectively. And then configure a bootloader.

I'd rather use longterm branches (3.18, 4.1, 4.4) instead of latest stable and mainline. But usually there is no difference between, say, 4.4 and 4.5. The biggest changes are mostly drivers included. As I don't have exotic hardware, it doesn't make a difference for me.

Thank you. Picking a longterm branch is a good idea.

I also try to eliminate a lot of unneeded drivers (if i can clearly identify them as such) from my setup, also in menuconfig.

When configuring from scratch I do make allnoconfig, then make nconfig and start adding what I need. This results in leanest kernel possible. I do not build modules, everything is built into kernel when possible. Answering no to all questions in make oldconfig is not such a good idea, you are going to miss new features you may want.

Edit: There is also make localmodconfig for lazy people.

You can get an already compiled 4.5 kernel from the Kernel/HEAD:/ repository for opensuse. If you feel adventurous you can also get 4.6-rc2 from there.

Sometimes; for example, when moving to 4.5 from 4.4 a new menu for wireless cards appeared, and if I'd say no, I'd miss my card. So, yes, clicking n's should be done carefully.

Allnoconfig? That sounds extreme. It would be good indeed to know every single function in the kernel config.

Unfortunately I do not know every little chip and sensor in my computer, or every administrative function for flash devices and hardware bus systems, or in my BIOS and the 1000 other things.

I rather deactivate drivers for network and grapics adapters, and for special hardware that I don't have. And functions, protocols and filesystems that I obviously don't need.

I forgot, I don't use initramfs/initrd - I disabled support for it, so if you use and move files to /boot manually, don't forget to move initrd.gz, too.

I also mark drivers as built-in[*] instead of [M], where possible; it didn't work with ALSA and wireless though. In my experience, it reduces memory footprint.

It may sound extreme, but think. Kernel is the most important part of your installation. There are tons of information about kernel options on the net, sites dedicated to help with kernel configuration. And you have to do it just once, from there on you have your own kernel seed. I use my seed on all my computers, just modifying it to suit the hardware and functionality, much faster then starting from scratch every time. BTW, I my first took over four hours to complete, but I feel rewarded with the result. :)

I need to find a competent person that already made a kernel config starting from allnoconfig for exactly my Lenovo T60 :D

If I tried to start with allnoconfig I'm sure it would take me 24 hours. But I think it would be near impossible to have missed no needed functionality, like a network protocol function, or a thermal sensor on my mainboard.

I also make the functions built-in for the hardware I know I have. If I'm unsure wheter I have or need it, and the help doesn't recommend "N" in that case, then I build a module.

Maybe you can dig something useful out from here. The author of kernel-seeds.org is out of business, methinks, but there are bits and pieces on the net.

Thanks.

A lot more research would be necessary to make an optimal Kernel.

But it is OK for me to eliminate only the obvious and still have a lot of unneeded funcionality in the kerne or modules.

the biggest question is WAY on 13.2 ?

13.2 is getting close to it's End of Life

if you MUST HAVE the newest kernel then install suse tumbleweed

and then build the release candidate kernels

I thought when I compile, why an old Kernel (actually it isn't even old, only 1 1/2 years).

Tumbleweed I did't install because it brings no support for 32-bit. The other day I found out that my supposedly so old Centrino is "Intel Core 2 Duo" (64-bit).

So I want to upgrade my 1 GB RAM to 3 - 4 GB

Then I will reinstall. But Slackware, Arch, Debian or something like that.