public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Feiler <kiza@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4.19, USB_HID only works compiled in, not as module
Date: Sun, 4 Aug 2002 16:56:19 +0200	[thread overview]
Message-ID: <200208041656.21035.kiza@gmx.net> (raw)

Hi,

Since 2.4.19 a usb mouse does not work anymore if

CONFIG_USB_HID=m
and
CONFIG_INPUT_MOUSEDEV=m

is set. It only works if both are compiled into the kernel. Yes, I have set
CONFIG_USB_HIDINPUT=y.

I've also seen other complaints about usb mice not working in 2.4.19, I guess 
that's the problem?

If the stuff is compiled as modules, everything seems to be fine. The kernel 
messages are the same, everything is detected fine. Except that 'cat 
/dev/input/mice' does not give any output if the driver is compiled as 
module.

Cheers,
Oliver

-- 
Oliver Feiler  <kiza@(gmx(pro).net|lionking.org|claws-and-paws.com)>
http://www.lionking.org/~kiza/  <--   homepage
PGP-key ID 0x561D4FD2    --> /pgpkey.shtml
http://www.lionking.org/~kiza/journal/


             reply	other threads:[~2002-08-04 14:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-04 14:56 Oliver Feiler [this message]
2002-08-04 16:20 ` 2.4.19, USB_HID only works compiled in, not as module Greg KH
2002-08-04 16:53   ` Oliver Feiler
     [not found] <fa.egf7e0v.kk5a2@ifi.uio.no>
2002-08-04 15:07 ` Jonathan Hudson
2002-08-04 15:46   ` Oliver Feiler
2002-08-04 21:51     ` Brad Hards
2002-08-04 22:41       ` Oliver Feiler
2002-08-18 12:52       ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2002-08-05  5:34 Tyler Longren
2002-08-05 11:14 ` Brad Hards
2002-08-05 14:00   ` Brad Hards
2002-08-05 14:37     ` K.R. Foley
2002-08-05 16:56     ` Greg KH
2002-08-05 21:02       ` Brad Hards
2002-08-06  5:41         ` Tyler Longren
2002-08-07 10:50         ` Oliver Feiler
2002-08-07 22:24           ` Brad Hards
2002-08-07 22:51             ` Oliver Feiler

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=200208041656.21035.kiza@gmx.net \
    --to=kiza@gmx.net \
    --cc=linux-kernel@vger.kernel.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