Intuos4 on centos5 fails to create device in time

View: New views
7 Messages — Rating Filter:   Alert me  

Intuos4 on centos5 fails to create device in time

by Grant Street :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello

I was wondering if anyone else had seen this.

version 0.8.4-3
kernel 2.6.18-128

on boot, with the wacom connected, the /dev/input/wacom device is not
created until after the X server has started, causing errors in Xorg log
file. If you immediately issue a ctrl-Alt-Bksp it works as expected.

I thought I may be able to roughly work around this by using wdaemon or
wacomproxy but they both don't look to support intuos4.

I will get more details soon

Grant



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 on centos5 fails to create device in time

by Grant Street :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Further information

>
> I was wondering if anyone else had seen this.
>
> version 0.8.4-3
> kernel 2.6.18-128
>
> on boot, with the wacom connected, the /dev/input/wacom device is not
> created until after the X server has started, causing errors in Xorg log
> file. If you immediately issue a ctrl-Alt-Bksp it works as expected.

When I plug in a Intuos2 it works without issue. it even works in the
graphical boot screen albeit in relative mode. I plug in the intuos 4
and I get nothing on the boot screen and the login screen is barely
working only moves on pendown+drag. I hit ctrl-Alt-Backsp and it works.
bleow are exerpts from the xorg log file of not working and working



>
> I thought I may be able to roughly work around this by using wdaemon or
> wacomproxy but they both don't look to support intuos4.

I check the websites of the two projects, anyone know if they are still
being updated?

Working log entries
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 245 for button 1
(==) Wacom USB Intuos4 tablet speed=9600 (38400) maxX=44704 maxY=27940
maxZ=2047 resX=5080 resY=5080  tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "pad" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded

Non Working entries

(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
         No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
         No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
         No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
         No such file or directory.
Error opening /dev/input/wacom : Success
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 on centos5 fails to create device in time

by Ping@LinuxWacom :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Thu, Oct 29, 2009 at 5:33 PM, Grant Street <grants@...> wrote:
Further information
>
> I was wondering if anyone else had seen this.
>
> version 0.8.4-3
> kernel 2.6.18-128
>
> on boot, with the wacom connected, the /dev/input/wacom device is not
> created until after the X server has started, causing errors in Xorg log
> file. If you immediately issue a ctrl-Alt-Bksp it works as expected.

When I plug in a Intuos2 it works without issue. it even works in the
graphical boot screen albeit in relative mode. I plug in the intuos 4
and I get nothing on the boot screen and the login screen is barely
working only moves on pendown+drag. I hit ctrl-Alt-Backsp and it works.
bleow are exerpts from the xorg log file of not working and working

The root cause, I think, is the kernel driver didn't load before X server starts.  The difference between I2 and I4 is, most probably, caused by the use of wdaemon.
 
>
> I thought I may be able to roughly work around this by using wdaemon or
> wacomproxy but they both don't look to support intuos4.

I check the websites of the two projects, anyone know if they are still
being updated?

I don't think either is updated, at least they are not for updated for I4.  You may contact with the authors.  Or you can add I4 to the application yourself if you know how to write C program.
 
Working log entries
(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/wacom"
stylus Wacom X driver grabbed event device
(==) Wacom using pressure threshold of 245 for button 1
(==) Wacom USB Intuos4 tablet speed=9600 (38400) maxX=44704 maxY=27940
maxZ=2047 resX=5080 resY=5080  tilt=enabled
(==) Wacom device "stylus" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "eraser" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "cursor" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(==) Wacom device "pad" top X=0 top Y=0 bottom X=44704 bottom Y=27940
resol X=5080 resol Y=5080
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded

Non Working entries

(II) XINPUT: Adding extended input device "pad" (type: Wacom Pad)
(II) XINPUT: Adding extended input device "cursor" (type: Wacom Cursor)
(II) XINPUT: Adding extended input device "eraser" (type: Wacom Eraser)
(II) XINPUT: Adding extended input device "stylus" (type: Wacom Stylus)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success
(**) Option "Device" "/dev/input/wacom"
(EE) xf86OpenSerial: Cannot open device /dev/input/wacom
        No such file or directory.
Error opening /dev/input/wacom : Success
(--) Mouse0: PnP-detected protocol: "ExplorerPS/2"
(II) Mouse0: ps2EnableDataReporting: succeeded

As I mentioned above, wacom.ko is not loaded when system starts.  So /dev/input/wacom is not available yet.  I bet if you "ls /dev/input", you don't see wacom in the output.

Ping


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 on centos5 fails to create device in time

by Grant Street :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


> The root cause, I think, is the kernel driver didn't load before X
> server starts.  The difference between I2 and I4 is, most probably,
> caused by the use of wdaemon.

Essentially the udev event is not being triggered untill the last moment
  which is too late. Why wouldn't the module be loaded until then?

I don't reference the wdaemon device and it has the same behavior with
it installed or removed

>  
>
>      >
>      > I thought I may be able to roughly work around this by using
>     wdaemon or
>      > wacomproxy but they both don't look to support intuos4.
>
>     I check the websites of the two projects, anyone know if they are still
>     being updated?
>
>
> I don't think either is updated, at least they are not for updated for
> I4.  You may contact with the authors.  Or you can add I4 to the
> application yourself if you know how to write C program.
>  
Fair enough
>
> As I mentioned above, wacom.ko is not loaded when system starts.  So
> /dev/input/wacom is not available yet.  I bet if you "ls /dev/input",
> you don't see wacom in the output.
I would suspect so. As mentioned the device is created after the xorg
server starts when udevd gets the event. I can't test this as by the
time I'm able to log in it is already there

Grant

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 on centos5 fails to create device in time

by Jason alavaliant :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



On Fri, Oct 30, 2009 at 5:08 PM, Grant Street <grants@...> wrote:


>
>
>      >
>      > I thought I may be able to roughly work around this by using
>     wdaemon or
>      > wacomproxy but they both don't look to support intuos4.
>
>     I check the websites of the two projects, anyone know if they are still
>     being updated?
>
>
> I don't think either is updated, at least they are not for updated for
> I4.  You may contact with the authors.  Or you can add I4 to the
> application yourself if you know how to write C program.
>

I don't think the author of wacomproxy is still updating it.   There are however other people still hacking around with it.    If you check the tracker for wacomproxy  (http://sourceforge.net/tracker/index.php?func=detail&aid=2786587&group_id=184413&atid=909158)  there is a patch for I4 support available.      Adding new tablet support to wacomproxy is actually fairly simple for the most part, if you read the source code comments a lot of it is copying and pasting sections of code from the linuxwacom source tree.   I made my own I4 patch for wacomproxy independantly for use at my work before noticing the one uploaded to the website.


Incidentally some of the admins at my work also managed to make a patch to make wacomproxy work with kernel 2.6.29 which I think we could release if anybody particular wanted it.  (I've not really looked into it at this point since outside my work I've not heard of any interest for wacomproxy on newer kernels.)

I can't speak for wdaemon as I've never used it.

-J



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 on centos5 fails to create device in time

by Alexia Death-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I dont really see a use for such things any more. Newer Xorgs all
support DBUS configuration. I've writen my own X hotplug daemon, that
when run tries to remove anything added automatically and then scans
for wacom device nodes and adds all devices it finds. This includes
any USB serial adapter using serial tablets I have. It also listens to
dbus for any notifications of plugged in tablets and if I so desire I
can also make it scan for new devices when I hotplug my USB serial
adapter and effectively have a fully hotpluggable serial tablet.
Hacking this up took me one or two evenings. If you wanna use it,
heres the python code:
http://sourceforge.net/projects/watahod/develop/  It does presume its
own udev file.

--
--Alexia

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Re: Intuos4 on centos5 fails to create device in time

by Grant Street :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

SOLUTION

For the records ....

Grant Street wrote:
>> The root cause, I think, is the kernel driver didn't load before X
>> server starts.  The difference between I2 and I4 is, most probably,
>> caused by the use of wdaemon.
>
> Essentially the udev event is not being triggered untill the last moment
>   which is too late. Why wouldn't the module be loaded until then?
>
> I don't reference the wdaemon device and it has the same behavior with
> it installed or removed

I didn't run depmod, running /sbin/depmod caused the kernel to load the
driver as normal. This may be because of the older kernel not
recognising the newer wacom.

>
>>  
>>
>>      >
>>      > I thought I may be able to roughly work around this by using
>>     wdaemon or
>>      > wacomproxy but they both don't look to support intuos4.
>>
>>     I check the websites of the two projects, anyone know if they are still
>>     being updated?
>>
>>
>> I don't think either is updated, at least they are not for updated for
>> I4.  You may contact with the authors.  Or you can add I4 to the
>> application yourself if you know how to write C program.
>>  
> Fair enough
>> As I mentioned above, wacom.ko is not loaded when system starts.  So
>> /dev/input/wacom is not available yet.  I bet if you "ls /dev/input",
>> you don't see wacom in the output.
> I would suspect so. As mentioned the device is created after the xorg
> server starts when udevd gets the event. I can't test this as by the
> time I'm able to log in it is already there
>

I applied the patch to wacom proxy and it works as designed
http://sourceforge.net/tracker/index.php?func=detail&aid=2786587&group_id=184413&atid=909158

Thanks to every one

Grant

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss