[arch-general] Cannot use monitor in 1920x1080 anymore
Hello fellow Arch users, Suddenly I cannot use my external monitor in the 1920x1080 mode, I add the following script that run every time I connect my thinkpad to the base: ``` #!/bin/bash set -x xrandr --output DP2-3 --mode 1920x1080 --right-of eDP1 xset m 1/2 1 ``` And after a update (I think) i can't use this resolution anymore. But when connecting the monitor to the laptop I still have that resolution ``` $ xrandr # Connected to the base Screen 0: minimum 8 x 8, current 2646 x 1024, maximum 32767 x 32767 eDP1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 277mm x 156mm 1366x768 60.00*+ 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP2-1 disconnected (normal left inverted right x axis y axis) DP2-2 disconnected (normal left inverted right x axis y axis) DP2-3 connected (normal left inverted right x axis y axis) 1024x768 60.00 + 75.08 1280x1024 75.02 60.02 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08 HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) ``` ``` $ xrandr # Connected to the laptop VGA Screen 0: minimum 8 x 8, current 2646 x 1024, maximum 32767 x 32767 eDP1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 277mm x 156mm 1366x768 60.00*+ 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP2 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 1680x1050 59.95 1280x1024 75.02 60.02 1152x864 75.00 1024x768 75.08 60.00 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08 DP2-1 disconnected (normal left inverted right x axis y axis) DP2-2 disconnected (normal left inverted right x axis y axis) DP2-3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) ``` Any ideas how can I debug this problem further ? -- Regards, Alfredo Palhares
Do you get an error message or the like?
On 2015-03-30 13:08:11, Alfredo Palhares wrote:
Any ideas how can I debug this problem further ?
Have a look at X's logfile, /var/log/Xorg.log. There should be messages that say the modes are being removed, and why (not enough Vram, some parameter out of range, etc.). It's likely warning or errors, so it should be among the output of egrep '\([WE]{2}\)' Xorg.0.log. Good luck, -Martin
On 30/03/15 06:24, Martin S. Weber wrote:
On 2015-03-30 13:08:11, Alfredo Palhares wrote:
Any ideas how can I debug this problem further ? Have a look at X's logfile, /var/log/Xorg.log. There should be messages that say the modes are being removed, and why (not enough Vram, some parameter out of range, etc.). It's likely warning or errors, so it should be among the output of egrep '\([WE]{2}\)' Xorg.0.log.
Good luck, -Martin
Hmmm... Martin, if you still have a Xorg.log it means you have a really old installation, or you installed syslog-ng and integrated it with journalctl, something that is not standard anymore. Heck, OpenSUSE just removed it of Tumbleweed, it's a sign of the times. Alfredo, as Arch uses systemd/journalctl, you need to use the command: journalctl -b0 _EXE=/usr/lib/xorg-server/Xorg If you are not in the systemd-journal group, you may need to run the command in a root shell or with sudo. -- Pedro A. López-Valencia http://about.me/palopezv
On Sat, 04 Apr 2015 11:29:26 -0500 "Pedro A. López-Valencia" <vorbote@gmail.com> wrote:
Hmmm... Martin, if you still have a Xorg.log it means you have a really old installation, or you installed syslog-ng and integrated it with journalctl, something that is not standard anymore. Heck, OpenSUSE just removed it of Tumbleweed, it's a sign of the times.
That would only be true if systemd launched Xorg directly. Xorg writes its log file on its own, not through syslog and not to the journal; I can tell you that on my fully up-to-date system, at least, Xorg writes to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for non-root Xorg). -- Patrick Burroughs (Celti) <celti@celti.name>
On 04/04/15 14:59, Patrick Burroughs (Celti) wrote:
On Sat, 04 Apr 2015 11:29:26 -0500 "Pedro A. López-Valencia" <vorbote@gmail.com> wrote:
Hmmm... Martin, if you still have a Xorg.log it means you have a really old installation, or you installed syslog-ng and integrated it with journalctl, something that is not standard anymore. Heck, OpenSUSE just removed it of Tumbleweed, it's a sign of the times. That would only be true if systemd launched Xorg directly. Xorg writes its log file on its own, not through syslog and not to the journal; I can tell you that on my fully up-to-date system, at least, Xorg writes to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for non-root Xorg).
You mean the contents of the xorg-server.install file? post_upgrade() { if (( $(vercmp $2 1.16.0-3) < 0 )); then post_install fi } post_install() { cat <<MSG >>> xorg-server has now the ability to run without root rights with the help of systemd-logind. xserver will fail to run if not launched from the same virtual terminal as was used to log in. Without root rights, log files will be in ~/.local/share/xorg/ directory. Old behavior can be restored through Xorg.wrap config file. See Xorg.wrap man page (man xorg.wrap). MSG } xorg-server.install (END) That was true for versions under 1.16.0-3 as evidenced by the version comparison, but it is not true anymore, Xserver 1.17 dumps its logs to syslog. And syslog is trapped by journalctl. -- Pedro A. López-Valencia http://about.me/palopezv
On Sun, 05 Apr 2015 12:10:13 -0500 "Pedro A. López-Valencia" <vorbote@gmail.com> wrote:
On 04/04/15 14:59, Patrick Burroughs (Celti) wrote:
On Sat, 04 Apr 2015 11:29:26 -0500 "Pedro A. López-Valencia" <vorbote@gmail.com> wrote:
Hmmm... Martin, if you still have a Xorg.log it means you have a really old installation, or you installed syslog-ng and integrated it with journalctl, something that is not standard anymore. Heck, OpenSUSE just removed it of Tumbleweed, it's a sign of the times. That would only be true if systemd launched Xorg directly. Xorg writes its log file on its own, not through syslog and not to the journal; I can tell you that on my fully up-to-date system, at least, Xorg writes to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for non-root Xorg).
You mean the contents of the xorg-server.install file?
post_upgrade() { if (( $(vercmp $2 1.16.0-3) < 0 )); then post_install fi }
post_install() { cat <<MSG >>> xorg-server has now the ability to run without root rights with the help of systemd-logind. xserver will fail to run if not launched from the same virtual terminal as was used to log in. Without root rights, log files will be in ~/.local/share/xorg/ directory.
Old behavior can be restored through Xorg.wrap config file. See Xorg.wrap man page (man xorg.wrap). MSG }
xorg-server.install (END)
That was true for versions under 1.16.0-3 as evidenced by the version comparison, but it is not true anymore, Xserver 1.17 dumps its logs to syslog. And syslog is trapped by journalctl.
Errrrrrrrrrrrrrrrrr No it does not this system is fully up to date . I use startx to start the graphical display nothing in journalctl it is in /var/log/Xorg.0.log .... Sorry to disapoint and all that .. Pete . -- Illegitimi non carborundum . ro for the purists out there Noli nothis permittere te terere.
Hmmm... Martin, if you still have a Xorg.log it means you have a really old installation,
That was true for versions under 1.16.0-3 as evidenced by the version comparison, but it is not true anymore, Xserver 1.17 dumps its logs to syslog. And syslog is trapped by journalctl.
Errrrrrrrrrrrrrrrrr No it does not this system is fully up to date .
I use startx to start the graphical display nothing in journalctl it is in /var/log/Xorg.0.log ....
Sorry to disapoint and all that ..
From what I've read, it's *only* GDM that "hacks" the X server to run so that it redirects the logs to the journal. Otherwise, it'll go to the /var/log/Xorg.0.log file as ever.
ps. on my two - always up-to-date - Arch installations, using lightdm and sddm X logs to /var/log/Xorg.0.log -- damjan
On 04/04/15 14:59, Patrick Burroughs (Celti) wrote:
That would only be true if systemd launched Xorg directly. Xorg writes its log file on its own, not through syslog and not to the journal; I can tell you that on my fully up-to-date system, at least, Xorg writes to /var/log/Xorg.X.log (or to ~/.local/share/xorg/Xorg.X.log for non-root Xorg).
I did some testing, and found we both are right, although what I said isn't. If you launch the xserver manually or with a display manager that is not well integrated with systemd, you'll get your text logs. If it is well integrated, namely GDM, everything will go into journalctl. -- Pedro A. López-Valencia http://about.me/palopezv
On 2015-04-04 11:29:26, "Pedro A. López-Valencia" wrote:
On 30/03/15 06:24, Martin S. Weber wrote:
On 2015-03-30 13:08:11, Alfredo Palhares wrote:
Any ideas how can I debug this problem further ? Have a look at X's logfile, /var/log/Xorg.log. There should be messages that say the modes are being removed, and why (not enough Vram, some parameter out of range, etc.). It's likely warning or errors, so it should be among the output of egrep '\([WE]{2}\)' Xorg.0.log.
Good luck, -Martin
Hmmm... Martin, if you still have a Xorg.log it means you have a really old installation, or you installed syslog-ng and integrated it with journalctl, something that is not standard anymore. Heck, OpenSUSE just removed it of Tumbleweed, it's a sign of the times.
Alfredo, as Arch uses systemd/journalctl, you need to use the command:
journalctl -b0 _EXE=/usr/lib/xorg-server/Xorg
As evidenced by your reply, if you can see the file, it's so much easier to look at and massage with base system utilities, thanks for the showcase; if it's not there, one might wish it was. Anyways, Alfredo, right, as Arch says you cannot configure your system, you NEED, you absolutely MUST use journalctl to access your logs. Happy Easter, -Martin
Hello everyone, Thanks for your answers. I came on the office earlier today just to test this out and: $ xrandr Screen 0: minimum 8 x 8, current 3286 x 1080, maximum 32767 x 32767 eDP1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 277mm x 156mm 1366x768 60.00*+ 1024x768 60.00 800x600 60.32 56.25 640x480 59.94 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP2-1 disconnected (normal left inverted right x axis y axis) DP2-2 disconnected (normal left inverted right x axis y axis) DP2-3 connected 1920x1080+1366+0 (normal left inverted right x axis y axis) 477mm x 268mm 1920x1080 60.00*+ 1680x1050 59.95 1280x1024 75.02 60.02 1152x864 75.00 1024x768 75.08 60.00 800x600 75.00 60.32 640x480 75.00 60.00 720x400 70.08 HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) The problem appears to have sorted itself out over the course of a week. I did not upgraded my system, I avoided it at all costs. I did not like that the problem sorted itself out. I will test it, if the problem reappears, I will get X.org logs. (Being wherever they are). Regards, -- Alfredo Palhares GPG/PGP Key Fingerprint 68FC B06A 6C22 8B9B F110 38D6 E8F7 4D1F 0763 CAAD
participants (7)
-
"Pedro A. López-Valencia"
-
Alfredo Palhares
-
Damjan Georgievski
-
Martin S. Weber
-
Martti Kühne
-
Patrick Burroughs
-
pete nikolic