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.
well that looks ok
(assuming you also have a section in XF86Config called "ServerLayout" that calls these two input devices (maybe at the end of the file?))
have you had a look at XFree86.0.log?
(less /var/log/XFree86.0.log)
that might give us a clue - especially any lines flagged as errors
(grep EE /var/log/XFree86.o.log)
i have a serverlayout at the end of my file, no errors, and IMPS/2 does not work...
but i've found another thing: my keyboard blanks out the second i try to use my mouse... have you got that too papa0822? do you perhaps have a compaq, coz i heared about special problems with compaq
ava, no compaq, home built job here, mouse and keyboard are cordless set Micro Innovations Office kb&mouse, both work off the same dual line transeiver connected to both ps/2 ports.
Originally posted by boreo Does your mouse and keyboard work under mandrake?.. If they do just copy your xf86config setup for the mouse, and add them to your slack xf86config. It should work fine if you do that.... I do not use mandrake but my xf86config is located at /etc/X11/xf86config.. In both Slack and Redhat... Before you change anything make sure you do a backup of your already created xf86config file. Good luck.
I tried copying my XF86Config from my Red Hat partition to compare, but same values for mouse in Slack don't work.
Alas Success of a sort. After trashing my MBR last night and reinstalling mandrake9.1, I now have a linux OS running, It just isn't slack. Gonna work on that next, but first I will get used to using this one.
To all of you out there who tried to hepl me, THANK YOU, But rmrember I am very new to this and will be bugging you for more help in the future.
As I posted this morning, I now have mdk9.1 up and running, however it was a byt__ to get going. I reinstalled everything, then when I set up lilo, I put it into the MBR of my 1st drive. Only thing it did was stop me from booting anything. Ran fdisk/mbr, copied my windoze boot loader back into it, tried to boot from the boot floppy,,, no go, booted from a slackware boot floppy just changed the mnt root to my mandrake partition, it booted with a lot of errors, with the mouse and keyboard working, so I ran xf86config, reste my settings and saved it,,,,, to the wrong dirrectory, then finished booting up. It worked but with alot of errors. Gave up, went to bed. This morning when i tornrd it on, I put the mdk boot floppy in, it booted( don't know why) it worked and so does mandrake now.. go figure.
You look like your having a bit of problems eh... Your mouse config is exactly the same as mines, and I'm running Slack.. So if your mouse and keyboard are working fine with MDK9, they should work fine with your slack if you edit the xf86config and make your mouse config like the one on mdk.. Well.. Good luck..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.