LinuxQuestions.org
Visit Jeremy's Blog.
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 06-28-2020, 09:25 PM   #1
jr_bob_dobbs
Member
 
Registered: Mar 2009
Distribution: Slackware,Linux From Scratch
Posts: 443
Blog Entries: 64

Rep: Reputation: 75
Slackware 64 Current: upgrading just the kernel


Right now I've got a comfy Slackware install, which I installed in March. All of the programs I like are in and working. Wine is running some programs that it was never able to run before: I am even able to run a few games (real games, full-on 3d games, not minesweeper). This may be the best Linux install ever!

There are two problems (which may or may not be one problem). One: lid close then open freezes the computer. Two: randomly, tapping a key to turn the screen on after being away from the keyboard causes an immediate reboot.

I'm thinking this is caused by some kernel and/or firmware bug, because I've used different Linux installs (and a windows install) on this same computer without this problem.

Since my current install is otherwise so perfectly tuned, I don't want to upgrade anything except for the kernel & firmware.

My idea is to upgrade *just* the kernel and firmware. In the past, I did this by one of two methods. One: grab a newer kernel source and rebuild the kernel & modules. Two: a fresh install of a newer version of the operating system.

The odd thing is, while I know how to compile a kernel, I don't how to upgrade a pre-compiled kernel within Slackware. Also I do not know the exact packages needed to upgrade using the Slackware packages!

Near as I can tell, if I manually get the latest Current of only the following packages, I should be able to install them, without touching the existing kernel, modules & firmware:
  • kernel-firmware
  • kernel-generic
  • kernel-huge
  • kernel-modules
  • kernel-source

The source probably isn't needed, I don't know for sure. I realize that I do not need both huge and generic. I normally use generic ... but I like the idea of having huge as a fallback. I don't need to upgrade kernel headers.

So my actual question is: is simply grabbing and installing those packages (from Current), generating the new initrd and then updating lilo going to achieve my goal of a new kernel in a March install of Slackware?

Thank you.
 
Old 06-28-2020, 10:03 PM   #2
cwizardone
LQ Guru
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 5,700
Blog Entries: 1

Rep: Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049Reputation: 3049
It should.

You would want,
/a/kernel-generic
/a/kernel-huge
/a/kernel-modules
/d/kernel-headers
/k/kernel-source
and
/a/kernel-firmware
if you need it.

Then run, installpkg
on the first five and
upgradepkg --reinstall --install-new
on the firmware update.

In /boot, run, mkinitrd (add your options)
if you are going to use the generic kernel.

Then edit your /etc/lilo.conf
run, lilo
and reboot.

You may have to reinstall your graphics driver and VirtualBox.

If you build any packages you may need both the headers and the source.

By using, installpkg
your new kernel can happily co-exist with your old kernel.
If you duplicate the entries for your old kernel in your lilo.conf for your new kernel, with the appropriate changes, of course, you will be able to choose, at boot up, your new kernel or your old kernel. If something goes wrong with the new kernel installation, you can always boot the old kernel and still have a working computer while you sort out the problem.

Last edited by cwizardone; 06-28-2020 at 10:30 PM.
 
Old 06-28-2020, 10:55 PM   #3
RedBlueYellow12
LQ Newbie
 
Registered: Aug 2019
Location: Melbourne, Australia
Distribution: Slackware
Posts: 27

Rep: Reputation: Disabled
It should; there's about five different kernels in my lilo from previous upgrades, just in case something broke. There's no need to purge the old ones, they don't take up much space anyway.
Doesn't compiling some things break if your headers aren't the same version though?

Last edited by RedBlueYellow12; 06-28-2020 at 10:57 PM.
 
1 members found this post helpful.
  


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
[SOLVED] Problem upgrading latest Slackware 64-current to kernel 5.4.29 gauchao Slackware 9 04-03-2020 10:04 AM
[SOLVED] Slackware 14.2 glibc-2.23 vs Slackware Current glibc-2.24 and the Current 4.4.17 Kernel kjhambrick Slackware 10 08-13-2016 01:00 AM
Kernel panic after upgrading slackware64-current to 2.6.32.x kernel Lenard Spencer Slackware 4 01-22-2010 10:54 AM
Slackware64 -current vs Slackware -current or Slackware onebuck Slackware 16 06-23-2009 01:19 PM

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

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