[S.u.S.E. Linux] SuSE-5.1 kernel version mismatch with sources
Following upgrade earlier this year from S.u.S.E.-5.0 to S.u.S.E.-5.1,
I have just found that I now have kernel version 2.0.33 and modules version
2.0.33 installed, but the kernel sources are for version 2.0.32.
Scanning the 5.1 CD-ROMS shows that only sources version 2.0.32 are provided.
I discovered this while trying to compile and install ftape-3.04d.
This compiles for version 2.0.32 and, as a result, I am unable to use the
resulting modules which refuse to be loaded by "modprobe" (" kernel-module
version mismatch").
Although insertion of the resulting ftape.o can be forced by "insmod -o", it
does not work:
mt -f /dev/nftape rewind
mt: /dev/nftape: No such device
(whereas the same does work with the ftape.o which came with modules-2.0.33 on
the S.u.S.E.-5.1 CD-ROM).
This mismatch on the S.u.S.E.-5.1 distribution between the distributed binary
kernel version and the source kernel version has really annoyed me.
Short of re-compiling from the supplied sources to get a 2.0.32 kernel (which
strikes me as a retrograde step!), is there a way round this?
And what have the S.u.S.E. management to say about the version mismatch?
With best wishes,
Ted.
--------------------------------------------------------------------
E-Mail: (Ted Harding)
The package you want is suse_lx. That is the source for 2.0.33, you just have the wrong packages installed, it isn't SuSE's fault. (Ted Harding) wrote:
Following upgrade earlier this year from S.u.S.E.-5.0 to S.u.S.E.-5.1, I have just found that I now have kernel version 2.0.33 and modules version 2.0.33 installed, but the kernel sources are for version 2.0.32.
Scanning the 5.1 CD-ROMS shows that only sources version 2.0.32 are provided.
I discovered this while trying to compile and install ftape-3.04d.
This compiles for version 2.0.32 and, as a result, I am unable to use the resulting modules which refuse to be loaded by "modprobe" (" kernel-module version mismatch").
Although insertion of the resulting ftape.o can be forced by "insmod -o", it does not work:
mt -f /dev/nftape rewind mt: /dev/nftape: No such device
(whereas the same does work with the ftape.o which came with modules-2.0.33 on the S.u.S.E.-5.1 CD-ROM).
This mismatch on the S.u.S.E.-5.1 distribution between the distributed binary kernel version and the source kernel version has really annoyed me.
Short of re-compiling from the supplied sources to get a 2.0.32 kernel (which strikes me as a retrograde step!), is there a way round this?
And what have the S.u.S.E. management to say about the version mismatch?
-- _____ .-'WWWWW'L. WindowMaker.... .'WWWWWWWWWWWW.__ /WWWWWWW| \W| The choice of ;WWWWWWWW| ;| a GNU generation. |WWWWWWWW| || ;WWW| ;| ===================================== \WW| /W| |Michael Lankton, satan@nfinity.com | __'W| .'WW| | University of Nebraska-Omaha CIST | |WWWWW-._____._WWWWW| ===================================== -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I said suse_lx, but I think it's actually lx_suse. Sorry 'bout that. _____ .-'WWWWW'L. WindowMaker.... .'WWWWWWWWWWWW.__ /WWWWWWW| \W| The choice of ;WWWWWWWW| ;| a GNU generation. |WWWWWWWW| || ;WWW| ;| ===================================== \WW| /W| |Michael Lankton, satan@nfinity.com | __'W| .'WW| | University of Nebraska-Omaha CIST | |WWWWW-._____._WWWWW| ===================================== -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On 26-May-98 Michael Lankton wrote:
The package you want is suse_lx. That is the source for 2.0.33, you just have the wrong packages installed, it isn't SuSE's fault.
(Ted Harding) wrote:
Following upgrade earlier this year from S.u.S.E.-5.0 to S.u.S.E.-5.1, I have just found that I now have kernel version 2.0.33 and modules version 2.0.33 installed, but the kernel sources are for version 2.0.32.
Thanks for your 2 mails (nice sig by the way).
I can't really agree with you. Thanks for pointing out lx_suse.
However,
1. S.u.S.E.-5.0 (which I originally installed) has only 2.0.30 sources.
2. When I upgraded off the 4-CD 5.1 set in February, the packages
"linclude" ("Include files for the kernel") and "linux" ("Rest of the kernel
source code") were upgraded routinely. These are version 2.0.32. They could
not have come from 5.0 (see (1) above).
3. The kernel which was installed by the upgrade was 2.0.33.
4. Package "lx_suse" is "Kernel sources with additional drivers" and is
presented by YaST as if it is an option. Furthermore, having got as far
as (2) above, when I now select "lx_suse" it says
5. "It does not make sense to install this package in combination with one
of the following packages ... linclude .. linux"
So what am I now supposed to do? Uninstall "linclude" and "linux"? Is this
likely to give trouble running the system? Then what? Will "lx_suse" (which
apparently has a directory tree usr/src/linux-2.0.33.pre.SuSE.3/ have to be
linked to from /usr/src/linux after installation? Are there any other
consequential changes (e.g. in config files elsewhere in the system)?
Remember this would be taking place as if it were installation of an optional
package, not upgrading a mainline package. So I don't know where I stand.
I cannot afford to break this system, so can only make any radical change which
I am confident will work and not generate problems or conflicts.
I therefore await carefully considered advice on how to cope with this
situation safely.
I still think it was ill-conceived on the 5.1 distribution to automatically
upgrade the kernel to 2.0.33 and upgrade the sources to 2.0.32, thereby leaving
the system in an inconsistent state which can not be straightforwardly put
right.
Thanks for the pointer.
Ted.
--------------------------------------------------------------------
E-Mail: (Ted Harding)
<PRE> On 27-May-98 Ted Harding wrote:
So what am I now supposed to do? Uninstall "linclude" and "linux"? Is this likely to give trouble running the system? Then what? Will "lx_suse" (which apparently has a directory tree usr/src/linux-2.0.33.pre.SuSE.3/ have to be linked to from /usr/src/linux after installation? Are there any other consequential changes (e.g. in config files elsewhere in the system)?
Yes. Do it. I did and suffered no ill effects. "linclude" has the packages necessary to develop for linux (the header files) but not compile the actual kernel. "linux" has the .c (and such) files for the kernel. lx_suse has both the headers and the .c files. Further more, by uninstalling the two packages, if something would go wrong, will not cripple your machine and can be easily reinstalled (you might have to over ride the warning, but it can be). I know... I've done that, too... tried a patch that went wild. YaST wouldn't remove the package so I just reinstalled over the top.. no ill effects. ---------------------------------- <A HREF="http://benham.net/index.html"><A HREF="http://benham.net/index.html</A">http://benham.net/index.html -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCS d+(-) s:+ a29 C++$ UL++>++++ P+++$ L++>++++ E? W+++$ N+(-) o? K- w+++$(--) O M-- V- PS-- PE++ Y++ PGP++ t+ 5 X R+ !tv b++++ DI+++ D++ G++>G+++ e h+ r* y+ ------END GEEK CODE BLOCK------ ---------------------------------- </PRE> <A HREF="pgp00003.pgp"> PGP signature</A></P>
Using yast select to install lx_suse and uninstall linclude and linux and you should be good to go, just compile a new kernel and you'll be set with 2.0.33. (Ted Harding) wrote:
So what am I now supposed to do? Uninstall "linclude" and "linux"? Is this likely to give trouble running the system?
-- _____ .-'WWWWW'L. WindowMaker.... .'WWWWWWWWWWWW.__ /WWWWWWW| \W| The choice of ;WWWWWWWW| ;| a GNU generation. |WWWWWWWW| || ;WWW| ;| ===================================== \WW| /W| |Michael Lankton, satan@nfinity.com | __'W| .'WW| | University of Nebraska-Omaha CIST | |WWWWW-._____._WWWWW| ===================================== -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (3)
-
gecko＠benham.net -
satan＠nfinity.com -
Ted.Harding＠nessie.mcc.ac.uk