Anyone know how/when I can get 2.6.30 for opensuse? Will it be part of the updater?
Not in 11.1 unless you compile yourself. 11.2 is using it currently rc6 version
Hi
Running it on 11.2 milestone 2, so would imagine around November when
11.2 is released.
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.2 Milestone 2 (i586) Kernel 2.6.30-rc6-git3-4-default
up 2 days 12:42, 3 users, load average: 1.66, 1.14, 0.66
CPU VIA Esther processor 1000MHz GPU VIA CX700/VX700
This is not correct you don’t need to compile it yourself just add the header repo Index of /repositories/Kernel:/HEAD/openSUSE_Factory (the current version available is 2.6.30-41.1) and install it with yast
Installed it over the weekend with in my vmware sandbox both 11.1 and 11.2 milestone2
However would only recommend this for testing
Just keep in mind that newer doesnt always mean better, for me kernel 2.6.25.20-0.4 on OpenSuse works better then Jaunty’s 2.6.28 Kernel
Not even Karmic promises 2.6.30
Once the kernel stabilizes then it will become available, if its not a security patch its not going to be a top priority…
Take care, Take care:
There’s some major changes in compilers and development files for the kernel 2.6.30. No trouble at all in Milestone2 / Factory, but expect a lot of trouble on 11.1. Realize that is distro is built around a kernel.
Yes the new kernel makes a lot of things a lot faster, but the bleeding edge is for testing purposes, so that the public release versions are stable and flawless.
Ugh, what troubles on 11.1? I run kernel 2.6.30 on 11.1 (self-compiled) and no troubles at all
Obviously there is room for different perspectives . . . my two cents is that it is wise to keep a copy of the previous kernel & initrd whenever there is an update, whether to the production release or installing a newer non-production kernel (which may be required for certain hardware support, etc.).
Just this week I helped a user who, upon updating to production 2.6.27.23, found the kernel could not initialize the machine’s USB controller, making the machine unbootable. That user has to reinstall the previous kernel, not trivial on a non-running system.
I’ve been running 11.2 (milestone2 64bit) as my main system for over 2 weeks now.
And I must say, it’s the smoothest, best looking, and most functional version of Linux I’ve ever used!
The 2.6.30 kernel is a powerhouse! My system runs way cooler than ever before (I hardly ever hear the fan anymore!), the video system runs cooler, and for the first time ever I have a fully functional suspend-to-ram!
It also does a cold boot faster than any previous openSUSE version.
I’ve never seen a laptop resume so fast in my life before, and I have seen a lot of laptops and operating systems.
Vista on the same laptop takes over a minute for a full resume (ie internet up and running), openSUSE 11.2 milestone2 takes 11 seconds, and that includes entering my screenlock password!!!
I’m actually not looking forward to anything getting changed in this version, I could stick with this to the end of my laptop’s life, it’s that good :D.
Wow. Sounds awesome. I have a crap computer that I might try installing that on. Where do i get the ISO for 11.2 with 2.6.30?
You cant get both at the same time the milestone is here Software.openSUSE.org and you need to add the kernel repos here Index of /repositories/Kernel:/HEAD/openSUSE_Factory
AFAIK, you don’t (unless you build one yourself with Kiwi). You would need to install from the Factory repository.
WARNING! Thread hijacking underway!
My lab rat seems to keep old kernels and lists them on the grub menu. You’re saying this is a good thing? I was going to ask how to get rid of them. Should I? Can I?
Not sure if you’re joking, or actually asking how to . . .
In order asked: Yes. No. Yes, it is your machine.
If I’m understanding you correctly . . .
The kernel update script also updates menu.lst. How it does that depends on what it finds in the stanzas and on the title lines. By default, it looks for a stanza which explicitly states the kernel file name, and updates that with the new file name. I maintain menu.lst myself, using my own titles and using the vmlinuz and initrd symlinks rather that fully qualified file names. So with my menu.lst, the update script adds a new stanza, leaving my custom stanzas alone. I have seen users with orphan stanzas referencing old replaced kernels; I don’t know the script logic well enough to know what causes that to happen. In any event, a stanza referencing an old kernel will of course ordinarily fail because the kernel update removes the present kernel before installing the new one.
I keep a sub-directory under /boot named “/last”. Before any kernel update, I copy the current kernel, the initrd, the two symlinks, and menu.lst to this directory. Then after the update before rebooting, I quickly check /boot and menu.lst to make sure everything is as expected and I remove the stanzas added to menu.lst because, as mentioned above, I use custom stanzas instead. Doing all this is a couple of additional steps, but it only takes a minute. If at reboot the new kernel fails, I return to the grub menu and do an on-the-fly edit of the menu entry, inserting “/last” into the kernel and initrd paths, which boots the machine with the previous kernel that I had made a copy of.
IMO, this is just good housekeeping; keeping a bootable backup is standard practice in corp IT shops. And it has come in handy more than once (e.g., recently a VirtualBox update caused the kernel update’s mkinitrd to fail; I got the new kernel but the initrd was missing). I’m surprised the kernel update script doesn’t include making a bootable backup.
Excellent advice there geoffro, I was having lots of problems compiling 2.6.30.xx on my 11.1 install and that saved me many headaches and wasted time and power messing around compiling.
After 3 failed attempts at compiling, I was about to give up, now I have kernel 2.6.30-50-default running like a charm :).
How or wich pack did you install?
I dunno wich one to install or what to do after I added the kernel repo
Search for kernel in yast, and just click on the newer one. It should tell you that it needs to install the new kernel headers and source (if you have that installed).
That should do it.
Although be aware that the newer kernel is compiled with a newer version of gcc. This only showed up when I recompiled my Nvidia module.
It warned me, but I just chose to ignore it and contiuned compiling. It works perfectly for me :).