| To: | =?iso-8859-1?Q? Frank=20F=F6rstemann ?= <Foerstemann@web.de> |
|---|---|
| Subject: | Re: No mouse support for Indy in 2.5.75 ? |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Tue, 29 Jul 2003 13:49:04 +0200 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <200307252137.h6PLb6Q01329@mailgate5.cinetic.de> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <200307252137.h6PLb6Q01329@mailgate5.cinetic.de> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Fri, Jul 25, 2003 at 11:37:06PM +0200, =?iso-8859-1?Q? Frank=20F=F6rstemann ?= wrote: > I tried kernel version 2.5.75 on my Indy. It works fine with the > exception that the mouse in XFree86 does not move. The devices are > available, but event debugging shows no mouse events at all. Are there > any special configuration options for the Indy mouse except the ones in > the 'input' section ? Dmesg output and kernel configuration are > attached. We knew there was something wrong in that area; the probe for kbd and mouse also takes very long on the Indy. What worries me more are those kernel messages from your log: mount: Exception at [<88113a38>] (88113bf0) mount: Exception at [<88113a38>] (88113bf0) mount: Exception at [<88113a38>] (88113bf0) Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | 64bit _syscall6 fix, Atsushi Nemoto |
|---|---|
| Next by Date: | Re: CVS Update@-mips.org: linux, Jan-Benedict Glaw |
| Previous by Thread: | No mouse support for Indy in 2.5.75 ?, Frank=20F=F6rstemann |
| Next by Thread: | Re: No mouse support for Indy in 2.5.75 ?, Frank=20F=F6rstemann |
| Indexes: | [Date] [Thread] [Top] [All Lists] |