<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Daryl,<br>
<br>
daryl kuchay wrote:
<blockquote
cite="mid:BANLkTimbm1DWksk5rwriA+7UJpcHuKW0Ag@mail.gmail.com"
type="cite">Hi Folks,
<div><br>
</div>
<div>I am working on bringing two industrial tablet pc's loaded with
linux to the Tuesday meeting. Have one up and running however I am
getting stuck with segfaults on the touchscreen driver for the second
tablet. More specifically I segfault when running the calibration
utility and I think I know why but I need someone to confirm my
thoughts.</div>
<div><br>
</div>
<div>The tablets in question use geode hardware from AMD. These are
i586 and lack the nop capability or long noops from what I have read
from "synthhead" in the arch linux community. He wrote a kernel patch
to bring geodes and transmeta crusoe's up to i686. I know what you are
thinking and I only have a 1gb ssd to work with. Not enough room for
kernel source and a recompile.</div>
<div><br>
</div>
<div>Here is my suspicion:</div>
<div><br>
</div>
<div>If the mfgr of the touchscreen wrote their drivers on an i686 or
emulated i686 system (utilizing libc6-i686) could that explain why I am
getting segfaults when running the calibration utility? I have checked
dependencies and I should be good. Xorg and libgtk are the only deps
mentioned. dmesg only stated a general segfault </div>
<div><br>
</div>
<div>Thank you in advance</div>
<div>Daryl</div>
<div><a moz-do-not-send="true" href="http://webdt.org">webdt.org</a></div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
clue mailing list: <a class="moz-txt-link-abbreviated" href="mailto:clue@cluedenver.org">clue@cluedenver.org</a>
For information, account preferences, or to unsubscribe see:
<a class="moz-txt-link-freetext" href="http://cluedenver.org/mailman/listinfo/clue">http://cluedenver.org/mailman/listinfo/clue</a></pre>
</blockquote>
<br>
Please run the calibration utility under "strace -f" and capture the
output and post it to the list and maybe we can suggest what might be
causing it. If that isn't helpful then you'll need to run it in a
debugger.<br>
<br>
For example: # DISPLAY=:0; sh -c "strace -f /path/to/command
1>>/tmp/strace.out 2>>/tmp/strace.out"
1>>/tmp/strace.out 2>>/tmp/strace.out<br>
<br>
I know all those redirects and running strace inside of sh might seem
excessive but if you really want to capture stdout and stderr of
everything, I've found sometimes that's necessary.<br>
<br>
HTH<br>
Jim<br>
<pre class="moz-signature" cols="72">--
Jim Ockers, P.Eng. (<a class="moz-txt-link-abbreviated" href="mailto:ockers@ockers.net">ockers@ockers.net</a>)
Contact info: <a class="moz-txt-link-freetext" href="http://www.ockers.net/msi.html">http://www.ockers.net/msi.html</a>
</pre>
</body>
</html>