*** This bug is a duplicate of bug 226279 ***
https://bugs.launchpad.net/bugs/226279
Thanks for testing and the update. I'm glad to hear the 2.6.24-19
kernel is working for you. Based on your last comment it would seem
that fixes that were applied for bug 226279 has resolved this issue for
y
2.6.22-19 kernel solved the problem, suspend works again!
Thanks.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Same error with the new 2.6.22-18 kernel. Working nice with 2.6.22-16.
What could cause the problem in the newer kernels?
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/19161
With the new 2.6.22-17 kernel, my computer goes to sleep, but doesn't wake up.
Only I recive is blank unpowered monitor, and the HDD led keeps lighting.
I'm using Hardy with all updates enabled, and daily updated.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.lau
"Wake up by USB device" and "Wake up by LAN" was turned on in the BIOS,
turned off them, and suspend works. So the bug should be searched that
way. In windows, the suspend works well with those wake up settings
above.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.
(2.6.24-16-generic) new kernel, and the old bug.
So i965 guys won't have working suspend in Hardy?!
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Updated to the new kernel (2.6.24-15-generic), suspend still doesn't
work.
** Attachment added: "dmesg_2008.04.05.txt"
http://launchpadlibrarian.net/13134000/dmesg_2008.04.05.txt
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You rece
It's really similar to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/94332
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Tried to trigger a suspend from root terminal (with the same results,
maybe the messages are useful):
# /etc/acpi/sleep.sh sleep
ifdown: interface eth0 not configured
* Shutting down ALSA... [ OK ]
* Saving the system clock
/etc/acpi/resume.d/17-v
Completely uninstalled virtualbox (don't actually use it now). The bug
still occurs.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, please blacklist the vboxdrv module, reboot and try a
suspend/resume. Trying to alleviate the possibility that this is a bug
in something other than the stock kernel.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug
I couldn't make a dmesg log after suspend, because system didn't come up
after the suspend (monitor stayed power off), but when computer went
power off, it immediately waked up again according to the fans.
** Attachment added: "dmesg_nv_before_suspend.txt"
http://launchpadlibrarian.net/12759915
The original report shows that this occured with the nvidia binary
driver installed. Can we see about getting this reproduced using the
open nv xorg driver instead?
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notif
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I use 32bit Hardy, not 64bit
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
** Attachment added: "dmesg_after_suspend_w_ec_intr0.txt"
http://launchpadlibrarian.net/12604632/dmesg_after_suspend_w_ec_intr0.txt
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a mem
I tried your suggestion...doesn't work.
I've modified my menu.lst:
kernel /boot/vmlinuz-2.6.24-12-generic
root=UUID=410c3a15-68c7-4672-bc2b-f18b2d06d5d8 ec_intr=0 ro splash
I've reattached the dmesg outputs before, and after the suspend.
** Attachment added: "dmesg_before_suspend_w_ec_
Also, here are related bugs (they are referring to bad power management
information, but the cause seems to be the same)
bug 147560
bug 139701
Ben, I'll leave it to you to decide if this should be marked duplicate
of one of those (or which of those should be a master for this issue.
Paul Sladen h
Many sources are now showing that using the 64bit version of Ubuntu and
adding "ec_intr=0" before "ro splash" in the /boot/grub/menu.lst file.
Before it looks something like this:
kernel /boot/vmlinuz-2.6.22-14-generic root=/dev/sda1 ro quiet
Change it to look similar to this:
kernel /boot/vmlinu
** Attachment added: "dmesg_after_suspend.txt"
http://launchpadlibrarian.net/12592118/dmesg_after_suspend.txt
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I attach the before-suspend and after-suspend dmesg outputs. After
suspend the computer still wakes up immediately.
** Attachment added: "dmesg_before_suspend.txt"
http://launchpadlibrarian.net/12592116/dmesg_before_suspend.txt
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
** Changed in: linux (Ubuntu)
Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) => Ben Collins
(ben-collins)
Status: Triaged => Incomplete
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification
In the above comment I meant that your two kern.log files were the same,
not empty.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please do not include kern.log. Instead, try a suspend/resume cycle and
send the output of dmesg, since it is much more useful. In your
kern.log, I see no remnants of a suspend attempt (note that your two
files before and after attempt are empty. So in this case, the kernel
has performed no actions
Updated to 2.6.24-12-generic...still doesn't work.
Any chaces that Hardy final will suspend correctly on my machine? (on Archlinux
it works seamlessly, so it is possible)
I'd be glad to help you with this bug, even testing patches.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mo
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Description changed:
- In previous Hardy alphas suspend worked well, but nowdays the same bug occurs
as in Gutsy. When i select suspend, the system goes to suspend, black screen is
coming, the computer goes to power off, then the system immediately wakes up,
then the login screen appears.
-
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please attach the following information (as _separate_ attachments):
Output of 'sudo lspci -vvnn'
Output of 'sudo dmidecode'
Try to hibernate/suspend and then restart the system and attach
/var/log/kern.log.0
T
** Attachment added: "kern.log.just_after_failed_suspend"
http://launchpadlibrarian.net/12152882/kern.log.just_after_failed_suspend
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a mem
** Attachment added: "kern.log.clear_boot"
http://launchpadlibrarian.net/12152881/kern.log.clear_boot
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/12152879/dmidecode.txt
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "acpi_dir.tar.bz2"
http://launchpadlibrarian.net/12152877/acpi_dir.tar.bz2
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "lspci_vvnn.txt"
http://launchpadlibrarian.net/12152884/lspci_vvnn.txt
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Now with 2.6.24-11-generic still doesn't work.
--
[hardy] suspend to ram doesn't work on intel i965 chipset mobo
https://bugs.launchpad.net/bugs/191613
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
34 matches
Mail list logo
