Mouse stopped working after upgrade to FC2 from FC1
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Mouse stopped working after upgrade to FC2 from FC1
I use a KVM switch between two machines. Everything worked fine before.
I recently did a clean install to Fedora Core 2 and my mouse doesn't work at all with my linux box.
The linksys KVM switch is working fine because the keyboard and monitor work on both computers but the mouse stopped working only on the Linux box.
The mouse is a logitech MX300 USB scrollmouse, connected to the KVM with a PS/2 adapter. Any help would be appreciated.
This is my xorg.conf file (I've tried the original /dev/input/mice and /dev/psaux) :
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "unix/:7100"
EndSection
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
#
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Yeah, well, I can't say I've had much progress on this situation, except by some weird twist it seems that the mouse is now working again.
So I haven't rebooted either of my computers since this worked because it's likely that rebooting will mess up this nice situation I've found myself in.
*A possibility for my case is that since I installed the proper driver for my windows box, that may have somehow made things smoother when the linux box booted up.
I've noticed that various orderings of booting my two boxes seems to result in different functionalities/disfunctions with the mouse.
The comment at the top of my conf file may be misleading, but is indeed my xorg.conf file and not XFree86.
But thanks a lot for the system-config-mouse keyboard shortcut. That will come in pretty handy.
Actually, the shortcut was really bad advice.
It just took me out of that X session and it got all confusing, and it eventually led to me rebooting the computer (because the KVM switch locked and wouldn't switch), which now refuses to recognize the frikkin mouse once more.
>:-| GRRRRRR...
It was once working, but is now dead. I really shouldn't have upgraded!#%
For several people (including me) who had mice stop working after upgrading FC1 to FC2, the fix was to disable USB Legacy support in the BIOS settings. My mouse is also on a usb->ps/2 adapter, but I don't have a KVM.
I tried disabling USB Legacy Support, and all that did was disable my keyboard until the kernel booted
I'm still not getting mouseage, then. Should I attempt a 2.6.6 compile and install? Would it be worth my time?
I have a Belkin KVM and have had RH8, RH9, FC1, Windows 95, 98, 2000 and XP PCs hooked up in different combinations of three at a time. Always worked with no problems if I identified my mouse as 2 button PS/2 on the Linux platforms.
I currently have two Linux platforms and an XP platform. I had XP, FC1 and RH8 running and all was well. I upgraded the RH8 box to FC2 and tried every trick I could think up editing the /etc/sysconfig/mouse file and /etc/X11/xorg.conf file. Never got the mouse to behave after switching away and returning on the FC2 box. Replaced FC2 with FC1 and the mouse is happy.
I don't know what the mouse port sees when a different platform is active. I feel strongly there needs to be a standard for all KVM switches and mouse drivers so this problem does not occur for any mouse configuration..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.