public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Boszormenyi <zboszor@freemail.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB mice do not work on 2.6.12-rc5-git9, -rc5-mm1, -rc5-mm2
Date: Sun, 05 Jun 2005 12:08:39 +0200	[thread overview]
Message-ID: <42A2CF27.8000806@freemail.hu> (raw)
In-Reply-To: <42A2BC4B.5060605@freemail.hu>

Zoltan Boszormenyi írta:
> Andrew Morton írta:
> 
>> Zoltan Boszormenyi <zboszor@freemail.hu> wrote:
>>
>>> Zoltan Boszormenyi írta:
>>>
>>>> Hi,
>>>>
>>>> $SUBJECT says almost all, system is MSI K8TNeo FIS2R,
>>>> Athlon64 3200+, running FC3/x86-64. I use the multiconsole
>>>> extension from linuxconsole.sf.net, the patch does not touch
>>>> anything relevant under drivers/input or drivers/usb.
>>>>
>>>> The mice are detected just fine but the mouse pointers
>>>> do not move on either of my two screens. The same patch
>>>> (not counting the trivial reject fixes) do work on the
>>>> 2.6.11-1.14_FC3 errata kernel. Both PS2 keyboard on the
>>>> keyboard and aux ports work correctly.
>>>
>>>
>>> The same patch also works on 2.6.12-rc4-mm2, with working mice.
>>> It seems the bug is mainstream.
>>>
>>
>>
>> Please test an unpatched kernel.
> 
> 
> Unmodified rc5-git9, only one X server started on the PCI Radeon
> so the agpgart isn't initialized in the attached dmesg.
> 
> Same bug, USB interrupt count does not change if mice are moved.
> I told you, it's upstream.

pci=routeirq - still same bug.
acpi=off     - rc5-git9 stops booting after PCI -> ACPI IRQ remapping.
???

I will try some older kernels, too.
2.6.12-rc4-mm2 definitely works.

Mainboard BIOS' version is 1.9,
I had ACPI problems with previous versions.

Best regards,
Zoltán Böszörményi

  reply	other threads:[~2005-06-05  9:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05  6:50 USB mice do not work on 2.6.12-rc5-git9, -rc5-mm1, -rc5-mm2 Zoltan Boszormenyi
2005-06-05  7:14 ` Zoltan Boszormenyi
2005-06-05  7:10   ` Andrew Morton
2005-06-05  7:27     ` Dmitry Torokhov
2005-06-05 14:18       ` Sid Boyce
2005-06-05 14:33         ` Sid Boyce
2005-06-05  8:48     ` Zoltan Boszormenyi
2005-06-05 10:08       ` Zoltan Boszormenyi [this message]
2005-06-05 10:29         ` Zoltan Boszormenyi
2005-06-05 15:17         ` Zoltan Boszormenyi
2005-06-06 20:33           ` Zoltan Boszormenyi
2005-06-06 22:04             ` Mousedev or hiddev problem, was: " Zoltan Boszormenyi
2005-06-07  5:39               ` Vojtech Pavlik
2005-06-08  4:55                 ` Zoltan Boszormenyi
2005-06-08  5:17                   ` Vojtech Pavlik
2005-06-05  9:09 ` Gene Heskett
2005-06-05  9:10 ` Gene Heskett

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=42A2CF27.8000806@freemail.hu \
    --to=zboszor@freemail.hu \
    --cc=akpm@osdl.org \
    --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