public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: xorg-server mouse and keyboard woes
Date: Fri, 10 Jul 2009 13:47:09 -0500	[thread overview]
Message-ID: <4A578CAD.2020907@gmail.com> (raw)
In-Reply-To: <200907101946.00954.alan.mckinnon@gmail.com>

Alan McKinnon wrote:
> On Friday 10 July 2009 17:43:44 Kevin O'Gorman wrote:
>   
>> On Fri, Jul 10, 2009 at 4:55 AM, Philip Webb<purslow@ca.inter.net> wrote:
>>     
>>> 090709 Kevin O'Gorman wrote:
>>>       
>>>>> On Thu, Jul 9, 2009 at 8:51 PM, Dale<rdalek1967@gmail.com> wrote:
>>>>>           
>>>>>> If all else fails:
>>>>>> x11-base/xorg-server  -hal
>>>>>>             
>>>>> Is there any other advice?
>>>>>           
>>>> A new HAL made no difference.  Sigh.
>>>>         
>>> I ran into this twice, first on my frontline machine, then on the
>>> stand-by. The solution was 'USE="-hal" emerge xorg-server', then remerge
>>> all drivers. There was a Gentoo help doc re it, which gave this as the
>>> simplest option.
>>>
>>> 'evdev' is a separate matter: you need to include it in your kernel,
>>> than you can simplify your drivers.
>>>
>>> HTH
>>>       
>> Evdev has been included in my kernels throughout this mess.  It hasn't
>> helped.  The Gentoo doc on the upgrade was a bit scetchy about
>> configuring HAL; now that I find that disabling HAL in xorg is the
>> solution, I suspect that the underlying problem is HAL configuration.
>> After all, there's nothing at all special about my mouse or keyboard.
>>
>> Why should we have to configure HAL manually?  Since the stone ages,
>> Linux installations have determined what keyboard we have and have set
>> things up for us.  How different can PS/2 or USB mice be?
>>
>> SO: if anyone succeeded with xorg and HAL, with a USA keyboard and a
>> wheel mouse,  would please tell me about their HAL config, I'd sure
>> love to see it.
>>     
>
> I run latest unstable here with a regular USA layout on a Dell XPS M1530 with 
> nvidia driver, hal and evdev. The HAL config is empty apart from a policy file 
> for a touch pad, and it's a dual-screen setup. Here's my xorg.conf:
>
> # egrep -v '^$|^#' /etc/X11/xorg.conf
> Section "ServerLayout"
>     Identifier     "Layout0"
>     Screen      0  "Screen0" 0 0
> EndSection
> Section "Files"
> EndSection
> Section "Module"
>     Load           "dbe"
>     Load           "extmod"
>     Load           "glx"
> EndSection
> Section "ServerFlags"
>     Option         "Xinerama" "0"
> EndSection
> Section "Monitor"
>     # HorizSync source: edid, VertRefresh source: edid
>     Identifier     "Monitor0"
>     VendorName     "Unknown"
>     ModelName      "Samsung SyncMaster"
>     HorizSync       30.0 - 81.0
>     VertRefresh     56.0 - 75.0
>     Option         "DPMS"
> EndSection
> Section "Device"
>     Identifier     "Device0"
>     Driver         "nvidia"
>     VendorName     "NVIDIA Corporation"
>     BoardName      "GeForce 8600M GT"
> EndSection
> Section "Screen"
>     Identifier     "Screen0"
>     Device         "Device0"
>     Monitor        "Monitor0"
>     DefaultDepth    24
>     Option         "NoLogo" "True"
>     Option         "TwinView" "1"
>     Option         "TwinViewXineramaInfoOrder" "DFP-0"
>     Option         "metamodes" "CRT: nvidia-auto-select @1440x900 +1920+0, 
> DFP: nvidia-auto-select +0+0"
>     SubSection     "Display"
>         Depth       24
>     EndSubSection
> EndSection
>
> It all JustWorks for me, I assume in my case at least it's working as 
> designed.
>
>   

What gets me is this, I even did a fresh install on another hard drive,
it don't work there either.  hal and friends were included from the very
start of the install too.  Either I am missing something that is not in
the guide or it just don't like my hardware.  My mouse is a old P/S2
type mouse.  It's not even as complicated as a USB thingy.

Dale

:-)  :-) 



  reply	other threads:[~2009-07-10 18:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-10  3:03 [gentoo-user] xorg-server mouse and keyboard woes Kevin O'Gorman
2009-07-10  3:18 ` [gentoo-user] " James
2009-07-10  3:51   ` Dale
2009-07-10  4:52     ` Kevin O'Gorman
2009-07-10  5:02       ` Dale
2009-07-10  5:40         ` Kevin O'Gorman
2009-07-10  5:33       ` Kevin O'Gorman
2009-07-10  5:52         ` Dale
2009-07-10  7:34         ` Robin Atwood
2009-07-10 11:55         ` Philip Webb
2009-07-10 15:43           ` Kevin O'Gorman
2009-07-10 15:58             ` Dale
2009-07-10 17:46             ` Alan McKinnon
2009-07-10 18:47               ` Dale [this message]
2009-07-11  6:04                 ` Keith Dart
2009-07-11  6:40                   ` Dale
2009-07-10  8:18 ` [gentoo-user] " Keith Dart
2009-07-10  8:24   ` Keith Dart
2009-07-10 10:07     ` Kevin O'Gorman
2009-07-10 10:10   ` Kevin O'Gorman
2009-07-10 13:19     ` Dale
2009-07-10 14:22       ` Paul Hartman
2009-07-10 14:32       ` Helmut Jarausch
2009-07-10 16:02         ` Dale
2009-07-10 16:03         ` Kevin O'Gorman
2009-07-10  8:29 ` Helmut Jarausch
2009-07-10 18:50   ` [gentoo-user] " walt
2009-07-10 19:07     ` David
2009-07-11  3:53     ` Kevin O'Gorman
2009-07-11  5:46       ` Keith Dart
2009-07-12  5:03         ` Kevin O'Gorman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A578CAD.2020907@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox