Okay, I realize that this is a really sketchy error report, so feel free to ignore me... on two separate installs of SuSE 5.3 (CD) I've had this problem occasionally. That is, I startx and it blacks out the screen, then returns to the console and says "Cannot open mouse: device or resource busy" ... here's the kicker: the cure for it is to run SaX, use the existing XF86Config, and then immediately do File->Exit. X loads fine after that. Anyone run into this before? - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Sat, 21 Nov 1998, Ryan Bagueros wrote:
Okay, I realize that this is a really sketchy error report, so feel free to ignore me... on two separate installs of SuSE 5.3 (CD) I've had this problem occasionally. That is, I startx and it blacks out the screen, then returns to the console and says "Cannot open mouse: device or resource busy" ... here's the kicker: the cure for it is to run SaX, use the existing XF86Config, and then immediately do File->Exit. X loads fine after that.
Anyone run into this before?
I had this problem when my mouse was not set up properly. Buy a ps\2 mouse or stop using gpm at boot time. # killall gpm --> should fix the problem. -alexm - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 11:30 22/11/98 -0600, you wrote:
problem occasionally. That is, I startx and it blacks out the screen, then returns to the console and says "Cannot open mouse: device or resource busy" ... here's the kicker: the cure for it is to run SaX, use the existing XF86Config, and then immediately do File->Exit. X loads fine after that. I had this problem when my mouse was not set up properly. Buy a ps\2 mouse or stop using gpm at boot time. # killall gpm --> should fix the problem.
I had the same problem, but I fixed it without buying a new mouse :-) All I did was edit /etc/XF86Config and changed the Device in the Pointer section to be /dev/mouse (it used to be /dev/cua0). ----- cut /etc/XF86Config ----- Section "Pointer" Protocol "Microsoft" Device "/dev/mouse" ----- cut /etc/XF86Config ----- As far as I can tell, it was because /dev/mouse (which is was what gpm used) is a symlink to /dev/ttyS0, so it's a different device from /dev/cua0.. I hope it helps. Best regards, -- Sotiris Tsimbonis <tsimbonis@rosehill-1.irc.gr> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Ryan Bagueros wrote:
Okay, I realize that this is a really sketchy error report, so feel free to ignore me... on two separate installs of SuSE 5.3 (CD) I've had this problem occasionally. That is, I startx and it blacks out the screen, then returns to the console and says "Cannot open mouse: device or resource busy" ... here's the kicker: the cure for it is to run SaX, use the existing XF86Config, and then immediately do File->Exit. X loads fine after that.
Anyone run into this before?
Yeah I have seen this before too, but thats because I was moving the mouse when X was booting up. My guess is it was trying to access the mouse or what ever it was doing and I was moving it so it couldn't get a lock on it and it crashed. -- From: Frank Hale Email: halef@bellatlantic.net Homepage: <A HREF="http://members.xoom.com/frankhale/main.html"><A HREF="http://members.xoom.com/frankhale/main.html</A">http://members.xoom.com/frankhale/main.html</A</A>> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (4)
-
alexm＠htr-60.tx.symbio.net -
halef＠bellatlantic.net -
rbaguer＠freenet.columbus.oh.us -
tsimbonis＠rosehill-1.irc.gr