LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
LinkBack Search this Thread
Old 11-29-2012, 01:42 AM   #16
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266

I am using the 3.4.x kernels, but may move to 3.6.x soon. I don't like 3.2.x because of bad nouveau drivers and a few other issues. If you don't have problems with it, you can stay with it.
 
Old 11-29-2012, 04:49 AM   #17
arubin
Senior Member
 
Registered: Mar 2004
Location: Middx UK
Distribution: Slackware64 14.1 (multilib)
Posts: 1,209

Rep: Reputation: 55
I went to 3.4 based on Pat's configuration in /testing because I wanted to try a kernel with EFI stub enabled. It is working fine for me.
 
Old 11-29-2012, 09:24 AM   #18
GazL
Senior Member
 
Registered: May 2008
Posts: 3,231

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
I tried 3.6 but it introduced some ACPI Conflict warnings on my box (Actually, googling, it looks like it was 3.5 that introduced them, but I never tried that one so I can't say for certain). I believe 3.7 contains a fix, so I'll be waiting for that one. In the mean time, it's nice being able to fallback to the 3.2 branch and I'm glad Pat chose to base the release on a long-term kernel.
 
Old 11-29-2012, 09:25 AM   #19
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
I have been upgrading to the latest kernel the day they appear on kernel.org since around 1999 using slackware. It is easy. I have only run into one small problem. That was with vmware when the 'tickless kernel' was introduced. That problem only effected vmware and was quickly fixed by the developers.
My reasoning has always been if the kernel developers think the kernel should be constantly upgraded why shouldn't I. After all it is their kernel.
I always start with Pat's latest config.
John
 
Old 11-29-2012, 01:03 PM   #20
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
As a note 3.4.x is also long-term.
 
Old 11-30-2012, 09:09 PM   #21
derfzz
LQ Newbie
 
Registered: Oct 2009
Posts: 3

Original Poster
Rep: Reputation: 0
I just finished upgrading the kernel, after a long strenuous figuring things out, to 3.7.0-rc. Took awhile to figure out what should be turned on in /usr/src/linux/.config. One of the problems that I encountered building the new kernel was that the .config, by default, did not have CONFIG_TMPFS and CONFIG_TMPFS_MOUNT turned on. had to look at GENTOO forums for that :P

Anyways, my question is what are the primary difference between mainline and stable in www.kernel.org ? their FAQ do not explain what the mainline is, at least i think not ;D

Last edited by derfzz; 11-30-2012 at 09:13 PM.
 
Old 11-30-2012, 10:36 PM   #22
qweasd
Member
 
Registered: May 2010
Posts: 432

Rep: Reputation: Disabled
Quote:
Originally Posted by derfzz View Post
Anyways, my question is what are the primary difference between mainline and stable in www.kernel.org ? their FAQ do not explain what the mainline is, at least i think not ;D
I think that's the official position: no explanation. From my personal experience, "stable" kernels do tend to be more stable, and the higher is the 3rd version number, the more stable they are. But the newer ones support more devices, or support them more fully.

Edit: I am running linux-libre 3.6.6 on my lappy now, used Pat's 3.6 config and it just worked (TM). Feels great, with more than a week uptime now. I upgraded to support Ivy Bridge and to purge the kernel blobs.

Last edited by qweasd; 12-04-2012 at 10:22 AM.
 
Old 12-03-2012, 09:19 PM   #23
kite
Member
 
Registered: Aug 2003
Location: Shenzhen, China
Distribution: Slackware
Posts: 296

Rep: Reputation: 47
I have upgraded to very bleeding edge 3.7rc3 with some other patches to solve my macbook pro 8,1 internal mic problem. All is fine.
 
Old 12-04-2012, 07:40 AM   #24
frushiyama
Member
 
Registered: Oct 2010
Location: Brazil
Distribution: Slackware64 14.0
Posts: 32

Rep: Reputation: 0
I'm using 3.7.0-rc7 with .config from http://slackbuilds.org/mirror/slackw...ic-3.6-rc4.x64 Slackware testing file tree. All new modules i'd assumed with the default option.
In mounting USB external disks, i'm having troubles with it dismounting itself, but it seems to be a new approach of udev of newer kernels, not sure yet, anyway i'm trying to solve it...
I also had three reboots with this kernel config, but i was not watching it so not sure too what happened.
I builded a new kernel because i had same troubles of this post http://www.linuxquestions.org/questi...30-4175426269/
 
Old 12-06-2012, 12:30 AM   #25
narz
Member
 
Registered: May 2007
Location: US
Distribution: slackware
Posts: 184

Rep: Reputation: 35
Quote:
Originally Posted by AlleyTrotter View Post
My reasoning has always been if the kernel developers think the kernel should be constantly upgraded why shouldn't I. After all it is their kernel.
By that logic, you should go with a bleeding edge rolling release distribution. Get the "latest and greatest" from everyone.
 
Old 12-06-2012, 04:08 AM   #26
commandlinegamer
Member
 
Registered: Dec 2007
Posts: 68

Rep: Reputation: 11
I haven't compiled a custom kernel for about 5-6 years I reckon; the generic pretty much just works for me. Might even be longer, from memory the last time I did was before the video4linux stuff was integrated.
 
Old 12-06-2012, 04:34 AM   #27
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 462

Rep: Reputation: Disabled
The only time I upgrade a kernel outside of what comes with Slackware is if I need too. The last time I needed to upgrade a kernel was ages ago.
 
Old 12-06-2012, 08:06 AM   #28
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.1 (3.14.0) UEFI enabled
Posts: 344

Rep: Reputation: 71
Quote:
Originally Posted by narz View Post
By that logic, you should go with a bleeding edge rolling release distribution. Get the "latest and greatest" from everyone.
Actually I do. I upgrade everything that Pat says I need to upgrade. After all its his distribution.
You have a problem with that?
John
 
Old 12-06-2012, 08:13 AM   #29
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266Reputation: 1266
It really depends on your needs. For a while I used bleeding edge kernels because I wanted good nouveau support. Now I use the long term 3.4.x, because it has a good nouveau driver, is stable, and is long term support. You may have different requirements and probably can use the default kernel. In fact, for a long time I also used the default kernel version, but still a custom kernel for performance reasons.
 
Old 12-07-2012, 08:19 PM   #30
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 Current
Posts: 313

Rep: Reputation: 64
Quote:
Originally Posted by SqdnGuns View Post
Depends on your distro. In Slackware it is much easier and straightforward. Other distro have the kernels so heavily patched it's like playing Twister with a greased pig.

http://docs.slackware.com/howtos:sla...kernelbuilding

Using the above link, I can build a new kernel in 15 - 20 minutes.
This is one of the great things about slackware imo. When we were still at 13.37 and the release candidates i was keeping up with the latest kernel and had no trouble. Since 14 was officially released i have been using the stock kernel.
But to address the op, just back up your boot dir/partition and lilo.conf and create a new menu entry in lilo for the new kernel, dont delete the old one, this way you have a way back and can boot to either kernel when you want to.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Split a file, byte-wise, not character-wise. stf92 Linux - Newbie 4 11-17-2010 06:43 AM
how to Block a site in a Firewall or Router by Protocol wise & host wise. shahid khan Linux - Security 2 06-26-2009 04:13 PM
is it safe running slackware 10.1 now, security-wise? guy24x Slackware 12 05-05-2008 02:48 PM
bandwidth allocation by user wise and ip wise basbosco Linux - Networking 1 11-12-2003 02:54 AM
is it wise to upgrade to kernel 2.4.21 duister Slackware 26 08-16-2003 03:39 PM


All times are GMT -5. The time now is 11:55 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration