Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I have installed SUSE SLES11.0 and when it boots up, the keyboard works, but the mouse does not. I am connected via a KVM, and the pointer does not move when I move the mouse.
I have run:
> init 3
> cat /dev/input/mice
> sax2 (after I got the mouse working)
But after the reboot, it no longer works within the gui.
I have already searched for hours via google and tried many things to no avail. Any help would be appreciated.
I'd say it looks like sax2 broke the mouse, since it was working before you ran it. I don't have many good things to say about sax2, myself.
1) Apply service pack 1, because SLES 11.0 is out of support. That might fix your problem.
2) If not, give the Yast2 mouse module a try.
3) Finally, you could try modifying /etc/X11/xorg.conf manually, though this is not typically a good exercise for people who don't know what they're doing. What might prove more productive, though, is to compare the xorg.conf file that existed before sax2 broke it (it should be in the same directory as xorg.conf~) to the current one.
4) When all else fails, you have an enterprise Linux for a reason, so contact support.
I unplugged and re-inserted the mouse into the USB port, and the pointer on the screen started working. I've since read that I should have seen garbage characters being printed to the screen, which I did not. So I'm wondering if I ever really had it working prior to running sax2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.