Include kernel 3.2.29 in Slackware 14?
 

Linux 3.2.29 has been released.

I saw some bugs corrections which could be of interest for i915 or radeon users.

Well, if it's too late anyone interested will be able to make 3.2.29 with config files for 3.2.28 :cool:

Great news. Good to know that config files can be re-used. Any special hint? or performance insight?

·······················

I do not have any performance insight as I didn't build that kernel (yet). Anyway I assume that YMMV depending on your hardware and settings.

If by "special hint" you meant "to reuse the config files from 3.2.28", really nothing special. As a reminder copy the "old" config file as /usr/src/linux-3.2.29/.config then run "make oldconfig", that's about it. If need be this will tell you more.

Inclusion of the the new kernel is unlikely,
I think we see it end up in /testing

I think we will see the new kernel.

Pat always adopted a new kernel when was released and I don`t think we need to test this kernel too long. It`s a LTS kernel and with every release it has fewer and fewer bugs.

http://ftp.heanet.ie/mirrors/ftp.sla.../ChangeLog.txt has the answer already.

Fri Aug 24 20:08:37 UTC 2012:
"3.2.28 is going to be the release kernel."

I think Pat didn`t consider that it will resume the devel cycle when he said that :)

Isn't the /testing kernel usually one of the more recent released kernels usually?

If history repeats itself, if anything we will get config files for newer kernels in /testing/source.

Yes, but this is not another kernel branch, this is the same branch.

For the same branch, just reuse one of the config files in /boot.

Anyway there will be probably several kernel releases in the 3.2.x branch before the release of Slackware-next-after-14 and you will have to do that if you want to install one of these.

I doubt 3.2.29 will end up in /testing as it makes no sense; 3.4.x DOES belong there, however. I give it 50/50 Pat will upgrade to 3.2.29: he wrote the above quoted message back on the 24th, and I'm sure he had no idea we would still be pre-release in mid-September...

Speaking of which, perhaps a .rc5 along with 3.2.29 would be prudent, considering all the other changes?


Mike

What about kernel 3.5.x?

Maybe config file(s) only in /testing/source, no more.

and 3.6-rc5 ? (Like 2.6.39-rc4 in 13.37/testing.)

Kernel upgrade question
 

Got Slackware 14RC running on a laptop here, rock solid so far, but had to compile a newer kernel (3.4.x) to get the ALPS touchpad to work.
I compiled the 3.4 kernel with the existing 3.2.28 headers. Sorry if this sounds like a noobish question but now let's say Pat updates to a 3.2.29 or even a 3.4.x kernel and the distro ends up with a new headers package, wouldn't that mean a recompile is required since the header files have changed (3.2.28 --> 3.x.x)?

Always stick with the version of kernel headers that were compiled with the version of glibc. In other words, don't worry about the kernel headers until glibc is upgraded.

More here:

http://www.linuxquestions.org/questi...nt-4175415605/

Thanks for the link. RC5 just came out with a glibc upgrade among other things (kernel and header packages too)
...so if I understood correctly, I'll have to recompile the 3.4.11 kernel on that laptop, right?

Just checked the Change Logs (09/19/12 at 20:40 hrs PDT) and Pat has decided to use 3.2.29 Kernel in RC5 and has stated that unless major bugs found, this will be Slackware 14!

I can't wait!

But Pat also said that 3.2.30 was also released just a couple of hours before writing that change log. Personally, after reviewing the change log for 3.2.30 and seeing all the security fixes in there (along with a couple of OLD, serious bugs squashed), there's a good chance I'm going to upgrade to it when 14.0 is released.

Wait... all the security fixes? The only security related thing I saw was a bluetooth information leak of ONE single byte! I'd definitely respin for security holes (even though printing has to come before replication, and I've already halted the presses once), but didn't see anything of note. And if there are old bugs that are so serious that you've run into them (and/or can tell me how to reproduce them here) please tell me. If it's serious enough, we'll halt again. Thanks!

honestly I can't wait for 14 I got an i3 that's been setting bare drooling. yes I could install rc and upgrade been playing with slackware gawd since 10.2 and can't wait for 14!

Robert

kernel 3.2.29 seems to solve the freeze problem of previous kernels. It has been running about 2 days, no freeze occurred. But I compiled that kernel on my own using 3.2.28's config file, and two changes: corresponding processor family and preemption kernel.

From Slackware 14 RELEASE_NOTES as Sept 20 2012:

So definitively some additional kernels to play around (at least the .config files) will be available.

Oops, RC5's kernel 3.2.29 just froze :(

Retrace your steps, what caused it?

The Kernel Headers package seriously just needs to be renamed to:

glibc-kernel-headers-$version-$arch.txz

To where this question doesn't need to be asked ever again.