Re: [linux-dvb] Nova-S-Plus Locking Issues

[Dwaine Garden]

Solar Storm???   8*)



Dark Dragon <[EMAIL PROTECTED]> wrote: 

 Problem is i can no longer ESTABLISH a lock at all.  It simply stays at status 
01!
  
 I know ther ewere some Voltage problems with the cards, but it will not lock H 
or V at all.  Any way to what is going on?!?!!?

 
  On 1/4/08, Dwaine Garden <[EMAIL PROTECTED] > wrote:  I'm getting the same 
results.  Working on the digiwave 108g card.  So I bought another card the 
Digiwave 103g.   The existing 103g which has been in the kernel for a while, is 
getting the same problem that you are experiencing.  It keeps losing the lock 
while scanning for channels.  

Must be a patch that was pushed to the kernel v4l/dvb tree.  Been smashing my 
head against the wall (4 days) until about an hour ago when I started playing 
around with the 103g card and getting the same issue.
 
I'm running knoppmyth with kernel 2.6.18 with v4l/dvb updates from the 2.6.22 
kernel.  The other box is running 2.6.24-0.123.rc6.fc9 with today v4l/dvb tree 
from HG.

Finds the satellites, locks, scan loses lock.  

Dark Dragon <[EMAIL PROTECTED]> wrote:
   I have been fiddling with this set up for some time.  
 I have a Nova-S-Plus in a P4 1.7 running Fedora Core 6
  
 When i first got it running everythign worked great.  Tried it with 1 lnb. Got 
Good Signal, Good Locks and channels Scanned.
 The kernel that comes with Fedora Core 6 is 2.6.18-1.2798
  
 Apperntly there are problems with diseqc, so i decided before moving to a 
deseqc i shouls try upgradeing the kernel.
 I tried pulling linux tv hg but it would not compile under that kernel.
  
 I updated to kernel 2.6.20-1.2948 from the repositories. I noticed after this 
kernel was loaded that my card would no longer lock. I saw that the Signal had 
fallen, previously grater then ff00 now at 6800 and less.I  also noticed the 
quality was irratic.
 When downgrading to 2.6.18 i found the card would once again lock. 
  
 Fianlly i tried upgrading and pulling the latest HG drivers, but found myself 
in the same position.  Can some one please shine some light on this.
  
 DMESG:
 Linux video capture interface: v2.00
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S 
[card=37,autodetected]
cx88[0]: TV tuner type 4, Radio tuner type -1  
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
tveeprom 1-0050: Hauppauge model 92001, rev B1B1, serial# 295008
tveeprom 1-0050: MAC address is 00-0D-FE-04-80-60
tveeprom 1-0050: tuner model is Conexant_CX24109 (idx 111, type 4)  
tveeprom 1-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
tveeprom 1-0050: audio processor is CX883 (idx 32)
tveeprom 1-0050: decoder processor is CX883 (idx 22)
tveeprom 1-0050: has no radio, has IR receiver, has no IR transmitter  
cx88[0]: hauppauge eeprom: model=92001
input: cx88 IR (Hauppauge Nova-S-Plus  as /class/input/input3
cx88[0]/2: cx2388x 8802 Driver Manager
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered  
ACPI: PCI Interrupt :00:09.2[A] -> Link [LNKB] -> GSI 10 (level, low) -> 
IRQ 10
cx88[0]/2: found at :00:09.2, rev: 5, irq: 10, latency: 32, mmio: 0xe300
ACPI: PCI Interrupt :00:09.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> 
IRQ 10  
cx88[0]/0: found at :00:09.0, rev: 5, irq: 10, latency: 32, mmio: 0xe500
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88/2: cx2388x dvb driver version 0.0.6 loaded
 cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S [card=37]
cx88[0]/2: cx2388x based DVB/ATSC card
DVB: registering new adapter (cx88[0])  
DVB: registering frontend 0 (Conexant CX24123/CX24109)...
 
 LSPCI:
  00:09.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and 
Audio Decoder (rev 05)
Subsystem: Hauppauge computer works Inc. Nova-S-Plus DVB-S
Flags: bus master, medium devsel, latency 32, IRQ 10  
Memory at e500 (32-bit, non-prefetchable) [size=16M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
 00:09.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [Audio Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10  
Memory at e400 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
 00:09.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [MPEG Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10  
Memory at e300 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
 00:09.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [IR Port] (rev 05)
Sub

[linux-dvb] Nova-S-Plus Locking Issues

[Dark Dragon]

Problem is i can no longer ESTABLISH a lock at all.  It simply stays at
status 01!

I know ther ewere some Voltage problems with the cards, but it will not lock
H or V at all.  Any way to what is going on?!?!!?


 On 1/4/08, Dwaine Garden <[EMAIL PROTECTED]> wrote:
>
> I'm getting the same results.  Working on the digiwave 108g card.  So I
> bought another card the Digiwave 103g.   The existing 103g which has been in
> the kernel for a while, is getting the same problem that you are
> experiencing.  It keeps losing the lock while scanning for channels.
>
> Must be a patch that was pushed to the kernel v4l/dvb tree.  Been smashing
> my head against the wall (4 days) until about an hour ago when I started
> playing around with the 103g card and getting the same issue.
>
> I'm running knoppmyth with kernel 2.6.18 with v4l/dvb updates from the
> 2.6.22 kernel.  The other box is running 2.6.24-0.123.rc6.fc9 with today
> v4l/dvb tree from HG.
>
> Finds the satellites, locks, scan loses lock.
>
> *Dark Dragon <[EMAIL PROTECTED]>* wrote:
>
>  I have been fiddling with this set up for some time.
> I have a Nova-S-Plus in a P4 1.7 running Fedora Core 6
>
> When i first got it running everythign worked great.  Tried it with 1 lnb.
> Got Good Signal, Good Locks and channels Scanned.
> The kernel that comes with Fedora Core 6 is 2.6.18-1.2798
>
> Apperntly there are problems with diseqc, so i decided before moving to a
> deseqc i shouls try upgradeing the kernel.
> I tried pulling linux tv hg but it would not compile under that kernel.
>
> I updated to kernel 2.6.20-1.2948 from the repositories. I noticed after
> this kernel was loaded that my card would no longer lock. I saw that the
> Signal had fallen, previously grater then ff00 now at 6800 and less.I also
> noticed the quality was irratic.
> When downgrading to 2.6.18 i found the card would once again lock.
>
> Fianlly i tried upgrading and pulling the latest HG drivers, but found
> myself in the same position.  Can some one please shine some light on this.
>
> DMESG:
> Linux video capture interface: v2.00
> cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
> cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S
> [card=37,autodetected]
> cx88[0]: TV tuner type 4, Radio tuner type -1
> cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
> tveeprom 1-0050: Hauppauge model 92001, rev B1B1, serial# 295008
> tveeprom 1-0050: MAC address is 00-0D-FE-04-80-60
> tveeprom 1-0050: tuner model is Conexant_CX24109 (idx 111, type 4)
> tveeprom 1-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
> tveeprom 1-0050: audio processor is CX883 (idx 32)
> tveeprom 1-0050: decoder processor is CX883 (idx 22)
> tveeprom 1-0050: has no radio, has IR receiver, has no IR transmitter
> cx88[0]: hauppauge eeprom: model=92001
> input: cx88 IR (Hauppauge Nova-S-Plus  as /class/input/input3
> cx88[0]/2: cx2388x 8802 Driver Manager
> ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
> PCI: setting IRQ 10 as level-triggered
> ACPI: PCI Interrupt :00:09.2[A] -> Link [LNKB] -> GSI 10 (level, low)
> -> IRQ 10
> cx88[0]/2: found at :00:09.2, rev: 5, irq: 10, latency: 32, mmio:
> 0xe300
> ACPI: PCI Interrupt :00:09.0[A] -> Link [LNKB] -> GSI 10 (level, low)
> -> IRQ 10
> cx88[0]/0: found at :00:09.0, rev: 5, irq: 10, latency: 32, mmio:
> 0xe500
> cx88[0]/0: registered device video0 [v4l2]
> cx88[0]/0: registered device vbi0
> cx88/2: cx2388x dvb driver version 0.0.6 loaded
> cx88/2: registering cx8802 driver, type: dvb access: shared
> cx88[0]/2: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S
> [card=37]
> cx88[0]/2: cx2388x based DVB/ATSC card
> DVB: registering new adapter (cx88[0])
> DVB: registering frontend 0 (Conexant CX24123/CX24109)...
>
> LSPCI:
>  00:09.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and
> Audio Decoder (rev 05)
> Subsystem: Hauppauge computer works Inc. Nova-S-Plus DVB-S
> Flags: bus master, medium devsel, latency 32, IRQ 10
> Memory at e500 (32-bit, non-prefetchable) [size=16M]
> Capabilities: [44] Vital Product Data
> Capabilities: [4c] Power Management version 2
> 00:09.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio
> Decoder [Audio Port] (rev 05)
> Subsystem: Hauppauge computer works Inc. Unknown device 9202
> Flags: bus master, medium devsel, latency 32, IRQ 10
> Memory at e400 (32-bit, non-prefetchable) [size=16M]
> Capabilities: [4c] Power Management version 2
> 00:09.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio
> Decoder [MPEG Port] (rev 05)
> Subsystem: Hauppauge computer works Inc. Unknown device 9202
> Flags: bus master, medium devsel, latency 32, IRQ 10
> Memory at e300 (32-bit, non-prefetchable) [size=16M]
> Capabilities: [4c] Power Management version 2
> 00:09.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio
> Deco

Re: [linux-dvb] Nova-S-Plus Locking Issues

[Dwaine Garden]

I'm getting the same results.  Working on the digiwave 108g card.  So I bought 
another card the Digiwave 103g.   The existing 103g which has been in the 
kernel for a while, is getting the same problem that you are experiencing.  It 
keeps losing the lock while scanning for channels.

Must be a patch that was pushed to the kernel v4l/dvb tree.  Been smashing my 
head against the wall (4 days) until about an hour ago when I started playing 
around with the 103g card and getting the same issue.

I'm running knoppmyth with kernel 2.6.18 with v4l/dvb updates from the 2.6.22 
kernel.  The other box is running 2.6.24-0.123.rc6.fc9 with today v4l/dvb tree 
from HG.

Finds the satellites, locks, scan loses lock.

Dark Dragon <[EMAIL PROTECTED]> wrote: I have been fiddling with this set up 
for some time.  
 I have a Nova-S-Plus in a P4 1.7 running Fedora Core 6
  
 When i first got it running everythign worked great.  Tried it with 1 lnb. Got 
Good Signal, Good Locks and channels Scanned.
 The kernel that comes with Fedora Core 6 is 2.6.18-1.2798
  
 Apperntly there are problems with diseqc, so i decided before moving to a 
deseqc i shouls try upgradeing the kernel.
 I tried pulling linux tv hg but it would not compile under that kernel.
  
 I updated to kernel 2.6.20-1.2948 from the repositories. I noticed after this 
kernel was loaded that my card would no longer lock. I saw that the Signal had 
fallen, previously grater then ff00 now at 6800 and less.I  also noticed the 
quality was irratic.
 When downgrading to 2.6.18 i found the card would once again lock. 
  
 Fianlly i tried upgrading and pulling the latest HG drivers, but found myself 
in the same position.  Can some one please shine some light on this.
  
 DMESG:
 Linux video capture interface: v2.00
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S 
[card=37,autodetected]
cx88[0]: TV tuner type 4, Radio tuner type -1 
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
tveeprom 1-0050: Hauppauge model 92001, rev B1B1, serial# 295008
tveeprom 1-0050: MAC address is 00-0D-FE-04-80-60
tveeprom 1-0050: tuner model is Conexant_CX24109 (idx 111, type 4) 
tveeprom 1-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
tveeprom 1-0050: audio processor is CX883 (idx 32)
tveeprom 1-0050: decoder processor is CX883 (idx 22)
tveeprom 1-0050: has no radio, has IR receiver, has no IR transmitter 
cx88[0]: hauppauge eeprom: model=92001
input: cx88 IR (Hauppauge Nova-S-Plus  as /class/input/input3
cx88[0]/2: cx2388x 8802 Driver Manager
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered 
ACPI: PCI Interrupt :00:09.2[A] -> Link [LNKB] -> GSI 10 (level, low) -> 
IRQ 10
cx88[0]/2: found at :00:09.2, rev: 5, irq: 10, latency: 32, mmio: 0xe300
ACPI: PCI Interrupt :00:09.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> 
IRQ 10 
cx88[0]/0: found at :00:09.0, rev: 5, irq: 10, latency: 32, mmio: 0xe500
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88/2: cx2388x dvb driver version 0.0.6 loaded
 cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S [card=37]
cx88[0]/2: cx2388x based DVB/ATSC card
DVB: registering new adapter (cx88[0]) 
DVB: registering frontend 0 (Conexant CX24123/CX24109)...
 
 LSPCI:
  00:09.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and 
Audio Decoder (rev 05)
Subsystem: Hauppauge computer works Inc. Nova-S-Plus DVB-S
Flags: bus master, medium devsel, latency 32, IRQ 10 
Memory at e500 (32-bit, non-prefetchable) [size=16M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2
 00:09.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [Audio Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10 
Memory at e400 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
 00:09.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [MPEG Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10 
Memory at e300 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2
 00:09.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio 
Decoder [IR Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10 
Memory at e200 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2

  
 SZAP ATTEMPT
 [EMAIL PROTECTED] szap]# ./szap -l DBS CHAN01
reading channels from file '/root/.szap/channels.conf'

[linux-dvb] Nova-S-Plus Locking Issues

[Dark Dragon]

I have been fiddling with this set up for some time.
I have a Nova-S-Plus in a P4 1.7 running Fedora Core 6

When i first got it running everythign worked great.  Tried it with 1 lnb.
Got Good Signal, Good Locks and channels Scanned.
The kernel that comes with Fedora Core 6 is 2.6.18-1.2798

Apperntly there are problems with diseqc, so i decided before moving to a
deseqc i shouls try upgradeing the kernel.
I tried pulling linux tv hg but it would not compile under that kernel.

I updated to kernel 2.6.20-1.2948 from the repositories. I noticed after
this kernel was loaded that my card would no longer lock. I saw that the
Signal had fallen, previously grater then ff00 now at 6800 and less.I also
noticed the quality was irratic.
When downgrading to 2.6.18 i found the card would once again lock.

Fianlly i tried upgrading and pulling the latest HG drivers, but found
myself in the same position.  Can some one please shine some light on this.

DMESG:
Linux video capture interface: v2.00
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S
[card=37,autodetected]
cx88[0]: TV tuner type 4, Radio tuner type -1
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
tveeprom 1-0050: Hauppauge model 92001, rev B1B1, serial# 295008
tveeprom 1-0050: MAC address is 00-0D-FE-04-80-60
tveeprom 1-0050: tuner model is Conexant_CX24109 (idx 111, type 4)
tveeprom 1-0050: TV standards ATSC/DVB Digital (eeprom 0x80)
tveeprom 1-0050: audio processor is CX883 (idx 32)
tveeprom 1-0050: decoder processor is CX883 (idx 22)
tveeprom 1-0050: has no radio, has IR receiver, has no IR transmitter
cx88[0]: hauppauge eeprom: model=92001
input: cx88 IR (Hauppauge Nova-S-Plus  as /class/input/input3
cx88[0]/2: cx2388x 8802 Driver Manager
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt :00:09.2[A] -> Link [LNKB] -> GSI 10 (level, low) ->
IRQ 10
cx88[0]/2: found at :00:09.2, rev: 5, irq: 10, latency: 32, mmio:
0xe300
ACPI: PCI Interrupt :00:09.0[A] -> Link [LNKB] -> GSI 10 (level, low) ->
IRQ 10
cx88[0]/0: found at :00:09.0, rev: 5, irq: 10, latency: 32, mmio:
0xe500
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88/2: cx2388x dvb driver version 0.0.6 loaded
cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S
[card=37]
cx88[0]/2: cx2388x based DVB/ATSC card
DVB: registering new adapter (cx88[0])
DVB: registering frontend 0 (Conexant CX24123/CX24109)...

LSPCI:

00:09.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and
Audio Decoder (rev 05)
Subsystem: Hauppauge computer works Inc. Nova-S-Plus DVB-S
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e500 (32-bit, non-prefetchable) [size=16M]
Capabilities: [44] Vital Product Data
Capabilities: [4c] Power Management version 2

00:09.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio
Decoder [Audio Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e400 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2

00:09.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio
Decoder [MPEG Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e300 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2

00:09.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio
Decoder [IR Port] (rev 05)
Subsystem: Hauppauge computer works Inc. Unknown device 9202
Flags: bus master, medium devsel, latency 32, IRQ 10
Memory at e200 (32-bit, non-prefetchable) [size=16M]
Capabilities: [4c] Power Management version 2



SZAP ATTEMPT

[EMAIL PROTECTED] szap]# ./szap -l DBS CHAN01
reading channels from file '/root/.szap/channels.conf'
zapping to 151 'CHAN01':
sat 0, frequency = 12442 MHz H, symbolrate 2000, vpid = 0x1321, apid =
0x1322
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 01 | signal 6800 | snr a2c2 | ber  | unc fffe |
status 01 | signal 5b00 | snr a2dc | ber  | unc fffe |
status 01 | signal 5b00 | snr a284 | ber  | unc fffe |
status 01 | signal 5b00 | snr a3c0 | ber  | unc fffe |
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] New / Corrected Initial scan file se-Karlstad_Sormon

[Simon G]

Hi,

After some investigations a new corrected scan file is attached for
Karlstad, Sweden DVB-T transmitter. The FEC values were incorrect thanks
to incorrect NIT (PID 0x0010) data.

Yours

Simon G.



se-Karlstad_Sormon
Description: Binary data
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] scan command returning wrong FEC if wrong NIT info. se-Karlstad mux now fixed.

[Simon G]

It appears that the scan command (regarding dvb-t at least) is reading the
0x0010 PID (NIT) to return the FEC values instead of getting them from the
tuner frontend. Maybe it was easier this way. Anyway I noticed this as my
channels.conf generated by the scan command wasn't working for me.

It turned out that the NIT PID(Network Information) was sending the wrong
info from the Karlstad transmitter. I contacted them about it and
amazingly they fixed the problem! Thanks to Teracom (The Swedish
transmission authority).

Anyway it appears that the NIT is only meant as information and that most
tuners can discover the FEC rates themselves. So it can be a good tip to
try changing your generated channels.conf to FEC_NONE or FEC_AUTO if your
having problems.


/Simon.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Digiwave 108G/GeniaTech TVStar Card - Adding it to the CX88 Driver

[hermann pitton]

Hi,

Am Donnerstag, den 03.01.2008, 06:50 -0500 schrieb Dwaine Garden:
> Oppsss.  The chip is actually "TDB2028E3".  So we know that the chip
> is actually a silicon TV Tuner.

sorry, don't know yet what this should be. The XCeive tuners have 48
pins and the known ones are clearly marked.

> Looking at the Windows INF file, it does list a lot of  Xceive
> references.  Too bad it was not marked as "TDA", then we could assume
> it was a Phillips Silicon TV Tuner.

The Philips/NXP tuner(s)=54 have good autodetection capabilities and are
also easily to identify, if visible.

> Examples
> 
> [CX23880.Xceive.NT] 
> Include=ks.inf, kscaptur.inf, ksfilter.inf, wdmaudio.inf, bda.inf 
> Needs=
> KS.Registration,KSCAPTUR.Registration.NT,MSPCLOCK.Installation,WDMAUDIO.Registration,BDA.Registration,bda.Installation.NT
>  
> AddReg= CX880.AddReg,Xceive.AddReg,XBAR.AddReg 
> CopyFiles=  CX880.CopyDrivers,DSFilters.CopyFiles 
> RegisterDlls=DSFilters.RegDLL 
>  
> [CX23880.XceiveZarlink.NT] 
> Include=ks.inf, kscaptur.inf, ksfilter.inf, wdmaudio.inf, bda.inf 
> Needs=
> KS.Registration,KSCAPTUR.Registration.NT,MSPCLOCK.Installation,WDMAUDIO.Registration,BDA.Registration,bda.Installation.NT
>  
> AddReg= CX880.AddReg,XceiveZarlink.AddReg,XBAR.AddReg,CXTS.AddReg 
> CopyFiles=  CX880.CopyDrivers,DSFilters.CopyFiles 
> RegisterDlls=DSFilters.RegDLL 
>  
> [CX23880.XceiveConexant.NT] 
> Include=ks.inf, kscaptur.inf, ksfilter.inf, wdmaudio.inf, bda.inf 
> Needs=
> KS.Registration,KSCAPTUR.Registration.NT,MSPCLOCK.Installation,WDMAUDIO.Registration,BDA.Registration,bda.Installation.NT
>  
> AddReg=
> CX880.AddReg,XceiveConexant.AddReg,XBAR.AddReg,CXTS.AddReg 
> CopyFiles=  CX880.CopyDrivers,DSFilters.CopyFiles 
> RegisterDlls=DSFilters.RegDLL 
> 
> Still have not got anything off the dvb frontend.  It's also getting
> confused with the voltage for the LNB.

Don't know how this is wired on your card. On the ISL6421 LNB control
chips the voltage can be set by some gpio switching or by i2c and most
likely by both too, if wired like that. (32pins square package)

The gpio switching can come from everywhere. Since you have already
voltage, I would call this good progress. Did you measure it?

Else, the current status of the older supported Geniatech DVB-S card is
not clear to me. On the HVR4000 is advanced DiSEqC progress now.

The early patches by Vadim Catana for the KWorld DVB-S 100 might be
helpfull too.

Cheers,
Hermann

> Jan  3 06:24:17 mythtv kernel: LNB Voltage On.
> Jan  3 06:24:17 mythtv kernel: cx24123_set_voltage: setting voltage
> 18V
> Jan  3 06:24:18 mythtv kernel: cx24123_read_signal_strength:  Signal
> strength = 5120
> Jan  3 06:24:18 mythtv kernel: cx24123_read_snr:  read S/N index = 0
> Jan  3 06:25:01 mythtv kernel: LNB Voltage OFF.
> Jan  3 06:25:01 mythtv kernel: Voltage Not Set Properly
> Jan  3 06:25:14 mythtv kernel: LNB Voltage On.
> Jan  3 06:25:14 mythtv kernel: cx24123_set_voltage: setting voltage
> 18V
> Jan  3 06:25:15 mythtv kernel: cx24123_read_signal_strength:  Signal
> strength = 5120
> Jan  3 06:25:15 mythtv kernel: cx24123_read_snr:  read S/N index =
> 65500
> Jan  3 06:25:21 mythtv kernel: LNB Voltage OFF.
> Jan  3 06:25:21 mythtv kernel: Voltage Not Set Properly
> Jan  3 06:26:16 mythtv syslogd 1.4.1#20: restart.
> Jan  3 06:26:23 mythtv kernel: LNB Voltage On.
> Jan  3 06:26:23 mythtv kernel: cx24123_set_voltage: setting voltage
> 18V
> Jan  3 06:26:25 mythtv kernel: cx24123_read_signal_strength:  Signal
> strength = 5120
> Jan  3 06:26:25 mythtv kernel: cx24123_read_snr:  read S/N index =
> 65500
> Jan  3 06:26:54 mythtv kernel: LNB Voltage OFF.
> Jan  3 06:26:54 mythtv kernel: Voltage Not Set Properly
> Jan  3 06:27:01 mythtv kernel: LNB Voltage On.
> Jan  3 06:27:01 mythtv kernel: cx24123_set_voltage: setting voltage
> 18V
> Jan  3 06:27:02 mythtv kernel: cx24123_read_signal_strength:  Signal
> strength = 5120
> Jan  3 06:27:02 mythtv kernel: cx24123_read_snr:  read S/N index =
> 65500
> Jan  3 06:27:10 mythtv kernel: LNB Voltage OFF.
> Jan  3 06:27:11 mythtv kernel: Voltage Not Set Properly
> Jan  3 06:28:45 mythtv kernel: LNB Voltage On.
> Jan  3 06:28:45 mythtv kernel: cx24123_set_voltage: setting voltage
> 18V
> Jan  3 06:21:36 mythtv kernel: LNB Voltage On.
> Jan  3 06:21:36 mythtv kernel: cx24123_set_voltage: setting voltage
> 13V
> Jan  3 06:21:37 mythtv kernel: cx24123_read_signal_strength:  Signal
> strength = 1792
> Jan  3 06:21:37 mythtv kernel: cx24123_read_snr:  read S/N index = 0
> Jan  3 06:21:38 mythtv kernel: cx24123_read_signal_strength:  Signal
> strength = 2048
> Jan  3 06:21:38 mythtv kernel: cx24123_read_snr:  read S/N index = 0
> Jan  3 06:21:39 mythtv kernel: cx24123_read_signal_strength:  Signal
> strength = 2560
> Jan  3 06:21:39 mythtv kernel: cx24123_read_snr:  read S/N index = 0
> Jan  3 06:21:27 mythtv kernel: LNB Voltage On.
> Jan  3 06:21:27 mythtv kernel: cx24123_set_voltage: setting voltage
> 13V
> Jan  3 06:21:28 mythtv kernel: cx2

Re: [linux-dvb] Diseqc and TT 3200-S2

[Marco Coli]

Brougs78 ha scritto:
>  Everething else is 
> working really well with that card. Thanks to the driver developers out 
> there.
>
>   
Hi Brougs. Unfortunately for me my 3200-S2 is not recognized, even with 
latest (1 dec) multiproto. I tried to search on list first, then I wrote 
here, but no luck.

Can you please post the results of lspci -v  concerning your card? Maybe 
mine has something different.
Thank you.

My lspci -v follows:

04:07.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
Subsystem: Unknown device 5b2f:1081
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at fddfe000 (32-bit, non-prefetchable) [size=512]


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] How can I extract the firmware file from windows drivers?

[Qinyong Liu]

My usb device is not on the list. Can anyone tell me how to get the 
firmware file from windows driver?


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Diseqc and TT 3200-S2

[Reinhard Nissl]

Hi,

Brougs78 schrieb:

> Should diseqc allready work with the current multiproto-driver?
> 
> I've got a multiswitch where 2 satellites are attached to it. It seems 
> that I don't get a lock with the TT 3200.
> 
> This is the only thing I'm really missing right now. Everething else is 
> working really well with that card. Thanks to the driver developers out 
> there.

I've been using DiSEqC all the time with this card and VDR to
control my multiswitch for ASTRA 19.2 E and Hotbird 13.0 E.

Bye.
-- 
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Diseqc and TT 3200-S2

[Brougs78]

Hi!

Should diseqc allready work with the current multiproto-driver?

I've got a multiswitch where 2 satellites are attached to it. It seems 
that I don't get a lock with the TT 3200.

This is the only thing I'm really missing right now. Everething else is 
working really well with that card. Thanks to the driver developers out 
there.

Bye,
Andreas Brugger

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How can I save an entire TS to a file? Please help me

[Andrea Venturi]

Matteo Pampolini wrote:

> 
> But what about the entire TS? I read about the special
> PID 8192, but I did not understood if this is a
> dvbstream feature (that doesn't work, at least for me)
> or if it's a LinuxDVB one.

hi,

in theory, it's not that difficult to dump a complete stream, BUT you 
should pay attention to the signal level because it's easy to get some 
continuity errors too if the BER is not zero..

i have a USB DVB-T device called Cinergy T2, and i can share my two 
hints. BTW i don't know if your device has the same capability (full ts 
dump..):

when i insert it on the USB BUS i get from dmesg:

==
  [10511.327179] usb 2-2.2.3: new high speed USB device using ehci_hcd 
and address 15
[10511.346586] usb 2-2.2.3: configuration #1 chosen from 1 choice
[10511.543120] DVB: registering new adapter (TerraTec/qanu USB2.0 
Highspeed DVB-T Receiver)
[10511.544594] usbcore: registered new interface driver cinergyT2
==

and here it's a sample of a command line for dvbstream (you get La7 in 
Bologna) to dump the complete ts stream


[EMAIL PROTECTED]:/opt$ dvbstream -f 714000 -o 8192 > /tmp/prova.ts
dvbstream v0.6 - (C) Dave Chapman 2001-2004
Released under the GPL.
Latest version available from http://www.linuxstb.org/
Tuning to 714000 Hz
Using DVB card "TerraTec/qanu USB2.0 Highspeed DVB-T Receiver", freq=714000
tuning DVB-T (in United Kingdom) to 71400 Hz, Bandwidth: 8
Getting frontend status
Bit error rate: 0
Signal strength: 54068
SNR: 46260
UNC: 0
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI 
FE_HAS_SYNC
dvbstream will stop after -1 seconds (71582788 minutes)
Output to stdout
Streaming 1 stream
Caught signal 2 - closing cleanly.
=

as i told before, pay attention to the "Bit Error Rate" line, it should 
be zero..

let's see the file has grown a bit

[EMAIL PROTECTED]:/opt$ ls -l /tmp/prova.ts
-rw-r--r-- 1 andrea andrea 17268552 2008-01-03 18:28 /tmp/prova.ts

now it's time to play it with VLC:

running with vlc you get some continuity errors only at the beginning 
(just to synchronize from the zero value as default..), if your TS is 
good enough.. like here:

[EMAIL PROTECTED]:/opt$ vlc /tmp/prova.ts
VLC media player 0.8.6c Janus
libdvbpsi error (PSI decoder): TS discontinuity (received 8, expected 0) 
for PID 0
libdvbpsi error (PSI decoder): TS discontinuity (received 11, expected 
0) for PID 269
libdvbpsi error (PSI decoder): TS discontinuity (received 10, expected 
0) for PID 256
libdvbpsi error (PSI decoder): TS discontinuity (received 5, expected 0) 
for PID 343
libdvbpsi error (PSI decoder): TS discontinuity (received 8, expected 0) 
for PID 7042
libdvbpsi error (PSI decoder): TS discontinuity (received 15, expected 
0) for PID 283
libdvbpsi error (PSI decoder): TS discontinuity (received 12, expected 
0) for PID 279
libdvbpsi error (PSI decoder): TS discontinuity (received 1, expected 0) 
for PID 289
libdvbpsi error (PSI decoder): TS discontinuity (received 7, expected 0) 
for PID 298
libdvbpsi error (PSI decoder): TS discontinuity (received 9, expected 0) 
for PID 295
libdvbpsi error (PSI decoder): TS discontinuity (received 11, expected 
0) for PID 292
libdvbpsi error (PSI decoder): TS discontinuity (received 5, expected 0) 
for PID 301
libdvbpsi error (PSI decoder): TS discontinuity (received 11, expected 
0) for PID 359
libdvbpsi error (PSI decoder): TS discontinuity (received 14, expected 
0) for PID 304
libdvbpsi error (PSI decoder): TS discontinuity (received 13, expected 
0) for PID 18
libdvbpsi error (PSI decoder): TS discontinuity (received 1, expected 0) 
for PID 17


HTH

bye

andrea



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] How can I save an entire TS to a file? Please help me

[Nico Sabbi]

Il Thursday 03 January 2008 17:12:07 Matteo Pampolini ha scritto:
> Hello everybody and happy new year,
>
> my name is Matteo, I'm writing from Italy and this is
> my first post to this list.
>
> I'm trying to record an entire (data included) DVB-T
> TS into a file, I tried many solutions before posting,
> say dvbstream, DVBStreamer, VideoLAN, but always
> without success.
>
> I have an USB 2.0 SigmaTek DVB-300 device, that Linux
> recognises as:
>
>  dvb-usb: found a 'DiBcom USB2.0 DVB-T reference
> design (MOD3000P)' in warm state.
>
> Moreover, during initialization I get this message:
>
> dvb-usb: will pass the complete MPEG2 transport stream
> to the software demuxer.
>
> As far as I can understand this means that the entire
> transport stream should be passed to the kernel
> software demuxer that in turns selects the PIDs I
> need.
>
> But what about the entire TS? I read about the special
> PID 8192, but I did not understood if this is a
> dvbstream feature (that doesn't work, at least for me)
> or if it's a LinuxDVB one.

it's a feature of the linuxdvb drivers  that the specific driver
must be able to handle correctly, although in your case
there doesn't seem to be a problem

>
> Anyway, I am able to tune, of course, able to record a
> single service and stream it to be watched through
> VLC, but not to record the entire TS into a file, can
> anyone please help me?

what command line are you using?
$ dvbstream -f FREQ -bw BW -o 8192 > dump.ts 
is sufficient

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] How can I save an entire TS to a file? Please help me

[Matteo Pampolini]

Hello everybody and happy new year,

my name is Matteo, I'm writing from Italy and this is
my first post to this list.

I'm trying to record an entire (data included) DVB-T
TS into a file, I tried many solutions before posting,
say dvbstream, DVBStreamer, VideoLAN, but always
without success.

I have an USB 2.0 SigmaTek DVB-300 device, that Linux
recognises as:

 dvb-usb: found a 'DiBcom USB2.0 DVB-T reference
design (MOD3000P)' in warm state.

Moreover, during initialization I get this message:

dvb-usb: will pass the complete MPEG2 transport stream
to the software demuxer.

As far as I can understand this means that the entire
transport stream should be passed to the kernel
software demuxer that in turns selects the PIDs I
need.

But what about the entire TS? I read about the special
PID 8192, but I did not understood if this is a
dvbstream feature (that doesn't work, at least for me)
or if it's a LinuxDVB one.

Anyway, I am able to tune, of course, able to record a
single service and stream it to be watched through
VLC, but not to record the entire TS into a file, can
anyone please help me?

Many thanks in advance,

Matteo.


  ___ 
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: 
http://it.docs.yahoo.com/nowyoucan.html


___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Getting a Zarlink ZL10353-based tuner to work.

[Anthony Long]

Hello,

I'm attempting to get a USB DVB tuner working on my Ubuntu 7.10 box
(which is currently running a PCI-based DVB-T tuner card fine). It's
something like this one:

http://www.my-neotionbox.tv/gb/index.php?page=02_NEOTION%20Box%20DTT/02_NEOTION%20Mini%20Box%20T.php&rub=NEOTION%20Box%20DTT

I've opened the casing and have worked out that it's a Zarlink
ZL10353-based unit with a Cypress FX2 chip, and the RF shield has
Philips on it.

Having looked at  and
followed what it says, I'm none the wiser. In:
/lib/firmware/2.6.22-14-generic/

I have:
dvb-usb-wt220u-01.fw

 From what I picked up elsewhere, this may be the correct firmware (the
other usual firmwares are present as well). Following the instructions
on the aforementioned page, when I check dmesg, I don't get much output
(and nothing like the link suggests):

[174659.084398] usb 1-8: new high speed USB device using ehci_hcd and
address 10
[174659.216657] usb 1-8: configuration #1 chosen from 1 choice

The linked page says that the firmware should be downloaded to the
device; clearly this isn't happening, as the device isn't being 
recognised properly.

lsusb -v gives the following output:

Bus 001 Device 010: ID 04b4:8613 Cypress Semiconductor Corp. CY7C68013
EZ-USB FX2 USB 2.0 Development Kit
Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   2.00
   bDeviceClass  255 Vendor Specific Class
   bDeviceSubClass   255 Vendor Specific Subclass
   bDeviceProtocol   255 Vendor Specific Protocol
   bMaxPacketSize064
   idVendor   0x04b4 Cypress Semiconductor Corp.
   idProduct  0x8613 CY7C68013 EZ-USB FX2 USB 2.0 Development Kit
   bcdDevice   a0.01
[..]

Searching for information based on this, I couldn't find anything that 
helped me any further. In other words, I'm stuck.

I'd appreciate any assistance that somebody could provide, please.

Thanks,
Anthony.

___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Consistent kernel crash on latest hg repo with 2.6.24-rc6

[Erik van Zijst]

Solved!

It turned out the problem was in the external PCI adaptor I'm using to 
increase the (rather limited) number of legacy 32-bit PCI slots in my 
server system through a PCI-Express slot 
(http://www.virtuavia.eu/shop/pci-express-to-pci-expansion-box-p29809.html)

Although the card did get properly detected, it was very unstable, 
constantly crashing the kernel. I've removed the external PCI expansion 
box, plugged the card directly in the only on-board PCI slot and now it 
works perfectly stable.

Lessons learned: don't buy these external PCI expansion boxes.

Erik


Erik van Zijst wrote:
> Erik van Zijst wrote:
>> So far all tests have been done using 64 bit distro's and kernels.
> 
> I've just tried a fresh, vanilla 32-bit Ubuntu 7.10 install (kernel 
> 2.6.22-14), but this still exhibits the same kernel freeze (albeit after 
> a bit more time).
> 
> Could this somehow be a firmware issue, or should a firmware or badly 
> behaving card never crash the driver?
> 
> Erik
> 
> 
>> Erik van Zijst wrote:
>>> Hi folks,
>>>
>>> Since I installed a TechnoTrend 1500 Budget (with optional budget-ci CAM 
>>> board), my kernel crashes completely everytime I run a frequency scan 
>>> using the w_scan utility. There's no kernel panic message or anything 
>>> printed to the tty, just instant death.
>>>
>>> The server box (dual quadcore Xeon) ran perfectly stable until I 
>>> installed the T-1500 last week, and still runs stable as long as I don't 
>>> use the card.
>>>
>>> I started out using a stock 2.6.22-something kernel (vanilla Fedora 8 
>>> and Ubuntu 7.10 server), then switched to 2.6.24-rc6 (generated at 
>>> 2007-12-21) and finally tried today's trunk of 
>>> http://linuxtv.org/hg/v4l-dvb using hg, on top of my 2.6.24-rc6 kernel. 
>>> Yet, every combination dies.
>>>
>>> The kernel usually dies the first time "w_scan -x" 
>>> (http://wirbel.htpc-forum.de/w_scan/index2.html version 20071209) is run 
>>> and then usually dies near the end when w_scan prints "tune to:". 
>>> Occasionally it takes more than one run before it crashes. The box is 
>>> idle during the scan and there's no other PCI activity.
>>>
>>> I'm using firmware dvb-fe-tda10046.fw, installed using get_dvb_firmware.
>>>
>>> regards,
>>> Erik van Zijst
>>>
>>> ___
>>> 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 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] Digiwave 108G/GeniaTech TVStar Card - Adding it to the CX88 Driver

[Dwaine Garden]

Oppsss.  The chip is actually "TDB2028E3".  So we know that the chip is 
actually a silicon TV Tuner.

Looking at the Windows INF file, it does list a lot of  Xceive references.  Too 
bad it was not marked as "TDA", then we could assume it was a Phillips Silicon 
TV Tuner.

Examples

[CX23880.Xceive.NT] 
Include=ks.inf, kscaptur.inf, ksfilter.inf, wdmaudio.inf, bda.inf 
Needs=  
KS.Registration,KSCAPTUR.Registration.NT,MSPCLOCK.Installation,WDMAUDIO.Registration,BDA.Registration,bda.Installation.NT
 
AddReg= CX880.AddReg,Xceive.AddReg,XBAR.AddReg 
CopyFiles=  CX880.CopyDrivers,DSFilters.CopyFiles 
RegisterDlls=DSFilters.RegDLL 
 
[CX23880.XceiveZarlink.NT] 
Include=ks.inf, kscaptur.inf, ksfilter.inf, wdmaudio.inf, bda.inf 
Needs=  
KS.Registration,KSCAPTUR.Registration.NT,MSPCLOCK.Installation,WDMAUDIO.Registration,BDA.Registration,bda.Installation.NT
 
AddReg= CX880.AddReg,XceiveZarlink.AddReg,XBAR.AddReg,CXTS.AddReg 
CopyFiles=  CX880.CopyDrivers,DSFilters.CopyFiles 
RegisterDlls=DSFilters.RegDLL 
 
[CX23880.XceiveConexant.NT] 
Include=ks.inf, kscaptur.inf, ksfilter.inf, wdmaudio.inf, bda.inf 
Needs=  
KS.Registration,KSCAPTUR.Registration.NT,MSPCLOCK.Installation,WDMAUDIO.Registration,BDA.Registration,bda.Installation.NT
 
AddReg= CX880.AddReg,XceiveConexant.AddReg,XBAR.AddReg,CXTS.AddReg 
CopyFiles=  CX880.CopyDrivers,DSFilters.CopyFiles 
RegisterDlls=DSFilters.RegDLL 

Still have not got anything off the dvb frontend.  It's also getting confused 
with the voltage for the LNB.

Jan  3 06:24:17 mythtv kernel: LNB Voltage On.
Jan  3 06:24:17 mythtv kernel: cx24123_set_voltage: setting voltage 18V
Jan  3 06:24:18 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
5120
Jan  3 06:24:18 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:25:01 mythtv kernel: LNB Voltage OFF.
Jan  3 06:25:01 mythtv kernel: Voltage Not Set Properly
Jan  3 06:25:14 mythtv kernel: LNB Voltage On.
Jan  3 06:25:14 mythtv kernel: cx24123_set_voltage: setting voltage 18V
Jan  3 06:25:15 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
5120
Jan  3 06:25:15 mythtv kernel: cx24123_read_snr:  read S/N index = 65500
Jan  3 06:25:21 mythtv kernel: LNB Voltage OFF.
Jan  3 06:25:21 mythtv kernel: Voltage Not Set Properly
Jan  3 06:26:16 mythtv syslogd 1.4.1#20: restart.
Jan  3 06:26:23 mythtv kernel: LNB Voltage On.
Jan  3 06:26:23 mythtv kernel: cx24123_set_voltage: setting voltage 18V
Jan  3 06:26:25 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
5120
Jan  3 06:26:25 mythtv kernel: cx24123_read_snr:  read S/N index = 65500
Jan  3 06:26:54 mythtv kernel: LNB Voltage OFF.
Jan  3 06:26:54 mythtv kernel: Voltage Not Set Properly
Jan  3 06:27:01 mythtv kernel: LNB Voltage On.
Jan  3 06:27:01 mythtv kernel: cx24123_set_voltage: setting voltage 18V
Jan  3 06:27:02 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
5120
Jan  3 06:27:02 mythtv kernel: cx24123_read_snr:  read S/N index = 65500
Jan  3 06:27:10 mythtv kernel: LNB Voltage OFF.
Jan  3 06:27:11 mythtv kernel: Voltage Not Set Properly
Jan  3 06:28:45 mythtv kernel: LNB Voltage On.
Jan  3 06:28:45 mythtv kernel: cx24123_set_voltage: setting voltage 18V
Jan  3 06:21:36 mythtv kernel: LNB Voltage On.
Jan  3 06:21:36 mythtv kernel: cx24123_set_voltage: setting voltage 13V
Jan  3 06:21:37 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
1792
Jan  3 06:21:37 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:38 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
2048
Jan  3 06:21:38 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:39 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
2560
Jan  3 06:21:39 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:27 mythtv kernel: LNB Voltage On.
Jan  3 06:21:27 mythtv kernel: cx24123_set_voltage: setting voltage 13V
Jan  3 06:21:28 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
1280
Jan  3 06:21:28 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:29 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
1280
Jan  3 06:21:29 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:30 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
1280
Jan  3 06:21:30 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:31 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
1024
Jan  3 06:21:31 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:32 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
1024
Jan  3 06:21:32 mythtv kernel: cx24123_read_snr:  read S/N index = 0
Jan  3 06:21:33 mythtv kernel: cx24123_read_signal_strength:  Signal strength = 
1024
Jan  3 06:21:33 mythtv kernel: cx24123_read_snr:  read S/N index = 0

 

hermann pitton <[EMAIL PROTECTED]> wrote: Am Mittwoch, den 02.01.2008, 23:21 
-0500 schrieb Dwaine Garden:
> Looking at th

[linux-dvb] Geniatech T328

[Qinyong Liu]

This device confused me for a long time. And yesterday, I opened it and 
checked every IC it uses. Appearently, this device uses MT2060F and 
ZL10353, and another IC called CY7C68013A.

So, I searched bttv and found that FREECOM has made a usb pen with 
almost the same three chips. 
( http://bttv-gallery.de/high/bttv-gallery.html ) 

Now, the only difference is that the two usb pens have different usb id. 
Freecom: 14aa:022b
Geniatech T328: 04b4:8613

I read the files in v4l and it seems that mt2060, zl10353 are finished, 
but there is no file with the name cy7c68013. And until now, I an still 
not clear with v4l and i don't know how it works. Would you give me some 
hint? 



___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb