From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60606] vga_switcheroo / new Radeon DPM code mess up fbcon
Date: Mon, 05 Aug 2013 12:33:43 +0000 [thread overview]
Message-ID: <bug-60606-2300-tyBnaJC0sZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60606-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60606
--- Comment #2 from Sebastien Fievet <sebastien.fievet@free.fr> ---
After a *lot* of googling effort, I managed to narrow down and find a
workaround to this bug.
- First, my mistake was to have an xorg.conf.d directory defining the video
drivers.
Letting X auto detect the driver was the necessary first step.
- Second I applied the "drm/i915: do not disable backlight on vgaswitcheroo
switch off" patch referenced in
https://bugs.freedesktop.org/show_bug.cgi?id=59785
It made switching from IGD to discrete functional, but switching away from
IGD with discrete OFF was still screwing up the display.
- Finally, I found
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1077675, which was
reporting the exact same bug as I was experiencing.
Same hardware, same issue. Same workaround : echoing MIGD to
/sys/kernel/debug/vgaswitcheroo/switch restores display when discrete is
switched back ON
- I am now on 3.11.0-rc4 + drm/i915 patch and everything works fine (with the
workaround)
Conclusion :
1. DPM is not involved at all.
2. Switcheroo doesn't fully support Acer 3820TG hybrid (muxed) laptop out of
the box, but workaround exists.
If anyone wants to investigate further, I'll be glad to provide any relevant
information.
Thanks,
Seb.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-08-05 12:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 19:55 [Bug 60606] New: vga_switcheroo / new Radeon DPM code mess up fbcon bugzilla-daemon
2013-07-22 20:16 ` [Bug 60606] " bugzilla-daemon
2013-08-05 12:33 ` bugzilla-daemon [this message]
2013-08-08 7:00 ` bugzilla-daemon
2013-08-08 10:10 ` bugzilla-daemon
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-60606-2300-tyBnaJC0sZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).