From jajcus at jajcus.net Sat Jan 5 14:58:55 2013 From: jajcus at jajcus.net (Jacek Konieczny) Date: Sat, 5 Jan 2013 14:58:55 +0100 Subject: [linux-dvb] Problem with 'NOT Only TV DVB-T USB Deluxe" Message-ID: <20130105145855.75998a29@lolek.nigdzie> Hi, I have a 'NOT Only TV DVB-T USB Deluxe' tuner device: Model name: LV5TDLX DVB-T USB P/N: STLV5TDLXT702 S/N: LV5TDLX120700116 USB ID: 1f4d:c803 This is based on the RTL2838UHIDIR chip with e4000 tuner (at least, that is detected by various drivers). I had some minor success with it with some old 3.x kernel and the drivers from: https://github.com/tmair/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 This stopped working with kernel 3.5 and would not even build with newer kernels. Then I tried drivers from linuxtv.org, with little success. The RTL2838u driver has been recently included in the upstream kernel (3.7), so I have tried that. The hardware is detected, but I am not able to tune in. The signal is good - tested with my TV set. The USB tuner device is also OK, I have tried it with Windows and the software provided with the device and the same channels are available as on the TV. So the driver must be broken. Any ideas how can I debug or fix that? dmesg: > [ 3336.916384] usb 2-4: new high-speed USB device number 7 using ehci_hcd > [ 3337.051822] usb 2-4: New USB device found, idVendor=1f4d, idProduct=c803 > [ 3337.051829] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [ 3337.051835] usb 2-4: Product: RTL2838UHIDIR > [ 3337.051839] usb 2-4: Manufacturer: Realtek > [ 3337.051843] usb 2-4: SerialNumber: 00000001 > [ 3337.072145] usb 2-4: dvb_usb_v2: found a 'Trekstor DVB-T Stick Terres 2.0' in warm state > [ 3337.072194] usbcore: registered new interface driver dvb_usb_rtl28xxu > [ 3337.136867] usb 2-4: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer > [ 3337.136886] DVB: registering new adapter (Trekstor DVB-T Stick Terres 2.0) > [ 3337.147449] usb 2-4: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))... > [ 3337.163939] i2c i2c-7: e4000: Elonics E4000 successfully identified > [ 3337.174823] Registered IR keymap rc-empty > [ 3337.174928] input: Trekstor DVB-T Stick Terres 2.0 as /devices/pci0000:00/0000:00:1d.7/usb2/2-4/rc/rc0/input15 > [ 3337.174989] rc0: Trekstor DVB-T Stick Terres 2.0 as /devices/pci0000:00/0000:00:1d.7/usb2/2-4/rc/rc0 > [ 3337.174994] usb 2-4: dvb_usb_v2: schedule remote query interval to 400 msecs > [ 3337.187693] usb 2-4: dvb_usb_v2: 'Trekstor DVB-T Stick Terres 2.0' successfully initialized and connected Scanning on one of the available channels: > # tzap -r "TVP2" > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > reading channels from file '/root/.tzap/channels.conf' > tuning to 746000000 Hz > video pid 0x00ca, audio pid 0x00cb > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 008c | ber 00004ca0 | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 008d | ber 00004ca0 | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 0072 | ber 00004ca0 | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | > status 00 | signal bfe1 | snr 008b | ber 00004ca0 | unc bfe14648 | > status 00 | signal bfe1 | snr 0000 | ber 0000ffff | unc bfe14648 | And on the other one: > # tzap -r "Polsat" > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > reading channels from file '/root/.tzap/channels.conf' > tuning to 698000000 Hz > video pid 0x0066, audio pid 0x0067 > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | > status 00 | signal bfb5 | snr 0000 | ber 0000ffff | unc bfb5f4d8 | Greets, Jacek From nise.design at gmail.com Mon Jan 14 18:02:15 2013 From: nise.design at gmail.com (nise.design) Date: Tue, 15 Jan 2013 01:02:15 +0800 Subject: [linux-dvb] Problem between DMB-TH USB dongle drivers and Frontend broken (DVBv3 migrate to DVBv5) Message-ID: <50F43A17.7000805@gmail.com> Hello, I'm a Ubuntu and DMB-TH digital TV USB dongle user. The USB dongle working flawlessly in Ubuntu 10.XX, but it failed after migrate to latest Ubuntu 12.10. Then I using google to find out the problem and suspect the problem come from DVBv3 migrate to DVBv5. Because of creator of original DMB-TH drivers passed away so I wanted to continue his work to migrate DMB-TH drivers to new DVBv5 system. I need some help to perform this task and the situation as below: I plugged the USB dongle to USB port and it init normally: [103542.354826] usb 2-1.7: new high-speed USB device number 9 using ehci_hcd [103542.448349] usb 2-1.7: New USB device found, idVendor=0572, idProduct=d811 [103542.448353] usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [103542.448356] usb 2-1.7: Product: USB Stick [103542.448358] usb 2-1.7: Manufacturer: Geniatech [103542.448360] usb 2-1.7: SerialNumber: 080116 [103542.449395] dvb-usb: found a 'Mygica D689 DMB-TH' in warm state. [103542.790351] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [103542.790666] DVB: registering new adapter (Mygica D689 DMB-TH) [103543.038504] usb 2-1.7: DVB: registering adapter 0 frontend 0 (AltoBeam ATBM8830/8831 DMB-TH)... [103543.055041] input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/input/input18 [103543.055119] dvb-usb: schedule remote query interval to 100 msecs. [103543.055215] dvb-usb: Mygica D689 DMB-TH successfully initialized and connected. It failed after issued scan or any other command with messages: [103835.202015] usb 2-1.7: dtv_property_cache_sync: doesn't know how to handle a DVBv3 call to delivery system 0 Its alway show xxxx: doesn't know how to handle a DVBv3 call to delivery system 0. I have two dongles using altobeam 8830 chip and LG8GXX chip but both had same issued. After google search I think the problem may be come from connection between DMB-TH drivers and dvb_frontend.c broken. I wanted to know any example code or instruction about DVBv3 driver connect to dvb_frontend.c. Thank you for any advice. KP Lee. google search attached: *[PATCHv2 00/94] Only use DVBv5 internally on frontend drivers* * /Subject/: [PATCHv2 00/94] Only use DVBv5 internally on frontend drivers * /From/: Mauro Carvalho Chehab > * /Date/: Fri, 30 Dec 2011 13:06:57 -0200 * /Cc/: Mauro Carvalho Chehab >, Linux Media Mailing List > This patch series comes after the previous series of 47 patches. Basically, changes all DVB frontend drivers to work directly with the DVBv5 structure. This warrants that all drivers will be getting/setting frontend parameters on a consistent way, and opens space for improving the DVB core, in order to avoid copying data from/to the DVBv3 structs without need. Most of the patches on this series are trivial changes. Yet, it would be great to test them, in order to be sure that nothing broke. The last patch in this series hide the DVBv3 parameters struct from the frontend drivers, keeping them visible only to the dvb_core. This helps to warrant that everything were ported, and that newer patches won't re-introduce DVBv3 structs by mistake. There aren't many cleanups inside the dvb_frontend.c yet. Before cleaning up the core, I intend to do some tests with a some devices, in order to be sure that nothing broke with all those changes. Test reports are welcome. [media] atbm8830: convert set_fontend to new way and fix delivery system [media] lgs8gl5: convert set_fontend to use DVBv5 parameters [media] lgs8gxx: convert set_fontend to use DVBv5 parameters drivers/media/dvb/frontends/atbm8830.c | 24 ++-- drivers/media/dvb/frontends/lgs8gl5.c | 26 ++-- drivers/media/dvb/frontends/lgs8gxx.c | 23 ++-- -------------- next part -------------- An HTML attachment was scrubbed... URL: From stelios.koroneos at gmail.com Thu Jan 17 02:13:09 2013 From: stelios.koroneos at gmail.com (Stelios Koroneos) Date: Thu, 17 Jan 2013 03:13:09 +0200 Subject: [linux-dvb] Baseband I/Q raw data from dvb-s. Is it possible ? Message-ID: Greetings to all ! I am looking for a way to access the raw baseband I/Q either for dvb-s or dvb-s2 but i am kind of confused if this is possible and with which card. As far as i can tell the STB0899 demodulator provides this info but i am not sure if this is available by the driver, or if there are any other alternatives. The reason i want to access the I/Q is because i am in the process of building a high speed random number generator that will use the thermal noise produced by the LNB Any info,pointers would be highly appreciated Stelios -------------- next part -------------- An HTML attachment was scrubbed... URL: From member at linkedin.com Thu Jan 24 18:58:22 2013 From: member at linkedin.com (=?UTF-8?Q?=E6=9E=97=28Lin=29=E5=8D=9A=E4=BB=81=28Henry=29_via_LinkedIn?=) Date: Thu, 24 Jan 2013 17:58:22 +0000 (UTC) Subject: [linux-dvb] =?utf-8?q?Rejoindre_mon_r=C3=A9seau_sur_LinkedIn?= Message-ID: <304725064.3501867.1359050302179.JavaMail.app@ela4-app2309.prod> LinkedIn ------------ ?(Lin)??(Henry) souhaite se connecter ? vous sur LinkedIn?: ------------------------------------------ Je vous invite ? faire partie de mon r?seau professionnel en ligne sur le site LinkedIn. Accepter l'invitation de ?(Lin)??(Henry) http://www.linkedin.com/e/fsr5ur-hcc7gkih-3t/XMU0fwnQq28-ZPDQPi60aF6zk7O-8KbSaR/blk/I350084708_110/e39SrCAJoS5vrCAJoyRJtCVFnSRJrScJr6RBfnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_c34NnPwMdPgUc30RcQALikoSm3xQpnELdj8SejsSdPwSc34LrCBxbOYWrSlI/eml-comm_invm-b-in_ac-inv28/?hs=false&tok=1fnBlQpMzmDRA1 Voir le profil de ?(Lin)??(Henry) http://www.linkedin.com/e/fsr5ur-hcc7gkih-3t/rso/228144354/_npb/name/111416342_I350084708_110/?hs=false&tok=3NTf-53T3mDRA1 ------------------------------------------ Vous recevez des invitations par e-mail. Cet e-mail est destin? ? Linux Dvb. D?couvrez pourquoi nous avons inclus ceci?: http://www.linkedin.com/e/fsr5ur-hcc7gkih-3t/plh/http%3A%2F%2Fhelp%2Elinkedin%2Ecom%2Fapp%2Fanswers%2Fdetail%2Fa_id%2F4788/-GXI/?hs=false&tok=24JEnwhXjmDRA1 (c) 2012, LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, USA. -------------- next part -------------- An HTML attachment was scrubbed... URL: