lircd doesn't find dvico usb IR remote device correctly (expects /dev/lirc)

Can you elaborate which type of lirc device you chose? Please post that functional hardware.conf so we can get a better idea on the proper total solution.

I have attached a copy of lsusb -v on the device in question (it is a DVICO USB HID Remocon V5.00) and the new hardware.conf as well as backed up versions of hardware.conf in case they are relevant to the problem.

fixed in bzr #28

This bug was fixed in the package lirc - 0.8.3-0ubuntu2

---------------
lirc (0.8.3-0ubuntu2) intrepid; urgency=low

  * debian/patches/25_upstream_2.6.26.patch:
    - Fix lirc-modules-source compilation on 2.6.26 by pulling some
      patches from CVS (LP: #247233)
  * debian/rules:
    - Install original modules back into proper location for
      intrepid kernel (LP: #242216)
  * debian/patches/37_msi_tv_anywhere.dpatch:
    - Create patch for supporting MSI TV @anywhere remote. (LP: #241830)
  * debian/lirc.postinst:
    - Correct path to look for module in Intrepid.
    - Ask for a path when using dvico remotes. (LP: #238032)
    - Don't accidentally overwrite lircd.conf and hardware.conf
      when things haven't really changed at all. (LP: #206609)
  * debian/lirc.init.d:
    - Don't allow udev to put us into endless spinning loops. Instead
      pray that module hotplugging worked for all things USB. (LP: #269743)
  * debian/lirc.fdi:
    - Include this FDI file to prevent in kernel support for the
      saa7134 when LIRC is installed. (LP: #204960, #164627)
  * debian/rules:
    - Install FDI file.
  * debian/lirc.install:
    - List FDI file.
  * debian/patches/22_hauppauge_novat_500.dpatch:
    - Adapt to include alternative numeric keys. (LP: #224080)
  * debian/patches/25_upstream_2.6.27.dpatch:
    - Update to content that is currently sitting in Ubuntu GIT
      tree.

 -- Mario Limonciello <email address hidden> Wed, 24 Sep 2008 12:02:17 -0500

This problem still exists for me (Mythbuntu Intrepid AMD64) in lirc 0.8.3-0ubuntu2.

I chose the Dvico USB IR as part of the install configuration.

Editing /etc/lirc/hardware.conf to set REMOTE_DEVICE to /dev/usb/hiddev0 (was /dev/lirc0) fixed the problem.

Output of lsusb -v for the USB IR is attached.

I just did a clean install of mythbuntu 8.10 on the machine in question, and I'm not sure that the solution listed above is an adequate one to the problem.

When installing I was asked where the device for the remote was located and two choices were given (one was /dev/usb/hiddev0 and I cannot remember the other - probably /dev/lirc I guess). How is the average user supposed to be able to answer this question? I can only answer because of a fair bit of googling I did back when I submitted this bug report.

Surely this can be determined automatically in some manner to avoid asking questions the user will be unable to give an answer for? In my case only one of the listed devices actually existed in /dev anyway, so what was the point of asking the question?

So there are a few messy parts to this bug. The first one is that the mythbuntu installer doesn't propose that question and neither does MCC.

The other part is that when it's posed via debconf, you don't know a lot of the information you need to about the device. We'll see if there is anything more that can be done about all these.

Marking incomplete as this release isn't supported anymore. Can anyone confirm that this issue is still present on a supported Mythbuntu/MythTV release?

Same expired goes for lirc...

..unless there is more input

expiring manually