DVB-C (CT-3650) with german KabelBW provider under freebsd

Sat Apr 21 10:08:39 UTC 2012

Hi Jürgen,

thx for the tipps you provided. I was busy last week so I just started looking into it again.

Am 15.04.2012 um 16:49 schrieb Juergen Lock:

> On Sat, Apr 14, 2012 at 03:41:46PM +0200, Christian Kniep wrote:
>> Hey fellows,
> Hi!
>> 
>> I am a fresh starter with freebsd but I am pretty exited about it the last couple of days.
>> I bought a N36L from HP and it fits my needs perfectly.
>> 4x2TB as raidz1 (previously on debian with zfs-fuse) and a couple of services I am playing around with.
>> 
>> My current problem is that I can't bring the CT-3650 I bought to work with vdr-1.7.
>> webcamd finds them and the device is created, but I could not get any DVB-C bouqet.
>> I try to debug this by adding some parameters, but besides the "Creating*"-output I failed.
>> 
>> # webcamd -m dvb-ttusb-budget.debug=1 dvb_frontend.frontend_debug=1 dvb-pll.debug=1 ttusb_dec.debug=1 dvb-usb-init.debug=31
>> Attached ugen1.4[0] to cuse unit 0
>> Creating /dev/dvb/adapter0/demux0
>> Creating /dev/dvb/adapter0/dvr0
>> Creating /dev/dvb/adapter0/frontend0
>> Creating /dev/input/event0
>> 
> To see driver messages here you need to build the webcamd port with the
> DEBUG knob enabled.
With the new webcamd-version build (without vTuner) I got
paso# pwd
/root/ports/multimedia/webcamd
paso# cat distinfo 
SHA256 (webcamd-3.4.0.1.tar.bz2) = b069d99e521392d5afc771229efa779a5050a7dbfd3f86f24ff05e3f4154e6c2
SIZE (webcamd-3.4.0.1.tar.bz2) = 9128935
paso# webcamd 
lirc_dev: IR Remote Control driver registered, major 14 
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR SANYO protocol handler initialized
IR LIRC bridge handler initialized
Linux video capture interface: v2.00
Em28xx: Initialized (Em28xx dvb Extension) extension
USBVision USB Video Device Driver for Linux : 0.9.11
pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
pvrusb2: Debug mask is 31 (0x1f)
cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
au0828 driver loaded
uvcvideo: Unable to create debugfs directory
USB Video Class driver (1.1.1)
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
Attached ugen1.4[0] to cuse unit 0
dvb-usb: found a 'Technotrend TT-connect CT-3650' in warm state.
dvb-usb: bulk message failed: -32 (4/0)
ttusb2: there might have been an error during control message transfer. (rlen = 0, was 0)
dvb-usb: bulk message failed: -32 (5/0)
ttusb2: there might have been an error during control message transfer. (rlen = 0, was 0)
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Technotrend TT-connect CT-3650)
dvb-usb: bulk message failed: -32 (9/0)
ttusb2: there might have been an error during control message transfer. (rlen = 3, was 0)
ttusb2: i2c transfer failed.
DVB: TDA10023(-1): tda10023_writereg, writereg error (reg == 0x00, val == 0x33, ret == 0)
dvb-usb: bulk message failed: -32 (8/0)
ttusb2: there might have been an error during control message transfer. (rlen = 4, was 0)
ttusb2: i2c transfer failed.
DVB: TDA10023(-1): tda10023_readreg: readreg error (reg == 0x1a, ret == 0)
dvb-usb: no frontend was attached by 'Technotrend TT-connect CT-3650'
Registered IR keymap rc-tt-1500
rc0: IR-receiver inside an USB DVB receiver as webcamd
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: bulk message failed: -32 (4/0)
ttusb2: there might have been an error during control message transfer. (rlen = 0, was 0)
dvb-usb: bulk message failed: -32 (4/0)
ttusb2: there might have been an error during control message transfer. (rlen = 9, was 0)
dvb-usb: error -5 while querying for an remote control event.
dvb-usb: bulk message failed: -32 (5/0)
ttusb2: there might have been an error during control message transfer. (rlen = 0, was 0)
dvb-usb: Technotrend TT-connect CT-3650 successfully initialized and connected.
Creating /dev/dvb/adapter0/demux0
Creating /dev/dvb/adapter0/dvr0
Creating /dev/input/event0
dvb-usb: bulk message failed: -32 (4/0)
ttusb2: there might have been an error during control message transfer. (rlen = 9, was 0)
dvb-usb: error -5 while querying for an remote control event.
dvb-usb: bulk message failed: -32 (4/0)

Are the error messages showstopper I have to solve first?

> 
>> On my debian machine the DVB-box works fine. I also have DVB-S boxes, but no dish to test it.
>> I entertain suspicion that the DVB-CT box (it is for DVB-T and DVB-C) thinks it has to tune for DVB-T and not DVB-C.
>> But I am not sure.
>> 
> Well I doubt it's that but...
> 
>> Anyone who can give me a hint?
>> Christian
>> 
>> PS: This went on for hours, even if the link specify that there should be channels waiting.
>> http://kbwhelpdesk.script-ecke.de/index_druck.php?site=digitalbelegung&art=technik&gebiet=A&servicetyp=FTA
>> # w_scan -f c -R 0 -E 0 -o 7 -Q 1 -S 0 >> channels.conf
>> w_scan version 20111203 (compiled for DVB API 5.1)
>> WARNING: could not guess your country. Falling back to 'DE'
>> guessing country 'DE', use -c <country> to override
>> using settings for GERMANY
>> DVB cable
>> DVB-C
>> frontend_type DVB-C, channellist 7
>> output format vdr-1.7
>> WARNING: could not guess your codepage. Falling back to 'UTF-8'
>> output charset 'UTF-8', use -C <charset> to override
>> Info: using DVB adapter auto detection.
>>        /dev/dvb/adapter0/frontend0 -> DVB-C "Philips TDA10023 DVB-C": good :-)
>> Using DVB-C frontend (adapter /dev/dvb/adapter0/frontend0)
>> -_-_-_-_ Getting frontend capabilities-_-_-_-_
>> Using DVB API 5.2
>> frontend 'Philips TDA10023 DVB-C' supports
>> INVERSION_AUTO
>> QAM_AUTO not supported, trying QAM_256.
>> FEC_AUTO
>> FREQ (55.00MHz ... 860.00MHz)
>> SRATE (0.458MBd ... 7.333MBd)
>> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
>> searching QAM256...
>> 73000: sr6900 (time: 00:01) 
> 
> OK I never could test DVB-C (only have -S2 and -T here), but I
> remember there was a dvb api change concerning hybrid tuners which
> the CT-3650 seems to be:
> 
> 	http://linuxtv.org/wiki/index.php/TechnoTrend_TT-connect_CT-3650_CI
> 
> ..so it's possible you either need the symlinks mentioned in this
> posting,
> 
> 	http://www.mail-archive.com/linux-media@vger.kernel.org/msg43015.html
> 
> or since we still have the old v4l_compat headers in ports you
> actually need to test with those headers and apps updated:
> 
> 1. v4l_compat update:
> 
> 	http://lists.freebsd.org/pipermail/freebsd-multimedia/2012-February/012847.html
> 
> 2. w_scan 20120128 update: (needs updated v4l_compat)
> 
> 	http://people.freebsd.org/~nox/tmp/w_scan-20120128-newv4lcompat.patch
> 
> 3. vdr 1.7.27 update: (maybe no point in testing this if the updated
>   w_scan still fails, tho you could test scanning using the
>   reelchannelscan or wirbelscan plugins too; comment out PATCH_SITES
>   PATCHFILES PATCH_DIST_STRIP in multimedia/vdr/Makefile to build
>   with new v4l_compat headers, and if you want a correct plist
>   also remove include/vdr/s2apiwrapper.h from multimedia/vdr/pkg-plist.)
> 
> 	http://people.freebsd.org/~nox/tmp/vdr-ports-1.7.27-009.shar
> 
> 4. webcamd 3.4.0.1 update: (may not be needed but might still possibly help)
> 
> 	http://lists.freebsd.org/pipermail/freebsd-multimedia/2012-March/012905.html
> 
> Good luck! :)
> 	Juergen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.freebsd.org/pipermail/freebsd-multimedia/attachments/20120421/3125fccb/signature.pgp