I have suse 11u4 installed but having 3.0.101-107 kernel . But i need 3.0.101-63 as one module only works with "3.0.101-63".
this "3.0.101-63" comes with default ISO from SLES but when i ma trying to install or upgrade in both situation in last it gives either dependency issue or rpm exec issue something. due to GLIBC.
I have only 2 opton to fix it:
1. Downgrade kernel from 107 to 63 (recommended)
2. Shifting or reload current module which is configured for "3.0.101-107" to "3.0.101-63" but dont know how.
Pease help
Linux* OpenSUSELinux Distributions
Last Comment
Panagiotis Toumpaniaris
8/22/2022 - Mon
David Favor
This is correct behavior.
When you upgrade your Kernel, many other system libraries (like libc) can also update.
This, creates a cascade where all software dependent on libc also update.
Downgrading a Kernel really means downgrading... sometimes 100s of software packages.
Be very careful to only execute this type of action using a dryrun flag, till you get a clean downlevel.
If you somehow get some packages downleveled + other broken, you may end up with a Bricked system (unable to finish a clean boot).
If a client asked me to do this, I'd start with a fresh machine + install the exact kernel version, then port their code to the downlevel machine.
Using a fresh install of downleveled Kernels, is the cleanest/fastest way to produce your desired runtime environment + ensure you have a machine that boots.
Panagiotis Toumpaniaris
You can install multiple kernel versions in suse :
ok this is the kernel i need to add with diffrent kernel:
host-192-168-1-118:/lib/modules/3.0.101-63-default/kernel/drivers/scsi/scsi_ep_front # pwd
/lib/modules/3.0.101-63-default/kernel/drivers/scsi/scsi_ep_front
host-192-168-1-118:/lib/modules/3.0.101-63-default/kernel/drivers/scsi/scsi_ep_front # ls
scsi_ep_front.ko
@David Favour - Agreed with you comments but sitiuation is diffcult - i need to make this module work without installing new machine. so either i should downgrade kernel to the needed one or manually add this module to the current kernel
Panagiotis Toumpaniaris
This solution is best for inserting a module to the kernel, but it is not advisable in practice just as David said.
When you upgrade your Kernel, many other system libraries (like libc) can also update.
This, creates a cascade where all software dependent on libc also update.
Downgrading a Kernel really means downgrading... sometimes 100s of software packages.
Be very careful to only execute this type of action using a dryrun flag, till you get a clean downlevel.
If you somehow get some packages downleveled + other broken, you may end up with a Bricked system (unable to finish a clean boot).
If a client asked me to do this, I'd start with a fresh machine + install the exact kernel version, then port their code to the downlevel machine.
Using a fresh install of downleveled Kernels, is the cleanest/fastest way to produce your desired runtime environment + ensure you have a machine that boots.