Re: [linux-dvb] DVB-S Stream multiple Channels
Original Message - From: Nikos Parastatidis [EMAIL PROTECTED] To: linux-dvb@linuxtv.org Sent: Wednesday, March 05, 2008 12:22 PM Subject: Re: [linux-dvb] DVB-S Stream multiple Channels i see ! this creared everything now so DVB-S has a tuner also i thoght it was one frequency for every LNB and every satelite and with this frequency was a carrier for all channels. anyway ok in theory but are there frequencies that cary more than one channel? can someone give me an excample like Patrick gave me on DVB-T if you can speak Greek :-) and give me a nova excample it would be great :-) To see what channels are available, I have always found sites like www.satcodx.com and www.lygsat.com useful to see what is available on individual satellites/transponders. Pete how can i check it my self within dreambox ? how can i check if one freq has many channels? Thanks in advance your help so far was very precius. On 3/5/08, Patrick Bulteel [EMAIL PROTECTED] wrote: Zaheer Merali wrote: On Wed, Mar 5, 2008 at 9:58 AM, Nikos Parastatidis [EMAIL PROTECTED] wrote: Hi there i would like to ask you if it is posible to stream multiple channels with any DVB-S card in linux. do DVB-S have the capability to decode/tune to multiple channels? i know this is not posible at DVB-T because of the tuner, it cannot tune to multiple channels at once, you need dual or more pci cards to do this. what about at DVB-S ? Thanks in advace Parastatidis Nikos Nikos, if they are on the same transponder/multiplex you can stream multiple channels. If not you need a different tuner per channel. Zaheer And I believe that applies for DVB-T as well. Meaning with one tuner in the UK you should be able to tune/stream the following on Mux 1: BBC ONE, BBC TWO, BBC THREE / CBBC, BBC NEWS 24 and so on... -- Patrick ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.21.4/1310 - Release Date: 04/03/2008 08:35 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] DMX_OUT_TSDEMUX_TAP: record two streams from same mux, resend
[Resending patch with proper signed-off-by and updated description, but otherwise unchanged] Hi there, Currently (in linux-2.6.24, but linux-dvb hg looks similar), the dmx_output_t in the dmx_pes_filter_params decides two things: whether output is sent to demux0 or dvr0 (in dmxdev.c:dvb_dmxdev_ts_callback), *and* whether to depacketise TS (in dmxdev.c:dvb_dmxdev_filter_start). As it stands, those two things can't be set independently: output destined for demux0 is depacketised, output for dvr0 isn't. This is what you want for capturing multiple audio streams from the same multiplex simultaneously: open demux0 several times and send depacketised output there. And capturing a single video stream is fine too: open dvr0. But for capturing multiple video streams, it's surely not what you want: you want multi-open (so demux0, not dvr0), but you want the TS nature preserved (because that's what you want on output, as you're going to re-multiplex it with the audio). At least one existing solution -- GStreamer -- sends all its streams simultaneously via dvr0 and demuxes again in userland, but it seems a bit of a shame to pick out all the PIDs in kernel, stick them back together in kernel, and send them to userland only to get unpicked again, when the alternative is such a small API addition. The attached patch adds a new value for dmx_output_t: DMX_OUT_TSDEMUX_TAP, which sends TS to the demux0 device. With this patch and a dvb-usb-dib0700 (and UK Freeview from Sandy Heath), I can successfully capture an audio/video PID pair into a TS file that mplayer can play back. Peter Signed-off-by: Peter Hartley [EMAIL PROTECTED] Acked-by: Andreas Oberritter [EMAIL PROTECTED] --- include/linux/dvb/dmx.h~ 2008-01-24 22:58:37.0 + +++ include/linux/dvb/dmx.h 2008-02-25 23:01:45.0 + @@ -39,9 +39,10 @@ typedef enum DMX_OUT_DECODER, /* Streaming directly to decoder. */ DMX_OUT_TAP, /* Output going to a memory buffer */ /* (to be retrieved via the read command).*/ - DMX_OUT_TS_TAP /* Output multiplexed into a new TS */ + DMX_OUT_TS_TAP, /* Output multiplexed into a new TS */ /* (to be retrieved by reading from the */ /* logical DVR device). */ + DMX_OUT_TSDEMUX_TAP /* Like TS_TAP but retrieved from the DMX device */ } dmx_output_t; --- drivers/media/dvb/dvb-core/dmxdev.c~ 2008-01-24 22:58:37.0 + +++ drivers/media/dvb/dvb-core/dmxdev.c 2008-02-25 23:02:29.0 + @@ -374,7 +374,8 @@ static int dvb_dmxdev_ts_callback(const return 0; } - if (dmxdevfilter-params.pes.output == DMX_OUT_TAP) + if (dmxdevfilter-params.pes.output == DMX_OUT_TAP + || dmxdevfilter-params.pes.output == DMX_OUT_TSDEMUX_TAP) buffer = dmxdevfilter-buffer; else buffer = dmxdevfilter-dev-dvr_buffer; @@ -618,7 +619,7 @@ static int dvb_dmxdev_filter_start(struc else ts_type = 0; - if (otype == DMX_OUT_TS_TAP) + if (otype == DMX_OUT_TS_TAP || otype == DMX_OUT_TSDEMUX_TAP) ts_type |= TS_PACKET; if (otype == DMX_OUT_TAP) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] [PATCH] DMX_OUT_TSDEMUX_TAP: record two streams from same mux
Hi there, Currently (in linux-2.6.24, but linux-dvb hg looks similar), the dmx_output_t in the dmx_pes_filter_params decides two things: whether output is sent to demux0 or dvr0 (in dmxdev.c:dvb_dmxdev_ts_callback), *and* whether to depacketise TS (in dmxdev.c:dvb_dmxdev_filter_start). As it stands, those two things can't be set independently: output destined for demux0 is depacketised, output for dvr0 isn't. This is what you want for capturing multiple audio streams from the same multiplex simultaneously: open demux0 several times and send depacketised output there. And capturing a single video stream is fine too: open dvr0. But for capturing multiple video streams, it's surely not what you want: you want multi-open (so demux0, not dvr0), but you want the TS nature preserved (because that's what you want on output, as you're going to re-multiplex it with the audio). The attached patch adds a new value for dmx_output_t: DMX_OUT_TSDEMUX_TAP, which sends TS to the demux0 device. The main question I have, is, seeing as this was such a simple change, why didn't it already work like that? Does everyone else who wants to capture multiple video streams, take the whole multiplex into userspace and demux it themselves? Or do they take PES from each demux0 device and re-multiplex that into PS, not TS? With this patch and a dvb-usb-dib0700 (and UK Freeview from Sandy Heath), I can successfully capture an audio/video PID pair into a TS file that mplayer can play back. Peter --- include/linux/dvb/dmx.h~ 2008-01-24 22:58:37.0 + +++ include/linux/dvb/dmx.h 2008-02-25 23:01:45.0 + @@ -39,9 +39,10 @@ typedef enum DMX_OUT_DECODER, /* Streaming directly to decoder. */ DMX_OUT_TAP, /* Output going to a memory buffer */ /* (to be retrieved via the read command).*/ - DMX_OUT_TS_TAP /* Output multiplexed into a new TS */ + DMX_OUT_TS_TAP, /* Output multiplexed into a new TS */ /* (to be retrieved by reading from the */ /* logical DVR device). */ + DMX_OUT_TSDEMUX_TAP /* Like TS_TAP but retrieved from the DMX device */ } dmx_output_t; --- drivers/media/dvb/dvb-core/dmxdev.c~ 2008-01-24 22:58:37.0 + +++ drivers/media/dvb/dvb-core/dmxdev.c 2008-02-25 23:02:29.0 + @@ -374,7 +374,8 @@ static int dvb_dmxdev_ts_callback(const return 0; } - if (dmxdevfilter-params.pes.output == DMX_OUT_TAP) + if (dmxdevfilter-params.pes.output == DMX_OUT_TAP + || dmxdevfilter-params.pes.output == DMX_OUT_TSDEMUX_TAP) buffer = dmxdevfilter-buffer; else buffer = dmxdevfilter-dev-dvr_buffer; @@ -618,7 +619,7 @@ static int dvb_dmxdev_filter_start(struc else ts_type = 0; - if (otype == DMX_OUT_TS_TAP) + if (otype == DMX_OUT_TS_TAP || otype == DMX_OUT_TSDEMUX_TAP) ts_type |= TS_PACKET; if (otype == DMX_OUT_TAP) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] auto detection of Flytv duo/hybrid and pci/cardbus confusion
On Monday 18 February 2008, hermann pitton wrote: Hi Peter, Am Sonntag, den 17.02.2008, 14:28 +1100 schrieb Peter D.: Hi, I've finally gotten around to reading the code and trying to get my PCI MSI [EMAIL PROTECTED] A/D card auto detected. First clarification, duo versus hybrid. Are duo cards equipped with two independent tuners that can both be used at the same time? Are hybrid cards necessarily equipped with digital and analogue tuners? Can a two tuner card be both a duo and a hybrid, if one tuner is digital the other is analogue and they can both be used at the same time? for that all I give some examples further below. Second clarification, PCI versus cardbus. They don't look anything like each other, but can they be logically interchangeable? If the code for a cardbus tuner happens to work for a PCI tuner is there anything wrong with referring to the PCI tuner as a cardbus device? No, we do such and vice versa, but then we add a comment PCI or cardbus version usually and another important compatible category is Mini PCI. You should also add LR306 as the board type. Looking at http://www.linuxtv.org/wiki/index.php/DVB-T_PCMCIA_Cards there does not appear to be any such thing as a SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS, despite the entry (number 94) in saa7134.h. Looking at http://www.linuxtv.org/wiki/index.php/DVB-T_PCI_Cards#LifeView there is a PCI version - but there is no PCI version in saa7134.h. They do exist, see bttv-gallery.de, OK found it. also Mauro has already a MSI OEM version. They are special for DVB-T, since they switch the mode by a gpio pin and have the silent i2c connection to the tuner open and don't use the i2c gate of the tda8290 analog demod inside the saa7131e for DVB-T tuning. So the PCI version looks like a slightly dysfunctional cardbus device. Should SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS be changed to SAA7134_BOARD_FLYDVBT_HYBRID? No. Just also add PCI and LR306 to your comments. The gpio 21 is used for the TV/radio switch. The gpio 22 = 0 in the mask is used to switch the tuner AGC to the analog demod. On some cardbus version, which have the gpio 27 high, switching it to 0 turns the fan on, on yours it does nothing, since it is 0 anyway. I can safely ignore all of that? It appears that both PCI and cardbus versions of the Flytv duo exist and are listed in saa7134.h - despite slightly inconsistent punctuation; SAA7134_BOARD_FLYDVBTDUO versus SAA7134_BOARD_FLYDVBT_DUO_CARDBUS. Should SAA7134_BOARD_FLYDVBTDUO be changed to SAA7134_BOARD_FLYDVBT_DUO? Not related to your device. Subdevice is 0x0306 and you have 0x3306, but yes, these are in a different family of devices too. I just thought that I have found a very minor typo - an extra underscore in on of the constants would look more systematic to me. It is not important. I have an MSI [EMAIL PROTECTED] A/D PCI card that works with the option card=94 There appears to not be an entry in struct pci_device_id saa7134_pci_tbl[] in saa7134-cards.c for my card. There is a reference to a [EMAIL PROTECTED] DUO which I guess is a valid entry for a different card. Yes it is. Peter Missel bought some and added the entry. Duo in LifeView terminology means two separate tuners. One for analog TV/FM and one for DVB-T. LifeView terminology. The meaning might change might change and we have to live with it. I was hoping that there would be a technical definition. On the older Duo versions those two tuners were _not hybrid_ and different for analog TV and DVB-T. Only the newer Duo variants with tda8275A use two identical such tuners, but not in hybrid mode. One is always in analog and the other always in digital mode. The older types are out of production and using two still allows to have DVB-T and analog TV from the tuners at once. This is not possible with one single hybrid tuner. DVB-T and analog video from an external input, VCR tuner or something, is possible at once, but needs also to use packed video formats for analog during that due to limitations of the dma engines with planar formats. Then the Trio has even one more tuner for DVB-S, but there is only _one_ saa713x PCI bridge on all such and only one channel decoder/demodulator for each mode. Since the single saa713x chip has only one TS/mpeg/host interface, either usable in parallel or serial mode, DVB-S and DVB-T can not be used at the same time. (also not an mpeg encoder) This is only possible with two saa713x bridges, like the md7134 in the CTX925 version has them and when we enable DVB-S support on the second bridge hopefully soon. Else functionality is like on the Trio. (BTW, the md7134 represents lots of different cards through eeprom detection) Next category is the Medion md8800 Quad(ro) with two saa7131e, two fully usable tda8275ac1 hybrid (2 analog + 2 DVB-T demods, no FM) and two tda8263 DVB-S tuners plus
Re: [linux-dvb] auto detection of Flytv duo/hybrid and pci/cardbus confusion
On Wednesday 20 February 2008, hermann pitton wrote: Am Sonntag, den 17.02.2008, 21:53 +0100 schrieb Peter Missel: Greetings all! Let me clear things up a bit. First clarification, duo versus hybrid. Are duo cards equipped with two independent tuners that can both be used at the same time? Are hybrid cards necessarily equipped with digital and analogue tuners? Can a two tuner card be both a duo and a hybrid, if one tuner is digital the other is analogue and they can both be used at the same time? LifeView are using two vendor IDs - 4E42h for all (!) their OEMs, and their own one for LifeView branded cards. Hence we need two PCI ID entries for everything, each pair pointing back to the same card data. Then, card types. The analog-only and hybrid have one single tuner, for DVB-T or analog. The Duo cards have two tuner frontends, one for DVB-T and the other for analog. Trio cards add a DVB-S frontend, which cannot be used at the same time as the DVB-T frontend. Like the Duo, these can run one digital and one analog stream in parallel. Finally, card shapes. Each card type comes in CardBus, PCI, and MiniPCI shape. The flavors are compatible, so that again, the PCI ID data point back to the same card entry for e.g. the PCI and CardBus Duo. The card type/shape combinations are distinctly identified by their subsystem ID. No need to guesstimate anything. That's the plan at least. regards, Peter Hi Peter! Your plan is fine so far. We might add some more comments to group devices obviously together, since those looking first time at it are a bit lost. For such i2c IR limits, we have your and Eddi's comments. Since we can't help it easily, Peter D. should suggest the older version of the MSI A/D for auto detection. It won't make anything more worse on that not fully clear Vivanco stuff, except Hartmut might have ideas. Cheers, Hermann I think that you just suggested something. I'm going to stand at the side and nod my head. ;-) What should I do to make it an official suggestion? -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Update to au-Melbourne scan list
On Monday 11 February 2008, Bruce Schultz wrote: On 21/01/08 08:13, Peter D. wrote: On Monday 21 January 2008, Bruce Schultz wrote: On 20/01/08 20:47, Peter D. wrote: On Sunday 20 January 2008, Jeff Bailes wrote: Hi, Back in November, channel Seven changed their fec_hi from 2/3 to 3/4 causing scans to not pick it up ( http://www.dba.org.au/index.asp?sectionID=39newsID=982display=news ). The new entry in the au-Melbourne file for channel seven should be: # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE I attached the complete updated file anyway. Jeff They are a pain. Anyway, according to the web site that you quoted, all tuners that comply with Australian standards will cope without adjustment. Unfortunately not all tuners comply with Australian standards. :-( Presumably all au-tuning_files should have their channel 7 entry updated. Can this be done at the data base end, or do all files have to be re-submitted? Also the GI in Brisbane is noted as changing as well. I can confirm that the au-Brisbane scan file needs to change. It works now for me with the same channel 7 line that Jeff included above. Scan wasn't finding channel 7 without the change. Did you just change fec_hi, or did you change the Guard Interval as well? The quoted web page states that the GI is now 1/16. (It is possible that your card is smart enough to sort out GI by itself, but not fec_hi.) Sorry about the belated reply Yes, I changed the GI to 1/16. Bruce, That's OK. Do you feel competent to submit an updated file for Brisbane? -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] auto detection of Flytv duo/hybrid and pci/cardbus confusion
Hi,
I've finally gotten around to reading the code and trying to get my
PCI MSI [EMAIL PROTECTED] A/D card auto detected.
First clarification, duo versus hybrid.
Are duo cards equipped with two independent tuners that can both be
used at the same time?
Are hybrid cards necessarily equipped with digital and analogue tuners?
Can a two tuner card be both a duo and a hybrid, if one tuner is digital
the other is analogue and they can both be used at the same time?
Second clarification, PCI versus cardbus.
They don't look anything like each other, but can they be logically
interchangeable? If the code for a cardbus tuner happens to work for
a PCI tuner is there anything wrong with referring to the PCI tuner
as a cardbus device?
Looking at http://www.linuxtv.org/wiki/index.php/DVB-T_PCMCIA_Cards
there does not appear to be any such thing as a
SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS, despite the entry (number 94)
in saa7134.h. Looking at
http://www.linuxtv.org/wiki/index.php/DVB-T_PCI_Cards#LifeView
there is a PCI version - but there is no PCI version in saa7134.h.
Should
SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS be changed to
SAA7134_BOARD_FLYDVBT_HYBRID?
It appears that both PCI and cardbus versions of the Flytv duo exist
and are listed in saa7134.h - despite slightly inconsistent punctuation;
SAA7134_BOARD_FLYDVBTDUO versus
SAA7134_BOARD_FLYDVBT_DUO_CARDBUS.
Should
SAA7134_BOARD_FLYDVBTDUO be changed to
SAA7134_BOARD_FLYDVBT_DUO?
I have an MSI [EMAIL PROTECTED] A/D PCI card that works with the option card=94
There appears to not be an entry in struct pci_device_id saa7134_pci_tbl[]
in saa7134-cards.c for my card. There is a reference to a
[EMAIL PROTECTED] DUO which I guess is a valid entry for a different card.
Is the entry;
{
.vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7133,
.subvendor= 0x4e42,
.subdevice= 0x3502,
.driver_data = SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS
},
supposed to be;
{
.vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7133,
.subvendor= 0x4E42, /* MSI */
.subdevice= 0x3306, /* [EMAIL PROTECTED] Hybrid A/D
*/
driver_data = SAA7134_BOARD_FLYDVBT_HYBRID_CARDBUS,
},
with the subdevice changed, or possibly;
{
.vendor = PCI_VENDOR_ID_PHILIPS,
.device = PCI_DEVICE_ID_PHILIPS_SAA7133,
.subvendor= 0x4E42, /* MSI */
.subdevice= 0x3306, /* [EMAIL PROTECTED] Hybrid A/D
*/
driver_data = SAA7134_BOARD_FLYDVBT_HYBRID,
},
with the subdevice and driver_data changed, or should there be an extra
entry in the list?
Thank you.
--
sig goes here...
Peter D.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AVerMedia DVB-S Hybrid+FM and DVB-S Pro [A700]
Am Dienstag, 12. Februar 2008 schrieben Sie: I added this to the wiki-page about A700: http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_DVB-S_Pro_(A700) Maybe we should rename the page to AverMedia_AverTV_DVB-S_A700 or anything similar. * Could you load saa7134 module of unpatched driver, but with parameter i2c_scan=1. * lspci -vvnn also should be interesting * If you have a camera, could you do a picture, so we can get info about the used analog tuner. I guess it is some XC30??. But to get it running you should contact video4linux mailinglist. Regards Matthias Hello Matthias, if I load the saa7134 module of unpatched driver, but with parameter i2c_scan=1, dmesg shows (Kernel 2.6.24-gentoo-r2) saa7130/34: v4l2 driver version 0.2.14 loaded saa7133[0]: found at :02:07.0, rev: 209, irq: 18, latency: 64, mmio: 0xd3024000 saa7133[0]: subsystem: 1461:a7a2, board: UNKNOWN/GENERIC [card=0,autodetected] saa7133[0]: board init: gpio is 6da00 saa7133[0]: i2c eeprom 00: 61 14 a2 a7 ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c scan: found device @ 0x1c [???] saa7133[0]: i2c scan: found device @ 0xa0 [eeprom] saa7133[0]: registered device video0 [v4l2] saa7133[0]: registered device vbi0 and lspci -vvnn returns 02:07.0 Multimedia controller [0480]: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder [1131:7133] (rev d1) Subsystem: Avermedia Technologies Inc Unknown device [1461:a7a2] 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: 64 (63750ns min, 63750ns max) Interrupt: pin A Route to IRQ 18 Region 0: Memory at d3024000 (32-bit, non-prefetchable) [size=2K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=3 PME- Kernel driver in use: saa7134 Kernel modules: saa7134 I did some pictures too... the link to them is in a PM for you. The analog tuner seems to be a XC2028, but I don't see any possibilities to test the tuner. Regards Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] AVerMedia DVB-S Hybrid+FM and DVB-S Pro [A700]
Hello, I'm watching this list for quite a while now, looking forward to see my Avermedia AVerTV DVB-S Hybrid+FM supported. This card looks very similar to the Avermedia AVerTV DVB-S Pro [A700], so I tried the two existing patches. Finally, Matthias Schwarzott's (zzam) patch a700_full_20080204 did it. DVB-S is working very well using Kaffeine 0.8.5, input via S-Video or Composite worked, since I bought the card, and is still working. Is it possible, to add the cards ID (1461:a7a2) to the list? Thanks for all the work you did! Ich ziehe meinen Hut! Best regards, Peter Meszmer ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AVerMedia DVB-S Hybrid+FM and DVB-S Pro [A700]
Am Donnerstag, 7. Februar 2008 schrieben Sie: @Peter: 1. Maybe you want to start a page in the wiki dedicated to your card. Or should we check for similarity and merge both of these cards into one page? At least I am interested in the eeprom content of your card. I should request some schematics from Avermedia to maybe get gpio controlling correct. (Like resetting chips, ir ...) Regards Matthias Hello Matthias, the eeprom content is slightly different form the one shown on the wiki: saa7133[0]: found at :02:07.0, rev: 209, irq: 18, latency: 64, mmio: 0xd3024000 saa7133[0]: subsystem: 1461:a7a2, board: Avermedia A700 [card=132,autodetected] saa7133[0]: board init: gpio is 48a00 saa7133[0]: i2c eeprom 00: 61 14 a2 a7 ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom e0: 00 01 81 af d7 09 ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: registered device video0 [v4l2] saa7133[0]: registered device vbi0 DVB: registering new adapter (saa7133[0]) Writing a page in the wiki sounds interesting, but I think, I shouldn't start this project. So I would prefer to merge the information of both cards. Best regards Peter Meszmer ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] PULL request for a bunch of DiBcom-based changes
On Fri, 2008-01-25 at 11:36 +0100, Patrick Boettcher wrote: Hi Mauro, Can you please pull from http://linuxtv.org/hg/~pb/v4l-dvb/ for a bunch of changes for DiBcom-based hardware. All users, can you please test, whether I broke something committing all of that. Thanks to everyone who contributed to improved device-quality and support. I tried this with my TV-QQ usb dvb-t device. dmesg gives :- usb 3-4: new high speed USB device using ehci_hcd and address 5 usb 3-4: new device found, idVendor=10b8, idProduct=1e78 usb 3-4: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 3-4: Product: TV QQ T-03S usb 3-4: Manufacturer: East Sun Inc. usb 3-4: SerialNumber: 086755 usb 3-4: configuration #1 chosen from 1 choice dib0700: loaded with support for 6 different device-types dvb-usb: found a 'DiBcom STK7700P reference design' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'DiBcom STK7700P reference design' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DiBcom STK7700P reference design) DVB: registering frontend 0 (DiBcom 7000PC)... MT2060: successfully identified (IF1 = 1220) input: IR-receiver inside an USB DVB receiver as /class/input/input9 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: DiBcom STK7700P reference design successfully initialized and connected. But it doesn't appear to tune :- $ dvbscan /usr/share/dvb/scan/dvb-t/uk-CrystalPalace scanning /usr/share/dvb/scan/dvb-t/uk-CrystalPalace using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 50583 0 3 9 1 0 0 0 tune to: 50583:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 50583:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. Is there anything I can do ? Also, I can't see any sign of analogue ( which, according to the box, this device is supposed to support ). cheers, Pete -- --- Peter Lord -- Please bottom post, for examples, please see http://mailformat.dan.info/quoting/bottom-posting.html and http://www.kassj.com/netiquette/netiquette.html#5 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] build problems
Hi All, I've searched around but I've not found this reported. When building, I see the following objdump warning :- CC [M] /home/plord/src/v4l/v4l-dvb/v4l/zoran_card.o objdump: invalid option -- h and then :- LD [M] /home/plord/src/v4l/v4l-dvb/v4l/saa7146.o ld: cannot load ld backend library 'libld_elf_x86_64.so': libld_elf_x86_64.so: cannot open shared object file: No such file or directory I'm using stock opensuse 10.3 on x86_64 Thanks, Pete -- --- Peter Lord -- Please bottom post, for examples, please see http://mailformat.dan.info/quoting/bottom-posting.html and http://www.kassj.com/netiquette/netiquette.html#5 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] build problems
On Sun, 2008-01-27 at 09:35 +, Peter Lord wrote: Hi All, I've searched around but I've not found this reported. When building, I see the following objdump warning :- CC [M] /home/plord/src/v4l/v4l-dvb/v4l/zoran_card.o objdump: invalid option -- h and then :- LD [M] /home/plord/src/v4l/v4l-dvb/v4l/saa7146.o ld: cannot load ld backend library 'libld_elf_x86_64.so': libld_elf_x86_64.so: cannot open shared object file: No such file or directory I'm using stock opensuse 10.3 on x86_64 Ah. I had installed a different version of ld in /usr/local/bin which was being picked up by the build ... removing that junk fixed the problem ! Pete -- --- Peter Lord -- Please bottom post, for examples, please see http://mailformat.dan.info/quoting/bottom-posting.html and http://www.kassj.com/netiquette/netiquette.html#5 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] saa7134 TUN 900 card remote driver
I think that you are asking in the correct place BUT you are addressing a bunch of volunteers working on their hobby. Things get done when someone feels inspired to do something. There probably isn't a HOWTO. If you find one let me know. I have an MSI without remote support and a Kworld with remote support that I haven't managed to get working. :-( You are, of course, welcome to do any work that you are up to doing yourself. ;-) Peter D. On Saturday 26 January 2008, Timothy E. Krantz wrote: Hmmm, no response yet. Am I asking in the wrong place? _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Timothy E. Krantz Sent: Thursday, January 24, 2008 2:48 PM To: linux-dvb@linuxtv.org Subject: [linux-dvb] saa7134 TUN 900 card remote driver Hi, looking at the code for the TUN 900 (card 66) part of the saa7134 driver I see that it says that the remote control is not implemented. Can someone point me in the direction of a FAQ or HOWTO that would get me started on fixing that? Thanks in Advance. Tim -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Locking problem in dvb_demux?
Manu Abraham wrote:
[EMAIL PROTECTED] wrote:
Hi,
I am running a Hauppauge NOVA-S plus (cx2388x based card) and an older
technotrend S-1500 card in the same chassis. Trying to debug other problems
I have turned on lock debugging in the kernel and have started getting the
following dump when both cards are started:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547514]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547515]
=
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547519] [ INFO: inconsistent lock
state ]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547521] 2.6.23.14 #5
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547523]
-
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547525] inconsistent {softirq-on-W}
- {in-softirq-W} usage.
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547527] startup1.pl/13742
[HC0[0]:SC1[1]:HE1:SE0] takes:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547532] (dvbdemux-lock){-+..},
at: [f0a10df9] dvb_dmx_swfilter_packets+0x1f/0x49 [dvb_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547590] {softirq-on-W} state was
registered at:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547598] [c0440eb7]
__lock_acquire+0x4aa/0xc1a
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547615] [c04416a1]
lock_acquire+0x7a/0x94
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547682] [c06339bd]
_spin_lock+0x2e/0x58
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547712] [f0a10c8b]
dvb_dmx_swfilter+0x21/0x104 [dvb_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547737] [f0d22383]
videobuf_dvb_thread+0x83/0x105 [video_buf_dvb]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547752] [c0435b9c]
kthread+0x3b/0x63
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547804] [c0405b9f]
kernel_thread_helper+0x7/0x10
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547874] [] 0x
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547888] irq event stamp: 22178648
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547889] hardirqs last enabled at
(22178648): [c04298e8] tasklet_action+0x26/0xa8
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547893] hardirqs last disabled at
(22178647): [c04298cd] tasklet_action+0xb/0xa8
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547896] softirqs last enabled at
(22178536): [c0429889] __do_softirq+0xe3/0xe9
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547899] softirqs last disabled at
(22178645): [c0407046] do_softirq+0x61/0xc7
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547903]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547903] other info that might help
us debug this:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547904] no locks held by
startup1.pl/13742.
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547906]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547906] stack backtrace:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547908] [c0405f18]
show_trace_log_lvl+0x1a/0x2f
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547911] [c040690a]
show_trace+0x12/0x14
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547914] [c0406922]
dump_stack+0x16/0x18
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547916] [c043f3b9]
print_usage_bug+0x140/0x14a
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547919] [c0440070]
mark_lock+0x12e/0x45b
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547921] [c0440e47]
__lock_acquire+0x43a/0xc1a
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547923] [c04416a1]
lock_acquire+0x7a/0x94
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547926] [c06339bd]
_spin_lock+0x2e/0x58
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547928] [f0a10df9]
dvb_dmx_swfilter_packets+0x1f/0x49 [dvb_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547937] [f091f73a]
vpeirq+0xc0/0x130 [budget_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547941] [c0429915]
tasklet_action+0x53/0xa8
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547943] [c0429815]
__do_softirq+0x6f/0xe9
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547946] [c0407046]
do_softirq+0x61/0xc7
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547948] ===
Jan 22 11:00:18 TEMERAIRE kernel: [ 219.745305] saa7146_i2c_writeout: timed
out waiting for end of xfer
The same dump occurs with different processes named in the line:
startup1.pl/13742 [HC0[0]:SC1[1]:HE1:SE0] takes:, though the rest is
essentially the same.
Now, I am interpreting this as saying that the demux-lock used in
dvb_dxm_swfilter and dvb_dmx_swfilter_packets has become inconsistent. I
think this has happened because one of the locks was taken from a soft IRQ.
Changing the spinlocks to spin_lock_irqsave/restore on that lock object in
dvb_demux.c has stopped that error message.
I am not an expert in this, but is this the correct interpretation and
resolution? If so, I'll send a patch. If this is not the correct way of
fixing this,
[linux-dvb] Locking problem in dvb_demux?
Hi,
I am running a Hauppauge NOVA-S plus (cx2388x based card) and an older
technotrend S-1500 card in the same chassis. Trying to debug other problems I
have turned on lock debugging in the kernel and have started getting the
following dump when both cards are started:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547514]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547515]
=
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547519] [ INFO: inconsistent lock
state ]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547521] 2.6.23.14 #5
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547523]
-
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547525] inconsistent {softirq-on-W} -
{in-softirq-W} usage.
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547527] startup1.pl/13742
[HC0[0]:SC1[1]:HE1:SE0] takes:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547532] (dvbdemux-lock){-+..}, at:
[f0a10df9] dvb_dmx_swfilter_packets+0x1f/0x49 [dvb_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547590] {softirq-on-W} state was
registered at:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547598] [c0440eb7]
__lock_acquire+0x4aa/0xc1a
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547615] [c04416a1]
lock_acquire+0x7a/0x94
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547682] [c06339bd]
_spin_lock+0x2e/0x58
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547712] [f0a10c8b]
dvb_dmx_swfilter+0x21/0x104 [dvb_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547737] [f0d22383]
videobuf_dvb_thread+0x83/0x105 [video_buf_dvb]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547752] [c0435b9c]
kthread+0x3b/0x63
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547804] [c0405b9f]
kernel_thread_helper+0x7/0x10
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547874] [] 0x
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547888] irq event stamp: 22178648
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547889] hardirqs last enabled at
(22178648): [c04298e8] tasklet_action+0x26/0xa8
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547893] hardirqs last disabled at
(22178647): [c04298cd] tasklet_action+0xb/0xa8
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547896] softirqs last enabled at
(22178536): [c0429889] __do_softirq+0xe3/0xe9
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547899] softirqs last disabled at
(22178645): [c0407046] do_softirq+0x61/0xc7
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547903]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547903] other info that might help us
debug this:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547904] no locks held by
startup1.pl/13742.
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547906]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547906] stack backtrace:
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547908] [c0405f18]
show_trace_log_lvl+0x1a/0x2f
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547911] [c040690a]
show_trace+0x12/0x14
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547914] [c0406922]
dump_stack+0x16/0x18
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547916] [c043f3b9]
print_usage_bug+0x140/0x14a
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547919] [c0440070]
mark_lock+0x12e/0x45b
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547921] [c0440e47]
__lock_acquire+0x43a/0xc1a
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547923] [c04416a1]
lock_acquire+0x7a/0x94
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547926] [c06339bd]
_spin_lock+0x2e/0x58
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547928] [f0a10df9]
dvb_dmx_swfilter_packets+0x1f/0x49 [dvb_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547937] [f091f73a]
vpeirq+0xc0/0x130 [budget_core]
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547941] [c0429915]
tasklet_action+0x53/0xa8
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547943] [c0429815]
__do_softirq+0x6f/0xe9
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547946] [c0407046]
do_softirq+0x61/0xc7
Jan 22 11:00:17 TEMERAIRE kernel: [ 218.547948] ===
Jan 22 11:00:18 TEMERAIRE kernel: [ 219.745305] saa7146_i2c_writeout: timed
out waiting for end of xfer
The same dump occurs with different processes named in the line:
startup1.pl/13742 [HC0[0]:SC1[1]:HE1:SE0] takes:, though the rest is
essentially the same.
Now, I am interpreting this as saying that the demux-lock used in
dvb_dxm_swfilter and dvb_dmx_swfilter_packets has become inconsistent. I think
this has happened because one of the locks was taken from a soft IRQ.
Changing the spinlocks to spin_lock_irqsave/restore on that lock object in
dvb_demux.c has stopped that error message.
I am not an expert in this, but is this the correct interpretation and
resolution? If so, I'll send a patch. If this is not the correct way of fixing
this, does anyone have any suggestions?
This is of course using an SMP kernel and I have a Intel Core2 6700 @ 2.66GHz
processor.
Cheers
Pete
Re: [linux-dvb] linux device ordering at boot time
Dear Alan, dear kernel dvb hackers, Am Sonntag, 20. Januar 2008 schrieb Alan Cox: Well, it's a major pain in the a**. I've no idea, what reversed the order of PCI devices, but I had to disable the automatic dvb driver loading in order It depends on the order you load the modules Sure, but given, that userspace didn't changed meanwhile, I relied on some hotplug figure before (in openSUSE 10.2 with 2.6.18) to load the modules in the correct order which itself surely enumerates the PCI bus in some way. After switching to 2.6.24-rc this order was reversed. At least, my budget card was first now, while the ff dvb card second, which resulted in a working vdr, unfortunately without picture and sound (that dropped the WAF immensely 8-|). I solved this issue by blacklisting both cards in /etc/modprobe.d/blacklist, and manually determined the order and which modules to load, only to discover, that the system won't wake up on the scheduled times anymore. Ahh, /proc/acpi/alarm disappeared and needed adaption to /sys/class/rtc/rtc0/wakealarm. That move seems to have (yet to examine, but easy to work around) timezone issues. On the bright side, this new interface doesn't interfere with setting the c-mos clock on power down anymore. One gross hack down. Cool. The last regressions awaiting to get tackled are: - rewind is somewhat broken: after a few seconds rewinding correctly, the pictures stutter, and vdr uses cpu like mad. - from time to time, the same happens for a few seconds on simple replay. Both issues _feel_ like locking artefacts, which 2.6.18 (with http://linuxtv.org/hg/v4l-dvb drivers) didn't suffer from (my vdr operates mostly on nfs3 mounted files). I'm trying to explore these problems in more detail and will come back. For the record, these issues happen with the factory drivers/media modules and with drivers from v4l-dvb tree. Please don't get me wrong, I'm not whining about all this, it's just a report from user side about what happens, if one tries to follow a strong moving target. Take it as a reminder, that some decisions during (kernel) development does have an wider impact on us poor users out there, as it seems. The only thing, what makes me really sad, is that current dvb development is distracted by political and emotional (ego-logical) reasons, repressing the full potential in this area. Pete ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Update to au-Melbourne scan list
On Sunday 20 January 2008, Jeff Bailes wrote: Hi, Back in November, channel Seven changed their fec_hi from 2/3 to 3/4 causing scans to not pick it up ( http://www.dba.org.au/index.asp?sectionID=39newsID=982display=news ). The new entry in the au-Melbourne file for channel seven should be: # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE I attached the complete updated file anyway. Jeff They are a pain. Anyway, according to the web site that you quoted, all tuners that comply with Australian standards will cope without adjustment. Unfortunately not all tuners comply with Australian standards. :-( Presumably all au-tuning_files should have their channel 7 entry updated. Can this be done at the data base end, or do all files have to be re-submitted? Also the GI in Brisbane is noted as changing as well. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Update to au-Melbourne scan list
On Monday 21 January 2008, Bruce Schultz wrote: On 20/01/08 20:47, Peter D. wrote: On Sunday 20 January 2008, Jeff Bailes wrote: Hi, Back in November, channel Seven changed their fec_hi from 2/3 to 3/4 causing scans to not pick it up ( http://www.dba.org.au/index.asp?sectionID=39newsID=982display=news ). The new entry in the au-Melbourne file for channel seven should be: # Seven T 17750 7MHz 3/4 NONE QAM64 8k 1/16 NONE I attached the complete updated file anyway. Jeff They are a pain. Anyway, according to the web site that you quoted, all tuners that comply with Australian standards will cope without adjustment. Unfortunately not all tuners comply with Australian standards. :-( Presumably all au-tuning_files should have their channel 7 entry updated. Can this be done at the data base end, or do all files have to be re-submitted? Also the GI in Brisbane is noted as changing as well. I can confirm that the au-Brisbane scan file needs to change. It works now for me with the same channel 7 line that Jeff included above. Scan wasn't finding channel 7 without the change. Did you just change fec_hi, or did you change the Guard Interval as well? The quoted web page states that the GI is now 1/16. (It is possible that your card is smart enough to sort out GI by itself, but not fec_hi.) -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Another compiling issue em28xx-audio.c
Am Samstag, 19. Januar 2008 schrieb [EMAIL PROTECTED]: im running ubuntu hardy 8.04 with the 2.6.24-4-generic linux kernel based of of the 2.6.24-rc6 linux kerneli get this error running make in the v4l-dvb folder make -C /home/eric/build/mercurial/v4l-dvb/v4l make[1]: Entering directory `/home/eric/build/mercurial/v4l-dvb/v4l' creating symbolic links... Kernel build directory is /lib/modules/2.6.24-4-generic/build make -C /lib/modules/2.6.24-4-generic/build SUBDIRS=/home/eric/build/mercurial/v4l-dvb/v4l modules make[2]: Entering directory `/usr/src/linux-headers-2.6.24-4-generic' CC [M] /home/eric/build/mercurial/v4l-dvb/v4l/em28xx-audio.o In file included from /home/eric/build/mercurial/v4l-dvb/v4l/em28xx-audio.c:39: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) /home/eric/build/mercurial/v4l-dvb/v4l/em28xx-audio.c:58: error: array index in initializer not of integer type /home/eric/build/mercurial/v4l-dvb/v4l/em28xx-audio.c:58: error: (near initialization for 'index') make[3]: *** [/home/eric/build/mercurial/v4l-dvb/v4l/em28xx-audio.o] Error 1 make[2]: *** [_module_/home/eric/build/mercurial/v4l-dvb/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-4-generic' make[1]: *** [default] Error 2 make[1]: Leaving directory `/home/eric/build/mercurial/v4l-dvb/v4l' make: *** [all] Error 2 is it another issue like the radio-si470x.c not compiling I'm not sure, if it's the right fix, but this patch fixed it for me: --- em28xx-audio.c~ 2008-01-19 00:14:24.0 +0100 +++ em28xx-audio.c 2008-01-19 00:33:26.891186900 +0100 @@ -36,6 +36,7 @@ #include linux/proc_fs.h #include linux/module.h #include compat.h +#include sound/driver.h #include sound/core.h #include sound/pcm.h #include sound/pcm_params.h Hth, Pete ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Multiproto ???
On Jan 16, 2008 4:17 PM, Stephen Rowles [EMAIL PROTECTED] wrote: Ouchy, I'll revise my hardware estimate then if they are 1080i I will need a seriously quick processor, or the VAAPI project to get off the ground quickly then :D Not sure what you mean by seriously quick processor, but just to add a data point, I'm using an Intel core2duo E6600 in MythTV and a patch to enable dual core decoding of h264. Picture quality is very good! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Lockups with cx2388x cards
Steven Toth wrote: Peter Martin wrote: I have a couple of Hauppauge cards (Nova-T using the cx2388x and a Nova Plus, again using an cx2388x) in an industrial motherboard (an Axiomtek ATX6022-14G) which is causing me some grief. After a short time I am getting both cards locking up (no DMA) at the same time. Does it happen with only a single card active in the system? Yes it does. If I start streaming from one card, it runs for a few minutes, then I get the timeout. I am then unable to start streaming from the other card after this. I will try a single card in the motherboard later. Have you tried the cards on other motherboards and do they operate successfully without error? Both these cards work fine in other motherboards, indeed they work with up to 5 cards for extended periods. In order to get these cards working at all in this configuration, I have re-arranged the SRAM and increased the FIFO size in cx88-core.c to 0x4800 bytes, and disabled all the other channels (video, audio etc), which has cured the FIFO overflow errors I was getting ( general errors: 0x0100), but the cards still lock up. The cards can run from between 5 seconds and 30 minutes before the lockup. I also get the lockups with the stock code, so I am happy that my SRAM chganges have not broken anything. IIRC, the fifo is pretty small (resulting in potential short latency issues). This could be compounded with a busy DMA bus and short fifo's both competing for the same DMA queue resource. I suspect increasing the fifo really just masks the real DMA contension issue. Sounds plausible. Since the failure of one card affects the other card(s) then I suspect you are right and there is a common DMA problem here. Any suggestions as to how I can look for this, I am a relative newbie to debugging PC systems at this level. FWIW, the PCI bridge is a Pericom P17C 8150B. What else is happening DMA wise in your system? Not a lot of other DMA activity. A bit of disk IO for logging, and and 100Kbps for ethernet, but this is all being done on the controlling SBC anyway which is behind the Pericom bridge. Pete - Steve ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] BUG in videobuf-core.c:73 (MAGIC_CHECK mismatch)
Dear DVB developers, after switching to current http://linuxtv.org/hg/v4l-dvb (2008-01-11 01:03 CET) on an openSUSE 10.2 based vdr system, I harvest these reproducible crashes on trying to record something: Jan 11 01:25:47 ziggy vdr: [3874] switching device 2 to channel 22 Jan 11 01:25:47 ziggy vdr: [3874] timer 12 (22 0055-0140 'Domian unterwegs') start Jan 11 01:25:47 ziggy vdr: [3874] Title: 'Domian unterwegs' Subtitle: '(null)' Jan 11 01:25:47 ziggy vdr: [3874] record /video0/Domian_unterwegs/2008-01-11.00.55.99.99.rec Jan 11 01:25:47 ziggy vdr: [3874] cFileName::SetOffset: removing zero-sized file /video0/Domian_unterwegs/2008-01-11.00.55.99.99.rec/001.vdr Jan 11 01:25:47 ziggy vdr: [3874] recording to '/video0/Domian_unterwegs/2008-01-11.00.55.99.99.rec/001.vdr' Jan 11 01:25:47 ziggy vdr: [4053] file writer thread started (pid=3874, tid=4053) Jan 11 01:25:47 ziggy vdr: [4054] recording thread started (pid=3874, tid=4054) Jan 11 01:25:47 ziggy vdr: [4055] receiver on device 2 thread started (pid=3874, tid=4055) Jan 11 01:25:47 ziggy vdr: [4056] TS buffer on device 2 thread started (pid=3874, tid=4056) Jan 11 01:25:47 ziggy kernel: Error: mmap_mapper() never called! Jan 11 01:25:47 ziggy kernel: magic mismatch: f6941bc0 (expected 20070728) Jan 11 01:25:47 ziggy kernel: [ cut here ] Jan 11 01:25:47 ziggy kernel: kernel BUG at /usr/src/kernel-modules/v4l-dvb/v4l/videobuf-core.c:73! Jan 11 01:25:47 ziggy kernel: invalid opcode: [#1] SMP Jan 11 01:25:47 ziggy kernel: last sysfs file: /devices/pci:00/:00:18.3/temp3_input Jan 11 01:25:47 ziggy kernel: Modules linked in: nfsd auth_rpcgss exportfs ipv6 autofs4 snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device nfs lock d nfs_acl sunrpc af_packet cpufreq_conservative cpufreq_userspace cpufreq_powersave powernow_k8 zl10353 xc5000 ves1820 tua6100 tda827x tda826x td a8083 tda18271 tda10086 tda1004x tda10023 tda10021 stv0297 sp887x sp8870 s5h1420 s5h1409 qt1010 or51211 or51132 nxt6000 nxt200x mt352 mt312 mt226 6 mt2131 mt2060 lnbp21 lgdt330x l64781 dvb_pll dib7000p dib7000m dib3000mc dibx000_common dib3000mb dib0070 cx24110 cx22702 cx22700 bcm3510 stv02 99 ves1x93 dvb_ttpci button battery ac power_supply nls_utf8 ntfs loop isl6421 cx24123 cx88_dvb cx88_vp3054_i2c videobuf_dvb cx88_alsa snd_pcm sn d_timer snd soundcore rtc_cmos snd_page_alloc cx8800 rtc_core cx8802 cx88xx dvb_core rtc_lib firmware_class ir_common saa7146_vv i2c_algo_bit k8t emp saa7146 compat_ioctl32 tveeprom videobuf_dma_sg videodev hwmon videobuf_core v4l2_common v4l1_compat btcx_risc ttpci_eeprom ohci1394 ieee1394 forcedeth Jan 11 01:25:47 ziggy kernel: ide_cd cdrom ohci_hcd ehci_hcd usbcore i2c_nforce2 i2c_core parport_pc lp parport xfs edd sg fan sata_nv libata amd 74xx thermal processor sd_mod scsi_mod ide_disk ide_core Jan 11 01:25:47 ziggy kernel: Jan 11 01:25:47 ziggy kernel: Pid: 4052, comm: cx88[0] dvb Tainted: G N (2.6.24-rc7-20080109173439-default #1) Jan 11 01:25:47 ziggy kernel: EIP: 0060:[f91e4608] EFLAGS: 00010282 CPU: 0 Jan 11 01:25:47 ziggy kernel: EIP is at videobuf_waiton+0x4d/0xe9 [videobuf_core] Jan 11 01:25:47 ziggy kernel: EAX: 0030 EBX: dfc2b1ac ECX: 0046 EDX: 0046 Jan 11 01:25:47 ziggy kernel: ESI: EDI: f6961fb0 EBP: 0001 ESP: f6961f90 Jan 11 01:25:47 ziggy kernel: DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 Jan 11 01:25:47 ziggy kernel: Process cx88[0] dvb (pid: 4052, ti=f696 task=f69626f0 task.ti=f696) Jan 11 01:25:47 ziggy kernel: Stack: f91e580a f6941bc0 20070728 f69626f0 c0120107 Jan 11 01:25:47 ziggy kernel:dfc2b1d0 dfc2b110 dfc2b1ac f9307361 dfc2b110 dfc2b110 Jan 11 01:25:47 ziggy kernel:f93072fb c01361b1 c0136179 c0106307 f7125de0 Jan 11 01:25:47 ziggy kernel: Call Trace: Jan 11 01:25:47 ziggy kernel: [f9307361] videobuf_dvb_thread+0x66/0x131 [videobuf_dvb] Jan 11 01:25:47 ziggy kernel: [c01361b1] kthread+0x38/0x5d Jan 11 01:25:47 ziggy kernel: [c0106307] kernel_thread_helper+0x7/0x10 Jan 11 01:25:47 ziggy kernel: === Jan 11 01:25:47 ziggy kernel: Code: a1 00 10 45 c0 89 44 24 10 8b 43 04 3d 28 07 07 20 74 1c c7 44 24 08 28 07 07 20 89 44 24 04 c7 04 24 0a 58 1 e f9 e8 b1 f4 0f c7 0f 0b eb fe 8d 43 34 8d 54 24 0c e8 8b 1f f5 c6 eb 67 85 f6 74 Jan 11 01:25:47 ziggy kernel: EIP: [f91e4608] videobuf_waiton+0x4d/0xe9 [videobuf_core] SS:ESP 0068:f6961f90 Jan 11 01:25:47 ziggy kernel: ---[ end trace 89f8cead76ef35ad ]--- Jan 11 01:25:48 ziggy vdr: [3959] channel 22 (EinsFestival) event Fre 11.01.2008 01:00-01:30 (VPS: 11.01 00:59) 'Domian unterwegs' status 4 Jan 11 01:25:51 ziggy vdr: [3874] connect from 127.0.0.2, port 42097 - accepted Jan 11 01:25:51 ziggy vdr: [3876] video directory scanner thread ended (pid=3874, tid=3876) Jan 11 01:25:52 ziggy vdr: [3874] closing SVDRP connection Jan 11 01:25:56 ziggy vdr: [3961] frontend 1 timed out while
[linux-dvb] Lockups with cx2388x cards
I have a couple of Hauppauge cards (Nova-T using the cx2388x and a Nova Plus, again using an cx2388x) in an industrial motherboard (an Axiomtek ATX6022-14G) which is causing me some grief. After a short time I am getting both cards locking up (no DMA) at the same time. In order to get these cards working at all in this configuration, I have re-arranged the SRAM and increased the FIFO size in cx88-core.c to 0x4800 bytes, and disabled all the other channels (video, audio etc), which has cured the FIFO overflow errors I was getting ( general errors: 0x0100), but the cards still lock up. The cards can run from between 5 seconds and 30 minutes before the lockup. I also get the lockups with the stock code, so I am happy that my SRAM chganges have not broken anything. I am using the latest hg code and kernel 2.6.23.8 The processor is a Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz I have tried the system with maxcpus=0 and maxcpus=1 kernel parameter with the same results, so it is not an SMP/locking problem as far as I can tell. I have tried changing the pci latencies using both setpci and by changing the module paramers from 0 to 128, again with no real change. Just before the lock up, there is a cx88 timeout, (DMA or PCI locked up maybe?). As far as I can see, the timeout will almost always result in the cards stopping. The rest of the system runs fine, and a module unload/reload usually puts things right. The relevant part of the syslog messages looks like this, though I have added few more printks to try to see what is happening. Sometimes, the RISC dump contains INVALID opcodes, though I don't understand enough about the RISC controller at the moment to say whether this is important or not. It looks like after the restarting of the queues, the DMA does not start. Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]/2-mpeg: Timeout in cx88 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]/2-mpeg: cx8802_timeout Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: mpeg - CX88-CORE dma channel status dump Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: initial risc: 0x0c813000 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: cdt base: 0x00180800 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: cdt size: 0x0040 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: iq base : 0x001807c0 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: iq size : 0x0010 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: risc pc : 0x0c813038 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: iq wr ptr : 0x01fe Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: iq rd ptr : 0x01f2 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: cdt current : 0x0808 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: pci target : 0x Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cmds: line / byte : 0x Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: risc0: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: risc1: 0x07332000 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: risc2: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: risc3: 0x073322f0 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 0: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 1: 0x07332000 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 2: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 3: 0x073322f0 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 4: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 5: 0x073325e0 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 6: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 7: 0x073328d0 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 8: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq 9: 0x07332bc0 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq a: 0x18000150 [ write sol count=336 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq b: 0x07332eb0 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq c: 0x140001a0 [ write eol count=416 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq d: 0x0cedf000 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq e: 0x1c0002f0 [ write sol eol count=752 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: iq f: 0x03ed0490 [ arg #1 ] Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: fifo: 0x00181000 - 0x187000 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: ctrl: 0x001807c0 - 0x180820 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: ptr1_reg: 0x00181000 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: ptr2_reg: 0x00180808 Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cnt1_reg: 0x Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]: cnt2_reg: 0x Jan 9 19:01:32 TEMERAIRE kernel: cx88[1]/2-mpeg: cx8802_stop_dma Jan 9 19:01:32
Re: [linux-dvb] DViCO Dual Digital 4 and remote
Bonne Eggleston wrote: On 11/15/07, Robert Backhaus [EMAIL PROTECTED] wrote: Two questions: 1. Some keys do not generate an event (I've been testing it using xev). Does anyone know how to get all keys to work (an example is the DVD key) I can't recall if this is expected, or necessary. See next response. 2. Has anyone gone and mapped the keycodes to their equivalents? I would normally do it using Xmodmap, but there's probably a better way. I'll do it if noone else already has, but no need to duplicate work ;) Once you have your input device working correctly, just attach lirc to the event device with the 'dev/input' lirc driver and use it like a regular remote - this gives you far more power, and should allow you to map all the buttons. Just follow a tutorial for the DD2 and you should be pretty much there. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] AF9015 (A-Link DTU(m)) test results
Hi all, I tried to run the af9015 driver from http://jusst.de/hg/af901x/ on the A-Link DTU (m) dongle (USB ID 15a4:9016). The firmware seems to load fine, but there are a few errors from mt2060, after which the driver apparently tries to reload the firmware. Running dvbscan with the fi-Espoo scan file (which apparently applies for Helsinki too(?)) seems to get stuck without any results. The driver version is 40fc9491ff06, from Sun, 11 Nov 2007 00:47:17 +0400), with http://jusst.de/manu/fw/AFA/dvb-usb-af9015.fw_a-link saved to /lib/firmware/2.6.22-14-server/dvb-usb-af9015.fw . The kernel is 2.6.22-14-server from Ubuntu, version 2.6.22-14.46 The complete kernel log is at http://pfp.iki.fi/af9015_results_20071112.txt If there's something that would help test this further, please let me know. -peter -- [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] MSI TVanywhere A/D is still not auto detected in 2.6.22.5
Hi, The MSI TV (at) nywhere A/D [4e42:3306] is still not auto detected in 2.6.22 series kernels. It works with the option card=94. (It is a clone of the LifeView FlyDVB-T Hybrid Card [5168:3306,5168:3502].) It is different from; the TVanywhere Plus, the TVanywhere Duo (a LifeView FlyDVB-T Duo clone), the TVanywhere Master and the TVanywhere. Possibly off topic... Could the file linux/Documentation/video4linux/CARDLIST.* have clone names on a different line such as, 94 - LifeView FlyDVB-T Hybrid Cardbus [5168:3306,5168:3502] MSI [EMAIL PROTECTED] A/D [4e42:3306] Even further off topic... Parameters can no longer be passed to modules in /etc/modprobe.preload. Mine had saa7134 card=94 in it. That does not work anymore with recent kernels. It is necessary to put options saa7134 card=94 in /etc/modprobe.conf, or maybe in one of the modprobe* directories. TIA -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge NOVA-T Stick 2: USB Disconnect with *-03-pre1.fw
Have you connected the Nova-T Stick directly to the computer? I have had USB disconnect problems with the WinTV PVR USB2 using a D-Link 7 ports USB hub but have had none with a 7 ports USB hub from Sandberg. Even though the quick start manual from Hauppauge says you should connect the Stick directly to the computer and avoid USB hubs I have had no problems connecting 8 sticks to Sandberg hubs. Have never seen a USB disconnect on these devices with this hub not even when connecting the two hubs in cascade. Peter 2007/8/9, Soeren Moch [EMAIL PROTECTED]: Unfortunately I have to report another USB disconnect. Using the *-03-pre1.fw for my Nova-T Stick 2 (DiB7000P) I had 1 disconnect within the last 10 days (1 disconnect within 5 minutes with older firmware and hg drivers). Although the new firmware is much better, all types of dib0700 devices still seem to suffer from the old disconnect problem (as reported by different people on the list). S:oren ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Wiki page [was [PATCH] Add remote control support for Hauppauge Nova-T 500]
On 7/30/07, Uwe Bugla [EMAIL PROTECTED] wrote: Please do not generalize! :) Me? generalising? If I'm not mistaken, it was Man* that said that every Windows/Microsoft user is a code thief who is not able to code/implement anything or read docs :) There are hundreds of real fine and good unnamed people out there doing a pretty good job. Without their contributions it would never be possible to keep up any kind of infrastructure. Why don't those hundreds of people gather together and ditch the illustrous losers in leadership? It wouldn't be the first time a project forks. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Fix Hauppauge Nova-T 500 USB disconnects
On 7/29/07, Torgeir Veimo [EMAIL PROTECTED] wrote: It was designe`d before dvb usb devices hit the market. That's a lame excuse, specially considering Linux DVB has been worked on for at least 4 years, and there were attempts to refactor things left and right. 4 years is PLENTY of time to properly support device removal. There was at least 1 USB device in 2003/4, the Hauppauge Dec2000-t. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Fix Hauppauge Nova-T 500 USB disconnects
On 7/29/07, Soeren Moch [EMAIL PROTECTED] wrote: I think the crash is caused by the disconnect itself since the dvb stack is not designed to deal with disappearing devices. In other words, the DVB stack was designed to be useless to end users. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Wiki page [was [PATCH] Add remote control support for Hauppauge Nova-T 500]
On 7/29/07, Nicolas Will [EMAIL PROTECTED] wrote: All contributors, First, thanks for your work, very much appreciated, indeed. So do not take the following as a flame, it is not a flame. It's not a flame, it's pointing the obvious truth that Open Source / Community does not work for Lunix DVB. But I'm getting lost. I do not know anymore what works for what, what doesn't, the patching order, what has been committed to the v4l-dvb tree, or not. That is not only a problem of Linux DVB but of Linux in general. Status of what works Nothing Status of what doesn't work, with possible reason Almost everything Dated links to patches, with description Once those patches are committed, date of the commit It's not Xmas yet... Note to timecop: no, I will not use MCE You show how narrow-minded you are if you think MCE is the only other alternative. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge dec2540-t
Hi Kees Stoop schrieb: Hello, Has anyone been able to get this device working under linux ? I am have some trouble with it. When I switch the device on, the correct modules get loaded (ttusb_dec and ttusbdecfe), firmware gets loaded and I do not get any weird messages, so far so good. dmesg gives me: [74969.803277] DVB: registering new adapter (DEC2540-t) [74969.803409] DVB: registering frontend 0 (TechnoTrend/Hauppauge DEC2000-t Frontend)... However when I run tzap, I get lines like this: status 00 | signal 0001 | snr | ber b7f8a858 | unc b7f8ab38 | status 1f | signal 0001 | snr | ber b7f8a858 | unc b7f8ab38 | FE_HAS_LOCK status 1f | signal 0001 | snr | ber b7f8a858 | unc b7f8ab38 | FE_HAS_LOCK The signal-field always reads 0001 and snr is always . I would expect a much higher value for signal then 0001 isn't it ? Only the status field contains valid information, because that's the only information this driver supports. It's just the lack of some error checking in tzap that always all fields are displayed here. I can get a channel list, so part of the driver must be working, but mplayer does not work. I use: mplayer dvb://Nederland 1 -vo x11 The error message that mplayer gives me is: Playing dvb://Nederland 1. dvb_tune Freq: 61800 ERROR IN SETTING DMX_FILTER 7011 for fd 4: ERRNO: 38ERROR, COULDN'T SET CHANNEL 0: Failed to open dvb://Nederland 1. errno:38 is ENOSYS, i guess mplayer tries to set a filter that the driver doesn't support(most likely DMX_TS_PES_OTHER). You probably need to look into the dvb tuning code in mplayer to find out what is happing here. try tuning with tzap and directly opening /dev/dvb/adaper0/dvr0 with mplayer, ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Now and next info
Hi Does anyone have a link to specs on how to decode 'now and next' information available in a DVB stream ? Does anyone know if VDR can do this (yes it is more vdr question) ? WinTV/Happauge have these popups that shows what is being whatch right now and what is coming next. Is any of the 'now and next' info precise enough to use for cutting clips or is precise with a couple of seconds/minutes ? Kind regards Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] tzap output not human readable
On Wednesday 18 July 2007 11:22, P. van Gaans wrote: timecop wrote: Edit the sores, and replace %04x with %d or wahtever suits your fancy. insert rant about you can do this because lunix is opensores (but never mind the fact that since actual real programmers write windows apps, this wouldn't be a problem in teh first place) [snip] I was seriously almost going to ask you where I could find the sores, until I realized the meaning of the word sore in proper English and it's pronunciation. Source versus sores. Was it a joke or a mistake? I guess that timecop was trying to be a little bit rude and funny. Am I allowed to rant on some people on this list? It is hard to stop you. Try to keep it a bit civilised. Remember that facial expressions don't work very well and many jokes don't translate well. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI D VB at Anywhere a.k.a LifeView Hybrid doesn't s can
On Saturday 23 June 2007 09:19, hermann pitton wrote: Hello, Am Freitag, den 22.06.2007, 23:29 +0200 schrieb Werner Braun: Am Freitag, 22. Juni 2007 00:43:44 schrieb hermann pitton: The card in this thread ([EMAIL PROTECTED] a/d) looks exactly like mine: http://www.linuxtv.org/pipermail/linux-dvb/2006-September/012646. html Werner Sorry its late. I am a bit confused: Is analog (via Tuner) partly working or not at all? I can try to retrieve the baseband input configuration from the eeprom dump. I had a glance at the pictures you sent me. Looks like the card supports FM radio - did you try it? There is a chip between antenna input and the tuner chip (TDA8275A) Can you find out its type? It is a unusual package for RF, can you see whether there are traces going to the sucket or to the tuner? Hi, that should be the same RF input switcher we have on the Asus stuff and on the LifeView Trio. It is already addressed in analog mode for radio versus TV, but gpio21 usage can be reversed depending on the manufacturer. On the gpio22 in the comments I have some doubts. Seems not to be in the eeprom? Hartmut and Hermann, ok, I got out the manual and will try to describe the card as good as I can. The card in question is a PCI DVB-T TV (analog) FM Tuner card named Vivanco 21056 (the cardbus version is called 21057). The description claims parallel processing of DVB and analog signal with picture in picture resp. split-screen capacity. It is late here now and just for a first look. It has a combined DVB/Analog connector, an FM connector and one further connector for a combined AV cable with connectors for Composite, S-Video, Audio L/R and IR Remote. The card doesn't have a second Composite input, contrary to what TVTime suggests, there is a connector on the card just next to the AV connector, which seems to provide these interfaces, maybe for the front panel. The second Composite you should get over the S-Video Connector, either with a S-Video signal or with an S-Video to Composite adapter connected. (Not so important, but people wanting to connect two Composite sources don't have to plug connectors if this is present) I haven't bothered trying FM under Linux, but under XP it works. S-Video works under Linux and XP. As mentioned earlier, analog works only for one frequency which is Channel 12 (here: FAB) That must be further investigated. Now for the chips: the big three Philips are (a slash indicates a new line) - SAA7131E / CE0957 / S37513 / T-N05101 - TDA10046A / SA6724-1 06 / ZSG 05111 - 8275AC1 / P1M48 / 01 / cPG05131 With only one single hybrid tuner you can use analog and DVB-T simultaneously only, if the condition is given that analog comes from an external source like a VCR over Composite or S-Video. (needs packed formats, planar don't work!) There might be a lot of very similar cards out there. I thought that Werner's card was a clone of mine, an [EMAIL PROTECTED] A/D, but mine does not support using both tuners at the same time. It seems that a very similar card does. On this site; http://global.msi.com.tw/index.php?func=prodfaqanswerfaq_no=1599prod_no=623maincat_no=132cat2_no=261cat3_no= it says, [EMAIL PROTECTED] Duo: Same as the A/D, this card also support the most advance PIP-picture in picture, and TWIN-one analog TV channel and one digital TV channel side by side. Once you plug both signals, you don't need to switch between 2 signals. The one you mentioned (between antenna and 8275): - 4231 / 0761 / 433 it doesn't seem to be directly connected to the 8275. Rather to the 7131, but I can't tell that exactly. I am not an expert. It is the mentioned RF switch on current LifeView and Asus stuff. Here's a few other chips - top middle: LV4052 / AR245 / UnG05 / 12C - a bit right, left of the TDA10046A: ATMEL 508 / 24C256N / ??U27 B - right of the TDA10046A: RM18B / R133AL - further down, just upper right to the 7131: ATMEL 516 / 24C02N / SU27 D - to the right, at the right edge: PIC16C505 / -041/SL / 050838A Though a separate firmware eeprom and that PIC is a i2c IR controller also found on the other LifeView cards. There are patches from Eddi for the Trio remote, but not in master yet. - further down: LD1117A / L33ASA, further left (left of the 7131) there is another one Hopefully this information is of any use to you. Thanks for your efforts. Greetings, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO Dual Digital 4 and remote
Craig Cook wrote: Try the instructions for the original dvico dual tuner... http://www.mythtv.org/wiki/index.php/DViCO_FusionHDTV_DVB-T_Dual_Digital_Installation or http://www.mythtv.org/wiki/index.php/DVICO-Ultraview_Install_in_Australia Hopefully v4 is similar... Craig Yeppo, the dev/input stuff is what you want, probably also worth writing some udev rules, or using the by-id links in /dev/input to ensure you don't get ordering problems with the eventX dev numbering if you have a keyboard or other input device attached. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI DVB at Anywhere a.k.a LifeView Hybrid doesn't scan
On Monday 25 June 2007 07:21, hermann pitton wrote: Hello, Am Sonntag, den 24.06.2007, 23:49 +1000 schrieb Peter D.: On Saturday 23 June 2007 09:19, hermann pitton wrote: Hello, Am Freitag, den 22.06.2007, 23:29 +0200 schrieb Werner Braun: [snip] The card in question is a PCI DVB-T TV (analog) FM Tuner card named Vivanco 21056 (the cardbus version is called 21057). The description claims parallel processing of DVB and analog signal with picture in picture resp. split-screen capacity. [snip] With only one single hybrid tuner you can use analog and DVB-T simultaneously only, if the condition is given that analog comes from an external source like a VCR over Composite or S-Video. (needs packed formats, planar don't work!) There might be a lot of very similar cards out there. I've had another look at the manual. You obviously know more about what is going on than I do. I thought that I might be saving people from confusion, but it was just my ignorance showing through. :-( yes, LifeView always has a lot of OEMs. Also the first generation of the tda8275 tuner found on some is not in production anymore and they use the tda8275a now, maybe they change more with this replacement. I thought that Werner's card was a clone of mine, an [EMAIL PROTECTED] A/D, but mine does not support using both tuners at the same time. It seems that a very similar card does. You and Werner have only one hybrid tuner at 0x61 for dvb-t and analog. I really thought it is a clone too. Did you ever try radio? [snip] Yes the FM radio of the MSI [EMAIL PROTECTED] card definitely works under linux. I don't use it much because I have real radios as well. Is there any application that can be programmed to change stations and record programs like Kaffeine does with dvb? -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI DVB at Anywhere a.k.a LifeView Hybrid doesn't scan
On Monday 18 June 2007 08:41, hermann pitton wrote: Hi, Am Sonntag, den 17.06.2007, 23:46 +1000 schrieb Peter D.: On Sunday 17 June 2007 09:46, hermann pitton wrote: Hi Werner, Am Samstag, den 16.06.2007, 23:38 +0200 schrieb Werner Braun: [snip] Don't forget to plug the antenna into the correct socket. ;-) It does antenna input switching on analog for TV and radio. The MSI [EMAIL PROTECTED] A/D manual suggests that the FM tuner is optional. The card has a female TV (analogue + DVB-T) connector, an (optional?) male FM radio connector and a multipurpose connector (with custom adapter that has many sockets). It is possible to connect the cable to the FM radio socket and wonder why it does not display TV. [snip] Generally I don't look at the analogue side of things. Today kmplayer did not work and kdetv displayed a picture, but did not give any sound. Then the computer crashed - repeatedly. A known risk is analog TV in overlay/preview mode when the data are directly written to the memory of the graphics card from PCI to PCI/AGP device. Many chipsets don't play nice with it. Another additional risk are Ati and Nvidia binary driver in that mode. Using the free ati/radeon driver on a 9250 series PCI card - so I should be safe on that point. On the other hand I'm not, so happy about the motherboard. Capture mode like on tvtime or xawtv so called grabdisplay should be save. I'm also quite sure I never had a crash with mplayer, that can also do dma sound with saa7134-alsa or saa7134-oss if you have no audio cable to the soundcard connected. I can see a analog audio onboard connector. You find more stuff about saa7134-alsa helper apps on the v4l wiki. It was tvtime that seemed to be miss behaving, but it is OK now. There are three internal connectors on the MSI [EMAIL PROTECTED] A/D card, none of which are mentioned in the manual. There is an audio out connector, which was empty yesterday, but is now connected to the optical drive audio connector on the motherboard. There is now sound with tvtime. There is also a CD in connector and an unlabeled ten pin connector. Herman, What exactly do you want me to do? Against which kernel? Currently there is a Mandriva kernel (2.6.17.something) with source code and several vanilla kernels on that machine. I have this file, http://linuxtv.org/hg/v4l-dvb/rev/76b92a337aec.bz2 which seems to be the most recent. It makes things work with the Mandriva kernel. The most recent vanilla kernel (2.6.21.5) works without it. Applying it to 2.6.21.5 stops it working. Which old v4l-dvb do you want me to try (link please) against which kernel? If you are not at all fussed, there is an old one here from February. Do you want me to then apply http://linuxtv.org/hg/~hhackmann/v4l-dvb/rev/f182b5f389b3.bz2 to the patched kernel, or a clean one? Thanks, fairly current stuff on the 2.6.17 should be enough. I have not the slightest idea what should break it on 2.6.21.5. Testing with card=112 should did no harm, I wonder that Werner has at least analog with a stock kernel, but also not even that with recent mercurial. My stuff works. Since I have no datasheets and not even the pinning, someone must help where to look for the physical connection. Usually I would say to Werner try to add .i2c_gate = 0x4b, if analog works and else no tuner is responding. Thought first it might have two, but it is the LR306! It is a bit confusing currently. Help is welcome, Hermann -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI DVB at Anywhere a.k.a LifeView Hybrid doesn't scan
On Monday 18 June 2007 08:51, Hartmut Hackmann wrote:
Hi, Werner
Werner Braun schrieb:
[snip]
Summing up the test results, i have the impression that this card is
different from what we have yet.
I am almost sure that the problem lies in the GPIO configuration. Please
try the following:
Please keep forcing the card type to 94
In the configuration structure (saa7134-dvb.c):
static struct tda1004x_config ads_tech_duo_config = {
change the entry
.gpio_config = TDA10046_GP00_I,
to
.gpio_config = TDA10046_GP10,
I expect that this makes DVB-T work but it might break analog TV.
Please try also
.gpio_config = TDA10046_GP10_I,
This should make analog work again but it might carsh the channel decoder
(bad firmware) if this is the case, please report this. It might be
necessary to increase a delay in the channel decoder initialization
procedure.
Good luck
Hartmut
That is interesting. Looking at saa7134-dvb.c in 2.6.21.5 and a
recent v4l-dvb patch, they are different. That could be why patching
2.6.21.5 stops it working for my MSI [EMAIL PROTECTED] A/D.
cat floppy/temp_kernel
static struct tda1004x_config ads_tech_duo_config = {
.demod_address = 0x08,
.invert= 1,
.invert_oclk = 0,
.xtal_freq = TDA10046_XTAL_16M,
.agc_config= TDA10046_AGC_TDA827X_GP00,
.if_freq = TDA10046_FREQ_045,
.request_firmware = NULL,
};
cat floppy/temp_patch
static struct tda1004x_config ads_tech_duo_config = {
.demod_address = 0x08,
.invert= 1,
.invert_oclk = 0,
.xtal_freq = TDA10046_XTAL_16M,
.agc_config= TDA10046_AGC_TDA827X,
.gpio_config = TDA10046_GP00_I,
.if_freq = TDA10046_FREQ_045,
.tuner_address = 0x61,
.request_firmware = philips_tda1004x_request_firmware
};
--
sig goes here...
Peter D.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI DVB at Anywhere a.k.a LifeView Hybrid doesn't scan
On Tuesday 19 June 2007 10:01, Werner Braun wrote: [snip] In DVB-T, I haven't been able to tune in into all stations (e.g. RTL, ZDF), but this might be an antenna issue. It could also be a configuration problem. If, for example, the station changes its guard interval the [EMAIL PROTECTED] A/D is not smart enough to sort it out. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI DVB at Anywhere a.k.a LifeView Hybrid doesn't scan
On Saturday 16 June 2007 04:18, hermann pitton wrote: Hi, Am Freitag, den 15.06.2007, 16:16 +0200 schrieb Werner Braun: [snip] Just looking at the subject line; LR306 suggests an MSI TV at nywhere Somewhere along the way the commercial at symbol was munged into space at space. Is that a feature of the mailing list software? [snip] tda827x_probe_version: could not read from tuner at addr: 0xc2 hm, that was recently introduced by Hartmut to improve it for those cards. http://linuxtv.org/hg/~hhackmann/v4l-dvb/rev/bc9a765d3bb4 Peter, does Hartmut's repo or the recent mercurial master still work for you? After some mucking around (like plugging the cable into the correct socket) yes it works with v4l-dvb-76b92a337aec.tar.bz2 from about four days ago against a Mandriva kernel 2.6.17-14mdvcustom. It also works with the vanilla 2.6.21.5, although something wrong when I applied the v4l-dvb patch to it. shrug Might we have a hardware change now? Think no. http://linuxtv.org/pipermail/linux-dvb/2007-March/016823.html [snip] How would I tell? I don't recognize that error. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI D VB at Anywhere a.k.a LifeView Hybrid doesn' t scan
On Sunday 17 June 2007 09:46, hermann pitton wrote: Hi Werner, Am Samstag, den 16.06.2007, 23:38 +0200 schrieb Werner Braun: [snip] The patch will work, not sure if the same IR trouble/fun is on the cardbus version to be expected, but that can be investigated. [snip] tda827x_probe_version: could not read from tuner at addr: 0xc2 Tuner seems to be dead/not initialized. I only saw that message after deliberately miss setting card=NN. [snip] Peter, how did you finally get your MSI to work? Which distro are you using? Yes, Peter could try the recent without ever using card=112 before. And you could try if it makes a difference without Hartmut's latest changes by downloading a snapshot just before and than try also his latest again. There are more cooks on it recently. Maybe taking the bz2 or gz on top from that one? http://linuxtv.org/hg/~hhackmann/v4l-dvb/rev/f182b5f389b3 Cheers, Hermann My card is a PCI MSI [EMAIL PROTECTED] A/D. (There is also a Kworld VStream XPert DVB-T in another box.) The MSI card is in a box running Mandriva 2007.1 (also known as Spring). It is also known to work with 2007.0. Although I have not made the remote control of either card do what I want. It is necessary to change the kernel and/or use v4l-dvb from linuxtv.org. Then put saa7134 card=94 in /etc/modprobe.preload and modprobe saa7134-dvb in /etc/rc.d/rc.local. My application of choice is /Kaffeine/. Don't forget to plug the antenna into the correct socket. ;-) On the dvb side of things the MSI card works with card=94. It does not work with 55, 112, or without a card value. Generally I don't look at the analogue side of things. Today kmplayer did not work and kdetv displayed a picture, but did not give any sound. Then the computer crashed - repeatedly. Herman, What exactly do you want me to do? Against which kernel? Currently there is a Mandriva kernel (2.6.17.something) with source code and several vanilla kernels on that machine. I have this file, http://linuxtv.org/hg/v4l-dvb/rev/76b92a337aec.bz2 which seems to be the most recent. It makes things work with the Mandriva kernel. The most recent vanilla kernel (2.6.21.5) works without it. Applying it to 2.6.21.5 stops it working. Which old v4l-dvb do you want me to try (link please) against which kernel? If you are not at all fussed, there is an old one here from February. Do you want me to then apply http://linuxtv.org/hg/~hhackmann/v4l-dvb/rev/f182b5f389b3.bz2 to the patched kernel, or a clean one? -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Vivanco 21056/LR306 a.k.a. MSI [EMAIL PROTECTED] a.k.a LifeView Hybrid doesn't scan
On Friday 15 June 2007 06:31, Werner Braun wrote: [snip] thanks for your reply. Here's what DMESG says when using card=112: [snip] Hi Werner, Just looking at the subject line; LR306 suggests an MSI [EMAIL PROTECTED] A/D. Try card=94. The Anywhere A/D appears to be distinct from the Anywhere Plus, Anywhere Master and the plain Anywhere. I don't know where [EMAIL PROTECTED] fits in the lineup. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] divide error with ST STV0297 DVB-C
Hi Oliver. Adding a symbol rate did the trick. Thanks. Now I just have to find the right frequencies/qam/rate. Thanks for your hint. --PMM Oliver Endriss wrote: Peter Maersk-Moller wrote: Hi When trying to tune with my TT Budget T1500,I get a divide error from the kernel. Tried 2.6.21.2 and 2.6.21.5. Is this a well known issue ? Not until now. Thanks for reporting. ;-) More info below. When I try to tune my TT Premium DVB-C (same front end ST STV0297 DVB-C) the same dvide error happens locking up the card. ... dvbtune -c 1 -f 562000 Using DVB card ST STV0297 DVB-C tuning DVB-C to 562000, srate=0 ^^^ Please test whether it works when you use a sane symbol rate. 0 does not make sense. ... Jun 14 20:36:09 dvb01 kernel: EIP is at stv0297_set_sweeprate+0xa/0x5f [stv0297] ... Apparently, specifying symbol rate 0 causes a divide-by-zero error in stv0297_set_sweeprate(). Anyway, the driver should not crash. I'll apply a fix asap. Oliver ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVB-C Questions for Holland
Hi. Has any one been using Budget and Technotrend cards for receiving digital Cable TV from Casema in Holland ? If yes, which frequencies, qam and symbol rates are you using ? Is the qam 64 and the symbol rate 6.875.000? And is this table valid for the Leiden/Leyden area today ? http://www.digitalekabeltelevisie.nl/techniek/tvd.shtml Which CAM are you using ? Kind regards --PMM ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] divide error with ST STV0297 DVB-C
Hi When trying to tune with my TT Budget T1500,I get a divide error from the kernel. Tried 2.6.21.2 and 2.6.21.5. Is this a well known issue ? More info below. When I try to tune my TT Premium DVB-C (same front end ST STV0297 DVB-C) the same dvide error happens locking up the card. Kind regards Peter MM dvbtune -c 1 -f 562000 Using DVB card ST STV0297 DVB-C tuning DVB-C to 562000, srate=0 polling Getting frontend event Message from [EMAIL PROTECTED] at Thu Jun 14 20:36:09 2007 ... dvb01 kernel: divide error: [#1] --- From syslog Jun 14 20:18:07 dvb01 kernel: saa7146: register extension 'budget_ci dvb'. Jun 14 20:18:07 dvb01 kernel: saa7146: found saa7146 @ mem f8866000 (revision 1, irq 21) (0x13c2,0x1012). Jun 14 20:18:07 dvb01 kernel: saa7146 (0): dma buffer size 192512 Jun 14 20:18:07 dvb01 kernel: DVB: registering new adapter (TT-Budget-T-CI PCI). Jun 14 20:18:07 dvb01 kernel: adapter has MAC addr = 00:d0:5c:07:dc:d9 Jun 14 20:18:07 dvb01 kernel: saa7146: register extension 'dvb'. Jun 14 20:18:07 dvb01 kernel: budget-ci: A frontend driver was not found for device 1131/7146 subsystem 13c2/1012 Jun 14 20:18:07 dvb01 kernel: saa7146: found saa7146 @ mem f886a400 (revision 1, irq 22) (0x13c2,0x1010). Jun 14 20:18:07 dvb01 kernel: saa7146 (1): dma buffer size 192512 Jun 14 20:18:07 dvb01 kernel: DVB: registering new adapter (TT-Budget-C-CI PCI). Jun 14 20:18:07 dvb01 kernel: adapter has MAC addr = 00:d0:5c:67:be:ed Jun 14 20:18:07 dvb01 kernel: DVB: registering frontend 1 (ST STV0297 DVB-C)... Jun 14 20:18:07 dvb01 kernel: saa7146: found saa7146 @ mem f8816c00 (revision 1, irq 20) (0x13c2,0x000a). Jun 14 20:18:07 dvb01 kernel: DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-CA rev1.X). Jun 14 20:18:07 dvb01 kernel: adapter has MAC addr = 00:d0:5c:01:d9:cc Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: gpioirq unknown type=0 len=0 Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: info @ card 2: firm f0240009, rtsl b0250018, vid 71010068, app 80002622 Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: firmware @ card 2 supports CI link layer interface Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: DVB-C analog module @ card 2 detected, initializing MSP3415 Jun 14 20:18:07 dvb01 kernel: dvb_ttpci: saa7113 not accessible. Jun 14 20:18:07 dvb01 kernel: saa7146_vv: saa7146 (2): registered device video0 [v4l2] Jun 14 20:18:07 dvb01 kernel: saa7146_vv: saa7146 (2): registered device vbi0 [v4l2] Jun 14 20:18:07 dvb01 kernel: DVB: registering frontend 2 (ST STV0297 DVB-C)... Jun 14 20:18:07 dvb01 kernel: saa7146: found saa7146 @ mem f8c32000 (revision 1, irq 21) (0x13c2,0x000e). Jun 14 20:18:07 dvb01 kernel: DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-S rev2.3). Jun 14 20:18:07 dvb01 kernel: adapter has MAC addr = 00:d0:5c:63:ac:3c Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: gpioirq unknown type=0 len=0 Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: info @ card 3: firm f0240009, rtsl b0250018, vid 71010068, app 80002622 Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: firmware @ card 3 supports CI link layer interface Jun 14 20:18:07 dvb01 kernel: dvb-ttpci: Crystal audio DAC @ card 3 detected Jun 14 20:18:07 dvb01 kernel: saa7146_vv: saa7146 (3): registered device video1 [v4l2] Jun 14 20:18:07 dvb01 kernel: saa7146_vv: saa7146 (3): registered device vbi1 [v4l2] Jun 14 20:18:07 dvb01 kernel: DVB: registering frontend 3 (ST STV0299 DVB-S)... Jun 14 20:18:08 dvb01 sshd[2795]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use. Jun 14 20:36:09 dvb01 kernel: divide error: [#1] Jun 14 20:36:09 dvb01 kernel: SMP Jun 14 20:36:09 dvb01 kernel: Modules linked in: lnbp21 stv0299 stv0297 tda1004x dvb_ttpci saa7146_vv video_buf budget_ci videod ev budget_core v4l2_common dvb_core v4l1_compat saa7146 ttpci_eeprom ir_common i2c_i801 i2c_core Jun 14 20:36:09 dvb01 kernel: CPU:0 Jun 14 20:36:09 dvb01 kernel: EIP:0060:[f887d37f]Not tainted VLI Jun 14 20:36:09 dvb01 kernel: EFLAGS: 00010206 (2.6.21.5 #1) Jun 14 20:36:09 dvb01 kernel: EIP is at stv0297_set_sweeprate+0xa/0x5f [stv0297] Jun 14 20:36:09 dvb01 kernel: eax: 0fa0 ebx: 03e8 ecx: edx: Jun 14 20:36:09 dvb01 kernel: esi: f7b15400 edi: 0009 ebp: 0009 esp: f7523ee8 Jun 14 20:36:09 dvb01 kernel: ds: 007b es: 007b fs: 00d8 gs: ss: 0068 Jun 14 20:36:09 dvb01 kernel: Process kdvb-fe-1 (pid: 2879, ti=f7522000 task=c3247a30 task.ti=f7522000) Jun 14 20:36:09 dvb01 kernel: Stack: 03e8 f7b15400 f887db81 feb6 03e8 0064 Jun 14 20:36:09 dvb01 kernel:f752f004 0286 f752f000 f7b15408 f8a94624 c03f3f1d Jun 14 20:36:09 dvb01 kernel: 0001 c3247a30 c011857e 00100100 00200200 00089350 Jun 14 20:36:09 dvb01 kernel: Call Trace: Jun 14 20:36:09 dvb01 kernel: [f887db81] stv0297_set_frontend+0x42a/0x6c0 [stv0297] Jun 14 20:36:09
Re: [linux-dvb] cx88-dvb modprobe failure
On Thursday 07 June 2007 11:15, Sid Boyce wrote: Peter D. wrote: On Wednesday 30 May 2007 16:05, Sid Boyce wrote: [snip] CORE cx88[0]: subsystem: 17de:08a4, board: KWorld/VStream XPert DVB-T [snip] Any ideas? Thanks and Regards Sid. I have a similar card, except it is 17de:08a6. Is there any chance of static damage? Is the card seated properly? BTW how did you configure the remote control? Checked it was seated properly by pressing down on it, seemed OK. Took it to my daughter's and installed it in her openSUSE 10.0 PC, worked straight away, 17de:08a6. Installed her card in my PC, reported as 17de:08a6 and it works, kernel 2.6.22-rc4. Must have been some problem with seating as you said. Thanks Regards Sid. It was just a reminder to check the obvious. At one stage I thought that I must have zapped my Kworld card. In retrospect it might be that it won't work in my AM2 box (an ASUS M2N-E with nForce 570 ultra and a 65 Watt 3600+ 64X2), only in my Sempron box. Sooner or later I will shuffle some hardware and have another look. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] au tuning files
Hi, I'm taking some things on trust here, so feel free to tell me I am wrong. My main source is http://www.dba.org.au/index.asp?sectionID=120 It says, among other things; these parameters may be changed from time to time without warning, receivers need to comply with Standards Australia standards AS 4933 and AS 4599, as well as DVB standards, that say a receiver needs to identify and receive all COFDM modes, including hierarchical (see below), and the receiver should check the Transmission Parameter Signaling (TPS) some broadcasters use centre frequency offsets I'm not sure how clever that means tuners sold in Australia should be or, more importantly, actually are. In this post http://www.linuxtv.org/pipermail/linux-dvb/2007-May/018262.html John offered a tuning file for Australia that was mostly full of AUTOs with what looks like an entry for every frequency used in Australia. It works for me with a Kworld/VStream Xpert card in Melbourne. I don't know how much the Australian standards vary from international standards, but I believe that one or two channels have been moved by a Mega Hertz and an extra channel (9A) added. Channel 12 might be non standard too, I don't know. Looking through the au-* tuning files and the www.dba.org.au site there are some things that are still a mystery to me. There seem to be many more transmitters scattered around the country than are mentioned in the au-* tuning files. The www.dba.org.au site only lists a single FEC for each group of channels, while the tuning files have a fec_hi and a fec_lo. In many files that is given as a fraction and a NONE, sometimes as two fractions, usually the same fraction - sometimes as different ones. Is the fec_low value used? Only valid sometimes? Should it be AUTO, NONE, the same as fec_hi, or is it an independent variable? The big problem is that *most* of the channel 7 transmitters have changed their guard interval. The changes that I am offering here seem to be improvements, but I can only test Melbourne stuff. au-Perth and au-Melbourne have recently changed to have the new ch7 GI. The files attached are; A generic Australian file, au-auto, from John. au-Adelaide,new ch7 GI au-Cairns, new ch7 GI au-Canberra-Black-Mt, new Prime FEC and GI au-Darwin, new Southern Cross FEC and GI, new ch9 FEC and GI au-Melbourne-Upway, new ch7 GI au-MidNorthCoast, lots of changes au-SpencerGulf, new SBS FEC au-Sydney_Kings_Cross, new ch7 GI au-Townsville, new ch7 GI There are other au-*tuning files that I am not offering changes for. -- sig goes here... Peter D. # Australia all dvb frequencies - maybe # If this does not work try the city specific files # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 4850 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 5950 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 6650 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 8850 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 9750 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 10450 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 14050 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 17750 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 18450 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 19150 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 19850 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 20550 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 21150 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 21250 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 21850 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 21950 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 22650 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 52350 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 52950 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 53650 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 54350 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 55050 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 55750 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 56450 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 57150 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 57850 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 58550 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 59250 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 59950 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 60650 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 61350 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 62050 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 62750 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 63450 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 64150 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 64850 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 65550 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 66250 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 66950 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 67650 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 68350 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 69050 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 69750 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 70450 7MHz AUTO AUTO AUTO AUTO AUTO AUTO T 71150
Re: [linux-dvb] Remote control input event problem with recent kernels
On Saturday 02 June 2007 07:36, Tony Houghton wrote: In [EMAIL PROTECTED], Tony Houghton wrote: I've got 2 DVB-T PCI cards, a Hauppauge Nova-T wwhich uses the budget_ci (even though it doesn't have a CI) module and a K-World cx88-based card. [Snip] I've got a Kworld cx88 based card. With the driver in recent kernels (2.6.20 onwards?) I no longer have to patch it, but the remote doesn't work so well. I never did work out how to configure the remote. While holding a key down I get a series of alternate press and release events with no repeat events. Sometimes I have to hold down a key for a few seconds before it starts sending events. In a console showkey reveals a single keypress immediately followed by one or several keyrelease events (depending on the key). I'm disappointed there's been no response to this. Isn't anyone else having the same problem? I never got it to work in the first place. :-( -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fwd: Re: cx88-dvb modprobe failure
I meant to send this to the list... -- Forwarded Message -- Subject: Re: [linux-dvb] cx88-dvb modprobe failure Date: Saturday 02 June 2007 17:20 From: Peter D. [EMAIL PROTECTED] To: [EMAIL PROTECTED] On Wednesday 30 May 2007 16:05, Sid Boyce wrote: [snip] CORE cx88[0]: subsystem: 17de:08a4, board: KWorld/VStream XPert DVB-T [snip] Any ideas? Thanks and Regards Sid. I have a similar card, except it is 17de:08a6. Is there any chance of static damage? Is the card seated properly? BTW how did you configure the remote control? -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVB-T HD in Sweden
Hi all! We will soon have HDTV in the Teracom DVB-T network here in Sweden. In Stockholm the transmissions will officially start on saturday, however they are already up and running. The new mux is named Teracom network 6 and the Nacka transmitter in Stockholm are using 730 MHz (channel 53). The SVT HD channel is not scrambled. It's 720p (H.264) and the bandwidth is about 13 Mbps. I have some problems to decode the video. mplayer complains about FPS not specified in the header or invalid, use the -fps option.. Can someone explain why mplayer don't find that info in the stream? If I add -fps 25 mplayer seems to work, but I don't know what is the correct FPS value. All hints are welcome. I can upload a TS sample if anybody is interested. -- Peter Fassberg ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-T HD in Sweden
mplayer complains about FPS not specified in the header or invalid, use the -fps option.. Can someone explain why mplayer don't find that info in the stream? because it's missing :( ARG!! the framerate is optional in the main header of H264 (sps). To bad! What is sps? In these cases you can use -demuxer lavf, that involves a more complete analysis of the video stream by means of libavcodec and libavformat (part of ffmpeg) If I add -demuxer lavf mplayer ignores the -tsprog 610! Can you play the HD channel using mplayer? -- Peter Fässberg E-mail: [EMAIL PROTECTED] Leissner Data AB Box 912 461 29 TROLLHÄTTAN Telefon: 0520 - 300 00 Telefax: 0520 - 300 89 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-T HD in Sweden
All hints are welcome. It would be interesting to see how far you get with using VDR with these transmissions. Unfortunately I havn't VDR installed at this moment. I tried to open the file using VLC 0.8.5 to no avail. I'll try a newer version as well. -- Peter Fassberg ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S- and DVB-S2-streams with TT3200
I just removed those and it worked somehow, still having bad problems about locking and every time you acan channels it find diffrent ones. Is it possible to get this TT3200 card work like normal technotrend budget DVB-S1 card? on windows atleast all technotrends have same drivers. That's because in Linux, people have nothing better to do than bitch, act I'm-holier-than-thou, and don't spend time designing a good driver/architecture model first before coding spaghetti non-working code. _ Change is good. See what’s different about Windows Live Hotmail. http://www.windowslive-hotmail.com/learnmore/default.html?locale=en-usocid=RMT_TAGLM_HMWL_reten_changegood_0507 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] remote for Kworld cx88 how?
Hi, I have a Kworld/VStream Xpert DVB-T pci card with an IR remote. The hardware seems to be working. Kaffeine 0.8.3 displays TV fine. Using showkey in a virtual terminal (but not under X) all of the buttons are doing something. For example the up arrow or CH+ key gives... keycode 0 press keycode 3 release keycode 18 release keycode 0 release keycode 3 release keycode 18 release But does not change the channel. Is it necessary to configure Kaffeine, Lirc, X or something else entirely? I found http://www.linuxtv.org/v4lwiki/index.php/Remote_controllers which seems to suggest changing saa7134-cards.c. That does not seem appropriate for a cx88 card, not that I can see what sort of definition to create anyway. irrecord -H dev/input -d /dev/input/event2 /tmp/my_remote does not do anything for me it just returns irrecord: gap not found, can't continue I've tried a couple of kernels including 2.6.20.11. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Incorrect tuning parameters for Perth Western Australia
On Friday 18 May 2007 14:20, Peter D. wrote: On Monday 14 May 2007 19:50, Jim Barber wrote: [snip] It's a request to fix an incorrect setting in the configuration file supplied for the scan utility of the dvb-utils software, the the au-Perth region. [snip] I'm not brave enough to submit changes for other cities even bases on data from an official web site. Maybe we should? There are other Australian cities. [snip] Finally I stumbled across the correct settings on the Digital Broadcasting Australia's website at the following link: http://www.dba.org.au/index.asp?sectionID=120 The problem is that everywhere, the guard interval for channel 7 has been reported as being 1/8. This is incorrect. It is actually 1/16. It was enough to stop me from being able to tune to it, even when doing auto scans. I was just about to return the DVB-T capture card as faulty because of this setting reported incorrectly everywhere. [snip] Cristoph, Do you want to risk taking data from what seems to be an official web site without being able to test it? The web site claims to have been updated this year. Jim has reported a change for Perth and I have recently reported a change for Melbourne, so we are probably on the right track. ;-) -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Update of initial tuning file se-Pajala
Hi Antti! Looks like there has been done some channel changes or teracom www-page is not updated recently. Attached tuning file is as channels are just now (have been at least one month or more...). I am not sure whether or not 738 MHz is reserved. Currently there is no transmission in that channel so I marked it as reserved... http://www.teracom.se/?page=5196 You're using an old URL. New URL is: http://www.teracom.se/?page=5883 The latest changes was done May 14. It doesn't seems that 738 MHz is reserved. -- Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
RE: [linux-dvb] DVB-S streams with TT3200
Hi Laasa, Where do I get the patches from. It would help a learner like me if I can simply download the source and install, as I'm not sure what I am doing with patches. I have Manu's snapshot and cant find any reference to TT3200 in its files. In advance, thanks for the reply. Regards Peter Cockle -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of laasa Sent: Monday, 7 May 2007 7:08 a.m. To: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] DVB-S streams with TT3200 Second try: Here again with patchfile and shifted from budget to budget-ci (thanks to marco for some hints). Sources - Manus snapshot at http://jusst.de/manu/stb0899-v4l-dvb.tar.bz - the szap-sources from http://dev.kewl.org/tmp/hvr4000/szap2.tgz Envoirenment: - TT3200 (SAA7146AH, STB0899 C2L, STB6100, LNBP21 PD, 27000 MHz, board B2S3000 Rev 1.0 TT2006.1) - Tested with Linux-Kernel 2.6.16-45 (from kernel.org) and 2.6.17-chw-8 (MythTV R5D1): must be = 2.6.17 Procedure for compiling and loading of drivers: - unpack kernel-sources (to /usr/src/linux) if necessary - unpack v4l-dvb-sources (to /usr/src/v4l-dvb) - unpack szap2-sources (to /usr/src/szap) - change to /usr/src/szap - make - make install = check if szap2 now is installed - change to /usr/src/v4l-dvb - patch the tree - v4l-scripts-make_myconfig.pl - rename .version in /usr/src/v4l-dvb/v4l - make - unload all dvb-driver (e.g. make rmmod) - make install - modprobe budget-ci - szap -r ... - xine ... Notes: - the TT3200 is build into modules budget-ci - to tune a channel you must (most times) tune to different channels (for me ZDF and Kika are good candidates to get a LOCK) Problems: - everytime with the locking of PLL (sometimes after some trys on different DVB-S-channels, on some DVB-S-channels and all DVB-S2-channels never) - It seems to be a problem with higher frequences (higest successfuly tuned frequency is 11836 MHz, e.g. ARD = ProSieben ... not work) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Australia and the DViCO Dual Digital 4
I currently have access to one of these cards in Melbourne for further testing, and can provide another file mirror if necessary. Congrats on the work Roger. [EMAIL PROTECTED] wrote: Finally some promising news for Australian Dual Digital 4 users. Many, many hours later it turns out to be fairly simple and I don't think we need to touch anything other than the tuner but I'm sticking with my hacked code which spews out register values galore until it's confirmed. It would have been nice to get my name in the source code again but I don't think it's warranted. Okay, I need some volunteers elsewhere in Australia to try something and I need a place to upload a 25 byte firmware file. Any takers? The 25 byte firmware file replaces the 7MHz file from the v3 firmware but only for AU users. There are still some tuning issues. The frequency offset in the xc3028 file needs to be changed from 275 to 225 which will break it for the rest of the world using 7MHz bandwidth so again only AU users please. Also this still doesn't quite map into the actual numbers we need to send to the tuner so you'll find anything below 190MHz may require you to increase the frequency by 100kHz or so to lock properly. Ideally I need 184.5MHz (channel 7) to map to 0x2D98 but instead it's 0x2D90. 212.5MHz (channel 10) goes to 0x3490 which is correct. UHF frequencies may be right out and may even require different firmware but I now know what to look for so we can probably fix it. Hobart digital TV is transmitted on channels 7,8,9A,10 and 11 so I'm somewhat limited in my sampling ability. After having my brain in gigabytes of log files, device driver code and the user manual for the CE6231 (similar to the ZL10353/CE6353 and VERY useful) for the past three days I think I'll take the rest of the evening off. :) Cheers, Roger. Send instant messages to your online friends http://au.messenger.yahoo.com ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
RE: [linux-dvb] Re: STB0899 and TT 3200-S2
Thanks Jan I downloaded Manu's tree. At first it would not install. Apparently it expected a kernel version 0f 2.6.20. I discovered it was getting that from ./v4l/.version. By changing its name to .versionold it attempted to compile but quit with errors about not finding xmit_lock. From my attempts to build from an earlier version I recalled that dvb.net.c needs to have VERSION(2,6,18) changed to VERSION(2,6,17). After changing that (my kernel is 2.6.17-5) I successfully ran M make and make install. But the TT S2 does not appear to be recognised, and the are no dvb devises created. So I'm still stuck. I hope the above install stuff helps you. Regards Peter Cockle -Original Message- From: Jan Tisje [mailto:[EMAIL PROTECTED] Sent: Sunday, 8 April 2007 9:19 p.m. To: Peter Cockle Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Re: STB0899 and TT 3200-S2 Hi, I am not sure, but I believe manu was talking about this file. (he posted the link on 1.4.) http://jusst.de/manu/stb0899-v4l-dvb.tar.bz2 but it did not work for me. perhaps I need a newbie howto for applying a patch to the kernel sources?! :( did you succeed yet? Jan Peter Cockle schrieb: -Original Message- From: [EMAIL PROTECTED] [mailto:linux-dvb- [EMAIL PROTECTED] On Behalf Of Manu Abraham Sent: Saturday, 24 February 2007 8:56 p.m. To: Mike Kazmier Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Re: STB0899 and TT 3200-S2 On 2/23/07, Mike Kazmier [EMAIL PROTECTED] wrote: I do have an update: I was able to patch the v4l-dvb mercurial tip with patches from http://kromtek.com/dvb/patches/ and build the stb0899 modules. I was able to load the stb0899 kernel module successfully along with the budget kernel module but I can't see and /dev/dvb devices. I saw the post from manu about the new szap, but I can't even get the card up. Manu - have you ever used the TT3200-S2 successfully? Has anyone? Yep, will update the tree soon. manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, I'm new at all this though I've been readying the posts for some months. Can anyone tell me where to find the tree Manu was to update? Then maybe I to can get my TT S2-3200 working. Thanks Peter Cockle ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
RE: [linux-dvb] Re: STB0899 and TT 3200-S2
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manu Abraham Sent: Saturday, 24 February 2007 8:56 p.m. To: Mike Kazmier Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Re: STB0899 and TT 3200-S2 On 2/23/07, Mike Kazmier [EMAIL PROTECTED] wrote: I do have an update: I was able to patch the v4l-dvb mercurial tip with patches from http://kromtek.com/dvb/patches/ and build the stb0899 modules. I was able to load the stb0899 kernel module successfully along with the budget kernel module but I can't see and /dev/dvb devices. I saw the post from manu about the new szap, but I can't even get the card up. Manu - have you ever used the TT3200-S2 successfully? Has anyone? Yep, will update the tree soon. manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, I'm new at all this though I've been readying the posts for some months. Can anyone tell me where to find the tree Manu was to update? Then maybe I to can get my TT S2-3200 working. Thanks Peter Cockle ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] freecom
Hi, I am trying to get the freecom-dvb-t device working on fc6. I copied the firmware (dvb-usb-wt220u-fc03.fw) in /lib/firmware. I obtained the driver from linuxtv.org (v4l-dvb), compiled and installed it without any problem. Now as I understand from the wiki I should have a non-empty /dev/dvb/adapter0/, but this is not the case. I do not have a /dev/dvb at all. When I plug in the device it is somehow being recognized; this is the output of tail -f /var/log/messages: Mar 18 21:23:41 cello syslogd 1.4.1: restart. Mar 18 21:37:16 cello kernel: usb 5-5: new high speed USB device using ehci_hcd and address 7 Mar 18 21:37:17 cello kernel: usb 5-5: configuration #1 chosen from 1 choice Does anybody have a clue? Any help would be appreciated. Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] freecom
Hi, I am trying to get the freecom-dvb-t device working on fc6. I copied the firmware (dvb-usb-wt220u-fc03.fw) in /lib/firmware. I obtained the driver from linuxtv.org (v4l-dvb), compiled and installed it without any problem. Now as I understand from the wiki I should have a non-empty /dev/dvb/adapter0/, but this is not the case. I do not have a /dev/dvb at all. When I plug in the device it is somehow being recognized; this is the output of tail -f /var/log/messages: Mar 18 21:23:41 cello syslogd 1.4.1: restart. Mar 18 21:37:16 cello kernel: usb 5-5: new high speed USB device using ehci_hcd and address 7 Mar 18 21:37:17 cello kernel: usb 5-5: configuration #1 chosen from 1 choice Does anybody have a clue? Any help would be appreciated. Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] FE_HAS_LOCK but no signal
Tom Jacobs schrieb: i am having problems getting data from my STB i am using Mythdora as my distro so, i believe this is basically Fedora Core 5 with MythTV-0.20 included (and various other required packages). i have a Hauppauge DEC2000 stb which i am trying to use within mythtv. the correct firmware is in /lib/firmware and from dmesg i can see the adapter and frontend are both registered. i can successfully ./scan for available channels and have produced my channels.conf file. when i ./tzap i get the following: [EMAIL PROTECTED] ~]# tzap -r BBC TWO using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 64180 Hz video pid 0x0262, audio pid 0x0263 status 00 | signal | snr | ber | unc 009c645e | status 1f | signal | snr | ber | unc 009c645e | FE_HAS_LOCK status 1f | signal | snr | ber | unc 009c645e | FE_HAS_LOCK status 1f | signal | snr | ber | unc 009c645e | FE_HAS_LOCK status 1f | signal | snr | ber | unc 009c645e | FE_HAS_LOCK if i pick different channels the frequency an pids change but i always get signal and a lock. The driver doesn't report values for signal strength/noise ratio/etc. Only whether the tuner has locked into a channel or not. It's a bit misleading that tzap always prints zero here for the other stuff even though the kernel reports that the driver doesn't support these infos. if i try and capture stream using the following: cat /dev/dvb/adapter0/dvr0 myvideo.mpg i get a file of zero bytes. if i try and use mplayer or xine they both fail too. since this is a stb also i can play a scart cable into it and i do see that the channels are being changed when i tzap but i just dont seem to be getting any data back from the stb. does anyone have any ideas? hm not really. just to be sure, tzap has to be running(e.g. in another terminal) while you are trying to capture data from /dev/dvb/adapter0/dvr0. (btw. iirc tzap can also directly dump the data into a file by itself) xine never really worked with this driver for me(for unknown reasons). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] IR device changes after reboot
Paul Wilson wrote: Is there any way to lock down or predict what device my CX-88 IR input class is going to use. My device event# seems to change after every reboot which means I need to manual re-configure my lircd device settings udev: http://www.reactivated.net/writing_udev_rules.html ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Bad TS from dvb-t recording?
When playing with mplayer I got video and audio out of sync. How do I fix that? maybe during the first few seconds, but after little time it will resync I have sometimes the same problem, and that can be solved by starting with some additional chaching: mplayer -cache 8000 -- Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] revised initial tuning data for au-Melbourne
Hi, I'm not certain exactly what should be in dvb-apps-2e83ebcb51de/util/scan/dvb-t/au-Melbourne but things work better if channel 7's guard interval is changed. With the tarball I downloaded a few days ago scan au-Melbourne temp does not put anything into temp about channel 7, after changing the guard interval output for channel 7 is also put into temp. The exact same temp file is created if the last six fields of each line in au-Melbourne is changed to AUTO. Strangely, a lot of tuning failed messages went to standard error with all of the input files; original, changed GI, and six fields of AUTO. My tuner is an MSI [EMAIL PROTECTED] A/D PCI card -lspci -s 05:07 05:07.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) -lspci -s 05:07 -n 05:07.0 0480: 1131:7133 (rev d1) It is a hybrid LifeView LR306 clone. -- sig goes here... Peter D. # Australia / Melbourne (Mt Dandenong transmitters) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # ABC T 22650 7MHz 3/4 NONE QAM64 8k 1/16 NONE # Seven T 17750 7MHz 2/3 NONE QAM64 8k 1/16 NONE # Nine T 191625000 7MHz 3/4 NONE QAM64 8k 1/16 NONE # Ten T 21950 7MHz 3/4 NONE QAM64 8k 1/16 NONE # SBS T 536625000 7MHz 2/3 NONE QAM64 8k 1/8 NONE # Australia / Melbourne (Mt Dandenong transmitters) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # ABC T 22650 7MHz AUTO AUTO AUTO AUTO AUTO AUTO # Seven T 17750 7MHz AUTO AUTO AUTO AUTO AUTO AUTO # Nine T 191625000 7MHz AUTO AUTO AUTO AUTO AUTO AUTO # Ten T 21950 7MHz AUTO AUTO AUTO AUTO AUTO AUTO # SBS T 536625000 7MHz AUTO AUTO AUTO AUTO AUTO AUTO ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Bad TS from dvb-t recording?
Hi! I'm also using dvbstream with great success. dvbstream -f 522000 -o -tm 8 8192 /tmp/test.ts When using DVB-T the frequency should be given in Hz, 52200. -- Peter Fassberg ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Bad TS from dvb-t recording?
Ok, I've installed dvbstream but the frequency seems wrong. Here is one row from channels.conf generated with dvbscan SVT24:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_ INTERVAL_1_8:HIERARCHY_NONE:1249:1248:5180 So, I assume 52200 is the frequency? But when I run: Correct. Mux 1 is on 522 MHz in Motala. dvbstream -f 52200 -o -tm 8 8192 recordings/test.ts I got an empty file and this: dvbstream v0.5 - (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://www.linuxstb.org/ Using DVB card Zarlink MT352 DVB-T tuning DVB-T (in United Kingdom) to -1986010112 Hz polling Getting frontend event FE_STATUS: polling Getting frontend event FE_STATUS: FE_HAS_SIGNAL The frequency seems wrong? Yes, it seems... Try using kHz anyway (522000). I'm using another version of dvbstream: [EMAIL PROTECTED]:~$ dvbstream -f 73000 1018 1019 dvbstream v0.6 - (C) Dave Chapman 2001-2004 Released under the GPL. Latest version available from http://www.linuxstb.org/ Tuning to 73000 Hz Using DVB card DST DVB-T, freq=73000 tuning DVB-T (in United Kingdom) to 73000 Hz, Bandwidth: 8 Getting frontend status Event: Frequency: 73000 Signal strength: 25088 SNR: 20480 FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC // Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Bad TS from dvb-t recording?
But how do I record a specific program in a mux? If I point out the video and sound pids for a program with dvbstream -f 522000 -o -tm 8 1249 1248 recordings/test.ts The stream does not play in VLC. Exact. That is not a true TS as some mandatory PID's is missing. PAT/PMT/SDT/NIT/SID ... I'm sure there is someone who can explain exactly what PIDs you need to get i compliant TS. You need to include some more PIDs, or use another player. I use mplayer which is more forgiving. http://www.mplayerhq.hu/ -- Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Bad TS from dvb-t recording?
dvbstream -f 522000 -o -tm 8 0 1248 1249 5180 recordings/test.ts The PMT for thje specific channel is probably 1240: dvbstream -f 522000 -o -tm 8 0 1240 1248 1249 recordings/test.ts ... and -tm 8 is probably not needed, most of the params is automatic. -- Peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] cinergy 1200 DVB-C install help neeeded
hi there arround (already wrote some days ago, but think, that my mail got lost in space) okthe things I have done: I bought a DVB-C card (as mentioned in the topic) because it was in the compatibility-listwell, ok, now we know, that there is another tuner chip (tda100023) and that ne has to use a patch to get that running. what I have done is: tv-backend:/usr/local/dvb_new#hg clone http://linuxtv.org/hg/v4l-dvb everything I tried with doing a bzcat tda10023.diff.bz2 |patch -p1 failed could please any of you proide a dummy's cook-book for me how to get that running ? thanks in advance! kind regards peter -- Peter Loeffler ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] terratec cinergy 1200 dvb-c
hi guys I am absolutely sure, that these topic has been up here some weeks ago, but I cant gt that runnung (and I am sure the it is me makeing the errors) so, it seems, that I have above mentioned dvb-c card with the NEW CHIPSET (tda10023). lspci says: 05:08.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: TERRATEC Electronic GmbH Unknown device 1176 Flags: bus master, medium devsel, latency 32, IRQ 58 Memory at d300 (32-bit, non-prefetchable) [size=512] what I have done is the following: tv-backend:/usr/local/dvb_new#hg clone http://linuxtv.org/hg/v4l-dvb that created a directory named v4l-dvb within this created directory i did put the tda10023.diff.bz2 file and tried to patch with bzcat tda10023.diff.bz2 |patch -p1 ...which did not work. so, can please anyone tell me, what I am doing wrong ? regards peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital 4
Michael Krufky wrote: Julian, So far, all users that have trouble with this device are located in au-Melbourne. Users located anywhere else in the world are having no troubles at all. I don't know what is causing the trouble, but I am under the impression that it is caused by problems in the zl10353 driver. It would be nice to hear if there are _any_ linux users with a zl10353-based device working in au-Melbourne. There isn't much I can do from here... If there are any developers located in the area, please feel free to try to debug the problem. Sorry, Michael Krufky I know someone in Melb with this card, if they can't get it working I'll grab it and do some debugging, won't be for a couple of weeks though most likely. Cheers, Peter Fern ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital 4
On Saturday 17 February 2007 05:27, Michael Krufky wrote: Julian wrote: Hi, Sorry for creating a new thread - ive just joined the list and been following the archives for a while. I purchased this card today, d/l'd the master repository and applied the patch, card seems to be recognized properly. Using version 3 of the firmware. Yep it cant seem to tune. (au-Melbourne) Thanks alot Mike for working on this card...I guess we need someone with windows? Jules (sunru) Julian, So far, all users that have trouble with this device are located in au-Melbourne. Users located anywhere else in the world are having no troubles at all. I don't know what is causing the trouble, but I am under the impression that it is caused by problems in the zl10353 driver. It would be nice to hear if there are _any_ linux users with a zl10353-based device working in au-Melbourne. There isn't much I can do from here... If there are any developers located in the area, please feel free to try to debug the problem. Sorry, There are three possibilities that spring to mind. One, DViCO produced a small batch of defective hardware that just happened to land in Melbourne. (Does it work under Windows?) Two, there is something very odd about Melbourne transmissions. The Australian government has a long history of improving international television standards. For example, most countries did not have channels 0, 5A and 13. Channel numbers below 7 have been discouraged for a many years now, but they recently moved one of the standard channels slightly to make room for and extra one - 9A, I think. But if the government was the cause of the problem then it should be Nation wide rather than Melbourne only. Three, the initial configuration file is sufficiently wrong that the DViCO can't cope with it. I have recently seen my Kworld card work well, while my MSI card refused channel 7 until some of the settings were adjusted. Unfortunately I don't know where to find authoritative information about what is standard here, or what is actually used. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital 4
On Saturday 17 February 2007 12:53, Michael Krufky wrote: [snip] Peter D. wrote: [snip] Three, the initial configuration file is sufficiently wrong that the DViCO can't cope with it. I have recently seen my Kworld card work well, while my MSI card refused channel 7 until some of the settings were adjusted. Maybe, but I doubt it. I have tried adding / subtracting various offsets, to no avail. [snip] I don't know how relevant it is but digital channel 7 (on physical channel 6 or 8, I forget which) is the first digital channel (not) found. Digital channel 2 is broadcast on physical channel 12. If it is choking on the first channel encountered and it is known that some cards have problems with that channel they might be related facts. I think that the important thing for the MSI card was changing the guard interval. I'm using Kaffeine 0.8.3 with these numbers for channel 7; Frequency: 177500 Transport stream ID: 1283 Service ID: 1328 Video PID: 769 Teletext PID: 772 Transmission: 8k FEC low: auto FEC high: 2/3 Bandwidth: 7MHz Inversion: auto Modulation: QAM64 Hierarchy: auto Guard Interval: auto I am, of course, in Melbourne. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital 4
Michael Krufky wrote: snip DViCO has been very helpful in the development of the bluebird driver, but there is nothing that we can ask DViCO to help us with in this case. The problem is in relation to the zl10353 demodulator driver, and they are not at liberty to share any information of that ic. Chris reverse-engineered the zl10353 driver. If somebody can get a spec and try to figure out what the Linux driver is lacking, that is the only way that we can resolve this issue. The device-specific code of the FusionHDTV Dual Digital 4 driver is completely correct -- this problem is specifically localized to AU, perhaps even just Melbourne (although I have doubts about that). We need somebody to analyze the zl10353 behavior and take it from there. I am quite sure that any other device with a zl10353 will produce the same problematic behavior when used in this area. snip I have a FusionHDTV Dual Digital 2, with a Zarlink ZL10353 frontend that performs without problem (aside from an offset adjustment for some channels) in Melbourne AU. So, doesn't seem like we're on the right track. Can I provide you any data that might be helpful? As I posted earlier, I will have access to a v4 card shortly, so might be able to provide some more info then. Regards, Peter Fern ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] Should a DVB frontend report the board name?
On Saturday 10 February 2007 11:07, Hartmut Hackmann wrote: [snip] I understand the give the component name in it's own relevant place and not in the frontend code but the point is: there is no such place! And we can't easily create one because this would mean a API change - IMHO this is not an option. And the information is useless if it isn't reported to the user space. [snip] Is there an official wish-list for future versions of the API? If so then put it on the list and if/when a change is forced, for this or any other reason, it should be added. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [RFC] Should a DVB frontend report the board name?
On Wednesday 07 February 2007 09:15, Manu Abraham wrote: On 2/7/07, Hartmut Hackmann [EMAIL PROTECTED] wrote: Manu Abraham schrieb: On 2/6/07, Christophe Thommeret [EMAIL PROTECTED] wrote: Le mardi 06 février 2007 01:34, Markus Rechberger a écrit: The name of a frontend should be that of the frontend itself and not the board, if it reports the board name then it is wrong, since the board is not the frontend. not that this is very important but I've seen that some people were confused because of displaying the name of the demodulator, they stated out that they own product xy and not a ZL10353, MT352, etc. Indeed, i think that for a user TerraTec/qanu USB2.0 Highspeed DVB-T Receiver makes more sense than ST STV0299 DVB-S but in the latter case, the board name Philips Semiconductors SAA7146 (rev 01) is also somewhat mysterious when the user would expect WinTV Nova CI ;) The issue is that the board name shouldn't be the name of the frontend. I did have the issue taht which you mentioned, but that i did have a fix to it by using the adapter device that i mentioned sometime back in another thread on a mantis bridge. With this it gives the bridge name, Generic name and the frontend name, all in it's own relevant place and not in the frontend. it will be just messing up the frontend to a state where it will be hopeless. for example: bridge name = Mantis PCI rev 1.0 Generic name = VP-1034 frontend name = MB86A16 DVB-S/DSS DC receiver It additionally fixes some other issues as well, such as handling bridge reset 's etc. Will post the changes after i have cleaned it up, most probably will push it along with the multiproto/stb0899 tree. Manu Hm, we technical guys tend to associate frontend with the channel decoder / tuner combination but the average user can can easily assume that the frontend is the entire card. He has no idea what the functions of the chips are. frontend = demod name (that's what we have currently), Tuner is unimportant in this case as it doesn't have much of ops. for the average person, frontend = RF module, inclusive of the demod the problem comes when you have 2 different frontends on one bridge. The user get's even more confused. Tune to board frontend 0 /1 ? which is frontend 0 which is frontend 1 ? There needs to be clear distinction when multiple devices exists. So in your case you are always tuning to your board name, irrespective of the number of frontends. IMHO, in the case where you had one frontend (with demod as name) is not as confusing compared to this scenario. Assuming that a board has multiple demods. I feel qualified to comment for the ignorant user. ;-) My guess is that they would expect something like; MSI [EMAIL PROTECTED] A/D, using analogue tuner or MSI [EMAIL PROTECTED] A/D, using digital tuner. I would also guess that the the people reading this list would expect much more detailed information, such as, SAA7134 etc. But ack, we should be as precise as possible. So the next question is: If we have the entries you propose, how do these get reported to user space? Currently, the API only reports the frontend type. In multiproto, there is DVBFE_GET_INFO, working with that as a base. It is extendable to the adapter object. Currrently playing around with a bit with some devices on the same in that aspect manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MSI TV @nywhere a/d support
On Friday 12 January 2007 16:47, Greg 'groggy' Lehey wrote: Wow, your email is in red. It must be important. Either that or kmail does not recognize your gpg signature. ;-) On Friday, 12 January 2007 at 0:35:53 +0100, hermann pitton wrote: Am Donnerstag, den 11.01.2007, 22:14 +1030 schrieb Trevor Glen: [snip] Any other thoughts out there people? That might depend on if your au-Adelaide (?) initial scan file is already tda10046 safe. It needs correct values. Other frontends are more tolerant and this can break it for you. I'm not sure I understand this. A couple of questions: - By the original scan file, do you mean the channels.conf file described at http://www.linuxtv.org/wiki/index.php/Zap ? If so, what might be wrong with it, in particular the au-Adelaide file? I've had no trouble with it with the DVICO Fusion cards. I don't know what hermann meant, but different hardware copes differently with configuration file errors. One of my tuners refused Melbourne's digital channel 7 even though the other worked - until Kaffeine's configuration was corrected, then they both worked. Are you worried about the output of Zap, or the contents of a master configuration file somewhere? - What's tda10046 safe? In particular, what values do you think might be incorrect? How would one go about establishing what's wrong? Usually, if using scan from mercurial dvb-apps, it is best to set all to AUTO there except freq. and bandwidth. Is this version significantly different from the one described at http://www.linuxtv.org/wiki/index.php/Scan ? This works fine for me on all 8MHz transponders, but my single 7MHz one won't do it that way. Might differ for you. I think people had already success also with 7MHz stuff. It would appear that transponders in Adelaide are all 7 MHz. Another known pitfall with the tda10046 is that in Australia reportedly offsets of 167000Hz are in use. You might try with modified scan files with such positive and negative offsets. Where would this be? On Friday, 12 January 2007 at 15:38:01 +1100, Peter D. wrote: On Friday 12 January 2007 10:35, hermann pitton wrote: [snip] That might depend on if your au-Adelaide (?) initial scan file is already tda10046 safe. It needs correct values. Other frontends are more tolerant and this can break it for you. I forgot about that. I have two tuner cards and they differ in their capabilities when presented with wrong configuration files. Be warned that there are many places that such a config file can be lurking - especially if you are playing with multiple applications. I'm in Melbourne if you are interested in my configuration of Kaffeine. I'd certainly be interested in what differences you have in the configuration file. I think that the important change was guard interval (in Kaffeine) from 1/8 to auto. The nearest thing that I can find that looks like an authoritative source about what Australian broadcasters were using in 2003 is http://www.dba.org.au/index.asp?sectionID=120 which says that the correct guard interval is 1/16, but it also says that things can change. Do you want any information about the remote? I'd certainly be interested. Have you got any specific questions? This card (if it's the one I'm thinking of) looks like being the cheapest locally available DVB-T card, so it would be nice to get good support for it. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MSI TV @nywhere a/d support
On Saturday 13 January 2007 10:18, hermann pitton wrote: Am Freitag, den 12.01.2007, 23:55 +0100 schrieb Peter Missel: Hi all! Guys, before anyone scratches a hole into their head: The MSI [EMAIL PROTECTED] A/D is the LifeView FlyDVB-T Hybrid. Remote support, as far as I know, is identical to the FlyDVB-Trio - keydown on GPIO18 (as I discovered originally), and keycode fetch through I2C. Code for this has recently been implemented, as far as I follow things. Of course the remote is also the one LifeView supplies. I added its definition quite a while ago, when I worked on the Trio. Which reminds me - can we call I2C code from the saa7134 IRQ handler yet? regards, Peter Hi Peter, really had you in mind when I posted over, but not that exact chip anymore. Yes, there it sits on the TRIO and grins ;) Not yet I think. [snip] Does all of this mean that the remote; should work, can't possibly work, or needs to be configured properly? -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MSI TV @nywhere a/d support
On Wednesday 10 January 2007 18:21, Trevor Glen wrote: Hi All, I have a MSI TV @nywhere A/D PCI DVB-T card that I'm trying to get working on ubuntu for MythTV. The PCI id (or whatever it's called) is 4e42:3306. I've got one of them. It works with Mandriva and Kaffeine after a bit of configuration, although I haven't bothered to sort out the remote control. With an ubuntu standard kernel (version 2.6.17-10-generic) I have tried using card=94 on the modprobe, and it gets inserted into the kernel ok. Using a self compiled, Mandriva patched, kernel 2.6.17-8mdvcustom. This is in /etc/modprobe.preload saa7134 card=94$ saa7134-dvb$ I then do a modprobe saa7134_dvb and it says: DVB: registering frontend 1 (Philips TDA10046H DVB-T)... and then later: tda1004x: found firmware revision 29 -- ok I get this is syslog Jan 10 19:00:04 live kernel: tda1004x: setting up plls for 48MHz sampling clock Jan 10 19:00:06 live kernel: tda1004x: found firmware revision 29 -- ok But then when I try to tune to a channel in mythtv, I see this in the syslog: tda1004x: pll set failed Not here. In looking at the latest mercurial code, this card isn't detected automatically. What do I have to do to get that to happen? (or, please, correct me if I am wrong) Don't know, but that model does work. Hopefully an expert will jump in and offer a solution. -- sig goes here... Peter D. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVB-C PCI cards for ComHem cable
Hi all! Is there anybody on this list that have a working setup using swedish cable operator ComHem DVB-C? CA or just free channels? What card are you using? Regards, -- Peter Fassberg E-mail: [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] receiving on a server and broadcasting to machines?
Not sure, if this is the right mailinglist, but I give it try. Its less a technical than a general question about linux and dvb. If the topic is not appropriate on this list I would be happy if anyone could point me to a more suiteable location. I want to to be able to watch TV on two of my laptops (maybe different people looking different channels at the same time) So instead of buying two expensive USB-DVB-cards, I was thinking about buying one cheaper PCI-card and put it into the local server and then broadcast all the channels over the intranet. I've seen such a broadcast-option in my player Kaffeine. So now I dont have much idea what this would mean for the cpu-load and the network-load. If broadcast means that the server reads all channels simultanously and send them over the network then the server and network would break down within seconds I guess. If it means that a client can connect to the server and request a certain channel and then this channel is transmitted over the network then I would probably be ok !? The clients are connected via WLAN to the server and 20 MBit is a realistic transfer-rate that is achieved all over the covered area. I dont have any clue how much bandwith a dvb-stream needs and if the server broadcasts the original dvb-stream or an encoded version or whatever. I dont even know if the client then has all abilities that dvb brings : like stopping the TV and continue lateron - using programpreview and so on. The server is a old 500MHz-Celeron with 512MB which is more than enough for a SOHO-fileserver but maybe not for dvb-server!? On the other hand : I dont want to watch TV on that server. It should just distribute the signal. any help, hints, insights highly appretiated, thnx, peter ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvb-t usb
Hi Leif, You'll need to compile a new kernel and maybe also install the newest linux-dvb software. Do you have any experience with that? To get my Hauppauge Nova-T USB sticks to work I had to install kernel 2.6.19-rc5, newest stable linux-dvb and upgrade from Debian Sarge to Debian Testing. Please consult a Ubuntu forum / resource on how to configure, build and install a kernel package. Peter M. 2006/11/17, Leif Hanack [EMAIL PROTECTED]: Hello, please forgive me, when i'm bother you with this email:) I hope you can help me anyway. I try to use a DVB-T USB 2.0 stick with my ubuntu 6.06 2.6.15-27-386 linux. On linuxtv.org i found my hardware (Grand DVB-T Pen USB 2.0) and the supported firmware: http://www.linuxtv.org/wiki/index.ph...3000M-C.2FP.29 My problem is, that not all required modules are available (not listed with modprobe -l) on my machine. Could you give me a hint, where i can get the following modules: - crc32 (i got crc32c and crc16) - firmware_class - mt2060.ko Or did you have an idea, where i could find help? I tried a couple of forums without success. Thanks a lot, Leif ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kernel Oops when unplugging several
Hi, I expeirenced a kernel oops when removing several Nova-T sticks one by one from a USB hub. Details below and the full syslog attached Regards Peter M. Kernel 2.6.19-rc5 hg clone http://linuxtv.org/hg/v4l-dvb from 2006-11-10 Debian 3.1 Sarge on a ASUS laptop. Had connected 4 Hauppauge WinTV-PVR USB2 devices and 7 Hauppauge WinTV Nova-T devices through a copule of D-Link USB hubs. When I disconnected the Nova-T devices in fast succession I got the oops. Have tried to reproduce it without luck ;-) Nov 15 17:01:30 pingumobile kernel: usb 1-3.5: USB disconnect, address 28 Nov 15 17:01:30 pingumobile udev[16672]: removing device node '/dev/dvb/adapter0/frontend0' Nov 15 17:01:30 pingumobile udev[16681]: removing device node '/dev/dvb/adapter0/net0' Nov 15 17:01:30 pingumobile udev[16683]: removing device node '/dev/dvb/adapter0/demux0' Nov 15 17:01:30 pingumobile udev[16685]: removing device node '/dev/dvb/adapter0/dvr0' Nov 15 17:01:30 pingumobile kernel: mt2060 I2C write failed Nov 15 17:01:30 pingumobile kernel: dvb-usb: Hauppauge Nova-T Stick successfully deinitialized and disconnected. Nov 15 17:01:30 pingumobile udev[16714]: removing device node '/dev/usbdev1.28' Nov 15 17:01:31 pingumobile kernel: BUG: unable to handle kernel paging request at virtual address fff2 Nov 15 17:01:31 pingumobile kernel: printing eip: Nov 15 17:01:31 pingumobile kernel: d513c1a4 Nov 15 17:01:31 pingumobile kernel: *pde = 2067 Nov 15 17:01:31 pingumobile kernel: *pte = Nov 15 17:01:31 pingumobile kernel: Oops: [#1] Nov 15 17:01:31 pingumobile kernel: Modules linked in: wm8775 tuner cx25840 pvrusb2 cx2341x videodev v4l1_compat v4l2_common tveeprom mt2060 dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc dibx000_common pcmcia firmware_class nfsd exportfs lockd sunrpc ipv6 ide_cd parport_pc parport pcspkr rtc eth1394 ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc i2c_i801 i2c_core uhci_hcd shpchp pci_hotplug joydev intel_agp agpgart dm_mod sg usb_storage ehci_hcd usbcore ide_scsi sr_mod scsi_mod cdrom thermal button battery asus_acpi ac irtty_sir sir_dev irda crc_ccitt speedstep_centrino freq_table processor evdev psmouse mousedev snd i810_audio ac97_codec soundcore 8139too mii tg3 reiserfs ext3 jbd ide_disk ide_generic siimage aec62xx trm290 alim15x3 hpt34x hpt366 cmd64x piix rz1000 slc90e66 generic cs5530 cs5520 sc1200 triflex atiixp pdc202xx_old pdc202xx_new opti621 ns87415 cy82c693 am Nov 15 17:01:31 pingumobile kernel: 74xx sis5513 via82cxxx serverworks ide_core unix Nov 15 17:01:31 pingumobile kernel: CPU:0 Nov 15 17:01:31 pingumobile kernel: EIP: 0060:[pg0+349811108/1069929472]Not tainted VLI Nov 15 17:01:31 pingumobile kernel: EFLAGS: 00210246 (2.6.19-rc5-2m #1) Nov 15 17:01:31 pingumobile kernel: EIP is at 0xd513c1a4 Nov 15 17:01:31 pingumobile kernel: eax: ccf6872c ebx: 80046f45 ecx: edx: bf9bfd38 Nov 15 17:01:31 pingumobile kernel: esi: fff2 edi: c8c7dea8 ebp: esp: c8c7de94 Nov 15 17:01:31 pingumobile kernel: ds: 007b es: 007b ss: 0068 Nov 15 17:01:31 pingumobile kernel: Process tzap (pid: 15964, ti=c8c7c000 task=ccf11550 task.ti=c8c7c000) Nov 15 17:01:31 pingumobile kernel: Stack: e0d5c604 ccf6872c d355cb00 80046f45 c8c7dea8 001f de63c000 000a Nov 15 17:01:31 pingumobile kernel:004e 0001 00200286 c01fe804 000a de63c000 Nov 15 17:01:31 pingumobile kernel:004f ccf11550 c02f6fd4 00200082 004f c8c7df14 Nov 15 17:01:31 pingumobile kernel: Call Trace: Nov 15 17:01:31 pingumobile kernel: [pg0+547075588/1069929472] dvb_usercopy+0xb0/0x110 [dvb_core] Nov 15 17:01:31 pingumobile kernel: [write_chan+461/483] write_chan+0x1cd/0x1e3 Nov 15 17:01:31 pingumobile kernel: [pg0+547074557/1069929472] dvb_generic_ioctl+0x43/0x47 [dvb_core] Nov 15 17:01:31 pingumobile kernel: [do_ioctl+93/99] do_ioctl+0x5d/0x63 Nov 15 17:01:31 pingumobile kernel: [vfs_ioctl+392/403] vfs_ioctl+0x188/0x193 Nov 15 17:01:31 pingumobile kernel: [sys_ioctl+91/119] sys_ioctl+0x5b/0x77 Nov 15 17:01:31 pingumobile kernel: [syscall_call+7/11] syscall_call+0x7/0xb Nov 15 17:01:31 pingumobile kernel: === Nov 15 17:01:31 pingumobile kernel: Code: 00 00 00 00 00 00 00 41 ac 1e c0 80 0d ef df 00 00 00 00 8c c1 13 d5 8c c1 13 d5 ba e4 1c c0 80 c1 13 d5 c0 6b f1 df 00 00 00 00 a4 c1 13 d5 a4 c1 13 d5 00 00 00 00 00 00 00 00 e0 c7 38 c0 40 Nov 15 17:01:31 pingumobile kernel: EIP: [pg0+349811108/1069929472] 0xd513c1a4 SS:ESP 0068:c8c7de94 Nov 15 17:01:31 pingumobile kernel: 1BUG: unable to handle kernel NULL pointer dereference at virtual address 01b0 Nov 15 17:01:31 pingumobile kernel: printing eip: Nov 15 17:01:31 pingumobile kernel: e0d62e66 Nov 15 17:01:31 pingumobile kernel: *pde = Nov 15 17:01:31 pingumobile kernel: Oops: 0002 [#2
[linux-dvb] Kernel Oops when unplugging several Nova-T devices
Just corrected the subject to clarify the device type. Peter 2006/11/17, Peter M. [EMAIL PROTECTED]: Hi, I expeirenced a kernel oops when removing several Nova-T sticks one by one from a USB hub. Details below and the full syslog attached Regards Peter M. Kernel 2.6.19-rc5 hg clone http://linuxtv.org/hg/v4l-dvb from 2006-11-10 Debian 3.1 Sarge on a ASUS laptop. Had connected 4 Hauppauge WinTV-PVR USB2 devices and 7 Hauppauge WinTV Nova-T devices through a copule of D-Link USB hubs. When I disconnected the Nova-T devices in fast succession I got the oops. Have tried to reproduce it without luck ;-) Nov 15 17:01:30 pingumobile kernel: usb 1-3.5: USB disconnect, address 28 Nov 15 17:01:30 pingumobile udev[16672]: removing device node '/dev/dvb/adapter0/frontend0' Nov 15 17:01:30 pingumobile udev[16681]: removing device node '/dev/dvb/adapter0/net0' Nov 15 17:01:30 pingumobile udev[16683]: removing device node '/dev/dvb/adapter0/demux0' Nov 15 17:01:30 pingumobile udev[16685]: removing device node '/dev/dvb/adapter0/dvr0' Nov 15 17:01:30 pingumobile kernel: mt2060 I2C write failed Nov 15 17:01:30 pingumobile kernel: dvb-usb: Hauppauge Nova-T Stick successfully deinitialized and disconnected. Nov 15 17:01:30 pingumobile udev[16714]: removing device node '/dev/usbdev1.28' Nov 15 17:01:31 pingumobile kernel: BUG: unable to handle kernel paging request at virtual address fff2 Nov 15 17:01:31 pingumobile kernel: printing eip: Nov 15 17:01:31 pingumobile kernel: d513c1a4 Nov 15 17:01:31 pingumobile kernel: *pde = 2067 Nov 15 17:01:31 pingumobile kernel: *pte = Nov 15 17:01:31 pingumobile kernel: Oops: [#1] Nov 15 17:01:31 pingumobile kernel: Modules linked in: wm8775 tuner cx25840 pvrusb2 cx2341x videodev v4l1_compat v4l2_common tveeprom mt2060 dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc dibx000_common pcmcia firmware_class nfsd exportfs lockd sunrpc ipv6 ide_cd parport_pc parport pcspkr rtc eth1394 ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc i2c_i801 i2c_core uhci_hcd shpchp pci_hotplug joydev intel_agp agpgart dm_mod sg usb_storage ehci_hcd usbcore ide_scsi sr_mod scsi_mod cdrom thermal button battery asus_acpi ac irtty_sir sir_dev irda crc_ccitt speedstep_centrino freq_table processor evdev psmouse mousedev snd i810_audio ac97_codec soundcore 8139too mii tg3 reiserfs ext3 jbd ide_disk ide_generic siimage aec62xx trm290 alim15x3 hpt34x hpt366 cmd64x piix rz1000 slc90e66 generic cs5530 cs5520 sc1200 triflex atiixp pdc202xx_old pdc202xx_new opti621 ns87415 cy82c693 am Nov 15 17:01:31 pingumobile kernel: 74xx sis5513 via82cxxx serverworks ide_core unix Nov 15 17:01:31 pingumobile kernel: CPU:0 Nov 15 17:01:31 pingumobile kernel: EIP: 0060:[pg0+349811108/1069929472]Not tainted VLI Nov 15 17:01:31 pingumobile kernel: EFLAGS: 00210246 (2.6.19-rc5-2m #1) Nov 15 17:01:31 pingumobile kernel: EIP is at 0xd513c1a4 Nov 15 17:01:31 pingumobile kernel: eax: ccf6872c ebx: 80046f45 ecx: edx: bf9bfd38 Nov 15 17:01:31 pingumobile kernel: esi: fff2 edi: c8c7dea8 ebp: esp: c8c7de94 Nov 15 17:01:31 pingumobile kernel: ds: 007b es: 007b ss: 0068 Nov 15 17:01:31 pingumobile kernel: Process tzap (pid: 15964, ti=c8c7c000 task=ccf11550 task.ti=c8c7c000) Nov 15 17:01:31 pingumobile kernel: Stack: e0d5c604 ccf6872c d355cb00 80046f45 c8c7dea8 001f de63c000 000a Nov 15 17:01:31 pingumobile kernel:004e 0001 00200286 c01fe804 000a de63c000 Nov 15 17:01:31 pingumobile kernel:004f ccf11550 c02f6fd4 00200082 004f c8c7df14 Nov 15 17:01:31 pingumobile kernel: Call Trace: Nov 15 17:01:31 pingumobile kernel: [pg0+547075588/1069929472] dvb_usercopy+0xb0/0x110 [dvb_core] Nov 15 17:01:31 pingumobile kernel: [write_chan+461/483] write_chan+0x1cd/0x1e3 Nov 15 17:01:31 pingumobile kernel: [pg0+547074557/1069929472] dvb_generic_ioctl+0x43/0x47 [dvb_core] Nov 15 17:01:31 pingumobile kernel: [do_ioctl+93/99] do_ioctl+0x5d/0x63 Nov 15 17:01:31 pingumobile kernel: [vfs_ioctl+392/403] vfs_ioctl+0x188/0x193 Nov 15 17:01:31 pingumobile kernel: [sys_ioctl+91/119] sys_ioctl+0x5b/0x77 Nov 15 17:01:31 pingumobile kernel: [syscall_call+7/11] syscall_call+0x7/0xb Nov 15 17:01:31 pingumobile kernel: === Nov 15 17:01:31 pingumobile kernel: Code: 00 00 00 00 00 00 00 41 ac 1e c0 80 0d ef df 00 00 00 00 8c c1 13 d5 8c c1 13 d5 ba e4 1c c0 80 c1 13 d5 c0 6b f1 df 00 00 00 00 a4 c1 13 d5 a4 c1 13 d5 00 00 00 00 00 00 00 00 e0 c7 38 c0 40 Nov 15 17:01:31 pingumobile kernel: EIP: [pg0+349811108/1069929472] 0xd513c1a4 SS:ESP 0068:c8c7de94 Nov 15 17:01:31 pingumobile kernel: 1BUG: unable to handle kernel NULL pointer dereference at virtual address 01b0 Nov 15 17:01:31 pingumobile kernel: printing eip: Nov 15 17:01:31 pingumobile kernel
Re: [linux-dvb] Kernel Oops when unplugging several
Hi Markus, Thanks for your mail. I have just joined the list today. 2006/11/17, Markus Rechberger [EMAIL PROTECTED]: Hi, could you test: http://linuxtv.org/hg/~mrechberger/v4l-dvb-stable this should at least fix the tzap, this is just 1/4 of what has to be done to make it stable. What problem with tzap? For me it works for Nova-T adapter 0,1,2,3. Not for device 4,5,6. I think it has something to do with udev device major numbers. I'm currently upgrading my laptop to Debian Etch which should give me a more modern udev. 1/4 of work to get v4l-dvb stable or just the drivers for Nova-T stick? Regards Peter Markus On 11/17/06, Peter M. [EMAIL PROTECTED] wrote: Hi, I expeirenced a kernel oops when removing several Nova-T sticks one by one from a USB hub. Details below and the full syslog attached Regards Peter M. Kernel 2.6.19-rc5 hg clone http://linuxtv.org/hg/v4l-dvb from 2006-11-10 Debian 3.1 Sarge on a ASUS laptop. Had connected 4 Hauppauge WinTV-PVR USB2 devices and 7 Hauppauge WinTV Nova-T devices through a copule of D-Link USB hubs. When I disconnected the Nova-T devices in fast succession I got the oops. Have tried to reproduce it without luck ;-) Nov 15 17:01:30 pingumobile kernel: usb 1-3.5: USB disconnect, address 28 Nov 15 17:01:30 pingumobile udev[16672]: removing device node '/dev/dvb/adapter0/frontend0' Nov 15 17:01:30 pingumobile udev[16681]: removing device node '/dev/dvb/adapter0/net0' Nov 15 17:01:30 pingumobile udev[16683]: removing device node '/dev/dvb/adapter0/demux0' Nov 15 17:01:30 pingumobile udev[16685]: removing device node '/dev/dvb/adapter0/dvr0' Nov 15 17:01:30 pingumobile kernel: mt2060 I2C write failed Nov 15 17:01:30 pingumobile kernel: dvb-usb: Hauppauge Nova-T Stick successfully deinitialized and disconnected. Nov 15 17:01:30 pingumobile udev[16714]: removing device node '/dev/usbdev1.28' Nov 15 17:01:31 pingumobile kernel: BUG: unable to handle kernel paging request at virtual address fff2 Nov 15 17:01:31 pingumobile kernel: printing eip: Nov 15 17:01:31 pingumobile kernel: d513c1a4 Nov 15 17:01:31 pingumobile kernel: *pde = 2067 Nov 15 17:01:31 pingumobile kernel: *pte = Nov 15 17:01:31 pingumobile kernel: Oops: [#1] Nov 15 17:01:31 pingumobile kernel: Modules linked in: wm8775 tuner cx25840 pvrusb2 cx2341x videodev v4l1_compat v4l2_common tveeprom mt2060 dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc dibx000_common pcmcia firmware_class nfsd exportfs lockd sunrpc ipv6 ide_cd parport_pc parport pcspkr rtc eth1394 ohci1394 ieee1394 yenta_socket rsrc_nonstatic pcmcia_core snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd_page_alloc i2c_i801 i2c_core uhci_hcd shpchp pci_hotplug joydev intel_agp agpgart dm_mod sg usb_storage ehci_hcd usbcore ide_scsi sr_mod scsi_mod cdrom thermal button battery asus_acpi ac irtty_sir sir_dev irda crc_ccitt speedstep_centrino freq_table processor evdev psmouse mousedev snd i810_audio ac97_codec soundcore 8139too mii tg3 reiserfs ext3 jbd ide_disk ide_generic siimage aec62xx trm290 alim15x3 hpt34x hpt366 cmd64x piix rz1000 slc90e66 generic cs5530 cs5520 sc1200 triflex atiixp pdc202xx_old pdc202xx_new opti621 ns87415 cy82c693 am Nov 15 17:01:31 pingumobile kernel: 74xx sis5513 via82cxxx serverworks ide_core unix Nov 15 17:01:31 pingumobile kernel: CPU:0 Nov 15 17:01:31 pingumobile kernel: EIP: 0060:[pg0+349811108/1069929472]Not tainted VLI Nov 15 17:01:31 pingumobile kernel: EFLAGS: 00210246 (2.6.19-rc5-2m #1) Nov 15 17:01:31 pingumobile kernel: EIP is at 0xd513c1a4 Nov 15 17:01:31 pingumobile kernel: eax: ccf6872c ebx: 80046f45 ecx: edx: bf9bfd38 Nov 15 17:01:31 pingumobile kernel: esi: fff2 edi: c8c7dea8 ebp: esp: c8c7de94 Nov 15 17:01:31 pingumobile kernel: ds: 007b es: 007b ss: 0068 Nov 15 17:01:31 pingumobile kernel: Process tzap (pid: 15964, ti=c8c7c000 task=ccf11550 task.ti=c8c7c000) Nov 15 17:01:31 pingumobile kernel: Stack: e0d5c604 ccf6872c d355cb00 80046f45 c8c7dea8 001f de63c000 000a Nov 15 17:01:31 pingumobile kernel:004e 0001 00200286 c01fe804 000a de63c000 Nov 15 17:01:31 pingumobile kernel:004f ccf11550 c02f6fd4 00200082 004f c8c7df14 Nov 15 17:01:31 pingumobile kernel: Call Trace: Nov 15 17:01:31 pingumobile kernel: [pg0+547075588/1069929472] dvb_usercopy+0xb0/0x110 [dvb_core] Nov 15 17:01:31 pingumobile kernel: [write_chan+461/483] write_chan+0x1cd/0x1e3 Nov 15 17:01:31 pingumobile kernel: [pg0+547074557/1069929472] dvb_generic_ioctl+0x43/0x47 [dvb_core] Nov 15 17:01:31 pingumobile kernel: [do_ioctl+93/99] do_ioctl+0x5d/0x63 Nov 15 17:01:31 pingumobile kernel: [vfs_ioctl+392/403] vfs_ioctl+0x188/0x193 Nov 15 17:01:31 pingumobile kernel: [sys_ioctl+91/119] sys_ioctl+0x5b/0x77 Nov 15 17:01:31 pingumobile
[linux-dvb] Hanftek UMT-010
hi, is this USB device supported? lsusb says: Bus 005 Device 002: ID 15f4:0001 HanfTek HanfTek UMT-010 USB2.0 DVB-T (cold) after loading the Hanftek firmware: Bus 001 Device 008: ID 15f4:0015 HanfTek /proc/bus/usb/devices T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 8 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=15f4 ProdID=0015 Rev= 0.01 S: Manufacturer=UMT-010 V00.01 S: Product=HANF FIRMWARE C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 4 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none) E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 512 Ivl=0ms E: Ad=86(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms lsmod |grep dvb dvb_usb_umt_010 5760 1 dvb_usb_dibusb_common 6788 1 dvb_usb_umt_010 dib3000mc 14848 1 dvb_usb_dibusb_common dvb_usb16264 2 dvb_usb_umt_010,dvb_usb_dibusb_common dvb_core 70568 1 dvb_usb dvb_pll13060 3 dvb_usb_umt_010,dvb_usb_dibusb_common,dvb_usb mt352 6916 1 dvb_usb_umt_010 i2c_core 17792 6 dvb_usb,dvb_pll,mt352,i2c_ec,dib3000_common,i2c_i801 usbcore 107908 9 dvb_usb_umt_010,dvb_usb,usb_storage,libusual,usbhid,usbkbd,uhci_hcd,ehci_hcd kaffeine accepting the device as Zarlink MT352 but channelscan find no channels. winxp says, it's a CE device the device works fine under win, hardware o.k. thx Horst -- Ein Herz für Kinder - Ihre Spende hilft! Aktion: www.deutschlandsegelt.de Unser Dankeschön: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Freecom tuning
Hello, Having finally got my system to recognise my Freecom USB DVB-T stick, I am now having no luck tuning it. Does anyone have any pointers? Many, many thanks. A few file outputs are shown below. Peter Here is my tuning file: # Nottingham (Kimberley, Nottinghamshire) # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 53000 8MHz 3/4 3/4 QAM16 2k 1/32 NONE T 61000 8MHz 3/4 3/4 QAM16 2k 1/32 NONE T 73000 8MHz 2/3 1/2 QAM64 2k 1/32 NONE T 77000 8MHz 3/4 3/4 QAM16 2k 1/32 NONE T 81000 8MHz 3/4 3/4 QAM16 2k 1/32 NONE T 84000 8MHz 2/3 1/2 QAM64 2k 1/32 NONE Here is the result of scandvb on this file: [EMAIL PROTECTED] siepmann]# scandvb /home/siepmann/.kde/share/apps/kaffeine/dvb-t/uk-Nottingham scanning /home/siepmann/.kde/share/apps/kaffeine/dvb-t/uk-Nottingham using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 53000 0 3 3 1 0 0 0 initial transponder 61000 0 3 3 1 0 0 0 initial transponder 73000 0 2 1 3 0 0 0 initial transponder 77000 0 3 3 1 0 0 0 initial transponder 81000 0 3 3 1 0 0 0 initial transponder 84000 0 2 1 3 0 0 0 tune to: 53000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 53000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 61000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 61000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 77000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 77000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 81000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 81000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_3_4:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 84000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 84000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. Here is dmesg on connection of the device: usb 4-5: new high speed USB device using ehci_hcd and address 8 usb 4-5: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-wt220u-fc03.fw' usb 4-5: USB disconnect, address 8 dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. usb 4-5: new high speed USB device using ehci_hcd and address 9 usb 4-5: configuration #1 chosen from 1 choice dvb-usb: found a 'WideView WT-220U PenType Receiver (Typhoon/Freecom)' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 15). DVB: registering new adapter (WideView WT-220U PenType Receiver (Typhoon/Freecom)). DVB: registering frontend 0 (WideView USB DVB-T)... input: IR-receiver inside an USB DVB receiver as /class/input/input7 dvb-usb: schedule remote query interval to 300 msecs. dvb-usb: WideView WT-220U PenType Receiver (Typhoon/Freecom) successfully initialized and connected. dvb-usb: recv bulk message failed: -110 -- Peter Siepmann Nottingham, UK http://www.petersiepmann.net ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DIVCO Fusion (Utraview) tuning problem 2.6.18 kernel
G'day all, has the tuning problem with the 2.6.18 kernels for the Dvico Fusion HDTV cards been solved yet? I have the problem with Fedora Core 5 and 6 with this kernel (module-init-tools 3.2.2) using mplayer I get: dvb_tune Freq: 205625000 Not able to lock to the signal on the given frequency, timeout: 3 dvb_tune, TUNING FAILED ERROR, COULDN'T SET CHANNEL 0: Failed to open dvb://ABC TV. tzap gives me: using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 205625000 Hz video pid 0x0200, audio pid 0x028a status 00 | signal 10bf | snr | ber | unc | status 00 | signal 000f | snr | ber | unc | //repeated forever lsmod looks ok to me, loading mt352 module. uname -a Linux zoot.mcneils.net 2.6.18-1.2200.fc5 #1 SMP Sat Oct 14 16:59:56 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux I saw this thread http://linuxtv.org/pipermail/linux-dvb/2006-September/012639.html and this one http://www.linuxtv.org/pipermail/linux-dvb/2006-September/012691.html which seems to suggest people were working on it but I haven't seen any conclusions. Can anyone shed some light on this? I'd love to keep my system up to date but if I can't have my DVB ... Cheers, Peter. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Using card reader in a dreambox
I have a dreambox connected to the lan here with a Sk* UK Free sat card in it. I would like to know if there is anyway I can use the card reader and cam from my linux box on the same subnet to view Channel 4 and 5 using freevo / mplayer? Unfortunately, afaik that is impossible. However, if you use VDR and the softcam plugin (VDR-SC) you can do that. I havn't tried it, but according to other postings is should work. It's probably illegal in some countries, even if you have a valid subscription. I'd love to have a descrambler that can be used as a filter: dvbstream | descramble | mplayer In the Windows world it's almost there: http://joshyfun.peque.org/OfflineDescrambler/ I've used it once when I needed to record two scrambled programs sent simultaneous on the same DVB-S transponder. -- Peter Fassberg ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Compilation issues in kernel 2.6.18
Hmm... I suspect you didn't enabled I2C or V4L support. I've ensured these are now enabled. I noticed this warning on running 'make bzImage': Warning! Found recursive dependency: I2C VIDEO_MXB VIDEO_SAA7146_VV VIDEO_SAA7146 I2C Might this be the root of the problem? Any ideas how to resolve it? Many thanks! Peter -- Peter Siepmann Nottingham, UK http://www.petersiepmann.net ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Compilation issues in kernel 2.6.18
I am try to get my Freecom DVB stick to work under Fedora. It is the one with product/vendor id 14aa:0225 so is turning out to be more complicated than I first imagined (as it seems this product code is not in the version of dvb-usb included in the Fedora package). So, armed with the source of kernel 2.6.18, and the source of linux-dvb-1.1.1, I ran makelinks which did its stuff. make bzImage worked fine but make modules finds compilation errors in drivers/media/common/saa7146_i2c.c and bails out. Is this a noted problem? Is there a corrected version of this file out there somewhere? Many thanks. Peter -- Peter Siepmann Nottingham, UK http://www.petersiepmann.net ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Compilation issues in kernel 2.6.18
Julian Scheel wrote: Am Sonntag, 22. Oktober 2006 16:33 schrieb Peter Siepmann: make bzImage worked fine but make modules finds compilation errors in drivers/media/common/saa7146_i2c.c and bails out. Is this a noted problem? Is there a corrected version of this file out there somewhere? Please post the exact error message, without it'll be hard to help you. In file included from drivers/media/common/saa7146_i2c.c:2: include/media/saa7146_vv.h:187: warning: ‘struct video_device’ declared inside parameter list include/media/saa7146_vv.h:187: warning: its scope is only this definition or declaration, which is probably not what you want include/media/saa7146_vv.h:188: warning: ‘struct video_device’ declared inside parameter list drivers/media/common/saa7146_i2c.c:397: error: unknown field ‘name’ specified in initializer drivers/media/common/saa7146_i2c.c:397: warning: initialization from incompatible pointer type drivers/media/common/saa7146_i2c.c:398: error: unknown field ‘id’ specified in initializer drivers/media/common/saa7146_i2c.c:398: error: ‘I2C_ALGO_SAA7146’ undeclared here (not in a function) drivers/media/common/saa7146_i2c.c: In function ‘saa7146_i2c_adapter_prepare’: drivers/media/common/saa7146_i2c.c:428: error: ‘I2C_ADAP_CLASS_TV_ANALOG’ undeclared (first use in this function) drivers/media/common/saa7146_i2c.c:428: error: (Each undeclared identifier is reported only once drivers/media/common/saa7146_i2c.c:428: error: for each function it appears in.) make[3]: *** [drivers/media/common/saa7146_i2c.o] Error 1 make[2]: *** [drivers/media/common] Error 2 make[1]: *** [drivers/media] Error 2 make: *** [drivers] Error 2 -- Peter Siepmann Nottingham, UK http://www.petersiepmann.net ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TTUSB DEC-2000T Driver: tuning problems
Mario Rossi schrieb:
IIRC DMX_PES_OTHER is the correct pid filter, while DMX_PES_AUDIO and
_VIDEO
were used only by FF cards
... and all devices driven by the ttusb-dec driver ;)
This is the same thing I've read.
The card has a MPEG-decoder but it is not possible to use it from USB
(it works when connecting the card to television), so I am not sure
whether it is a FF card or not.
Reading the source code, in
linux/drivers/media/dvb/ttusb-dec/ttusb_dec.c I can find a lot of
support for _PES_AUDIO and _PES_VIDEO while (apparently) nothing for
_PES_OTHER.
It's not really a FF card as the MPEG-decoder is not used when connected to
a pc, as you said. However the card does the initial processing of the TS
stream,
and sends only the extracted MPEG ES stream for video and the MPEG PES stream
for audio(iirc).
It not possible to just get a part of the TS stream by setting an arbitrary PID
filter.
It is only possible to tell the device which PIDs belong to the video/audio
stream.
So using DMX_PES_OTHER is not possible.
An application can simply try DMX_PES_OTHER first and if -ENOTSUPPORTED is
returned,
as it would be the case here, it can fallback to DMX_PES_{AUDIO,VIDEO}.
Mythtv does it this way afaik.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital problems
Kielogl wrote: I also tried Chris Pascoe's tree http://linuxtv.org/hg/~pascoe/v4l-dvb-test/ and it has the same problems with USB tuner stability and with SBS on the PCI tuner. But it does not require the +17Hz offset for Nine and SBS (thanks Damien) as the current development tree does, so it looks like all of Chris's changes have not been merged as yet. I have both tuners working fine under 2.6.16.19 with the hg tree using the ZL10353 based version, with the following transports for SBS and Nine in Melbourne: Nine: 191791667 SBS: 53667 Perhaps try a stock kernel instead of the FC-rolled version? Cheers, Pete ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] What should scan files look like
Hi Alan! You are perfectly right! All my files look that way. -- Peter Fassberg On Wed, 20 Sep 2006, Alan Chandler wrote: I am a bit puzzled over exactly what scan files (ie the driving file for the scan program) should contain. In particular, with my Freecom usb pen drive (14aa:0225 ids), the scan file for the UK Crystal Palace that is distributed with scan does not work. It has the single line T 50583 8MHz 3/4 NONE QAM16 2k 1/32 NONE noting in particular the frequency of 505.83MHz, against the published frequency for JUST ONE of the multiplexes at Crystal Palace of 506MHz. There was a post on this list that the Freecom device needed an exact frequency because of a firmware bug, so I did create a new file with T 50600 8MHz 3/4 NONE QAM16 2k 1/32 NONE And it appears to find the channels on one of the multiplexes. But Crystal Palace has six multiplexes for digital terrestial TV, some with frequencies above and below the 506MHz I had a poke around the code as to how it was finding frequencies to scan, but couldn't really understand it. It appeared to be generating the next scan frequency once it had done the initial tune, but it was too hard without really getting down and understanding it. I have created a file with the following in, and it works (in the sense that it scans the 6 frequencies mentioned and finds loads of channels, and then starts looking at others and fails most of the time but does seem to pick up some more) T 50600 8MHz 3/4 NONE QAM16 2k 1/32 NONE T 48200 8MHz 3/4 NONE QAM64 2k 1/32 NONE T 56200 8MHz 3/4 NONE QAM64 2k 1/32 NONE T 53000 8MHz 3/4 NONE QAM16 2k 1/32 NONE T 57800 8MHz 3/4 NONE QAM16 2k 1/32 NONE T 53800 8MHz 3/4 NONE QAM16 2k 1/32 NONE So is this what the uk-CrystalPalace file _should_ look like, or have I totally misunderstood what should happen ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cx88 pci_abort messages
Scott wrote: Greets. I have a FusionHDTV5 Gold RT running under Gentoo and vanilla kernel 2.6.18-rc7. The drivers load and I can view OTA ATSC streams using mplayer. I'm seeing the following message log: cx88[0]: irq mpeg [0x8] pci_abort* cx88[0]/2: general errors: 0x0008 What can cause these messages? Are the safe to ignore? Some output from my logs and lspci: These are generally caused by another device stealing the IRQ from the tuner card, and this is likely to cause corruption in your MPEG stream. To find out what devices the card is sharing an interrupt with, `cat /proc/interrupts`. Shuffle the card around until it's not sharing any more, or until it's sharing with a device that has sensible interrupt handling. Cheers, Pete ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
