On Fri, Jan 16, 2009 at 1:36 AM, Dale <[email protected]> wrote: > Paul Hartman wrote: >> On Fri, Jan 16, 2009 at 12:59 AM, Dale <[email protected]> wrote: >> >>> Wolfgang Liebich wrote: >>> >>>> On Thu, Jan 15, 2009 at 09:35:11AM -0600, Paul Hartman wrote: >>>> >>>> >>>>> On Thu, Jan 15, 2009 at 2:58 AM, Wolfgang Liebich >>>>> <[email protected]> wrote: >>>>> >>>>> >>>>>> Furthermore yesterday I had a total lockup when I came to work at the >>>>>> morning --- could not login at kdm, kdm would ignore all keyboard >>>>>> input etc. I had to do a hard restart with the "Magic SysRQ" key >>>>>> (remount ro, hard reboot). >>>>>> >>>>>> >>>>> Do you have evdev installed? Without it, you probably won't have any >>>>> keyboard or mouse. Recent xorg made dramatic changes to the way >>>>> hardware is detected/configured by using HAL and evdev. xorg.conf is >>>>> basically unused now when it comes to configuring hardware. I don't >>>>> even have keyboard or mouse, or video modelines or anything like that >>>>> in mine. Search the list archives or the gentoo web forums, there are >>>>> many many people who had the same issues (assuming it's the cause of >>>>> yours). >>>>> >>>>> >>>> Evdev is installed, but I configured the kbd driver (I have a MS >>>> Natural Keyboard, btw --- what's the best driver for that keyboard?). >>>> I still have an xorg.conf (and I'm not very inclined to change it as >>>> long as it works :-). >>>> >>>> Furthermore -- after the reboot everything worked again as before. It >>>> seems to have been some fluke, but I want to know where it comes from. >>>> >>>> TIA, >>>> Wolfgang >>>> >>>> >>>> >>> Someone else like me. I still have my xorg.conf and want to keep it >>> too. I don't have evdev installed but from the way it sounds, me and >>> you may have to change in the future, maybe near future. >>> >>> I'm sort of wondering what pulls in evdev anyway? I got a fully running >>> KDE and this is my new install. Nothing pulled it in here. I may be >>> missing a USE flag or something. >>> >>> Let's hope this works for a while longer yet. ;-) >>> >>> Dale >>> >>> :-) :-) >>> >>> >>> >> >> You need "evdev" in your INPUT_DEVICES variable (mine lives in >> make.conf). In my case I have: >> >> INPUT_DEVICES="keyboard mouse joystick evdev" >> >> and portage automagically built those packages. >> >> >> > > So if evdev failed for some reason, it would fall back to the keyboard > and mouse drivers you think? That I would be willing to try if that is > the case. > > Dale > > :-) :-) > >
I don't know, for me it simply works as intended so... maybe I'll try to remove the keyboard and mouse and see what happens :) but in my case my xorg.conf is virtually empty aside from some fonts and nvidia card options. My display and input devices "just work" without being specified in xorg.conf with drivers, modelines or any of that stuff. I changed monitors yesterday and simply killed X and it restarted in the optimal resolution for the new monitor. I've plugged different mouse/keyboard and it just works automatically. The HAL policies in /etc/hal/fdi/policy contain the same exact settings as xorg.conf only formatted a little differently... you can give device-specific custom settings if you need and I think everything you have done in xorg.conf can be done the new way.
