1 |
Neil Stone posted <43C61400.7080904@×××××××××××.com>, excerpted below, on |
2 |
Thu, 12 Jan 2006 08:32:00 +0000: |
3 |
|
4 |
> 1. All of my fonts have gone small.. whats up with that, I know I have |
5 |
> updated a few things, but (afaik) nothing that would cause this to happen |
6 |
|
7 |
The subject is xorg related questions, then mention updating some things, |
8 |
but don't mention whether xorg was among them. If so, then definitely, |
9 |
yes, that could cause your fonts to change size. Even if not, it could be |
10 |
related to xorg, or more precisely, to the lack of a specific setting in |
11 |
xorg.conf. |
12 |
|
13 |
The problem is this. xorg can't always reliably tell how physically big |
14 |
your display is, in relatiion to the pixel-resolution. Put another way, |
15 |
xorg doesn't always reliably know the correct dots (pixels) per inch |
16 |
setting. |
17 |
|
18 |
What dots per inch (dpi), therefore, how big a particular font point-size |
19 |
actually looks on-screen, can be affected by a number of things. xorg |
20 |
itself has some sort of default that from my experience often changes from |
21 |
version to version. Some desktop environments have their own setting, as |
22 |
well. In particular, gnome-settings-daemon enforces its own version of |
23 |
what it thinks is correct. Therefore, if it's substantially off from the |
24 |
X default and from anything else trying to set dots per pixel, if it's |
25 |
running, you'll get one size, while you'll get an entirely DIFFERENT size |
26 |
if it's not. From my experience, gnome-settings-daemon tends to be more |
27 |
accurate, and not change as wildly, as X by itself. This used to be a |
28 |
problem for me because I run KDE as my default desktop, but would |
29 |
occasionally run something from Gnome that would trigger |
30 |
gnome-settings-daemon, and everything started while it was running would |
31 |
have an entirely DIFFERENT font-size then everything started either before |
32 |
it, or after it was terminated. |
33 |
|
34 |
The solution I found to all this is to tell X the proper dpi setting, so |
35 |
it doesn't have to guess. Because gnome-settings-daemon seems to be |
36 |
decently accurate in any case, it then tends to agree with the X settings, |
37 |
and things quit changing on me. How many other applications potentially |
38 |
mess with that setting, or whether setting it correctly in xorg.conf |
39 |
solves it for all of them, I don't know, but it solved the problem in both |
40 |
instantiations (gsd and X version changes) for me. |
41 |
|
42 |
Let me pull up my xorg.conf and find the setting... |
43 |
|
44 |
OK, it depends on your setup. Ordinarily (single screen/monitor or with a |
45 |
separate device and screen section for each monitor), the setting is in/as: |
46 |
|
47 |
Section "Monitor" |
48 |
DisplaySize 400 300 |
49 |
|
50 |
DisplaySize is in mm, x, y, so the above entry is for a 400x300 mm screen, |
51 |
which is about a 21 or 22 inch monitor. (I'm running two, a 21" and a |
52 |
22", but on regular CRTs, a 22" monitor is rather less than an inch larger |
53 |
than a 21", in actual display area. Apparently, a 22" has more |
54 |
"unviewable" area than a 21". Anyway, since they are so close, I run the |
55 |
same 400x300 setting for both.) xorg does the math, since it knows the |
56 |
resolution you are running. As it happens, 400x300mm @ 1600x1200 |
57 |
resolution is real close to 100 dpi square. 400x300mm @ 2048x1536 is 120 |
58 |
dpi. |
59 |
|
60 |
Note that xorg ships by default with 75 and 100 dpi bitmapped fonts. Thus, |
61 |
100 dpi is a "natural" no-conversion setting for it, when using the 100 |
62 |
dpi fonts. If you prefer larger font settings, you could run that same |
63 |
400x300mm monitor at 1280x920, which is close enough to 75 dpi to use |
64 |
that. (Note that the common 1280x1024 is a 5x4 ratio, not the standard |
65 |
4x3, so that will result in rectangular pixels, slightly shorter than they |
66 |
are wide. Likewise, I have an old game that uses 640x400 resolution, |
67 |
which results in pixels slightly taller than they are wide, 640x480 would |
68 |
be standard 4x3 ratio square pixels at that resolutiion.) |
69 |
|
70 |
If you are running a Radeon dual-output in merged frame-buffer mode |
71 |
(using the free xorg drivers, not slaveryware), as I am, the setting is |
72 |
different. There's a single setting for both monitors, since it's a single |
73 |
framebuffer, so if they aren't close to the same physical size (assuming |
74 |
one is running them at the same resolution), fonts will simply be smaller |
75 |
on the smaller monitor. In this case, the setting is actually in dpi |
76 |
rather than in size, and occurs in/as: |
77 |
|
78 |
Section "Device" |
79 |
Option "MergedDPI" "100 100" |
80 |
|
81 |
That's the X and Y dots per inch setting. From the above, discussion, you |
82 |
can see that corresponds to running the same 400x300mm monitors @ |
83 |
1600x1200 resolution each. I have them stacked, for a 1600x2400 pixel |
84 |
viewport. (As mentioned above, I used to run them @ 2048x1536, for a |
85 |
2048x3072 viewport, 120 dpi, but decided the 1600x1200 each, 1600x2400 |
86 |
total, was more practical.) |
87 |
|
88 |
|
89 |
> 2. xfs - I can't suss out how to get this installed... and wouw it help |
90 |
> the above situ ? |
91 |
|
92 |
It shouldn't help the above, no, as it's the dpi setting that determines |
93 |
size, regardless of how the fonts are served. |
94 |
|
95 |
I'm running xfs here, altho I've debated turning it off and letting X |
96 |
handle its own fonts. You don't say what your problem is, but if it's |
97 |
simply a matter of not knowing what package the xfs binary is in... |
98 |
|
99 |
In monolithic xorg (pre 7.0-modular), xfs is part of the xorg package, |
100 |
with its compilation controlled by the font-server USE flag. |
101 |
|
102 |
With modular-xorg (7.0 on), xfs is a separate package, x11-apps/xfs, along |
103 |
with all the other separate packages making up modular-xorg. |
104 |
|
105 |
> 3. TwinView.... I saw a few posts of people using this, and I would like |
106 |
> to have a go... can someone point me at a document that would provide me |
107 |
> recent, revevant information on being able to use multiple monitors in |
108 |
> xorg ? |
109 |
|
110 |
TwinView is an NVidia Trademark, referring to dual monitor mode with their |
111 |
proprietary/slaveryware drivers. I used to run it, back when I first |
112 |
switched to Linux, as I had known enough to investigate whether my card |
113 |
had Linux drivers but didn't realize there /was/ such a thing as Linux |
114 |
proprietaryware/slaveryware drivers, at the time I purchased the card, and |
115 |
NVidia doesn't release enough information for the free nv driver to do |
116 |
dual video output mode. That's why I'm running an ATI Radeon 9250, now -- |
117 |
that's the closest thing to a modern card that has fully functional Free |
118 |
drivers. |
119 |
|
120 |
Anyway, if you are running NVidia hardware and NVidia's slaveryware |
121 |
drivers, their README does a pretty good job of explaining how to run dual |
122 |
monitors, and what your options are for doing so. |
123 |
|
124 |
If you are running a dual output Radeon 7000 thru 9250, you are in luck, |
125 |
as that's what I run now. The info is available in the xorg.conf and |
126 |
radeon manpages, and/or I can explain your options and the necessary |
127 |
settings, for both separate framebuffers, and merged framebuffer mode. |
128 |
(Lest there be any confusion, "framebuffer" in this case does *NOT* refer |
129 |
to the framebuffer driver in the kernel, but rather, to the memory space |
130 |
to which the pixels are actually drawn.) |
131 |
|
132 |
Other hardware often also supports either multiple cards or multiple |
133 |
outputs per card, or both, and there's individual manpages for most brands |
134 |
giving the brand dependent details. Do note, however, if you plan to run |
135 |
multiple cards, that not all cards work together. Choosing an appropriate |
136 |
dual-output card is most likely to work, altho I don't believe the free nv |
137 |
drivers support it so if it's an NVidia card, you'll have to run the |
138 |
slaveryware drivers to do that. Whether that's an issue or not for you, I |
139 |
can't say, but it'd be a show stopper, here. |
140 |
|
141 |
In any case, you'll want to enable the xinerama USE flag for support in |
142 |
various apps. Whether you actually want to run xorg's xinerama itself, or |
143 |
the xinerama emulation most merged framebuffer type solutions offer, |
144 |
depends to a large extent on what your hardware offers and personal |
145 |
preference. The Free Radeon drivers even support accelerated OpenGL on |
146 |
dual monitors, in merged framebuffer mode up to 2048x2048 combined |
147 |
resolution, and I believe NVidia's slaveryware drivers have similar 3D |
148 |
support with TwinView. |
149 |
|
150 |
-- |
151 |
Duncan - List replies preferred. No HTML msgs. |
152 |
"Every nonfree program has a lord, a master -- |
153 |
and if you use the program, he is your master." Richard Stallman in |
154 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
155 |
|
156 |
|
157 |
-- |
158 |
gentoo-amd64@g.o mailing list |