On Sun, Sep 6, 2015 at 6:53 PM, Lennart Poettering
wrote:
> On Sun, 06.09.15 18:24, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>
>> On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering
>> wrote:
>> > On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>> >
>> > I fear thi
On Sun, 06.09.15 18:24, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering
> wrote:
> > On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> >
> > I fear this newer Plugable device is not as carefully designed as the
> > old
On Sun, Sep 6, 2015 at 5:22 PM, Lennart Poettering
wrote:
> On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>
> I fear this newer Plugable device is not as carefully designed as the
> older ones, and uses non-recognizable vendor/product ids... Thus we
> cannot really add
On Sun, 06.09.15 16:31, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
I fear this newer Plugable device is not as carefully designed as the
older ones, and uses non-recognizable vendor/product ids... Thus we
cannot really add an ID_AUTO_SEAT rule from upstream for it. Pity.
Lennart
--
Lenna
On Sun, Sep 6, 2015 at 4:19 PM, Lennart Poettering
wrote:
> On Sun, 06.09.15 16:02, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>
>> > 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
On Sun, 06.09.15 16:02, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> > 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
On Sun, Sep 6, 2015 at 3:36 PM, Lennart Poettering
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
>> wrote:
>> > On Sun, 06.09.15 13:01, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>> >
>> >> On Sun, S
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
> 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
> >> wrote:
> >> > On T
On Sun, Sep 6, 2015 at 1:08 PM, Lennart Poettering
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
>> wrote:
>> > On Thu, 03.09.15 13:26, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
>> >
>> >> I plan t
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
> 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
> >> al
On Sun, Sep 6, 2015 at 12:53 PM, Lennart Poettering
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 a
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
On Fri, Sep 4, 2015 at 9:36 PM, Floris wrote:
>
>> I can't create a new seat1, no idea why.
>>
>> Here is my current configuration:
>>
>> -nvidia card + nvidia driver + nouveau blacklisted
>> - USB 3 dock station with displaylink driver + systemd service
>> - gdm
>> - systemd 219
>>
>>
>>
I can't create a new seat1, no idea why.
Here is my current configuration:
-nvidia card + nvidia driver + nouveau blacklisted
- USB 3 dock station with displaylink driver + systemd service
- gdm
- systemd 219
---
$ loginc
Arnaud,
You must focus on the graphics/fb* syspaths (since they are tagged as
[MASTER] in udev/logind), not the drm/card* ones. You must attach the
[MASTER] devnode to a new seat in order to create it.
BTW, systemd already ships udev rules to set property ID_AUTOSEAT for
DisplayLink USB 2.0 Docki
On Thu, Sep 3, 2015 at 5:06 PM, arnaud gaboury wrote:
>
> On Thu, Sep 3, 2015, 3:46 PM Floris wrote:
>
>>
>> I was missing one piece of the puzzle. My USB dock station is
>> Plugable® UD-3900 USB 3.0
>>
>>
>> 1-
>> I had to install the kern
On Thu, Sep 3, 2015, 3:46 PM Floris wrote:
>
> I was missing one piece of the puzzle. My USB dock station is
> Plugable® UD-3900 USB 3.0
>
>
> 1-
> I had to install the kernel driver for it, following instructions per
> this displaylink for
I was missing one piece of the puzzle. My USB dock station is
Plugable® UD-3900 USB 3.0
1-
I had to install the kernel driver for it, following instructions per
this displaylink forum[0]. Once the .rpm package installed, I could
verify:
$
On Thu, Sep 3, 2015 at 2:12 PM, Floris wrote:
> Op Thu, 03 Sep 2015 13:51:06 +0200 schreef arnaud gaboury
> :
>
>> On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury
>> 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 u
Op Thu, 03 Sep 2015 13:51:06 +0200 schreef arnaud gaboury
:
On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury
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
On Thu, Sep 3, 2015 at 1:26 PM, arnaud gaboury 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 fo
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
22 matches
Mail list logo
