On onsdag 25 juli 2007, Gian Paolo Mureddu wrote: > I have an issue I don't seem to find any explanation for. My issue seems > not to be directly related to the LinuxWacom driver, but I'd like other > users of either Xorg 1.3 (7.2.99 / 7.3) and/or GDM 2.18.3 or newer to > confirm this. If the Wacom tablet is configured in Xorg and working > regularly, GDM works just "fine" (well, maybe you are unable to move the > mouse pointer while in the greeter screen, cursor moves to lower right > corner). At any rate, the issue I'm experiencing in such a configuration > (Fedora 7) is that if I detach the tablet from the computer and restart > X (or simply log out) GDM won't start again, X is fine, a message may > appear stating that there has been a problem running the login manager, > and then restarts... in cycles. I've narrowed the problem to a > correlation in Xorg and GDM log files. Xorg will be unable to find and > initialize the /dev/input/wacom device (obviously, as it is detached > from the computer), GDM will catch this error from X and will also print > it out to its own log as the reason why it is not able to start... > > === GDM log === [...] > (II) Module already built-in > FATAL: Module evdev not found. [...]
Getting an error opening the wacom device should not cause any problem.. I'm running KDM myself (Kubuntu 6.10, 7.04) and have never had any problems without the tablet connected, GDM might however do things a little different (not that I can see why). The fact that X works but not GDM makes me wonder if there's two separate installations (or maybe only configurations) of X that are used for different things.. The strance behaviour from the tablet when it's connected makes it makes almost more likely (in KDM it works as when I've logged in for me). Anyway the 'fatal' message might be worth looking more closely at since those usually are worse than 'only' errors. I know the evdev driver in X has some fishy hotplug-code that can cause some grief, but since it complain it can't load it that should not be the problem in this case. > === Xorg.0.log === > > (**) Option "Device" "/dev/input/wacom" > (EE) xf86OpenSerial: Cannot open device /dev/input/wacom > No such file or directory. > Error opening /dev/input/wacom : Success [...] > In my Xorg.conf file there's an exception for the mice devices to allow > X to start even in failure to initialize the device... > > === Xorg.conf - ServerFlags == > > Section "ServerFlags" > Option "AllowMouseOpenFail" "yes" > Option "AIGLX" "on" > EndSection If I remember correctly this was needed before the aggregated device /dev/input/mice existed (which always is allowed to be opened despite no mice beeing connected). Returning '!Success' from some functions will cause the X-server to abort during initialization, but the wacom-driver does not return that so that's not the reason for an abort. > Looks like the Wacom InputDevice entries are not being treated as mice > devices at all, but other serial devices. I wonder if other users with > similar configurations in other distributions have the same issue with > GDM or in even Fedora 7 (but with KDM for example), or if this might in > any way be imputable to the LinuxWacom driver (which I highly doubt). > This poses problem for me, as in the environment I need this working > there are more computers than tablets available, and the tablets are > constantly moved from one system to another, however, for obvious > reasons, a situation like this is a rather serious problem. I wouldn't > want to move the whole lab to another distribution, currently we're > using FC6 for the production environment, but if this wouldn't be a > problem in another distribution with the same features set as Fedora 7, > I'd be willing to take my chances... If you're going to move the tablets around, you'll probably want to ask how much hassle you'd like to have when unpluggin/replugging them. Also I know I've had problem getting the tablet to work when starting X without the tablet connected (=had to restart X to get it working at all). The most easy way to get hotplugging to work would be to just switch VT, but there are other options which will give you more seamless hotplugging. It all depend on your users and how much inconvenience they are willing to put up with. Real hotplugging is still a bit into the future as far as I know, and 7.3 is definitely not there yet. > Do you think there might be a workaround for this? Thus far I've been > unable to find any. There should be a viable solution for you, the first 'problem' is to know what your problem is though.. Your system does seem to act a bit fishy.. :) Cheers Magnus ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Linuxwacom-discuss mailing list Linuxwacom-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
