The mouse needed its firmware updated. Razer mice have upgradeable
firmware. It has to be flashed from Windows.
That is all. With the latest firmware the problem is gone.
Thanks for the help everyone.
---
Using Tomcat but need to do more
On Thu, 30 Mar 2006, Gabor K. Horvath wrote:
> I tried a few more different kernels.
> FC5's 2.6.15 variant, 2.6.16, 2.6.16-mm2, 2.6.15 from Ubuntu.
>
> They all do the same dance. After a long off period the mouse won't
> generate events until reconnected.
>
> Is there anything I can do to trac
I tried a few more different kernels.
FC5's 2.6.15 variant, 2.6.16, 2.6.16-mm2, 2.6.15 from Ubuntu.
They all do the same dance. After a long off period the mouse won't
generate events until reconnected.
Is there anything I can do to track this down?
Is it worth reporting to bugzilla.kernel.org?
It's concievable.
X only sees events from 7 of its 9 buttons.
Luckily the 2 lost are not very ergonomically placed anyway.
Dave Dodge wrote:
The Razer Copperhead has a bunch of extra buttons. Perhaps it transmits
those as keyboard data?
-Dave
On Sun, Mar 26, 2006 at 12:18:54PM -0500, Alan Stern wrote:
> If you look at just the lines I extracted, you'll see that the device does
> indeed claim to be both a mouse and a keyboard.
The Razer Copperhead has a bunch of extra buttons. Perhaps it transmits
those as keyboard data?
On Sun, 26 Mar 2006, Horvath Gabor Kalman wrote:
> >It depends on what's in the descriptors the mouse sends to the computer.
> >If you use a recent version of lsusb, you should be able to see the
> >contents of those descriptors. Perhaps the mouse is claiming to be a
> >keyboard...
> >
> >
>
Alan Stern wrote:
On Sun, 26 Mar 2006, Horvath Gabor Kalman wrote:
That message is okay, nothing to worry about.
ack, thx.
It depends on what's in the descriptors the mouse sends to the computer.
If you use a recent version of lsusb, you should be able to see the
contents of those d
On Sun, 26 Mar 2006, Horvath Gabor Kalman wrote:
> When I replug the mouse I get this error:
> Mar 26 10:17:12 shelob kernel: drivers/usb/input/hid-core.c: can't
> resubmit intr, :00:02.0-5/input1, status -19
That message is okay, nothing to worry about. It will occur whenever you
unplug an
When I replug the mouse I get this error:
Mar 26 10:17:12 shelob kernel: drivers/usb/input/hid-core.c: can't
resubmit intr, :00:02.0-5/input1, status -19
Another strange thing I noticed:
Mar 26 10:17:18 shelob kernel: input: USB HID v0.01 Keyboard [Razer
Razer Copperhead Laser Mouse] on u
On Sat, 25 Mar 2006, Horvath Gabor Kalman wrote:
> Alan Stern wrote:
>
> >When you do a warm reboot, the mouse will be reinitialized. That happens
> >a long time after the mouse is plugged in.
> >
> >
> >
>
> Hmm. Last test I could come up with was a brief total power off (small
> switch on
Alan Stern wrote:
When you do a warm reboot, the mouse will be reinitialized. That happens
a long time after the mouse is plugged in.
Hmm. Last test I could come up with was a brief total power off (small
switch on the back of the PSU), then starting the machine.
Surprisingly the mouse
Hello,
I recently bought a Razer Copperhead mouse.
When I boot the box the mouse is detected, but sometimes X can't use it.
cat /dev/input/(mice|mouse0) is also silent.
If I unplug replug the thing it starts working right away.
On warm boots the mouse always works (as far as I know). On cold bo
On Thu, 23 Mar 2006, Horvath Gabor Kalman wrote:
> Alan Stern wrote:
>
> >What I meant was that the mouse needs to be "warmed up" before
> >initialization. Even when you left it plugged in for 20 minutes, it was
> >still initialized at boot time.
> >
> >
> I still can't say I understand this
Of course I forgot to mention the very thing I wanted to write about...
I tried the boot without mouse then plug in the mouse method.
The mouse works perfectly when I plug it in.
---
This SF.Net email is sponsored by xPML, a groundbreaking
Alan Stern wrote:
What I meant was that the mouse needs to be "warmed up" before
initialization. Even when you left it plugged in for 20 minutes, it was
still initialized at boot time.
I still can't say I understand this :)
It can't be warmed up before initialization can it?
The time that
On Thu, 23 Mar 2006, Gabor K. Horvath wrote:
> Alan Stern wrote:
>
> >Have you tried doing
> >
> > rmmod usbhid
> > modprobe usbhid
> >
> >when the mouse doesn't respond, instead of unplugging it?
> >
> >
> Yepp. I did that. No change.
>
> >What happens if you leave the mouse unplugged
Alan Stern wrote:
>Have you tried doing
>
> rmmod usbhid
> modprobe usbhid
>
>when the mouse doesn't respond, instead of unplugging it?
>
>
Yepp. I did that. No change.
>What happens if you leave the mouse unplugged while you boot (for example,
>if you unplug the mouse when you get
On Thu, 23 Mar 2006, Gabor K. Horvath wrote:
> Hello,
>
> I recently bought a Razer Copperhead mouse.
> When I boot the box the mouse is detected, but sometimes X can't use it.
>
> cat /dev/input/(mice|mouse0) is also silent.
>
> If I unplug replug the thing it starts working right away.
>
> O
Hello,
I recently bought a Razer Copperhead mouse.
When I boot the box the mouse is detected, but sometimes X can't use it.
cat /dev/input/(mice|mouse0) is also silent.
If I unplug replug the thing it starts working right away.
On warm boots the mouse always works (as far as I know). On cold bo
19 matches
Mail list logo
