Hey! I eventually realized that the error message is sometimes a red herring!
Apparently, what happens is that there are 2 protocols used by different revs of the USBUIRT. The driver tries to use the v1 protocol to interpret a packet, fails, logs an error, then succeeds with v2 and proceeds. So without doing any changes to the kernel, I eventually got lirc receiving stuff. Haven't had a chance to configure a .lirc to use it though... On Fri, Apr 3, 2009 at 12:08 PM, randomubuntuguy <john4li...@gmail.com>wrote: > still exists in mythbuntu 8.10 > 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux > > I don't want to recompile modules from source to fix this. > > Why not fix it? I already spent the $58 and I'm sure a bunch of others did > too. I'll hound the maker to participate more in linux bugtesting. > > ______________________________________________________________________________________ > >From the mythtv wiki: > > Partial Fix > > A number of distributions are using a patched FTDI driver that solves > the kernel oops, but is missing a critical fix to allow the USB-UIRT to > work. > > In /usr/src/linux/drivers/usb/serial/ftdi_sio.c locate the function > ftdi_tiocmget and add "case FT232RL:" just after "case FT223C:". Then > rebuild and install your modules. > > Without this fix you will get an error from lircd about not being able > to set DTR. > > -- > USB UIRT: uirt2_raw: checksum error > https://bugs.launchpad.net/bugs/177166 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux-meta” source package in Ubuntu: Fix Released > > Bug description: > Binary package hint: linux-image > > There was a regression in between 2.6.22 and 2.6.20 that made the USB UIRT > stop working. > > The USB UIRT is an infrared transceiver. You plug it into your computer, > and it receives signals from your remote control. This is an important > device because it's not only the cheapest piece of hardware that does this > ($8), but it's also the only cheap one that connects via USB and not via > your serial port. So, it's a very important piece of hardware for HTPC > software like MythTV. > > Here is the error messages reported in /var/log/messages: > > Sep 28 21:33:33 cesspool lircd-0.8.2[3729]: accepted new client on > /dev/lircd > Sep 28 21:33:33 cesspool lircd-0.8.2[3729]: uirt2_raw: checksum error > Sep 28 21:33:34 cesspool lircd-0.8.2[3729]: uirt2_raw: UIRT version 0905 ok > Sep 28 21:33:34 cesspool lircd-0.8.2[3729]: uirt2_raw: could not set DTR > Sep 28 21:33:34 cesspool lircd-0.8.2[3729]: caught signal > > People are working around this issue by copying ftdi_sio.c and ftdi_sio.h > from a 2.6.20 kernel source code tree into the 2.6.22 sources: > > http://ubuntuforums.org/showthread.php?t=579024 > > It's definitely an upstread issue. Here, they're talking about the issue > on the mythtv-users mailing list and distributions other than Ubuntu: > > http://www.gossamer-threads.com/lists/mythtv/users/293503 > -- USB UIRT: uirt2_raw: checksum error https://bugs.launchpad.net/bugs/177166 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
