LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Desktop (https://www.linuxquestions.org/questions/linux-desktop-74/)
-   -   Can't start Xorg after upgrade to Debian Buster (https://www.linuxquestions.org/questions/linux-desktop-74/cant-start-xorg-after-upgrade-to-debian-buster-4175657475/)

Fruchtenstein 07-16-2019 06:35 AM

Can't start Xorg after upgrade to Debian Buster
 
Hi, folks,

I never was good at configuring Xorg :) I've upgraded my PC from Debian Stretch to Buster two days ago. The process was pretty straightforward, but I can't run my favorite window manager anymore. I know they have switched from Xorg to Wayland in this release, but the situation is not that simple.

My setup is: a PC with Intel chipset and i915 video. Two monitors, identified as VGA-1 and HDMI-2, both with equal resolutions 1920x1080.

I can run all kinds of Gnome from gdm3, including Gnome under Xorg.

I can run Plasma from gdm3, but I can see the desktop only on VGA-1.

Other desktop managers, like sddm and slim, fail to show login form.

I can run startx from command line when gdm is down, but I don't see anything on displays. So, if I leave .xinitrc empty, I can only see my own command line and then I get 'Server terminated successfully' in Xorg log file. So far, so good. But if I add something to .xinitrc, like 'xterm', and run startx again, I see the starting messages of Xorg and then nothing else. It seems that Xterm is running, but is not visible. If I try to switch to another virtual terminal, Xorg crashes with messages:

Quote:

[ 17344.449] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 17344.496] (II) systemd-logind: got pause for 13:64
[ 17344.496] (II) systemd-logind: got pause for 13:66
[ 17344.496] (II) systemd-logind: got pause for 13:69
[ 17344.496] (II) systemd-logind: got pause for 226:0
[ 17344.497] (II) systemd-logind: got pause for 13:70
[ 17344.497] (II) systemd-logind: got pause for 13:68
[ 17344.497] (II) systemd-logind: got pause for 13:67
[ 17344.497] (II) systemd-logind: got pause for 13:71
[ 17344.497] (II) systemd-logind: got pause for 13:65
[ 17346.258] (II) systemd-logind: got resume for 13:64
[ 17346.275] (II) systemd-logind: got resume for 13:66
[ 17346.291] (II) systemd-logind: got resume for 13:69
[ 17346.291] (II) systemd-logind: got resume for 226:0
[ 17346.291] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 17346.301] (EE) modeset(0): failed to set mode: Invalid argument
When I try to run Xorg using xinit instead of startx, it fails right now with the following message:

parse_vt_settings: Cannot open /dev/tty0 (Permission denied).

But Gnome and, partially, KDE manage to run under Xorg! There must be a way to run it. Any ideas?

evo2 07-17-2019 12:01 AM

Hi,

modern X11 like what is on Buster should work without any custom configuration. Do you have something strange in /etc/X11/xorg.conf of in /etc/X11/xorg.conf.d/*? If so, please try removing it.

It would also be useful to know more about your graphics setup. Install inxi (if you don't already have it), then run and post the output of the following:
Code:

inxi --graphics
Evo2.

Fruchtenstein 07-17-2019 02:58 AM

No, there are no config files. I did try to create a config file with 'Xorg --configure' and play with settings, but it didn't help and I deleted the file.

Code:

$ inxi --graphics

Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel
          Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
          resolution: 1920x1080~60Hz, 1920x1080~60Hz
          OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 18.3.6


evo2 07-17-2019 03:16 AM

Hi,

so that looks fine. I'm trying to understand what the problem is.

Quote:

I can run all kinds of Gnome from gdm3, including Gnome under Xorg.

I can run Plasma from gdm3, but I can see the desktop only on VGA-1.

Other desktop managers, like sddm and slim, fail to show login form.
Is the issue that only one of your displays works when using gdm3 and a secondary problem is that X crashes when you try to run it with startx?

Evo2.

P.S. Please use [code] tags when displaying text from a terminal not [quote] tags

Fruchtenstein 07-17-2019 03:35 AM

Quote:

Originally Posted by evo2 (Post 6015763)
Is the issue that only one of your displays works when using gdm3 and a secondary problem is that X crashes when you try to run it with startx?

Well, not really. When Xorg is started from gdm with window managers other than Gnome and KDE, the screen remains black.

When Xorg is started from command line, it kinda works without errors, but the image on the screen remains unchanged, just text console with Xorg startup messages. If at this moment I try to switch to another virtual console, Xorg exits with error message.

However, when Xorg is started from gdm with Gnome, it works correctly. When it is started from gdm with KDE Plasma, only one monitor of the two works.

Fruchtenstein 07-18-2019 12:36 AM

Did some more research. If I run 'startx xterm', what I see on the screen is just plain text console with some typical messages of running Xorg. However, if I log in via SSH and make a screenshot, I see a desktop with xterm.
https://imgur.com/74QFRLe

evo2 07-18-2019 12:48 AM

Hi,

I'm really at a loss as to what is going on. So gnome-shell and KDE sessions both work fine when starting with gdm, but starting just a window manager does not. I run just a window manager started from my .xsession with gdm and have no issues on two machines that I recently upgraded to Buster. Did your upgrade really complete correctly?

Evo2.

Fruchtenstein 07-18-2019 02:42 AM

Quote:

Originally Posted by evo2 (Post 6016086)
Did your upgrade really complete correctly?

I thought so, till I started to run my window manager.

evo2 07-18-2019 02:58 AM

Hi,

ok so have you tried checking your package manager? Eg
Code:

dpkg --audit
dpkg --configure --pending
apt update
apt upgrade

etc.

Evo2.

Fruchtenstein 07-18-2019 04:56 AM

No, no, as far as packages are concerned, everything is fine. There's a number of packages of non-Debian origin, but neither of them has 'xorg' in its name.

evo2 07-18-2019 07:47 PM

Hi,

well, I don't think I can provide any help since I have no experience running X without a display manager and the output from "xini --graphics" indicates that both displays are working correctly. For all I know what you are seeing is the expected behaviour in buster.

Evo2.

Fruchtenstein 07-19-2019 01:11 AM

Thanks for help, evo2! I think I did it, using https://wiki.archlinux.org/index.php/Intel_graphics. First, I created xorg.conf and enabled "intel" driver:

Code:

Section "Device"
  Identifier  "Intel Graphics"
  Driver      "intel"
EndSection

And here it is! It gave me two identical pictures on two monitors. Then I added a bit more to make them one single desktop:

Code:

Section "Monitor"
    Identifier  "VGA1"
    Option      "Primary" "true"
EndSection
Section "Monitor"
    Identifier  "HDMI2"
    Option      "LeftOf" "VGA1"
EndSection

And here is my favorite StumpWM :)

evo2 07-19-2019 01:44 AM

Hi,

I'm quite surprise you had to do that. Had you tried using xrandr? That's how I configure multiple displays if I'm not using a fancy desktop.

What is the output of "inxi --graphics" now?

Evo2.

Fruchtenstein 07-19-2019 02:02 AM

Yes, I use xrandr to rotate one of my monitors to portrait mode.

The output of "inxi --graphics" has not changed:
Code:

Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel
          Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
          resolution: 1920x1080~60Hz, 1920x1080~60Hz
          OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 18.3.6


evo2 07-19-2019 02:37 AM

Quote:

Originally Posted by Fruchtenstein (Post 6016554)
Yes, I use xrandr to rotate one of my monitors to portrait mode.

Hmm, but it wouldn't turn your second display on etc? You could only get that to work with the xorg.conf.

The output of "inxi --graphics" has not changed:
Code:

Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics driver: i915 v: kernel
          Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
          resolution: 1920x1080~60Hz, 1920x1080~60Hz
          OpenGL: renderer: Mesa DRI Intel Haswell Desktop v: 4.5 Mesa 18.3.6

[/QUOTE]
Hmm, that really makes me think you shouldn't need that xorg.conf. Just turning displays on and off, and positioning them with xrandr should be enough.

Evo2.

Fruchtenstein 07-19-2019 03:20 AM

Quote:

Originally Posted by evo2 (Post 6016561)
Hmm, but it wouldn't turn your second display on etc? You could only get that to work with the xorg.conf.

Of course. The rotation was done in .xinitrc, which I completely removed when I understood that Xorg doesn't start. The problems I described above were happening when there were no configuration files, neither xorg.conf, nor .xinitrc or anything else.

Quote:

Hmm, that really makes me think you shouldn't need that xorg.conf. Just turning displays on and off, and positioning them with xrandr should be enough.
Unfortunately, I don't know of any way to turn displays on other than to put that 'Device' section in xorg.conf. Any ideas?

evo2 07-20-2019 11:48 PM

Hi,

you can use xrandr or a gui frontend to it like arandr.

Evo2.

mrmazda 07-21-2019 03:17 AM

You might try making one or the other display explicitly primary with xrandr.

Any chance your VGA cable could be replaced with a DVI-DVI or DVI-HDMI cable? My Haswell has HDMI, DVI and VGA. Going all digital can sometimes work better, or at all.

My xrandr script is in /etc/X11/Xsession.d/. No .xinitrc, .xsession, Gnome or GDM here. I have no trouble getting my Kaby Lake to use all connected displays without any need for xorg.conf* whether I use startx or TDM:
Code:

## to stack displays instead of side by side by side
# xrandr --output DP-1 --mode 2560x1440 --primary --output HDMI-1 --mode 2560x1080 --above DP-1 --output HDMI-2 --mode 1920x1200 --above HDMI-1
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current 2560 x 3720, maximum 8192 x 8192
HDMI-2 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
HDMI-1 connected 2560x1080+0+1200 (normal left inverted right x axis y axis) 673mm x 284mm
DP-1 connected primary 2560x1440+0+2280 (normal left inverted right x axis y axis) 598mm x 336mm
  2560x1440    59.95*+  74.92
  2560x1080    60.00*+
  1920x1200    59.95*+
# inxi -GxxS
System:    Host: gb250 Kernel: 4.19.0-5-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Trinity R14.0.7 tk: Qt 3.5.0
          wm: Twin dm: startx Distro: Debian GNU/Linux 10 (buster)
Graphics:  Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912
          Display: tty server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa
          resolution: 2560x1080~60Hz, 1920x1200~60Hz, 2560x1440~60Hz
          OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.6 compat-v: 3.0
          direct render: Yes

Note HDMI-2 here is actually a DVI connection.

I would expect my Haswell to do no differently other than connector names in xrandr, but I don't have Buster on it.


All times are GMT -5. The time now is 02:53 PM.