LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
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 02-09-2019, 02:22 PM   #1
alpage2
LQ Newbie
 
Registered: Sep 2003
Location: North-East UK
Distribution: Mandrake 9.1
Posts: 15

Rep: Reputation: 0
Instructions for Updates to Generic Kernel


Is there a clear set of blow-by-blow instructions available for installing routine kernel upgrades for someone running with the generic kernel? I have searched in the forums and the slack docs, but couldn't find exactly this.

The slackware beginners_guide has a great set of instructions for switching to the generic kernel, and it is something in this detail that I am looking for so that I don't end up with an unbootable system every time a routine kernel upgrade comes along.

Thanks in anticipation.
Alan
 
Old 02-09-2019, 03:04 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 3,930

Rep: Reputation: 1185Reputation: 1185Reputation: 1185Reputation: 1185Reputation: 1185Reputation: 1185Reputation: 1185Reputation: 1185Reputation: 1185
upgrade kernel
run /usr/share/mkinitrd/mkinitrd_command_generator.sh -k <kernel-version>
execute the output of the above command
run lilo or grub-mkconfig
 
1 members found this post helpful.
Old 02-09-2019, 03:05 PM   #3
Okie
Senior Member
 
Registered: Mar 2002
Location: Oklahoma
Posts: 1,050

Rep: Reputation: 97
building your own kernel is a risky endeavor, and if you dont do it just right you can end up with a slackware install that wont boot, or the very least something wont work,

what i do once i get the kernel source installed i cd to /usr/src/linux, run make localmodconfig, then run make menuconfig and look through it to make sure the the things i need are selected which is a long and tedious chore then save & exit, run make then make install then make modules_install and recently grub wont boot my rebuilt kernel and i have since swiched back to lilo for a bootloader

like i said this is a risky thing to do if you are unfamiliar with building a kernel so do it at your own risk because if you dont do everything correctly you will have a unbootable system, and the benefits are basically just a slightly smaller kernel that boots a little faster so it is almost not worth the trouble, if you have plenty of disk space you might want to do another install of slackware and just dual boot slackware with another install of slackware for testing to learn building kernels on so if it goes badly you dont mess up your main working slackware install

good luck and may the source be with you
 
Old 02-09-2019, 11:46 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: Carrollton, Texas
Distribution: Slackware64 14.2
Posts: 3,184

Rep: Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549Reputation: 1549
Quote:
Originally Posted by alpage2 View Post
Is there a clear set of blow-by-blow instructions available for installing routine kernel upgrades for someone running with the generic kernel? I have searched in the forums and the slack docs, but couldn't find exactly this.

The slackware beginners_guide has a great set of instructions for switching to the generic kernel, and it is something in this detail that I am looking for so that I don't end up with an unbootable system every time a routine kernel upgrade comes along.

Thanks in anticipation.
Alan
Do you have intel processors on your machines or AMD?
Does your motherboard use BIOS boot or EFI boot?
Do you want to use lilo, elilo, or grub to boot?
 
Old 02-10-2019, 08:00 AM   #5
rkfb
Member
 
Registered: Oct 2003
Location: Guildford, England
Distribution: Slackware64 current running TWM
Posts: 453

Rep: Reputation: 116Reputation: 116
I would advocate installing the new kernel, rather than upgrading to it.

If you then leave your old working kernel as the default one to boot (in for instance lilo or grub) and have the new kernel as one you have to select to boot you should be able to guard against any issues with the new kernel failing.
 
Old 02-10-2019, 08:41 AM   #6
alpage2
LQ Newbie
 
Registered: Sep 2003
Location: North-East UK
Distribution: Mandrake 9.1
Posts: 15

Original Poster
Rep: Reputation: 0
Instructions for Updates to Generic Kernel

Many thanks to all responders. I think my loose terminology has given the wrong impression in some cases. I was not referring to building my own kernel - just installing the routine updates by:

Code:
slackpkg update
followed by:

Code:
slackpkg upgrade-all
I am guessing that the commands offered by willysr are the answer that I was looking for?

Thanks again for all the help!
Alan
 
Old 02-10-2019, 09:00 AM   #7
rkfb
Member
 
Registered: Oct 2003
Location: Guildford, England
Distribution: Slackware64 current running TWM
Posts: 453

Rep: Reputation: 116Reputation: 116
Although this is where you could run in to problems if the new kernel won't boot.

Better to blacklist kernel updates (see the file /etc/slackpkg/blacklist for information (you may have to add kernel-headers)) then download the new kernel manually from your preferred source (find the various packages in a/, d/ and k/). You can then install them manually using installpkg rather than upgrading via slackpkg and if you follow my previous suggesion of leaving the old kernel as the default one to boot then if you do run in to any problems you will still have a working computer.
 
Old 02-10-2019, 09:51 AM   #8
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 438
Blog Entries: 3

Rep: Reputation: 113Reputation: 113
Instructions for Updates to Generic Kernel

+1 for blacklisting kernel packages

You could automate the download of the new kernel with a rsync script and the install, and in the row parse the kernel version, build your initrd and update your lilo or grub.

Just saying : I do this by hand, assuming I mirror the Slackware repo and have a mkinitrd.conf that is well completed.
It's like :
Code:
 
installpkg /my_local_repo/*/kernel*.t?z
mkinitrd -F -k $kernel_version 
grub-mkconfig -o /boot/grub/grub.cfg
 
Old 02-10-2019, 04:04 PM   #9
bormant
Member
 
Registered: Jan 2008
Posts: 321

Rep: Reputation: 181Reputation: 181
@Tonus,
why rsync,
slackpkg download kernel
does the trick.
 
  


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] setting up initrd / generic kernel in Grub2...can't load generic Ubunoob001 Slackware 12 03-20-2015 08:32 AM
kernel-generic and kernel-generic-smp ?? liuyug Slackware - Installation 5 06-01-2014 08:01 PM
Update from 2.6.27-13-generic to 2.6.27-14-generic fails bobreeves Linux - Kernel 1 03-19-2009 10:02 AM
GART TLB error generic level generic Clydesdale Linux - Software 1 08-13-2007 07:47 PM
GART TLB error generic level generic Clydesdale Linux - Hardware 0 08-13-2007 07:18 PM

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

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