LinuxQuestions.org
Review your favorite Linux distribution.
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 11-13-2016, 08:20 PM   #1
STDOUBT
Member
 
Registered: May 2010
Location: Stumptown
Distribution: Slackware64
Posts: 583

Rep: Reputation: 242Reputation: 242Reputation: 242
Unhappy Possible to find an old firmware package?


Greetings all!

For a reason (edge case?, unconfirmed bug I think I'm experiencing),
I would like to revert to kernel-firmware-20160924git-noarch-1.txz.
I can no longer find this package on the mirrors since it was upgraded in -Current.
What happens to these "interim" packages?

Foolishly, I allowed slackpkg to upgrade this thing which has been the best I've used so far.
While using kernel-firmware-20160924git-noarch-1.txz, I never once experienced the dreaded "black screen" upon resume from suspend. Since the upgrade I've seen it twice and it's a serious buzzkill.
 
Old 11-13-2016, 08:52 PM   #2
CTM
Member
 
Registered: Apr 2004
Distribution: Slackware
Posts: 308

Rep: Reputation: 287Reputation: 287Reputation: 287
They get deleted from mirrors, so your only option is to find a mirror that hasn't synced with OSUOSL yet (unlikely) or build the package yourself from the kernel-firmware SlackBuild, which is actually quite easy because it just clones and repackages the kernel-firmware Git repository. In the SlackBuild, after cloning the repository, you can roll back to a commit of your choice with:

Code:
git checkout <commit_hash> .
This one should put you back to the state of that package on 2016-09-24:

Code:
git checkout 42ad5367dd38371b2a1bb263b6efa85f9b92fc93 .
 
1 members found this post helpful.
Old 11-13-2016, 08:54 PM   #3
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,371

Rep: Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750
Uploaded from my personal cache. http://expirebox.com/download/b55fe1...07051ce9e.html
Contents of kernel-firmware-20160924git-noarch-1.txz.asc
Code:
-----BEGIN PGP SIGNATURE-----

iEYEABECAAYFAlfnN5MACgkQakRjwEAQIjMAXwCgirjrQrmcWrdLUCye/VfU94Qe
Q+IAn1HJcb2ETxyqMrI/Evwq09w/Ioj0
=BD3C
-----END PGP SIGNATURE-----
Our BDFL does not keep 'stinking old packages'
 
1 members found this post helpful.
Old 11-13-2016, 09:08 PM   #4
CTM
Member
 
Registered: Apr 2004
Distribution: Slackware
Posts: 308

Rep: Reputation: 287Reputation: 287Reputation: 287
Clearly I spoke too soon

Actually, there used to be a guy who maintained a mirror of slackware[64]-current as a git repository in which the commits were ChangeLog entries, which was quite convenient for digging out old stuff. I wonder if I can find that link...
 
Old 11-13-2016, 09:26 PM   #5
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,371

Rep: Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750
Just a long standing practice of mine to run slackpkg with the option to retain files. After using slackpkg, I do 'mv /var/cache/packages /var/cache/packages<date>'. When following -current, it is occasionally useful to be able to easily revert to an old package.
 
1 members found this post helpful.
Old 11-13-2016, 10:32 PM   #6
STDOUBT
Member
 
Registered: May 2010
Location: Stumptown
Distribution: Slackware64
Posts: 583

Original Poster
Rep: Reputation: 242Reputation: 242Reputation: 242
You've all given me a lot to go on.

It is greatly appreciated!
 
Old 11-14-2016, 02:34 AM   #7
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 7,097

Rep: Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174Reputation: 4174
Quote:
Originally Posted by CTM View Post
Actually, there used to be a guy who maintained a mirror of slackware[64]-current as a git repository in which the commits were ChangeLog entries, which was quite convenient for digging out old stuff. I wonder if I can find that link...
http://cgit.notk.org/adrien/slackwar...rrent.ext.git/

but he doesn't archive tarballs, there are just their hashes...
 
2 members found this post helpful.
  


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
[SOLVED] Compiling a newer Slackware 14.1 kernel-firmware package for a laptop? gordydawg Slackware 2 04-24-2014 01:00 PM
Toshiba Satellite A10: BCM94318MPG + b43 Firmware [no package] NiTrOcx Linux - Laptop and Netbook 8 03-10-2013 11:50 AM
[SOLVED] Building linux-firmware package with Pat's slackbuild script Phorize Slackware 8 10-05-2011 05:54 AM
Where to file a bug report for the linux-firmware package MALDATA Arch 1 05-24-2011 06:53 AM
Failure to find E100 firmware even though present in /lib/firmware afhartman Linux - Networking 2 07-27-2009 07:31 AM

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

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