public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "JDM" <jdm@arcticwolf.myzen.co.uk>
To: "Gentoo" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] USB Problems
Date: Tue, 14 Jun 2011 07:18:02 +0000	[thread overview]
Message-ID: <1894814150-1308035885-cardhu_decombobulator_blackberry.rim.net-1387163609-@b11.c20.bise7.blackberry> (raw)

Have only tried CONFIG_HID_ROCCAT but this did not help. Will give the others a go.

Not quite sure why older kernels would recognise keyboard but .39 kernel does not and .38 I have issues with when plugging in usb stick. Are the kernel guys trying to make the hardware support more specific? Or should any keyboard be recognised? Fascinating

------Original Message------
From: Thanasis
To: Gentoo
Cc: john
ReplyTo: Gentoo
Subject: Re: [gentoo-user] USB Problems
Sent: 14 Jun 2011 07:59

on 06/14/2011 08:38 AM john wrote the following:
snip
> Will try studying all options in kernel to see if I can cure this.
> There are roccat options but these are for macros and don't help. But
> there maybe more other subtle ones available.
> 
> Regards
> 
> Thanks for your help

Have you enabled roccat support in 2.6.39 ?

grep -i roccat .config
# CONFIG_HID_ROCCAT is not set
# CONFIG_HID_ROCCAT_ARVO is not set
# CONFIG_HID_ROCCAT_KONE is not set
# CONFIG_HID_ROCCAT_KONEPLUS is not set
# CONFIG_HID_ROCCAT_KOVAPLUS is not set
# CONFIG_HID_ROCCAT_PYRA is not set



JDM

             reply	other threads:[~2011-06-14  7:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14  7:18 JDM [this message]
2011-06-14 11:52 ` [gentoo-user] USB Problems Indi
2011-06-14 15:50   ` Dale
2011-06-14 15:56     ` Thanasis
  -- strict thread matches above, loose matches on Subject: below --
2014-08-26 20:29 siefke_listen
2014-08-27  5:54 ` Alexander Kapshuk
2014-08-27  6:04 ` Alexander Kapshuk
2014-08-28 18:49 ` siefke_listen
2014-09-03 23:25 ` siefke_listen
2014-09-04  4:58   ` J. Roeleveld
2014-09-06 16:52     ` siefke_listen
2014-09-06 17:38       ` Alexander Kapshuk
2014-09-06 18:35       ` J. Roeleveld
2014-09-06 23:11         ` siefke_listen
2014-09-07  7:42           ` J. Roeleveld
2014-09-07 15:54             ` siefke_listen
2014-09-08 19:03               ` J. Roeleveld
2014-09-08 20:04                 ` Neil Bothwick
2014-09-09  5:04                 ` Stroller
2011-06-16  7:30 JDM
2011-06-12 14:30 john
2011-06-12 14:45 ` meino.cramer
2011-06-12 18:45   ` john
2011-06-12 19:20     ` meino.cramer
2011-06-12 20:50       ` Dale
2011-06-12 21:32         ` john
2011-06-12 21:57           ` Dale
2011-06-13  5:22             ` john
2011-06-13  5:44               ` Dale
2011-06-14  5:38                 ` john
2011-06-14  6:59                   ` Thanasis
2011-06-13  6:42               ` meino.cramer
2011-06-13 11:00                 ` Volker Armin Hemmann
2011-06-12 21:55         ` Volker Armin Hemmann
2011-06-12 22:04           ` Dale
2011-06-12 21:30       ` john
2011-06-12 23:35         ` Volker Armin Hemmann
2011-06-12 23:56         ` meino.cramer
2011-06-12 21:54 ` Volker Armin Hemmann
2011-06-15 23:34 ` Peter Humphrey

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=1894814150-1308035885-cardhu_decombobulator_blackberry.rim.net-1387163609-@b11.c20.bise7.blackberry \
    --to=jdm@arcticwolf.myzen.co.uk \
    --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