![]() : Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M <- one bus You can solve the above situation by using an USB 2.0 connection or adding for example a PCI-Express to USB3.0 card: |_ Port 4: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <- 2nd DVB device, shares bandwidth |_ Port 2: Dev 2, If 0, Class=vend., Driver=dvb_usb_ttusb2, 480M <- 1st DVB device, shares bandwidth : Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M <- one bus : Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/8p, 12M <- USB1.1, slow, don't us With this setup you will have bandwidth problems with no appropriate warning whatsoever on any log file. The tuner is a USB 2.0 tuner, so connecting the tuner through an USB 1.1 interface will result in performance issues: In such cases it might be needed to make a workaround with symbolic links, as mentioned in this mail on the linux-media list. with each DVB-C/T tuner having their own frontend devices (/dev/dvb/adaptor0/frontend0 and /dev/dvb/adaptor0/frontend1) while the other devices are shared between the tuners (/dev/dvb/adaptor0/demux0 exists, but there's no demux1). Many applications for DVB playback currently doesn't support the structure of the combined tuner, eg. According to the developer of the driver, the CI should also work fine when using VDR for playback. The CI has been tested to work successfully with a DVB-T Viaccess 4.0 CAM (BoxerTV DK branded) and MythTV (v0.24-0.26) and AlphaCrypt Classic with MythTV 0.24-0.26. Once an application requests to use the CAM, it will wake up and get initialized automatically. dvb_ca adapter 0: Invalid PC card inserted :(īeware that the initialization of the CAM in most cases will fail as seen above ("Invalid PC card inserted") due to the CAM being in sleep-mode. usbcore: registered new interface driver dvb_usb_ttusb2 dvb-usb: Technotrend TT-connect CT-3650 successfully initialized and connected. dvb-usb: schedule remote query interval to 150 msecs. DVB: registering adapter 0 frontend 1 (NXP TDA10048HN DVB-T). DVB: registering adapter 0 frontend 0 (Philips TDA10023 DVB-C). lirc_dev: IR Remote Control driver registered, major 248 IR MCE Keyboard/mouse protocol handler initialized DVB: registering new adapter (Technotrend TT-connect CT-3650) dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. dvb-usb: found a 'Technotrend TT-connect CT-3650' in warm state. usb 2-1.1: new high-speed USB device number 5 using ehci_hcd As of kernel 3.2, the CI interface is now also supported and can be used to decrypt pay-TV with the use of a CAM. Both the DVB-C and DVB-T part of the tuner are supported in current kernels.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |