LinuxQuestions.org
Help answer threads with 0 replies.
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
  Search this Thread
Old 12-04-2017, 01:35 PM   #1
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 473

Rep: Reputation: 78
current testing kernel 4.14.3


The -current testing kernel 4.14.3 is working well here. I checked all the log files after reboot and so far so good.

Code:
bash-4.4$ uname -a
Linux slacker.localdomain 4.14.3 #1 SMP Thu Nov 30 12:14:28 CST 2017 x86_64 AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G AuthenticAMD GNU/Linux
I have both 4.9.66 & 4.14.3 kernel packages installed:

Code:
bash-4.4$ ls /var/log/packages | grep kernel                                                     
kernel-firmware-20171130git-noarch-1                                                                    
kernel-generic-4.14.3-x86_64-1                                                                          
kernel-generic-4.9.66-x86_64-1                                                                          
kernel-headers-4.14.3-x86-1                                                                             
kernel-huge-4.14.3-x86_64-1                                                                             
kernel-huge-4.9.66-x86_64-1                                                                             
kernel-modules-4.14.3-x86_64-1                                                                          
kernel-modules-4.9.66-x86_64-1                                                                          
kernel-source-4.14.3-noarch-1
I'm wondering the best approach to install multiple -current kernels?

In particular, the header packages from different kernels appear to write to the same directory so I'm thinking only the running kernel header package (4.14.3 in my case) should be installed. Also, the source package takes up a lot of space so I'm choosing to only install the running kernel source package (again 4.14.3 in my case).

12 years running Slackware & I'm still learning! :-)
 
Old 12-04-2017, 03:20 PM   #2
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 1,641

Rep: Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583Reputation: 583
Just wondering what you needed a new thread instead of posting your questions in https://www.linuxquestions.org/quest...07/page10.html ?

BTW, you should leave only the kernel-headers from main tree, aka v4.9.66. Do NOT install the second ones from /testing.

All other packages are at your mercy.

Last edited by Darth Vader; 12-04-2017 at 03:35 PM.
 
Old 12-04-2017, 03:39 PM   #3
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 473

Original Poster
Rep: Reputation: 78
NBD if it makes the most sense for all 4.14.x posts to be in a single thread. Secondarily I did wanted to ask how best to manage the testing kernel packages. I can't remember the last time I chose to run a testing kernel. I'll see if a mod can move my post.
 
Old 12-04-2017, 04:30 PM   #4
montagdude
Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 724

Rep: Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526Reputation: 526
As I understand it, the kernel headers on your system should be the ones that glibc was linked against. In other words, if you upgrade the kernel, you do not need to upgrade the kernel headers. See this thread:

https://www.linuxquestions.org/quest...rs-4175615412/
 
Old 12-04-2017, 04:34 PM   #5
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,318

Rep: Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709
Quote:
Originally Posted by montagdude View Post
As I understand it, the kernel headers on your system should be the ones that glibc was linked against. In other words, if you upgrade the kernel, you do not need to upgrade the kernel headers. See this thread:

https://www.linuxquestions.org/quest...rs-4175615412/
I always upgrade the kernel-headers package here. In theory, it could cause issues, but I've not run into any doing this for many years.
 
5 members found this post helpful.
Old 12-04-2017, 05:14 PM   #6
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,239
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
Quote:
Originally Posted by volkerdi View Post
I always upgrade the kernel-headers package here. In theory, it could cause issues, but I've not run into any doing this for many years.
Am I miss understanding this. Every time you have changed glibc and built the kernel we have linked to those headers. newer glibc would be ok with older headers?
since you build pretty much Vanilla way we always are linked to that glibc.
Pat I have back in 2004 we was going from 2.4 to the 2.6. using an old glibc with linked headers to a newer glibc pretty much breaks things.

New may use older to a certain point. But it is all the the kernel changes.

Ask my self what is a header. what is it's function. when you know that you have your answer.
 
Old 12-04-2017, 05:28 PM   #7
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,318

Rep: Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709Reputation: 3709
Quote:
Originally Posted by Drakeo View Post
Pat I have back in 2004 we was going from 2.4 to the 2.6. using an old glibc with linked headers to a newer glibc pretty much breaks things.
My recollection is that the warning was issued either as the kernel was going from 2.2 to 2.4, or from 2.4 to 2.6, and was a good warning then. Every kernel since 2.6 has basically followed a similar structure and I've encountered no incompatibilities using the kernel-headers from whatever kernel is installed, regardless of whether that's what glibc was compiled against.
 
3 members found this post helpful.
Old 12-04-2017, 07:06 PM   #8
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,239
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
Quote:
Originally Posted by volkerdi View Post
My recollection is that the warning was issued either as the kernel was going from 2.2 to 2.4, or from 2.4 to 2.6, and was a good warning then. Every kernel since 2.6 has basically followed a similar structure and I've encountered no incompatibilities using the kernel-headers from whatever kernel is installed, regardless of whether that's what glibc was compiled against.
A header is just that a file that is used for compiling linking assembler etc. It is the "C" way. I think we had a structure change in the 2.6.18 not sure it in a changelog somewhere I believe caused some problems with compiling older modules.
I am sure the header file care less about the GLIBC. but what it builds will.

Last edited by Drakeo; 12-04-2017 at 07:27 PM. Reason: 2.6.18 "C"
 
Old 12-04-2017, 08:38 PM   #9
dugan
LQ Guru
 
Registered: Nov 2003
Location: Canada
Distribution: Slackware
Posts: 7,701

Rep: Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980Reputation: 2980
FWIW, I'm using 4.14.3, including the 4.14.3 kernel headers, and everything's been great so far.

So far I've built the binary NVidia drivers and a git xpad driver. So the kernel headers seem to be working fine.
 
3 members found this post helpful.
Old 12-04-2017, 08:46 PM   #10
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,239
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
Quote:
Originally Posted by dugan View Post
FWIW, I'm using 4.14.3, including the 4.14.3 kernel headers, and everything's been great so far.

So far I've built the binary NVidia drivers and a git xpad driver. So the kernel headers seem to be working fine.
I am to the huge kernel did ok but I always run generic. I am sure the right config is out there
 
Old 12-04-2017, 09:03 PM   #11
slackb0t
Member
 
Registered: Apr 2005
Location: Canada
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 246

Rep: Reputation: 60
Quote:
Originally Posted by dugan View Post
FWIW, I'm using 4.14.3, including the 4.14.3 kernel headers, and everything's been great so far.

So far I've built the binary NVidia drivers and a git xpad driver. So the kernel headers seem to be working fine.
I am staying with 4.14.x also.. running generic with the new headers. No problems so far.
 
1 members found this post helpful.
Old 12-04-2017, 09:14 PM   #12
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,239
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
Quote:
Originally Posted by slackb0t View Post
I am staying with 4.14.x also.. running generic with the new headers. No problems so far.
If you like the generic kernel I wrote a script that builds the initrd.gz of the installed kernel not the running kernel.
it will also download latest nvidia driver and build it if you do not use nvidia it will pass it. just click ok or hit return.

https://github.com/Drakeo/update-nvidia-mkinitrd

you can run lilo before rebooting that way grub does not care.

Last edited by Drakeo; 12-04-2017 at 09:21 PM.
 
1 members found this post helpful.
Old 12-04-2017, 09:21 PM   #13
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,239
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
oops

Last edited by Drakeo; 12-04-2017 at 09:42 PM.
 
Old 12-06-2017, 09:56 AM   #14
slackb0t
Member
 
Registered: Apr 2005
Location: Canada
Distribution: Slackware64-current on Thinkpad Carbon X1
Posts: 246

Rep: Reputation: 60
Quote:
Originally Posted by Drakeo View Post
If you like the generic kernel I wrote a script that builds the initrd.gz of the installed kernel not the running kernel.
it will also download latest nvidia driver and build it if you do not use nvidia it will pass it. just click ok or hit return.

https://github.com/Drakeo/update-nvidia-mkinitrd

you can run lilo before rebooting that way grub does not care.
Thanks I will have a look.
 
  


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



Similar Threads
Thread Thread Starter Forum Replies Last Post
-current and /testing Rinndalir Slackware 29 09-17-2016 09:41 PM
[TESTING REQUEST] Xorg in -current (yes, again) rworkman Slackware 171 10-31-2009 05:49 PM
Trying some -current testing Alstare Slackware 4 11-10-2008 04:36 PM
Request for Testing - hal-0.5.11rc1 in -current rworkman Slackware 11 03-18-2008 02:23 PM
slack 10.1 -> current testing kernel and battery support jasone Slackware 3 05-24-2005 04:00 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:33 PM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration