I must have been editing when you posted.
What about this missing kernel?
Hugh
Odd
do
zypper ref
zypper dup
Post the output
zypper ref
Repository 'repo-non-oss' is up to date.
Repository 'repo-oss' is up to date.
Repository 'repo-update' is up to date.
Repository 'repo-update-non-oss' is up to date.
Repository 'tumbleweed' is up to date.
All repositories have been refreshed.
linux-s3zv:~ # zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Nothing to do.
Please post
rpm -qa | grep kernel
rpm -qa | grep kernel
kernel-desktop-devel-3.6.0-3.1.x86_64
kernel-devel-3.6.0-3.1.noarch
kernel-firmware-20120719git-2.9.1.noarch
kernel-desktop-3.4.6-2.10.1.x86_64
there you go,
Hugh
Are you using kde or gnome?
I ask because it will help me with the next step
I am using KDE - and legacy grub if that helps as well,
Hugh
OK
Try this
https://dl.dropbox.com/u/10573557/Software%20Management/system_update.png
Does that help?
umm…what was I supposed to see or do after the final step of accept?
the software manager closed - no other output or message given. It just went back yo yast2 module.
Hugh
Just take a look at the tab ‘Installation Summary’
Does it look like the kernel is there
No the tab is empty - quite blank,
Hugh
Try doing this
https://dl.dropbox.com/u/10573557/Software%20Management/vendor_change_allow.jpg
And try the previous step again
OK.
What happens now is that I have a window of choices. I didn’t get to the accept stage:
here is the list
Conflict resolution
1.deinstallation of virtualbox-guest-kmp-desktop-4.1.18_3.4.6_2.10-1.3.1_x84_64
2. do not install kernel-desktop-3.6.0-3.1.x86_64
3.break virtualbox-guest-kmp-desktop-4.1.18_3.4.6_2.10-1.3.1_x84_64 by ignoring some of its dependencies
I haven’t answered anything here yet,
Hugh
Option 1
It may lead to more ?'s
IIRC I removed all that virtual box rubbish and ndiswrapper too, which is fine to do
Yeah, well I wish I’d done that just now.
I haven’t used YAST2 before as an instrument of installation but I can read and it did not look like
it was downloading a kernel-3.6xxxxx of any description.
I have to reboot now according to The YAST2 module to finalise installation of my kernel: which looks mighty like .3.4.xxxx again,
Back shortly - I hope,
Hugh
Darn. I’m locked out of the install at the momen BUT here is the new
grub entry:
###Don't change this comment - YaST2 identifier: Original name: linux###
title Desktop -- openSUSE 12.2 - 3.6.0-3
root (hd0,7)
kernel /boot/vmlinuz-3.6.0-3-desktop root=/dev/disk/by-id/ata-WDC_WD1001FAES-75W7A0_WD-WCATR1943769-part8 resume=/dev/disk/by-id/ata-WDC_WD10EAVS-32D7B1_WD-WCAU48420094-part2 nomodeset splash=silent quiet showopts
initrd /boot/initrd-3.6.0-3-desktop
So the new kernel did get installed. I amended my controlling menu.lst to reflect the new entry but unfortunately
the machine seems to get stuck after its initial loading bar and mantis blah blah blah.
I am guessing, because I do not know, that like the distro I am writing from now that the kernel is rebuilding its bits and pieces but I can not see much
the odd word like LSB or network (large, green) but no steady output of conscientious module rebuilding that a fellow can read.
I am wondering if it would be worth removing splash=silent and quiet to see if I can get a boot that I can read.
I am currently becoming tired - been at this since this morning and it is now approaching 6.00pm here.
Low blood sugar and all that,
but hey we are making progress,
Hugh
Just hit Esc at any splash and it should go verbose
You will need to rebuild nvidia of course too
Ah,
one more go before stopping for the evening,
Thanks,
Hugh
It’s sure strange that zypper dup wasn’t working properly, because during this thread I did a clean 12.2 install and updated and dup to TW. It pulled the kernel in fine.