Hi I was thinking about something. It would be cool to have a “kernel-latest” flavour (just like there are -trace, -vanilla, -xen etc) to test out the bleeding edge kernel without messing with the kernel-default from Factory, but rather have it as a “playground option” in GRUB.
I have seen the instructions about compiling a kernel for OpenSuse, but I have still not gotten around to actually try it with 2.6.28 or 2.6.29-RC.
I am not quite sure how things are contributed to the “software search” repositories available - there are some private name repositories there, but perhaps that is just “certified developers” or something. Otherwise I would gladly upload the (x86_64) RPMs if I ever make them.
As you can see I’m running kernel 2.6.29 from a openSUSE repo. Mind that this means that some kernel-dependent packages no longer work. NVidia driver has to be installed “by hand”, VirtualBox has to be installed manually, sometimes grub errors, once needing a complete power-off.
But, since you’re aware of this now, here’s the repo:
I actually found this one just before I saw your reply. The way I “played safe” was to lock the “-trace” kernel in YAST and then update the “-default”.
For some reason other kernels ("-vanilla" etc) did not want to use the (.29-rc4) kernel-source in order to compile an Nvidia driver module…
Pretty fun living on the edge
I think I will wait a while before I start playing around with ext4 and brtfs
I’m running ext4 now on Arch. It also works on Sidux. You need more than just the kernel, though, so it’s wise to wait until your distro actually supports it. Then you’ll have the updated mkfs, fsck, grub, gparted, and such working properly.
not to hijack this thread :X
if you use that repo and install one of them kernels does it overwrite the one your useing or just adds the option to grub?
Well…it’s not all. Today on 2.6.29-rc4-default VirtualBox-2.1.2_41885_openSUSE111-1 64-bit rpm installs and compiles ending ‘Succes’, module loads, but I cannot start any VM’s. VBOX states:
Failed to load VMMR0.r0 (VERR_SYMBOL_NOT_FOUND).
Unknown error creating VM (VERR_SYMBOL_NOT_FOUND).
Looks like compiling from source will only help if source contains a fix for this
Usually a “SYMBOL_NOT_FOUND” indicates that you don’t have matching kernel-source, -syms, etc. installed. They should match the output of “uname -a”. See post #6.