I am using Hardy heron and after updating to Linux 2.6.24-21-generic #1 SMP
suspend failed to resume. It was working in Linux 2.6.24-19-generic.
I am not sure if I have to report this as a different bug ?
below I attached my lspci -vvnn and cat /var/log/Xorg.0.log
** Attachment added: "lspci_Xor
I have rechecked it with the older Kernel. It seems to be a kernel fix
since it only works with the new 2.6.24-8 Ubuntu kernel and not the
version before.
--
[Hardy] [regression] latest update to the intel driver fails suspend
https://bugs.launchpad.net/bugs/190153
You received this bug notificat
hmm, that was not applied yet, so maybe it was something in 2.6.24.1
that fixed this. Either way, nice.
--
[Hardy] [regression] latest update to the intel driver fails suspend
https://bugs.launchpad.net/bugs/190153
You received this bug notification because you are a member of Ubuntu
Bugs, which
Seems to be fixed in current Hardy with lastest kernel package. Thanks!
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
[Hardy] [regression] latest update to the intel driver fails suspend
https://bugs.launchpad.net/bugs/190153
You received this bug notification because
That could very well be the fix. Perhaps someone could build a test
kernel with that patch to try out?
--
[Hardy] [regression] latest update to the intel driver fails suspend
https://bugs.launchpad.net/bugs/190153
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I mean that commit is in .25-rc1, and might fix this.
--
[Hardy] [regression] latest update to the intel driver fails suspend
https://bugs.launchpad.net/bugs/190153
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
perhaps its this commit:
commit ba8bbcf6ff4650712f64c0ef61139c73898e2165
Author: Jesse Barnes <[EMAIL PROTECTED]>
Date: Thu Nov 22 14:14:14 2007 +1000
i915: add suspend/resume support
Add suspend/resume support to the i915 driver. Moves some of the
initialization into the driv
I have now been using the drm modules from git with 2.6.24, and
everything has worked just fine. The native suspend/resume of the intel
driver (which was merged in 2.6.25) might be the reason for all I know.
I'm quite certain now that the bug cannot be fixed in intel driver, but
rather in the drm