<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - systemd-loginctl should deal better with PCI/PCI-e graphics cards"
href="https://bugs.freedesktop.org/show_bug.cgi?id=56579">56579</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd-loginctl should deal better with PCI/PCI-e graphics cards
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>lbsousajr@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>This is related to another bug I filed in
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=868851">https://bugzilla.redhat.com/show_bug.cgi?id=868851</a> . After reading about
loginctl, I feel that it's optimized for frame buffer devices (mainly USB ones,
like that from Plugable), but is not so friendly with PCI(-e) graphics cards.
Taking my hardware example (a SiliconMotion SM501 PCI card), it's only
attachable by loginctl if I load a kernel module for its frame buffer (namely,
sm501fb), so it can be accessible to X.Org via the generic fbdev driver.
I wonder if loginctl could deal better with PCI graphics cards when creating
additional seats. This is specially useful for Brazil, when we have a huge
educational program based on multiseat computers following the
multiple-graphics-cards model, instead of Plugable devices. Some steps for this
can be very similar to Huo&Cameron patches for ConsoleKit to work with Sun Ray
devices, namely:
1. A new seat could be registered with no need to attach a frame buffer device.
2. In this new seat settings, there sould be an option to pass a custom
xorg.conf with the necessary configuration for the graphics card, similar to
patched-CK displays.d approach.
3. [Optional] For multihead cards, there could be a way to easily launch a bare
(with no Display Manager) underneath X server spanning all heads, on top of
which we can launch a Xephyr instance for each head, assinging it to each seat.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>