LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 08-11-2016, 08:20 PM   #1
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
Slackware 14.2 glibc-2.23 vs Slackware Current glibc-2.24 and the Current 4.4.17 Kernel


Question for the Experts.

I've been installing the 4.4.x Kernel Packages from Slackware64 Current into my Slackware64 14.2 System.

Up to now, Current and 14.2 were both running glibc-2.23 and both were compiled with gcc-5.3.0 so no problems with that.

Now Current is running glibc-2.24 compiled with gcc-5.4.0.

I suppose the Current 4.4.x Kernels are no longer safe to install in 14.2 ?

Thanks !

-- kjh( all good ( easy ) things must eventually come to an end )

Last edited by kjhambrick; 08-11-2016 at 08:27 PM. Reason: misspelled glibc-2.24 in Title Line
 
Old 08-12-2016, 03:28 AM   #2
phenixia2003
Member
 
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 948

Rep: Reputation: 870Reputation: 870Reputation: 870Reputation: 870Reputation: 870Reputation: 870Reputation: 870
Hello,

AFAIK, you can use a newer kernel even if it was compiled against new glibc and/or with new gcc, but, you must not upgrade the kernel-headers package.

To not break anything, it's better to not upgrade the kernel packages, but to *install* the news alongside the older versions. slackpkg will complain about duplicate packages, but you can circumvent that by blacklisting the kernel packages in /etc/slackpkg/blacklist.

Once you have installed the new packages (ie. kernel-huge, kernel-generic, kernel-modules, and kernel-sources), do not forget to re-create the initrd for the generic kernel as in example below, and to re-run lilo (if you use it).

Code:
$ /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.17

...
mkinitrd -c -k 4.4.17 ...
I just tried in a VM while writing this message, and all seems to work, even VirtualBox that I installed in the VM (for fun) has automatically rebuilt the modules for 4.4.17.

Anyway, It would be better that you try this in a VM before doing that on your system.

--
SeB
 
2 members found this post helpful.
Old 08-12-2016, 06:41 AM   #3
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Original Poster
Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
Thank you as always, SeB !

Interesting results !

I'll give it a shot:
Code:
cd /home/dld/slackware/slackware-current-64
installpkg slackware64/a/kernel-generic-4.4.17-x86_64-1.txz \
           slackware64/a/kernel-huge-4.4.17-x86_64-1.txz    \
           slackware64/a/kernel-modules-4.4.17-x86_64-1.txz
vim /etc/lilo.conf
lilo
shutdown -r now
#
# after booting 4.4.17  ...
#
cd /home/dld/nvidia
NVIDIA-Linux-x86_64-367.35.run
shutdown -r now
#
# after booting 4.4.17 + NVidia ...
#
startx
Since I can always 'revert' to an older kernel I'll give it a go on my Prod Laptop and report back.

Thanks again, SeB.

-- kjh
 
Old 08-12-2016, 06:55 AM   #4
phenixia2003
Member
 
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 948

Rep: Reputation: 870Reputation: 870Reputation: 870Reputation: 870Reputation: 870Reputation: 870Reputation: 870
Hello,

about nvidia driver. Just in case you don't know, you can build the driver module for the running kernel without uninstall of the existing module(s) with the option --kernel-module-only. Personaly, I always run it as below :

Code:
$ sh ./NVIDIA-Linux-<ARCH>-<VERSION>.run --accept-license --ui=none --kernel-module-only
--
SeB
 
1 members found this post helpful.
Old 08-12-2016, 07:53 AM   #5
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Original Poster
Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
Thanks for the NVidia hint SeB.

[EDIT]
The following did not work because I failed to install the kernel-source-4.4.17 !

See post #3

I installed kernel-source-4.4.17, reset the symlinks in /boot/ and all is well.

I'll run 4.4.17 for a while and watch the logs.
[/EDIT]


The 4.4.17 experiment was a bust.

The system booted 4.4.17 fine but my VMWare Workstation BlockDev and Network Modules FAILED to load.

Normally with a new Kernel, there will be a delay on 'first boot' while VMWare rebuilds the Kernel Modules.

This time with kernel-4.4.17 from Slackware64 Current the rebuild failed and I had no vmnet interfaces ( not sure about the disks -- didn't even try ).

I rebooted 4.4.16 which hung hard after the 'ACPI: Power Button [PWRF]' message but before the message saying it was loading a custom ath10k_pci Kernel Module I built for my Killer 1535 Wireless.

I did a Hard-Reset and booted 4.4.17 and fixed the symlinks in /boot:
Code:
cd /boot/
ln -sf System.map-huge-4.4.16   System.map
ln -sf config-huge-4.4.16       config
ln -sf vmlinuz-huge-4.4.16      vmlinuz
ln -sf vmlinuz-generic-4.4.16   vmlinuz-generic
ln -sf vmlinuz-huge-4.4.16      vmlinuz-huge
After which I was able to boot 4.4.16 and the NVidia Modules loaded and VMWare started OK.

I'll be removing those 4.4.17 Packages ( after I do a dry-run: `removepkg -warn kernel-*-4.4.17`) and then I'll build and install those 4.4.17 Kernel Packages locally

-- kjh

Last edited by kjhambrick; 08-12-2016 at 09:32 AM.
 
Old 08-12-2016, 09:33 AM   #6
Toutatis
Member
 
Registered: Feb 2013
Posts: 262

Rep: Reputation: Disabled
I have always assumed that in slackware-current, where a new version of a package appears, every package that would be affected by this change is rebuilt or updated. Unless of course there is some mistake. I never had serious problems after updating.
 
Old 08-12-2016, 10:08 AM   #7
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Original Poster
Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
Toutatis --

Yes, Pat does a great job with Dependencies so it is generally true within a single version that the Packages are 'consistent'.

I have been cheating though.

I have been installing kernel-4.4.x Packages from Current into my Slackware64 14.2 System.

But, I've not installed anything from Current into 14.2 except for the Kernel.

So if anything has changed in Current that affects the kernel binaries, I will have to stop 'cheating' and then build and package-up my own kernels in 14.2.

I was worried that the new gcc-5.4.0 and glibc-2.24 in Current might break the Kernel for 14.2 which has gcc-5.3.0 and glibc-2.23

And then to complicate things even more, I am running the MultiLib versions of gcc and glibc:

Code:
# ver gcc- glibc-
-rw-r--r-- 1 root root  44797 Mar 12 14:11 /var/log/packages/gcc-5.3.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root  41905 Mar 12 14:11 /var/log/packages/gcc-g++-5.3.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root   2762 Mar 12 14:11 /var/log/packages/gcc-gfortran-5.3.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 251603 Mar 12 14:11 /var/log/packages/gcc-gnat-5.3.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root  20355 Mar 12 14:12 /var/log/packages/gcc-go-5.3.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root 236582 Mar 12 14:12 /var/log/packages/gcc-java-5.3.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root   2232 Mar 12 14:12 /var/log/packages/gcc-objc-5.3.0_multilib-x86_64-3alien
-rw-r--r-- 1 root root  32507 Feb 29 05:48 /var/log/packages/glibc-2.23_multilib-x86_64-1alien
-rw-r--r-- 1 root root 491578 Feb 29 05:48 /var/log/packages/glibc-i18n-2.23_multilib-x86_64-1alien
-rw-r--r-- 1 root root   1325 Feb 29 05:48 /var/log/packages/glibc-profile-2.23_multilib-x86_64-1alien
-rw-r--r-- 1 root root  15563 Feb 29 05:48 /var/log/packages/glibc-solibs-2.23_multilib-x86_64-1alien
-rw-r--r-- 1 root root  71018 Aug 12 09:54 /var/log/packages/glibc-zoneinfo-2016f-noarch-1_slack14.2
Seb's post gave me enough info and the courage to try out the 4.4.17 kernel Packages from Current is 14.2.

The Current kernel-*-4.4.17 Packages seem to run OK, after I fixed my goof ( by not installing kernel-source-4.4.17 ).

For the record, this is what I've installed from Current in my 14.2 ( note that slackware64/d/kernel-headers-4.4.17-x86-1 are excluded )

Code:
# ver kernel-*4.4.17

-rw-r--r-- 1 root root     985 Aug 12 06:51 /var/log/packages/kernel-generic-4.4.17-x86_64-1
-rw-r--r-- 1 root root     981 Aug 12 06:51 /var/log/packages/kernel-huge-4.4.17-x86_64-1
-rw-r--r-- 1 root root  248554 Aug 12 06:51 /var/log/packages/kernel-modules-4.4.17-x86_64-1
-rw-r--r-- 1 root root 3413105 Aug 12 08:18 /var/log/packages/kernel-source-4.4.17-noarch-1
Thanks.

-- kjh
 
Old 08-12-2016, 02:16 PM   #8
atelszewski
Member
 
Registered: Aug 2007
Distribution: Slackware
Posts: 890

Rep: Reputation: Disabled
Hi,

Quote:
Originally Posted by phenixia2003 View Post
AFAIK, you can use a newer kernel even if it was compiled against new glibc and/or with new gcc, but, you must not upgrade the kernel-headers package.
It's not the kernel that is built against glibc, it's the glibc that is built against the kernel. More specifically, against the kernel headers.

Kernel can be compiled with pretty which ever compiler you want, as long as it produces the correct code ;-)
Among the officially supported compilers is gcc, gcc, and gcc ;-)

--
Best regards,
Andrzej Telszewski
 
4 members found this post helpful.
Old 08-12-2016, 02:20 PM   #9
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,484

Original Poster
Rep: Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921Reputation: 921
Dooh !

Thanks for that info atelszewski !

That explains why it works ( very well so far ).

-- kjh
 
Old 08-12-2016, 05:30 PM   #10
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 7,925

Rep: Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593Reputation: 6593
I have uploaded new multilib versions of gcc-5.4.0 and glibc-2.24 for slackware64-current.
 
1 members found this post helpful.
Old 08-13-2016, 01:00 AM   #11
Wiser Slacker
Member
 
Registered: May 2014
Location: germany
Distribution: slackware x86_64 , arm , slackware
Posts: 73

Rep: Reputation: Disabled
Hi,

i have changed to current just to get the newer gcc, and glibc also , now i do my own custom kernel 4.6.6

at most time after fresh installation i went with the kernel some versions when i also have new hardware
so one can get better support for new functions and devices

i have never had any problems by going this way , its just time consuming , but i have an actual system when i have done

later when its all running like it should, i do only some security patches by compiling these packages by myself

than there is nothing todo until the next slackware comes up or i get new hardware
 
  


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
Upgrade Slackware 14.1's glibc to the current version moisespedro Slackware 15 12-09-2019 11:43 AM
glibc-2.21 in Slackware-current! Didier Spaier Slackware 1 02-16-2015 09:40 PM
[SOLVED] [Slackware-current]: glibc 2.17; CVE-2013-4332 mancha Slackware 12 11-11-2013 03:08 PM
[Slackware-current] glibc 2.17, shadow, and other penumbrae mancha Slackware 16 10-04-2013 02:59 PM
Problems with glibc on Slackware current? MS3FGX Slackware 2 03-30-2006 09:57 PM

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

All times are GMT -5. The time now is 05:53 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