troubleshooting /dev/mouse link in a Slack14 VM guest
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.
troubleshooting /dev/mouse link in a Slack14 VM guest
My mouse wheel doesn’t work in my Slackware guest VM. This is prolly because I selected the incorrect input device when installing. My, times have changed: /etc/X11/xorg.conf no longer exists and neither does xorgconfig. As root and with the xserver deactivated, ‘xorgsetup’ segfaults. The closest thing to an /etc/X11/xorg.conf is /etc/X11/xorg.conf-vesa. The only instance of Mouse in that file is:
Code:
InputDevice “Mouse1” “CorePointer”
I hesitated to try appending
Code:
Option "ZAxisMapping" "4 5"
because it made me feel stupid. My intuition was right b/c that didn’t help at all. How do I change my /dev/mouse link in Slackware14?
Last edited by Drone4four; 09-26-2013 at 03:55 PM.
Reason: grammar fix in second sentence + added VM to title
Can you post the contents of /var/log/Xorg.0.log ? that should show us what driver its using. It may be that you will need to create an xorg.conf but we should start out with knowing what X is auto-detecting.
When you run xorgsetup, check your /root folder for a xorg.conf.new file.
X has been having trouble recently with proper detection of multiple monitor displays on video cards actually NOT being there. The cause of X's internal configuration being messed up is an upstream issue that may need reporting.
Just edit the xorg.conf.new file as needed for DRI, and remove the lines for the extra displays, save, and copy it to /etc/X11 and it should work now.
I tried commenting quite a few different combinations of lines out of the xorg.conf.new in /root. I obviously copied that file to /etc/X11/xorg.conf.
I tried commenting out the second instance of Screen under the ServerLayout section and the second "Screen" section. The file was initially set to load two similar modules: dri and dri2. I tried commenting out dri2 (but leaving dri) and that still didn't fix the X server. Likewise, I commented out dri, but re-enabled dri2. Still no dice.
It's worth noting that both Device sections were commented out by default.
I can't seem get X to start with the new config. I'm not familiar enough with DRI to figure out what parameters are essential and what are not.
I would really appreciate it if someone could advise me on this.
Here are the contents of the xorg.conf that I am experimenting with:
Comment out only the extra monitors. DRI2 and DRI are the driver handlers, and DRI2 is the handler for the Gallium API under Mesa. Leave those uncommented along with GLX.
Here's a general usage revision you might need:
Note: I have added the fbdev driver detection, but this can be safely ignored if you don't have the xf86-driver-fbdev package installed from /extras. It's more or less there for legacy purposes.
You can also swap out the modesetting driver for any other video card driver needed such as radeon, nouveau, or intel should you have those cards.
Maybe I'm confused. What are you trying to solve? Your initial post suggests to me that you were able to start X in the VM though you couldn't get the mouse wheel working.
If it was just the mouse wheel, there's no need to mess about with DRI, DRI2, monitors, graphics drivers or other display related stuff. You probably don't need a full xorg.conf, you should only need to override the mouse configuration, something like what jtsn suggested but obviously we need to figure out what should really go in that file.
I don't know if it'll help, but perhaps you could try using xev and scrolling your mouse wheel in the window. Look for what button events occur (if any) when you scroll up and down. For example, I get ButtonPress and ButtonRelease events for button 4 when I scroll up and button 5 when I scroll down.
Virtual Machines, as he's pointing out, often have issues with peripheral devices being detected, especially VirtualBox as of late. I've been noticing that VirtualBox's mouse is somewhat glitchy and doesn't often register properly and the vboxvideo driver seems to not want to work with X11 in most regards simply not working at all and crashing.
In regards to this, a full xorg.conf might not be needed, but it's a good place to start the process of finding out what went wrong by having a master xorg.conf file to work from. As his Xorg.log.0 shows, basically, vboxvideo failed to load completely which caused vesa to fail too, and without fbdev to fallback, there was no available driver, and since X11's configuration mode has been problematic, xorgsetup fails to work properly resulting in the fact he couldn't get his mouse working also.
xorg.conf might be legacy, but it damn well works.
In fact VirtualBox has been rather problematic as of late with the Additions drivers being very glitchy and buggy, not just with GNU/Linux, but FreeBSD, and Windows as well.
In regards to this, a full xorg.conf might not be needed, but it's a good place to start the process of finding out what went wrong by having a master xorg.conf file to work from.
I do not agree. Why introduce more variables to debug? xorg.conf files are useful if you need to override autodetect settings. It should be kept minimal, you should only fix what doesn't work. Drone4four cannot even start X with the new config, so having a full xorg.conf has instead introduced problems.
He can't start xorg due to the fact he has a bad video driver.
Instead of condemning a full configuration file, you need to understand why it's useful...
...to present an xorg.conf DEFAULTS setup which you know always works. He needs defaults to work from to see what the standard defaults are then re-customize back to his personalized specifications.
For him the "modesetting" driver might not be wise to use, so he can switch it with the "vesa" driver.
Just becasue a script is old doesn't devalidate it's usage and usefulness. Automation often has it's problems and just because the automated design is there, doesn't walways mean it's always the best choice.
He can't start xorg due to the fact he has a bad video driver.
Initial post states: Mouse wheel not working, which implies X was running and there was a working video driver.
Later post states: Cannot get X to run.
Changes made between X running and not running: xorg.conf
Cause of X failure: bad xorg.conf configuration
Quote:
Originally Posted by ReaperX7
Instead of condemning a full configuration file, you need to understand why it's useful...
...to present an xorg.conf DEFAULTS setup which you know always works. He needs defaults to work from to see what the standard defaults are then re-customize back to his personalized specifications.
And I will repeat, it's now not working at all and has introduced problems?
I'm just saying, I am quite error prone but I (usually) read posts carefully and do do my research.
Please read the man page for Xorg(1) (xorgsetup executes this to generate an xorg.conf and then modifies that), in particular "-configure" in the OPTIONS section and the full CONFIGURATION section, and understand why autoconfiguration and minimal overrides for what isn't correct (i.e. wrong keyboard layout, video driver) is usually better than using a full xorg.conf. Essentially, safe fallbacks. If you provide a full xorg.conf, X will assume you know best. If you're wrong, well, it won't start.
Also, for a VM, why would you suggest that Drone4four use the nvidia, radeon or intel driver? It doesn't actually make sense.
I shall wait for the OP or others to respond before making further posts here.
The new /etc/X11/xorg.conf suggested by ReaperX7 now starts X. It's also worth noting that I am using vesa as the driver, and not nouveau. However my initial problem with the lack of scroll wheel functionality persists. Even with
I don't know if it'll help, but perhaps you could try using xev and scrolling your mouse wheel in the window. Look for what button events occur (if any) when you scroll up and down. For example, I get ButtonPress and ButtonRelease events for button 4 when I scroll up and button 5 when I scroll down.
Did you try this? What button events did you see (ignore all the mouse movement events)?
ZAxisMapping should setup the wheel mouse completely and set it properly for scrolling. As Turtleli suggested run xev and see what comes out in the output and logs.
Do you by chance have package xf86-input-mouse installed? I know a lot of distributions ONLY supply the xf86-input-evdev package for udev purposes, and I think Patrick does still include some of the older drivers for maximum detection capabilities, but you should run and check pkgtool's list to be sure before we proceed any further.
I'm also wondering becasue of how fickle VirtualBox is, I'm wondering if there's a remote chance your system isn't looking for hald for some reason. It shouldn't, but just in case you require it, here's the downloads for it:
You shouldn't need this package at all to be truthful, but as I stated VirtualBox tends to misbehave and often doesn't work right in any regards.
Just curious but have you attempted to check your VirtualBox virtual machine of Slackware against another Virtual machine like qemu to see if one has problems the other does or doesn't?
As I stated before VirtualBox has been problematic as of late, so don't put too much stock in it being completely stable and useful, but we will see what we can do to help with the mouse problem.
To be completely honest, I think it's VirtualBox that has the problem and not Slackware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
