Any reason not to get rid of the mouse if you want to use the Wacom?
I would happily ditch the mouse, and in the course of testing what you suggest in this email, I have. No change, though. As I understand it, it's not the mouse itself, but the configuration I have. But I could be wrong about that.
What does # ls -alF /dev/input show?
It shows this: [root@localhost dave]# ls -alF /dev/input total 0 drwxr-xr-x 2 root root 180 Aug 3 2005 ./ drwxr-xr-x 8 root root 5760 Aug 3 01:13 ../ crw-r--r-- 1 root root 13, 64 Aug 3 2005 event0 crw-r--r-- 1 root root 13, 65 Aug 3 2005 event1 crw-r--r-- 1 root root 13, 66 Aug 3 2005 event2 crw-r--r-- 1 root root 13, 63 Aug 3 2005 mice crw-r--r-- 1 root root 13, 32 Aug 3 2005 mouse0 crw-r--r-- 1 root root 13, 33 Aug 3 2005 mouse1 lrwxrwxrwx 1 root root 6 Aug 3 2005 wacom -> event2
I'd try rebooting to runlevel 3 with the mouse disconnected and reconfiguring X as follows:
I did what you suggest, and the net result was that it wiped out what I had in the xorg.conf and writes a new one. This makes the wacom go to it's default settings, and I also can't access it anymore by using the configuration GUI utility that comes with the drivers. When I start the utility, it says tablet not found. I put the xorg.conf file back to how I had it, and I can start the utility and it finds the tablet, but then I'm basically back to where I was with the first posting, where the tablet will respond to some speed and sensitivity settings, but the buttons can't be configured, and it's stuck in "absolute" mode, and not "relative" mode. In short, I can't configure it because it's conflicting with the mouse still.
It's still opaque to me as to where this conflict is happening. There is no mouse connected to the computer anymore, and yet still if I try to have an xorg.conf file without reference to a mouse, X windows crashes. What's up with that?
Dave