Hi,

I have an AMD 64 bit laptop with an Logitech "Premium optical wheel mouse" (This is a really standard model). During the startup of Suse 9.3 *installed with my mouse plugged in" the light of the mouse is on and then turns of during the "starting devices" fase. When it's completely started my mouse doesn't work. I tried almost everything... In yast, sax2 etc. from the info I found on different forums. Here's some output:

geiser@LAPTOP:~> lsmod | grep hcd
ohci_hcd 22536 0
ehci_hcd 35592 0
usbcore 132976 5 usbhid,usbserial,ohci_hcd,ehci_hcd
geiser@LAPTOP:~> lsmod | grep usb
usbhid 47520 0
usbserial 34800 0
usbcore 132976 5 usbhid,usbserial,ohci_hcd,ehci_hcd
geiser@LAPTOP:~>

I think that if someone can help me it will solve many problems because a lot of people are having this problem. My computer is a HP Pavillion zv5000.

Tell me if you need more information.

Thanks in advance,
greetz Sven

go to Ctrl - Alt - F1 and login as root:
type init 3

type sax2

Add
1. /dev/input/mice for USBmouse
2. /dev/psaux for touch pad

Hi,

thanks for your suggestion!, but it didn't work...
I tried the different steps you suggested, also with different mouse models (auto->generic, USB->ps2 on USB). But It didn't work after a restart.
At the startup the light goes off during the "starting devices" fase (in text during coldplug or mandatory devices). The light stays off so it probably cannot work.
During "init 3" the light is also off.
It has worked in the past for one session but after that it had the same problem. I reinstalled the system with my mouse plugged as many people suggest but this is also no solutions...
I hope someone can help me!

Many Regards, Sven.

Hi,

I just started (using) Linux (SUSE 9.3) also and am also having problems getting a mouse to work. Seems like I have done most of the things that you have done, also to no avail. I posted a message and got one answer so far, which basically said to try selecting a generic mouse. Although YaST2 doesn't even list a "generic" mouse, I did try the USB Mouse selection (assuming it was a "generic" device, but that didn't work either. Inerestingly enough, each time I rotate the connection between the two mice, the system seems to recognize that a mouse has been connected, and in fact even provides a different ID for each one. At this VERY early point in my Linux career, I don't even know what diagnostic tools are available to track the problem ---

I have tried two mice. One a Microsoft optical and the other a Logiteck wheel mouse. I have run the install program (YaST2) more times than I can remember, but the mouse cursor never moves.

So ------ if you find a solution, please let me know, as will I

Oke Ed,

I will let you know how to solve this mysterious problem as soon as I know the answer.
I also tried the generic mouse. In yast2 the "generic" mouse is located under the "auto" mouse group but this one didn't solve my problem either.

Greetz Sven

ps. Please let me know if you find the answer.

Hi,

I found a solution for my system (HP Pavillion zv5000 serie).
I did a bios update.
- goto (www.hp.com)
- drivers en software update
- Give your system/product code (search for it in the bios)
- Also check your bios version in the bios
- Check and install the bios update (I did thid in windows, I don't know if there are other ways for this update beside windows.)
- Reboot the system and startup linux

After this the mouse light still went off but after a second the light was visible again and the mouse worked fine for me. I did recieve a power battery message after the update but know I'm planning a clean install on my system after the bios update and I hope that the power message will also dissapear. There's also information on the internet about this power battery warning after the bios update.

Many regards,

Sven Gijsen

Hello,

I had the similar problem. The /etc/X11/xorg.conf became bad for unknow reason.
I modified the file in the section "Section "InputDevice"" and replaced the line
Option "Device" "/dev/mouse"
by
Option "Device" "/dev/input/mice"

After a logout, login it's working again correctly.
--
free_ouyo