Am Wed, 30 Dec 2009 18:54:16 -0700 schrieb Steve Holmes :

Hey, has anyone been experiencing any problems with the newest kernel26 package from Arch? this would be 2.6.32.2. After upgrading to it, my machine starts to boot but then dies. When I downgrade to kernel26-2.6.31.6, all works fine again. I'm a totally blind guy so haven't had a chance to get anyone to look at the screen for me but one thing sure, no messages get logged to /var/log/syslog or messages. Just thought I would check to see if I'm not alone with these kernel problems. For now, I'm gonna have to downgrade my kernel once again so at least my machine will work again.

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. So the packages which are currently in [testing] urgently need to be moved to [core] or kernel26 2.6.32.2-2 urgently needs to be moved back to [testing] until the other packages are moved to [core], too. I think the first option is the better one. This should be done before more users, who are using the stable repos, get serious problems. See my bug report at http://bugs.archlinux.org/task/17649 and my e-mail "[arch-general] Kernel panic with kernel26 2.6.32.2-2 from [core]". Greetings, Heiko

Chris Brannon wrote:

Heiko Baums writes:

...

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.

I'm using 2.6.32.2-2 and I only used [testing] to install udev-compat. Working great.

On Thu, Dec 31, 2009 at 09:50:26AM +0000, Paulo Santos wrote:

Chris Brannon wrote:

...

Heiko Baums writes:

...

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.

I'm using 2.6.32.2-2 and I only used [testing] to install udev-compat.

Working great.

I upgraded two systems here to 2.6.32 without any problems, I have never used testing, and everything seems fine. Chuck -- The Moon is Full General web site: www.hallenbeck.ftml.net Audio editor weblog: edway.wordpress.com Or jabber 1on1 with me, chuckh1@jabber.org -------- Violence is a sword that has no handle -- you have to hold the blade.

I always expect problems with my setup when updating with more than just a bugfix release kernel, but no issues with this one. This is a workstation with 8-cores, a finicky motherboard and screwball lvm+raid setup. Never used testing either. Another great job by the Arch devs. On Dec 31, 2009 6:21 AM, "Attila" wrote: At Donnerstag, 31. Dezember 2009 03:51 Chris Brannon wrote: >> If you, too, don't use [testing] and... +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