Mythbuntu Control Centre sets DVICO USB remote to wrong /dev

Bug #718667 reported by John Haywood
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Won't Fix
Undecided
Unassigned

Bug Description

Mythbuntu 9.04 - 10.10 (all versions including 0.24-fixes)

When using Mythbuntu Control Centre to configure a DVICO USB Remote, the lirc configurator incorrectly sets the device to /dev/lircX, whereupon the remote fails to register in irw or mythtv, or any other application

The correct entry should read
 REMOTE_DEVICE="/dev/usb/hiddevX", e.g. REMOTE_DEVICE="/dev/usb/hiddev0"

The full conf file follows:

# /etc/lirc/hardware.conf
 #
 #Chosen Remote Control
 REMOTE="DViCO USB Remote"
 REMOTE_MODULES=""
 REMOTE_DRIVER="dvico"
 REMOTE_DEVICE="/dev/usb/hiddev0"
 REMOTE_SOCKET=""
 REMOTE_LIRCD_CONF="dvico/lircd.conf.fusionHDTV"
 REMOTE_LIRCD_ARGS=""

 #Chosen IR Transmitter
 TRANSMITTER="None"
 TRANSMITTER_MODULES=""
 TRANSMITTER_DRIVER=""
 TRANSMITTER_DEVICE=""
 TRANSMITTER_SOCKET=""
 TRANSMITTER_LIRCD_CONF=""
 TRANSMITTER_LIRCD_ARGS=""

 #Enable lircd
 START_LIRCD="true"

 #Don't start lircmd even if there seems to be a good config file
 #START_LIRCMD="false"

 #Try to load appropriate kernel modules
 LOAD_MODULES="true"

 # Default configuration files for your hardware if any
 LIRCMD_CONF=""

 #Forcing noninteractive reconfiguration
 #If lirc is to be reconfigured by an external application
 #that doesn't have a debconf frontend available, the noninteractive
 #frontend can be invoked and set to parse REMOTE and TRANSMITTER
 #It will then populate all other variables without any user input
 #If you would like to configure lirc via standard methods, be sure
 #to leave this set to "false"
 FORCE_NONINTERACTIVE_RECONFIGURATION="false"
 START_LIRCMD=""

 # Receiver settings required by gnome-lirc-properties
 RECEIVER_MODEL="USB\ Remote"
 RECEIVER_VENDOR="DViCO"

Revision history for this message
Vince McIntyre (vmcintyr) wrote :

Could you post 'lsusb' output? I may have the same hardware and be able to test as well.

Revision history for this message
John Haywood (john-jhit) wrote : Re: [Bug 718667] Re: Mythbuntu Control Centre sets DVICO USB remote to wrong /dev
Download full text (20.0 KiB)

On 28/02/2011, at 1:30 PM, Vince McIntyre wrote:

> Could you post 'lsusb' output? I may have the same hardware and be able
> to test as well.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/718667
>
> Title:
> Mythbuntu Control Centre sets DVICO USB remote to wrong /dev
>
> Status in Mythbuntu, Ubuntu derivative focused upon MythTV:
> New
>
> Bug description:
> Mythbuntu 9.04 - 10.10 (all versions including 0.24-fixes)
>
> When using Mythbuntu Control Centre to configure a DVICO USB Remote,
> the lirc configurator incorrectly sets the device to /dev/lircX,
> whereupon the remote fails to register in irw or mythtv, or any other
> application
>
> The correct entry should read
> REMOTE_DEVICE="/dev/usb/hiddevX", e.g. REMOTE_DEVICE="/dev/usb/hiddev0"
>
> The full conf file follows:
>
> # /etc/lirc/hardware.conf
> #
> #Chosen Remote Control
> REMOTE="DViCO USB Remote"
> REMOTE_MODULES=""
> REMOTE_DRIVER="dvico"
> REMOTE_DEVICE="/dev/usb/hiddev0"
> REMOTE_SOCKET=""
> REMOTE_LIRCD_CONF="dvico/lircd.conf.fusionHDTV"
> REMOTE_LIRCD_ARGS=""
>
> #Chosen IR Transmitter
> TRANSMITTER="None"
> TRANSMITTER_MODULES=""
> TRANSMITTER_DRIVER=""
> TRANSMITTER_DEVICE=""
> TRANSMITTER_SOCKET=""
> TRANSMITTER_LIRCD_CONF=""
> TRANSMITTER_LIRCD_ARGS=""
>
> #Enable lircd
> START_LIRCD="true"
>
> #Don't start lircmd even if there seems to be a good config file
> #START_LIRCMD="false"
>
> #Try to load appropriate kernel modules
> LOAD_MODULES="true"
>
> # Default configuration files for your hardware if any
> LIRCMD_CONF=""
>
> #Forcing noninteractive reconfiguration
> #If lirc is to be reconfigured by an external application
> #that doesn't have a debconf frontend available, the noninteractive
> #frontend can be invoked and set to parse REMOTE and TRANSMITTER
> #It will then populate all other variables without any user input
> #If you would like to configure lirc via standard methods, be sure
> #to leave this set to "false"
> FORCE_NONINTERACTIVE_RECONFIGURATION="false"
> START_LIRCMD=""
>
> # Receiver settings required by gnome-lirc-properties
> RECEIVER_MODEL="USB\ Remote"
> RECEIVER_VENDOR="DViCO"
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/mythbuntu/+bug/718667/+subscribe

Hi Vince,

Of course - first the short version:

tvuser@mythtv:~$ lsusb
Bus 004 Device 002: ID 0fe9:9010 DVICO
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 1241:f728 Belkin
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 05d8:810f Ultima Electronics Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

now the long:

tvuser@mythtv:~$ sudo lsusb -v
[sudo] password for tvuser:

Bus 004 Device 002: ID 0fe9:9010 DVICO
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0...

Revision history for this message
Obleak (fraser-arkhostings) wrote :

confirmed - I had the same issue with my DVICO usb receiver.

/home/media$ lsusb
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 004: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
Bus 004 Device 003: ID 046d:c318 Logitech, Inc. Illuminated Keyboard
Bus 004 Device 002: ID 0fe9:9010 DVICO
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 2040:8400 Hauppauge
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 2040:8400 Hauppauge
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/home/media$ sudo lsusb -v
...
Bus 004 Device 002: ID 0fe9:9010 DVICO
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x0fe9 DVICO
  idProduct 0x9010
  bcdDevice 1.00
  iManufacturer 1 DVICO
  iProduct 2 DVICO USB HID Remocon V1.00
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 41
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 3 Human Interface Device
      bInterfaceSubClass 0 No Subclass
      bInterfaceProtocol 0 None
      iInterface 0
        HID Device Descriptor:
          bLength 9
          bDescriptorType 33
          bcdHID 1.10
          bCountryCode 0 Not supported
          bNumDescriptors 1
          bDescriptorType 34 Report
          wDescriptorLength 73
         Report Descriptors:
           ** UNAVAILABLE **
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0003 1x 3 bytes
        bInterval 32
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0001 1x 1 bytes
        bInterval 32
Device Status: 0x0001
  Self Powered

Revision history for this message
Thomas Mashos (tgm4883) wrote :

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream believes this to be fixed in the latest version. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

Changed in mythbuntu:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.