<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - ATI radeon driver displays nothing or a client refused to switch message on hybrid graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=94811#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - ATI radeon driver displays nothing or a client refused to switch message on hybrid graphics" href="https://bugs.freedesktop.org/show_bug.cgi?id=94811">bug 94811</a> from <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to Saurav from <a href="show_bug.cgi?id=94811#c7">comment #7</a>) > (In reply to Michel Dänzer from <a href="show_bug.cgi?id=94811#c6">comment #6</a>) > > Looks like the AMD GPU has no physical display connections, so running X on > > that alone isn't possible, and I'm not sure vgaswitcheroo is useful either. > > How does fglrx work on Ubuntu 15.10, then? Booting with fglrx installed > (which creates the XOrg configuration file I have posted for radeon but with > "fglrx" instead of "radeon" for the driver) works properly and selects the > AMD chip. The active GPU is shown as the AMD one in both the GUI > (Unity/GNOME system details panel) and by the text-mode tools (glxinfo, > inxi, etc.). The intel driver still drives the display. fglrx just copies the rendered content to the intel display buffer. > > Also, with the radeon driver, the system does not select the AMD chip for > HDMI either. The AMD chip you have does not even have display hardware. You have a muxless system which means the dGPU is only used for offscreen rendering. The dGPU renders to an offscreen buffer and it's copied to the integrated GPU for display.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>