Skip to contentSkip to conversation

DiBcom adapter problems

DISCUSSION Rodolfo Timoteo da Silva 2 participants 6 messages Jun 17, 2012 – Jun 22, 2012 Media (V4L/DVB)

lore
Share & tools
lore

Rodolfo Timoteo da Silva

author
#0 lore raw

Hi, every time that i try to syntonize DVB-T channels i receive a message in kernel like in log1.txt arch.

There are in log2.txt some usefull information about the device.

My kernel/system is:

Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3 (Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012

Best Regards

dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dvb_frontend_ioctl_legacy: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0
dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0

usb 2-1.2: new high-speed USB device number 4 using ehci_hcd
usb 2-1.2: New USB device found, idVendor=10b8, idProduct=1fa0
usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1.2: Product: STK8096GP
usb 2-1.2: Manufacturer: DiBcom
usb 2-1.2: SerialNumber: 1
dvb-usb: found a 'DiBcom STK8096GP reference design' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
dib0700: firmware started successfully.
dvb-usb: found a 'DiBcom STK8096GP reference design' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (DiBcom STK8096GP reference design)
DVB: registering adapter 0 frontend 0 (DiBcom 8000 ISDB-T)...
DiB0090: successfully identified
Registered IR keymap rc-dib0700-rc5
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/rc/rc0/input14
rc0: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/rc/rc0
dvb-usb: schedule remote query interval to 50 msecs.
dvb-usb: DiBcom STK8096GP reference design successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_dib0700

Bus 002 Device 004: ID 10b8:1fa0 DiBcom
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00

  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x10b8 DiBcom
  idProduct          0x1fa0 
  bcdDevice            1.00
  iManufacturer           1 DiBcom
  iProduct                2 STK8096GP
  iSerial                 3 1
  bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 46
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 4
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00

  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0

bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)

#1 lore raw

Hello,
can you provide more information:
- kernel version
- more log information (not only the error message but also the log from the beginning, when you plug the device) with:
* the debug parameter of the dib8000 module set to 1
* the frontend_debug parameter of the dvb-core module set to 1
- which application do you use to tune the board

regards,
Olivier
________________________________________
From: [email protected] [[email protected]] On Behalf Of Rodolfo Timoteo da Silva [[email protected]]
Sent: Sunday, June 17, 2012 3:58 PM
To: [email protected]
Subject: DiBcom adapter problems

Hi, every time that i try to syntonize DVB-T channels i receive a message in kernel like in log1.txt arch.

There are in log2.txt some usefull information about the device.

My kernel/system is:

Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3 (Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012

Best Regards

author
#2 lore raw

Ok, my kernel versions are 3.4.2 and 3.4.3.

The apps used to tune are

media-tv/w_scan - http://wirbel.htpc-forum.de/w_scan/index2.html
media-tv/linuxtv-dvb-apps (dvbscan) - http://www.linuxtv.org/
media-video/vlc - http://www.videolan.org/vlc/
media-video/kaffeine - http://kaffeine.kde.org/

A six month later i've already created a channels.conf and still working with vlc.

A question: How to set debug parameter using modprobe?

Something like, "modrobe dib8000 debug=1; modprobe dvb-core debug=1"?

Thanks for now.

Em 19-06-2012 12:43, Olivier GRENIE escreveu:

Quoted 29 lines

Hello,
can you provide more information:
- kernel version
- more log information (not only the error message but also the log from the beginning, when you plug the device) with:
* the debug parameter of the dib8000 module set to 1
* the frontend_debug parameter of the dvb-core module set to 1
- which application do you use to tune the board

regards,
Olivier
________________________________________
From: [email protected] [[email protected]] On Behalf Of Rodolfo Timoteo da Silva [[email protected]]
Sent: Sunday, June 17, 2012 3:58 PM
To: [email protected]
Subject: DiBcom adapter problems

Hi, every time that i try to syntonize DVB-T channels i receive a message in kernel like in log1.txt arch.

There are in log2.txt some usefull information about the device.

My kernel/system is:

Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3 (Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012

Best Regards

Signature · 7 lines
---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: [email protected]
skype: zhushazang

Ribeirão Preto - SP

TV CLUBE HD:485142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:0:0:59776 TV CLUBE MOVEL:485142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:0:0:59800 EP HD:641142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:273:274:59520 EPTV1Seg:641142857:INVERSION_AUTO:BANDWIDTH_6_MHZ:FEC_AUTO:FEC_AUTO:QAM_AUTO:TRANSMISSION_MODE_AUTO:GUARD_INTERVAL_AUTO:HIERARCHY_NONE:529:530:59544

#3 lore raw

Hello,
can you test the following patch.

regards,
Olivier

From: Olivier Grenie <[email protected]>
Date: Thu, 21 Jun 2012 18:57:14 +0200
Subject: [PATCH] [media] dvb frontend core: tuning in ISDB-T using DVB API v3
The intend of this patch is to be able to tune ISDB-T using
the DVB API v3

Signed-off-by Olivier Grenie <[email protected]>
---
 drivers/media/dvb/dvb-core/dvb_frontend.c |    7 +++++++
 1 file changed, 7 insertions(+)
drivers/media/dvb/dvb-core/dvb_frontend.c +7 -0
index aebcdf2..ee1cc10 100644
@@ -1531,6 +1531,13 @@ static int set_delivery_system(struct dvb_frontend *fe, u32 desired_system)
                                delsys = desired_system;
                                break;
                        }
+
+                       /* check if the fe delivery system corresponds
+                          to the delivery system in cache */
+                       if (fe->ops.delsys[ncaps] == c->delivery_system) {
+                               delsys = c->delivery_system;
+                               break;
+                       }
                        ncaps++;
                }
                if (delsys == SYS_UNDEFINED) {
Signature · 29 lines
1.7.9.5

________________________________________
From: Zhu Sha Zang [[email protected]]
Sent: Thursday, June 21, 2012 2:59 PM
To: [email protected]
Cc: Olivier GRENIE
Subject: Re: DiBcom adapter problems

Ok, my kernel versions are 3.4.2 and 3.4.3.

The apps used to tune are

media-tv/w_scan - http://wirbel.htpc-forum.de/w_scan/index2.html
media-tv/linuxtv-dvb-apps (dvbscan) - http://www.linuxtv.org/
media-video/vlc - http://www.videolan.org/vlc/
media-video/kaffeine - http://kaffeine.kde.org/

A six month later i've already created a channels.conf and still working
with vlc.

A question: How to set debug parameter using modprobe?

Something like, "modrobe dib8000 debug=1; modprobe dvb-core debug=1"?


Thanks for now.

Em 19-06-2012 12:43, Olivier GRENIE escreveu:
Quoted 21 lines

Hello,
can you provide more information:
- kernel version
- more log information (not only the error message but also the log from the beginning, when you plug the device) with:
* the debug parameter of the dib8000 module set to 1
* the frontend_debug parameter of the dvb-core module set to 1
- which application do you use to tune the board

regards,
Olivier
________________________________________
From: [email protected] [[email protected]] On Behalf Of Rodolfo Timoteo da Silva [[email protected]]
Sent: Sunday, June 17, 2012 3:58 PM
To: [email protected]
Subject: DiBcom adapter problems

Hi, every time that i try to syntonize DVB-T channels i receive a message in kernel like in log1.txt arch.

There are in log2.txt some usefull information about the device.

Quoted 8 lines

My kernel/system is:

Linux version 3.4.2-gentoo-r1-asgard (root@asgard) (gcc version 4.6.3 (Gentoo 4.6.3 p1.3, pie-0.5.2) ) #1 SMP PREEMPT Thu Jun 14 07:45:19 BRT 2012

Best Regards

--

---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: [email protected]
skype: zhushazang

Ribeirão Preto - SP

author
#4 lore raw

Excuse me, dumb question, but where and how can i apply this patch?

Thanks again!

Em 21-06-2012 14:07, Olivier GRENIE escreveu:

Quoted 36 lines

Hello,
can you test the following patch.

regards,
Olivier

From: Olivier Grenie <[email protected]>
Date: Thu, 21 Jun 2012 18:57:14 +0200
Subject: [PATCH] [media] dvb frontend core: tuning in ISDB-T using DVB API v3
The intend of this patch is to be able to tune ISDB-T using
the DVB API v3

Signed-off-by Olivier Grenie <[email protected]>
---
  drivers/media/dvb/dvb-core/dvb_frontend.c |    7 +++++++
  1 file changed, 7 insertions(+)
drivers/media/dvb/dvb-core/dvb_frontend.c +7 -0
index aebcdf2..ee1cc10 100644
@@ -1531,6 +1531,13 @@ static int set_delivery_system(struct dvb_frontend *fe, u32 desired_system)
                                 delsys = desired_system;
                                 break;
                         }
+
+                       /* check if the fe delivery system corresponds
+                          to the delivery system in cache */
+                       if (fe->ops.delsys[ncaps] == c->delivery_system) {
+                               delsys = c->delivery_system;
+                               break;
+                       }
                         ncaps++;
                 }
                 if (delsys == SYS_UNDEFINED) {
Signature · 7 lines
---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: [email protected]
skype: zhushazang

Ribeirão Preto - SP
#5 lore raw

You need to get the source code of your kernel, apply the path and recompile the kernel. There is another solution by compiling the module externally (http://git.linuxtv.org/media_build.git). You will also need to patch it.

regards,
Olivier
________________________________________
From: Zhu Sha Zang [[email protected]]
Sent: Friday, June 22, 2012 2:15 PM
To: [email protected]
Cc: Olivier GRENIE
Subject: Re: DiBcom adapter problems

Excuse me, dumb question, but where and how can i apply this patch?

Thanks again!

Em 21-06-2012 14:07, Olivier GRENIE escreveu:

Quoted 26 lines

Hello,
can you test the following patch.

regards,
Olivier

From: Olivier Grenie <[email protected]>
Date: Thu, 21 Jun 2012 18:57:14 +0200
Subject: [PATCH] [media] dvb frontend core: tuning in ISDB-T using DVB API v3
The intend of this patch is to be able to tune ISDB-T using
the DVB API v3

Signed-off-by Olivier Grenie <[email protected]>
---
  drivers/media/dvb/dvb-core/dvb_frontend.c |    7 +++++++
  1 file changed, 7 insertions(+)
drivers/media/dvb/dvb-core/dvb_frontend.c +0 -0
index aebcdf2..ee1cc10 100644
@@ -1531,6 +1531,13 @@ static int set_delivery_system(struct dvb_frontend *fe, u32 desired_system)
                                 delsys = desired_system;
                                 break;
                         }

drivers/media/dvb/dvb-core/dvb_frontend.c static int set_delivery_system(struct dvb_frontend *fe, u32 desired_system) · line 1543

Quoted 10 lines
drivers/media/dvb/dvb-core/dvb_frontend.c +7 -0
+
+                       /* check if the fe delivery system corresponds
+                          to the delivery system in cache */
+                       if (fe->ops.delsys[ncaps] == c->delivery_system) {
+                               delsys = c->delivery_system;
+                               break;
+                       }
                         ncaps++;
                 }
                 if (delsys == SYS_UNDEFINED) {

--

---
Rodolfo Timóteo da Silva
Linux Counter: 359362
msn: [email protected]
skype: zhushazang

Ribeirão Preto - SP