Gentoo Archives: gentoo-user

From: Paul Hartman <paul.hartman+gentoo@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Error message in Xorg.log for intel xorg driver
Date: Fri, 16 Jan 2009 08:59:38
Message-Id: 58965d8a0901160059y349b4f34mffd78e11af9489b7@mail.gmail.com
In Reply to: Re: [gentoo-user] Error message in Xorg.log for intel xorg driver by Dale
1 On Fri, Jan 16, 2009 at 2:20 AM, Dale <rdalek1967@×××××.com> wrote:
2 > Paul Hartman wrote:
3 >> On Fri, Jan 16, 2009 at 1:58 AM, Paul Hartman
4 >> <paul.hartman+gentoo@×××××.com> wrote:
5 >>
6 >>> On Fri, Jan 16, 2009 at 1:36 AM, Dale <rdalek1967@×××××.com> wrote:
7 >>>
8 >>>> Paul Hartman wrote:
9 >>>>
10 >>>>> On Fri, Jan 16, 2009 at 12:59 AM, Dale <rdalek1967@×××××.com> wrote:
11 >>>>>
12 >>>>>
13 >>>>>> Wolfgang Liebich wrote:
14 >>>>>>
15 >>>>>>
16 >>>>>>> On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote:
17 >>>>>>>
18 >>>>>>>
19 >>>>>>>
20 >>>>>>>> On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich
21 >>>>>>>> <Wolfgang.Liebich@×××××××.com> wrote:
22 >>>>>>>>
23 >>>>>>>>
24 >>>>>>>>
25 >>>>>>>>> Furthermore yesterday I had a total lockup when I came to work at the
26 >>>>>>>>> morning --- could not login at kdm, kdm would ignore all keyboard
27 >>>>>>>>> input etc. I had to do a hard restart with the "Magic SysRQ" key
28 >>>>>>>>> (remount ro, hard reboot).
29 >>>>>>>>>
30 >>>>>>>>>
31 >>>>>>>>>
32 >>>>>>>> Do you have evdev installed? Without it, you probably won't have any
33 >>>>>>>> keyboard or mouse. Recent xorg made dramatic changes to the way
34 >>>>>>>> hardware is detected/configured by using HAL and evdev. xorg.conf is
35 >>>>>>>> basically unused now when it comes to configuring hardware. I don't
36 >>>>>>>> even have keyboard or mouse, or video modelines or anything like that
37 >>>>>>>> in mine. Search the list archives or the gentoo web forums, there are
38 >>>>>>>> many many people who had the same issues (assuming it's the cause of
39 >>>>>>>> yours).
40 >>>>>>>>
41 >>>>>>>>
42 >>>>>>>>
43 >>>>>>> Evdev is installed, but I configured the kbd driver (I have a MS
44 >>>>>>> Natural Keyboard, btw --- what's the best driver for that keyboard?).
45 >>>>>>> I still have an xorg.conf (and I'm not very inclined to change it as
46 >>>>>>> long as it works :-).
47 >>>>>>>
48 >>>>>>> Furthermore -- after the reboot everything worked again as before. It
49 >>>>>>> seems to have been some fluke, but I want to know where it comes from.
50 >>>>>>>
51 >>>>>>> TIA,
52 >>>>>>> Wolfgang
53 >>>>>>>
54 >>>>>>>
55 >>>>>>>
56 >>>>>>>
57 >>>>>> Someone else like me. I still have my xorg.conf and want to keep it
58 >>>>>> too. I don't have evdev installed but from the way it sounds, me and
59 >>>>>> you may have to change in the future, maybe near future.
60 >>>>>>
61 >>>>>> I'm sort of wondering what pulls in evdev anyway? I got a fully running
62 >>>>>> KDE and this is my new install. Nothing pulled it in here. I may be
63 >>>>>> missing a USE flag or something.
64 >>>>>>
65 >>>>>> Let's hope this works for a while longer yet. ;-)
66 >>>>>>
67 >>>>>> Dale
68 >>>>>>
69 >>>>>> :-) :-)
70 >>>>>>
71 >>>>>>
72 >>>>>>
73 >>>>>>
74 >>>>> You need "evdev" in your INPUT_DEVICES variable (mine lives in
75 >>>>> make.conf). In my case I have:
76 >>>>>
77 >>>>> INPUT_DEVICES="keyboard mouse joystick evdev"
78 >>>>>
79 >>>>> and portage automagically built those packages.
80 >>>>>
81 >>>>>
82 >>>>>
83 >>>>>
84 >>>> So if evdev failed for some reason, it would fall back to the keyboard
85 >>>> and mouse drivers you think? That I would be willing to try if that is
86 >>>> the case.
87 >>>>
88 >>>> Dale
89 >>>>
90 >>>> :-) :-)
91 >>>>
92 >>>>
93 >>>>
94 >>> I don't know, for me it simply works as intended so... maybe I'll try
95 >>> to remove the keyboard and mouse and see what happens :) but in my
96 >>> case my xorg.conf is virtually empty aside from some fonts and nvidia
97 >>> card options. My display and input devices "just work" without being
98 >>> specified in xorg.conf with drivers, modelines or any of that stuff. I
99 >>> changed monitors yesterday and simply killed X and it restarted in the
100 >>> optimal resolution for the new monitor. I've plugged different
101 >>> mouse/keyboard and it just works automatically.
102 >>>
103 >>> The HAL policies in /etc/hal/fdi/policy contain the same exact
104 >>> settings as xorg.conf only formatted a little differently... you can
105 >>> give device-specific custom settings if you need and I think
106 >>> everything you have done in xorg.conf can be done the new way.
107 >>>
108 >>>
109 >>
110 >> I should say they CAN contain the same exact settings. It is up to you
111 >> to put them there :)
112 >>
113 >>
114 >>
115 >
116 > I'm curious about this now. I run my monitor at 1280x1024 but it can
117 > run 1600x something. Thing is, everything is so small, I can't really
118 > see anything. Even the mouse pointer is really small, about the size of
119 > a pencil lead. If I know where it is I can find it otherwise I have to
120 > push to a corner, then find it and go from there. I need new glasses
121 > but can't afford it right now.
122 >
123 > If I can still run at 1280x1024, this may be worth trying out. I would
124 > rather try it while the old way still works rather than wait until it
125 > doesn't and run into . . . issues.
126
127 Surely you can, the exact instructions depend on your video drivers
128 and desktop environment. I'm using KDE 3.5 and it gives me an
129 exhaustive list of screen resolutions I can choose to use as the
130 default.
131
132 As far as the size of things, I have a 2042x1152 monitor and my mouse
133 cursor is "normal" sized, not as small as yours sounds. (no, I'm not
134 bragging about who has the bigger mouse cursor :P)
135
136 As far as everything being too small at the higher resolution, it
137 sounds like your DPI setting may not be correct. If it's set, things
138 should be roughly the same physical size on any monitor in any
139 resolution, a 12-point font on a 15inch monitor running 1024x768
140 should be the same physical size as a 12-point font on a 20-inch
141 monitor running 1600x1200. Window decorations etc should be the same
142 size on any system if the WM/DE respects DPI. 1024x768 vs 1280x960 vs
143 1600x1200 should look the same from afar, the higher resolutions will
144 just look better because they are better. :)
145
146 A simple test to see if your system DPI is correct is to create a
147 blank text document in OpenOffice, set it to Print View which should
148 show a "sheet of paper" on the screen. Make sure the zoom is set to
149 100%. It should be exactly the same size as a real-life sheet of
150 paper. Hold a sheet of paper up to the screen and see if it's right.
151 If you type text into the document and then print it and hold it up to
152 the screen, again the text should be exactly the same size printed as
153 it is on the screen. (same test could be done on Windows using
154 Microsoft Word)
155
156 There is an exception: Bitmaps (pictures on web pages) and
157 fixed-pixel-size fonts. On websites, that's where the web browser zoom
158 function comes in handy. Most photo editing/viewing software allows
159 you to zoom so that's not usually a problem. Again, a photo zoomed to
160 fit the screen will just look better the higher the resolution you're
161 using despite being the same size on the screen.
162
163 Alternatively, you can use an incorrect DPI value on purpose to "zoom"
164 or "shrink" your desktop environment artificially instead of changing
165 all of the font sizes in KDE (or whatever you use).
166
167 All that being said, use whatever you're comfortable with, it's your
168 computer. :)