Final details... I'm an idiot... Looks like I edited the wrong file when I added in the Server section... the input device sections were there, but they weren't referenced.
Soo... everything appears to be working. The only thing I'd like to change is the sensitivity of the mouse by itself... is this possible? I tried to do this through the KDE GUI but it appeared to have no effect. Thanks (and I appologize for the spam... I should've looked at my configuration closer) --Jeff On Wednesday 14 March 2007 18:33, wrote: > Some more details... > > I've rebuilt the kernel module, the X11 module, and the kernel itself (with > evdev as a module this time). > > I no longer get the evdev fatal error, but I do continue to get the stack > trace, and X fails to load. > > I'm lost for ideas now, and stuck with a non-functional XOrg 7.2 setup. > What can I do!? > > Please help! > --Jeff > > PS: wacdump shows my tablet working perfectly in the console. > > --------- Original message -------- > From: > To: linuxwacom-discuss@lists.sourceforge.net > <linuxwacom-discuss@lists.sourceforge.net> > Subject: [Linuxwacom-discuss] unable to startx using SuSE 10.2 with > Graphire4 > Date: 03-15-07 00:50 > > > Hello, > > I got through the process (./configure; make; make install) with the latest > linxuwacom distribution. > > In the process, the already existing wacom_drv.o was used (I assume from > SuSE). > > Everything appears to be working properly, in that I'm able to capture the > output from /dev/input/event2. However, when I start to start X11, via > 'startx' I receive the attached error log. > > What confuses me is the FATAL: message near the end of the trace. It > complains about not being able to find evdev. I believe, without this, > that /dev/input/event3 wouldn't be working, so I must have it! Can someone > please suggest what is wrong? > > Also, the stack trace at the end -- is this merely an indication of where > the error came from, or is this an indication of a fault/exception? If so, > does this mean I'll need to rebuild some drivers? I thought sticking with > the drivers provided by SuSE 10.2 would be the safest approach... perhaps > this isn't true? > > Any help on this matter would be greatly appreciated! > > Thanks, > Jeff > > ________________________________________________ > This mail was sent by UebiMiau 2.5 > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys-and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID= >DEVDEV > > > _______________________________________________ > > Linuxwacom-discuss mailing list > Linuxwacom-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss > > > ________________________________________________ > This mail was sent by UebiMiau 2.5 > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Linuxwacom-discuss mailing list > Linuxwacom-discuss@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Linuxwacom-discuss mailing list Linuxwacom-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
