Hi !
It’s been a while before, I noticed that every time I needed to compile a kernel module, the headers were not matching current kernel. e.g. today the kernel 2.6.29 is installed (for sure) on my osuse 11.1, but uname -r returns 2.6.19 and before the install with Yast2.
Now that can be resolved using yast and downgrading kernel-sources to the 2.6.19 release, quite embarassing because 2.6.19 kernel-syms seem not available anymore…
:sarcastic:
as far as i know it is possible to have many kernels installed at the
same time…but, only one can be booted at a time…
do this, in a terminal:
sudo cat /boot/grub/menu.lst
give your root password when asked, and copy past the results back to
here…
–
palladium
# Modified by YaST2. Last modification on Wed Sep 30 02:59:53 CEST 2009
default 4
timeout 30
gfxmenu (hd0,6)/boot/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.29-0.1 (default)
root (hd0,6)
kernel /boot/vmlinuz-2.6.27.29-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10X225162-part7 resume=/dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10X225162-part6 splash=silent showopts vga=0x317
initrd /boot/initrd-2.6.27.29-0.1-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1 - 2.6.27.29-0.1 (default)
root (hd0,6)
kernel /boot/vmlinuz-2.6.27.29-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10X225162-part7 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
initrd /boot/initrd-2.6.27.29-0.1-default
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.29-0.1 (pae)
root (hd0,6)
kernel /boot/vmlinuz-2.6.27.29-0.1-pae root=/dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10X225162-part7 resume=/dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10X225162-part6 splash=silent showopts vga=0x317
initrd /boot/initrd-2.6.27.29-0.1-pae
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 11.1 - 2.6.27.29-0.1 (pae)
root (hd0,6)
kernel /boot/vmlinuz-2.6.27.29-0.1-pae root=/dev/disk/by-id/ata-SAMSUNG_SP1614N_S016J10X225162-part7 showopts ide=nodma apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x317
initrd /boot/initrd-2.6.27.29-0.1-pae
###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows
rootnoverify (hd0,0)
chainloader +1
well, i’m stumped…
i wonder how uname learns the kernel version…i had thought it would
look inside the kernel, but apparently it is reading from file name…
my GUESS is you have (somehow) an actual 2.6.19 kernel (on the inside)
that is named 2.6.29 on the outside…
would you know how to CAREFULLY look in your /boot directory, and look
at what kernels you have there, what they are named and how that
compares to their internals (CAREFUL, do not change them)…
–
palladium
ls -i /boot/
952161 backup_mbr 953377 symtypes-2.6.27.29-0.1-default.gz
952145 boot 952164 symtypes-2.6.27.29-0.1-pae.gz
952144 boot.readme 953378 symvers-2.6.27.29-0.1-default.gz
953273 config-2.6.27.29-0.1-default 952165 symvers-2.6.27.29-0.1-pae.gz
952158 config-2.6.27.29-0.1-pae 953190 System.map-2.6.27.29-0.1-default
952131 grub 952149 System.map-2.6.27.29-0.1-pae
952146 initrd 953396 vmlinux-2.6.27.29-0.1-default.gz
953675 initrd-2.6.27.29-0.1-default 952166 vmlinux-2.6.27.29-0.1-pae.gz
952168 initrd-2.6.27.29-0.1-pae 952148 vmlinuz
952147 message 953402 vmlinuz-2.6.27.29-0.1-default
953318 symsets-2.6.27.29-0.1-default.tar.gz 952167 vmlinuz-2.6.27.29-0.1-pae
952163 symsets-2.6.27.29-0.1-pae.tar.gz
That’s what I thought too… Anyway these all kernels are coming from official suse repos…
but you didn’t look inside yet…try, in a terminal
sudo cat /boot/vml* | grep -a 2.6.19
which should return nothing…
and,
sudo cat /boot/vml* | grep -a 2.6.29
which should return a lot (of garbage looking code)
but, STILL i say i’m stumped and just trying to entertain the REAL
gurus (reading and laughing as i flounder), until they decide to step
in and help…
–
palladium
now I see what you pointed out : yes there are 2.6.27.29 but there’s no 2.6.27.19 in.
ls -l /boot
....
lrwxrwxrwx 1 root root 29 sept. 30 03:04 vmlinuz -> vmlinuz-2.6.27.29-0.1-default
....
linux-jsxl:/home/tiana/Documents # uname -r
2.6.27.19-3.2-default
linux-jsxl:/home/tiana/Documents # ls /boot/vml* | grep -a 2.6.27.
/boot/vmlinux-2.6.27.29-0.1-default.gz
/boot/vmlinux-2.6.27.29-0.1-pae.gz
/boot/vmlinuz-2.6.27.29-0.1-default
/boot/vmlinuz-2.6.27.29-0.1-pae
linux-jsxl:/home/tiana/Documents # ls /boot/vml* | grep -a 2.6.
/boot/vmlinux-2.6.27.29-0.1-default.gz
/boot/vmlinux-2.6.27.29-0.1-pae.gz
/boot/vmlinuz-2.6.27.29-0.1-default
/boot/vmlinuz-2.6.27.29-0.1-pae
linux-jsxl:/home/tiana/Documents # cat /boot/vml* | grep -a 2.6.27.
,��Jvmlinux-2.6.27.29-0.1-default�;TSW�7
ɾ@C�*▒$t�u;��F8��`�-
�����/�x���0m�)����zap�|
��C�?ra�~z�+��0x}▒��Rx9��CW���{;7������{G������ݨ��φ�܉��pyn�+s�}?���`��#�>���9n���������u�"��p;�ɷ:��})|����▒���t(��N=▒��τ/�L�ij��/D>�\�zT��7"����M���?���N��φr�����P����f%���
��0��
c�:��=��ȃ�����Jvmlinux-2.6.27.29-0.1-pae�<mtוO�Ȗl�Q�����R6��I��>ǃm0_�:��e7��HZh
�d㸜��=g��Yd��"�!9�1 58<� ���/vm�9{����9���{����_��{��G�3▒
d▒��D�������(��'�� ed��og��n�3��Y��<
2.6.27.29-0.1-default (geeko@buildhost) #1 SMP 2009-08-15 17:53:59 +0200VGACGA/MDA/HGCEGA�$�$;%`&&m%�%`1P1▒1]0i0Y0VESABIOSY0$$o&�0�(�&�0�*W+�DDPP2P+PPP"P<PP+PU�ZZ��@u��▒�؎�����Ѝ���]��%����������+����
+%��
�ÁÀ��������V��d�%��d�%�d�%����^����������+%���*%���J�;tSU�7�K��)/��)��Ԗu▒-��1��"ⴥ��*J�rXF9����1�(�v���+�N��uu�SҰ#/}Н����º�⺯����~�}iKa�sf��=ͻ�����������&}n��R�NGF��▒��f%y�|�J){�#v▒�A���q+{Ȭa��}��~6��}�2|H��DB*l$16�A�3�Av^�K�q�#Ɵ#�/�/�/�/�/�/�/���.C[S����6^�>=���2�sG�yGh�z�) �jұr�j2�b`��d�Z�� �WZ�1k�#�o��4�n#B�N��k�ۀ�a�ۉ�bR�>q�eR@���*j��QRCڮD�I���{���W �(�jHV�p7o�{��!�2>9�0��"�6��ӱ7��o{2��C������d>ׇ����x���P��g2tV�J������Z��Sd�{
A6��FŞݵ���=��k@˰���
�!m��7;9e��6ĤS��g�{�L���,
�2�����K�9Y�^
�-�)�9EdH-���N�$l��#�]�I��� �Z�=�tWV������W0�Uķ�#�▒�ӞSޡ����Z�-��eħ�s)�>
2.6.27.29-0.1-default (geeko@buildhost) #1 SMP 2009-08-15 17:53:59 +0200VGACGA/MDA/HGCEGA�$�$;%`&&m%�%`1P1▒1]0i0Y0VESABIOSY0$$o&�0�(�&�0�*W+�DDPP2P+PPP"P<PP+PU�ZZ��@u��▒�؎�����Ѝ���]��%����������+����
+%��
�ÁÀ��������V��d�%��d�%�d�%����^����������+%���*%���J�;tSU�7�K��)/��)��Ԗu▒-��1��"ⴥ��*J�rXF9����1�(�v���+�N��uu�SҰ#/}Н����º�⺯����~�}iKa�sf��=ͻ�����������&}n��R�NGF��▒��f%y�|�J){�#v▒�A���q+{Ȭa��}��~6��}�2|H��DB*l$16�A�3�Av^�K�q�#Ɵ#�/�/�/�/�/�/�/���.C[S����6^�>=���2�sG�yGh�z�) �jұr�j2�b`��d�Z�� �WZ�1k�#�o��4�n#B�N��k�ۀ�a�ۉ�bR�>q�eR@���*j��QRCڮD�I���{���W �(�jHV�p7o�{��!�2>9�0��"�6��ӱ7��o{2��C������d>ׇ����x���P��g2tV�J������Z��Sd�{
A6��FŞݵ���=��k@˰���
�!m��7;9e��6ĤS��g�{�L���,
�2�����K�9Y�^
�-�)�9EdH-���N�$l��#�]�I��� �Z�=�tWV������W0�Uķ�#�▒�ӞSޡ����Z�-��eħ�s)�>
2.6.27.29-0.1-pae (geeko@buildhost) #1 SMP 2009-08-15 17:53:59 +0200VGACGA/MDA/HGCEGA�$�$;%`&&m%�%p1`1(1i0u0e0VESABIOSe0$$o&�0�(�&�0�*W+� D DPP2P+PPP"P<PP+PU�ZZ��@u��▒�؎�����Ѝ���]��%����������+�����%��
�ÁÀ��������V��dP&��dP&�dP&����^�����������%��w�%A��J�<mtוO��H��Q�����R6��I��>+�m0_�:��e7��H▒h
�d㸜��=g��Yd��"�!9�1 58 ���-��������ECڜ���=�͛����;3�=����s
#1��N�(gw� �=�ȣd��og��*n7����߃m~d��qОI�%�9��"����
broumbroum23 wrote:
> now I see what you pointed out : yes there are 2.6.27.29 but there’s no
> 2.6.27.19 in.
then the questions are:
From where is uname getting its wrong information? and
Why can’t you get your booted kernel and kernel headers to match?
and, again i say: i’m stumped…
–
palladium
Hi
If you run the command ls -la on /boot. Are vmlinuz and initrd
softlinks to the 29-0.1 kernel?
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.2 RC 1 (i586) Kernel 2.6.31.3-1-desktop
up 14:06, 2 users, load average: 0.38, 0.22, 0.12
ASUS eeePC 1000HE ATOM N280 1.66GHz | GPU Mobile 945GM/GMS/GME
yes, they do.
I ain’t no kernel developer, and I can’t figure out where the error is to be found. looking at the uname manpage and doc would lead me to the utsname.h source file…
as of this thread : uname -r giving me wrong kernel version : Fedora, Fedora, 9 it might be an EXTRA_VERSION value in the /usr/src/linux/MakeFile . let’s check it out people !!
I too have the same problem. I have checked everywhere and I have installed kernel version 2.6.27.37-0.1 but uname returns 2.6.27.19-3.2.
I have even recompiled and reinstalled the kernel with the same result.
Does anyone know where does uname get it version info from?
Thanks.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Did you reboot after getting the .37-0.1 patches?
Good luck.
jlmoya wrote:
> I too have the same problem. I have checked everywhere and I have
> installed kernel version 2.6.27.37-0.1 but uname returns 2.6.27.19-3.2.
>
> Does anyone know where does uname get it version info from?
>
> Thanks.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJK8NEUAAoJEF+XTK08PnB5YJ4QAMhJjdWohd92EVlPziB96e6Z
az0ssKgxGHdGToOzBVc5FDA81bHNxvXm+I/Y11M+uPgOqLLcV9/ArYDY2nSs9prt
Stc+/gtF4khK37rOAQpbiz0BWtwUch8iZrqKD0jYDuOQhT6bXmcYu7drIKzP+tIa
C1rQ+9S9ccXBEOq5YQ5JmbdOPSZZb5Zj9YAl/HRR1dNXnGQf5hojAxYTc2nNY97O
+OIvH+YDChHHC/ckAIVizcpGfkjExlmngV+jr59ZCGsjHQ9znKn2z3nHq9muNy/u
lhfFqqqOMIqJkrMUeyBEHsV/fgqnCsSHFlCuU9gkfQEyanShVh5pp/2ixOtda/De
fw/TVZCsK+kukCPSA+HYwT7wJMVMAqpd2kE3ZhttimjWwN8YlEAPEnj322EIqg8q
GjThj1NkkN5AapYX97iem/tx1+J2mqdz299fe4MdIShHc6W1V87EilR6Psb/gitt
Z/zN2IKg2jlWCHRcOuDULh0/oOs5uSOzxcoM6s72pVtXx1dbmeQNyaLC41d4aGM5
22O06+EKnUCbS0HTxPHWGgMMPMx2bTTSKwSvgrF/Ld1hHthkyQY78nhjqNjQiFJD
wKFMP7R//lj+758obZ4S/hirtVCY/CsWk6aQqOvN701xML/efrd5h1xA/K9PWXwV
cZdI7OlnMxiNT2MLsavT
=qPhz
-----END PGP SIGNATURE-----
Thanks, yes I did boot after I compiled the kernel and got the same result.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
You compiled the kernel? For some reason I thought you had just updated
from the repositories. I think there is an option in the kernel
configuration that lets you add a string to your kernel version but I
think it only lets you append to the end; I could be wrong and maybe it
lets you set the entire version and that is not being updated.
Good luck.
jlmoya wrote:
> Thanks, yes I did boot after I compiled the kernel and got the same
> result.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJK8Qe4AAoJEF+XTK08PnB5yBsQALNOUhFwVrziGV6qIi6HVHtp
sfoQcOQWAwIdKuHP2UsQoaZpgWMWMASHqUyWQXS3n2KUEAA1j7N0aZSy3xGsNJSA
6bhpOx6wr1FYoPGEtAINAcPiXtyBGXaIDONsq3cWxyPZQGg8ef7GJFb2yBUu9hCE
Qa44NFwCIo4pMIvt+I7/77AJ8olGBh1KULf1r24E8OpRqKEfFa6zOl0XZgpvbwHb
yxkOWsuJtAsPbNNSkxejsL3wYRfS62MkRNv3TQzkixFc0DKu2uLyzALVzxFcbmQG
w6VVkkRDnRhaWlUzSHXDYuFIQX8KLdXDAReAEsU15JcEhpotuzeSoM4aLxYjfQ4E
PN9Y3bWO5dwQ2HNSv7+OVyQxe4XFRXsXEbyPTFQH5IDfjKX6rjqgiAk5L6albEI0
m1M/AU0lp58lOinmaTqL9eZj+5xBUvso77svO1gkVcRf/+Em05oIAB0wJZBL1fNo
n/bmuqoFRCOSi8BvfkIY074Mq9cxYZydS3a+e9GuRYfIUO4oY8LcVUxFSPVTwMh4
egVPdIZA2q8US/b6ZoGTBt4oFHz2/AFdCwiLZIku1WZZuNO+GZuW5XLMcJqNjZ52
NgNjb0B3/+ef9NT8N/lTXS2H3U3TutjfU/XZSYBP1Aw2hkfXtFQm559glhrzRxu4
tcz8tLWLsmq6hGrc2efC
=CE/y
-----END PGP SIGNATURE-----
Got it working even though I’m still not pleased with the solution, apparently the error comes from an outdated VirtualBox driver. What I did was the following:
[ol]
[li]Downloaded and installed the latest version of VirtualBox from url=http://www.virtualbox.org[/li][li]Executed /etc/init.d/vboxdrv setup as root. Got an error because kernel versions don’t match but this procedure uninstalls the old driver.[/li][li]Now this is the part I don’t like. I opened yast and updated the coreutils package, plus installed coreutils-debugsource (Wanted to look at the source and understand how uname got its data). After checking uname.c code, I again uninstalled the debug packages (coreutils-debuginfo and coreutils-debugsource).[/li][li]Again executed /etc/init.d/vboxdrv setup and it worked. Mainly because uname -r now returns the correct version.[/li][/ol]
I wish I knew exactly what happened, I guess I should be happy because it’s working now. 
Seems to be a (very rare) bug in coreutils you got hit by.
For people understanding german:
LINUX - openSUSE - [geloest] Installierte Kernelversion stimmt nicht bei uname
thank you.
then coreutils and coreutils-lang must be re-installed… lol
Hi!
I has similar problem with ‘uname -r’
Before I updated opensuse from 10.3 to 11.1.
first time I got ‘uname -r’ from 10.3 (~2.6.22…), then I removed all modules from /lib/modules/ for 10.3, and got:
Linux gamma 2.6.27.19-3.2-default #1 SMP 2009-10-15 14:56:58 +0200 x86_64 x86_64 x86_64 GNU/Linux
Real version is:
Linux version 2.6.27.37-0.1-default (geeko@buildhost) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP
Also I removed all virtualbox, kvm modules.
As I understood, ‘uname’ is a system call from kernel. But I don’t understand how to replace the version in kernel?
PS. Main problem for me is: hibernate to disk doesn’t work!