At Donnerstag, 31. Dezember 2009 03:51 Chris Brannon wrote: >> If you, too, don't use [testing] and get kernel panics then this is >> because there is at least one important package update which is needed >> by kernel26 2.6.32.2-2 missing in [core]. I guess it's mkinitcpio. If >> you update your system to [testing] then it works again. > > I'm running 2.6.32.2-1 just fine on a box that has never had [testing] > enabled. +1 I think it would be better to search too the reason at another place than only mkinitcpio. And yes, i don't use testing too. Good Luck Steve and perhaps it would be a good idea to use an own kernel package for 2.6.31.x to have this as fallback and therefore better possibilies to find out why 2.6.32 don't works for you. See you, Attila