Quote:>I'm trying to install the 2.2.3 kernel and I'm having trouble with a few
>modules. I'm upgrading a RH5.1 system (kernel 2.0.34).
I hope that you are aware that there might be some packages that you
may need to upgrade to support the 2.2.x kernels?
Also, at least for Red Hat 5.2, when you built a new kernel, you have
to create by hand a new file in /lib/modules/2.2.3/.rhkmvtag where I
assume that 2.2.3 is where you left the new modules at.[1] The
.rhkmvtag should contain the kernel version, and you can best do this
by:
1) boot up the new kernel
2) cat /proc/version > /lib/modules/2.2.3/.rhkmvtag
At least for 5.2, when linux boots up, the start up script will match
the kernel version with those it can find in the
/lib/modules/*/.rhkmvtag files. When it finds a match, it will redo
the symlink /lib/modules/preferred to that directory.
But first check to see if that's how it is done in Red Hat 5.1.
Quote:>I get these errors on boot up and when I trying using modprobe:
>modprobe sound
>/lib/modules/preferred/misc/sb.o: too many values for dma (max 1)
>sound: Device or resource busy
Looks like you have not configured sound correctly. Since you are
running Red Hat, you might want to run sndconfig to configure your
soundcard first. The new kernel sound modules may have changed
the options.
Or you are running the wrong version of the modules.
Quote:>modprobe ppa
>ppa: Version 2.03 (for Linux 2.2.x)
>ppa: parport reports no devices.
>scsi : 0 hosts.
>/lib/modules/preferred/scsi/ppa.o: init_module: Device or resource busy
>parport: Device or resource busy
Try loading the modules by hand, parport first, and then parport_pc,
and finally ppa/lp. Check with dmesg for more verbose info. I think
"Device or resource busy" is a catch all error message that the kernel
emits when the modules doesn't return with a 0. you might want to give
some params to parport_pc when you load it.
Anyway, check out the doco in /usr/src/linux/Documentations/parport.txt.
You did get the source to 2.2.3, didn't you? ;-)
[1] After creating the .rhkmvtag, you can rename the 2.2.3 directory to
something else--it doesn't matter.
Cheers,
by