From: Philip Webb <purslow@ca.inter.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new machine : mouse trouble : solved by accident
Date: Thu, 13 Sep 2012 17:53:26 -0400 [thread overview]
Message-ID: <20120913215326.GB2893@ca.inter.net> (raw)
In-Reply-To: <CAK2H+eeSYqcn==rasoNHzzMRYH2FQRWx-v_fT4uC2+SRAuJT3Q@mail.gmail.com>
120913 Mark Knecht wrote:
> On Thu, Sep 13, 2012 at 1:05 PM, Philip Webb <purslow@ca.inter.net> wrote:
>> 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 .
> Look at which host controller interfaces you have enabled.
> IIRC USB-3.0 required a new one - probably XHCI but I don't remember.
> 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
Yes, the 3.4.9 .config has nearly all of those.
However, I'm not sure that your logic is the right way round (smile):
something is telling Kernel + Udev to recognise only a 3.0 mouse,
whereas Mageia/SR recognise a 2.0 mouse ; the mouse is 2012 ,
so perhaps it will function either way, depending on software.
Why would K+U not recognise a 2.0 mouse ?
That also suggests that if I plug a USB stick into those 2 back ports,
it will give faster transfer speed ; the front ports are 2.0/1.1 .
Is it safe to test that ? -- ie I don't want to ruin a stick.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT `-O----------O---' purslowatchassdotutorontodotca
next prev parent reply other threads:[~2012-09-13 21:55 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 [this message]
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=20120913215326.GB2893@ca.inter.net \
--to=purslow@ca.inter.net \
--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