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 prefer to start directly in X windows (initlevel 4), but my mouse doesn't work then because the gpm server is not started. There are also other scripts, deamons not started which are started in runlevel 3 (e.g. syslogd, rc.hotplug). Instead of copying the line that starts the mouse server I would like know if there is a more elegant solution to solve my mouse problem and could someone clariy the difference between both runlevels if X windows is used (usually).
Distribution: BeOS, BSD, Caldera, CTOS, Debian, LFS, Mac, Mandrake, Red Hat, Slackware, Solaris, SuSE
Posts: 1,761
Rep:
If you change the default run level to 4 in /etc/inittab, the run level 3 scripts are still executed. Run level 3 is console sessions (no GUI), but you can start a GUI session buy typing "startx" at the command line. Run level 4 takes you right into GUI.
The /etc/rc.d/rc.gpm mouse server is used during console sessions (great for copy and paste between virtual consoles), The X server handles mouse movement during GUI sessions. Since your mouse is not functional during GUI sessions, your xorg.conf may need to be corrected.
When I start X in runlevel 3 (by startx), my mouse works without problem. Nothing seems to be the problem in my xorg.conf, the mouse section is properly set, but when I directly start in runlevel 4 my mouse stays fixed on the screen.
At the moment I can only access my Linux section by booting from the cd-rom. When I use the standard boot kernel, I get a series of '9A' characters on the screen. I don't know yet whether there is a connection between these two problems.
but my mouse doesn't work then because the gpm server is not started.
gpm is for using a mouse within a console, and is not related to the mouse in X.
Quote:
There are also other scripts, daemons not started which are started in runlevel 3 (e.g. syslogd, rc.hotplug).
This should not be the case, but is possible if you are starting runlevel 4 in an obscure manner.
Quote:
Instead of copying the line that starts the mouse server I would like know if there is a more elegant solution to solve my mouse problem and could someone clarify the difference between both runlevels if X windows is used (usually).
I changed in inittab '3' in '4' in the default runlevel (as usual), nothing obscure I should think. I will have a look at your manual and build a new kernel with 2.6 as well (as soon as I manage to get a decent xterm in kde or other windowmanager, I sadly miss Gnome). Thanks for the links.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.