Description of problem:
Currently RHEL 4 and 5 do not support the Wacom mini tablet PTZ-431W. It
appears to work in Fedora 6 kernel 2.6.22-1-32
Version-Release number of selected component (if applicable):
Created attachment 161887 [details]
Please apply this patch and report how it goes.
Charlie, about the kbd issue, see the comment I added on that BZ#.
About the wacom stuff, will be queued for the next RHEL-4 version (4.7) along with
This kernel solved all the problems with this tablet? All the features are working
Charlie, did you tried the test packages?
please test and tell me how it goes
Okay, I got some hardware so I can begin testing again. I downloaded the 55 and
the 65 kernel from the link provided. Neither of them seem to work in absolute
mode. I added `Options "Mode" "Absolute"` to all wacom devices. But that
didn't seem to improve anything.
did you installed the linuxwacom package too?
Correct, even the wdaemon packages.
(In reply to comment #0)
> Description of problem:
> Currently RHEL 4 and 5 do not support the Wacom mini tablet PTZ-431W. It
> appears to work in Fedora 6 kernel 2.6.22-1-32
did you tested the packages with PTZ-431W too?
Yes, it appears to work beautifully.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Charlie, the required patches will be on RHEL4.7 kernel and the needed packages
will be also on RHEL4.7.
Will be possible to them to update to RHEL4.7 when it's out?
Committed in 68.22.EL. Released in 68.23.EL. RPMS are available at http://people.redhat.com/vgoyal/rhel4/
Created attachment 299057 [details]
Hrm, I was hoping I could attach that and send a message. Okay, so wdaemon is
chkconfig to on. However on boot it doesn't say fail it just goes on like it
worked. Then we find the daemon isn't running and try to restart it twice.
Here is the current software versions I am running.
cwyse@unbridled [:~] % rpm -q wdaemon linuxwacom; uname -r
Also here is my wdaemon.conf
device = 41,/dev/input/wacom-tablets/cintiq21ux-tablet
thanks for the info. It's strange because:
Mar 21 13:52:57 doerun wdaemon: Unable to grab device
/dev/input/wacom-tablets/cintiq21ux-tablet (Device or resource busy)
this message means something else is grabbing the device and the usual components
that do that are wdaemon or xorg wacom driver. anyway, wdaemon must be more
robust on those cases (keep trying to grab the device instead of just giving up
after some tries)
can you try running the debug wdaemon RPM that I uploaded to
upgrade using it, then reboot the machine. It'll create a /tmp/wdaemon.log. Please
send me this log after the machine finishing booting.
Okay it doesn't create the /tmp/wdaemon.log file. But it does look like the
error is from /dev/uinput not being created by the time wdaemon runs. Also,
this problems seems to happen every other reboot or two. So it's not
persistent. Here are some commands I ran right after reboot.
cwyse@unbridled [:~] % rpm -q wdaemon linuxwacom
cwyse@unbridled [:~] % uname -r
cwyse@unbridled [:~] % ls -l /tmp/wdaemon.log
ls: /tmp/wdaemon.log: No such file or directory
cwyse@unbridled [:~] % tail -50 /var/log/al
cwyse@unbridled [:~] % tail -50 /var/log/all.all | grep wdaemon
Mar 31 17:30:47 unbridled wdaemon: succeeded
Mar 31 17:30:47 unbridled wdaemon: wdaemon version 0.14
Mar 31 17:30:47 unbridled wdaemon: Setting debug level to 2
Mar 31 17:30:47 unbridled wdaemon: Did 2 conversions
Mar 31 17:30:47 unbridled wdaemon: Got key [device], value
Mar 31 17:30:47 unbridled wdaemon: Got device type 41 and filename
Mar 31 17:30:47 unbridled wdaemon: hotplug_add_file: added directory
Mar 31 17:30:47 unbridled wdaemon: Unable to open uinput file /dev/uinput: No
such file or directoryError adding device
Mar 31 17:30:47 unbridled wdaemon: wdaemon startup failed
cwyse@unbridled [:~] % sudo service wdaemon status
wdaemon is stopped
(In reply to comment #35)
> Okay it doesn't create the /tmp/wdaemon.log file. But it does look like the
> error is from /dev/uinput not being created by the time wdaemon runs. Also,
> this problems seems to happen every other reboot or two. So it's not
> persistent. Here are some commands I ran right after reboot.
> Mar 31 17:30:47 unbridled wdaemon: Unable to open uinput file /dev/uinput: No
> such file or directoryError adding device
> Mar 31 17:30:47 unbridled wdaemon: wdaemon startup failed
> cwyse@unbridled [:~] % sudo service wdaemon status
great catch Charlie! thanks, I'll fix this as first thing tomorrow morning.
the new wdaemon package is available at
please test it. it'll fix the initialization problem.
Also, notice that this version will be in RHEL4.7, so if you find any
problems, let me know ASAP.
I just installed it and booted my machine 5 times in a row and wdaemon seems to
have started with no problems. I put the package in an update tree and let the
other people using cintiqs know where to get it so they will be helping me test
it out some time tomorrow, hopefully. But everything looks good so far, I'll
let you know of something changes. Thanks.
added to RHEL4.7 Driver Updates:
wacom: driver updated to add support for the following input devices:
* Intuos3 12x19
* Intuos3 12x12
* Intuos3 4x6
* Cintiq 20wsx
please advise if any further revisions are required. thanks!
the RHEL4.7 release notes deadline is on June 17, 2008 (Tuesday). they will
undergo a final proofread before being dropped to translation, at which point no
further additions or revisions will be entertained.
a mockup of the RHEL4.7 release notes can be viewed here:
please use the aforementioned link to verify if your bugzilla is already in the
release notes (if it needs to be). each item in the release notes contains a
link to its original bug; as such, you can search through the release notes by
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.