[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mouse & keyboard probs under X [WAS: usb mouse problems: etch/gnome/metacity]



On Thu, 2008-01-03 at 13:05 +0000, michael wrote:
> On Thu, 2008-01-03 at 12:41 +0000, michael wrote:
> > On Wed, 2008-01-02 at 21:36 -0600, Adam Porter wrote:
> > > cs wrote:
> > > 
> > > > actually after using KDE for an hour today, the keyboard froze too...
> > > > playing with the control centre somehow reset it such that keyboard
> > > > started accepting USB input again
> > > > 
> > > > it seems (under Gnome) openning many more application windows (that have
> > > > not been previously openned?) somehow resets it so keyboard started
> > > > accepting input again
> > > > 
> > > > any ideas??! or ways to narrow this down?
> > > 
> > > grep through your /var/logs for USB-related messages.  Maybe something is
> > > going on.  I have a PS/2 keyboard but my USB mouse is fine.  Once in a
> > > while my USB hard disk will bork itself and, because of LVM, I'll have to
> > > reboot to fix it.  Sometimes my SanDisk USB memory card reader will mess up
> > > too.  I often wonder if it's something to do with the USB controllers on my
> > > motherboard (which is pretty old).
> > 
> > I'd already checked and there was nothing USB related in syslog,
> > Xorg.*.log etc.
> > 
> > However, commenting out this line in xorg.conf:
> > 	
> >         Option         "Protocol" "ImPS/2"
> > 
> > seems to have helped (so far!)
> > 
> > > If that doesn't turn anything up, I'd suggest trying a different USB
> > > keyboard, and a PS/2 one if possible.
> > > 
> > > If that doesn't help, I'd suggest seeing a psychiatrist; perhaps your
> > > original theory of your slowly going mad is correct.  ;)
> > 
> > ;)
> > 
> > I'll post an update to the list once I'm sure the above line makes a
> > diff or not 
> 
> Okay, I spoke too soon :(
> The mouse just ''froze'' on me again (as in I could move it but clicking
> did nothing) - had to ALT-TAB (to 'nothing' then again to get current
> apps)...
> 
> 

adding boot kernel option 'noapic' (as suggested on some fora) doesn't
help


Reply to: