1 |
Paul Hartman wrote: |
2 |
> On Fri, Jan 16, 2009 at 1:58 AM, Paul Hartman |
3 |
> <paul.hartman+gentoo@×××××.com> wrote: |
4 |
> |
5 |
>> On Fri, Jan 16, 2009 at 1:36 AM, Dale <rdalek1967@×××××.com> wrote: |
6 |
>> |
7 |
>>> Paul Hartman wrote: |
8 |
>>> |
9 |
>>>> On Fri, Jan 16, 2009 at 12:59 AM, Dale <rdalek1967@×××××.com> wrote: |
10 |
>>>> |
11 |
>>>> |
12 |
>>>>> Wolfgang Liebich wrote: |
13 |
>>>>> |
14 |
>>>>> |
15 |
>>>>>> On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote: |
16 |
>>>>>> |
17 |
>>>>>> |
18 |
>>>>>> |
19 |
>>>>>>> On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich |
20 |
>>>>>>> <Wolfgang.Liebich@×××××××.com> wrote: |
21 |
>>>>>>> |
22 |
>>>>>>> |
23 |
>>>>>>> |
24 |
>>>>>>>> Furthermore yesterday I had a total lockup when I came to work at the |
25 |
>>>>>>>> morning --- could not login at kdm, kdm would ignore all keyboard |
26 |
>>>>>>>> input etc. I had to do a hard restart with the "Magic SysRQ" key |
27 |
>>>>>>>> (remount ro, hard reboot). |
28 |
>>>>>>>> |
29 |
>>>>>>>> |
30 |
>>>>>>>> |
31 |
>>>>>>> Do you have evdev installed? Without it, you probably won't have any |
32 |
>>>>>>> keyboard or mouse. Recent xorg made dramatic changes to the way |
33 |
>>>>>>> hardware is detected/configured by using HAL and evdev. xorg.conf is |
34 |
>>>>>>> basically unused now when it comes to configuring hardware. I don't |
35 |
>>>>>>> even have keyboard or mouse, or video modelines or anything like that |
36 |
>>>>>>> in mine. Search the list archives or the gentoo web forums, there are |
37 |
>>>>>>> many many people who had the same issues (assuming it's the cause of |
38 |
>>>>>>> yours). |
39 |
>>>>>>> |
40 |
>>>>>>> |
41 |
>>>>>>> |
42 |
>>>>>> Evdev is installed, but I configured the kbd driver (I have a MS |
43 |
>>>>>> Natural Keyboard, btw --- what's the best driver for that keyboard?). |
44 |
>>>>>> I still have an xorg.conf (and I'm not very inclined to change it as |
45 |
>>>>>> long as it works :-). |
46 |
>>>>>> |
47 |
>>>>>> Furthermore -- after the reboot everything worked again as before. It |
48 |
>>>>>> seems to have been some fluke, but I want to know where it comes from. |
49 |
>>>>>> |
50 |
>>>>>> TIA, |
51 |
>>>>>> Wolfgang |
52 |
>>>>>> |
53 |
>>>>>> |
54 |
>>>>>> |
55 |
>>>>>> |
56 |
>>>>> Someone else like me. I still have my xorg.conf and want to keep it |
57 |
>>>>> too. I don't have evdev installed but from the way it sounds, me and |
58 |
>>>>> you may have to change in the future, maybe near future. |
59 |
>>>>> |
60 |
>>>>> I'm sort of wondering what pulls in evdev anyway? I got a fully running |
61 |
>>>>> KDE and this is my new install. Nothing pulled it in here. I may be |
62 |
>>>>> missing a USE flag or something. |
63 |
>>>>> |
64 |
>>>>> Let's hope this works for a while longer yet. ;-) |
65 |
>>>>> |
66 |
>>>>> Dale |
67 |
>>>>> |
68 |
>>>>> :-) :-) |
69 |
>>>>> |
70 |
>>>>> |
71 |
>>>>> |
72 |
>>>>> |
73 |
>>>> You need "evdev" in your INPUT_DEVICES variable (mine lives in |
74 |
>>>> make.conf). In my case I have: |
75 |
>>>> |
76 |
>>>> INPUT_DEVICES="keyboard mouse joystick evdev" |
77 |
>>>> |
78 |
>>>> and portage automagically built those packages. |
79 |
>>>> |
80 |
>>>> |
81 |
>>>> |
82 |
>>>> |
83 |
>>> So if evdev failed for some reason, it would fall back to the keyboard |
84 |
>>> and mouse drivers you think? That I would be willing to try if that is |
85 |
>>> the case. |
86 |
>>> |
87 |
>>> Dale |
88 |
>>> |
89 |
>>> :-) :-) |
90 |
>>> |
91 |
>>> |
92 |
>>> |
93 |
>> I don't know, for me it simply works as intended so... maybe I'll try |
94 |
>> to remove the keyboard and mouse and see what happens :) but in my |
95 |
>> case my xorg.conf is virtually empty aside from some fonts and nvidia |
96 |
>> card options. My display and input devices "just work" without being |
97 |
>> specified in xorg.conf with drivers, modelines or any of that stuff. I |
98 |
>> changed monitors yesterday and simply killed X and it restarted in the |
99 |
>> optimal resolution for the new monitor. I've plugged different |
100 |
>> mouse/keyboard and it just works automatically. |
101 |
>> |
102 |
>> The HAL policies in /etc/hal/fdi/policy contain the same exact |
103 |
>> settings as xorg.conf only formatted a little differently... you can |
104 |
>> give device-specific custom settings if you need and I think |
105 |
>> everything you have done in xorg.conf can be done the new way. |
106 |
>> |
107 |
>> |
108 |
> |
109 |
> I should say they CAN contain the same exact settings. It is up to you |
110 |
> to put them there :) |
111 |
> |
112 |
> |
113 |
> |
114 |
|
115 |
I'm curious about this now. I run my monitor at 1280x1024 but it can |
116 |
run 1600x something. Thing is, everything is so small, I can't really |
117 |
see anything. Even the mouse pointer is really small, about the size of |
118 |
a pencil lead. If I know where it is I can find it otherwise I have to |
119 |
push to a corner, then find it and go from there. I need new glasses |
120 |
but can't afford it right now. |
121 |
|
122 |
If I can still run at 1280x1024, this may be worth trying out. I would |
123 |
rather try it while the old way still works rather than wait until it |
124 |
doesn't and run into . . . issues. |
125 |
|
126 |
Dale |
127 |
|
128 |
:-) :-) |