You are not logged in.
Following the wiki, I decided to check if my DPI settings were correct, and fix them if they were not. These are the results I'm getting (full commands typed out for clarity):
First, without any configuration, the screen settings:
$ xinit /usr/bin/awesome -- :0
$ xdpyinfo | grep -B2 resolution
screen #0:
dimensions: 1920x1080 pixels (508x285 millimeters)
resolution: 96x96 dots per inchThis is wrong. Altering the commandline -dpi parameter results in the following:
xinit /usr/bin/awesome -- :0 -dpi 165
$ xdpyinfo | grep -B2 resolution
screen #0:
dimensions: 1920x1080 pixels (295x166 millimeters)
resolution: 165x165 dots per inchThis is right. For a more permanent solution one might alter xorg.conf settings, which I did:
/etc/X11/xorg.conf.d/10-dpi.conf
Section "Monitor"
Identifier "Monitor0"
DisplaySize 295 166
EndSectionHowever, it results the default 96x96 DPI, as you saw in the first code snippet. Furthermore, directly editing the DPI in xorg.conf such as this:
/etc/X11/xorg.conf.d/10-dpi.conf
Section "Monitor"
Identifier "Monitor0"
Option "DPI" "166 x 166"
EndSectionagain results in the default 96x96 DPI.
Interestingly enough, if I deliberately put some bogus values into the config, Xorg complains about it and will not start up. So the config file IS being read, and there are apparently no errors in it. As well the other .conf files in the /etc/X11/xorg.conf.d/ directory is working (such as fonts.conf, which I am using to include /usr/share/font directories).
Why is the config not applying?
Last edited by Whef (2012-09-04 07:10:13)
Offline
I think you can put it in .Xdefaults or .Xresources:
Xft.dpi: 166Offline
I looked this up also, and found that Xorg0.log gives different results then xdpyinfo :
$ xdpyinfo | grep -B2 resolution
screen #0:
dimensions: 1920x1200 pixels (508x317 millimeters)
resolution: 96x96 dots per inchXorg.0.log
[7232.286] (**) RADEON(0): Display dimensions: (520, 320) mm
[ 7232.286] (**) RADEON(0): DPI set to (93, 95)No 90-monitor.conf file present, and Xorg.0.log only has 2 other lines with dpi , both about font paths.
So the question seems to be : which is right, Xorg.0.log or xdpyinfo ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I think you can put it in .Xdefaults or .Xresources:
Xft.dpi: 166
If this does infact work, then it didn't for me.
I looked this up also, and found that Xorg0.log gives different results then xdpyinfo :
$ xdpyinfo | grep -B2 resolution screen #0: dimensions: 1920x1200 pixels (508x317 millimeters) resolution: 96x96 dots per inchXorg.0.log
[7232.286] (**) RADEON(0): Display dimensions: (520, 320) mm [ 7232.286] (**) RADEON(0): DPI set to (93, 95)No 90-monitor.conf file present, and Xorg.0.log only has 2 other lines with dpi , both about font paths.
So the question seems to be : which is right, Xorg.0.log or xdpyinfo ?
Interesting... The xdpyinfo one is correct (I can tell because of text sizes). However, when starting X without the -dpi argument it shows this:
[ 2194.180] (**) intel(0): DPI set to (174,171)Not only is this the wrong DPI for my monitor, but it isn't the actual DPI that X is using. xdpyinfo correctly displays that the DPI is 96x96. However, if I launch X with the -dpi argument then Xorg.0.log will report the correct DPI (what I set it to). I really have no idea what's going on. I just wish my DPI settings would save!
Last edited by Whef (2012-09-05 08:47:33)
Offline