LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
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 04-20-2019, 01:11 PM   #1
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
Slackware64.12 linux-4.4.172 why it was broken at upgrade.


This discussion Caused me a write up because. I was pissed that stuff broke for no reason.

Upgrade from 4.4.157 to 4.4.172. now nothing builds none of the Virtual box stuff. none of the Nvidia drivers till Nvidia turned the warning off.

It was a Slackpkg pkgtool issue.
The reason why Pat could not see the problem is because he uses fresh system upgrade to another.
And as we all see now the way Pat is building the kernel in current will fix this issue.

pkgtool is leaving old files.
So after testing the issue over and over. and was able to repeat the issue.
Upgrading from 4.4.157 to 4.4.172 left old headers and you never know because pkgtool did it's job did not delete them installing new ones or over write them. It is a pkgtool issue.
 
Old 04-21-2019, 11:54 PM   #2
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by Drakeo View Post
Upgrading from 4.4.157 to 4.4.172 left old headers and you never know because pkgtool did it's job did not delete them installing new ones or over write them. It is a pkgtool issue.
Do you have more information on this? Because by design, there should be no leftover files unless they were renamed in the doinst.sh or they belong to multiple packages (or it was generated after the package was created).

I was under the impression the issue was due to the kernel developers changing ABI on an LTS kernel due to some issue, but I can't remember what it is.

I haven't run a 4.4.x kernel on my 14.2 system for like 2 years, so I can't comment on this specific issue, but I've never seen a problem with upgrading packages unless it was one of the two instances I mention above.
 
1 members found this post helpful.
Old 04-24-2019, 11:48 AM   #3
akimmet
Member
 
Registered: Jul 2018
Location: NW Ohio, USA
Distribution: Slackware64 -current
Posts: 62

Rep: Reputation: 62
Bassmadrigal is correct, this problem is due to a kernel ABI change with 4.4.172.
There are many threads already here about this particular issue.
I haven't had any issues since nVidia updated their drivers to work with newer 4.4.x kernels.
Since I don't use VirtualBox, I don't know if they ever fixed their kernel drivers.
 
Old 04-26-2019, 11:33 PM   #4
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716

Original Poster
Blog Entries: 3

Rep: Reputation: 483Reputation: 483Reputation: 483Reputation: 483Reputation: 483
Hi bassmadrigal yes some of the headers stayed the same. did not change.
When I built it and did a make install_headers that
fixed the problem so the headers package seems to be the issue.

The other way I tested it was to actual rm -rf /usr/include/linux
Then upgrade to the new kernels and header package.
and all problems fixed.
So that pointed me to headers package not deleting some of headers.
Do not know the exact ones you can do it.
Found my fix.
Glad you had know problems all my fresh install on on Vbox had the same issues.
for building guest additions.
and both pc I have with slackware 14.2 I can reproduce it.
with the older Nvidia drivers and VBox
I am glad you had no issues.
But like I said I can reproduce this issue over and over.

Last edited by Drakeo; 04-26-2019 at 11:37 PM.
 
Old 04-27-2019, 12:34 AM   #5
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,792

Rep: Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656Reputation: 6656
Quote:
Originally Posted by Drakeo View Post
Hi bassmadrigal yes some of the headers stayed the same. did not change.
When I built it and did a make install_headers that
fixed the problem so the headers package seems to be the issue.

The other way I tested it was to actual rm -rf /usr/include/linux
Then upgrade to the new kernels and header package.
and all problems fixed.
So that pointed me to headers package not deleting some of headers.
Do not know the exact ones you can do it.
Found my fix.
Glad you had know problems all my fresh install on on Vbox had the same issues.
for building guest additions.
and both pc I have with slackware 14.2 I can reproduce it.
with the older Nvidia drivers and VBox
I am glad you had no issues.
But like I said I can reproduce this issue over and over.
If you can produce it over and over, can you provide some of the files that were not deleted by removepkg/upgradepkg (instead of deleting /usr/include/linux/, move it somewhere else and then run make install_headers and compare the difference between the directories)? This is the first I've ever heard of this issue and looking through the code of removepkg, I don't understand how it could happen.
 
Old 04-27-2019, 06:38 PM   #6
Poprocks
Member
 
Registered: Sep 2003
Location: Toronto, Canada
Distribution: Slackware
Posts: 522

Rep: Reputation: 279Reputation: 279Reputation: 279
As much as I'm getting tired of hearing these complaints, the kernel maintainers breaking ABI from *patchlevel* releases is pretty lame.
 
  


Reply



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
Nvidia driver 390.87 install fails after update to Linux 4.4.172 ProzacR Slackware 1 02-01-2019 03:46 PM
Why is traceroute failing at 172.16.7.2 postcd Linux - Networking 5 03-03-2016 09:01 AM
LXer: Softpedia Linux Weekly, Issue 172 LXer Syndicated Linux News 0 11-06-2011 05:50 PM
wdb Error: Can't open display: 172.16.1.28:0 murugesan Linux - Networking 4 02-19-2004 04:01 AM

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

All times are GMT -5. The time now is 06:11 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
Open Source Consulting | Domain Registration