From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 93887] New: Amilo Xi 3650: G96M [GeForce 9600M GT]: HDMI monitor stays black after s2ram
Date: Wed, 27 Jan 2016 16:00:53 +0000 [thread overview]
Message-ID: <bug-93887-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1395 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93887
Bug ID: 93887
Summary: Amilo Xi 3650: G96M [GeForce 9600M GT]: HDMI monitor
stays black after s2ram
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: estellnb-7Km2I/eHSAQdnm+yROfE0A@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
When my machine awakes from 'systemctl suspend' my integrated LVDS display
comes up fine while an external HDMI monitor stays black with 'no signal'. As
far as tested the VGA output of my G96M will resume without a problem.
I have tested the following kernel parameters in addition to a plain boot
with nouveau.hdmimhz=225:
* acpi_sleep=s3=bios: resumes well but HDMI stays without a signal
* acpi_sleep=s3_mode: crash on resume with total blackscreen of LVDS as well as
HDMI, a hard reset is the only way out.
* acpi_sleep=s3_bios,s3_mode: same as s3_mode
kernel version: 4.5.0-rc1-ARCH #2 SMP
nouveau version of the Arch package: 1.0.12-1
Is there anything else I can try or do?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2618 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2016-01-27 16:00 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:00 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-93887-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-01-27 16:03 ` [Bug 93887] Amilo Xi 3650: G96M [GeForce 9600M GT]: HDMI monitor stays black after s2ram bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-27 16:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-27 16:44 ` [Bug 93887] [NV96] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-27 16:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-27 20:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-01-28 11:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-13 15:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-21 13:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-25 23:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-25 23:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-25 23:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-26 11:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-26 11:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 21:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 21:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 21:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 21:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 21:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 21:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-02-29 22:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-04 18:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-17 10:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-28 12:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 12:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 13:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 14:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 14:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 14:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 14:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 15:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 16:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 16:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 17:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 17:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 17:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 17:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 18:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-03 19:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 5:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 7:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 7:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 11:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 14:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 15:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 15:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 15:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 15:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-04 15:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-05 10:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-18 9:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-18 10:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-31 11:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-16 5:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-16 8:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-18 18:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-18 19:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-18 19:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-18 20:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-18 22:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-19 4:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-19 14:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-20 18:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-93887-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.