Re: Fwd: Bug#669715: dvb-apps: Channel/frequency/etc. data needs updating for London transmitters
On 5/14/12 1:54 PM, Andrew Benham wrote: I don't know if it's just Crystal Palace, but one of the multiplexes thinks it's using QPSK even though it's using QAM64 - this messes up 'scan' unless one reorders the frequency list. Having done the scan, one then needs to replace 'QPSK' by 'QAM_64' in the output. I reported the issue through my channels and the issue was fixed earlier this evening. The DVB-SI tables have been updated so that now the constellation type has been changed from 0 (QPSK) to 2 (64-QAM). Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Updated tuning file for Crystal Palace transmitter, UK
I'm surprised that it is providing you with AUTO values, if you look at most other entries for tuning files, everything is clearly marked and there are (virtually?) no AUTO parameters in use. The whole point being that we remove the guessing. I'll update it next time I'm in the London area and have some time to generate the output. Cheers, Thomas On 3/12/12 5:29 PM, Chris Rankin wrote: I am only reporting the output from w_scan. To be honest, I'm concerned that more precise information might do more harm than good; more DVB tuners seem to understand AUTO than QAM256, for example. Cheers, Chris *From:* Thomas Kernen tker...@deckpoint.ch *To:* Christoph Pfister christophpfis...@gmail.com; Chris Rankin ranki...@yahoo.com *Cc:* linux-media@vger.kernel.org linux-media@vger.kernel.org *Sent:* Monday, 12 March 2012, 16:00 *Subject:* Re: Updated tuning file for Crystal Palace transmitter, UK Any chance we can get more specific parameters for the T2 transmissions than AUTO/AUTO/AUTO/AUTO/AUTO/AUTO? It should be using UK Freeview Mode 6: QAM256, 32K, FEC=2/3, guard= 1/128 Chris can you confirm that is what you are seeing? I seem to recall that some time ago we tired to enforce using the specific tuning parameters for all the options. Cheers, Thomas On 3/10/12 3:18 PM, Christoph Pfister wrote: Updated, thanks. Christoph Am 12. Februar 2012 01:23 schrieb Chris Rankinranki...@yahoo.com mailto:ranki...@yahoo.com: Hi, The UK's Crystal Palace transmitter supports DVB-T2, so here's an updated tuning file. Cheers, Chris #-- # file automatically generated by w_scan # (http://wirbel.htpc-forum.de/w_scan/index2.html) #!w_scan 20120112 1 0 TERRESTRIAL GB/w_scan #-- # location and provider: Crystal Palace, UK # date (-mm-dd) : 2012-02-12 # # T[2] [plp_id] [system_id]freq bw fec_hi fec_lo mod tm guard hi [# comment] #-- T 48180 8MHz 2/3 NONE QAM64 2k 1/32 NONE # London. T 53780 8MHz 3/4 NONE QAM16 2k 1/32 NONE # London. T 50580 8MHz 3/4 NONE QAM16 2k 1/32 NONE # London. T 56180 8MHz 2/3 NONE QAM64 2k 1/32 NONE # London. T 52980 8MHz 3/4 NONE QAM16 2k 1/32 NONE # London. T 578166670 8MHz 3/4 NONE QAM16 2k 1/32 NONE # London. T2 0 16435 55400 8MHz AUTO AUTO AUTO AUTO AUTO AUTO # London. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org mailto:majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org mailto:majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Updated tuning file for Crystal Palace transmitter, UK
Any chance we can get more specific parameters for the T2 transmissions than AUTO/AUTO/AUTO/AUTO/AUTO/AUTO? It should be using UK Freeview Mode 6: QAM256, 32K, FEC=2/3, guard= 1/128 Chris can you confirm that is what you are seeing? I seem to recall that some time ago we tired to enforce using the specific tuning parameters for all the options. Cheers, Thomas On 3/10/12 3:18 PM, Christoph Pfister wrote: Updated, thanks. Christoph Am 12. Februar 2012 01:23 schrieb Chris Rankinranki...@yahoo.com: Hi, The UK's Crystal Palace transmitter supports DVB-T2, so here's an updated tuning file. Cheers, Chris #-- # file automatically generated by w_scan # (http://wirbel.htpc-forum.de/w_scan/index2.html) #!w_scan 20120112 1 0 TERRESTRIAL GB/w_scan #-- # location and provider: Crystal Palace, UK # date (-mm-dd): 2012-02-12 # # T[2] [plp_id] [system_id]freq bw fec_hi fec_lo mod tm guard hi [# comment] #-- T 48180 8MHz 2/3 NONEQAM64 2k 1/32 NONE# London. T 53780 8MHz 3/4 NONEQAM16 2k 1/32 NONE# London. T 50580 8MHz 3/4 NONEQAM16 2k 1/32 NONE# London. T 56180 8MHz 2/3 NONEQAM64 2k 1/32 NONE# London. T 52980 8MHz 3/4 NONEQAM16 2k 1/32 NONE# London. T 578166670 8MHz 3/4 NONEQAM16 2k 1/32 NONE# London. T2 0 16435 55400 8MHz AUTO AUTO AUTO AUTO AUTO AUTO# London. -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Switzerland, Geneva DVB-T scan update
Hi Christoph, A new MUX for a local TV station is now online and covering the Geneva region of Switzerland. Attached is the updated file for the ch-Geneva region. Regards, Thomas # Switzerland, Geneva region # Updated by tker...@deckpoint.ch on 2010/12/03 # T[2] freq bw fec_hi fec_lo mod tm guard hi [# comment] #-- T 570166000 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 57800 8MHz 5/6 NONE QAM16 8k 1/4 NONE T 658166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE T 666166000 8MHz 2/3 NONE QAM64 8k 1/32 NONE T 682166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE T 70600 8MHz 1/2 NONE QAM16 8k 1/4 NONE T 746166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE T 76200 8MHz 1/2 NONE QPSK 2k 1/32 NONE T 770166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE T 794166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE T 818166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE T 850166000 8MHz 3/4 NONE QAM64 8k 1/8 NONE
Re: Hauppauge WinTV-NOVA-T-500 support
So I've tested a WinTV-NOVA-T-500 model 283 (SL-283-V2.0-GER) which according to the wiki isn't suppose to work: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 Anyhow, the revision I own, (WinTV-NOVA-T-500, 99101 LF, Rev D8B5) I seem to have no issues with support, no errors on loading the modules or tuning to the different DVB-T tuners. I'll go ahead and update the Wiki page to add a note that this revision actually does work and that the blanket statement claiming all model 283 are not supported. Regards, Thomas On 9/7/10 10:22 AM, Thomas Kernen wrote: Hello, According to the wiki entry for the Hauppauge WinTV-NOVA-T-500 hardware: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 Models 289 and 287 are supported (ie: the UK sold cards), but model 283 sold in Germany, Switzerland and maybe some other countries isn't. Is this still an accurate statement or has this situation evolved but hasn't been updated in the wiki entry? Regards, Thomas -- -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hauppauge WinTV-NOVA-T-500 support
Hello, According to the wiki entry for the Hauppauge WinTV-NOVA-T-500 hardware: http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-500 Models 289 and 287 are supported (ie: the UK sold cards), but model 283 sold in Germany, Switzerland and maybe some other countries isn't. Is this still an accurate statement or has this situation evolved but hasn't been updated in the wiki entry? Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Switzerland, Geneva DVB-T scan update
On 6/24/10 8:57 PM, Christoph Pfister wrote: 2010/6/21 Thomas Kernentker...@deckpoint.ch: Hi all, For the Switzerland, Geneva region, a new mux has been launched in May 2010 for the local TV station. Therefore this is now different from the ch-All DVB-T file. Attached is a new file for ch-Geneva containing the SFN frequency for the main mux and this new mux. I've added this mux to ch-All (this way the file stays valid). I expect another update may appear in August if/when the French DVB-T mux start broadcasting in this region. Regards, Thomas Thanks, Christoph Ok, Thanks Christoph -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Switzerland, Geneva DVB-T scan update
Hi all, For the Switzerland, Geneva region, a new mux has been launched in May 2010 for the local TV station. Therefore this is now different from the ch-All DVB-T file. Attached is a new file for ch-Geneva containing the SFN frequency for the main mux and this new mux. I expect another update may appear in August if/when the French DVB-T mux start broadcasting in this region. Regards, Thomas # Switzerland, Geneva region # Created from http://www.broadcast.ch/portal.aspx?pid=705 # http://www.broadcast.ch/data_program_dvbt.aspx # and w_scan for the new mux # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 57800 8MHz 5/6 NONE QAM16 8k 1/4 NONE T 70600 8MHz 1/2 NONE QAM16 8k 1/4 NONE
Re: TBS 6980 Dual DVB-S2 PCIe card
On 3/4/10 1:03 PM, Per Lundberg wrote: Hi Hermann, On Thu, Mar 4, 2010 at 11:05 AM, hermann pittonhermann-pit...@arcor.de wrote: Has anyone done any attempt at contacting TBS to see if they can release their changes under the GPLv2? Ideally, they would provide a patch themselves, but it should be fairly simple to diff the linux/ trees from their provided linux-s2api-tbs6980.tar.bz2 file with the stock Linux 2.6.32 code... in fact, it could be that their patch is so trivial that we could just include it in the stock Linux kernel without asking them for license clarifications... but obviously, if we can get a green sign from them, it would be even better. It is always the other way round. In the end they need a green sign from us. Well... I guess we are both right. :-) They need to assert ownership and license the code under the GPL, and we need to ensure that the quality of the code is high enough (driver is working and does not interfer with other parts of the code base...). We I asked TBS' support about this question they told me they would like to get it out under GPL as it has been done with other cards they sell but that right now it was not possible due to legal contraints related to some of the code in use by some of the chips on the board. No further details were provided. BTW, the TBS dual seems to be fine on m$, but there are some mysterious lockups without any trace, if used in conjunction with some prior S2/HDTV cards. I can't tell yet, if that it is evenly distributed over amd/ati and nvidia stuff or whatever on win7 ... , but people do spend lifetime in vain on it. This is pretty interesting, do you have any references? (forum links or similar) In my particular case, I was thinking about using it as the only S2 card in the machine, later possibly adding a DVB-C card if/when we get cable... so, it might not be a problem for me, but it still doesn't feel really good. I guess the card is pretty new, so maybe (hopefully) it will get fixed by a new firmware release. Do we have any readers of this list who own the card and use it in Linux (with the drivers from TBS)? Could you please share your experiences: is the picture quality good? Sound? Does the tuner work well? (e.g. can you receive all channels you normally receive...) Yes I use the card. Have had it for a couple of months now running in a server that acts as a video head-end in my test network. I only tune to specific transponders when I boot the server so I can't really comment on tuning time and related issues. Yes I've used it for S and S2 feeds and so far it fits my requirements. HTH, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: TBS 6980 Dual DVB-S2 PCIe card
Ian Richardson wrote: On 2009-12-08 13:31, Thomas Kernen wrote: Matthias Wächter wrote: Hallo Thomas! Am 02.12.2009 15:31, schrieb Thomas Kernen: Is someone already working on supporting the TBS 6980 Dual DVB-S2 PCIe card? http://www.tbsdtv.com/english/product/6980.html I got one last Thursday, also direct from TBS. They provide a mini CD with their own V4L which has support for it included, together with versions of scan-s2 and szap-s2, but I'm a relative newbie and I've already managed to break my MythTV 0.22 setup trying to get it working. Any tips on how to get it working with Ubuntu 9.10 and kernel 2.6.31-16.52 would be very handy. With their V4L I can only get as far as a successful channel scan. Ian, I got my card today and have installed it. Works fine with the drivers from the mini CD and the streamer I'm testing against (DVBlast). So unfortunately I can't help you with MythTV since I don't use it. Note that I'm using Ubuntu 9.10 with 2.6.31-16-server Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: TBS 6980 Dual DVB-S2 PCIe card
Matthias Wächter wrote: Hallo Thomas! Am 02.12.2009 15:31, schrieb Thomas Kernen: Is someone already working on supporting the TBS 6980 Dual DVB-S2 PCIe card? http://www.tbsdtv.com/english/product/6980.html Have you seen/tried their all-in-one linux source package which was released 2009-12-03? http://www.tbsdtv.com/download/common/linux_tbs_all.rar – Matthias BTW: Where did you get yours? Hello Matthias, I've ordered a card directly from TBS. It's currently being shipped hence I won't be able to test it until at least next week. Then I'll see how it behaves in my system alongside all the other cards I have in it. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
TBS 6980 Dual DVB-S2 PCIe card
Hello, Is someone already working on supporting the TBS 6980 Dual DVB-S2 PCIe card? http://www.tbsdtv.com/english/product/6980.html Chips in use appear to be: - Conexant CX23885 (PCI Express bridge) - NXP/Conexant CX24132 (DVB-S/S2 tuner) - NXP/Conexant CX24117 (DVB-S/S2 demodulator) I know there is code in v4l-dvb for the CX23885 but I don't think I've seen any for the CX24132 and CX24117. Any insight into supporting this card would be great Thanks Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Ubuntu karmic, 2.6.31-14 + KNC1 DVB-S2 = GPF
Julian Scheel wrote: It would appear that since I've upgraded to Ubuntu Karmic and the 2.6.31-14 kernel, my KNC1 DVB-S2 now enjoys a GPF when I use scan-s2. Has anyone else come across this issue with a KNC1 card? Any suggestions what I can do to trace the issue? Which gcc version are you using? If you run a gcc 4.4 could you try to compile the v4l-dvb tree with a gcc-4.3 and see if it helps? Hi Julian, I did recompile with gcc-4.3 as you suggested and yes that solved the issue. My card now works fine with v4l-dvb complied with gcc 4.3. Since gcc 4.4 is the default GCC version with Ubuntu Karmic (9.10), I expect others will run into the same issue. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)
Thomas Kernen wrote: Hello, I came across this thread from June 2009 in the news archives about Ubuntu Karmic and v4l-dvb compile broken with stock Ubuntu Karmic build: http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/7161 I've just come across this issue myself after an upgrade of a server to the Ubuntu Karmic release. Is there any plans to attempt to mitigate this so that other users would not be impacted? Regards, Thomas I don't like answering my own messages but hopefully this will be useful to other users too who may come across the same issue as I and didn't do enough research before asking the question. Ubuntu Karmic is missing some Firewire/IEEE1394 files in the kernel-headers package. Workaround: in the v4l folder, open the .config file, find the line with CONFIG_DVB_FIREDTV=m and change to CONFIG_DVB_FIREDTV=n. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: v4l-dvb compile broken with stock Ubuntu Karmic build (firedtv-ieee1394.c errors)
Hello, I came across this thread from June 2009 in the news archives about Ubuntu Karmic and v4l-dvb compile broken with stock Ubuntu Karmic build: http://article.gmane.org/gmane.linux.drivers.video-input-infrastructure/7161 I've just come across this issue myself after an upgrade of a server to the Ubuntu Karmic release. Is there any plans to attempt to mitigate this so that other users would not be impacted? Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Ubuntu kernel 2.6.28-11/13 and KNC One clone
I just noticed something on a minor Ubuntu kernel upgrade. Running Linux nylon 2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64 GNU/Linux and Ubuntu update system offers 2.6.28-13. I take the upgrade and notice that in 2.6.28-13 the budget-av module will not load anymore for the KNC One DVB-S2 card. 11:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: KNC One Device 0019 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 123 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at d0220400 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget_av Kernel modules: budget-av The only diff is that -13 will not have the last 2 lines. Nothing in dmesg that indicates any error on loading in -13. Is this worth reporting to the Ubuntu QA team or already old news? Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Seeking recommendation for DVB-S PCI card with on-card CI
Andy Zivkovic wrote: Are these the same boards and/or different revisions? Are they supported by the Mantis driver including the CI? This part I wasn't able to confirm from my search. Thomas, The maintis driver currently doesn't support CI. Unfortunately I bought a Twinhan SP300 (1034) before I knew this, so I now have a DVB-S card that is effectively useless to me, but I'm hopeful someone will fix the driver one day (although I bought the card months ago and I'm close to cancelling my sat subscription since the set top box I have is crap, so I don't watch it enough to justify the monthly fees). In mid May, Manu, who I think is a (the?) mantis developer, posted on this list saying he hadn't had time to work on mantis CI for the 2 months prior to that. I haven't noticed anything new since then, so I don't know where it's at. Andy, Thanks for the feedback, that was what I feared (CI not supported). Better to know ahead of time that after ordering such a card Manu, Any chance you would be able to comment on the planned roadmap for the CI support on the Azurewave/Twinham 1034 based cards? All, Are there any known working PCI based solutions that have the CI slot on the card itself? I'm attempting to find something that can be self contained within a single PCI slot. Regards, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Seeking recommendation for DVB-S PCI card with on-card CI
Hello all, I'm attempting to find a supported DVB-S PCI card with an on-card CI (ie: not a seperate daughter board) to contain all in one slot. Based on the wiki and mailing list archives I seem to come up with the Twinhan AD-SP300(1034): http://www.twinhan.com/product_satellite_1034.asp But the wiki entries seem to refer to a 1030A version: http://www.linuxtv.org/wiki/index.php/Twinhan_VP-1030A Are these the same boards and/or different revisions? Are they supported by the Mantis driver including the CI? This part I wasn't able to confirm from my search. Are there other suggestions for such cards that are 100% supported? Thanks, Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[SOLVED] Re: TT-S1500 budget-ci registeration
Thomas Kernen wrote: Thomas Kernen wrote: Hello to all, I'm currently testing a TT-S1500 budget card with the TT budget CI adapter with vl4 tree and kernel 2.6.28. When I modprobe budget_ci, the CI adapter seems to be detected but not registered in /dev/dvb/adapter3/ca0 as I would have expected it to be. Instead I see the following output: [ 148.664846] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci:00/:00:1e.0/:11:09.0/input/input5 Any suggestions/ideas what the cause may be and how I can attempt to solve this? Thanks Thomas -- And I realised I cut and pasted the wrong line: I was expecting to see budget_ci: CI interface initialised after the other line but nothing of the like did appear. Nor any line indicating an error. As one can see from the lspci the drivers claim to be in use: 11:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Device 1017 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 123 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at d022 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget_ci dvb Kernel modules: budget-ci Am I missing a point here? I can't find anything that addresses this in the LinuxTV wiki or in the archives of the mailing list. It would appear that I enjoy speaking to myself on this mailer ;-) Anyway, good news is that the issue had to do with a defective cable that was bridging the Budget CI and the TT S-1500. It is now functional and descrambles the Viaccess streams I needed to test against. Later today I will update the wiki pages with the details of my setup: [8.850659] saa7146: register extension 'budget_ci dvb'. [8.850678] budget_ci dvb :11:08.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [8.850695] saa7146: found saa7146 @ mem c20001198000 (revision 1, irq 22) (0x13c2,0x1017). [8.850698] saa7146 (0): dma buffer size 192512 [8.850700] DVB: registering new adapter (TT-Budget/S-1500 PCI) [8.910869] adapter has MAC addr = 00:d0:5c:64:c2:55 [8.911046] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci:00/:00:1e.0/:11:08.0/input/input4 [8.972616] budget_ci: CI interface initialised [9.335816] LNBx2x attached on addr=8DVB: registering adapter 0 frontend 0 (ST STV0299 DVB-S)... [9.340535] dvb_ca adapter 0: DVB CAM detected and initialised successfully CAM Application type: 01 CAM Application manufacturer: 02ca CAM Manufacturer code: 3000 CAM Menu string: PowerCam_HD V2.0.4 Hopefully this might be useful to others too. Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
TT-S1500 budget-ci registeration
Hello to all, I'm currently testing a TT-S1500 budget card with the TT budget CI adapter with vl4 tree and kernel 2.6.28. When I modprobe budget_ci, the CI adapter seems to be detected but not registered in /dev/dvb/adapter3/ca0 as I would have expected it to be. Instead I see the following output: [ 148.664846] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci:00/:00:1e.0/:11:09.0/input/input5 Any suggestions/ideas what the cause may be and how I can attempt to solve this? Thanks Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: TT-S1500 budget-ci registeration
Thomas Kernen wrote: Hello to all, I'm currently testing a TT-S1500 budget card with the TT budget CI adapter with vl4 tree and kernel 2.6.28. When I modprobe budget_ci, the CI adapter seems to be detected but not registered in /dev/dvb/adapter3/ca0 as I would have expected it to be. Instead I see the following output: [ 148.664846] input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci:00/:00:1e.0/:11:09.0/input/input5 Any suggestions/ideas what the cause may be and how I can attempt to solve this? Thanks Thomas -- And I realised I cut and pasted the wrong line: I was expecting to see budget_ci: CI interface initialised after the other line but nothing of the like did appear. Nor any line indicating an error. As one can see from the lspci the drivers claim to be in use: 11:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: Technotrend Systemtechnik GmbH Device 1017 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 123 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at d022 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget_ci dvb Kernel modules: budget-ci Am I missing a point here? I can't find anything that addresses this in the LinuxTV wiki or in the archives of the mailing list. Thanks Thomas -- To unsubscribe from this list: send the line unsubscribe linux-media in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[SOLVED] Re: Mystique SaTiX DVB-S2 s2-liplianin Ubuntu 9.04 64 bit - modules load but tuning not successful
Thomas Kernen wrote: Dear team, I'm installing a Mystique SaTiX DVB-S2 PCI card (apparently an OEM version of KNC DVB Station S2) in a box running Ubuntu 9.04 64bit. (2.6.28-11-server #42-Ubuntu SMP Fri Apr 17 02:45:36 UTC 2009 x86_64 GNU/Linux) I've pulled the latest s2-liplianin code from: http://mercurial.intuxication.org/hg/s2-liplianin I was able to compile and the modules do load, but I don't seem to be able to tune to anything. Note that I've only tried to tune to DVB-S transponders for now. lspci -vvv shows the following: 11:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: KNC One Device 0019 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 123 (3750ns min, 9500ns max) Interrupt: pin A routed to IRQ 23 Region 0: Memory at d022 (32-bit, non-prefetchable) [size=512] Kernel driver in use: budget_av Kernel modules: budget-av From dmesg: [9.796943] budget_av :11:09.0: PCI INT A - GSI 23 (level, low) - IRQ 23 [9.796972] saa7146: found saa7146 @ mem c20001186000 (revision 1, irq 23) (0x1894,0x0019). [9.796976] saa7146 (0): dma buffer size 192512 [9.796977] DVB: registering new adapter (KNC1 DVB-S2) [9.853417] adapter failed MAC signature check [9.853419] encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff [ 10.162850] KNC1-1: MAC addr = 00:09:d6:65:2d:91 [ 10.35] saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer [ 10.424422] stb0899_attach: Attaching STB0899 [ 10.432541] tda8261_attach: Attaching TDA8261 8PSK/QPSK tuner [ 10.432543] DVB: registering adapter 1 frontend 0 (STB0899 Multistandard)... [ 10.432731] budget-av: ci interface initialised. dvbsnoop shows the following: dvbsnoop V1.4.50 -- http://dvbsnoop.sourceforge.net/ - FrontEnd Info... - Device: /dev/dvb/adapter1/frontend0 Basic capabilities: Name: STB0899 Multistandard Frontend-type: QPSK (DVB-S) Frequency (min): 950.000 MHz Frequency (max): 2150.000 MHz Frequency stepsiz: 0.000 MHz Frequency tolerance: 0.000 MHz Symbol rate (min): 1.00 MSym/s Symbol rate (max): 45.00 MSym/s Symbol rate tolerance: 0 ppm Notifier delay: 0 ms Frontend capabilities: auto inversion FEC AUTO QPSK Current parameters: Frequency: 1776.000 MHz Inversion: AUTO Symbol rate: 27.50 MSym/s FEC: FEC AUTO If I try to use scan-s2 I get the following output: API major 5, minor 0 ERROR: Cannot open rotor configuration file 'rotor.conf'. scanning /usr/share/dvb/dvb-s/Astra-19.2E using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' initial transponder DVB-S 12551500 V 2200 5/6 AUTO AUTO initial transponder DVB-S2 12551500 V 2200 5/6 AUTO AUTO -- Using DVB-S tune to: 12551:vC56S0:S0.0W:22000: DiSEqC: uncommitted switch pos 0 DiSEqC: e0 10 39 f0 00 00 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 DVB-S IF freq is 1951500 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 WARNING: tuning failed!!! tune to: 12551:vC56S0:S0.0W:22000: (tuning failed) DiSEqC: uncommitted switch pos 0 DiSEqC: e0 10 39 f0 00 00 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 DVB-S IF freq is 1951500 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 WARNING: tuning failed!!! -- Using DVB-S2 tune to: 12551:vC56S1:S0.0W:22000: DiSEqC: uncommitted switch pos 0 DiSEqC: e0 10 39 f0 00 00 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 DVB-S IF freq is 1951500 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 WARNING: tuning failed!!! tune to: 12551:vC56S1:S0.0W:22000: (tuning failed) DiSEqC: uncommitted switch pos 0 DiSEqC: e0 10 39 f0 00 00 DiSEqC: switch pos 0, 13V, hiband (index 2) DiSEqC: e0 10 38 f1 00 00 DVB-S IF freq is 1951500 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status == 0x00 tuning status
CAM initialisation failing
Dear community, After finally getting my Mystique SaTiX DVB-S2 PCI card (clone of KNC1 DVB Station S2), I'm now facing trouble with the CAM initialisation (KNC1 CA daughter card, PowerCam Pro CAM and Viaccess card) All of the hardware (DVB-S2 PCI card, sat card, CI, CAM) has been tested under Windows with any issues, hence I suspect this is a module related issue. To try and better understand the issue, I added some debug statements to the following modules: options dvb-core cam_debug=1 debug=1 options budget-core debug=1 And this is the output I'm getting: [9.146782] DVB: registering new adapter (KNC1 DVB-S2) [9.203364] adapter failed MAC signature check [9.203366] encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff [9.410061] budget_av: saa7113_init(): saa7113 not found on KNC card [9.510352] KNC1-1: MAC addr = 00:09:d6:65:2d:91 [9.642505] saa7146 (0) saa7146_i2c_writeout [irq]: timed out waiting for end of xfer [9.764427] stb0899_attach: Attaching STB0899 [9.776853] tda8261_attach: Attaching TDA8261 8PSK/QPSK tuner [9.776855] DVB: registering adapter 1 frontend 0 (STB0899 Multistandard)... [9.776888] dvb_ca_en50221_init [9.777048] budget-av: ci interface initialised. [9.777050] dvb_ca_en50221_thread snip [ 14.770017] budget-av: cam inserted A [ 14.770032] budget_av: ciintf_slot_reset(): ciintf_slot_reset [ 14.950033] TUPLE type:0x1d length:4 [ 14.950041] 0x00: 0x00 . [ 14.950048] 0x01: 0x61 a [ 14.950055] 0x02: 0x00 . [ 14.950063] 0x03: 0xff . [ 14.950076] TUPLE type:0x1c length:4 [ 14.950083] 0x00: 0x00 . [ 14.950091] 0x01: 0xd3 . [ 14.950098] 0x02: 0x00 . [ 14.950105] 0x03: 0xff . [ 14.950118] TUPLE type:0x15 length:11 [ 14.950126] 0x00: 0x05 . [ 14.950133] 0x01: 0x00 . [ 14.950140] 0x02: 0x47 G [ 14.950147] 0x03: 0x00 . [ 14.950154] 0x04: 0x4d M [ 14.950161] 0x05: 0x00 . [ 14.950168] 0x06: 0x4c L [ 14.950175] 0x07: 0x00 . [ 14.950182] 0x08: 0x4c L [ 14.950189] 0x09: 0x00 . [ 14.950196] 0x0a: 0xff . [ 14.950210] TUPLE type:0x20 length:4 [ 14.950217] 0x00: 0x02 . [ 14.950224] 0x01: 0xca . [ 14.950232] 0x02: 0x12 . [ 14.950239] 0x03: 0x60 ` [ 14.950252] TUPLE type:0x1a length:21 [ 14.950260] 0x00: 0x01 . [ 14.950267] 0x01: 0x0f . [ 14.950274] 0x02: 0x00 . [ 14.950281] 0x03: 0x02 . [ 14.950288] 0x04: 0x03 . [ 14.950295] 0x05: 0xc0 . [ 14.950302] 0x06: 0x0e . [ 14.950309] 0x07: 0x41 A [ 14.950316] 0x08: 0x02 . [ 14.950323] 0x09: 0x44 D [ 14.950330] 0x0a: 0x56 V [ 14.950337] 0x0b: 0x42 B [ 14.950344] 0x0c: 0x5f _ [ 14.950352] 0x0d: 0x43 C [ 14.950359] 0x0e: 0x49 I [ 14.950366] 0x0f: 0x5f _ [ 14.950373] 0x10: 0x56 V [ 14.950380] 0x11: 0x31 1 [ 14.950387] 0x12: 0x2e . [ 14.950394] 0x13: 0x30 0 [ 14.950401] 0x14: 0x30 0 [ 14.950415] TUPLE type:0x1b length:42 [ 14.950422] 0x00: 0xcf . [ 14.950429] 0x01: 0x04 . [ 14.950436] 0x02: 0x09 . [ 14.950443] 0x03: 0x7f . [ 14.950450] 0x04: 0x55 U [ 14.950458] 0x05: 0xcd . [ 14.950465] 0x06: 0x19 . [ 14.950472] 0x07: 0xd5 . [ 14.950479] 0x08: 0x19 . [ 14.950486] 0x09: 0x3d = [ 14.950493] 0x0a: 0x9e . [ 14.950500] 0x0b: 0x25 % [ 14.950507] 0x0c: 0x26 [ 14.950514] 0x0d: 0x54 T [ 14.950521] 0x0e: 0x22 [ 14.950528] 0x0f: 0xc0 . [ 14.950535] 0x10: 0x09 . [ 14.950542] 0x11: 0x44 D [ 14.950549] 0x12: 0x56 V [ 14.950557] 0x13: 0x42 B [ 14.950564] 0x14: 0x5f _ [ 14.950571] 0x15: 0x48 H [ 14.950578] 0x16: 0x4f O [ 14.950585] 0x17: 0x53 S [ 14.950592] 0x18: 0x54 T [ 14.950599] 0x19: 0x00 . [ 14.950606] 0x1a: 0xc1 . [ 14.950613] 0x1b: 0x0e . [ 14.950620] 0x1c: 0x44 D [ 14.950627] 0x1d: 0x56 V [ 14.950634] 0x1e: 0x42 B [ 14.950642] 0x1f: 0x5f _ [ 14.950649] 0x20: 0x43 C [ 14.950656] 0x21: 0x49 I [ 14.950663] 0x22: 0x5f _ [ 14.950670] 0x23: 0x4d M [ 14.950677] 0x24: 0x4f O [ 14.950684] 0x25: 0x44 D [ 14.950691] 0x26: 0x55 U [ 14.950698] 0x27: 0x4c L [ 14.950705] 0x28: 0x45 E [ 14.950712] 0x29: 0x00 . [ 14.950727] TUPLE type:0x14 length:0 [ 14.950734] END OF CHAIN TUPLE type:0xff [ 14.950735] Valid DVB CAM detected MANID:ca02 DEVID:6012 CONFIGBASE:0x200 CONFIGOPTION:0xf [ 14.950736] dvb_ca_en50221_set_configoption [ 14.950750] Set configoption 0xf, read configoption 0xf [ 14.950757] DVB CAM validated successfully snip [ 15.050023] dvb_ca_en50221_link_init [ 15.050030] dvb_ca_en50221_wait_if_status [ 15.050037] dvb_ca_en50221_wait_if_status succeeded timeout:0 [ 15.050038] dvb_ca_en50221_read_data [ 15.050084] dvb_ca adapter 1: DVB CAM link initialisation failed :( So if I understand correctly the CAM is ok but the en50221 module is times out when trying to read the card, is this correct? Any
