Hey,

It appears to be a problem with the lirc_imon driver and not with the
LCDproc daemon. What I found out so far is this:

After loading the lirc_imon module you can write to /dev/lcd0 and text
will appear on the display. You can also read from /dev/lirc0 and you'll
see signals coming from the IR reciever or the Wheel in the frontpanel.

When you would either read or write a lot of data from/to these devices
the driver will somehow fail. The iMon device will be "disconnected" and
immediately after that "reconnect" and be recognised by the lirc_imon
driver again. The problem is that any programs that were reading/writing
to these devices will no longer respond.
For instance: LCDd needs to be restarted to be able to use the /dec/lcd0
device again and lirc needs to be restarted to be able to use /dev/lirc0.

A simple way to trigger this problem (on my machine at least) is to
execute the following command:
cat /dev/lirc0 > /dev/lcd0

When you turn the Wheel around a lot (or press buttons on the remote)
you'll see some characters appear on the LCD display and after a while
(about a minute) it will stop responding. In the message log you'll see
that the device got disconnected and reconnected again and messages about
the iMon device not being available will also keep popping up until you
kill the "cat" command.

Maybe you can verify this and we should report this to Venky Raju (the
iMon driver guy)?

Greetings, Edwin van Drunen

> I have the exact same case, and almost the same issue - The device fails
> with the same error listed in dmesg, but only after a seemingly random
> amount of time (in this case, the box has been up for 48+ hours, but the
> error has only just occurred) yet, the device is still shows under lsusb:
>  [EMAIL PROTECTED]:~$ lsusb
> Bus 006 Device 001: ID 0000:0000
> Bus 001 Device 001: ID 0000:0000
> Bus 007 Device 002: ID 2040:9950 Hauppauge
> Bus 007 Device 001: ID 0000:0000
> Bus 005 Device 001: ID 0000:0000
> Bus 004 Device 001: ID 0000:0000
> Bus 003 Device 010: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote
> Controller
> Bus 003 Device 001: ID 0000:0000
> Bus 002 Device 001: ID 0000:0000
>
>
> At this point, the device will only display junk until the hardware is
> cold booted.
>
> --
> LCDd crashes: vfd_write: no iMON device present
> https://bugs.launchpad.net/bugs/146292
> You received this bug notification because you are a direct subscriber
> of the bug.
>

-- 
LCDd crashes: vfd_write: no iMON device present
https://bugs.launchpad.net/bugs/146292
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to