public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new machine : mouse trouble : solved by accident
Date: Fri, 14 Sep 2012 07:21:17 -0400	[thread overview]
Message-ID: <CA+czFiBOjgCAELWRXA-UWxcBWwcuMGNxAJrwT0HnaYx9KKsN=w@mail.gmail.com> (raw)
In-Reply-To: <20120914042448.GA6607@waltdnes.org>

[-- Attachment #1: Type: text/plain, Size: 1677 bytes --]

On Fri, Sep 14, 2012 at 12:24 AM, Walter Dnes <waltdnes@waltdnes.org> wrote:

> On Thu, Sep 13, 2012 at 10:06:01PM -0400, Philip Webb wrote
>
> > The effect is quite bizarre & it was the gods who saved me :
> > if I hadn't happened to plug the mouse into the neighbouring port,
> > I could have spent days struggling to find out what was wrong
> > & even taken the mobo back to the store as defective.
> >
> > Both Mageia -- installed from USB stick in a partition on the
> > HDD -- & System Rescue show  /dev/input/mouse0  after booting ;
> > in the case of SR it does it before I enter the GUI via 'wizard'.
> > They have no problem with the 2.0/1.1 port, but the Gentoo system as
> > I've installed it don't show  /dev/input/mouse0 from that port, but
> > only if I plug the mouse into the 3.0/2.0 port.  Someone suggested
> > it is caused by a Kernel .config setting, which if enabled seems to
> > force the system to look in the 3.0 port.  Why it should do that
> > doesn't make much sense : such upgrades are usually permissive,
> > not restrictive.  BTW there's no difference between 3.4.9 & 3.5.3 .
>
>   Is the cpu AMD?  Intel machines require UHCI (USB 1.1) and AMD
> machines require OHCI (USB 1.0) for lowspeed USB devices like keyboards
> and mice.  There's a root hub translator selection in .config that's
> *SUPPOSED* to work with keyboards+mice, using only the EHCI kernel
> driver, but I never could get it to work.
>

UHCI vs OHCI has nothing to do with the CPU, but with the chipset on the
system. I haven't seen an OHCI-supporting chip in over a decade, either,
and most of my systems have been AMD.

Either way, there's no harm in enabling both.

-- 
:wq

[-- Attachment #2: Type: text/html, Size: 2190 bytes --]

  reply	other threads:[~2012-09-14 11:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11 20:21 [gentoo-user] new machine : mouse trouble Philip Webb
2012-09-11 20:31 ` Paul Hartman
2012-09-11 22:25 ` Walter Dnes
2012-09-12 11:21   ` Philip Webb
2012-09-13 20:05     ` [gentoo-user] new machine : mouse trouble : solved by accident Philip Webb
2012-09-13 21:34       ` Mark Knecht
2012-09-13 21:53         ` Philip Webb
2012-09-13 22:58           ` Paul Hartman
2012-09-14  2:06             ` Philip Webb
2012-09-14  4:24               ` Walter Dnes
2012-09-14 11:21                 ` Michael Mol [this message]
2012-09-14 14:22                   ` Paul Hartman
2012-09-14 15:43                     ` Michael Mol
2012-09-14 15:32                   ` Volker Armin Hemmann
2012-09-15  0:16                     ` [gentoo-user] new machine : mouse trouble : finally explained Philip Webb

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='CA+czFiBOjgCAELWRXA-UWxcBWwcuMGNxAJrwT0HnaYx9KKsN=w@mail.gmail.com' \
    --to=mikemol@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