On Sun, Sep 6, 2015 at 3:36 PM, Lennart Poettering <lenn...@poettering.net> wrote: > On Sun, 06.09.15 13:14, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > >> On Sun, Sep 6, 2015 at 1:08 PM, Lennart Poettering >> <lenn...@poettering.net> wrote: >> > On Sun, 06.09.15 13:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >> > >> >> On Sun, Sep 6, 2015 at 12:53 PM, Lennart Poettering >> >> <lenn...@poettering.net> wrote: >> >> > On Thu, 03.09.15 13:26, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: >> >> > >> >> >> I plan to use the systemd mutli-seat features, but I am not sure at >> >> >> all how I must proceed and in waht order. I understand the main >> >> >> principle for mouse and keyboard: detect the device then >> >> >> $ loginctl attach seatNumber DevicePath >> >> >> As for the graphic card, I am lost. >> >> >> >> >> >> OS: Fedora 22 >> >> >> gdm >> >> >> 1 nvidia card >> >> >> 1 USB3 plugable dockin station for the second monitor >> >> > >> >> > I presume this hardware is not marked for "auto seat" yet, using >> >> > udev's ID_AUTO_SEAT property. If you let me know USB product and >> >> > vendor id of this device (as reported by lsusb in hex) I'll add it to >> >> > the default rules files. If that's done then just plugging in the >> >> > device will make it a new seat, without any configuration. >> >> >> >> >> >> Bus 002 Device 005: ID 17e9:4323 DisplayLink >> > >> > The docking station probably is an USB hub with the displaylink device >> > connected to it. the vendor/product ID i am interested in is the id of >> > that hub, i.e. the top-level device in the docking station device. >> >> If it can help, here is the udev rule and service shipped with the rpm: >> >> displaylink.service >> ------------------------------- >> [Unit] >> Description=DisplayLink Manager Service >> After=display-manager.service >> Conflicts=getty@tty7.service >> >> [Service] >> ExecStartPre=/sbin/modprobe evdi >> ExecStart=/usr/lib/displaylink/DisplayLinkManager >> Restart=always >> WorkingDirectory=/usr/lib/displaylink >> RestartSec=5 >> -------------------------------------------- >> >> /etc/udev/rules.d/99-displaylink.rules >> ACTION=="add", SUBSYSTEM=="usb", ENV{ID_VENDOR}=="DisplayLink", >> MODE="0660", RUN+="/bin/systemctl start displaylink.service" >> ACTION=="remove", SUBSYSTEM=="usb", ENV{ID_VENDOR}=="DisplayLink", >> RUN+="/bin/systemctl stop displaylink.service" > > That's awfully generic... > > I'd really just be interested in vendor/product ids if the usb hub > that is built into your docking station, where the display link is > connected to. > > If in doubt, please run "lsusb" once before you plug in the device, > and once after you plug it in, and let me know the difference: all the > lines that appeared in the output by plugging it in.
unplu/plug, diff of $ lsusb Bus 002 Device 005: ID 17e9:4323 DisplayLink Bus 002 Device 004: ID 2109:8110 VIA Labs, Inc. Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 007: ID 2109:2811 VIA Labs, Inc. Hub > > Thanks, > > Lennart > > -- > Lennart Poettering, Red Hat -- google.com/+arnaudgabourygabx _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel