Page 5 of 20 FirstFirst ... 3456715 ... LastLast
Results 41 to 50 of 198

Thread: HOWTO: DViCO FusionHDTV DVB-T Dual Digital 4 with remote tutorial

  1. #41
    Join Date
    Nov 2008
    Beans
    11

    Help: remote won't work

    Hi,

    Thanks for the guide, it got my Fusion DD4 tuner working great on Mythbuntu 8.10. Now I'm stuck trying to get the remote to work! I have one of these.

    The problem I have is that only a few keys in the remote work (arrow keys, enter key) and they are obviously not being interpreted by lirc because when I stop lirc the keys still work.

    I followed the guide exactly, including the step about modifying /usr/share/hal/fdi/preprobe/20thirdparty/lirc.fdi as suggested by askvictor.

    One thing that looks kind of different in my system is that the device is reported by dmesg as "/devices/pci0000:00/0000:00:08.0/0000:01:06.2/usb5/5-1/input/input5" rather than "/class/input/input5" as suggested by other posters.

    Any ideas?

    irw doesn's print anything, irrecord times out, cat /dev/input/input5 prints nothing.

    Here's some relevant prints.

    Code:
    tom@mythbox:~$ ls -l /dev/input/
    total 0
    drwxr-xr-x 2 root root     60 2008-11-22 14:58 by-path
    crw-rw---- 1 root root 13, 64 2008-11-22 14:58 event0
    crw-rw---- 1 root root 13, 65 2008-11-22 14:58 event1
    crw-rw---- 1 root root 13, 66 2008-11-22 14:58 event2
    crw-rw---- 1 root root 13, 67 2008-11-22 14:58 event3
    crw-rw---- 1 root root 13, 68 2008-11-22 14:58 event4
    crw-rw---- 1 root root 13, 69 2008-11-22 14:58 event5
    lrwxrwxrwx 1 root root      6 2008-11-22 14:58 irremote -> event5
    crw-rw---- 1 root root 13, 63 2008-11-22 14:58 mice
    crw-rw---- 1 root root 13, 32 2008-11-22 14:58 mouse0
    
    tom@mythbox:~$ dmesg | grep "IR-receiver"
    [   10.220648] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:08.0/0000:01:06.2/usb5/5-1/input/input4
    [   10.622795] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:08.0/0000:01:06.2/usb5/5-2/input/input5
    
    tom@mythbox:~$ hal-device
    
    22: udi = '/org/freedesktop/Hal/devices/temp/92'
      input.originating_device = '/org/freedesktop/Hal/devices/usb_device_fe9_db98_000080f2'  (string)
      linux.device_file = '/dev/input/event5'  (string)
      linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:08.0/0000:01:06.2/usb5/5-2/input/input5/event5'  (string)
      info.subsystem = 'input'  (string)
      info.ignore = true  (bool)
      info.parent = '/org/freedesktop/Hal/devices/usb_device_fe9_db98_000080f2'  (string)
      info.product = 'Ignored Device'  (string)
      info.udi = '/org/freedesktop/Hal/devices/ignored-device'  (string)
      linux.hotplug_type = 2  (0x2)  (int)
      linux.subsystem = 'input'  (string)
      input.device = '/dev/input/event5'  (string)
      input.product = 'IR-receiver inside an USB DVB receiver'  (string)
    
    
    27: udi = '/org/freedesktop/Hal/devices/temp/87'
      input.originating_device = '/org/freedesktop/Hal/devices/usb_device_fe9_db98_000000f2'  (string)
      linux.device_file = '/dev/input/event4'  (string)
      linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:08.0/0000:01:06.2/usb5/5-1/input/input4/event4'  (string)
      info.subsystem = 'input'  (string)
      info.ignore = true  (bool)
      info.parent = '/org/freedesktop/Hal/devices/usb_device_fe9_db98_000000f2'  (string)
      info.product = 'Ignored Device'  (string)
      info.udi = '/org/freedesktop/Hal/devices/ignored-device'  (string)
      linux.hotplug_type = 2  (0x2)  (int)
      linux.subsystem = 'input'  (string)
      input.device = '/dev/input/event4'  (string)
      input.product = 'IR-receiver inside an USB DVB receiver'  (string)
    Last edited by tvars; November 22nd, 2008 at 05:23 AM. Reason: added remote type

  2. #42
    Join Date
    Nov 2008
    Beans
    11

    Smile Fixed

    Ok I fixed my remote.

    Here's a summary of the problems I had.

    1) I had to update /usr/share/hal/fdi/preprobe/20thirdparty/lirc.fdi to stop my remote key-presses being interpreted as keyboard presses. Added the following match xml element.

    Code:
         <match key="info.product" contains_ncase="IR-receiver inside an USB DVB receiver">
            <merge key="info.ignore" type="bool">true</merge>
         </match>
    2) I have two IR-receiver devices, event4 and event5. The rule to create a symlink /dev/input/irremote on boot was always picking up event5. "sudo cat /dev/input/eventX" and pressing buttons on the remote did not give any output for event5, but it did for event4. I switched my /etc/lirc/hardware.conf to point directly at event4 without going through the irremote symlink.

    3) Lastly, the lircd.conf that is attached to this thread (lirc2.tar.bz2) did not match the codes for my remote. I had to record a new one using "sudo irrecord --driver=devinput --device=/dev/input/event4 lircd.conf". I've attached the resulting file to this post. I must have a newer version of this remote.

    4) I had a problem with remote key presses being duplicated. irw showed two lines per keypress. I fixed this by setting "toggle_bit_mask 0x16000000" in the lircd.conf.
    Attached Files Attached Files

  3. #43
    Join Date
    Oct 2007
    Beans
    206

    Re: Fixed

    Quote Originally Posted by tvars View Post
    Ok I fixed my remote.

    Here's a summary of the problems I had.

    1) I had to update /usr/share/hal/fdi/preprobe/20thirdparty/lirc.fdi to stop my remote key-presses being interpreted as keyboard presses. Added the following match xml element.

    Code:
         <match key="info.product" contains_ncase="IR-receiver inside an USB DVB receiver">
            <merge key="info.ignore" type="bool">true</merge>
         </match>
    2) I have two IR-receiver devices, event4 and event5. The rule to create a symlink /dev/input/irremote on boot was always picking up event5. "sudo cat /dev/input/eventX" and pressing buttons on the remote did not give any output for event5, but it did for event4. I switched my /etc/lirc/hardware.conf to point directly at event4 without going through the irremote symlink.

    3) Lastly, the lircd.conf that is attached to this thread (lirc2.tar.bz2) did not match the codes for my remote. I had to record a new one using "sudo irrecord --driver=devinput --device=/dev/input/event4 lircd.conf". I've attached the resulting file to this post. I must have a newer version of this remote.

    4) I had a problem with remote key presses being duplicated. irw showed two lines per keypress. I fixed this by setting "toggle_bit_mask 0x16000000" in the lircd.conf.
    thank you very much for this post can i ask what your remote looks like can you post a link to a photo does it look like one of the pics i have posted if so can you point it out

  4. #44
    Join Date
    Nov 2008
    Beans
    11

    Re: Fixed

    Quote Originally Posted by oobe-feisty View Post
    thank you very much for this post can i ask what your remote looks like can you post a link to a photo does it look like one of the pics i have posted if so can you point it out
    My remote looks like this one.

  5. #45
    Join Date
    Oct 2007
    Beans
    206

    Re: HOWTO: DViCO FusionHDTV DVB-T Dual Digital 4 with remote tutorial

    thanks tvars i will update my attached lirc files with yours soon if you dont mind i appreciate this post as i have the old remote and have no way of supporting or testing your remote

  6. #46
    Join Date
    Nov 2008
    Beans
    1

    Re: HOWTO: DViCO FusionHDTV DVB-T Dual Digital 4 with remote tutorial

    I have a question if anyone can help:

    I have installed the card as per the OP on Mythbuntu 8.04 and 8.10 (and I previously had it working fine on 7.10). Using tzap I can see all the channels locking correctly (and with mplayer can view them). However within MythTV some of the channels (that scan fine) just won't lock when I try to play them back.

    Anyone have any ideas?

  7. #47
    Join Date
    Apr 2008
    Beans
    32

    Re: HOWTO: DViCO FusionHDTV DVB-T Dual Digital 4 with remote tutorial

    Quote Originally Posted by Mr_Q View Post
    I have a question if anyone can help:

    I have installed the card as per the OP on Mythbuntu 8.04 and 8.10 (and I previously had it working fine on 7.10). Using tzap I can see all the channels locking correctly (and with mplayer can view them). However within MythTV some of the channels (that scan fine) just won't lock when I try to play them back.

    Anyone have any ideas?
    I'm curious if it's the same problem I experienced here:
    http://ubuntuforums.org/showthread.p...30#post6188530
    which I fixed here:
    http://ubuntuforums.org/showthread.p...42#post6215542

    The other thing you could try is to increase the tuning delay (I think that's what it's called) in the advanced settings for the capture card in the backend setup. I think the default values are something like 500ms and 3000ms; in previous installations I've increased them to 1000ms and 6000ms.

  8. #48
    Join Date
    Oct 2008
    Beans
    3

    Re: HOWTO: DViCO FusionHDTV DVB-T Dual Digital 4 with remote tutorial

    hi guys

    first of all thanks in advance for your help.

    SO i'm trying to get this cardworking and just upgraded to 8.10

    ubuntu recognise the card but it seems it only sees one card. My /dev/dvb/ only sees one adapter0, and mythbackend setup only allows me to create one card.

    i've posted some info below so any help is appreciated.

    LSUSB

    Bus 004 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 003 Device 006: ID 0fe9:db78 DVICO
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 003: ID 04b3:3108 IBM Corp. 800dpi Optical Mouse w/ Scroll Point
    Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub



    dmesg

    [ 14.770760] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state.
    [ 14.771086] dvb-usb: will pass the complete MPEG2 transport stream to the sof tware demuxer.
    [ 14.771141] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 177.80 Wed Oct 1 14:43:46 PDT 2008
    [ 14.792055] input: PC Speaker as /devices/platform/pcspkr/input/input5
    [ 14.802088] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual Digital 4)
    [ 14.889549] cxusb: No IR receiver detected on this device.
    [ 14.889557] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
    [ 14.909384] xc2028 2-0061: creating new instance
    [ 14.909389] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
    [ 14.910050] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initi alized and connected.
    [ 14.910092] usbcore: registered new interface driver dvb_usb_cxusb
    [ 16.328048] lp0: using parport0 (interrupt-driven).
    [ 16.548513] Adding 3012148k swap on /dev/sdb5. Priority:-1 extents:1 across: 3012148k

  9. #49
    Join Date
    Oct 2007
    Beans
    206

    Re: HOWTO: DViCO FusionHDTV DVB-T Dual Digital 4 with remote tutorial

    Quote Originally Posted by smeago1 View Post
    hi guys

    first of all thanks in advance for your help.

    SO i'm trying to get this cardworking and just upgraded to 8.10

    ubuntu recognise the card but it seems it only sees one card. My /dev/dvb/ only sees one adapter0, and mythbackend setup only allows me to create one card.

    i've posted some info below so any help is appreciated.

    LSUSB

    Bus 004 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 003 Device 006: ID 0fe9:db78 DVICO
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 003: ID 04b3:3108 IBM Corp. 800dpi Optical Mouse w/ Scroll Point
    Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub



    dmesg

    [ 14.770760] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state.
    [ 14.771086] dvb-usb: will pass the complete MPEG2 transport stream to the sof tware demuxer.
    [ 14.771141] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 177.80 Wed Oct 1 14:43:46 PDT 2008
    [ 14.792055] input: PC Speaker as /devices/platform/pcspkr/input/input5
    [ 14.802088] DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual Digital 4)
    [ 14.889549] cxusb: No IR receiver detected on this device.
    [ 14.889557] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
    [ 14.909384] xc2028 2-0061: creating new instance
    [ 14.909389] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
    [ 14.910050] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initi alized and connected.
    [ 14.910092] usbcore: registered new interface driver dvb_usb_cxusb
    [ 16.328048] lp0: using parport0 (interrupt-driven).
    [ 16.548513] Adding 3012148k swap on /dev/sdb5. Priority:-1 extents:1 across: 3012148k


    read the trouble shooting part of the first post it covers this

    try shutting down you your computer as in not rebooting but shutting down that will work

  10. #50
    Join Date
    Dec 2008
    Beans
    2

    Re: HOWTO: DViCO FusionHDTV DVB-T Dual Digital 4 with remote tutorial

    Howdy from a linux noob!

    I'm trying to get a Rev 2 ( db98 ) card to work on Mythbuntu 8.10.

    But, "the specified repository "v4l-dvb" is unknown, sorry."

    Where do i go now?

    BTW, "lsusb" correctly displays the two DVICO devices, "dmesg|grep dvb" and "dmesg|grep error" both return nothing.

    Thanks in advance,
    OzDude

Page 5 of 20 FirstFirst ... 3456715 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •