Re: [linux-dvb] Implementing support for multi-channel
2008/3/12 Ben Backx [EMAIL PROTECTED]: Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi-channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? AFAIK tuners can already receive from multiple channels as long as they are on the same transponder (I think that's the right word). So in Australia you can receive channel 7 and the channel 7 guide because they are broadcast together. But I don't think you can do anymore than that. I think mythtv is capable of doing it so you could have a look at that. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Implementing support for multi-channel
-Original Message- From: Jarryd Beck [mailto:[EMAIL PROTECTED] Sent: 12 March 2008 11:32 To: Ben Backx Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Implementing support for multi-channel 2008/3/12 Ben Backx [EMAIL PROTECTED]: Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi- channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? AFAIK tuners can already receive from multiple channels as long as they are on the same transponder (I think that's the right word). So in Australia you can receive channel 7 and the channel 7 guide because they are broadcast together. But I don't think you can do anymore than that. I think mythtv is capable of doing it so you could have a look at that. Jarryd. The tuner-part is no problem indeed (as you said: as long as the channels are on the same transponder). But for the moment: the driver-part is the problem, I don't think my driver supports the filtering of more than one channel at a time. So my question is: which (existing) driver does support multi-channel filtering? So I can have a look and see what modifications have to be made to my driver to implement multi-channel filtering. Ben ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Implementing support for multi-channel
Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi-channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? Regards, Ben ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] MT2266 I2C write failed, usb disconnet, WinTV Nova-TD stick, remote
Hello everyone! I recently installed mythbunut 7.10 and tried to get the WinTV Nova-TD stick working with the latest v4l-sources (mercurial) Output of lsusb: ID 2040:9580 Hauppauge Hauppauge Remote: A415-HPG-WE-A When I start mythbuntu, I get the following error, after switching the channels using the mythbuntu frontend (dmesg): ## [ 11.46] dib0700: loaded with support for 6 different device-types [ 11.46] dvb-usb: found a 'Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity' in warm state. [ 11.46] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 11.464000] DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) [ 11.708000] DVB: registering frontend 0 (DiBcom 7000PC)... [ 11.764000] ACPI: PCI Interrupt :00:14.2[A] - GSI 16 (level, low) - IRQ 16 [ 11.776000] MT2266: successfully identified [ 11.90] input: ImPS/2 Logitech Wheel Mouse as /class/input/input2 [ 11.904000] input: PC Speaker as /class/input/input3 [ 11.904000] parport_pc 00:0a: reported by Plug and Play ACPI [ 11.904000] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] [ 11.932000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 11.932000] DVB: registering new adapter (Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity) [ 11.984000] hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... [ 12.084000] DVB: registering frontend 1 (DiBcom 7000PC)... [ 12.088000] MT2266: successfully identified [ 12.244000] input: IR-receiver inside an USB DVB receiver as /class/input/input4 [ 12.244000] dvb-usb: schedule remote query interval to 150 msecs. [ 12.244000] dvb-usb: Hauppauge Nova-TD Stick/Elgato Eye-TV Diversity successfully initialized and connected. [ 12.244000] usbcore: registered new interface driver dvb_usb_dib0700 [ 12.644000] lp0: using parport0 (interrupt-driven). [ 12.864000] Adding 2642652k swap on /dev/sda5. Priority:-1 extents:1 across:2642652k [ 172.72] EXT3 FS on sda1, internal journal [ 174.548000] input: Power Button (FF) as /class/input/input5 [ 174.548000] ACPI: Power Button (FF) [PWRF] [ 174.548000] input: Power Button (CM) as /class/input/input6 [ 174.548000] ACPI: Power Button (CM) [PWRB] [ 174.596000] No dock devices found. [ 177.108000] r8169: eth0: link up [ 177.108000] r8169: eth0: link up [ 177.744000] NET: Registered protocol family 10 [ 177.748000] lo: Disabled Privacy Extensions [ 189.30] NET: Registered protocol family 17 [ 203.584000] eth0: no IPv6 routers present [ 232.72] hda-intel: Invalid position buffer, using LPIB read method instead. [ 428.888000] UDF-fs: Partition marked readonly; forcing readonly mount [ 428.936000] UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'Belleville', timestamp 2036/02/07 02:58 (103c) [ 459.596000] dib0700: Unknown remote controller key: 12 2A 1 0 [ 459.748000] dib0700: Unknown remote controller key: F A 1 0 [ 628.492000] hub 4-0:1.0: port 9 disabled by hub (EMI?), re-enabling... [ 628.492000] usb 4-9: USB disconnect, address 2 [ 628.50] MT2266 I2C write failed [ 628.50] MT2266 I2C write failed [ 650.208000] dvb-usb: error while stopping stream. [ 650.208000] MT2266 I2C write failed (len=9) [ 650.224000] MT2266 I2C write failed (len=4) [ 650.224000] MT2266 I2C write failed (len=3) [ 650.224000] MT2266 I2C read failed [ 650.24] MT2266 I2C read failed [ 650.256000] MT2266 I2C read failed [ 650.272000] MT2266 I2C read failed [ 650.288000] MT2266 I2C read failed [ 650.304000] MT2266 I2C read failed [ 650.32] MT2266 I2C read failed [ 650.336000] MT2266 I2C read failed [ 650.352000] MT2266 I2C read failed [ 650.368000] MT2266 I2C read failed ### If I disable the remote sensor in /etc/modprobe.d/options via options dvb_usb disable_rc_polling=1 this i2c failures do not seem to occur. Maybe it is a problem of the mainboard. It is an Asus m2a-vm hdmi (amd690g chipset and ati x1250 onboard graphics) with the latest Bios (1604). Best regards Bernhard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Implementing support for multi-channel
Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi-channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? Check out the dvbstreamer project: http://dvbstreamer.sourceforge.net/ This allows multi-channel recording / streaming if the DVB device supports sending the whole transport stream (some usb devices do not support this). This works by sending the whole transport stream to the dvbstreamer program, then this program allows filtering out and recording separate channels from that stream as required. This isn't a driver level solution, but might provide the function you need. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Implementing support for multi-channel
On Wed, Mar 12, 2008 at 12:19 PM, Stephen Rowles [EMAIL PROTECTED] wrote: Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi-channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? Check out the dvbstreamer project: http://dvbstreamer.sourceforge.net/ This allows multi-channel recording / streaming if the DVB device supports sending the whole transport stream (some usb devices do not support this). This works by sending the whole transport stream to the dvbstreamer program, then this program allows filtering out and recording separate channels from that stream as required. This isn't a driver level solution, but might provide the function you need. Read this blog post, this solution does not take the full stream but just filters the pids it requires for the different channels allowing it to work on most USB devices also. http://zaheer.merali.org/articles/2008/02/29/multiple-dvb-channels-streamed-by-flumotion-from-same-capture-card/ Zaheer ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Tue, Mar 11, 2008 at 11:06 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Also when I plugged it in, it sat there for about 10 seconds before finishing loading (dmesg printed another 5 lines about the device after about 10 seconds), but still no tuning. Can I see those five lines? ;-) While you're at it, you may as well include dmesg from the point that the bridge driver loads and on. Here's dmesg from the point it starts up until it finishes printing stuff. usb 2-10: new high speed USB device using ehci_hcd and address 22 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Leadtek Winfast DTV Dongle Gold) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 2 (Afatech AF9013 DVB-T)... af9015_tuner_attach: tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input34 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Leadtek Winfast DTV Dongle Gold successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input35 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 This is channel 7's entry in channels.conf: 7 Digital:17750:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:513:514:1312 Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Good Luck, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re : Implementing support for multi-channel
On 03/12/2008 06:36:04 AM, Ben Backx wrote: -Original Message- From: Jarryd Beck [mailto:[EMAIL PROTECTED] Sent: 12 March 2008 11:32 To: Ben Backx Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Implementing support for multi-channel 2008/3/12 Ben Backx [EMAIL PROTECTED]: Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi- channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? AFAIK tuners can already receive from multiple channels as long as they are on the same transponder (I think that's the right word). So in Australia you can receive channel 7 and the channel 7 guide because they are broadcast together. But I don't think you can do anymore than that. I think mythtv is capable of doing it so you could have a look at that. Jarryd. The tuner-part is no problem indeed (as you said: as long as the channels are on the same transponder). But for the moment: the driver-part is the problem, I don't think my driver supports the filtering of more than one channel at a time. So my question is: which (existing) driver does support multi-channel filtering? So I can have a look and see what modifications have to be made to my driver to implement multi-channel filtering. What is done for now is that some (all?) drivers can send the full stream and userspace apps do the demux of one or several channels themselves. Mythtv is doing just that, I guess vdr also. HTH Bye Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
hello
I looked sniffs and find correct demodulator initialization values for
this NXP tuner. Copy paste correct table from attached file and try.
Hopefully it works. I compared your sniff to mt2060 and qt1010 based
devices and there was still some minor differences to check.
regards,
Antti
Michael Krufky wrote:
On Tue, Mar 11, 2008 at 11:06 PM, Jarryd Beck [EMAIL PROTECTED] wrote:
Also when I plugged it in, it sat there for about 10 seconds before
finishing loading (dmesg printed another 5 lines about the device
after about 10 seconds), but still no tuning.
Can I see those five lines? ;-)
While you're at it, you may as well include dmesg from the point that the
bridge driver loads and on.
Here's dmesg from the point it starts up until it finishes printing stuff.
usb 2-10: new high speed USB device using ehci_hcd and address 22
usb 2-10: configuration #1 chosen from 1 choice
af9015_usb_probe:
af9015_identify_state: reply:01
dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in cold state, will
try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
af9015_download_firmware:
dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Leadtek Winfast DTV Dongle Gold)
af9015_eeprom_dump:
00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02
10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30
20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff
30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff
40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff
50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00
60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00
70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00
80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00
90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00
a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00
b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
af9015_read_config: xtal:2 set adc_clock:28000
af9015_read_config: tuner id1:156
af9015_read_config: spectral inversion:0
af9015_set_gpios:
af9013: firmware version:4.95.0
DVB: registering frontend 2 (Afatech AF9013 DVB-T)...
af9015_tuner_attach:
tda18271_tuner_attach:
tda18271 5-00c0: creating new instance
TDA18271HD/C1 detected @ 5-00c0
input: IR-receiver inside an USB DVB receiver as /class/input/input34
dvb-usb: schedule remote query interval to 200 msecs.
dvb-usb: Leadtek Winfast DTV Dongle Gold successfully initialized and
connected.
af9015_init:
af9015_download_ir_table:
input: Leadtek WinFast DTV Dongle Gold as /class/input/input35
input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on
usb-:00:02.1-10
This is channel 7's entry in channels.conf:
7
Digital:17750:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:513:514:1312
Jarryd,
I've analyzed the snoop that you've taken of the windows driver, and I
conclude that the driver is basically doing exactly the same that the
linux driver would do. The only thing that I cannot verify is whether
or not the tda18211 uses the same table values as the tda18271c1.
Based on the traffic in your snoop, it looks like the exact same
algorithm is used, but based on a new set of tables -- I will not be
able to confirm that without a tda18211 datasheet. The only thing
that you can do is try the tda18271 driver and hopefully it will work.
Have you tried to tune yet? There is a space in your channels.conf,
7 Digital -- you may want to change that to something like,
7Digital so that command line applications will work.
Good Luck,
Mike
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
--
http://palosaari.fi/
0023980 9bd5 0800 0001 9bd6 0800 0003 9bbe 0800
0023af0 9bd5 0800 0001 9bd6 0800 0007 d1a0 0101
0023ca0 9bd5 0800 0001 9bd6 0800 0006 9bbe 0800
0023e10 0800 0008 9bd5 0800 0001 9bd6
0023fa0 9bd5 0800 0001 9bd6 0800 0007 d1a0 0101
0024150 9bee 0100 0001 9bd5 0800 0001 9bd6
0024300 0080 9bee 0100 0001 9bd5 0800 0001 9bd6
00244d0 d73b 0103 9bd5 0800 0001 9bd6
0024670 9bd5 0800 0001 9bd6 0800 0004 d1a0 0101
0036740 9bd5 2062 29b2 0003 32d5 89d6 0001
[EMAIL PROTECTED] Files]$ hexdump -s 0x23980 -n 366 -e '1/2 { 0x%04x,
2/1 0x%02x, 1/1 0x%02x }, 1/1 \n' AF15BDA.sys
{ 0x9bd5, 0x00, 0x08, 0x01 },
{ 0x9bd6, 0x00, 0x08, 0x03 },
{ 0x9bbe, 0x00, 0x08, 0x01 },
{ 0xd1a0, 0x01, 0x01, 0x01 },
{ 0xd000, 0x00, 0x01, 0x01 },
{ 0xd000, 0x01, 0x01, 0x00 },
{ 0xd001, 0x01, 0x01, 0x01 },
{ 0xd001, 0x00, 0x01, 0x00 },
{
Re: [linux-dvb] NXP 18211HDC1 tuner
Michael Krufky wrote: On Tue, Mar 11, 2008 at 11:06 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Also when I plugged it in, it sat there for about 10 seconds before finishing loading (dmesg printed another 5 lines about the device after about 10 seconds), but still no tuning. Can I see those five lines? ;-) While you're at it, you may as well include dmesg from the point that the bridge driver loads and on. Here's dmesg from the point it starts up until it finishes printing stuff. usb 2-10: new high speed USB device using ehci_hcd and address 22 usb 2-10: configuration #1 chosen from 1 choice af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: dvb-usb: found a 'Leadtek Winfast DTV Dongle Gold' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Leadtek Winfast DTV Dongle Gold) af9015_eeprom_dump: 00: 31 c2 bb 0b 00 00 00 00 13 04 29 60 00 02 01 02 10: 00 80 00 fa fa 10 40 ef 01 30 31 30 31 30 32 30 20: 35 30 35 30 30 30 30 31 ff ff ff ff ff ff ff ff 30: 00 00 3a 01 00 08 02 00 cc 10 00 00 9c ff ff ff 40: ff ff ff ff ff 08 02 00 1d 8d c4 04 82 ff ff ff 50: ff ff ff ff ff 26 00 00 04 03 09 04 10 03 4c 00 60: 65 00 61 00 64 00 74 00 65 00 6b 00 30 03 57 00 70: 69 00 6e 00 46 00 61 00 73 00 74 00 20 00 44 00 80: 54 00 56 00 20 00 44 00 6f 00 6e 00 67 00 6c 00 90: 65 00 20 00 47 00 6f 00 6c 00 64 00 20 03 30 00 a0: 31 00 30 00 31 00 30 00 31 00 30 00 31 00 30 00 b0: 36 00 30 00 30 00 30 00 30 00 31 00 00 ff ff ff c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff af9015_read_config: xtal:2 set adc_clock:28000 af9015_read_config: tuner id1:156 af9015_read_config: spectral inversion:0 af9015_set_gpios: af9013: firmware version:4.95.0 DVB: registering frontend 2 (Afatech AF9013 DVB-T)... af9015_tuner_attach: tda18271_tuner_attach: tda18271 5-00c0: creating new instance TDA18271HD/C1 detected @ 5-00c0 input: IR-receiver inside an USB DVB receiver as /class/input/input34 dvb-usb: schedule remote query interval to 200 msecs. dvb-usb: Leadtek Winfast DTV Dongle Gold successfully initialized and connected. af9015_init: af9015_download_ir_table: input: Leadtek WinFast DTV Dongle Gold as /class/input/input35 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 This is channel 7's entry in channels.conf: 7 Digital:17750:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRAN SMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:513:514:1312 Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problems with MSI Digi VOX mini II
Hi there, I ran into problems using the MSI Digi VOX mini II (original Version, not V2.0 or V3.0) on Kubuntu 7.10. Here is a tail -f /var/run/kern.log while inserting the stick and opening Kaffeine: Mar 12 13:54:10 PBserver kernel: [ 561.467245] usb 6-5: new high speed USB device using ehci_hcd and address 6 Mar 12 13:54:10 PBserver kernel: [ 561.533991] usb 6-5: configuration #1 chosen from 1 choice Mar 12 13:54:10 PBserver kernel: [ 561.534163] dvb-usb: found a 'MSI DIGI VOX mini II DVB-T USB2.0' in cold state, will try to load a firmware Mar 12 13:54:10 PBserver kernel: [ 561.541310] dvb-usb: downloading firmware from file 'dvb-usb-digivox-02.fw' Mar 12 13:54:10 PBserver kernel: [ 561.745442] usb 6-5: USB disconnect, address 6 Mar 12 13:54:11 PBserver kernel: [ 561.861016] usb 6-5: new high speed USB device using ehci_hcd and address 7 Mar 12 13:54:11 PBserver kernel: [ 561.928714] usb 6-5: configuration #1 chosen from 1 choice Mar 12 13:54:11 PBserver kernel: [ 561.928876] dvb-usb: found a 'MSI DIGI VOX mini II DVB-T USB2.0' in warm state. Mar 12 13:54:11 PBserver kernel: [ 561.928903] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Mar 12 13:54:11 PBserver kernel: [ 561.929144] DVB: registering new adapter (MSI DIGI VOX mini II DVB-T USB2.0) Mar 12 13:54:11 PBserver kernel: [ 561.932178] DVB: registering frontend 0 (Philips TDA10046H DVB-T)... Mar 12 13:54:11 PBserver kernel: [ 561.932271] dvb-usb: MSI DIGI VOX mini II DVB-T USB2.0 successfully initialized and connected. Mar 12 13:54:27 PBserver kernel: [ 569.553799] tda1004x: setting up plls for 48MHz sampling clock Mar 12 13:54:29 PBserver kernel: [ 570.599029] tda1004x: timeout waiting for DSP ready Mar 12 13:54:29 PBserver kernel: [ 570.611871] tda1004x: found firmware revision 0 -- invalid Mar 12 13:54:29 PBserver kernel: [ 570.611876] tda1004x: trying to boot from eeprom Mar 12 13:54:31 PBserver kernel: [ 571.715696] tda1004x: timeout waiting for DSP ready Mar 12 13:54:31 PBserver kernel: [ 571.728537] tda1004x: found firmware revision 0 -- invalid Mar 12 13:54:31 PBserver kernel: [ 571.728541] tda1004x: no request function defined, can't upload from file Mar 12 13:54:31 PBserver kernel: [ 571.728543] tda1004x: firmware upload failed It seems that the stick itself ist correctly initialized, but as soon as I start a TV application, the tda1004x module outputs these error messages (it is the same with VLC). I personally think the important line is the line where the module states that no request function is defined. The firmware files dvb-fe-tda10046.fw (and dvb-fe-tda10045.fw, just to be sure) are in the correct directory (/lib/firmware/2.6.22-14-generic). I also tried the alternate Lifeview firmware. The stick is running fine under Windows XP. By the way, the stick ran under Linux, but I think it was with Kubuntu 7.04. There must be a misconfiguration in my system, but I don't know where. I tried checking out and compiling http://linuxtv.org/hg/v4l-dvb, but this does not help. Thanks in advance for your help! Greets, Bert ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
When I was having the problem, I was running 2.6.22 (vanilla ubuntu), so it doesn't appear to be related to kernel version. The fix posted a few weeks ago does seem to have stopped it for me. I said I lost a tuner recently, but I think that may have just been a loss in reception. Ben On 11 Mar 2008, at 22:37, Luis Cidoncha wrote: On Tue, Mar 11, 2008 at 11:10 PM, Nicolas Will [EMAIL PROTECTED] wrote: I'm building a kernel from the 2.6.24.2 virgin source on Ubuntu to do some testing; I'd like to prove that the problem exists in 2.6.24 proper before screaming kernel bug. But if 2.6.22 works, a bug is looking more and more likely. I'm having the losing one tuner problem on my Nova T-500 too. I'm currently running a vanilla 2.6.23.9, without USB_SUSPEND (the support for it is in the kernel, but I have it desactivated) Luis. ___ 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] Implementing support for multi-channel
-Original Message- From: Stephen Rowles [mailto:[EMAIL PROTECTED] Sent: 12 March 2008 13:20 To: Ben Backx Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] Implementing support for multi-channel Hello, I was wondering if there's some info to find on how to implement (and test) multi-channel receiving? It's possible, because dvb uses streams and the driver is currently capable to filter one channel, but how can I implement the support of multi-channel filtering? Is there perhaps an open-source driver supporting this that I can have a look at? Check out the dvbstreamer project: http://dvbstreamer.sourceforge.net/ This allows multi-channel recording / streaming if the DVB device supports sending the whole transport stream (some usb devices do not support this). This works by sending the whole transport stream to the dvbstreamer program, then this program allows filtering out and recording separate channels from that stream as required. This isn't a driver level solution, but might provide the function you need. It's (partly) for a research project, so I have to look at all possible solutions, software being one, so dvbstreamer is part of the solution :-) The others are at driver and hardware level (the hardware supports this). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On 3/12/08, Ben Firshman [EMAIL PROTECTED] wrote: When I was having the problem, I was running 2.6.22 (vanilla ubuntu), so it doesn't appear to be related to kernel version. The fix posted a few weeks ago does seem to have stopped it for me. I said I lost a tuner recently, but I think that may have just been a loss in reception. Ben On 11 Mar 2008, at 22:37, Luis Cidoncha wrote: On Tue, Mar 11, 2008 at 11:10 PM, Nicolas Will [EMAIL PROTECTED] wrote: I'm building a kernel from the 2.6.24.2 virgin source on Ubuntu to do some testing; I'd like to prove that the problem exists in 2.6.24 proper before screaming kernel bug. But if 2.6.22 works, a bug is looking more and more likely. I'm having the losing one tuner problem on my Nova T-500 too. I'm currently running a vanilla 2.6.23.9, without USB_SUSPEND (the support for it is in the kernel, but I have it desactivated) Luis. ___ 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 Could you specify which fix ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
2.6.22-14 with patches, stable for me. /Henrik On Tue, Mar 11, 2008 at 12:07 PM, [EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Looking in the kernel log I see a single mt2060 read failed message on March 6th and 9th and a single mt2060 write failed on March 8th. These events didn't cause any problems or cause the tuner or mythtv to fail though. Ivor. ___ 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] Nova-T 500 issues - losing one tuner
2008/3/12 Henrik Beckman [EMAIL PROTECTED]: 2.6.22-14 with patches, stable for me. /Henrik On Tue, Mar 11, 2008 at 12:07 PM, [EMAIL PROTECTED] wrote: Not sure if this helps or adds that much to the discussion... (I think this was concluded before) But I finally switched back to kernel 2.6.22.19 on March 5th (with current v4l-dvb code) and haven't had any problems with the Nova-t 500 since. Running mythtv with EIT scanning enabled. Looking in the kernel log I see a single mt2060 read failed message on March 6th and 9th and a single mt2060 write failed on March 8th. These events didn't cause any problems or cause the tuner or mythtv to fail though. Ivor. ___ 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 Henrik: What options (if any) are you using in modprobe.d ? Do you mean that you have patched the kernel or the v4l-dvb tree ? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Wed, Mar 5, 2008 at 12:03 AM, Ben Firshman [EMAIL PROTECTED] wrote: I am quite disappointed to report that one of my tuners has just died this evening. No error messages to speak of. Ben On 26 Feb 2008, at 19:18, Philip Pemberton wrote: Patrik Hansson wrote: Just wanted to say that I´m experiencing the same. Using latest rev (the one with patches merged) + unknown remote key patch. Ubuntu 7.10 Also having a lot of prebuffer timeout 10 times i the middle of shows. I think I might have a workaround... On Mythbuntu or one of the many Ubuntu variants, this seems to work: 1) Run: lsmod |grep usbcore 2) If step 1 produced any output that started with 'usbcore', then usbcore is loaded as a module. Perform step 3a. Otherwise, step 3b. 3a) Create a text file called /etc/modprobe.d/local-dvb (the name is fairly irrelevant). Insert one line of text into it: options usbcore autosuspend=-1 Now go to step 4. 3b) Your kernel has usbcore built in. That means you have to modify the kernel command line... Edit /boot/grub/menu.lst (you'll need to sudo to do this). Search for this line: # defoptions=quiet splash Amend it to read: # defoptions=quiet splash usbcore.autosuspend=-1 It's meant to be commented out, so leave the hash at the beginning of the line alone... Save and exit, then run ... sudo update grub Ubuntu will regenerate grub.conf, using the new kernel command line. Off to step 4 you go! If you're using a non-Debian distro (e.g. Fedora), do the same thing but edit the 'kernel' line instead. It might read: kernel /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash Change it to: kernel /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash usbcore.autosuspend=-1 4) Reboot your PC. This is a bit long-winded, but saves a kernel recompile, and a ton of messing around recompiling kernels when Ubuntu do another release. I'm working on what I consider to be a better fix, which involves using the kernel's Quirks function to disable USB suspend just for the DiBcom controllers. That is, the kernel won't try and suspend them at all... Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ 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 I just want check something i just discovered. Under /sys/module/dvb_core/parameters/ i have something called dvb_powerdown_on_sleep This i set to 1 for me. I also have one called dvb_shutdown_timeout and that is set to 0 Exactly what is it that options usbcore autosuspend=-1 controls ? I would have expected that at least one of those should be -1 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Nova-T 500 issues - losing one tuner
On Wed, Mar 12, 2008 at 9:34 PM, Patrik Hansson [EMAIL PROTECTED] wrote: On Wed, Mar 5, 2008 at 12:03 AM, Ben Firshman [EMAIL PROTECTED] wrote: I am quite disappointed to report that one of my tuners has just died this evening. No error messages to speak of. Ben On 26 Feb 2008, at 19:18, Philip Pemberton wrote: Patrik Hansson wrote: Just wanted to say that I´m experiencing the same. Using latest rev (the one with patches merged) + unknown remote key patch. Ubuntu 7.10 Also having a lot of prebuffer timeout 10 times i the middle of shows. I think I might have a workaround... On Mythbuntu or one of the many Ubuntu variants, this seems to work: 1) Run: lsmod |grep usbcore 2) If step 1 produced any output that started with 'usbcore', then usbcore is loaded as a module. Perform step 3a. Otherwise, step 3b. 3a) Create a text file called /etc/modprobe.d/local-dvb (the name is fairly irrelevant). Insert one line of text into it: options usbcore autosuspend=-1 Now go to step 4. 3b) Your kernel has usbcore built in. That means you have to modify the kernel command line... Edit /boot/grub/menu.lst (you'll need to sudo to do this). Search for this line: # defoptions=quiet splash Amend it to read: # defoptions=quiet splash usbcore.autosuspend=-1 It's meant to be commented out, so leave the hash at the beginning of the line alone... Save and exit, then run ... sudo update grub Ubuntu will regenerate grub.conf, using the new kernel command line. Off to step 4 you go! If you're using a non-Debian distro (e.g. Fedora), do the same thing but edit the 'kernel' line instead. It might read: kernel /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash Change it to: kernel /boot/vmlinuz-2.6.24-8-generic root=LABEL=/ ro quiet splash usbcore.autosuspend=-1 4) Reboot your PC. This is a bit long-winded, but saves a kernel recompile, and a ton of messing around recompiling kernels when Ubuntu do another release. I'm working on what I consider to be a better fix, which involves using the kernel's Quirks function to disable USB suspend just for the DiBcom controllers. That is, the kernel won't try and suspend them at all... Thanks, -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ 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 I just want check something i just discovered. Under /sys/module/dvb_core/parameters/ i have something called dvb_powerdown_on_sleep This i set to 1 for me. I also have one called dvb_shutdown_timeout and that is set to 0 Exactly what is it that options usbcore autosuspend=-1 controls ? I would have expected that at least one of those should be -1 .and now i see were i made my mistake (usbcore vs dvb_core) and made a fool out of myself. please disregard my last email. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Implementing support for multi-channel
It's (partly) for a research project, so I have to look at all possible solutions, software being one, so dvbstreamer is part of the solution :-) The others are at driver and hardware level (the hardware supports this). I can try to explain you what I have understood. Please anybody correct me where I am wrong. The following is true in the case of a USB card capable of passing the whole TS to the kernel. 1 tuner = only 1 frequency! The dvr is useless since it can be opened only once. You can open the demux as many times as you want. Each time you set a filter. Then you can read from them. You can filter 1) based on a PID 2) just get the whole signal 3) set a section filter case 1 and 2: you can decide whether to get the TS or PES version of the stream. I am not too sure about PES. TS is pretty easy to use. If you want to get a channel (audio + video), then you are in trouble. I can only filter 1 pid, or the whole TS. So you would need to get the whole signal from each demux and filter (audio, video, subtitles...) in your userspace application (which is a big waste!) I have tried to ask (but did not get any answer) in this list, what people think about multi pid filter, so that you can get a full channel in each demux. Hope it helps. Andrea ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] dvb fronted: LOCK but no data received.
Hi, I'd like to understand the behavior and meaning of the LOCK returned by the fronted. If I open the fronted in readonly, and ask for the INFO, it is possible that I get a LOCK but no data is actually received. This because the fronted receives data ONLY while it is opened in READ/WRITE. In dvb_frontend.c, in dvb_frontend_open, the fronted is started via dvb_frontend_start only if it opened in READ/WRITE. I see it as a misbehavior: 1) either a LOCK should NOT be returned 2) or the frontend should be started in any case (even if READ only) Which ioctl call should I use to know if the fronted is currently active? Anybody has an opinion about that? I know, I cant spell frontend properly :-), but other than that, what would be the correct behavior when opening the frontend in readonly? Andrea ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Driver source for Freecom DVB-T (with usb id 14aa:0160) v0.0.2 works
On Sun, 09 Mar 2008 23:21:17 +0100 Jan Hoogenraad [EMAIL PROTECTED] wrote: Mauro: Thanks a lot for the comments. One clear problem with this particular driver is that the code that came from RealTek does not conform to the Linux C coding style. Would that be an objection for the steps below ? Considering that RealTek won't be interested on correcting the CodingStyle, IMO, the better would be to commit RealTek code as-is, with their SOB, and then adding an additional patch, authored by somebody else could fix the CodingStyle. A very simple patch to fix CodingStyle can be created by running kernel scripts/Lindent. Unfortunately, the results of this automatic tool are not perfect, but generally are acceptable. Furthermore, can you confirm linux-dvb@linuxtv.org as the submission address for the patch ? Yes. Please C/C me also at the submission e-mail. Cheers, Mauro ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. Jarryd. What shows in dmesg during the above? -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. Jarryd. What shows in dmesg during the above? -Mike nothing new Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. Jarryd. What shows in dmesg during the above? -Mike nothing new Jarryd. Then, please turn ON debug, repeat your tests, and post again with dmesg. I am not familiar with the af9015 driver, but for tda18271, set debug=1. (you must unload all modules first -- do 'make unload' in the v4l-dvb dir, then replug your device) -Mike
Re: [linux-dvb] NXP 18211HDC1 tuner
On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:09 AM, [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 7:54 AM, Michael Krufky [EMAIL PROTECTED] wrote: On Wed, Mar 12, 2008 at 4:36 PM, Jarryd Beck [EMAIL PROTECTED] wrote: Jarryd, I've analyzed the snoop that you've taken of the windows driver, and I conclude that the driver is basically doing exactly the same that the linux driver would do. The only thing that I cannot verify is whether or not the tda18211 uses the same table values as the tda18271c1. Based on the traffic in your snoop, it looks like the exact same algorithm is used, but based on a new set of tables -- I will not be able to confirm that without a tda18211 datasheet. The only thing that you can do is try the tda18271 driver and hopefully it will work. Have you tried to tune yet? There is a space in your channels.conf, 7 Digital -- you may want to change that to something like, 7Digital so that command line applications will work. Antti Palosaari wrote: hello I looked sniffs and find correct demodulator initialization values for this NXP tuner. Copy paste correct table from attached file and try. Hopefully it works. I compared your sniff to mt2060 and qt1010 based devices and there was still some minor differences to check. regards, Antti Antti, Please remember not to top-post. Jarryd, I have done further analysis on the snoop logs. Not only is the driver using the same protocol as the tda18271 linux driver, it also seems to use the same table values as used with the tda18271c1 -- The linux driver should work on your tuner without any modification at all. Regards, Mike I've got another tuner which works, so I know I'm tuning correctly, it just doesn't actually tune. I tried with mplayer, it just sat there saying dvb_tune Freq: 21950 and did nothing. It also made my whole computer go really slow, I don't know what it was actually doing. Antti, as I said I've never done anything like this before so I have no idea what I'm doing, so I have no idea where to paste which table. Please try using tzap. This will show you FE status once every second. Let it run for a whole minute -- maybe there is some noise that may cause it to take a longer time to lock (if that's the case, then there are some tweaks that we can do.) Show us the femon output produced by running tzap. -Mike $ tzap -a 2 TEN Digital using '/dev/dvb/adapter2/frontend0' and '/dev/dvb/adapter2/demux0' tuning to 21950 Hz video pid 0x0200, audio pid 0x028a status 01 | signal | snr | ber | unc | $ femon -a 2 using '/dev/dvb/adapter2/frontend0' FE: Afatech AF9013 DVB-T (TERRESTRIAL) status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | The status 00 lines were from before I started tzap, after I started tzap it did nothing for half a minute, then printed the status 01 line, then sat there for another half a minute, and I killed it at that point. My computer was also taking quite a few seconds to respond to me pressing the keyboard for the whole time I was tuning it. Jarryd. What shows in dmesg during the above?
Re: [linux-dvb] NXP 18211HDC1 tuner
Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote: Then, please turn ON debug, repeat your tests, and post again with dmesg. I am not familiar with the af9015 driver, but for tda18271, set debug=1. (you must unload all modules first -- do 'make unload' in the v4l-dvb dir, then replug your device) Sorry I'm unsure where to set debug. You have two options. option 1) after unloading all modules, load the given module with the debug insmod option. To see the available insmod options, use modinfo. For instance, 'modinfo tda18271' will show you the tuner drivers available options. Load the driver using the option, modprobe tda18271 debug=1 ... then plug in the stick. ... option 2) set the insmod option in your boot script. I run Ubuntu... to enable debug for my tuner. i edit /etc/modprobe.d/options and add the following line: options tda18271 debug=1 ...then unload all modules, and replug the stick... or reboot your machine, then replug the stick. regards, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] MT2266 I2C write failed, usb disconnet, WinTV Nova-TD stick, remote
Bernhard Albers wrote: [ 628.492000] hub 4-0:1.0: port 9 disabled by hub (EMI?), re-enabling... [ 628.492000] usb 4-9: USB disconnect, address 2 [ 628.50] MT2266 I2C write failed [ 628.50] MT2266 I2C write failed [ 650.208000] dvb-usb: error while stopping stream. Maybe it is a problem of the mainboard. It is an Asus m2a-vm hdmi (amd690g chipset and ati x1250 onboard graphics) with the latest Bios (1604). Interesting theory... I'm seeing the same thing on a Biostar TA690G mainboard, which uses the same chipset. It works fine on my desktop machine though (VIA K8T800PRO chipset; ASUS A8V Deluxe) and on my ASUS Eee (can't remember off-hand what chipset that uses, an Intel one of some description IIRC). Had some strange signal issues with the Nova-TD-Stick too - Tuner 0 worked fine, but Tuner 1 failed to lock onto the mux that carries FilmFour. Putting a 6dB attenuator inline fixed that nicely -- seems the low-noise amplifier in the Microtune chip sets its level based on an average of the whole band it's tuned to. Lots of strong signals = low amplification = not much signal strength going into the DiBcom decoder/demux chip. Weaken some of the strong signals, and it's fine. Most peculiar. -- Phil. | (\_/) This is Bunny. Copy and paste Bunny [EMAIL PROTECTED] | (='.'=) into your signature to help him gain http://www.philpem.me.uk/ | ()_() world domination. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
status 00 | signal | snr | ber | unc | status 01 | signal | snr | ber | unc | I'm not familiar enough with the hardware and I don't know if this will help but this is the same thing I was seeing when I was getting the dvico dual digital 4 working in Australia. It wasn't a problem with the tuner but rather a sampling frequency issue with the demodulator. I'm posting this after a digest message so ignore this if you've already sorted it out. Regards, 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] STK7700-PH ( dib7700 + ConexantCX25842 + Xceive XC3028 )
Hi, i'm trying to get a AOPEN mc770a up and running. From what i can find it should be the same as a DIBCOM 7700-PH. This should contain dib7700 + ConexantCX25842 + Xceive XC3028 according to their own docs. After following this thread with some minor alterations to match my card's usbid parameters. http://thread.gmane.org/gmane.linux.drivers.dvb/39269/focus=39298 I've manged to get the card detected and it loads the driver accordings to dmesg log. (will post a full log later, currently that machine isn't running). No errors show up untill i try to tune, then i get this logged in log. dib0700: stk7700ph_xc3028_callback: XC2028_TUNER_RESET 0 xc2028 1-0061: i2c output error: rc = -5 (should be 64) xc2028 1-0061: -5 returned from send xc2028 1-0061: Error -22 while loading base firmware I traced it down to where it tries to write to the i2c address 0x61 which was setup for the XC3028. Is there any posibility that this address should be something else? If anybody has some experience with this types of card and can give me hand, let me know. Regards Joakim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] HVR-1250: detected ok but can't tune or get video
Hi all, A while back I reported I was having problems with compiling drivers for a HVR-1250. I got the drivers compiled recently using the latest source from v4l-dvb. I saw that cx23885 loaded and detected the card ok, so I tried watching video in mythtv, to no avail. I then tried dumping /dev/dvb/adaptor0/dvr0 to a file and got something 0KB in size. Also using azap, I don't get a lock... But the card seems to be loading drivers ok. the output of dmesg |grep cx gives the following: [ 1230.386126] cx23885 driver version 0.0.1 loaded [ 1230.386186] CORE cx23885[0]: subsystem: 0070:7911, board: Hauppauge WinTV-HVR1250 [card=3,autodetected] [ 1230.487835] cx23885[0]: i2c bus 0 registered [ 1230.487852] cx23885[0]: i2c bus 1 registered [ 1230.487863] cx23885[0]: i2c bus 2 registered [ 1230.514568] cx23885[0]: warning: unknown hauppauge model #0 [ 1230.514569] cx23885[0]: hauppauge eeprom: model=0 [ 1230.514571] cx23885[0]: cx23885 based dvb card [ 1230.575799] DVB: registering new adapter (cx23885[0]) [ 1230.575944] cx23885_dev_checkrevision() Hardware revision = 0xb0 [ 1230.575950] cx23885[0]/0: found at :03:00.0, rev: 2, irq: 17, latency: 0, mmio: 0xfd00 So It looks like the card should be working. However, the output of azap shows: using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 677028615 Hz video pid 0x0031, audio pid 0x0034 status 00 | signal 0082 | snr 0087 | ber | unc | status 00 | signal 0087 | snr 0087 | ber | unc | status 00 | signal 007d | snr 007d | ber | unc | status 00 | signal 0082 | snr 0082 | ber | unc | status 00 | signal 0087 | snr 0087 | ber | unc | status 00 | signal 0082 | snr 0082 | ber | unc | and so on. I never get FE_HAS_LOCK, which seems to mean that my tuner can't actually change channels or tune a particular one...? The next thing I tried was upgrading my kernel to 2.6.24, because I read that the HVR-1250 is supported in this kernel. However, still no luck, and I get the same output of azap and can't seem to watch TV. I'm stumped at this point, can anyone see what I'm doing wrong? Cheers, Raphael ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] NXP 18211HDC1 tuner
On Thu, Mar 13, 2008 at 10:11 AM, Antti Palosaari [EMAIL PROTECTED] wrote: Jarryd Beck wrote: On Thu, Mar 13, 2008 at 8:14 AM, [EMAIL PROTECTED] wrote: Then, please turn ON debug, repeat your tests, and post again with dmesg. I am not familiar with the af9015 driver, but for tda18271, set debug=1. (you must unload all modules first -- do 'make unload' in the v4l-dvb dir, then replug your device) -Mike Sorry I'm unsure where to set debug. Jarryd. I added initial support for this tda-tuner to the driver. Jarryd, can you test? http://linuxtv.org/hg/~anttip/af9015_new/ There is debug switch in af9013 module that may be helpful if it does not work. You can enable it as described or if it is too hard to play with modprobe just edit af9013.c file in frontend directory and set debug=1 by hard coding. If it does not work you can also try set GPIO3 setting (af9015) to 0xb instead 0x3 used currently. Also try to change rf-spectral inversion to see if it helps. Firmware should be ok and all other settings as well as I can see from usb-sniffs. With little lucky it should start working. regards Antti -- http://palosaari.fi/ Thanks, but now for some reason all I get is this: usb 2-10: new high speed USB device using ehci_hcd and address 6 usb 2-10: configuration #1 chosen from 1 choice input: Leadtek WinFast DTV Dongle Gold as /class/input/input8 input: USB HID v1.01 Keyboard [Leadtek WinFast DTV Dongle Gold] on usb-:00:02.1-10 af9015_usb_probe: af9015_identify_state: reply:01 dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw' af9015_download_firmware: usbcore: registered new interface driver dvb_usb_af9015 Jarryd. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HVR-1250: detected ok but can't tune or get video
On Wed, Mar 12, 2008 at 8:51 PM, raphy [EMAIL PROTECTED] wrote: Hi all, A while back I reported I was having problems with compiling drivers for a HVR-1250. I got the drivers compiled recently using the latest source from v4l-dvb. I saw that cx23885 loaded and detected the card ok, so I tried watching video in mythtv, to no avail. I then tried dumping /dev/dvb/adaptor0/dvr0 to a file and got something 0KB in size. Also using azap, I don't get a lock... But the card seems to be loading drivers ok. the output of dmesg |grep cx gives the following: [ 1230.386126] cx23885 driver version 0.0.1 loaded [ 1230.386186] CORE cx23885[0]: subsystem: 0070:7911, board: Hauppauge WinTV-HVR1250 [card=3,autodetected] [ 1230.487835] cx23885[0]: i2c bus 0 registered [ 1230.487852] cx23885[0]: i2c bus 1 registered [ 1230.487863] cx23885[0]: i2c bus 2 registered [ 1230.514568] cx23885[0]: warning: unknown hauppauge model #0 [ 1230.514569] cx23885[0]: hauppauge eeprom: model=0 [ 1230.514571] cx23885[0]: cx23885 based dvb card [ 1230.575799] DVB: registering new adapter (cx23885[0]) [ 1230.575944] cx23885_dev_checkrevision() Hardware revision = 0xb0 [ 1230.575950] cx23885[0]/0: found at :03:00.0, rev: 2, irq: 17, latency: 0, mmio: 0xfd00 So It looks like the card should be working. However, the output of azap shows: using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 677028615 Hz video pid 0x0031, audio pid 0x0034 status 00 | signal 0082 | snr 0087 | ber | unc | status 00 | signal 0087 | snr 0087 | ber | unc | status 00 | signal 007d | snr 007d | ber | unc | status 00 | signal 0082 | snr 0082 | ber | unc | status 00 | signal 0087 | snr 0087 | ber | unc | status 00 | signal 0082 | snr 0082 | ber | unc | and so on. I never get FE_HAS_LOCK, which seems to mean that my tuner can't actually change channels or tune a particular one...? The next thing I tried was upgrading my kernel to 2.6.24, because I read that the HVR-1250 is supported in this kernel. However, still no luck, and I get the same output of azap and can't seem to watch TV. I'm stumped at this point, can anyone see what I'm doing wrong? Cheers, Raphael Ok, scratch that It looks like I forgot that the included antenna with this card is a total piece of junk. Everything was working fine; I just needed to replace the antenna with one that came with a usb tuner and suddenly I could lock and view TV, etc. I should have known better on this one. Cheers, Raphael ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Trying to setup PCTV HD Card 800i
Alright, here is the new dmesg output http://pastebin.com/m35d1137d. Brandon On Tue, Mar 11, 2008 at 8:11 AM, Chaogui Zhang [EMAIL PROTECTED] wrote: On Tue, Mar 11, 2008 at 3:36 AM, Brandon Rader [EMAIL PROTECTED] wrote: I tried the different repo that you suggested, and get the same error. Here is my new dmesg output http://pastebin.com/m4d43d4ef Brandon Please do not drop the list from the cc. Use the reply to all function of your email client instead of just reply. It seems the i2c bus is not working the way it should. Can you try the following? (With the current v4l-dvb tree) First, unload all the modules related to your card (cx88-*, s5h1409, xc5000). Then, load cx88xx with options i2c_debug=1 and i2c_scan=1 Post the relevant dmesg output to the list. -- Chaogui Zhang ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem with lspci and PCIe slots - HVR-1800 not seen
I just put my new HVR-1800 in and restarted and found lspci dosen't see it. I have not redone drivers yet. They are still built only for the Nexus. I have searched all the logs for ref to the chip used, but nothing. Google came back with a lot of people having problems with lspci and PCIe cards. Some mis-named, some not showing at all. Going ahead with trying to build multiproto drivers and se what happens ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
