From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new machine : mouse trouble : solved by accident
Date: Thu, 13 Sep 2012 14:34:18 -0700 [thread overview]
Message-ID: <CAK2H+eeSYqcn==rasoNHzzMRYH2FQRWx-v_fT4uC2+SRAuJT3Q@mail.gmail.com> (raw)
In-Reply-To: <20120913200500.GA2893@ca.inter.net>
On Thu, Sep 13, 2012 at 1:05 PM, Philip Webb <purslow@ca.inter.net> wrote:
> No progress yesterday. Today, I carefully checked the Kernel .config
> & installed 3.4.9 , in case there was something new in 3.5.3 :
> I have 3.4.0 in this machine, where the mouse works.
> Then I started looking a Udev in this machine to see what mb missing there.
> Back in the new machine, I was preparing to remerge -evdev- etc
> & casually checked /dev/input : mouse0 was there !
> I logged in as user, 'startx' & the mouse worked in Fluxbox !
> -- Xorg.log had found a Logitech mouse at /dev/input/event3 using evdev.
> Well, perhaps it was some setting which took effect after the reboot.
>
> Well, no, it wasn't. When I had switched off & was replugging connections,
> I found that I'd plugged the mouse into a different USB slot :
> the previous one -- similar to the one in this machine -- was 2.0/1.1 ,
> the new one which works is 3.0/2.0 . NB Mageia + SystemRescue both
> find the mouse in the former place, but my new Gentoo only in the latter.
> The new mobo is a Gigabyte GA-990FXA-UD3 ; this one is an ASUS P5G41T-M .
>
> Further comments are very welcome.
>
> --
> ========================,,============================================
> SUPPORT ___________//___, Philip Webb
> ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
> TRANSIT `-O----------O---' purslowatchassdotutorontodotca
>
>
Look at which host controller interfaces you have enabled. IIRC
USB-3.0 required a new one - probably XHCI but I don't really
remember.
HTH,
Mark
mark@slinky ~ $ zcat /proc/config.gz | grep HCI
CONFIG_SATA_AHCI=y
# CONFIG_SATA_AHCI_PLATFORM is not set
# CONFIG_SATA_ACARD_AHCI is not set
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_ARCH_HAS_XHCI=y
CONFIG_USB_XHCI_HCD=y
# CONFIG_USB_XHCI_HCD_DEBUGGING is not set
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_HCD_PLATFORM is not set
# CONFIG_USB_EHCI_HCD_PLATFORM is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
mark@slinky ~ $
next prev parent reply other threads:[~2012-09-13 21:36 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 [this message]
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
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='CAK2H+eeSYqcn==rasoNHzzMRYH2FQRWx-v_fT4uC2+SRAuJT3Q@mail.gmail.com' \
--to=markknecht@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