From: Michael Tokarev <mjt@tls.msk.ru>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: mouse&keyboard with 2.6.10+
Date: Mon, 14 Mar 2005 19:38:21 +0300 [thread overview]
Message-ID: <4235BDFD.1070505@tls.msk.ru> (raw)
In-Reply-To: <20050314162537.GA2716@ucw.cz>
Vojtech Pavlik wrote:
> On Mon, Mar 14, 2005 at 06:53:11PM +0300, Michael Tokarev wrote:
>
>>Vojtech Pavlik wrote:
>>
>>>On Mon, Mar 14, 2005 at 02:52:00PM +0300, Michael Tokarev wrote:
>>>
>>>
>>>
>>>>After plugging in USB keyboard and loading uhci-hcd and
>>>>usbhid, the keyboard un-freeze, but mouse still didn't
>>>>work. So I tried re-loading psmouse module, and
>>>>surprizingly, mouse started working again, but now dmesg
>>>>says:
>>>>
>>>>input: PS2++ Logitech Wheel Mouse on isa0060/serio1
>>>>
>>>>(normally it's
>>>>input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
>>>>)
>>>>
>>>>and the mouse is moving very fast now. Previously
>>>>I either didn't able to make it work at all after such
>>>>freeze, or it worked automatically after loading usbhid.
>>>>
>>>>BTW, it's 2.6.10, I can't made it work with 2.6.11 at all.
>>>
>>>
>>>Can you try 'usb-handoff' on the kernel command line?
>>
>>The problem has nothing to do with USB per se, as far as
>>I can see. PS2 keyboard and mouse does not work when
>>the USB subsystem (incl. usbcore) is not loaded. And the
>>problem is with PS2 keyboard/mouse, not with USB one which
>>works just fine.
>
> Of course. Nevertheless 'usb-handoff' tells the BIOS not to meddle with
> the PS/2 interfaces, too.
Oh me bad, I should listen to whatever is being said, instead
of doing my stupid guesses... Just rebooted into 2.6.11.3
with usb-handoff and both the keyboard and mouse are Just Works,
and psmouse driver loads almost immediately too.
Also, it works just fine after turning off USB Keyboard and
Mouse support in BIOS and without usb-handoff kernel parameter.
In 2.6.9 (it works just fine too, problem happens with 2.6.10
and up only), there's no such parameter in drivers/pci/quirks.c.
Hmm.
So is this a bios/mobo problem, or can it be solved in kernel
somehow?
Thanks very much for your attention.
/mjt
next prev parent reply other threads:[~2005-03-14 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 10:32 mouse&keyboard with 2.6.10+ Michael Tokarev
2005-03-14 11:52 ` Michael Tokarev
2005-03-14 14:28 ` Vojtech Pavlik
2005-03-14 15:53 ` Michael Tokarev
2005-03-14 16:25 ` Vojtech Pavlik
2005-03-14 16:38 ` Michael Tokarev [this message]
2005-03-14 16:43 ` Vojtech Pavlik
2005-03-14 19:06 ` Michael Tokarev
2005-03-14 19:21 ` Vojtech Pavlik
2005-03-22 1:24 ` Andrew Morton
2005-03-22 7:44 ` Vojtech Pavlik
2005-03-22 13:56 ` Alan Cox
2005-03-14 16:30 ` Dmitry Torokhov
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=4235BDFD.1070505@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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