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. Thanks.
On Mon, 21 Dec 2009 18:35:30 -0500 Frank Hale <frankhale@gmail.com> wrote:
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.
if you had a ati card with KMS enabled, try to add "nomodeset" to the kernel line in grub. -- Ian-Xue Li <da.mi.spirit@gmail.com>
I do have an ATI card. I'll try that thanks! I did notice that 2.6.32 would boot into a graphical mode shortly after it started booting even though I didn't have one set in my GRUB conf. 2.6.31 didn't do this. Thanks for the help! On Mon, Dec 21, 2009 at 7:05 PM, Ian-Xue Li <da.mi.spirit@gmail.com> wrote:
On Mon, 21 Dec 2009 18:35:30 -0500 Frank Hale <frankhale@gmail.com> wrote:
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.
if you had a ati card with KMS enabled, try to add "nomodeset" to the kernel line in grub.
-- Ian-Xue Li <da.mi.spirit@gmail.com>
Adding "nomodeset" to my kernel boot line in Grub fixed the problem. Thanks! On Mon, Dec 21, 2009 at 7:29 PM, Frank Hale <frankhale@gmail.com> wrote:
I do have an ATI card. I'll try that thanks! I did notice that 2.6.32 would boot into a graphical mode shortly after it started booting even though I didn't have one set in my GRUB conf. 2.6.31 didn't do this. Thanks for the help!
On Mon, Dec 21, 2009 at 7:05 PM, Ian-Xue Li <da.mi.spirit@gmail.com> wrote:
On Mon, 21 Dec 2009 18:35:30 -0500 Frank Hale <frankhale@gmail.com> wrote:
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.
if you had a ati card with KMS enabled, try to add "nomodeset" to the kernel line in grub.
-- Ian-Xue Li <da.mi.spirit@gmail.com>
On Tue, Dec 22, 2009 at 12:35 AM, Frank Hale <frankhale@gmail.com> 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.
On Tue, 2009-12-22 at 09:49 +0100, Xavier wrote:
On Tue, Dec 22, 2009 at 12:35 AM, Frank Hale <frankhale@gmail.com> 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.
Something's been bugging me about this email, and I just realized, 2.6.32 hasn't moved to core yet!
2009/12/22 Ng Oon-Ee <ngoonee@gmail.com>:
Something's been bugging me about this email, and I just realized, 2.6.32 hasn't moved to core yet!
Ah ah, right. I thought it could have moved, since it seemed to be ready and got a few signoff. And Frank said it moved. I assumed it was just the package web page that wasn't up-to-date (I believe I already saw that a few times), but usually the websvn view is up-to-date and I didn't check it carefully. My mistake.
Something's been bugging me about this email, and I just realized, 2.6.32 hasn't moved to core yet!
Oops, you are absolutely correct. I don't know why I assumed this. It appears that the issue started for me with kernel26 2.6.32.2-1.
Adding "nomodeset" to the kernel boot line will allow the kernel to boot fine with no issues. If I don't add that the screen I am assuming tries to go into an unsupported video mode and then goes black. Setting a vga mode in Grub doesn't seem to affect this at all. I'll do some more testing tonight and see if I can gather more information about the actual problem. On Tue, Dec 22, 2009 at 7:29 AM, Frank Hale <frankhale@gmail.com> wrote:
Something's been bugging me about this email, and I just realized, 2.6.32 hasn't moved to core yet!
Oops, you are absolutely correct. I don't know why I assumed this. It appears that the issue started for me with kernel26 2.6.32.2-1.
Le mardi 22 décembre 2009 à 09:49 +0100, Xavier a écrit :
On Tue, Dec 22, 2009 at 12:35 AM, Frank Hale <frankhale@gmail.com> 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.
It seems that 2.6.32.2 is broken with r600 chips : http://old.nabble.com/-stable--Regression-in-2.6.32.2:-radeon-KMS-hangs-syst... and http://old.nabble.com/-PATCH--stable---drm-radeon-kms:-fix-crtc-vblank-updat.... Paul
On 12/22/2009 05:37 AM, Paul Ezvan wrote:
Le mardi 22 décembre 2009 à 09:49 +0100, Xavier a écrit :
On Tue, Dec 22, 2009 at 12:35 AM, Frank Hale<frankhale@gmail.com> 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.
It seems that 2.6.32.2 is broken with r600 chips : http://old.nabble.com/-stable--Regression-in-2.6.32.2:-radeon-KMS-hangs-syst... and http://old.nabble.com/-PATCH--stable---drm-radeon-kms:-fix-crtc-vblank-updat....
Paul
Yes ... it does not work here (KMS + Radeon Mobility HD 3670). Works fine with "nomodeset" Ignacio
This is what my video card shows when I do lspci 01:00.0 VGA compatible controller: ATI Technologies Inc RV610 video device [Radeon HD 2400 PRO] On Tue, Dec 22, 2009 at 10:32 AM, Ignacio Galmarino <igalmarino@gmail.com> wrote:
On 12/22/2009 05:37 AM, Paul Ezvan wrote:
Le mardi 22 décembre 2009 à 09:49 +0100, Xavier a écrit :
On Tue, Dec 22, 2009 at 12:35 AM, Frank Hale<frankhale@gmail.com> 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.
It seems that 2.6.32.2 is broken with r600 chips :
http://old.nabble.com/-stable--Regression-in-2.6.32.2:-radeon-KMS-hangs-syst... and
http://old.nabble.com/-PATCH--stable---drm-radeon-kms:-fix-crtc-vblank-updat....
Paul
Yes ... it does not work here (KMS + Radeon Mobility HD 3670). Works fine with "nomodeset"
Ignacio
I can't figure out how to use tuxonice or even "default" suspend with KMS enabled kernel 2.6.32.y, do you guys know anything about that?
participants (7)
-
Frank Hale
-
Ian-Xue Li
-
Ignacio Galmarino
-
Ng Oon-Ee
-
Paul Ezvan
-
Vasiliy Kurdin
-
Xavier