goglgator.blogg.se - Startx only runs as root

#Startx only runs as root install
#Startx only runs as root driver

And to be as"light' and fast as possible.

#Startx only runs as root install

I don't want to install a display manager as I want the system to boot to a standard terminal and not X as many times I only need a terminal. I've tested Stretch in VirtualBox under numerous configurations - systemd init, sysv and runit inits with and without systemd components - installed the same way as I did Antix and never experienced any startx problems. My thinking now is this startx failure is an Antix 17 Beta glitch and not an upstream Debian Stretch or xorg problem. Although, I don't think the bug report applies (and it's a year old), but I'll read it more thoroughly later. Thanks for your quick response, advice and the bug link. You can probably explore this further but it might be faster/easier to install slim or lightdm or some other display manager that you can start as an init.d service. I think the problem is upstream with Debian and/or X.org and/or. replace the contents of the previously created 20-intel.Code: Select all sudo chmod u+x /usr/bin/Xorgīut that didn't change anything. another configuration you can use is for the modesetting driver. Reboot and see if it's working, if not, name sure optimus-manager didnt overwrite the file with it's own contents. Option "DRI" "3" # DRI2 and DRI1 are alternatives if DRI3 performs performs poorly You can try falling back to DRI2 if you run

#Startx only runs as root driver

# This driver now uses DRI3 as the default Direct Rendering # xorg configuration for use with intel driver.

create a configuration for intel with the following contents.

conf file name or it will be read and used as a configuration.

go to /etc/X11// and backup and remove the currently used video configuration (just dont leave it in the directory with.

set intel mode with optimus-manager but dont logout or reboot yet.

either way, you can try both kernel options and if it makes no difference, you can try this: can you see if still happens on other kernels, 4.19 4.20 ? the other possibility might just come down to optimus manager. Some people are having issues with the 5.0 kernel and the intel driver. With root, I can start bumblebee service, load the nvidia driver and run optirun with success. Video-hybrid-intel-nvidia-bumblebee 2018.08.09 false PCI OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.4 Graphics: Device-1: Intel HD Graphics 630 driver: i915 v: kernelĭevice-2: NVIDIA GP107M driver: N/Aĭisplay: server: X.Org 1.20.4 driver: intel resolution: 1920x1080~60Hz Subsystem: Tongfang Hongkong Limited HD Graphics 630 # lspci -kĠ0:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)

The xserver cfg file loads the "intel" driver. Lspci shows my integrated graphics is using i915 driver, but inxi -G says that's the intel driver. (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)

(EE) systemd-logind: failed to get session: PID 1353 does not belong to any known session When I try to start X server with my normal user I get this error.

The only way I could manage to start X server was running startx with root, booting on single user mode. I have a NVIDIA Optimus setup, with an GTX 1050 Ti card and an Intel 630 integrated.Īt the momment, the boot freezes in a black screen. I've recently done a manjaro-architect 18 installation.