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 have downloaded Slackware 13 and installed it on Virtual Box.
When I was running it I noticed that gpm is working but when I started X I couldn't even move my mouse.
Then I installed Slackware 13 on my Compaq laptop both usb mouse and touchpad worked with gpm but I had the same problem in X.
I have used Ubuntu, OpenSUSE, Fedora, Mandriva, and even Slackware 12.2 before but never seen this problem.
Did you by any chance install the 32bit multilib packages that I created, and then ran the slackpkg command after that?
There is a bug in my multilib setup (which I am fixing right now) so that if you run slackpkg after installing my set of multilib packages and then tell slackpkg to install the *.new files that it finds, you will end up with empty /etc/rc.d/rc.hald , /etc/rc.d/rc.messagebus and /etc/rc.d/rc.mysqld scripts.
The result of not starting hal and dbus when the computer boots will perhaps not be immediately obvious, but if you start X, you will have no mouse and no keyboard.
The fix is to reinstall the hal, dbus and mysqld packages:
I'm seeing an issue with KVM switches and KDE where the keyboard works fine and the mouse won't, but I don't have enough info to pin it on any aspect of the distribution yet. It could be gpm or just about anything related to the switches. I'll keep poking around to develop better info.
I'm seeing an issue with KVM switches and KDE where the keyboard works fine and the mouse won't, but I don't have enough info to pin it on any aspect of the distribution yet. It could be gpm or just about anything related to the switches. I'll keep poking around to develop better info.
I suggest creating a new thread instead of hi-jacking this one.
Did you by any chance install the 32bit multilib packages that I created, and then ran the slackpkg command after that?
There is a bug in my multilib setup (which I am fixing right now) so that if you run slackpkg after installing my set of multilib packages and then tell slackpkg to install the *.new files that it finds, you will end up with empty /etc/rc.d/rc.hald , /etc/rc.d/rc.messagebus and /etc/rc.d/rc.mysqld scripts.
The result of not starting hal and dbus when the computer boots will perhaps not be immediately obvious, but if you start X, you will have no mouse and no keyboard.
The fix is to reinstall the hal, dbus and mysqld packages:
Well ISee you edited your previous post from "64bit" to "32bit". IN the case of 32bit Slackware, my answer does not apply of course.
Unless you provide troubleshooting information (log excerpts etc...) I can not start imagining what is wrong in your virtual box.
Well ISee you edited your previous post from "64bit" to "32bit". IN the case of 32bit Slackware, my answer does not apply of course.
Unless you provide troubleshooting information (log excerpts etc...) I can not start imagining what is wrong in your virtual box.
Eric
Can you explain more about "log excerpts" and where can I get them?
A "log excerpt" is the term for the relevant parts of your log file(s) that show indication of what is going on (errors, warnings, diagnostics).
As for where to get them... on your local machine of course. Look in /var/log and see what you can find there. Run "dmesg" and inspect the output. Copy the relevant bits into this forum (use [ code ] [ /code ] tags around your log lines to make it easier for other people to read).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.