[SOLVED] how can I switch kernel, SlackWare 13.37

TroN-0074 · 06-30-2012, 10:34 AM

I am trying to boot my slackware installation with the generic kernel. I need to see if that will fix my wireless connection problems.

Currently I have been booting using the huge kernel here is the slakware entry in grub

Code:

###Don't change this comment - YaST2 identifier: Original name: linux###
title SlackWare 13.37
    root (hd0,4)
    kernel /boot/vmlinuz-huge-2.6.37.6 root=/dev/sda5
    initrd /boot/vmlinuz-huge-2.6.37.6

that entry works fine but the kernel is not loading the right driver for my wireless card

I added another entry to boot from the generic kernel and this is how it looks

Code:

###Don't change this comment - YaST2 identifier: Original name: linux###
title SlackWare
    root (hd0,4)
    kernel (hd0,4)/boot/vmlinuz-generic-2.6.37.6 root=/dev/sda5
    initrd /boot/vmlinuz-generic-2.6.37.6

the boot starts but then goes into a panic and stop.
My question is what should I change to make it boot using the generic kernel?

I will appreciate all advice. Thank you!

ruario · 06-30-2012, 10:47 AM

The problem is this line "initrd /boot/vmlinuz-generic-2.6.37.6". That is not your initrd, it is your kernel. Make an initrd file using the directions in README.initrd within the /boot directory and then specify that instead.

ruario · 06-30-2012, 10:49 AM

And huge doesn't typically use an initrd but you have specified one (again your kernel, which was wrong). So your original setup was incorrect as well.

TroN-0074 · 06-30-2012, 12:27 PM

Thank you for the information. I went to create an initrd.gz file base on the instructions and came and changed my entry here is how it looks now

Code:

###Don't change this comment - YaST2 identifier: Original name: linux###
title SlackWare
    root (hd0,4)
    kernel /boot/vmlinuz-generic-2.6.37.6 root=/dev/sda5
    initrd /boot/initrd.gz

I still get a panic message when trying to boot using that file.

So I will really appreciate it all advice.
Thank you.

TobiSGD · 06-30-2012, 12:40 PM

Which filesystem is on your /-partition and which command have you launched exactly to create the initrd?

TroN-0074 · 06-30-2012, 01:13 PM

O.k so my / is formated in ext4 and to create the file I cd into /boot as root and issued the command # mkinitrd twice

If the file was wrongly created I can go and modify it.

I will appreciate it all advice. I feel I am swimming in deep waters here. Thank you

TobiSGD · 06-30-2012, 01:47 PM

You have to build in the modules needed to access the filesystem

Code:

mkinitrd -m ext4

This will automatically pull in some other modules, don't worry about that. After that, try it again.

TroN-0074 · 06-30-2012, 02:10 PM

Thank you! That worked. I re created the file and now I was able to boot with the generic kernel, however it didn't fix the wireless problem.

I really appreciate all the help provided to solve this thread

ruario · 06-30-2012, 02:37 PM

Glad it worked out for you in the end. Though I can't help but mention that README.initrd tells you about the switches to use (e.g. '-m').