[SOLVED] Mouse is not working in X server (kdrive xfbdev)
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Hey everybody
I have been working on getting my very own Linux distro up and running. I have a few questions, but I will separate them into separate post since they have nothing really to do with each other.
Right now I have a bootable linux system, it will boot on real hardware, but for development purposes I am using qemu. Once the system boots, it opens a getty on /dev/tty0. That works great, but I want graphics. So I have installed an Xserver, but I wanted to keep it small so I went with Kdrive Xfbdev, which needs a framebuffer device at /dev/fb0. I have it working with Linux 2.6.34, on boot I had to add "vga=792" to the kernel command line along with enabling vesafb in the kernel .config. That worked and I could get X running.
However, just because its running doesn't mean all is well. The mouse refuses to work. Now, the reason that this won't work has me stumped. I know that I have compiled the proper drivers for the mouse into my kernel, and I can see that they are working by issuing the command "sudo cat /dev/input/mouse0". I read somewhere that kdrive looks for a mouse at /dev/mouse, so I created a symlink at /dev/mouse pointing to /dev/input/mouse0, but still the mouse will not work in X.
Any ideas?
Hey everybody
I have been working on getting my very own Linux distro up and running. I have a few questions, but I will separate them into separate post since they have nothing really to do with each other.
Right now I have a bootable linux system, it will boot on real hardware, but for development purposes I am using qemu. Once the system boots, it opens a getty on /dev/tty0. That works great, but I want graphics. So I have installed an Xserver, but I wanted to keep it small so I went with Kdrive Xfbdev, which needs a framebuffer device at /dev/fb0. I have it working with Linux 2.6.34, on boot I had to add "vga=792" to the kernel command line along with enabling vesafb in the kernel .config. That worked and I could get X running.
However, just because its running doesn't mean all is well. The mouse refuses to work. Now, the reason that this won't work has me stumped. I know that I have compiled the proper drivers for the mouse into my kernel, and I can see that they are working by issuing the command "sudo cat /dev/input/mouse0". I read somewhere that kdrive looks for a mouse at /dev/mouse, so I created a symlink at /dev/mouse pointing to /dev/input/mouse0, but still the mouse will not work in X.
Any ideas?
I managed to solve this problem on my own. I needed to explicitly tell it where my mouse was: Xfbdev -mouse mouse,/dev/mice,5
However, now my keyboard won't work. I tried adding -keybd keyboard, like I saw on one website, and that seems to have made the Xserver detect the keypresses, but it can't seem to process them correctly. I don't know what to do.
I managed to solve this problem on my own. I needed to explicitly tell it where my mouse was: Xfbdev -mouse mouse,/dev/mice,5
However, now my keyboard won't work. I tried adding -keybd keyboard, like I saw on one website, and that seems to have made the Xserver detect the keypresses, but it can't seem to process them correctly. I don't know what to do.
Ok, nevermind. I got it working with a different keyboard driver. I'm happy now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.