CynicalPride, thanks a lot!
I had actually solved my problem myself by doing exactly what you said.
I got the ATI drivers using:
wget www2.ati.com/drivers/linux/ati-driver-installer-9.2-x86.x86_64.run
Then, I ran it with sudo sh ./ati-driver-installer-9.2-x86.x86_64.run
It did the kernel module compilation itself, and I restarted after
aticonfig --initial --force
Voilà!
Actually it messed with my dpi settings so maybe the --force option is not a good idea…
I hope this helps somebody else too! 
theGryphon,
Happy to …uh…“almost” help, lol. I am glad to hear that you fixed your problem,and ever happier to hear that you solved them through your own resolve.
CynicalPride
Nobody even cared about my small question here…
Again: Is it possible to clean up old kernel files as well as files that are not needed by the system anymore? Maybe that´s possible with a typed command somehow?
TheMask.***
Hey guys,
I wanted to share my experience with the updated kernel in that it is not good at all.
I’m using KDE 4.2 and the start-up time has drastically increased. It’s fine till the login screen but KDE itself loads very slowly.
Second, all my Wine programs take a lifetime to load and there are crashes that didn’t happen before. I took a look and what happens is that when I start a Wine program, X takes 100% cpu time on one of my four cores. This happens each time I start a Wine program. I have no idea why…
Any suggestions?
I am not experiencing any performance gains, it was snappy before and it is now too. Well, except for the points above…
Cheers!
PS: Sorry TheMask, I don’t have the knowhow to help you there…
Thats not true. ken_yap answered your question within 1 minute. A VERY fast response. Perhaps you need more detail from him?
Partly true, oldcpu.
Thing is I do not want to just clean up the kernel packages, but rather unneded files of the system as well as “junk” that is left from broken/failed installation as well as files that are left over in the “registry”. Now because I do now want to lock this kernel-upgrade thread with my own questions, I´ve opened a separate one here: System cleanup. - openSUSE Forums
Thanks for caring.
TheMask.
OK, another update from me: I just rolled back to previous kernel using repo-oss. I simply couldn’t take the slow-down. I might try later or just wait for the next distro-update.
If anybody wants to roll back, you should first rename/delete “/usr/src/linux-obj”…
Certainly, any solutions to KDE and/or Wine slow-down are highly welcomed and appreciated! Thanks!
I found a script online some years ago to clean old kernel and related files.
ask our friend google.
I would suggest that you keep the old kernel for some time incase you want to fall back on it. I have learnt it the hard way. 
Cheers
Hi,
thanks for the tip with this repository! It worked :)! But you have to be careful, by default, opensuse choose the stable and the unstable driver in parallel. I deselected the unstable driver and only the stable one was installed. I didn’t try out to install both drivers in parallel ;).
The problem with not working “log out” or “switch off” is gone after some “reboots”.
First, I tried also to go back to the old kernel.Here, the installation of the old kernel-source (I need for manual installation of the Nvidia driver) failed.
Greetings and thanks
Michael
P.S.: It’s not a clever idea of Opensuse to offer an kernel update which will be installed with the normal updates and leads to massive problems, which can not be tackled by a normal user (the normal user would not find these additional repositories)
Luckily, I do not need that driver.
I only had to rebuild the usb-rndis driver for my WM6 device.
theGryphon adjusted his/her tinfoil beanie to write:
>
> Hey guys,
> I wanted to share my experience with the updated kernel in that it is
> not good at all.
>
> I’m using KDE 4.2 and the start-up time has drastically increased.
> It’s fine till the login screen but KDE itself loads very slowly.
>
> Second, all my Wine programs take a lifetime to load and there are
> crashes that didn’t happen before. I took a look and what happens is
> that when I start a Wine program, X takes 100% cpu time on one of my
> four cores. This happens each time I start a Wine program. I have no
> idea why…
>
> Any suggestions?
I have updated this afternoon here on this machine and init and X were
using 100% on both CPU`s, ACPI was running amok and such like ( ATI
card here with recompiled modules ) also had to disable desktop effects
whci were working fine before update.
Have tried various boot options but irqpoll seems to have stabilised the
system somewhat.
Have not had time to look further though.
HTH
–
Mark
Nil illegitimi carborundum
I had the X taking 100% cpu only when I started a Wine program, and init was fine.
I suspect Wine has some kernel modules but I couldn’t figure what. I even re-installed Wine but it didn’t help.
I have no explanation for very slow KDE startup times though…
As I said, I rolled back to 2.6.27.7-9.1, and it runs fine now although both KDE and Wine startup times are still not as fast as it used to be.
At the end, I really think that this Kernel update is not thoroughly tested against different configurations and it is obviously not “just a security update”. They should be more user-centric in an update that’s offered to everybody as a security update.
Well, enough ranting, I’m still expecting to hear others’ experiences with KDE (4.x) and Wine…
I read in a blog post that installing the realtime kernel solved some problems. Anybody tried that? What is the differences between the default kernel and realtime (trace) kernel? Thanks!
goes back to lurking state
Hi,
So I understand why the changes, I also understand why I have to recompile (make, make install) the highpoint rr1740 kernel driver for my raid 5 array.
What I DON’T understand is why I cannot find the source for 2.6.27.19-3.2 on the build service’s one click install or anywhere else (so far).
I kind of need that stuff to get my raid card to stop beeping like a smoke alarm, let alone access my files.
Can anyone point me to the source please?
Also I just noticed that uname -a gets me
2.6.27.19-3.2-default #1 SMP 2009-02-25 15:40:44 +0100 i686 athlon i386 GNU/Linux
and not “2.6.27.19-3.2.1” did it change again?
Also, is there a way to get the system to just not mount a secondary filesystem that fails the check at boot instead of throwing me into a recovery console?
I suspect that I will end up going through this every time they update the kernel.
Thanks for your help!
@dstaples:
In parallel with the kernel, I was able to update the kernel source from the opensuse update repository.
Greetings
Michael
Michael,
With that thought in mind, I checked in yast and it says that the new source is already installed!
Considering that the first thing i tried was to redo the make & make install for the raid controller, (which was all I had to do the first time) i think i might be in in real trouble now.
Thanks for the clue.
Yup, I’m fish (as in scrod).
I try to re make (link?) the highpoint rocketraid 1740 kernel module and I get some warnings that I don’t remember seeing when i was running the previous kernel & set it up, and of course now it doesn’t work.
I am not personally capable of fixing this (at least so far) so I emailed highpoint tech support but till they fix it/tell me how I’d like to downgrade to the previous kernel, try as I might I cant seem to find the package. Can anyone point me to a clue?
While I’m asking for a clue, can anyone tell me what the feature was that allowed me to keep (and optionally boot from) various previous versions of the kernel? it showed a menu of choices at grub I think.
Thanks.
D
If anyone is feeling froggy the driver package is at
http://www.highpoint-tech.com/BIOS_Driver/rr1740/Linux/rr174x-linux-src-v2.1-080710-1311.tar.gz
I’m pasting the make & make install text with the error here too
thanks again,
begin paste—
linux-0pmp:/lib/rr174x-linux-src-v2.1/product/rr1740pm/linux # make
make[1]: Entering directory /usr/src/linux-2.6.27.19-3.2-obj/i386/default' make -C ../../../linux-2.6.27.19-3.2 O=/usr/src/linux-2.6.27.19-3.2-obj/i386/default/. modules CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/os_linux.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/osm_linux.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/div64.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/hptinfo.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/config.o LD [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/rr174x.o Building modules, stage 2. MODPOST 1 modules WARNING: could not find /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/.him_rr1740pm.o.cmd for /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/him_rr1740pm.o LD [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/rr174x.ko make[1]: Leaving directory /usr/src/linux-2.6.27.19-3.2-obj/i386/default’
linux-0pmp:/lib/rr174x-linux-src-v2.1/product/rr1740pm/linux # make install
make[1]: Entering directory /usr/src/linux-2.6.27.19-3.2-obj/i386/default' make -C ../../../linux-2.6.27.19-3.2 O=/usr/src/linux-2.6.27.19-3.2-obj/i386/default/. modules CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/os_linux.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/osm_linux.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/div64.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/hptinfo.o CC [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/config.o LD [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/rr174x.o Building modules, stage 2. MODPOST 1 modules WARNING: could not find /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/.him_rr1740pm.o.cmd for /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/him_rr1740pm.o LD [M] /lib/rr174x-linux-src-v2.1/product/rr1740pm/linux/.build/rr174x.ko make[1]: Leaving directory /usr/src/linux-2.6.27.19-3.2-obj/i386/default’
You made a module which is for current kernel 2.6.27.19-3.2-default.
Deleting previous installed driver module rr174x…
Install the new driver module…
Updating module dependencies…Done.
Checking for initrd images to be updated…
Kernel image: /boot/vmlinuz-2.6.27.19-3.2-default
Initrd image: /boot/initrd-2.6.27.19-3.2-default
Root device: /dev/disk/by-id/ata-Maxtor_6E040L0_E1CCX0PE-part2 (/dev/sda2) (mounted on / as ext3)
Resume device: /dev/disk/by-id/ata-Maxtor_6E040L0_E1CCX0PE-part1 (/dev/sda1)
Kernel Modules: hwmon thermal_sys processor thermal fan jbd mbcache ext3 dock scsi_mod libata pata_amd edd crc-t10dif sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid
Features: block usb resume.userspace resume.kernel
Bootsplash: openSUSE (1280x1024)
24362 blocks
Working just fine for me, see Laptop sig;)
I updated 2 PCs successfully to the new kernel:
But as near as I can determine, everything worked fine. No dramas.
Later this weekend, I plan to update the new laptop (Dell Studio 15) and my main desktop PC. The Dell Studio 15 in particular has me interested wrt the new kernel, as that model Dell laptop requires the 2.6.27 kernel for both its audio and wireless to function. I believe Novell/SuSE-GmbH had to back port some code to get that functional, and I’m curious to see if the backport has been maintained.
Hi dstaples,
I was able to use the new kernel source (32 bit, PAE) to “compile” the Nvidia (180.29) driver.
sorry, I have no better idea 
Greetings
Michael
This is a perennial problem with kernel updates, not only with openSUSE, but to a lessor extent with other distributions. Thus far no one has come up with a solution that prevents some breakage. Because of the very anarchic nature of open source free software, often when there is a kernel update ready for release, the manufacturers do not have a driver available to support that kernel version. I’ve on occasion wondered if this is a fundamental design limitation with Linux, where drivers are so impacted by kernel updates.