From: Rasmus Plewe (rplewe_at_suse.de)
Date: Tue Jul 17 2007 - 08:59:21 CEST
Date: Tue, 17 Jul 2007 08:59:21 +0200 From: Rasmus Plewe <rplewe@suse.de> Message-ID: <20070717065920.GF13249@coredump.suse.de> Subject: Re: [suse-sles-e] Is there a 3ware 9650 driver in SLES10 x86-64 SP1?
Hello,
not sure what "this case" is, so I'll explain both cases. ;-)
Kernel module as KMP:
---------------------
The kernel provides a number of symbols (the ABI), which can be used by
modules. We group those symbols and run a checksum over them. These
checksums are provided by the kernel rpm (see:
'rpm -q --provides kernel-smp' or whatever kernel you've got installed).
A KMP now requires the checksum for the symbol(s) it needs. If the ABI
is not changed for a kernel update, the checksum stays the same and no
action is required. If the checksum changes, there is a dependency
conflict that needs to get resolved. Either the KMP vendor offers an
online repository and puts an updated KMP in there, then the kernel
update will proceed and install the new KMP as well. Or you need to
resolve manually by having downloaded the new KMP and are ready to
install it.
Kernel module "downloaded from the web and built locally":
----------------------------------------------------------
Here it's your responsibility to remember that there was such a module,
and check that it still does work after the update or that you have an
updated module at hand. You are in risk of forgetting that and render
your system not functional by "just applying the latest updates".
Additionally, depending on how smart the module gets built locally, it
ends up somewhere where it isn't found after the update, although it
would work if it was found. There is technically no way for us to
prevent that.
Bottom line: Test every especially kernel updates on a non-productive
system.
Regards,
Rasmus
-- Rasmus Plewe --- Linux Beta Test Coordinator SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg On Mon, Jul 16, 2007 at 01:49:48PM -0600, Michael Folsom wrote: > Ramus - > > One more question - > > Not being totally wise in the ways of modules - in this case would the new > kernel during a kernel upgrade automatically inherit the "added on" modules > of the last kernel and try to use them? Or, would you need to add them back > in yourself? > > Hope this makes sense - > > > Michael > > > On 7/11/07, Rasmus Plewe <rplewe@suse.de> wrote: > > > >Hello, > > > >KMPs are Kernel Module Packages. That's a process that allows you (the > >HW vendor) to build kernel modules that don't shoot your customer in the > >foot in case of a kernel update. If you register your KMP with Novell, > >you will get notified of relevant kernel changes so that you can rebuild > >your KMP in advance. If your customers register an update channel for > >this KMP, the kernel module will be updated simultaneously with your > >kernel, making sure that you don't e.g. lose access to your storage > >because of the update. A detailed explanation of the process can be > >found at: http://en.opensuse.org/Kernel_Module_Packages > > > >It seems that 3web is not using this process, at least the contents of > >their driver disk indicates that. That means that it's up to the user > >(you) to make sure nothing breaks with a kernel update. Chances are > >rather slim that you will run into trouble, as we're making a "really > >very best effort" not to change the kernel ABI within the life of a > >product version (other than between service packs). But we can't > >guarantee it. So, yes, you have to be prepared to take the modules > >actively into account when upgrading a kernel. > > > > > >Regards, > > Rasmus > >-- > >Rasmus Plewe --- Linux Beta Test Coordinator > >SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) > >Maxfeldstrasse 5, D-90409 Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Jul 17 2007 - 11:03:01 CEST