Red Hat Bugzilla – Bug 445193
elographics driver fails to initialize
Last modified: 2008-11-06 21:50:46 EST
Description of problem:
We have a project using Sunit dSeries vehicle computers
Fedora installs and runs fine. Excellent work, guys!
The Sunit dSeries device has a Elo AccuTouch compatible touch screen attached to
/dev/ttyS1 and it works with the xorg-x11-drv-elographics driver.
The only problem is that the driver insists on probing the device at startup,
insisting on a response that never comes, and the shuts down.
A fix for this is adding an option "AllowNoCntl" that would allow the driver to
start up even if there is no response to the identification probe. This has
already been implemented for XFree86, I think.
We have a workaround: If we operate the touch screen during X startup, the
device is successfully identified (probably due to random coordinates sent) as
(--) Elographics touchscreen is a AccuTouch, connected through a serial link.
(--) The controller is a model E271-2200, firmware revision 2.0.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Fedora 8 on Sunit d12 Vehicle Computer.
2. Add touch screen device to xorg.conf
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
Option "Device" "/dev/ttyS1"
Option "Name" "ELO Touchscreen"
Option "AlwaysCore" "On"
Option "ScreenNo" "0"
Option "MinX" "341"
Option "MaxX" "3738"
Option "MinY" "471"
Option "MaxY" "3554"
Option "UntouchDelay" "3"
Option "ReportDelay" "1"
Option "debuglevel" "5"
3. Restart GDM
The ELO Touchscreen device fails to initialize with the following error message
Unable to ask Elographics touchscreen identification
If the touch screen is operated during X startup, the device is identified and
The device should initialize correctly even if it is not operated during X startup.
Could we get complete /var/log/Xorg.*.log attached to this bug, please?
Created attachment 304615 [details]
X server log when the probe fails
Created attachment 304616 [details]
X server log when the probe succeeds
Did the logs help?
Is this still an issue? I could probably knock up a patch to fix that if you're willing to test it.
Created attachment 320236 [details]
Naive patch to allow driver to start up without response to hardware probes.
Yes, this is still an issue. We have downloaded the upstream sources and made a naive change to enable initialization of the driver. I'll attach a patch for this.
Created attachment 320237 [details]
Add suppport for "Model" option, and support Sunit dSeries model
Here's two quick patches (in the same file) against git master.
Patch 1 adds general support for config option "Model" to the driver.
Patch 2 parses Option "Model" "Sunit dSeries" and does not execute the query commands if the model is set.
It's not exactly the same as your patch since it doesn't send anything to the device. From your previous logfile I can see that you're not getting any replies from the screen but I'm not sure if that also implies that you don't have to send the command.
This looks great! I'll test them as soon as can, by friday at the latest.
I'll report back here when I have tested the patches.
I'll just leave the needinfo flag here so we get notified for sure.
Hi Uwe, Peter and others
Great work guys! I have tested these patches with 7", 8" and 10" Sunit touchscreens under Ubuntu 8.04 without any problems (apart from calibration problems but that was expected). Maybe Uwe will test these patches under Fedora.
Now, Sunit d is actually dual display/touchscreen vehicle computer which means that it is possible to use two touchscreens with Sunit d. Both touchscreens use same COM2 port for sending data. First byte of the primary touchscreen (touchscreen connected to LVDS 1) is 55 (in hex) and first byte of secondary touchscreen (touchscreen connected to LVDS 2) is 66.
So, at some point there will be need for patch to support secondary touchscreen or own driver for Sunit d touchscreens. At the moment there are problems getting the secondary display work under linux but it will be fixed sooner or later.
Uwe: did you have any chance to test the patches for Fedora?
Unless you found any issues, they'll be going upstream.(In reply to comment #10)
> Now, Sunit d is actually dual display/touchscreen vehicle computer which means
> that it is possible to use two touchscreens with Sunit d. Both touchscreens use
> same COM2 port for sending data. First byte of the primary touchscreen
> (touchscreen connected to LVDS 1) is 55 (in hex) and first byte of secondary
> touchscreen (touchscreen connected to LVDS 2) is 66.
Jari, please take this upstream and file a bug on bugs.freedesktop.org.
(it'll most likely be me doing it anyway if I find the time :)
Sorry, I haven't found time to test this, and I probably will not find time any time soon, especially since the changes will go upstream if I do nothing :)
I have looked at the patches you sent, and they look good.
xorg-x11-drv-elographics-1.2.3-1.fc9 has been submitted as an update for Fedora 9.
xorg-x11-drv-elographics-1.2.3-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update xorg-x11-drv-elographics'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-9047
xorg-x11-drv-elographics-1.2.3-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.