|
Craig,
I'm using mine a backend so I'm not using the
new ir receiver. I am only using the USB receiver that came with
DIVICO DVB-T into a usb on the frontend. It works great. I can
see the ir receiver message on the backend but I won't have time to
investigate and plug in the receiver until the weekend (The hole in the card for
the ir receiver is partially covered by the chassis).
-Stephen
----- Original Message -----
Sent: Thursday, February 23, 2006 9:23
PM
Subject: Dvico Fusion Dual
Digital lircd problem
>lirc expects the DVICO to have /dev/usb/hiddev0 as the device interface. Mine creates /dev/hiddev0 so I had to create a rc.local entry to create the /dev/usb directory and then link the /dev/hiddev0 to it. You may also try irrecord and see if you get any output as you can specify the device directly.
I have seen other references to /dev/usb/hiddev0, but my system (FC4) does not have /dev/usb, or /dev/hiddev*
Any tips on how to identify what the devices shows up as?
from
dmesg after I connected the USB:
usb 1-4: new high speed USB device
using ehci_hcd and address 3
dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual
USB' in cold state, will try to load a firmware
dvb-usb: downloading
firmware from file 'dvb-usb-bluebird-01.fw'
usbcore: registered new driver
dvb_usb_cxusb
usb 1-4: USB disconnect, address 3
dvb-usb: generic
DVB-USB module successfully deinitialized and disconnected.
usb 1-4: new
high speed USB device using ehci_hcd and address 4
dvb-usb: found a 'DViCO
FusionHDTV DVB-T Dual USB' in warm state.
dvb-usb: will pass the complete
MPEG2 transport stream to the software demuxer.
DVB: registering new
adapter (DViCO FusionHDTV DVB-T Dual USB).
dvb-usb: recv bulk message
failed: -110
DVB: registering frontend 1 (Zarlink MT352 DVB-T)...
input:
IR-receiver inside an USB DVB receiver as /class/input/input2
dvb-usb:
schedule remote query interval to 150 msecs.
dvb-usb: DViCO FusionHDTV
DVB-T Dual USB successfully initialized and connected.
Before I
plugged the card into usb I had these devices
/dev/us*
usbdev1.1 usbdev2.1
usbdev3.1 usbdev3.2 usbdev4.1
After I plugged the card in I had these
/dev/us*
usbdev1.1 usbdev1.4
usbdev2.1 usbdev3.1
usbdev3.2 usbdev4.1
I looked for
/class/input/input2 and came up with this:
[root@localhost input2]#
pwd
/sys/class/input/input2
[root@localhost input2]#
ls
capabilities event2 id name phys
uevent uniq
[root@localhost input2]# cat name
IR-receiver inside
an USB DVB receiver
[root@localhost input2]# cat phys
/ir0
I
don't have /ir0, it looks like it has not been detected/linked
correctly...
[root@localhost input1]#
pwd
/sys/class/input/input1
[root@localhost input1]# cat
name
Logitech Optical USB Mouse
[root@localhost input1]# cat
phys
usb-0000:00:1d.1-1/input0
Any other
ideas?
Thanks
Craig Cook
Relax. Yahoo! Mail virus
scanning helps detect nasty viruses!
_______________________________________________
linux-dvb mailing
list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
|
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
