Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Multiseat fails after reboot
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
adomas
n00b
n00b


Joined: 04 May 2011
Posts: 17
Location: Schwerin, Germany

PostPosted: Sun Feb 18, 2018 10:43 pm    Post subject: Multiseat fails after reboot Reply with quote

Hello,
I have switched from Arch to Gentoo and I am unable to configure Multiseat setup on my system properly.

About my system:
I have two GPUs, GPU-0 is GTX 1080 Ti and used for seat0, GPU-1 is GTX 780 and used for seat1. I have two sets of input assigned to each seat via loginctl. I use ~amd64 Gentoo with OpenRC + elogind.

I manage to get Multiseat working, but after reboot it does not work anymore.

What I do:
1) Using loginctl I attach stuff to seat1
2) I generate xorg.conf file with nvidia-settings making a second X Screen on GPU-1
3) At this point second monitor turns on and shows sddm, I can log in and use seat1
4) I reboot the system and seat1 does not work anymore, also seat0 has glitches at this point
5) Deleting xorg.conf and restarting elogind or sddm disables seat1
6) Again I generate a new xorg.conf with nvidia-settings and everything works until reboot

At the point 4) when system is rebooted and xorg.conf is still there, I get loads of stuff going to /var/log/sddm.log and it reaches hundreds of megabytes in size.

In sddm.log I see these lines looping:

Code:

[22:57:31.420] (II) DAEMON: Adding new display on vt 7 ...
[22:57:31.420] (II) DAEMON: Loading theme configuration from ""
[22:57:31.420] (II) DAEMON: Display server starting...
[22:57:31.420] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{f3d977e0-0667-430d-8286-5dc57ecd35f1} -background none -noreset -displayfd 24 -seat seat1
[22:57:31.434] (II) DAEMON: Setting default cursor
[22:57:31.444] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[22:57:31.453] (II) DAEMON: Display server started.
[22:57:31.453] (II) DAEMON: Socket server starting...
[22:57:31.453] (II) DAEMON: Socket server started.
[22:57:31.453] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[22:57:31.454] (II) DAEMON: Greeter starting...
[22:57:31.458] (II) DAEMON: Adding cookie to "/var/run/sddm/{f3d977e0-0667-430d-8286-5dc57ecd35f1}"
[22:57:31.468] (II) HELPER: [PAM] Starting...
[22:57:31.469] (II) HELPER: [PAM] Authenticating...
[22:57:31.469] (II) HELPER: [PAM] returning.
[22:57:31.470] (WW) DAEMON: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
[22:57:31.470] (II) DAEMON: Display server stopped.
[22:57:31.470] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[22:57:31.479] (II) DAEMON: Socket server stopping...
[22:57:31.479] (II) DAEMON: Socket server stopped.
[22:57:31.479] (II) DAEMON: Removing display "" ...


Xorg.1.log has this:

Code:

[   682.564] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[   682.564] (II) Loader magic: 0x558197990c40
[   682.564] (II) Module ABI versions:
[   682.564]    X.Org ANSI C Emulation: 0.4
[   682.564]    X.Org Video Driver: 23.0
[   682.564]    X.Org XInput driver : 24.1
[   682.564]    X.Org Server Extension : 10.0
[   682.564] (II) xfree86: Adding drm device (/dev/dri/card1)
[   682.565] (II) LoadModule: "glx"
[   682.565] (II) Loading /usr/lib64/opengl/nvidia/extensions/libglx.so
[   682.568] (II) Module glx: vendor="NVIDIA Corporation"
[   682.568]    compiled for 4.0.2, module version = 1.0.0
[   682.568]    Module class: X.Org Server Extension
[   682.568] (II) NVIDIA GLX Module  390.25  Wed Jan 24 19:23:51 PST 2018
[   682.568] (II) Applying OutputClass "nvidia" to /dev/dri/card1
[   682.568]    loading driver: nvidia
[   682.568] (==) Matched nvidia as autoconfigured driver 0
[   682.568] (==) Matched nouveau as autoconfigured driver 1
[   682.568] (==) Matched nv as autoconfigured driver 2
[   682.568] (==) Matched modesetting as autoconfigured driver 3
[   682.568] (==) Matched fbdev as autoconfigured driver 4
[   682.568] (==) Matched vesa as autoconfigured driver 5
[   682.568] (==) Assigned the driver to the xf86ConfigLayout
[   682.568] (II) LoadModule: "nvidia"
[   682.568] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so
[   682.568] (II) Module nvidia: vendor="NVIDIA Corporation"
[   682.568]    compiled for 4.0.2, module version = 1.0.0
[   682.568]    Module class: X.Org Video Driver
[   682.568] (II) LoadModule: "nouveau"
[   682.568] (WW) Warning, couldn't open module nouveau
[   682.568] (II) UnloadModule: "nouveau"
[   682.568] (II) Unloading nouveau
[   682.568] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   682.568] (II) LoadModule: "nv"
[   682.568] (WW) Warning, couldn't open module nv
[   682.568] (II) UnloadModule: "nv"
[   682.568] (II) Unloading nv
[   682.568] (EE) Failed to load module "nv" (module does not exist, 0)
[   682.568] (II) LoadModule: "modesetting"
[   682.569] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   682.569] (II) Module modesetting: vendor="X.Org Foundation"
[   682.569]    compiled for 1.19.6, module version = 1.19.6
[   682.569]    Module class: X.Org Video Driver
[   682.569]    ABI class: X.Org Video Driver, version 23.0
[   682.569] (II) LoadModule: "fbdev"
[   682.569] (WW) Warning, couldn't open module fbdev
[   682.569] (II) UnloadModule: "fbdev"
[   682.569] (II) Unloading fbdev
[   682.569] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   682.569] (II) LoadModule: "vesa"
[   682.569] (WW) Warning, couldn't open module vesa
[   682.569] (II) UnloadModule: "vesa"
[   682.569] (II) Unloading vesa
[   682.569] (EE) Failed to load module "vesa" (module does not exist, 0)
[   682.569] (II) NVIDIA dlloader X Driver  390.25  Wed Jan 24 18:57:05 PST 2018
[   682.569] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   682.569] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   682.569] (WW) Falling back to old probe method for modesetting
[   682.569] (EE) No devices detected.
[   682.569] (EE)
Fatal server error:
[   682.569] (EE) no screens found(EE)
[   682.569] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[   682.569] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information.
[   682.569] (EE)
[   682.569] (EE) Server terminated with error (1). Closing log file.



In dmesg I see:
Code:

[    4.881300] input: G15 Keyboard G15 Keyboard as /devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10.4/3-10.4.4/3-10.4.4:1.0/0003:046D:C222.0010/input/input31
[    4.934151] hid-generic 0003:046D:C222.0010: input,hiddev103,hidraw15: USB HID v1.11 Keypad [G15 Keyboard G15 Keyboard] on usb-0000:00:14.0-10.4.4/input0
[    5.453990] elogind[4168]: New seat seat0.
[    5.454064] elogind[4168]: New seat seat1.
[    5.454463] elogind[4168]: Watching system buttons on /dev/input/event1 (Power Button)
[    5.454518] elogind[4168]: Watching system buttons on /dev/input/event0 (Power Button)
[    5.454587] elogind[4168]: Watching system buttons on /dev/input/event4 (Razer Razer DeathAdder 2013)
[    5.454627] elogind[4168]: Watching system buttons on /dev/input/event6 (Razer Razer DeathAdder 2013)
[    5.454667] elogind[4168]: Watching system buttons on /dev/input/event27 (Gaming Keyboard)
[    5.498040] NVRM: Your system is not currently configured to drive a VGA console
               on the primary VGA device. The NVIDIA Linux graphics driver
               requires the use of a text-mode VGA console. Use of other console
               drivers including, but not limited to, vesafb, may result in
               corruption and stability problems, and is not supported.
[    5.619097] elogind[4168]: Watching system buttons on /dev/input/event29 (G15 Keyboard G15 Keyboard)
[    5.635152] elogind[4168]: Watching system buttons on /dev/input/event16 (USB USB Keyboard)
[    5.635213] elogind[4168]: Watching system buttons on /dev/input/event25 (USB USB Keyboard)
[    6.287090] 8021q: 802.1Q VLAN Support v1.8
[    6.311763] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    6.312743] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    6.313757] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    6.313758] cfg80211: failed to load regulatory.db
[    6.489928] NET: Registered protocol family 10
[    6.490119] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[    6.490133] Segment Routing with IPv6
[    6.494584] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    6.495809] Bridge firewalling registered
[    6.501912] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[    6.510509] ip_tables: (C) 2000-2006 Netfilter Core Team
[    6.539435] udevd[3203]: RUN{builtin}: 'uaccess' unknown /lib64/udev/rules.d/73-seat-late.rules:15
[    9.411096] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[    9.411163] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[   13.407896] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[   13.407976] caller _nv001170rm+0xe3/0x1d0 [nvidia] mapping multiple BARs
[   13.640230] nvidia-modeset: Allocated GPU:0 (GPU-4e4b5a1d-9270-5438-8904-eede0a9b35e0) @ PCI:0000:01:00.0
[   14.100904] nvidia-modeset: Allocated GPU:1 (GPU-2e2e14b0-cd12-1ab8-965d-84975ee94a97) @ PCI:0000:02:00.0
[   14.646040] elogind[4168]: New session c1 of user sddm.
[   24.133855] elogind[4168]: New session 1 of user adomas.
[   24.265492] elogind[4168]: Removed session c1.
[  682.957770] elogind[4168]: New session c2 of user sddm.
[  730.966645] elogind[4168]: New session 2 of user natia.
[  731.044299] elogind[4168]: Removed session c2.


My xorg.conf which helps to setup temporary Multiseat:

Code:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 390.25  (portage@genesis)  Sun Feb 18 00:07:14 CET 2018

Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    Screen      1  "Screen1" RightOf "Screen0"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"
    # generated from data in "/etc/conf.d/gpm"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol"
    Option         "Device" "/dev/input/mice"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Samsung U28E590"
    HorizSync       30.0 - 135.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"
    # HorizSync source: unknown, VertRefresh source: unknown
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Samsung SMBX2431"
    HorizSync       0.0 - 0.0
    VertRefresh     0.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 1080 Ti"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 780"
    BusID          "PCI:2:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "nvidiaXineramaInfoOrder" "DFP-5"
    Option         "metamodes" "nvidia-auto-select +0+0"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "Stereo" "0"
    Option         "metamodes" "nvidia-auto-select +0+0 {AllowGSYNC=Off}"
    Option         "SLI" "Off"
    Option         "MultiGPU" "Off"
    Option         "BaseMosaic" "off"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection


Maybe someone are using Multiseat and had similar issue? At the moment I'm lost and unsure how to solve this.
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1296
Location: KUUSANKOSKI, Finland

PostPosted: Sun Feb 18, 2018 11:30 pm    Post subject: Reply with quote

Back when I had GPU on MB and seperate GPU I used to have a multiseta setup.
What I had different was that back then I used systemd as init and I used lightdm as display manager.

If it's not too much of a hassle, try out lightdm. If it works, then sddm has a bug or there's something wrong on your sddm configs.
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
adomas
n00b
n00b


Joined: 04 May 2011
Posts: 17
Location: Schwerin, Germany

PostPosted: Sun Feb 18, 2018 11:44 pm    Post subject: Reply with quote

Well same version of sddm (0.17.0) worked well on Arch. Might be something wrong with sddm.conf, but everything seems to be normal:

Code:

[Autologin]
Relogin=false
Session=
User=

[General]
HaltCommand=/usr/bin/loginctl poweroff
InputMethod=
Numlock=on
RebootCommand=/usr/bin/loginctl reboot

[Theme]
Current=breeze
CursorTheme=Breeze_Snow
DisableAvatarsThreshold=7
EnableAvatars=true
FacesDir=/usr/share/sddm/faces
ThemeDir=/usr/share/sddm/themes

[Users]
DefaultPath=/usr/local/bin:/usr/bin:/bin
HideShells=
HideUsers=
MaximumUid=60000
MinimumUid=1000
RememberLastSession=true
RememberLastUser=true
ReuseSession=false

[Wayland]
EnableHiDPI=true
SessionCommand=/usr/share/sddm/scripts/wayland-session
SessionDir=/usr/share/wayland-sessions
SessionLogFile=.local/share/sddm/wayland-session.log

[X11]
DisplayCommand=/usr/share/sddm/scripts/Xsetup
DisplayStopCommand=/usr/share/sddm/scripts/Xstop
EnableHiDPI=true
MinimumVT=7
ServerArguments=-nolisten tcp
ServerPath=/usr/bin/X
SessionCommand=/usr/share/sddm/scripts/Xsession
SessionDir=/usr/share/xsessions
SessionLogFile=.local/share/sddm/xorg-session.log
UserAuthFile=.Xauthority
XauthPath=/usr/bin/xauth
XephyrPath=/usr/bin/Xephyr


What I noticed, that Xorg runs on tty7 and in Arch it was running in tty1.
Now as seat0 utilized Xorg on tty7, as I see in sddm.log seat1 tries to run Xorg on the very same tty7. Can this be the issue?
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1296
Location: KUUSANKOSKI, Finland

PostPosted: Mon Feb 19, 2018 1:18 am    Post subject: Reply with quote

adomas wrote:
What I noticed, that Xorg runs on tty7 and in Arch it was running in tty1.
Now as seat0 utilized Xorg on tty7, as I see in sddm.log seat1 tries to run Xorg on the very same tty7. Can this be the issue?
It could be... but based on logs you provided it's something with sddm.
Code:
(WW) DAEMON: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
Looks like some qt (?) process dies and then the rest goes with it.

Also, I found this. At least one user there reported that lightdm worked too.
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
adomas
n00b
n00b


Joined: 04 May 2011
Posts: 17
Location: Schwerin, Germany

PostPosted: Mon Feb 19, 2018 1:53 am    Post subject: Reply with quote

Well the problem is Xorg Screen 1 dies as you can see from my Xorg.1.log, that is the reason sddm gets crazy retrying to launch Xorg.

I'm unsure but I think there is no problem with sddm, as sddm-helper does not exit.

At the moment I think it's something with xorg.conf, just unsure what. As I boot-up I let xorg detect stuffs by itself, and later I put xorg.conf to turn on the second Xorg server... It works like it should until reboot.

Checked the the link, I think it is not relevant...

Maybe it's problem with OpenRC? On Arch I had systemd and it worked well with same package versions.
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1296
Location: KUUSANKOSKI, Finland

PostPosted: Mon Feb 19, 2018 10:37 am    Post subject: Reply with quote

adomas wrote:
Maybe it's problem with OpenRC?
I'd blame it rather on elogind. But I doubt it is the problem.

I still had xconfig lest for my second seat.
/etc/X11/xorg.conf.d/79-seat1-screen.conf.disabled:
Section "Device"
        Identifier "OnBoard"
        Driver "radeon"
EndSection

Section "Screen"
        Identifier              "screen1"
        Device                  "OnBoard"
        DefaultDepth    24
        Subsection "Monitor"
                Option "Primary" "true"
        EndSubsection
        Subsection "Display"
                Depth   16
                Modes   "640x480_30.00"
        EndSubsection
EndSection

I didn't specify much more. My first seat config is the same but with two monitors. Maybe you should strip down the configs to bare minimum and let xorg choose the rest?

Also
Code:
NVRM: Your system is not currently configured to drive a VGA console
               on the primary VGA device. The NVIDIA Linux graphics driver
               requires the use of a text-mode VGA console. Use of other console
               drivers including, but not limited to, vesafb, may result in
               corruption and stability problems, and is not supported.
... might be the problem. Although your xorg.log tells that none of those other modules are loaded.

But I'd concentrate to the error of xorg being not able to find screens. There's a wiki section that matches your problem.
One solution would be to run /opt/bin/nvidia-xconfig before rebooting. Maybe create a small stop script inside /etc/local.d?
It's not elegant solution. :(

What does nvidia-xconfig actually do? Creates a new xorg.conf? And something more obviously...
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
adomas
n00b
n00b


Joined: 04 May 2011
Posts: 17
Location: Schwerin, Germany

PostPosted: Mon Feb 19, 2018 5:39 pm    Post subject: Reply with quote

I suspected that is OpenRC problem because of this article:

https://wiki.gentoo.org/wiki/Comparison_of_init_systems

In section "Supported services (in Gentoo)" I see that "X11 Display Manager setup" for OpenRC is "Single service for all (required to auto-restart)."
Somehow I'm unsure what does that mean, but I was thinking maybe it's about that only one DM can run from init? In systemd it says "Separate DM units."

Well about xorg.conf I think you are correct. I need to try to strip down as much as possible and let Xorg autodetect settings. I will try this right now :)

About that NVRM thing, it was always there, it does not depend on distro even. I always was seeing it on all Linux distros I have ran. It is because of NVIDIA proprietary drivers.

About nvidia-xconfig I can't use it, as it setups always only one Xorg Server and one Display. And yes it generates xorg.conf file :) I use graphical nvidia-settings and make a second GPU with a second Monitor to have a separate Xorg server...

I could do a script which moves around xorg.conf, and I think it would work, but it feels like a very dirty solution to me.

I hope stripping xorg.conf to minimum will help out.

Thanks Zucca for helping, if you have any more ideas, I'm interested.
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1296
Location: KUUSANKOSKI, Finland

PostPosted: Mon Feb 19, 2018 6:02 pm    Post subject: Reply with quote

I'd stick a second GPU into my PC if I had space left. :( µATX motherboards have their limits.

Anyway OpenRC should not matter. Your session/login -manager is what matters. You have elogind, and it should be no problem then.
Can you succesfully run multiseat if you change to software OpenGL renderer (elselect opengl list)?
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
adomas
n00b
n00b


Joined: 04 May 2011
Posts: 17
Location: Schwerin, Germany

PostPosted: Tue Feb 20, 2018 2:23 pm    Post subject: Reply with quote

With a software renderer was same problem. I have tried stripping down the xorg.conf to minimum, and got pretty weird results, as seat1 input was for Screen 0 and seat0 input did nothing as Screen 1 was off in a Xorg start-up loop.

Anyway I found sort of solution. I removed nouveau from blacklist and rebooted without xorg.conf and everything just did work as I would like. But as one of my GPUs is GTX 1080 Ti which is pretty new and not well supported by nouveau, I have pretty severe performance issues at least on seat0.

So the point is that NVIDIA proprietary drivers makes this a problem. I'm unsure how to proceed. I was few days already, I really need to get this seat1 working at full speed, as my wife wants to use it for graphics works.

I will try lightdm now.

EDIT: lightdm did not work at all with my configuration...
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1296
Location: KUUSANKOSKI, Finland

PostPosted: Tue Feb 20, 2018 2:43 pm    Post subject: Reply with quote

adomas wrote:
So the point is that NVIDIA proprietary drivers makes this a problem.
I so hoped that it wasn't the drivers. :( I have only AMD GPUs so I cannot give you any tips with Nvidia. :\

adomas wrote:
I will try lightdm now.
Fingers crossed...
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
adomas
n00b
n00b


Joined: 04 May 2011
Posts: 17
Location: Schwerin, Germany

PostPosted: Tue Feb 20, 2018 2:46 pm    Post subject: Reply with quote

Well lightdm did not work at all...

I'm lost and unsure what to try next.

I was using same version of NVIDIA drivers on Arch and everything worked.
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1296
Location: KUUSANKOSKI, Finland

PostPosted: Tue Feb 20, 2018 2:58 pm    Post subject: Reply with quote

adomas wrote:
Well lightdm did not work at all...

I'm lost and unsure what to try next.

I was using same version of NVIDIA drivers on Arch and everything worked.

I'd try to search which X server version is most compatible with the nividia driver version you have. I saw a listing of such somewhere...

Also read the wiki page. There's a lots of troubleshooting information.
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
n17r4m
n00b
n00b


Joined: 22 Jan 2018
Posts: 9

PostPosted: Wed Feb 21, 2018 1:17 am    Post subject: Reply with quote

Just throwing my 2 cents in, since I am running a very similar config as yours..

Often times there was trouble with one or both of the multi-seats not being brought up in a manner very similar to what is happening to you, however after setting up multi-seat, if after a reboot the display's refused to come up, changing the physical port the monitor was connected to in the back of the machine to one next to it (same card, different port), the problem fully resolved itself, and good behavior persisted across reboots. *shrugs* just something kinda non-intuitive that you may want to try,
Back to top
View user's profile Send private message
Nreal
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2009
Posts: 107

PostPosted: Mon Apr 02, 2018 10:54 am    Post subject: Reply with quote

Still have kdm as login manager, have not been able to upgrade the system for a long while.. Stupid thing replacing kdm with alpha sddm... just saying..
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 12356

PostPosted: Tue Apr 03, 2018 2:06 am    Post subject: Reply with quote

Nreal wrote:
Still have kdm as login manager, have not been able to upgrade the system for a long while.. Stupid thing replacing kdm with alpha sddm... just saying..
What prevents you from upgrading the system?
Back to top
View user's profile Send private message
Nreal
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2009
Posts: 107

PostPosted: Thu Apr 05, 2018 8:00 am    Post subject: Reply with quote

Hu wrote:
Nreal wrote:
Still have kdm as login manager, have not been able to upgrade the system for a long while.. Stupid thing replacing kdm with alpha sddm... just saying..
What prevents you from upgrading the system?


Need those 3 multiseat, Ive been using many years, 10 maybe with kdm and it has worked like it should. Havent been able to to get anything else working the way multiseat gentoo wiki says.. Now im only updating chrome and what needs - fresh install is the only option. But theres no working multiseat to install, nothing works here what ive tried- so maybe after a very long time Ill give up with gentoo.. What was so shiny in sddm that kdm was thrown away?
Back to top
View user's profile Send private message
Zucca
Veteran
Veteran


Joined: 14 Jun 2007
Posts: 1296
Location: KUUSANKOSKI, Finland

PostPosted: Thu Apr 05, 2018 8:33 am    Post subject: Reply with quote

Nreal wrote:
fresh install is the only option
In 99% of cases, it's not.
But yeah. If you go with Nvidia the multiseat setup might be complicated to set up. With Nouveau drivers you might have better luck, but then there's other problems...
Excluding one laptop I had year ago, I've been using either ATI/AMD or intel graphics on my PCs and the reason for it can be found from this topic.

If I were a user who used only single monitor on each setup, then I wouldn't mind if I had Nvidia GPU.000000

I guess I just ranting at Nvidia here. :(

Anyway. My experience is - with lightdm multiseat is pretty straight forward thing. You just need to seperate the devices for each seat.
_________________
..: Zucca :..

Code:
ERROR: '--failure' is not an option. Aborting...
Back to top
View user's profile Send private message
Nreal
Tux's lil' helper
Tux's lil' helper


Joined: 06 Jan 2009
Posts: 107

PostPosted: Fri Apr 06, 2018 4:04 am    Post subject: Reply with quote

Not sure if nouveau drivers work with games like minecraft and some steam games. In my setup theres 2 seats with nvidia and one intel hd graphics for www browsing. Havent had any luck with Lightdm, i have xorg conf for all 3 seats, and it has worked like the toilets in trains for ages with kdm..
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum