[SOLVED] How to switch from huge kernel to 2.6.38.4 kernel ?

Jullia · 06-22-2011, 09:42 PM

Hi

Fresh and Full install: Slackware 13.37 64-bit x86_64.
What is the correct procedure to switch from huge kernel to 2.6.38.4 kernel?

Thanks.

cfdisk · 06-22-2011, 10:10 PM

sure
http://www.linuxquestions.org/questi...kernel-886634/

dc_eros · 06-22-2011, 10:24 PM

On the installer, there is README.initrd file. I usually use it as a guide to switch to generic kernel.

Jullia · 06-23-2011, 11:35 AM

Here's what I did

# cd /media/SlackDVD/testing/packages/
# installpkg *2.6.38.4*txz
# mkinitrd -c -k 2.6.38.4 -f ext4 -r /dev/sda2 -m jbd2:mbcache:ext4 -u -o /boot/initrd.gz

editing lilo
# vi /etc/lilo.conf

# Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.38.4
initrd = /boot/initrd.gz
root = /dev/sda2
label = Lnx26384
read-only
# Linux bootable partition config ends

$ uname -r
2.6.38.4

So now, when i'm # slackpkg upgrade-all, I have this message:

Code:

Checking local integrity... DONE
You have a broken /var/log/packages - with two versions of the same package.
The list of packages duplicated in your machine are shown below, but don't
worry about this list - when you select your action, slackpkg will show a
better list:

kernel-firmware-2.6.37.6-noarch-2
kernel-firmware-2.6.38.4-noarch-1
kernel-generic-2.6.37.6-x86_64-2
kernel-generic-2.6.38.4-x86_64-1
kernel-headers-2.6.37.6-x86-2
kernel-headers-2.6.38.4-x86-1
kernel-huge-2.6.37.6-x86_64-2
kernel-huge-2.6.38.4-x86_64-1
kernel-modules-2.6.37.6-x86_64-2
kernel-modules-2.6.38.4-x86_64-1
kernel-source-2.6.37.6-noarch-2
kernel-source-2.6.38.4-noarch-1

You can (B)lacklist, (R)emove, or (I)gnore these packages.
Select your action (B/R/I):

What should I do? Is the procedure I followed was correct?
.

dimm0k · 06-23-2011, 12:59 PM

When you issued the "installpkg *2.6.38.4*txz", you basically installed 2.6.38.4 alongside whatever kernel you already had installed on your system. In this case it was 2.6.37.6. Also from the looks of it, you've restarted your system and booted successfully into the new kernel so you can remove the older kernel if space is tight... Usually I would follow the same steps you did so that the current kernel I'm running is there for backup in case the new kernel doesn't work well for whatever reason. It's nice to have at least one kernel that's been tested to run well as a backup in my opinion.

brianL · 06-23-2011, 01:01 PM

Uncomment these lines (delete the #) in /etc/slackpkg/blacklist:

Code:

#kernel-firmware
#kernel-generic
#kernel-generic-smp
#kernel-headers
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source

Jullia · 06-23-2011, 03:33 PM

Thank you all.