LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   How upgrade the 13.37 to Current if my actual kernel is 3.4.4? (http://www.linuxquestions.org/questions/slackware-14/how-upgrade-the-13-37-to-current-if-my-actual-kernel-is-3-4-4-a-4175414731/)

Alchemikos 07-03-2012 03:54 PM

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

business_kid 07-03-2012 04:12 PM

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.

damgar 07-03-2012 04:13 PM

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..........

Alchemikos 07-03-2012 04:53 PM

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

lukkon 07-03-2012 05:25 PM

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")

ReaperX7 07-03-2012 07:01 PM

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.

Alchemikos 07-03-2012 07:57 PM

Quote:

Originally Posted by lukkon (Post 4718531)
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 (Post 4718573)
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


ReaperX7 07-03-2012 08:09 PM

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.

BCarey 07-03-2012 08:18 PM

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

Alchemikos 07-03-2012 09:45 PM

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 :(

fogpipe 07-03-2012 10:30 PM

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.

Alchemikos 07-03-2012 11:00 PM

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

TobiSGD 07-04-2012 12:23 AM

Have you tried
Code:

slackpkg update gpg
as the message suggests?

Alchemikos 07-04-2012 12:28 AM

Quote:

Originally Posted by TobiSGD (Post 4718757)
Have you tried
Code:

slackpkg update gpg
as the message suggests?

Yes TobiSGD, I did it...

Does some Kernel 3.4.4 conflict?


Alchemikos

TobiSGD 07-04-2012 12:30 AM

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.


All times are GMT -5. The time now is 05:14 AM.