This is getting annoying... Setup is SuSE 9.3, and I have a USB mouse. The mouse has been working perfectly... up until recently. Now when I start up SuSE, the mouse doesn't work. If I do an Alt-F2 and start up YaST, then go to Hardware, Mouse Model... and just start up the Mouse Model part of YaST, the mouse starts working again... I dont' save anything or change anything... I've checked my xorg.conf file and nothing has changed there since the initial install/setup... it looks like this: ------------------------------------- Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "ButtonNumber" "7" Option "Buttons" "5" Option "Device" "/dev/mouse" Option "Name" "Logitech USB Trackball" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection ------------------------------------------ So... anyone have any suggestions why the mouse stoped being initialized on a boot? Or why simpy starting the Mouse Model part of YaST and exiting again without saving anything seems to "wake-up" the mouse? C.
Op zondag 19 juni 2005 20:09, schreef Clayton:
This is getting annoying... Setup is SuSE 9.3, and I have a USB mouse. The mouse has been working perfectly... up until recently. Now when I start up SuSE, the mouse doesn't work. If I do an Alt-F2 and start up YaST, then go to Hardware, Mouse Model... and just start up the Mouse Model part of YaST, the mouse starts working again... I dont' save anything or change anything...
I've checked my xorg.conf file and nothing has changed there since the initial install/setup... it looks like this: ------------------------------------- Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "ButtonNumber" "7" Option "Buttons" "5" Option "Device" "/dev/mouse" Option "Name" "Logitech USB Trackball" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection ------------------------------------------
So... anyone have any suggestions why the mouse stoped being initialized on a boot? Or why simpy starting the Mouse Model part of YaST and exiting again without saving anything seems to "wake-up" the mouse?
I encounter something similar... with a usb optical mouse. This has been investigated by suse, but sofar no results :( Perhaps you can view the bug report: https://bugzilla.novell.com/show_bug.cgi?id=72371 Might be interesting to provide: hwinfo --mouse -- Richard Bos Without a home the journey is endless
Clayton (smaug42@gmail.com) wrote something I wish to comment : (news:<e2996788050619110958d5373d@mail.gmail.com> posted on 19-juin-05 19:09:37)
So... anyone have any suggestions why the mouse stoped being initialized on a boot? Or why simpy starting the Mouse Model part of YaST and exiting again without saving anything seems to "wake-up" the mouse?
Check in /var/log/Xorg.0.log if there is any error (EE) with the mouse. AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN PRIVATE MESSAGE----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. IAMVvSxtBVyaHFUdSS0zEAOyyFMt5RO3ySFIaFAbavzD5xYVFznnPOURIIzFUcHpFqhTlDpk vnjaDvptIMHOBlDppJflIOLqMIDzHtAOdRyMVSOR1llGyFllLVVqvtpJECttMERpIOpWvz1W 5qtWJEEv0yJxKxLTV6qVOVOF5tGroMNJOHVzHItHHjHUKRyOvEH2tDRbVcGIvVuyWM3PEt== -----END PRIVATE MESSAGE----- Blessed are the pessimists;they make backups!
Clayton wrote:
This is getting annoying... Setup is SuSE 9.3, and I have a USB mouse. The mouse has been working perfectly... up until recently. Now when I start up SuSE, the mouse doesn't work. If I do an Alt-F2 and start up YaST, then go to Hardware, Mouse Model... and just start up the Mouse Model part of YaST, the mouse starts working again... I dont' save anything or change anything...
I've checked my xorg.conf file and nothing has changed there since the initial install/setup... it looks like this: ------------------------------------- Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "ButtonNumber" "7" Option "Buttons" "5" Option "Device" "/dev/mouse" Option "Name" "Logitech USB Trackball" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection ------------------------------------------
So... anyone have any suggestions why the mouse stoped being initialized on a boot? Or why simpy starting the Mouse Model part of YaST and exiting again without saving anything seems to "wake-up" the mouse?
C.
Hi Sorry i dont have a solution to your problem but i had the same problem with my usb mouse so i switch to ps2 now all is well, regards Mal
Op zondag 19 juni 2005 21:24, schreef malcolm:
but i had the same problem with my usb mouse so i switch to ps2 now all is well,
I switch to another usb mouse (as I don't have a ps/2 connector, I have to). And that worked out well as well. I think it has something to do with logitech... Did you have a logitech mouse as well? -- Richard Bos Without a home the journey is endless
On 6/19/05, malcolm <frosty@malf.freeserve.co.uk> wrote:
Clayton wrote:
This is getting annoying... Setup is SuSE 9.3, and I have a USB mouse. The mouse has been working perfectly... up until recently. Now when I start up SuSE, the mouse doesn't work. If I do an Alt-F2 and start up YaST, then go to Hardware, Mouse Model... and just start up the Mouse Model part of YaST, the mouse starts working again... I dont' save anything or change anything...
I've checked my xorg.conf file and nothing has changed there since the initial install/setup... it looks like this: ------------------------------------- Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "ButtonNumber" "7" Option "Buttons" "5" Option "Device" "/dev/mouse" Option "Name" "Logitech USB Trackball" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection ------------------------------------------
So... anyone have any suggestions why the mouse stoped being initialized on a boot? Or why simpy starting the Mouse Model part of YaST and exiting again without saving anything seems to "wake-up" the mouse?
A couple off-list replies got me started down the right road and I've fixed the problem. For some reason (in my endless tinkering) the device setting in my xorg.conf for the mouse got changed from /dev/input/mice to /dev/mouse. When I was starting up YaST and the Mouse Model module, it was re-querying the mouse, but on the right dev location. I'm not sure why it knew the right dev location.. but... all I had to do was edit my xorg file and point it to /dev/input/mice and now it works exactly like it is supposed to. :-S C.
participants (4)
-
AmigaPhil＠ping.be -
Clayton -
malcolm -
Richard Bos