<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 13 March 2013 11:44, Jos Hoekstra <span dir="ltr"><<a href="mailto:joshoekstra@gmx.net" target="_blank">joshoekstra@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div><div class="h5">
<div>On 12-3-2013 23:40, Karl Newman wrote:<br>
</div>
<blockquote type="cite">
<div class="gmail_quote">On Tue, Mar 12, 2013 at 1:12 PM, Jos
Hoekstra <span dir="ltr"><<a href="mailto:joshoekstra@gmx.net" target="_blank">joshoekstra@gmx.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>On 12-3-2013 4:49, Karl Newman wrote:<br>
</div>
<blockquote type="cite">
<div class="gmail_quote">On Mon, Mar 11, 2013 at 9:31 AM,
Jos Hoekstra <span dir="ltr"><<a href="mailto:joshoekstra@gmx.net" target="_blank">joshoekstra@gmx.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Hi
all, recently I decided to upgrade my frontend with
and SSD to speed up bootup and silence it a bit more.<br>
After this update something changed in I guess the
kernel since after that I get symptoms which look like
the up-arrow is constantly pressed on a keyboard. I
was able to determine it was the VFD that's causing
these symptoms, however I don't know how to get rid of
it.<br>
When I boot back in the old system which was Ubuntu
12.04 with kernel 3.2.something everything is ok.<br>
I cannot get that kernel installed in Ubuntu 12.10 and
everything that's 3.4 or higher seems to cause these
problems.<br>
<br>
Did anyone with this VFD experience the same problems?
If so, how did you get them solved?<br>
<br>
Thanks in advance,<br>
<br>
Jos<br>
</blockquote>
<div><br>
I don't know which SoundGraph model you have, and
unfortunately there are several different models, some
of which share the same USB ID (15c2:ffdc), but the
driver uses different, incompatible methods for
driving the different displays. There is a module
called 'imon' (kernel config symbol ir_imon) which has
a parameter called display_type which I had to set to
1 in order for the VFD to work. The default autodetect
(0) didn't work for me. Check your distribution
documentation for how to configure module parameters.<br>
<br>
Karl<br>
</div>
</div>
<br>
</blockquote>
I got the one in the silverstone LC16M(15c2:0036) and it
seems I'm not the only one experiencing these problems.<br>
<a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1086120" target="_blank">https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1086120</a><br>
It's actually kernel 2.6.32 that works ok all later seem to
screw this up.<br>
Changing the setting via module parameters doesn't help with
the issue which also occurs on other linux(fedora 18) with a
recent kernel.<br>
I wonder why there seem to be so little users with
problems....<span><font color="#888888"><br>
<br>
Jos<br>
</font></span></div>
</blockquote>
</div>
<br>
Mine came with a Silverstone LC11M, and is the above mentioned
15c2:ffdc model and it's still working fine with the imon module
in 3.7.10 (although its IR receiver died several years ago so now
it's just a display). Did you try it with a generic kernel, or
only with a Fedora-specific kernel?<br>
<br>
I found this post from Jarod Wilson, who did a lot of the work to
merge the lirc code into the kernel: <a href="http://wilsonet.com/?page_id=95" target="_blank">http://wilsonet.com/?page_id=95</a>
Maybe it will give you some ideas about where to look or what to
try next.<br>
<br>
Karl<br>
</blockquote></div></div>
I set it up on ubuntu and only tried a Fedora livedisk to rule out
ubuntuspecific problems. I tried with several mainline kernels from
ubuntu ranging from 2.6.32 to 3.8 and I'm guessing that the change
to dev-input is the possible cause. Maybe catching the offending
code and discarding it is the way to use the display and lirc again.<br>
<br>
</div>
<br></blockquote><div>I've got the same case and same device ie. 15c2:0036 and its working fine on 12.0.4.2 mythbuntu x86_64 3.2.0-38, recently updated from 12.04, I initially had a fight with lirc to get the remote working correctly but the VFD worked fine from memory. <br>
<br>/etc/LCDd.conf is set to imon and the imon config is as follows<br><br>[imon]<br><br># select the device to use<br>Device=/dev/lcd0<br><br># display dimensions<br>Size=16x2<br><br>CharMap=hd44780_euro<br><br></div><div>
/etc/lirc/hardware.conf contains<br><br>#Chosen Remote Control<br>REMOTE="Linux input layer (/dev/input/eventX)"<br>REMOTE_MODULES="lirc_dev lirc_imon"<br>REMOTE_DRIVER="devinput"<br>REMOTE_DEVICE="/dev/input/by-id/usb-15c2_0036-event-if00"<br>
REMOTE_SOCKET="/var/run/lirc/lircd"<br>REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput"<br>REMOTE_LIRCD_ARGS=""<br><br>/etc/udev/rules.d/10-lirc.rules<br>ATTRS{idVendor}=="15c2", ATTRS{idProduct}=="0036", OPTIONS=="ignore_device"<br>
</div><div><br></div><div>I think the udev rule was the winner in the end but this was some time back now<br></div><div><br></div><div>Cheers,<br><br></div><div>Anthony<br></div></div><br></div></div>