On Monday 06 September 2004 21:52, Yedidyah Bar-David wrote:
> On Mon, Sep 06, 2004 at 05:13:31PM +0300, ik wrote:
> > Hello list,
> >
> > I have a problem with my Mouse: Logitech Marble USB.
> > The mouse connected into my screen: LG Flatron 795 FT Plus, that connected to the
> > motherboard itself (I receive this way
> > more USB ports -> for people that are going to ask why).
>
> This is the obvious reason, but this isn't the question. The question
> is whether you tried to connect it directly and still had the problem.
> It could be a problem in the monitor/USB hub.
>
> >
> > Every now and then, The mouse stops responding in X, and I find that even GPM
> > stops working. When I leave the computer alone for at least one
> > minute.
> > I can't seems to reload the mouse, not in X (exit X and restart it) and no GPM run
> > as well.
> > Please note that I login into init 3 state from the beginning, so no ?dm and no X
> > itself loaded in the beginning.
> > I'm also using "hotplug" for usb detection.
>
> What does solve it? Only a reboot?
Yes only reboot helps ... I thought I wrote it down but it seems that I forgot it :(
sorry!
>
> >
> > When I started monitor this situation, I found out in the messages log:
> > Sep 6 16:07:08 ikn kernel: usb 1-1.3: new low speed USB device using address 6
> > Sep 6 16:07:08 ikn kernel: input: USB HID v1.10 Mouse [Logitech USB Trackball] on
> > usb-0000:00:1f.2-1.3
> > Sep 6 16:07:09 ikn input.agent[6537]: evbug: blacklisted
> > Sep 6 16:07:09 ikn input.agent[6553]: evbug: blacklisted
> > Sep 6 16:07:09 ikn input.agent[6553]: evdev: already loaded
> > Sep 6 16:07:09 ikn input.agent[6546]: evbug: blacklisted
> > Sep 6 16:07:09 ikn input.agent[6537]: evdev: already loaded
> > Sep 6 16:07:09 ikn input.agent[6562]: tsdev: already loaded
> > Sep 6 16:07:09 ikn input.agent[6546]: evdev: already loaded
> > Sep 6 16:07:09 ikn input.agent[6562]: mousedev: already loaded
> > Sep 6 16:07:09 ikn input.agent[6562]: evbug: blacklisted
> > Sep 6 16:07:09 ikn usb.agent[6521]: usbmouse: blacklisted
> > Sep 6 16:07:09 ikn input.agent[6562]: evdev: already loaded
> > Sep 6 16:07:09 ikn usb.agent[6521]: usbhid: already loaded
> > Sep 6 16:07:09 ikn input.agent[6562]: joydev: already loaded
> >
> > And every hour +- it tries again to detect the mouse.
>
> Can you check the logs and see if it's _exactly_ one hour? If it is,
> it might be some cron or such. If it's random, it's soemthing else.
> Also please send a few lines before and after this. I would personally
> expect messages about a disconnect before the "new device" ones.
Yes It happned evey hour over and over again untill the reboot time has come...
But I can't find any /etc/cron.hourly entry of any kind...
Here a dump of the messages:
Sep 8 01:02:03 ikn gconfd (ik-25087): GConf server is not in use, shutting down.
Sep 8 01:02:03 ikn gconfd (ik-25087): Exiting
Sep 8 01:02:08 ikn kernel: usb 1-1.3: new low speed USB device using address 6
Sep 8 01:02:09 ikn kernel: input: USB HID v1.10 Mouse [Logitech USB Trackball] on
usb-0000:00:1f.2-1.3
Sep 8 01:02:10 ikn input.agent[25239]: evbug: blacklisted
Sep 8 01:02:10 ikn input.agent[25251]: tsdev: already loaded
Sep 8 01:02:10 ikn input.agent[25239]: evdev: already loaded
Sep 8 01:02:10 ikn input.agent[25251]: mousedev: already loaded
Sep 8 01:02:10 ikn usb.agent[25197]: usbmouse: blacklisted
Sep 8 01:02:10 ikn input.agent[25251]: evbug: blacklisted
Sep 8 01:02:10 ikn usb.agent[25197]: usbhid: already loaded
Sep 8 01:02:10 ikn input.agent[25213]: evbug: blacklisted
Sep 8 01:02:10 ikn input.agent[25213]: evdev: already loaded
Sep 8 01:02:10 ikn input.agent[25251]: evdev: already loaded
Sep 8 01:02:10 ikn input.agent[25220]: evbug: blacklisted
Sep 8 01:02:10 ikn input.agent[25220]: evdev: already loaded
Sep 8 01:02:10 ikn input.agent[25251]: joydev: already loaded
I don't remember if the previus time the GConf also was shout down...
>
> >
> > I'm unable to find why this thing happened.
> >
> > Thank you for any help,
>
> Few other things:
>
> Can you try not using gpm? I had cases where gpm and X had a conflict
> and did not work well together. That's the reason gpm has the option -R
> (which is a bit more work to use, but you might want to try it).
>
My gpm runs with the current parameters of:
/usr/sbin/gpm -m /dev/input/mouse0 -t imps2 -Rms3
By default... I'd never touch the setting of it's deamon instructions...
> Can you do, both when it works well and when it's stuck
> od -tx1 /dev/input/mice
> move the mouse, click it, and see if you get any output?
I do reacive an Hex dump when implementing this command over the /dev/input/mice
afther the mouse was halted.
>
> Can you disable hotplug after all the modules are loaded?
It seems that modprob does not think it's a kernel module, and I can not find any
entry of it
in /etc/modules or in ps command.
>
> Do you have some other computer (or another OS on the same one) to
> try the mouse and make sure it's not a hardware problem?
I tryied this mouse over a WinXP OS and it never had this problem.
I also moved the mouse to PS/2 exit and still the same problem, so it does not seems
like a monitor problem.
Currently I'm using kernel 2.6.6 on Debian sid (I have some problem with newer
kernels, that I dont have the time to solve -> black screen output, ie no
real text is output)
Thank you very much for the help... (and I hope for more help on this matter ;) )
Ido
--
Victory belongs to the most persevering.
Napoleon Bonaparte
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
