On Tue, Dec 22, 2009 at 12:35 AM, Frank Hale <frankhale@xxxxxxxxx> wrote: > I was using the testing kernel 2.6.32 without an issue but then when > the kernel went to core my system would no longer boot. It would start > to boot half way then just go dead. I don't have any error messages to > post because the screen went blank. Grub was working fine as far as I > can tell. I had to use the Arch live CD to revert kernels back to an > earlier version. Has anyone been having issues with the stable kernel > 2.6.32? Like I said, 2.6.32 from testing worked fine. > Uh ? It is the same package that moves from testing to core. The move cannot break anything. When you use testing, and a package gets moved, you cannot even notice it, because pacman -Su won't do anything : you already have the latest packages. Maybe you want to be a bit more specific about which version exactly you were using ? If you don't know, you can check pacman logs. The changes to kernel26 can be seen here : http://repos.archlinux.org/wsvn/packages/kernel26/trunk/?op=log&rev=0&isdir=1 There has apparently been one revision for each stable kernel release so : 2.6.32-1 2.6.32.1-1 2.6.32.2-1 2.6.32.2 contains 5 radeon patches : http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.32.2 If you can actually confirm that this is what broke your setup, this narrows down the issue extremely. The list of changes between 2.6.31 and 2.6.32 is likely awfully huge.
