Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
Has anyone else been having this problem. My mouse works just fine at first. then after, lets say 15 minutes it stops responding. I am using a microsoft intella-whatever usb mouse pluged into the usb hub on my micosoft internet keyboard pro. I am using the right mouse drivers in redhat 9. I dual boot in xp and it works fine in XP. anyhow if you have found any leads to simular problems let me know.
If you have recently updated your RH9 Kernel to .9 that is the problem with the locking-up, it shouldn't just be your mouse though, your whole system should freeze, num-lock/scroll-lock lights on keyboard normally blink also.
Revert back to .8 kernel (the one RH9 shipped with) until they release a new kernel.....
at least I think that is the problem, but hey give it shot, got nothing to loose.....
I checked that out. it happens in both kernels. I can get it to happen almost anytime I try to use the hardware browser It seems the system become unresponsive for a second and it somehow loses the mouse for good. Sometimes the whole system become unresponsive and sometimes I can get it to restart before it all stops and other times during the kill process it stalls. it could have to do with my usb keyboard hub (non powered) but I don't see really why but I'll play around with it. if anyone has anymore information let me know
thanks
I had my share of lockups considering a mouse in X.
Luckily i could ssh into that machine. Turned out to
be the gpm console mouse service. After killing it
the problem was solved.
gpm + logitech wireless mouse + Xfree 4.2 can
cause trouble. My mouse was a ps2 mouse though,
not usb, but maybe it's the solution for this also.
That sounds like it could be a logical reason, wierd one, but logica, I'm as well as the person above a newbee, you could you explain how to go about doing that. My machine locks up all the time right in the middle of things and the mouse is the first thing to freezed then the sound and etc., etc..... drives me crazy.
although it don't do it as much with .8 kernel (original) .... thanks
Atlantis if you are in X, fire up a console like xterm
or konsole
type
ps aux (enter) ( ps aux|grep -i gpm shows only
the line where gpm service is; first no is PID no)
look at the PID no that is in the line whith the gpm service
type
kill -9 PIDno (enter)
after that see if your machine behaves normal.
If so; then you need to switch it off, using the
redhats runlevel editor (i can't remember its name
cause i am at work and i use mandrake) otherwise the
gpm is automaticly started at boot.
If not then it's something else
But maybe your lock ups are not mouse related at all
so try booting into runlevel 3 and see if it stays stable
then it maybe X related
at boot time bypass lilo using esc or ctrl x
type linux 3 (or use tab key to see which labelname to
use instead of linux) and enter
or check memory (use memtest) or check power supply
I also boot suspicious machines whith knoppix 3.2
thats a bootable linux cdrom that runs entirely in RAM
and see if the faults consists.
I killed the process but couldn't do it from terminal/xterm said the PID no# didn't exist, so I used SystemTools-System Monitor in Gnome and killed the proccess (even though it took a few times, system monitor kept hanging) finally the process was killed.
My Question is, What is GPM and why would I be having problems with it. its a fresh install and only 2 partitions used / and SWAP, 1 account and I never touch the root account. I mean is it just my PC or did I mess something up. I also have Mandrake 9.1 and I'm seriously thinking about switching back to it, too much hassle for RH9 for personal use, as a workstation it has more usable features.
However, Thanks for your reply so far so good, no crashes yet. But I still need to figure out how to disabled that perminantly during boot.
gpm;
gpm - a cut and paste utility and mouse server for virtual
consoles
according to the man page (man gpm) it's meant to be
for real virtual consoles so in X you won't need it.
The runlevel editor in RH 7.3 is named; redhat-config-services
edit runlevel 5 (i guess in RH 9 it still has the same name)
and i forgot to mention in the previous postings that you should be root to do this
Still i have no idea why root doesn't encounter the lock-ups
maybe add another user and see if that one runs in to
trouble.
I've narrow the problem down to the /etc/fstab file. there is something that is causing extra output from one of my devices (cdroms) if I disable the first or second cdrom, the OS works great, soon as I re-enable both of them the system crashes again after a few minutes to an hour or so. Not sure why and can't find no answers, I have just enabled my cdrw (cdrom1) and diabled my dvd(cdrom) I can only use one which kinda sucks, but its the only way the OS will stay stable. and not lock up.
So you have found a kind of workaround, that is good
But not really satisfying i guess.
Maybe this is kernel related indeed, try this at boot
bypass lilo (esc or ctrl x)
type ;
linux noapic acpi=off
(try tab key to get the right labelname for linux)
if the machine stays stable after doing this then
be root
edit your lilo.conf (lives in /etc)
the append="blabla bla" needs to be modifyied
put noapic acpi=off between the " "
save it
type lilo (enter)
Good luck
ah and another thing that happened once to me;
during secondstage install of freebsd it hang,
turned out that i had to change a bios setting
like; detecting drive was set to auto
and i switched it to cdrom or the other way around
I'm also having this problem after upgrading to RH9 yesterday from RH7.3
When the mouse locks, if I switch to another virtual console (CTRL-ALT-F1) and then back (CTRL-ALT-F7), the mouse is released.
I'm not running gpm.
The only message I can see is in /var/log/Xfree.0.log
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) Open APM successful
(II) DevInputMice: ps2EnableDataReporting: succeeded
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) Open APM successful
(II) DevInputMice: ps2EnableDataReporting: succeeded
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) Open APM successful
(II) DevInputMice: ps2EnableDataReporting: succeeded
(II) Mouse0: ps2EnableDataReporting: succeeded
I've stopped apmd but it still happens.
If this suggests something to anyone, Id like to know!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.