linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-usb@vger.kernel.org, linux-input@vger.kernel.org,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 12340] New: [regression] USB keyboard no longer recognised
Date: Sun, 04 Jan 2009 13:04:50 +0100	[thread overview]
Message-ID: <4960A5E2.2050601@freemail.hu> (raw)
In-Reply-To: <alpine.LRH.1.10.0901041151510.2418@twin.jikos.cz>

Jiri Kosina wrote:
> On Thu, 1 Jan 2009, Németh Márton wrote:
> 
>>>> Steps to reproduce:
>>>> 1. boot kernel with parameters "rw root=/dev/sdb1 log_buf_len=1M init=/bin/
>>>> bash"
>>>> 2. modprobe -k uhci_hcd
>>>> 3. modprobe -k usbhid
>>>> Current result in case of 2.6.27: USB keyboard starts to work
>>>> Current result in case of 2.6.28: USB keyboard does not work
>>> Is it input/HID, or USB?
>> The same USB keyboard is working correctly with Clevo D410J laptop with 2.6.28,
>> so I guess it might be an USB problem.
> 
> Why are you doing the modprobe by hand? Doesn't the module get autoloaded 
> properly?

The modules were not autoloaded. This is a minimal test environment with only
a few binaries in the root directory. Is the "modprobe" binary enough for
autoloading?

> Anyway, in 2.6.28, this keyboard is driven by specialized 'hid-bright' 
> driver. Does modprobing it by hand fix the problem?

I'll try the hid-bright module as soon as my laptop gets repaired.
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-01-04 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12340-10286@http.bugzilla.kernel.org/>
2009-01-01  9:12 ` [Bugme-new] [Bug 12340] New: [regression] USB keyboard no longer recognised Andrew Morton
     [not found]   ` <20090101011223.6a10dd66.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2009-01-01  9:20     ` Németh Márton
2009-01-01 17:35       ` Alan Stern
     [not found]       ` <495C8AE3.5000502-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
2009-01-04 10:53         ` Jiri Kosina
2009-01-04 12:04           ` Németh Márton [this message]
     [not found]             ` <4960A5E2.2050601-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
2009-01-05  7:31               ` Németh Márton
2009-01-05  9:13                 ` Jiri Kosina
2009-01-01 13:37   ` Oliver Neukum

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=4960A5E2.2050601@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).