Not tried it yet!
Post feedback if you like
/caf
I’ve updated the kernel using zypper. Although the stock kernel 2.6.25.5 didn’t failed me yet, the new 2.6.25.9 looks like somewhat faster. It’s just one the newest kernel which is called 2.6.25.10 and that powerful beast is just a few days around the corner.
I just did the update too.
All went fine.
Should have said but we are talking suse 11 (though my sig said that)
Upgraded - went fine - just had to re-run /usr/bin/vmware-config.pl and all is well.
came through here fine as well!
Pffff… 
I’ve updated through the automatic updater and rebooted.
Now kde does not start anymore and I’m presented the text login
from tty1. tty7 shows only a black screen. According to ‘ps aux’ kdm is running though.
Failsafe mode, however, does start kde. Be it only at 800x600 resolution on a 1920x1200 screen.
Can I undo this update somehow?
I’m running:
Lenovo T61p
Core 2 Duo T9300
2 gb ram
Opensuse 11.0
KDE 3.5
Compiz 0.7.6
Don’t undo it; it’s you video driver most likely
Try:
let it boot to the command line
login as root & password
Type: “sax2 -m 0=vesa” (which is a crappy driver, but will get you up)
do the setup & save
reboot
Now go about getting your good video driver as before:)
Boondock Saint wrote:
>
> I’ve updated through the automatic updater and rebooted.
>
> Now kde does not start anymore and I’m presented the text login
> from tty1. tty7 shows only a black screen. According to ‘ps aux’ kdm is
> running though.
>
> Failsafe mode, however, does start kde. Be it only at 800x600
> resolution on a 1920x1200 screen.
>
> Can I undo this update somehow?
>
>
> I’m running:
> Lenovo T61p
> Core 2 Duo T9300
> 2 gb ram
> Opensuse 11.0
> KDE 3.5
> Compiz 0.7.6
How did you install the video driver? If you used Yast, then the kernel
module was updated and we have one case. If compiled the driver or
installed from any source not using Yast (or RPM), you need to re-install
the driver to get the kernel modules updated. I had the same issue with
the VirtualBox pre-compiled binary - simply re-ran the installer that came
with the package and all was well.
–
Will Honea
Mine went well also…
On another note you should consider migrating to VirtualBox… I’ll be blogging why I switched soon.
I have a similar problem.
I updated the kernel and when I rebooted the following happened:
Computer was stuck at POST. I had to shut it down, not reset, in order to get the GRUB menu.
Selecting the opensuse as normal I get a black screen and it just sits there. I need to shutdown and get the GRUB menu again.
Selecting failsafe starts up and it loads gnome or kde fine with the resolution resulting in a big screen.
Any ideas? I can’t say it is the drivers because it’s not even starting.
Thank you
Sorry guys, it was late and I should have stated my video card :rolleyes:
Anyway, reinstalling the Nvidia drivers did the trick!
Once I get home, I’ll try re-installing the Nvidia drivers too. But really stupid question. Did you re-install thru Yast?
Thank you.
No problems here on my x86-64 machine, and I am using the nVidia drivers in the repo and installed via SaX2 -r -m 0=nvidia.
I`ve update without problem.I use opensuse 11 x64.I am using Ati drivers.
see you soon.
ok, i ran the following command.
SaX2 -r -m 0=nvidia
No good, I then tried to update the nvidia drivers via Yast and no help either.
This is what is happening
I can boot into failsafe then I go to shutdown and choose restart. The computer reboots and it gets stuck on the POST screen. I have to shutdown the machine and then turn it back on and it goes past POST and displays the GRUB menu. If I select opensuse 11, I get a black screen and nothing else.
Is there a BIOS setting that I should look at?
Also, can I rollback and go to a previous version?
Everything was fine prior to the Kernel update. Any suggestions would be greatly appreciated. I really don’t want to boot up to XP.
Thank you
No need to reply to this one, instead you can mock for the idiot that I am. :rolleyes: The thing that was hanging my POST was the USB memory card drive. I unplugged that and everything was fine. Opensuse started too, about that! I probably didn’t need to do anything with the nvidia drivers.
Oh well, I guess I learned my lesson and I can say the kernel update went fine. 
Ok, sorry if this question is slightly off topic, but if I decide not to upgrade to the new kernel, does that pose a significant security risk to me?
No, I wouldn’t say so, unless I hear of a specific major vulnerability with the 2.6.25 line, which I haven’t heard of.
Thread moved to Applications