SlackwareThis Forum is for the discussion of Slackware Linux.
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'm going to assume it is. You cannot run Mac OSX applications in linux. Period.
To help with your problem.
It looks like you set slack to boot into init 4 by default, but did not properly configure X11. Also, GPM is not starting up. To remedy this, boot into single user mode. (At lilo, pick your kernel and then type "single" after the kernel option)
Then from there login as "root"
then type
cd /etc/rc.d
chmod -x rc.gpm
then type xorgconfig and answer all the questions about your graphics hardware.
thanks, currently rebooting with CHMOD changes, hoping that i only have to do that. I think i have a pretty good memory on my graphics card stuff, but not sure.
The monitor clicking is a sign of a bad /etc/X11/xorg.conf
Post your /etc/X11/xorg.conf and then say what Videocard, monitor, and if your Mouse is PS/2 or USB. Also, are there any other errors if you wait about 20 seconds after the screen starts clicking?
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0" after 0 requests (0 known processes) with 0 events remaining.
Thats what it's told me after commanding startx.
As I take a look at the log, i get
Code:
(WW) No core pointer registered
(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
No core pointer
Fatal server error:
failed to initialize core devices
Well, I tried, and slackware is still telling me that the mouse resource is busy. I just don't get it.
Another thing that I've just remembered is that this always seems to happen after I get my soundcard working. I get it working, get done with it, shut her down. Then the next morning I want to get on it, can't because of this.
IT REALLY GETS ANNOYING. I hate the fact that it's like I have a choice, will I take sound or graphics.
MORE EDIT: It's also a PS2 mouse.
FIXED: I fixed it by editing /etc/rc.d/rc.M so that the mouse goes first before ALSA. Seeming ALSA wants to mandate, and everything still works.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.