[opensuse-factory] Launching multiple X sessions with proprietary NVIDIA?
With my old ATI Radeon graphics card and the Open Source driver radeon I was able to run multiple X sessions with one graphics card and one display, e.g. KDE Plasma on tty7 and GNOME on tty8. I tried the same with my NVidia card and the proprietary driver. The second X session (started from KDE Plasma 5 menu; display manager is SDDM) fails. /var/log/Xorg.1.log says: [ 29452.803] (II) xfree86: Adding drm device (/dev/dri/card0) [ 29452.803] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [...] It isn't only a permissions problem. Also when I change the permissions on /dev/dri/card0 manually to crw-rw-rw-+ the second session does not start, but replaces the first session. I also tried this trick without success (/etc/X11/xorg.conf.d/50-device.conf is correct for openSUSE Tumbleweed): Launching multiple X sessions with proprietary NVIDIA on Xorg 1.16 https://wiki.archlinux.org/index.php/xorg#Launching_multiple_X_sessions_with... Any tips? Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Bjoern Voigt
With my old ATI Radeon graphics card and the Open Source driver radeon I was able to run multiple X sessions with one graphics card and one display, e.g. KDE Plasma on tty7 and GNOME on tty8.
I tried the same with my NVidia card and the proprietary driver. The second X session (started from KDE Plasma 5 menu; display manager is SDDM) fails. /var/log/Xorg.1.log says:
[ 29452.803] (II) xfree86: Adding drm device (/dev/dri/card0) [ 29452.803] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [...]
It isn't only a permissions problem. Also when I change the permissions on /dev/dri/card0 manually to crw-rw-rw-+ the second session does not start, but replaces the first session.
I also tried this trick without success (/etc/X11/xorg.conf.d/50-device.conf is correct for openSUSE Tumbleweed):
Launching multiple X sessions with proprietary NVIDIA on Xorg 1.16 https://wiki.archlinux.org/index.php/xorg#Launching_multiple_X_sessions_with...
Any tips?
Not sure what is going on. I am able to run as many as 3 x-sessions, never tried 4. "start x /usr/bin/icewm -- :0" and changd ":0" to ":1" and .. each sessions starts and is usable. I sometime have sessions running for my wife to use when I step away :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan wrote:
Not sure what is going on. I am able to run as many as 3 x-sessions, never tried 4. "start x /usr/bin/icewm -- :0" and changd ":0" to ":1" and .. each sessions starts and is usable. I sometime have sessions running for my wife to use when I step away :) Thanks. I tried something similar too. "WINDOWMANGER=fvwm startx -- :1" works as user "root" and with Set-UID-Root for /usr/bin/Xorg in /etc/permissions.local also as normal user. It even works, if the normal (DISPLAY=:0) session is controlled by SDDM.
But the "new session" functionality of SDDM (also tried with KDM) does not work. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2016-04-05 at 23:54 +0200, Bjoern Voigt wrote:
Patrick Shanahan wrote:
Not sure what is going on. I am able to run as many as 3 x-sessions, never tried 4. "start x /usr/bin/icewm -- :0" and changd ":0" to ":1" and .. each sessions starts and is usable. I sometime have sessions running for my wife to use when I step away :) Thanks. I tried something similar too. "WINDOWMANGER=fvwm startx -- :1" works as user "root" and with Set-UID-Root for /usr/bin/Xorg in /etc/permissions.local also as normal user. It even works, if the normal (DISPLAY=:0) session is controlled by SDDM.
But the "new session" functionality of SDDM (also tried with KDM) does not work.
My guess is that the display manager changes the permissions of some devices to be owned by the second "seat". Check sound, might have a similar problem. startx doesn't do those clever tricks, so it still works. I tried "switch user" on my 13.1 install (xfce and lightdm), and it works just fine. Proprietary nvidia driver, but I don't think that is involved. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlcI4pUACgkQtTMYHG2NR9VuUwCfRNcQM1Nypi4TvIxHNEsB6NbO QpgAn3jDDNEDtwEpA88duJC/e2saqVYa =GbDD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bjoern Voigt composed on 2016-04-05 22:36 (UTC+0200):
With my old ATI Radeon graphics card and the Open Source driver radeon I was able to run multiple X sessions with one graphics card and one display, e.g. KDE Plasma on tty7 and GNOME on tty8.
I tried the same with my NVidia card and the proprietary driver. The second X session (started from KDE Plasma 5 menu; display manager is SDDM) fails. /var/log/Xorg.1.log says:
[ 29452.803] (II) xfree86: Adding drm device (/dev/dri/card0) [ 29452.803] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [...]
It isn't only a permissions problem. Also when I change the permissions on /dev/dri/card0 manually to crw-rw-rw-+ the second session does not start, but replaces the first session.
I also tried this trick without success (/etc/X11/xorg.conf.d/50-device.conf is correct for openSUSE Tumbleweed):
50-device.conf as it comes from its rpm is nothing but comments, a dummy file except for a bit of instruction.
Launching multiple X sessions with proprietary NVIDIA on Xorg 1.16 https://wiki.archlinux.org/index.php/xorg#Launching_multiple_X_sessions_with...
Any tips?
Why proprietary rather than FOSS driver? I have GeForce 8400GS (GT218) running TW 20160406, without using startup xrandr or any non-default configuration in xorg.conf*, with Plasma sessions on tty3 (simply startx) and tty4 (startx -- :1) and IceWM (startx /usr/bin/icewm) on tty5, all same user login. Other than not finding them on tty7 & up where they used to be, they seem to work same as always, as with Intel or ATI gfxchips. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Felix Miata wrote:
Why proprietary rather than FOSS driver? I have GeForce 8400GS (GT218) running TW 20160406, without using startup xrandr or any non-default configuration in xorg.conf*, with Plasma sessions on tty3 (simply startx) and tty4 (startx -- :1) and IceWM (startx /usr/bin/icewm) on tty5, all same user login. Other than not finding them on tty7 & up where they used to be, they seem to work same as always, as with Intel or ATI gfxchips. I have a Maxwell based graphics card (Geforce GTX 750). nouveau (Tumbleweed version) does not run with this card. I already tried this.
Kernel 4.6 will provide support for the Maxwell graphic cards. I am not sure, if a Mesa and/or xf86-video-nouveau update will be necessary too. Since the proprietary driver can run multiple sessions with "startx", I doubt, that not the driver itself causes the problem. Maybe something with systemd, KDM/SDDM ...? Is there anyone who runs multiple sessions with KDE Plasma5 and KDM or SDDM and the NVidia driver successfully? Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Bjoern Voigt
Felix Miata wrote:
Why proprietary rather than FOSS driver? I have GeForce 8400GS (GT218) running TW 20160406, without using startup xrandr or any non-default configuration in xorg.conf*, with Plasma sessions on tty3 (simply startx) and tty4 (startx -- :1) and IceWM (startx /usr/bin/icewm) on tty5, all same user login. Other than not finding them on tty7 & up where they used to be, they seem to work same as always, as with Intel or ATI gfxchips. I have a Maxwell based graphics card (Geforce GTX 750). nouveau (Tumbleweed version) does not run with this card. I already tried this.
Kernel 4.6 will provide support for the Maxwell graphic cards. I am not sure, if a Mesa and/or xf86-video-nouveau update will be necessary too.
Since the proprietary driver can run multiple sessions with "startx", I doubt, that not the driver itself causes the problem. Maybe something with systemd, KDM/SDDM ...?
Is there anyone who runs multiple sessions with KDE Plasma5 and KDM or SDDM and the NVidia driver successfully?
yes, I have three atm, twm, icewm-lite and plasma5. I started plasma5 with "systemctl isolate graphical" and the other with "starx /bin/... -- :#" from a <user> xterm but starting from a tty works as well. (only becasue I wanted to) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan wrote:
yes, I have three atm, twm, icewm-lite and plasma5. I started plasma5 with "systemctl isolate graphical" and the other with "starx /bin/... -- :#" from a <user> xterm but starting from a tty works as well. What does "systemctl isolate graphical" do exactly?
Don't you use a display manager? I had to start "startx ..." from a text console because of permissions problems otherwise. I wonder why it works in an xterm on your side. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Bjoern Voigt
Patrick Shanahan wrote:
yes, I have three atm, twm, icewm-lite and plasma5. I started plasma5 with "systemctl isolate graphical" and the other with "starx /bin/... -- :#" from a <user> xterm but starting from a tty works as well. What does "systemctl isolate graphical" do exactly?
changes from runlevel x to runlevel 5, ie: graphical.target
Don't you use a display manager?
yes, was kdm, now sddm (early on I had many probs with sddn and switched back to xdm, but recently I opted to try sddm again and haven't had any *noticable* problems, yet)
I had to start "startx ..." from a text console because of permissions problems otherwise. I wonder why it works in an xterm on your side.
permissions ???, I don't have a problem as long as Xorg is set suid, but that is necessary to used starx from a tty. GeForce GTS 450/PCIe/SSE@ 4.5.0 NVIDIA 364.12 (364.15 is out since Apr 6, next runlevel change) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan wrote:
Don't you use a display manager? yes, was kdm, now sddm (early on I had many probs with sddn and switched back to xdm, but recently I opted to try sddm again and haven't had any *noticable* problems, yet) You will probably get a problem with SDDM if your password expires soon (e.g. 7 days before): https://bugzilla.opensuse.org/show_bug.cgi?id=969813
I also tried both and I currently run SDDM. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Bjoern Voigt
Patrick Shanahan wrote:
Don't you use a display manager? yes, was kdm, now sddm (early on I had many probs with sddn and switched back to xdm, but recently I opted to try sddm again and haven't had any *noticable* problems, yet) You will probably get a problem with SDDM if your password expires soon (e.g. 7 days before): https://bugzilla.opensuse.org/show_bug.cgi?id=969813
I have a laptop with tw which has used sddm for ~3 months now and haven't see this, but my max_days is set to 99999 (default) by which time the machine and me will *probably* have expired :) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Bjoern Voigt composed on 2016-04-08 13:36 (UTC+0200):
Felix Miata wrote:
Why proprietary rather than FOSS driver? I have GeForce 8400GS (GT218) running TW 20160406, without using startup xrandr or any non-default configuration in xorg.conf*, with Plasma sessions on tty3 (simply startx) and tty4 (startx -- :1) and IceWM (startx /usr/bin/icewm) on tty5, all same user login. Other than not finding them on tty7 & up where they used to be, they seem to work same as always, as with Intel or ATI gfxchips.
I have a Maxwell based graphics card (Geforce GTX 750). nouveau (Tumbleweed version) does not run with this card. I already tried this.
Kernel 4.6 will provide support for the Maxwell graphic cards. I am not sure, if a Mesa and/or xf86-video-nouveau update will be necessary too.
I was a little too quick in clicking send, omitting to ask if you tried running with neither nouveau nor nvidia drivers installed. I just found out 3 days ago[1] that the modeset driver built into Xorg works better than gfxchip-specific drivers for many, but forgot until after responding to you yesterday to try for myself. Could modeset be already working for Maxwell? [1] https://www.reddit.com/r/archlinux/comments/4cojj9/it_is_probably_time_to_di... -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Felix Miata wrote:
Bjoern Voigt composed on 2016-04-08 13:36 (UTC+0200):
Felix Miata wrote:
Why proprietary rather than FOSS driver? I have GeForce 8400GS (GT218) running TW 20160406, without using startup xrandr or any non-default configuration in xorg.conf*, with Plasma sessions on tty3 (simply startx) and tty4 (startx -- :1) and IceWM (startx /usr/bin/icewm) on tty5, all same user login. Other than not finding them on tty7 & up where they used to be, they seem to work same as always, as with Intel or ATI gfxchips.
I have a Maxwell based graphics card (Geforce GTX 750). nouveau (Tumbleweed version) does not run with this card. I already tried this.
Kernel 4.6 will provide support for the Maxwell graphic cards. I am not sure, if a Mesa and/or xf86-video-nouveau update will be necessary too.
I was a little too quick in clicking send, omitting to ask if you tried running with neither nouveau nor nvidia drivers installed. I just found out 3 days ago[1] that the modeset driver built into Xorg works better than gfxchip-specific drivers for many, but forgot until after responding to you yesterday to try for myself. Could modeset be already working for Maxwell?
[1] https://www.reddit.com/r/archlinux/comments/4cojj9/it_is_probably_time_to_di... Good question. For my tests with nouveau I uninstalled the NVidia driver with "nvidia-uninstall". Unfortunately the uninstall-function is not complete. I had to remove the "blacklist nouveau" config file from /etc/modprobe.d and I had to remove the "nomodeset" setting from Grub.
To be sure, I also re-installed all Mesa libraries, build new initrd-files and I rebooted several times. Anyway, if I configured the "nouveau" driver I got the"Unknown chipset: NV117" errors in /var/log/Xorg.0.log: [ 105.407] (II) LoadModule: "nouveau" [ 105.408] (II) Loading /usr/lib64/xorg/modules/drivers/nouveau_drv.so [ 105.410] (II) Module nouveau: vendor="X.Org Foundation" [ 105.410] compiled for 1.18.0, module version = 1.0.12 [ 105.410] Module class: X.Org Video Driver [ 105.410] ABI class: X.Org Video Driver, version 20.0 [ 105.410] (II) LoadModule: "nv" [ 105.410] (II) Loading /usr/lib64/xorg/modules/drivers/nv_drv.so [ 105.411] (II) Module nv: vendor="X.Org Foundation" [ 105.411] compiled for 1.18.0, module version = 2.1.20 [ 105.411] Module class: X.Org Video Driver [ 105.411] ABI class: X.Org Video Driver, version 20.0 [ 105.411] (II) LoadModule: "modesetting" [ 105.411] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 105.412] (II) Module modesetting: vendor="X.Org Foundation" [ 105.412] compiled for 1.18.2, module version = 1.18.2 [ 105.412] Module class: X.Org Video Driver [ 105.412] ABI class: X.Org Video Driver, version 20.0 [ 105.412] (II) LoadModule: "fbdev" [ 105.412] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 105.413] (II) Module fbdev: vendor="X.Org Foundation" [ 105.413] compiled for 1.18.0, module version = 0.4.4 [ 105.413] Module class: X.Org Video Driver [ 105.413] ABI class: X.Org Video Driver, version 20.0 [ 105.413] (II) LoadModule: "vesa" [ 105.413] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 105.413] (II) Module vesa: vendor="X.Org Foundation" [ 105.413] compiled for 1.18.0, module version = 2.3.4 [ 105.413] Module class: X.Org Video Driver [ 105.413] ABI class: X.Org Video Driver, version 20.0 [ 105.413] (II) NOUVEAU driver [ 105.413] (II) NOUVEAU driver for NVIDIA chipset families : [ 105.413] RIVA TNT (NV04) [ 105.413] RIVA TNT2 (NV05) [ 105.413] GeForce 256 (NV10) [ 105.414] GeForce 2 (NV11, NV15) [ 105.414] GeForce 4MX (NV17, NV18) [ 105.414] GeForce 3 (NV20) [ 105.414] GeForce 4Ti (NV25, NV28) [ 105.414] GeForce FX (NV3x) [ 105.414] GeForce 6 (NV4x) [ 105.414] GeForce 7 (G7x) [ 105.414] GeForce 8 (G8x) [ 105.414] GeForce GTX 200 (NVA0) [ 105.414] GeForce GTX 400 (NVC0) [ 105.414] (II) NOUVEAU driver [ 105.414] (II) NOUVEAU driver for NVIDIA chipset families : [ 105.414] RIVA TNT (NV04) [ 105.414] RIVA TNT2 (NV05) [ 105.414] GeForce 256 (NV10) [ 105.414] GeForce 2 (NV11, NV15) [ 105.414] GeForce 4MX (NV17, NV18) [ 105.414] GeForce 3 (NV20) [ 105.414] GeForce 4Ti (NV25, NV28) [ 105.414] GeForce FX (NV3x) [ 105.414] GeForce 6 (NV4x) [ 105.414] GeForce 7 (G7x) [ 105.414] GeForce 8 (G8x) [ 105.414] GeForce GTX 200 (NVA0) [ 105.414] GeForce GTX 400 (NVC0) [ 105.414] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 105.414] (II) FBDEV: driver for framebuffer: fbdev [ 105.414] (II) VESA: driver for VESA chipsets: vesa [ 105.415] (II) [drm] nouveau interface version: 1.3.1 [ 105.415] (EE) Unknown chipset: NV117 [ 105.415] (II) [drm] nouveau interface version: 1.3.1 [ 105.415] (EE) Unknown chipset: NV117 [ 105.415] (II) [drm] nouveau interface version: 1.3.1 [ 105.415] (EE) Unknown chipset: NV117 [ 105.415] (II) [drm] nouveau interface version: 1.3.1 [ 105.415] (EE) Unknown chipset: NV117 [ 105.416] (II) [drm] nouveau interface version: 1.3.1 [ 105.416] (EE) Unknown chipset: NV117 [ 105.416] (II) [drm] nouveau interface version: 1.3.1 [ 105.416] (EE) Unknown chipset: NV117 [ 105.416] (II) [drm] nouveau interface version: 1.3.1 [ 105.416] (EE) Unknown chipset: NV117 [ 105.416] (II) [drm] nouveau interface version: 1.3.1 [ 105.416] (EE) Unknown chipset: NV117 [ 105.416] (II) [drm] nouveau interface version: 1.3.1 [ 105.416] (EE) Unknown chipset: NV117 [ 105.416] (II) [drm] nouveau interface version: 1.3.1 [ 105.416] (EE) Unknown chipset: NV117 [ 105.416] (II) modeset(0): using drv /dev/dri/card0 [ 105.416] (WW) Falling back to old probe method for fbdev [ 105.416] (II) Loading sub module "fbdevhw" [ 105.416] (II) LoadModule: "fbdevhw" [ 105.416] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so [ 105.417] (II) Module fbdevhw: vendor="X.Org Foundation" [ 105.417] compiled for 1.18.2, module version = 0.0.2 [ 105.417] ABI class: X.Org Video Driver, version 20.0 [ 105.417] (WW) Falling back to old probe method for vesa [ 105.421] (==) modeset(0): Depth 24, (==) framebuffer bpp 32 [ 105.421] (==) modeset(0): RGB weight 888 [ 105.421] (==) modeset(0): Default visual is TrueColor [ 105.421] (II) Loading sub module "glamoregl" [ 105.421] (II) LoadModule: "glamoregl" [ 105.421] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so [ 105.431] (II) Module glamoregl: vendor="X.Org Foundation" [ 105.431] compiled for 1.16.2, module version = 1.0.0 [ 105.431] ABI class: X.Org ANSI C Emulation, version 0.4 [ 105.431] (II) glamor: OpenGL accelerated X.org driver based. [ 105.647] (II) glamor: EGL version 1.4 (DRI2): The resolution of the framebuffer driver was too bad. If I find time, I will try Kernel 4.6-rcX. This kernel should have support for my graphics card and has the necessary signed NVidia firmware binaries. Anyway, I would prefer a solution the NVidia proprietary driver. I do not use multiple X session so often, but I use other NVidia functions like VDPAU very often. Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Bjoern Voigt -
Carlos E. R. -
Felix Miata -
Patrick Shanahan