public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin McWhorter <m_mcwhorter@prairiegroup.com>
To: Pete Zaitcev <zaitcev@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Possible Bug: 2.4.14 USB Keyboard
Date: Thu, 15 Nov 2001 13:57:11 -0600	[thread overview]
Message-ID: <3BF41E17.5080200@prairiegroup.com> (raw)
In-Reply-To: <3BF2DFBF.6090502@prairiegroup.com> <20011114145312.A6925@kroah.com> <mailman.1005834780.32418.linux-kernel2news@redhat.com> <200111151807.fAFI7XN30496@devserv.devel.redhat.com> <3BF40D17.4060501@prairiegroup.com> <20011115141430.B10133@devserv.devel.redhat.com>

Pete,


>>usbkbd                  2944   0  (unused)
>>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 
> YES! Kill this bastard (the best of all is to use rm(1), then reboot).
> 


rm /lib/modules/2.4.14/kernel/drivers/usb/usbkbd.o

reboot

HP usb-keyboard still does not work. Now the kernel that it does work 
with is 2.4.2 from redhat's tree. I have not tried it with a vanilla 2.4.2

Now when I do an
[root@m_mcwhorter m_mcwhorter]# /sbin/lsmod
Module                  Size  Used by
emu10k1                49584   0  (autoclean)
sr_mod                 13968   0  (autoclean)
ac97_codec              9248   0  (autoclean) [emu10k1]
soundcore               3376   4  (autoclean) [emu10k1]
autofs                  9184   1  (autoclean)
8139too                13152   1  (autoclean)
ipchains               31232   0
ide-scsi                7712   0
scsi_mod               86256   2  [sr_mod ide-scsi]
ide-cd                 26624   0
cdrom                  27328   0  [sr_mod ide-cd]
mousedev                3936   1
keybdev                 1728   0  (unused)
hid                    12576   0  (unused)
input                   3136   0  [mousedev keybdev hid]
usb-uhci               21344   0  (unused)
usbcore                49184   1  [hid usb-uhci]

Martin


  reply	other threads:[~2001-11-15 19:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 21:18 Possible Bug: 2.4.14 USB Keyboard Martin McWhorter
2001-11-14 22:53 ` Greg KH
2001-11-15 14:24   ` Martin McWhorter
2001-11-15 17:00     ` Greg KH
2001-11-15 18:40       ` Martin McWhorter
2001-11-15 18:55         ` Vojtech Pavlik
     [not found]         ` <mailman.1005850740.5583.linux-kernel2news@redhat.com>
2001-11-15 19:30           ` Pete Zaitcev
2001-11-15 19:47             ` Vojtech Pavlik
     [not found]   ` <mailman.1005834780.32418.linux-kernel2news@redhat.com>
     [not found]     ` <200111151807.fAFI7XN30496@devserv.devel.redhat.com>
2001-11-15 18:44       ` Martin McWhorter
2001-11-15 19:14         ` Pete Zaitcev
2001-11-15 19:57           ` Martin McWhorter [this message]
     [not found]             ` <20011115152432.A26630@devserv.devel.redhat.com>
2001-11-15 21:30               ` Martin McWhorter
     [not found]                 ` <20011115170148.A19715@devserv.devel.redhat.com>
     [not found]                   ` <3BF43E55.80401@prairiegroup.com>
     [not found]                     ` <20011115171751.A22915@devserv.devel.redhat.com>
2001-11-15 22:40                       ` Martin McWhorter
2001-11-16  0:03                         ` Greg KH

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=3BF41E17.5080200@prairiegroup.com \
    --to=m_mcwhorter@prairiegroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.com \
    /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