LinuxQuestions.org
Visit the LQ Articles and Editorials section
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 05-20-2005, 10:50 AM   #1
cavalier
Member
 
Registered: Feb 2005
Location: Denver, CO
Distribution: Slack 12, tweaked just so (though I'm also a fan of Ubuntu)
Posts: 198
Blog Entries: 1

Rep: Reputation: 30
upgrading the kernel using slackpkg


I've found that slackpkg does a nice job of keeping me up to date with -current. However, by default it also upgrades the kernel from the old 10.1 default of 2.4.29 to 2.4.30. No real gripe there, as it seems to actually work pretty well.

My issue comes from the fact that, when I installed 10.1, I chose the bareacpi.i kernel, and it does everything I want it to, but when I upgrade using slackpkg, I think I must be getting saddled with the bare.i kernel intead, as ACPI fails to load.

Am I missing a step?
 
Old 05-20-2005, 11:13 AM   #2
AxeZ
Member
 
Registered: Sep 2002
Location: Novi Sad, Vojvodina
Distribution: Slackware, FreeBSD
Posts: 386

Rep: Reputation: 32
Re: upgrading the kernel using slackpkg

Quote:
Originally posted by cavalier
Am I missing a step? [/B]

Well, yes.......why would anybody want to upgrade his kernel with automatic upgrade tool on Linux??????
Besides the fact that the kernel is single most important piece of software in your OS...why don't you upgrade it manualy.
 
Old 05-20-2005, 11:22 AM   #3
dunric
Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 441

Rep: Reputation: 51
Slackpkg is designed for automated installation/upgrading of packages. There is only 1 package containing gerneric kernel and only 1 containg modules for this kernel. Kernel with built in ACPI support is not in a package and can be found and maunaly installed from <slackware-repository>/slackware-current/kernels/bareacpi.i/ URL.

Good luck ;-)
 
Old 05-20-2005, 11:35 AM   #4
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 51
Just to avoid headaches, remember to run lilo after updating the kernel
 
Old 05-20-2005, 11:44 AM   #5
nukey
Member
 
Registered: Dec 2004
Location: Netherlands
Distribution: Slackware
Posts: 173

Rep: Reputation: 30
Quote:
Originally posted by gbonvehi
Just to avoid headaches, remember to run lilo after updating the kernel
slackpkg will ask if it should run it

Upgrading the kernel autmaticly isn't use-full when you have a custom kernel, when you use a standard kernel it's no problem and works perfectly.

Also take a look at the /etc/slackpkg/blacklist file.

Here you can put the packages you never want to have automaticly updated. (with the kernel being one of the packages you may want to blacklist).
 
Old 05-20-2005, 02:40 PM   #6
cavalier
Member
 
Registered: Feb 2005
Location: Denver, CO
Distribution: Slack 12, tweaked just so (though I'm also a fan of Ubuntu)
Posts: 198
Blog Entries: 1

Original Poster
Rep: Reputation: 30
To answer several questions at once...

1. I, for one, look forward to using an automatic tool to upgrade my kernel. Yes, I'm an old hand Linux hacker from the pre 1.0 kernel days. Yes, I can compile a kernel. But why, when bareacpi.i does the trick, should I waste the time? So yes, I'd like it if the kernel package included some options for other stock kernels.

But then, maybe that's not very Slackware of me, honestly. Using slackpkg at all really goes against the grain of the Slackware way of thinking.

2. Anybody got a pointer to instructions on replacing the 2.4.30 bare kernel with the 2.4.30 bareacpi kernel if I download bareacpi.i from -current?
 
Old 05-22-2005, 05:03 AM   #7
nukey
Member
 
Registered: Dec 2004
Location: Netherlands
Distribution: Slackware
Posts: 173

Rep: Reputation: 30
Quote:
Originally posted by cavalier
Using slackpkg at all really goes against the grain of the Slackware way of thinking.
Can you explain that ?

What else should be the (easy) way of keeping your system up to date ?
 
Old 05-22-2005, 09:46 PM   #8
detpenguin
Senior Member
 
Registered: Oct 2003
Location: lost in the midwest...
Distribution: Slackware
Posts: 1,091

Rep: Reputation: 45
slackpkg has a blacklist which you can modify so that it won't install the kernels...i have it set to not install the kernels and any alsa drivers made for the new kernels after having a few problems with that...

the blacklist file is at /etc/slackpkg/blacklist and it's pretty self-explanatory...
 
Old 05-22-2005, 09:50 PM   #9
detpenguin
Senior Member
 
Registered: Oct 2003
Location: lost in the midwest...
Distribution: Slackware
Posts: 1,091

Rep: Reputation: 45
Quote:
But then, maybe that's not very Slackware of me, honestly. Using slackpkg at all really goes against the grain of the Slackware way of thinking.
slackpkg doesn't go against the slackware way of thinking at all, as it uses the official slackware packages directly from the slackware site, and uses slackpkg which pat found stable enough to include in the extras...to me anyways, slackpkg is very slackware...it keeps my distro current and running great.
 
Old 05-22-2005, 09:59 PM   #10
cavalier
Member
 
Registered: Feb 2005
Location: Denver, CO
Distribution: Slack 12, tweaked just so (though I'm also a fan of Ubuntu)
Posts: 198
Blog Entries: 1

Original Poster
Rep: Reputation: 30
I will grant you that, using the native packaging system, it's not as "bad" as apt or yum, but anything that's automated just doesn't feel very Slackware. Slackware is all about doing it by hand, after all.

That said, I've already added the kernel to the blacklist, to avoid this in the future.
 
Old 05-23-2005, 04:51 AM   #11
cathectic
Member
 
Registered: Sep 2004
Location: UK, Europe
Distribution: Slackware64
Posts: 761

Rep: Reputation: 34
Also add:

aaa_base
aaa_elflibs
alsa-driver
alsa-lib
alsa-utils

to your blacklist - the aaa series are only for fresh installations, the alsa driver is kernel dependent, and should only be upgraded along with the kernel.
 
Old 05-23-2005, 03:13 PM   #12
gargamel
Senior Member
 
Registered: May 2003
Distribution: Slackware, SLAX, OpenSuSE
Posts: 1,593

Rep: Reputation: 142Reputation: 142
Quote:
Originally posted by cavalier
I will grant you that, using the native packaging system, it's not as "bad" as apt or yum, but anything that's automated just doesn't feel very Slackware. Slackware is all about doing it by hand, after all.

That said, I've already added the kernel to the blacklist, to avoid this in the future.

What you describe is Linux from Scratch, not Slackware. ;-)

Slackware's principle is KISS, not "make it as cumbersome as it possibly can be". slackpkg is good and reliable. And as much as I like to learn how everything works in Linux system, there is not much instructive in installing a binary kernel package by hand. You can make many mistakes, without learning something useful. (I think the same about X configuration, and I wouldn't mind to see a better tool than xorgconfig et al. ...)

Regarding your problem: Did you check which modules are loaded? When upgrading the kernel with slackpkg it can happen that a new configuration file (/etc/rc.d/rc.modules or so) is installed that doesn't load the right modules. Do the modules match your kernel (2.4 vs 2.6)?


Good luck
gargamel
 
Old 05-23-2005, 04:01 PM   #13
cavalier
Member
 
Registered: Feb 2005
Location: Denver, CO
Distribution: Slack 12, tweaked just so (though I'm also a fan of Ubuntu)
Posts: 198
Blog Entries: 1

Original Poster
Rep: Reputation: 30
Quote:
Originally posted by gargamel
Regarding your problem: Did you check which modules are loaded? When upgrading the kernel with slackpkg it can happen that a new configuration file (/etc/rc.d/rc.modules or so) is installed that doesn't load the right modules. Do the modules match your kernel (2.4 vs 2.6)?
Yes, the kernel and the modules were all 2.4.30. It's just the default assumption by slackpkg, on installation of the kernel, that you want the bare.i version. Were it to ask me, as it had during setup, that would be useful. Instead, I'll sit tight until I find the time to configure and build my own 2.6 kernel.
 
Old 05-23-2005, 04:11 PM   #14
gbonvehi
Senior Member
 
Registered: Jun 2004
Location: Argentina (SR, LP)
Distribution: Slackware
Posts: 3,145

Rep: Reputation: 51
Quote:
Originally posted by cavalier

2. Anybody got a pointer to instructions on replacing the 2.4.30 bare kernel with the 2.4.30 bareacpi kernel if I download bareacpi.i from -current?
Yes, just goto http://ftp.scarlet.be/pub/slackware/...ls/bareacpi.i/ or some other mirror but to the same directory, download the three files, gzip -d System.map.gz and replace the bare kernel you got from the package (or you could add anoher entry in lilo).
These are the files that you get when getting the new slackware package, replace vmlinuz with bzImage and the other two with their respective file.
/boot/System.map-ide-2.4.30
/boot/config-ide-2.4.30
/boot/vmlinuz-ide-2.4.30
After that re-run lilo.
 
Old 05-27-2005, 04:31 PM   #15
halo14
Senior Member
 
Registered: Apr 2004
Location: Surprise, AZ
Distribution: Debian | CentOS | Arch
Posts: 1,103

Rep: Reputation: 45
am I correct in understanding that slackpkg will only upgrade 1 package at a time??

There is no way to bring your system fully up-to-date with slackpkg via a single command such as with swaret, issueing 'swaret --update' and 'swaret --upgrade' will install all the need-to-be updated packages??
 
  


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
swaret and slackpkg lodder Slackware 5 10-14-2005 04:37 AM
Warning! Slackpkg walkingbeard Slackware 6 09-18-2005 09:17 PM
SuperKaramba 3.71 slackpkg adds2one Slackware 2 09-04-2005 04:23 PM
problems occured after upgrading kernel and kernel-utils parv Fedora 0 05-02-2005 06:21 PM
Upgrading kernel on Debian from 2.4 to 2.6.8, Kernel Panic omlette Linux - General 3 03-07-2005 07:00 AM


All times are GMT -5. The time now is 02:08 PM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration