Hi Everyone,

I recently followd the instruction on upgrading to the 2.6 kernel through installpkg using the 2.6.10 kernel under the testing directory on CD #2

All went well untill i rebooted and got this message

/boot/initrd.gz: Loading kernel modules from initrd image
Using /lib/modules/2.6.10/jbd.ko
Using /lib/modules/2.6.10/ext3.ko
mount: Mounting /dev/sda2 on /mnt failed: No such device or address
ERROR: mount returned error code 1. Trouble ahead
mount: Mounting /dev/sda2 on /mnt failed: Invalid arguemnt
mount: Mounting /dev/sda2 on /mnt failed: Invalid arguemnt
/boot/initrd.gz: exiting
pivot_root: pivot_root: Device or resource busy

Then it just drops me into the # prompt and i basically cant do anything. When i try to boot back into the 2.4.29 kernel I get

Kernel Panic - not syncing VFS: Unable to mount root fs on unknown block(8,2) What when wrong here

I folllowd this message posted by halo14

Installing 2.6 kernel from Slackware Disc-2 halo14 9 261
Yesterday 10:45 PM
by danny



I had both enties on lilo.conf the same way the link above showed. I dont mind reinstalling the system but I need SMP support as I have a dual processor system and the 2.4.29 kernel only shows one processor.

It seems you've a sata drive and the default Slackware kernel doesn't not support it. Is there any chance that before upgrading you selected sata.i kernel during installation?

The kernel apparently doesn't have support for your scsi adapter. Do you remember which kernel you used at install time? Probably bare.s, but you had a few choices.

If you can figure that out, you can boot your system using the install disc as a rescue disc. At the lilo prompt, type:
Replacing bare.s with the appropriate kernel, and /dev/sda2 with the appropriate partition if necessary.

Once you're able to get back, you can actually copy the bare.s or whichever kernel over to your /boot, and update lilo to use that. That, at least, should get you booting without needing the CD. Once you're able to boot without the CD, I'd suggest you go to http://kernel.org/ and download the latest 2.6.11.11 kernel, so you can compile it with support for your SCSI adapter.

I actually have scsi drives and i select adaptec.s during the install

i have tried to install the kernel by hand by i keep getting errors - the error at this time I dont remember but i remember one of the solution was to change a file i belive named ksloyyms.c something under the /usr/src/linux-kernel directory. The advise was to change a number but that did not work at all so thats why im doing it this way-

The file in question is kallsysms.c i get erros on that file and did a google search and was told to adjust a entry in there but that did not help

Does it boot at all if you use the "adaptec.s root=/dev/sda2"?

You can skip installing that kernel manually and go straight to downloading and installing 2.6.11 as long as you can still get online. I just suggested that to save you a step if the new kernel doesn't work right first go.

This is the error i always get when i type make when im trying to recompile the kernel


Inconsistent kallsyms data
Try setting CONFIG_KALLSYMS_EXTRA_PASS
make: *** [vmlinux] Error 1

Hi,

i recently use kernel packages 2.6.10 under the testing directory on CD#2 to
upgrade my Slackware10.1 kernel 2.4.29, i face the same problem of rrecchia.

However, i solved it no need to use kernel 2.6.11. The problem is when i use
mkinitrd i haven't load the driver of my scsi controller, in many instructions
they just load jbd and ext3, it was because they supposed you are using ide but
scsi, so if you are using scsi you must load the driver of your scsi controller,
for example, my scsi controller is AHA2940, so the driver should be aic7xxx,
the mkinitrd should be:

mkinitrd -c -k 2.6.10 -m aic7xxx:jbd:ext3 -f ext3 -r /dev/sda1

if you use other scsi controller, i think you can find a suitatable driver in
/lib/modules/2.6.10/kernel/drivers, after you reapply mkinitrd, you can view
the load_kernel_modules file in initrd-tree dir, the aic7xxx.ko should be at the first line, pls remember reapply lilo to update your lilo.conf, that's all,
good luck!

I never bothered with the Slackware 2.6 kernel package, but if it's the same as the 2.4 Slackware kernel, then SMP is still disabled. SMP support is not a new feature, it is a disabled feature. Upgrading via the package:

a) Introduces the need for mkinitrd
b) Won't solve the problem

Just recompile by hand. There may be a steeper learning curve, but once you can compile (well) by hand, you will see that it is really very easy.