There are a lot of posts out there with horror stories from people that are up the proverbial creek after applying the latest kernel update.
I for one am not applying this kernel update until I hear someone give the “all clear”, but should we at least post a “sticky”, warning folks not to apply this kernel update? Or should we (ask someone to?) just pull that kernel update from the site?
I had only one problem that I found a quick fix for by searching the forums. My keyboard and mouse were freezing. The script file that was posted(I cannot remember who posted it:sorry) worked like a charm.
I had to boot into run level 3 to install the latest nVidia driver. The hard way…which really is easy----at least for me it is
So, for me it worked like a charm;)
Whether or not you decide to upgrade your kernel or not is your decision; but when I read all of the bugfixes, I personally decided it was worth the risk to update my system.
I have had no problems at all; the main problems appear to have arisen from the replacement of ndiswrapper. If you aren’t using ndiswrapper, you can probably go ahead.
I have updated three machines. On two of them, there were no problems. On the third, grub was not properly updated so I had to boot from a repair disk to get in and fix it.
The update itself seems to be fine. The way it was applied seemed a bit faulty - a network connection problem in the middle of an update should not leave the system unbootable. I recommend editing “/etc/zypp/zypp.conf” before updating, and set it to download the patches before updating.
Well, there’s a new update out, and it acknowledges that the previous one had problems. But the old update is still listed, still requires a reboot to apply, and the last time I applied it my bootloader was completely corrupted, allowing me the single choice of booting into Windows and nothing else. Fixed by completely reinstalling and rejecting this update.
It ought to be taken down completely, since there is no sane way to apply it and move on to the next version unless your system is lucky enough to survive.
For now, I’m not applying the new update until a few days have passed and I see a lack of disaster-related posts. There are hundreds of horror stories scattered across the Web about the last update; I wish I had searched for them before hosing my system with the last one, but that burn taught me not to trust so much.
Dear all opensuseners -
Just received another Kernel update today… Since the last one my Skype will shut down if I try to chat or call someone (all was fine before). Does anyone have a solution for that or is experiencing the same issue? I have already tried re-installing skype from opensuse repos and from the skype webpage but no success so far. I noticed that skype requires libpng12, which i have installed, but I also have libpng14… was it there before or came with the latest’s updates? Could this be the reason why skype is having problems? I would be thankful for any comment.
Cheers,
Joao
Once again, I see a spike in reports of crashed, broken systems after applying the latest kernel update.
Does openSuSE do any sort of testing or quality control anymore? Or do they just dump buggy updates on their server and let their customers do their beta testing? This has gotten to the point of being ridiculous. SuSE used to be the most stable, reliable distro on the market, but the last few releases have been getting steadily worse, and whatever is causing the decline now seems to be creeping into the entire update system.
Is there some way to blacklist updates? I never want to install either of the last two kernel updates, given the horror stories circulating about them and my own dismal experience with the first one (a machine that couldn’t be booted into anything but Windows after grub got KOd) and don’t want to be nagged by the updater every day.
I agree the quality of OpenSUSE has declined markedly over the past 3 or 4 releases. I suspect the project really needs some help! I don’t use 11.3 and I know of several others lurking around here that don’t use it either.
That said, I think there is an upstream bug in the 2.6.34 kernel series. This problem is not specific to OpenSUSE! It’s been a big year for changes in linux, especially around low level video stuff … and the fallout …
2.6.34.7-0.2-desktop works for me but I do very little with video.
I have yet to get a 2.6.36x kernel to work. Last 2 of 3 I tried seemed ok but I could not build the video driver with source and syms installed? Gave up for now.
I’ve built several 2.6.35 kernels from source the most recent was 2.6.35.5 which seems to have some issue I’ll try again in a few days. (Takes a couple hours on my setup).
2.6.35.4 builds and runs flawlessly but I assume there was some reason besides drivers for a 2.6.35.5 release.
Non of the Xen kernels have let me build a video driver maybe nouveau would work but I’ve not much love for it yet.
But I agree is not so much a suse issue no doubt the kernel team does the best it can with what they are given to work with. Pushing a security fix seemed like the best move at the time. There were reports of exploits though very limited from what I read. Had to be on a 64bit system running specific 32bit apps effectively making it non issue for many.