My experience: if hardware gives trouble, first change kernel-desktop to kernel-default. Seen quite some laptops now, Acer, Asus, HP/Compaq, that seem to require kernel-default. At least, they do work completely with kernel-default, not with kernel-desktop.
The kernels 2.6.31 and 2.6.32 all have trouble with internet and RT61pci driver mostley dhcpd is not started
Even a misfitted 70-persistent-net.rules . I changed that
and 2.6.31 had internet bud very buggy loosing connection.
This is reported on Bugzilla
The original Ralink drivers wont compile on 2.6.3x
So i am stuck with the 2.6.29 kernel and all is working like clockwork.
I have a box that runs fine on 2.6.27.X but barfs at all the 2.6.31 kernels. If can try 2.6.29, and then 2.6.28 or 2.6.30 without compiling itād save much time. And narrow down which kernel, broke things.
the only more recent kernel i could find is 2.6.29rc4ā¦ all others are either (much) older or newer. Couldnāt find 2.6.30 either (I have it here but only in RPM source format for 64bit)
Probably on the configuration side and maybe few additional patches. Itās really specific to the kernel so youāll have to dig through and see what makes it different from the default oneā¦ I read a bit too many complains on default SUSE kernels and I blame those responsible for packaging/configuring them for the problems (Iām looking at you Jeff & Greg ;)). In itself, the mainline 2.6.31 kernels are just fine. Itās the packagers that screwed up in some way during config. Iāve no problems at all with self-configured & compiled kernels from the 2.6.31 series and also noticed that a few have reconfigured the same SUSE kernel in 11.2, compiled it, and suddenly their problems went away, but are present when they boot up the default SUSE kernel
Iāve suggested on Kernel mail list, that keeping some āgoldenā kernels around they make for ākotdā would help bisect problems for upgraders, and lead to better kernel bug reports. cross fingers perhaps someone will
