[linux-dvb] Re: Nebula DigiTV and nxt6000 problems

["Robert Cook" <robert@softek.com.au>]

tzap never locks onto the Nebula, the AVerTV is fine. Same channels
file, signal is good (it passes through the Nebula to the AVerTV, also
works under Windows). Lights are on but nobody at home.

# tzap -c channels.conf "nine digital"
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 191625000 Hz
video pid 0x0201, audio pid 0x0294
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 0000 | snr 0000 | ber 00000000 | unc 00000000 |

# tzap -a 1 -c channels.conf "nine digital"
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
tuning to 191625000 Hz
video pid 0x0201, audio pid 0x0294
status 01 | signal ffff | snr ae3a | ber ffffffff | unc ffffffff |
status 1f | signal ffff | snr b2cb | ber 0000002a | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr b27b | ber 00000022 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr b15b | ber 0000001c | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr b15b | ber 0000002b | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr b15b | ber 0000002f | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr b37b | ber 0000003b | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr ad9a | ber 00000028 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal ffff | snr ad3a | ber 00000020 | unc 00000000 |
FE_HAS_LOCK


-----Original Message-----
From: linux-dvb-bounce@linuxtv.org [mailto:linux-dvb-bounce@linuxtv.org]
On Behalf Of Holger Waechtler
Sent: Tuesday, 27 January 2004 9:09 PM
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Re: Nebula DigiTV and nxt6000 problems


Robert Cook wrote:
> How do I identify what tuner type I physically have? Here is the 
> output the debug=1

looks fine so far. The first three I/O errors are generated by the demod

probing at adresses 0x18, 0x24 and 0x28 (your demod is located at 0x14),

the second 4 errors are caused by the probing on the Avermedia i2c bus. 
Everything alright and logical.

Have you tried to zap a little around on both frontend devices using 
e.g. tzap? Please do so and if it does not works please post the kernel 
logs. For the Avermedia card you need to load the sp887x driver.

Holger



> #dmesg
> Linux video capture interface: v1.00
> bttv: driver version 0.9.12 loaded
> bttv: snapshot date 2004-01-21
> bttv: using 4 buffers with 2080k (520 pages) each for capture
> bttv: Bt8xx card found (0).
> bttv0: Bt878 (rev 17) at 02:0b.0, irq: 23, latency: 64, mmio: 
> 0xfbefc000
> bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem
ID
> is 0071:0101
> bttv0: using: Nebula Electronics DigiTV [card=104,insmod option]
> bttv0: gpio: en=00000000, out=00000000 in=00ff37cb [init]
> bttv0: using tuner=-1
> bttv0: registered device video0
> bttv0: registered device vbi0
> bttv0: PLL: 28636363 => 35468950 .. ok
> bttv: Bt8xx card found (1).
> bttv1: Bt878 (rev 17) at 02:0a.0, irq: 22, latency: 64, mmio:
0xfbefe000
> bttv1: subsystem: 1461:0761 (UNKNOWN)
> please mail id, board name and the correct card= insmod option to
> kraxel@bytesex.org
> bttv1: using:  *** UNKNOWN/GENERIC ***  [card=0,autodetected]
> bttv1: gpio: en=00000000, out=00000000 in=009c004d [init]
> bttv1: using tuner=-1
> bttv1: i2c: checking for MSP34xx @ 0x80... not found
> bttv1: i2c: checking for TDA9875 @ 0xb0... not found
> bttv1: i2c: checking for TDA7432 @ 0x8a... not found
> bttv1: registered device video1
> bttv1: registered device vbi1
> bt878: AUDIO driver version 0.0.0 loaded
> bt878: Bt878 AUDIO function found (0).
> bt878(0): Bt878 (rev 17) at 02:0b.1, irq: 23, latency: 64, memory:
> 0xfbefd000
> bt878: Bt878 AUDIO function found (1).
> bt878(1): Bt878 (rev 17) at 02:0a.1, irq: 22, latency: 64, memory:
> 0xfbeff000
> DVB: registering new adapter (Neb).
> DVB: registering new adapter (Ave).
> nxt6000: init
> nxt6000: attach
> nxt6000: detected TI ALP510 tuner at 0xC0
> nxt6000: attached at 0:0
> DVB: registering frontend 0:0 (NxtWave NXT6000)...
> nxt6000: nxt6000_read error (.addr = 0x18, reg: 0x73, ret: -5)
> nxt6000: nxt6000_read error (.addr = 0x24, reg: 0x73, ret: -5)
> nxt6000: nxt6000_read error (.addr = 0x28, reg: 0x73, ret: -5)
> nxt6000: attach
> nxt6000: nxt6000_read error (.addr = 0x14, reg: 0x73, ret: -5)
> nxt6000: nxt6000_read error (.addr = 0x18, reg: 0x73, ret: -5)
> nxt6000: nxt6000_read error (.addr = 0x24, reg: 0x73, ret: -5)
> nxt6000: nxt6000_read error (.addr = 0x28, reg: 0x73, ret: -5)
> 
> Robert
> 
> -----Original Message-----
> From: linux-dvb-bounce@linuxtv.org 
> [mailto:linux-dvb-bounce@linuxtv.org]
> On Behalf Of Holger Waechtler
> Sent: Tuesday, 27 January 2004 1:07 AM
> To: linux-dvb@linuxtv.org
> Subject: [linux-dvb] Re: Nebula DigiTV and nxt6000 problems
> 
> 
> Robert Cook wrote:
> 
>>Look like the driver is loading and registering the frontend but no
>>joy using ztap.
>>
>>Robert
>>
>>#dmesg
>>i2c-core.o: i2c core module version 2.8.1 (20031005)
>>Linux video capture interface: v1.00
>>bttv: driver version 0.9.12 loaded
>>bttv: snapshot date 2004-01-21
>>bttv: using 4 buffers with 2080k (520 pages) each for capture
>>bttv: Bt8xx card found (0).
>>bttv0: Bt878 (rev 17) at 02:0b.0, irq: 23, latency: 64, mmio:
>>0xfbefc000
>>bttv0: detected: Nebula Electronics DigiTV [card=104], PCI subsystem
> 
> ID
> 
>>is 0071:0101
>>bttv0: using: Nebula Electronics DigiTV [card=104,insmod option]
>>bttv0: gpio: en=00000000, out=00000000 in=00ff48cb [init]
>>bttv0: using tuner=-1
>>bttv0: registered device video0
>>bttv0: registered device vbi0
>>bttv0: PLL: 28636363 => 35468950 .. ok
>>bttv: Bt8xx card found (1).
>>bttv1: Bt878 (rev 17) at 02:0a.0, irq: 22, latency: 64, mmio:
> 
> 0xfbefe000
> 
>>bttv1: subsystem: 1461:0761 (UNKNOWN)
>>please mail id, board name and the correct card= insmod option to 
>>kraxel@bytesex.org
>>bttv1: using:  *** UNKNOWN/GENERIC ***  [card=0,autodetected]
>>bttv1: gpio: en=00000000, out=00000000 in=009c004d [init]
>>bttv1: using tuner=-1
>>bttv1: i2c: checking for MSP34xx @ 0x80... not found
>>bttv1: i2c: checking for TDA9875 @ 0xb0... not found
>>bttv1: i2c: checking for TDA7432 @ 0x8a... not found
>>bttv1: registered device video1
>>bttv1: registered device vbi1
>>bt878: AUDIO driver version 0.0.0 loaded
>>bt878: Bt878 AUDIO function found (0).
>>bt878(0): Bt878 (rev 17) at 02:0b.1, irq: 23, latency: 64, memory: 
>>0xfbefd000
>>bt878: Bt878 AUDIO function found (1).
>>bt878(1): Bt878 (rev 17) at 02:0a.1, irq: 22, latency: 64, memory: 
>>0xfbeff000
>>DVB: registering new adapter (Neb).
>>DVB: registering new adapter (Ave).
>>DVB: registering frontend 0:0 (NxtWave NXT6000)...
> 
> 
> Can you please load the nxt6000.o module with parameter debug=1? Then
> you get a message which should tell you what tunertype is used. Please

> check that this is the right one.
> 
> Holger
> 
> 
> 




-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe
linux-dvb" as subject.




-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.