LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
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 07-03-2012, 03:54 PM   #1
Alchemikos
Member
 
Registered: Jun 2012
Location: Porto Alegre-Brazil
Distribution: Slackware- 14, Debian Wheezy, Ubuntu Studio, Tails
Posts: 88

Rep: Reputation: 6
How upgrade the 13.37 to Current if my actual kernel is 3.4.4?


Hello Folks!

The Slackware 14 day is near, and I need to know what's happen when upgrade from a 13.37 running the 3.4.4 kernel?

Downgrade kernel?
Mess?

Thanks

Alchemikos
 
Old 07-03-2012, 04:12 PM   #2
business_kid
Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 6,375

Rep: Reputation: 557Reputation: 557Reputation: 557Reputation: 557Reputation: 557Reputation: 557
if you make sure there's _no_kernel_ showing in /var/log/packages, and run a mass updatepkg, wouldn't you be ok? Make sure you can rescue yourself (BACKUP) before you try it.
 
Old 07-03-2012, 04:13 PM   #3
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
If you were planning to use slackpkg to upgrade to -current just edit /etc/slackpkg/blacklist which tells slackpkg which packages to leave alone. From /etc/slackpkg/blacklist :
Quote:
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below
#
#kernel-firmware
#kernel-generic
#kernel-generic-smp
#kernel-headers
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source
It's pretty straightforward. Now as far as how the system will run, my guess is it will run just fine, but there's only one way to know for sure..........
 
Old 07-03-2012, 04:53 PM   #4
Alchemikos
Member
 
Registered: Jun 2012
Location: Porto Alegre-Brazil
Distribution: Slackware- 14, Debian Wheezy, Ubuntu Studio, Tails
Posts: 88

Original Poster
Rep: Reputation: 6
Firstly Thank's

And if I keep running the kernel 3.4 without edit the blacklist and upgrade the Slack to current via slackpkg, will it works?


Alchemikos
 
Old 07-03-2012, 05:25 PM   #5
lukkon
LQ Newbie
 
Registered: Dec 2011
Distribution: Slackware/Debian
Posts: 27

Rep: Reputation: Disabled
Check installed kernel packages, for example: "ls -l /var/log/packages/ | grep kernel"
if the output is blank you don't have any kernel packages installed, so "slackpkg upgrade-all" will no download and install kernel and you will still have 3.4.4.
If you have kernel packages installed slackpkg will download and install kernel version 3.2.21 and overwrite yours /boot/vmlinuz kernel image.
The safest way is to blacklist kernel packages (just edit the /etc/slackpkg/blacklist file and uncoment lines with "kernel")
 
Old 07-03-2012, 07:01 PM   #6
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,197
Blog Entries: 15

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
The only kernel package you NEED to update is the kernel-headers for GLIBC. The rest can be safely ignored unless you have built other kernel modules.
 
1 members found this post helpful.
Old 07-03-2012, 07:57 PM   #7
Alchemikos
Member
 
Registered: Jun 2012
Location: Porto Alegre-Brazil
Distribution: Slackware- 14, Debian Wheezy, Ubuntu Studio, Tails
Posts: 88

Original Poster
Rep: Reputation: 6
Quote:
Originally Posted by lukkon View Post
Check installed kernel packages, for example: "ls -l /var/log/packages/ | grep kernel"
if the output is blank you don't have any kernel packages installed, so "slackpkg upgrade-all" will no download and install kernel and you will still have 3.4.4.
If you have kernel packages installed slackpkg will download and install kernel version 3.2.21 and overwrite yours /boot/vmlinuz kernel image.
The safest way is to blacklist kernel packages (just edit the /etc/slackpkg/blacklist file and uncoment lines with "kernel")
Quote:
Originally Posted by ReaperX7 View Post
The only kernel package you NEED to update is the kernel-headers for GLIBC. The rest can be safely ignored unless you have built other kernel modules.
I have these packages installed but comes from the old kernel (now i'm using 3.4.4)..Still I using it?

Code:
root@Hackslack:/home/alchemik# ls -l /var/log/packages/ | grep kernel
-rw-r--r-- 1 root root    6134 Jun 27 19:29 kernel-firmware-2.6.37.6-noarch-2
-rw-r--r-- 1 root root    1010 Jun 27 19:29 kernel-generic-2.6.37.6-x86_64-2
-rw-r--r-- 1 root root   21062 Jun 27 19:32 kernel-headers-2.6.37.6-x86-2
-rw-r--r-- 1 root root    1007 Jun 27 19:29 kernel-huge-2.6.37.6-x86_64-2
-rw-r--r-- 1 root root  176299 Jun 27 19:30 kernel-modules-2.6.37.6-x86_64-2
-rw-r--r-- 1 root root 2299643 Jun 27 19:33 kernel-source-2.6.37.6-noarch-2

Last edited by Alchemikos; 07-03-2012 at 07:58 PM.
 
Old 07-03-2012, 08:09 PM   #8
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, FreeBSD 10.0
Posts: 3,197
Blog Entries: 15

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
Unless you update glibc you don't need to install the new kernel headers from the FTP. These two packages are tied together and each version is built just for that specific version of the kernel released with Slackware.
 
1 members found this post helpful.
Old 07-03-2012, 08:18 PM   #9
BCarey
Senior Member
 
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,455

Rep: Reputation: Disabled
For kernel-generic, huge, modules and source you can safely remove them since you are running 3.4.4. For headers and firmware you should upgrade them when you upgrade to current.

Actually, I don't think that upgrading the other kernel packages should cause a problem either as long as you don't use /boot/vmlinuz as a link to your 3.4.4 kernel. When you install/upgrade the install copies the new kernels into /boot and changes the symbolic link /boot/vmlinuz to point to the new kernel. lilo uses /boot/vmlinuz, that way lilo.conf does not need to be updated when upgrading slackware kernels.

Personally I do not create a symbolic link for my non-slack kernels but rather in lilo I specify the kernel directly. That way I don't care what /boot/vmlinuz points to and it is easier to have multiple kernels installed at the same time.

Brian

Last edited by BCarey; 07-03-2012 at 08:20 PM.
 
Old 07-03-2012, 09:45 PM   #10
Alchemikos
Member
 
Registered: Jun 2012
Location: Porto Alegre-Brazil
Distribution: Slackware- 14, Debian Wheezy, Ubuntu Studio, Tails
Posts: 88

Original Poster
Rep: Reputation: 6
Hi guys!

My last step was:

Code:
slackpkg install-new
And my error list:
Code:
	ERROR - Package not installed! gpg error!

Searching for NEW configuration files
		No .new files found.
         

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while slackpkg was running:                       

llvm-3.0-x86_64-1.txz:	gpg
marble-4.8.4-x86_64-1.txz:	gpg
mobile-broadband-provider-info-20120614-x86_64-1.txz:	gpg
mtdev-1.1.2-x86_64-1.txz:	gpg
networkmanagement-0.9.0-x86_64-1.txz:	gpg
okular-4.8.4-x86_64-1.txz:	gpg
oxygen-gtk2-1.2.5-x86_64-1.txz:	gpg
parley-4.8.4-x86_64-1.txz:	gpg
perlkde-4.8.4-x86_64-1.txz:	gpg
perlqt-4.8.4-x86_64-1.txz:	gpg
phonon-gstreamer-4.6.0-x86_64-1.txz:	gpg
phonon-xine-4.4.4-x86_64-1.txz:	gpg
polkit-kde-agent-1-9d74ae3_20120104git-x86_64-1.txz:	gpg
polkit-kde-kcmodules-1-001bdf7_20120111git-x86_64-1.txz:	gpg
polkit-qt-1-0.103.0-x86_64-1.txz:	gpg
printer-applet-4.8.4-x86_64-1.txz:	gpg
pycurl-7.19.0-x86_64-1.txz:	gpg
pykde4-4.8.4-x86_64-1.txz:	gpg
qtruby-4.8.4-x86_64-1.txz:	gpg
quanta-29a3f8e_20111223git-x86_64-1.txz:	gpg
raptor2-2.0.7-x86_64-1.txz:	gpg
rocs-4.8.4-x86_64-1.txz:	gpg
sg3_utils-1.33-x86_64-1.txz:	gpg
smokegen-4.8.4-x86_64-1.txz:	gpg
smokekde-4.8.4-x86_64-1.txz:	gpg
smokeqt-4.8.4-x86_64-1.txz:	gpg
soma-2.7.1-noarch-1.txz:	gpg
step-4.8.4-x86_64-1.txz:	gpg
superkaramba-4.8.4-x86_64-1.txz:	gpg
svgpart-4.8.4-x86_64-1.txz:	gpg
sweeper-4.8.4-x86_64-1.txz:	gpg
transset-1.0.0-x86_64-1.txz:	gpg
udisks-1.0.4-x86_64-1.txz:	gpg
upower-0.9.16-x86_64-1.txz:	gpg
wicd-kde-0.3.0_bcf27d8-x86_64-1.txz:	gpg
xcb-util-image-0.3.9-x86_64-1.txz:	gpg
xcb-util-keysyms-0.3.9-x86_64-1.txz:	gpg
xcb-util-renderutil-0.3.8-x86_64-1.txz:	gpg
xcb-util-wm-0.3.9-x86_64-1.txz:	gpg
xf86-video-modesetting-0.4.0-x86_64-1.txz:	gpg

==============================================================================
I don't use or did installed KDE, I use the XFCE 4.6, so I unchecked the KDE stuffs that I don't use, I use just Okular, K3B, Ksnapshot

And now

Last edited by Alchemikos; 07-03-2012 at 09:55 PM.
 
Old 07-03-2012, 10:30 PM   #11
fogpipe
Member
 
Registered: Mar 2011
Distribution: Slackware 64 Current
Posts: 329

Rep: Reputation: 77
Im running kernel 3.4.1 with no problem. After you install the 3.4 kernel uncheck all the kernel packages when you update thereafter. If you are using lilo its pretty easy to boot different kernel images. Here is an excerpt from my lilo.conf:

Code:
image = /boot/vmlinuz
     root = /dev/sda1
     label = 1337
    append = "video=640x480"
   #  initrd = /boot/initrd
     read-only
image = /boot/vmlinuz-huge-2.6.37.6
     root = /dev/sda1
     label = hugeslack
    append = "video=640x480"
   #  initrd = /boot/initrd
     read-only
If you arent naming your kernel image and system.map vmlinuz and System.map, just make sure that the version numbers are appended to vmlinuz and System.map and that the version numbers match the version numbers for the /lib/modules dir for that kernel.
 
Old 07-03-2012, 11:00 PM   #12
Alchemikos
Member
 
Registered: Jun 2012
Location: Porto Alegre-Brazil
Distribution: Slackware- 14, Debian Wheezy, Ubuntu Studio, Tails
Posts: 88

Original Poster
Rep: Reputation: 6
When I try the:

Code:
slackpkg upgrade-all
Returns:

Code:
You need the GPG key of Slackware Linux Project <security@slackware.com>.
To download and install that key, run:

	# slackpkg update gpg

You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.

How can I start again?

Thanks
 
Old 07-04-2012, 12:23 AM   #13
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
Have you tried
Code:
slackpkg update gpg
as the message suggests?
 
Old 07-04-2012, 12:28 AM   #14
Alchemikos
Member
 
Registered: Jun 2012
Location: Porto Alegre-Brazil
Distribution: Slackware- 14, Debian Wheezy, Ubuntu Studio, Tails
Posts: 88

Original Poster
Rep: Reputation: 6
Quote:
Originally Posted by TobiSGD View Post
Have you tried
Code:
slackpkg update gpg
as the message suggests?
Yes TobiSGD, I did it...

Does some Kernel 3.4.4 conflict?


Alchemikos
 
Old 07-04-2012, 12:30 AM   #15
TobiSGD
Moderator
 
Registered: Dec 2009
Location: Hanover, Germany
Distribution: Main: Gentoo Others: What fits the task
Posts: 15,592
Blog Entries: 2

Rep: Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046Reputation: 4046
What were the exact steps you made to upgrade the system and when exactly did you get errors?
There shouldn't be incompatibilities with the newer kernel.
 
  


Reply

Tags
kernel, slackware -current, slackware 13.37, upgrade


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] How do I upgrade from current kernel of 2.6.17-2 to at least 2.6.18? boomer42812 Linux - Newbie 4 12-10-2010 10:12 AM
Why upgrade kernel is current one works? acithium Linux - General 6 07-14-2008 11:06 AM
How to upgrade to -current ? New udev for new kernel !? introuble Slackware 8 04-21-2006 02:47 PM
What first upgrade kernel or upgrade slack 10.0 to current Kelean Slackware 7 01-16-2005 06:54 PM
I need to upgrade my current Kernel xmdms Linux - Software 2 05-06-2004 04:58 PM


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