10.1 after install, mouse not working

pcdebb · 03-04-2005, 11:35 AM

after painstakingly trying to get linux on this machine, I went thru an easy install of mandrake 10.1. On first reboot, the mouse isnt being recognized. I've tried two regular mice (a generic, a logitech) and even a laser mouse (which is usb), and nothing works. I don't know the keyboard shortcuts to get around so I'm trying. Is there some config I need to run to get the mouse to be recognized by mandrake?

pcdebb · 03-04-2005, 11:56 AM

AHA! I'm better than I thought. I had to chose a different "generic" wheel mouse, now i'm happy again.

opjose · 03-04-2005, 03:36 PM

You can also run mouseconfig and try different choices until you get what you want working.

DoctorDread · 03-08-2005, 05:30 PM

OK, I am having the same issue but with a different result. Once the system boots up and I log in I have to use the keyboard to get to system config and manually set the mouse to either generic PS2/USB or standard PS2. Once I set it up everything works fine and I have no issue with the mouse. So everytime I boot up I have to do the process all over again. I can not get the driver to stay with the mouse. I even went so far as to install 10.1 3 times and all with the same result. What is happening?

opjose · 03-08-2005, 05:34 PM

What is happening is that one of the startup scripts is reading the mouse configuration from a file someplace and reconfiguring the system.

Offhand I don't remember which files are involved, but you may want to reboot, drop to a text console, (CTRL-ALT-F1) then check the files in /etc/sysconfig and /etc/X11

I'll bet that either the mouse type is incorrect or that the port/device which the mouse is connected to is incorrectly defined somewhere.

e.g. you have a PS2 type mouse but the system reconfigures it at bootup to USB.

TastyWheat · 03-16-2005, 07:31 PM

I'm having the same trouble as DoctorDread. I checked my configuration before loading KDE and everything was setup fine. As soon as I booted into KDE the config files (/etc/sysconfig/mouse;/etc/X11/XF86Config) were changed to something different. So it looks like something related to KDE is trying to auto-configure the mouse on startup and doing a rather crappy job.

It might have something to do with harddrake. I didn't see any other kind of service or tool that I thought would affect the mouse settings. The only thing I can really do with harddrake is turn it off.

opjose · 03-16-2005, 08:41 PM

Most of this info is stored in /etc/sysconfig

You may want to grep the directory tree to search for refernces to mice.

Also if you EVER selected profiles, Mandrake will keep a configuration profile for your initial setup which it will attempt to restore upon every reboot.

Profiles are like Windows hardware profiles....

e.g. you can have one configuration for a docked machine and another for an undocked one, etc.

TastyWheat · 03-17-2005, 01:52 AM

FIXED IT!!!

Mousedrake kept using symbolic links for the device instead of pointing to the actual device. So my '/etc/sysconfig/mouse' file was pointing to a device that didn't exist. After running mousedrake in KDE it created the symbolic link and the mouse worked. I just changed the device to point to '/dev/mouse0' which should always be there. I think '/dev/psaux' would work as well.

opjose · 03-17-2005, 09:45 AM

Great!

DoctorDread · 04-01-2005, 12:04 PM

It is good to hear you got it fixed. I have been dealing with having to mount the mouse everytime I boot up. I plan on fixing this tonight, can you give me some idea where you change the entry. I am a bit new so bear with me. Was it changed in the sysconfig or the XF86config file? If you could post an example that would be great.

Thanks,

TastyWheat · 04-01-2005, 04:27 PM

This is how my '/etc/syconfig/mouse' file reads:

Code:

MOUSETYPE=ps/2
XMOUSETYPE=ExplorerPS/2
FULLNAME='"Universal|Any PS/2 & USB mice"'
XEMU3=no
WHEEL=yes
device=mouse0

And my '/etc/X11/XF86Config' file:

Code:

Section "InputDevice"
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "ExplorerPS/2"
    Option "Device" "/dev/mouse0"
    Option "ZAxisMapping" "6 7"
EndSection

I think the first file is more critical though. Anyway, the easiest way to fix the mouse for good is to configure the mouse like normal using mousedrake or harddrake. Then go to each of those files and change the device to either 'mouse0' or 'psaux'. The long and the short is that those devices always exist, whereas the one's automatically set are removed on reboot.