Bugzilla – Bug 527381
kernel-2.6.27.25-0.1.1.x86_64 version from update repo installs as 2.6.27.25-0.1.1
Last modified: 2009-10-05 07:40:01 UTC
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1 (.NET CLR 3.5.30729) when i updated me kernel from update repository to version 2.6.27.25-0.1.1 and run "uname -r" after reboot i get this version 2.6.27.23 i tries a fresh install and updated from original version to latest version from update repo i still get the wrong info by running uname -r (i still get 2.6.27.23) i ask one other person that used the 32bit verion but they didnt have that problem so iguess it a bug in 64bit version of update package of kernel this bug is (at list for me) critical cause it blockes the compiling of some apps (vbox services for example) Reproducible: Always Steps to Reproduce: 1.update the kernel to 2.6.27.25-0.1.1 in opensuse 11.1 x64 2.run "uname -r" 3. u get 2.6.27.23 Expected Results: uname should say 2.6.27.25 not 2.6.27.23
run: zypper up and quote the output here... sounds liks it was not installed correctyly? also: rpm -qa|grep kernel-
1) zypper up Loading repository data... Reading installed packages... The following package is going to be upgraded: chemtool The following package is going to change vendor: chemtool Overall download size: 221.0 K. After the operation, 39.0 K will be freed. Continue? [YES/no]: 2) rpm -qa|grep kernel- linux-kernel-headers-2.6.27-2.28 kernel-source-2.6.27.25-0.1.1 kernel-default-extra-2.6.27.25-0.1.1 kernel-default-2.6.27.25-0.1.1 kernel-default-base-2.6.27.25-0.1.1
looks like the kernel got intsalled just fine. how do you boot the machine? with grub this should be setup fine
i boot it normally if u need i config file (like grub menu or something like that....i am a Linux expert) posted here, tell me so i do it. and can u try this ( i dont have much hard drive or i would have tried it in vmware) install opensuse 11.1 x64 (32 seems to be fine) and update the kernel in update repo and then check its kernel this 'uname -r'?
well, i am updating the kernel regulary, and others too ... Yours is the first report I saw, so I suspect its confined to a bug related to your setup ;) can you please post the /boot/grub/menu.lst ?
# Modified by YaST2. Last modification on Fri Jul 31 22:25:42 IRDT 2009 default 0 timeout 8 gfxmenu (hd1,1)/boot/message ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.1 - 2.6.27.25-0.1 root (hd1,1) kernel /boot/vmlinuz-2.6.27.25-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1HL960974-part2 resume=/dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1HL960974-part1 splash=silent showopts vga=0x31a initrd /boot/initrd-2.6.27.25-0.1-default ###Don't change this comment - YaST2 identifier: Original name: failsafe### title Failsafe -- openSUSE 11.1 - 2.6.27.25-0.1 root (hd1,1) kernel /boot/vmlinuz-2.6.27.25-0.1-default root=/dev/disk/by-id/ata-SAMSUNG_SP2504C_S09QJ1HL960974-part2 showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 x11failsafe vga=0x31a initrd /boot/initrd-2.6.27.25-0.1-default ###Don't change this comment - YaST2 identifier: Original name: windows### title Windows rootnoverify (hd0,0) chainloader +1
Hmm, lost track iof this bug ... is this still the case? rpm -q kernel-default ? YOu are not using lilo by chance?
it seems to be fixed now and i used the default boot loader (GRUB) maybe the new kernel update fixed it somehow ~>rpm -q kernel-default kernel-default-2.6.27.29-0.1.1 ~> uname -a Linux linux-rd-com 2.6.27.29-0.1-default #1 SMP 2009-08-15 17:53:59 +0200 x86_64 x86_64 x86_64 GNU/Linux