[linux-dvb] DVB-S Channel searching problem

[linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

Hi,

I have a problem with DVB-S channel searching, the scan command doesn't find all channels in Linux on Astra 19.2E.
It works in Windows.

For instance the scan doesn't find RTL2, but if I add to channels.conf
RTL2:12187:h:0:27500:166:128:12020
then szap -r works correctly.

I have TeVii S460 DVB-S/S2.
Linux kernel 2.6.28.

Can anybody help me to find out why the scan doesn't work correctly.
I've compiled kernel from source so I can apply patches or change its settings.

Regards,
Roman

lspci:

00:09.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
        Subsystem: Unknown device d460:9022
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at e8000000 (32-bit, non-prefetchable) [size=16M]
        Capabilities: [44] Vital Product Data
        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: Unknown device d460:9022
        Flags: bus master, medium devsel, latency 32, IRQ 10
        Memory at e9000000 (32-bit, non-prefetchable) [size=16M]
        Capabilities: [4c] Power Management version 2

This is part of dmesg:
cx8800 0000:00:09.0: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 10                                                               
cx88[0]: quirk: PCIPCI_NATOMA -- set TBFX                                                                                                   
cx88[0]: subsystem: d460:9022, board: TeVii S460 DVB-S/S2 [card=70,autodetected], frontend(s): 1                                            
cx88[0]: TV tuner type -1, Radio tuner type -1                                                                                              
cx88[0]/0: found at 0000:00:09.0, rev: 5, irq: 10, latency: 32, mmio: 0xe8000000                                                            
cx88[0]/0: registered device video0 [v4l2]                                                                                                  
cx88[0]/0: registered device vbi0                                                                                                           
Linux agpgart interface v0.103                                                                                                              
agpgart-intel 0000:00:00.0: Intel 440BX Chipset                                                                                             
agpgart-intel 0000:00:00.0: AGP aperture is 32M @ 0xe4000000                                                                                
EXT3 FS on sda1, internal journal                                                                                                           
Adding 1020088k swap on /dev/sda5.  Priority:-1 extents:1 across:1020088k                                                                   
kjournald starting.  Commit interval 5 seconds                                                                                              
EXT3 FS on sda6, internal journal                                                                                                           
EXT3-fs: mounted filesystem with ordered data mode.                                                                                         
loop: module loaded                                                                                                                         
eth2: link up, 100Mbps, full-duplex, lpa 0xC5E1                                                                                             
warning: `proftpd' uses 32-bit capabilities (legacy support in use)                                                                         
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory                                                                   
NFSD: starting 90-second grace period                                                                                                       
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded                                                                                 
cx88[0]/2: cx2388x 8802 Driver Manager                                                                                                      
cx88-mpeg driver manager 0000:00:09.2: PCI INT A -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 10                                             
cx88[0]/2: found at 0000:00:09.2, rev: 5, irq: 10, latency: 32, mmio: 0xe9000000                                                            
cx8802_probe() allocating 1 frontend(s)                                                                                                     
cx88/2: cx2388x dvb driver version 0.0.6 loaded                                                                                             
cx88/2: registering cx8802 driver, type: dvb access: shared                                                                                 
cx88[0]/2: subsystem: d460:9022, board: TeVii S460 DVB-S/S2 [card=70]                                                                       
cx88[0]/2: cx2388x based DVB/ATSC card                                                                                                      
DVB: registering new adapter (cx88[0])                                                                                                      
DVB: registering adapter 0 frontend 0 (Conexant CX24116/CX24118)...                                                                         
cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...                                                               
i2c-adapter i2c-0: firmware: requesting dvb-fe-cx24116.fw                                                                                   
cx24116_firmware_ondemand: Waiting for firmware upload(2)...                                                                                
cx24116_load_firmware: FW version 1.23.86.1                                                                                                 
cx24116_firmware_ondemand: Firmware upload complete


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

Re: [linux-dvb] DVB-S Channel searching problem

[Brice DUBOST]

Roman Jarosz a écrit :
> Hi,
> 
> I have a problem with DVB-S channel searching, the scan command doesn't find all channels in Linux on Astra 19.2E.
> It works in Windows.
> 
> For instance the scan doesn't find RTL2, but if I add to channels.conf
> RTL2:12187:h:0:27500:166:128:12020
> then szap -r works correctly.
> 
> I have TeVii S460 DVB-S/S2.
> Linux kernel 2.6.28.
> 
> Can anybody help me to find out why the scan doesn't work correctly.
> I've compiled kernel from source so I can apply patches or change its settings.
> 
> Regards,
> Roman
> 


Hello

Scan tunes on one frequency, and uses the informations given by the
provider to find the others

Sometimes (quite often in fact) the providers doesn't give full informations

You can use wscan wich will try to lock on each possible frequency
(longer method)

regards

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

Re: [linux-dvb] DVB-S Channel searching problem

[BOUWSMA Barry]

On Sat, 3 Jan 2009, Brice DUBOST wrote:

> > For instance the scan doesn't find RTL2, but if I add to channels.conf
> > RTL2:12187:h:0:27500:166:128:12020
> > then szap -r works correctly.

> Scan tunes on one frequency, and uses the informations given by the
> provider to find the others
> 
> Sometimes (quite often in fact) the providers doesn't give full informations

In the case of Astra 19E2, the list of transponders is
sufficiently well-managed that pretty much regardless of
which transponder you start on, you'll get a list of most
of them, from which you'll get a list of them all.

Unlike, say, Hotbirds, where it's more or less a free-
for all...


To the original poster, what unusual things does the
output to the console of `scan -v' show, if you don't
see anything unusual for `scan' without -v ?

In particular, search for the particular frequencies
of RTL or any other transponders/channels which you
know are missing, or other obvious errors...

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sat, 03 Jan 2009 18:01:01 +0100, Brice DUBOST <braice@braice.net> wrote:

> Roman Jarosz a écrit :
>> Hi,
>>
>> I have a problem with DVB-S channel searching, the scan command doesn't  
>> find all channels in Linux on Astra 19.2E.
>> It works in Windows.
>>
>> For instance the scan doesn't find RTL2, but if I add to channels.conf
>> RTL2:12187:h:0:27500:166:128:12020
>> then szap -r works correctly.
>>
>> I have TeVii S460 DVB-S/S2.
>> Linux kernel 2.6.28.
>>
>> Can anybody help me to find out why the scan doesn't work correctly.
>> I've compiled kernel from source so I can apply patches or change its  
>> settings.
>>
>> Regards,
>> Roman
>>
>
>
> Hello
>
> Scan tunes on one frequency, and uses the informations given by the
> provider to find the others
>
> Sometimes (quite often in fact) the providers doesn't give full  
> informations
>
> You can use wscan wich will try to lock on each possible frequency
> (longer method)

I can't make it work

Info: using DVB adapter auto detection.
   Wrong type, ignoring frontend /dev/dvb/adapter0/frontend0
main:2762: FATAL: ***** NO USEABLE DVB CARD FOUND. *****

and on w_scan homepage is said that it doesn't work with DVB-S.


> regards
>
> _______________________________________________
> 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] DVB-S Channel searching problem

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 482 bytes --]

On Sat, Jan 3, 2009 at 6:42 PM, Roman Jarosz <roman.jarosz@gmail.com> wrote:

> Hi,
>
> I have a problem with DVB-S channel searching, the scan command doesn't
> find all channels in Linux on Astra 19.2E.
> It works in Windows.
>
Please specify what driver you use, what scan application, what is the
command line you gave to the scan application, what is the frequency file
you've used for scan application, what is the result of the scan you have.

Than maybe I can help somehow.

[-- Attachment #1.2: Type: text/html, Size: 791 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sat, 03 Jan 2009 18:28:03 +0100, Alex Betis <alex.betis@gmail.com> wrote:

> On Sat, Jan 3, 2009 at 6:42 PM, Roman Jarosz <roman.jarosz@gmail.com>  
> wrote:
>
>> Hi,
>>
>> I have a problem with DVB-S channel searching, the scan command doesn't
>> find all channels in Linux on Astra 19.2E.
>> It works in Windows.
>>
> Please specify what driver you use, what scan application, what is the
> command line you gave to the scan application, what is the frequency file
> you've used for scan application, what is the result of the scan you  
> have.
>
> Than maybe I can help somehow.

I use scan from dvb-apps, the command is
"scan -o vdr /root/dvb/Astra-19.2E > /etc/vdr/channels.conf"
where /root/dvb/Astra-19.2E is file with "S 11567500 V 22000000 5/6"

I use cx88-dvb driver but many modules are loaded with it see
http://kedge.wz.cz/dvb/lsmod.txt

Scan console output is in file http://kedge.wz.cz/dvb/channels.conf
and the result in http://kedge.wz.cz/dvb/channels.conf

When console shows
__tune_to_transponder:1508: ERROR: Setting frontend parameters failed: 22 Invalid argument

the dmesg prints
DVB: adapter 0 frontend 0 frequency 8175750 out of range (950000..2150000)

Roman

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

Re: [linux-dvb] DVB-S Channel searching problem

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 2562 bytes --]

On Sat, Jan 3, 2009 at 8:11 PM, Roman Jarosz <roman.jarosz@gmail.com> wrote:

> On Sat, 03 Jan 2009 18:28:03 +0100, Alex Betis <alex.betis@gmail.com>
> wrote:
>
> > On Sat, Jan 3, 2009 at 6:42 PM, Roman Jarosz <roman.jarosz@gmail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> I have a problem with DVB-S channel searching, the scan command doesn't
> >> find all channels in Linux on Astra 19.2E.
> >> It works in Windows.
> >>
> > Please specify what driver you use, what scan application, what is the
> > command line you gave to the scan application, what is the frequency file
> > you've used for scan application, what is the result of the scan you
> > have.
> >
> > Than maybe I can help somehow.
>
> I use scan from dvb-apps, the command is
> "scan -o vdr /root/dvb/Astra-19.2E > /etc/vdr/channels.conf"
> where /root/dvb/Astra-19.2E is file with "S 11567500 V 22000000 5/6"

I think that's the main issue. *BOUWSMA w*rote that its ok to rely on
astra's maintainers and connect to any transponder is enough to get a list
of all others. I personaly don't trust those maintainers since I saw too
many errors in NIT messages that specify the transponder, so I specify all
the frequencies I want to scan. I don't have a dish to 19.2, but there were
many errors with 5 other satellites I have.
You can get a list of those frequencies here:
http://www.lyngsat.com/astra19.html



>
> I use cx88-dvb driver but many modules are loaded with it see
> http://kedge.wz.cz/dvb/lsmod.txt

I meant to ask what is the origin of the driver. I use Igor's driver from:
http://mercurial.intuxication.org/hg/s2-liplianin/

If you have a S2API driver (or will use Igor's driver), you can use my
scan-s2 application with many changes in NIT parsing that might resolve your
issue.
http://mercurial.intuxication.org/hg/scan-s2/


>
> Scan console output is in file http://kedge.wz.cz/dvb/channels.conf
> and the result in http://kedge.wz.cz/dvb/channels.conf

You've posted the same link for both outputs. Please post console output
when you run scan with "-v" parameter. Maybe even with "-vv".


>
> When console shows
> __tune_to_transponder:1508: ERROR: Setting frontend parameters failed: 22
> Invalid argument
>
> the dmesg prints
> DVB: adapter 0 frontend 0 frequency 8175750 out of range (950000..2150000)

It could be anything. Bad NIT message (most probably) or a memory smashing
in scan application.


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

[-- Attachment #1.2: Type: text/html, Size: 4326 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] DVB-S Channel searching problem

[Gregoire Favre]

Well,

I would suggest not using S2API as it's seems to be broken for our card
at this time, I did test steven s2 repo which is better that all other
S2API repo I have tested but still worse than lipliandvb (multiproto
hg).

I wrote about the problem of the cx88 cards on this exact same ml ;-)
-- 
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
               http://picasaweb.google.com/Gregoire.Favre

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

Re: [linux-dvb] DVB-S Channel searching problem

[Goga777]

> I would suggest not using S2API as it's seems to be broken for our card
> at this time, 

why do you think so ? 

>I did test steven s2 repo which is better that all other
> S2API repo 

have you tested http://mercurial.intuxication.org/hg/s2-liplianin ?

>I have tested but still worse than lipliandvb (multiproto
> hg).

please try 

http://mercurial.intuxication.org/hg/s2-liplianin (yesterday Igor synchronized it with current v4l-dvb)
+
http://hg.kewl.org/dvb2010/ - new dvb scaner 

for me everything is working without any problem with my hvr4000. Also patched vdr 170 works well with s2api


Goga


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

Re: [linux-dvb] DVB-S Channel searching problem

[hermann pitton]

Am Sonntag, den 04.01.2009, 11:14 +0300 schrieb Goga777:
> > I would suggest not using S2API as it's seems to be broken for our card
> > at this time, 
> 
> why do you think so ? 
> 
> >I did test steven s2 repo which is better that all other
> > S2API repo 
> 
> have you tested http://mercurial.intuxication.org/hg/s2-liplianin ?
> 
> >I have tested but still worse than lipliandvb (multiproto
> > hg).
> 
> please try 
> 
> http://mercurial.intuxication.org/hg/s2-liplianin (yesterday Igor synchronized it with current v4l-dvb)
> +
> http://hg.kewl.org/dvb2010/ - new dvb scaner 
> 
> for me everything is working without any problem with my hvr4000. Also patched vdr 170 works well with s2api
> 
> 
> Goga
> 

Hi,

thanks.

We else need at least i2c_debug enabled on the cx88xx, yes, that is the
busmaster :)

I don't deny that strange things happened, wrong tuners loaded without
trace so far.

Mike at least had a hotfix, not to allow analog only tuners to oops
around.

Cheers,
Hermann





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

Re: [linux-dvb] DVB-S Channel searching problem

[Gregoire Favre]

On Sun, Jan 04, 2009 at 09:29:44AM +0100, hermann pitton wrote:

Hello,

> We else need at least i2c_debug enabled on the cx88xx, yes, that is the
> busmaster :)

Great, I have to try to do it, but I should first learn of a way to do
it, I'll report ASAP.

> I don't deny that strange things happened, wrong tuners loaded without
> trace so far.
> 
> Mike at least had a hotfix, not to allow analog only tuners to oops
> around.

Could you point me to an URL for this ?

Thank you very much,
-- 
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
               http://picasaweb.google.com/Gregoire.Favre

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

Re: [linux-dvb] DVB-S Channel searching problem

[hermann pitton]

Hi,

Am Sonntag, den 04.01.2009, 11:37 +0100 schrieb Gregoire Favre: 
> On Sun, Jan 04, 2009 at 09:29:44AM +0100, hermann pitton wrote:
> 
> Hello,
> 
> > We else need at least i2c_debug enabled on the cx88xx, yes, that is the
> > busmaster :)
> 
> Great, I have to try to do it, but I should first learn of a way to do
> it, I'll report ASAP.
> 
> > I don't deny that strange things happened, wrong tuners loaded without
> > trace so far.
> > 
> > Mike at least had a hotfix, not to allow analog only tuners to oops
> > around.
> 
> Could you point me to an URL for this ?

http://linuxtv.org/hg/v4l-dvb/rev/f9bdc9ff3da1

it must not be related at all, since it is still not clear how the wrong
tuner type sneaked in, could still be caused by user/system options.

But there seem to be some potential module load order problems.
In any case, I would not use "make load" at all trying to debug such!

I just tried and had to reboot on a x86_32 including lost keyboard.

Cheers,
Hermann







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

Re: [linux-dvb] DVB-S Channel searching problem

[Gregoire Favre]

On Sun, Jan 04, 2009 at 05:06:59PM +0100, hermann pitton wrote:

Hello,

> it must not be related at all, since it is still not clear how the wrong
> tuner type sneaked in, could still be caused by user/system options.
> 
> But there seem to be some potential module load order problems.
> In any case, I would not use "make load" at all trying to debug such!
> 
> I just tried and had to reboot on a x86_32 including lost keyboard.

Oh, then I am not the only one with this lost keyboard problem ;-)
I hope you got an sshd open on your computer and could reboot without
too much troubles ?

So, would it be right in order to debug this to compil an updated
v4l-dvb's hg with debug enabled, then "make install" from v4l dir, and
issue :

modprobe budget_ci
modprobe cx8800
modprobe cx88_alsa
modprobe cx88-dvb

? (sorry for long question)

Thank you very much,
-- 
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
               http://picasaweb.google.com/Gregoire.Favre

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

Re: [linux-dvb] DVB-S Channel searching problem

[hermann pitton]

Hi,

Am Sonntag, den 04.01.2009, 17:37 +0100 schrieb Gregoire Favre:
> On Sun, Jan 04, 2009 at 05:06:59PM +0100, hermann pitton wrote:
> 
> Hello,
> 
> > it must not be related at all, since it is still not clear how the wrong
> > tuner type sneaked in, could still be caused by user/system options.
> > 
> > But there seem to be some potential module load order problems.
> > In any case, I would not use "make load" at all trying to debug such!
> > 
> > I just tried and had to reboot on a x86_32 including lost keyboard.
> 
> Oh, then I am not the only one with this lost keyboard problem ;-)
> I hope you got an sshd open on your computer and could reboot without
> too much troubles ?
> 
> So, would it be right in order to debug this to compil an updated
> v4l-dvb's hg with debug enabled, then "make install" from v4l dir, and
> issue :
> 
> modprobe budget_ci
> modprobe cx8800
> modprobe cx88_alsa
> modprobe cx88-dvb
> 
> ? (sorry for long question)

I would even left the budget_ci out of the game as a start and the rest
should auto load.

For i2c traffic on the cx88xx it is i2c_debug=1.
(modinfo cx88xx)

Good Luck,
Hermann



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

Re: [linux-dvb] DVB-S Channel searching problem

[Gregoire Favre]

[-- Attachment #1: Type: text/plain, Size: 7968 bytes --]

On Sun, Jan 04, 2009 at 06:15:46PM +0100, hermann pitton wrote:

Hello again,

I added the options,

> > modprobe cx8800

Linux video capture interface: v2.00
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
cx8800 0000:04:02.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
cx88[0]: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,autodetected], frontend(s): 2
cx88[0]: TV tuner type 63, Radio tuner type -1
cx88[0]: i2c register ok
cx88[0]: i2c init: enabling analog demod on HVR1300/3000/4000 tuner
tuner' 7-0043: chip found @ 0x86 (cx88[0])
tda9887 7-0043: creating new instance
tda9887 7-0043: tda988[5/6/7] found
cx88[0]: tuner' i2c attach [addr=0x43,client=tuner']
tuner' 7-0061: chip found @ 0xc2 (cx88[0])
cx88[0]: tuner' i2c attach [addr=0x61,client=tuner']
tuner' 7-0063: chip found @ 0xc6 (cx88[0])
cx88[0]: tuner' i2c attach [addr=0x63,client=tuner']
tveeprom 7-0050: Hauppauge model 69009, rev B2A0, serial# 1241151
tveeprom 7-0050: MAC address is 00-0D-FE-12-F0-3F
tveeprom 7-0050: tuner model is Philips FMD1216ME (idx 100, type 63)
tveeprom 7-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xf4)
tveeprom 7-0050: audio processor is CX882 (idx 33)
tveeprom 7-0050: decoder processor is CX882 (idx 25)
tveeprom 7-0050: has radio, has IR receiver, has no IR transmitter
cx88[0]: hauppauge eeprom: model=69009
tuner-simple 7-0061: creating new instance
tuner-simple 7-0061: type set to 63 (Philips FMD1216ME MK3 Hybrid Tuner)
input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:04:02.0/input/input8
cx88[0]/0: found at 0000:04:02.0, rev: 5, irq: 23, latency: 64, mmio: 0xdb000000
wm8775' 7-001b: chip found @ 0x36 (cx88[0])
cx88[0]: wm8775' i2c attach [addr=0x1b,client=wm8775']
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
cx8800 0000:04:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
cx88[1]: subsystem: 14f1:0084, board: Geniatech DVB-S [card=52,autodetected], frontend(s): 1
cx88[1]: TV tuner type 4, Radio tuner type -1
cx88[1]: i2c register ok
cx88[1]/0: found at 0000:04:05.0, rev: 3, irq: 20, latency: 64, mmio: 0xd9000000
cx88[1]/0: registered device video1 [v4l2]
cx88[1]/0: registered device vbi1

> > modprobe cx88_alsa

cx2388x alsa driver version 0.0.6 loaded
cx88_audio 0000:04:02.1: PCI INT A -> GSI 23 (level, low) -> IRQ 23
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards

> > modprobe cx88-dvb

cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
cx88[0]/2: cx2388x 8802 Driver Manager
cx88-mpeg driver manager 0000:04:02.2: PCI INT A -> GSI 23 (level, low) -> IRQ 23
cx88[0]/2: found at 0000:04:02.2, rev: 5, irq: 23, latency: 64, mmio: 0xdd000000
cx8802_probe() allocating 2 frontend(s)
cx88[1]/2: cx2388x 8802 Driver Manager
cx88-mpeg driver manager 0000:04:05.2: PCI INT A -> GSI 20 (level, low) -> IRQ 20
cx88[1]/2: found at 0000:04:05.2, rev: 3, irq: 20, latency: 64, mmio: 0xda000000
cx8802_probe() allocating 1 frontend(s)
cx88/2: cx2388x dvb driver version 0.0.6 loaded
cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68]
cx88[0]/2: cx2388x based DVB/ATSC card
tuner-simple 7-0061: attaching existing instance
tuner-simple 7-0061: type set to 63 (Philips FMD1216ME MK3 Hybrid Tuner)
DVB: registering new adapter (cx88[0])
DVB: registering adapter 0 frontend 0 (Conexant CX24116/CX24118)...
DVB: registering adapter 0 frontend 1 (Conexant CX22702 DVB-T)...
cx88[1]/2: subsystem: 14f1:0084, board: Geniatech DVB-S [card=52]
cx88[1]/2: cx2388x based DVB/ATSC card
CX24123: detected CX24123
DVB: registering new adapter (cx88[1])
DVB: registering adapter 1 frontend 0 (Conexant CX24123/CX24109)...

And I still have my keyboard :-)

I then try ./xmlscan -s 0 13.0E > channels-13.0E.conf

cx24116_firmware_ondemand: Waiting for firmware upload (dvb-fe-cx24116.fw)...
i2c-adapter i2c-7: firmware: requesting dvb-fe-cx24116.fw
cx24116_firmware_ondemand: Waiting for firmware upload(2)...
cx24116_load_firmware: FW version 1.22.82.0
cx24116_firmware_ondemand: Firmware upload complete

Which gives 
wc -l  channels-13.0E.conf
552 channels-13.0E.conf

./xmlscan -s 1 19.2E > channels-19.2E.conf

wc -l  channels-19.2E.conf 
340 channels-19.2E.conf

./xmlscan -s 2 28.2E > channels-28.2E.conf
wc -l  channels-28.2E.conf
320 channels-28.2E.conf

./szap-s2 -r -c channels-28.2E.conf "6301=BBC 1 London;BSkyB"
reading channels from file 'channels-28.2E.conf'
zapping to 31 '6301=BBC 1 London;BSkyB':
delivery DVB-S, modulation QPSK
sat 2, frequency 10773 MHz H, symbolrate 22000000, coderate 5/6, rolloff 0.35
vpid 0x1388, apid 0x1389, sid 0x189d
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 03 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 03 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c240 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 
status 01 | signal c2c0 | snr 0000 | ber 00000000 | unc 00000000 | 

Isn't those numbers of channels quiete small ?

I think my debug info are wrong, I put :
options cx88_alsa index=-2
options cx88xx i2c_debug=1
in  /etc/modprobe.conf isn't that right ?
-- 
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
               http://picasaweb.google.com/Gregoire.Favre

[-- Attachment #2: channels-from-HVR4000.tar.bz2 --]
[-- Type: application/octet-stream, Size: 19496 bytes --]

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] DVB-S Channel searching problem

[hermann pitton]

Hi,

Am Sonntag, den 04.01.2009, 19:24 +0100 schrieb Gregoire Favre:
> On Sun, Jan 04, 2009 at 06:15:46PM +0100, hermann pitton wrote:
> 
[...]
> 
> Isn't those numbers of channels quiete small ?

sorry, did not read it to the end and only noticed the oops is gone.

Yes, looks poor, but I don't have any such hardware and can't compare
what a recent windows driver would deliver. Also at least on 13.0E the
scan file needs lots of updates (lyngsat.com), 19.2 I did not test, but
on 28.2 kaffeine finds much more, but I'm only in borderline reception
conditions and not a reference.

To my surprise, current tda826x silicon tuners for example have no
difference, but previous latest can tuners can have 30% less on the same
signal. I got it told the other way round.

> I think my debug info are wrong, I put :
> options cx88_alsa index=-2

The default -1 should auto enumerate and else you force the dsps/mixers
considering that the sound card(s) are usually first.

> options cx88xx i2c_debug=1
> in  /etc/modprobe.conf isn't that right ?

Thought that should always work.
("depmod -a" ?)

Cheers,
Hermann







_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] DVB-S Channel searching problem

[Gregoire Favre]

On Sun, Jan 04, 2009 at 11:14:29AM +0300, Goga777 wrote:
> > I would suggest not using S2API as it's seems to be broken for our card
> > at this time, 

> why do you think so ? 

Maybe because the three users speaking about this card fails to use it
with recent hg's source. And AFAIK you don't succeed in using vdr-1.7.2
neither with it, no ?

> >I did test steven s2 repo which is better that all other
> > S2API repo 
> 
> have you tested http://mercurial.intuxication.org/hg/s2-liplianin ?

Yes, it was exactly the same result.

> please try 
> 
> http://mercurial.intuxication.org/hg/s2-liplianin (yesterday Igor synchronized it with current v4l-dvb)

Oops, really bad one :

ovcamchip: v2.27 for Linux 2.6 : OV camera chip I2C driver
Linux video codec intermediate layer: v0.2
usbcore: registered new interface driver ttusb
usbcore: registered new interface driver sms1xxx
usbcore: registered new interface driver ttusb-dec
Linux video capture interface: v2.00
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully
au0828 driver loaded
usbcore: registered new interface driver au0828
usbcore: registered new interface driver dvb_usb_ttusb2
usbcore: registered new interface driver s2255
sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers v1:1.47pre49
usbcore: registered new interface driver sn9c102
usbcore: registered new interface driver dvb_usb_af9015
usbcore: registered new interface driver dvb_usb_af9005
V4L-Driver for Vision CPiA based cameras v1.2.3
Since in-kernel colorspace conversion is not allowed, it is disabled by default now. Users should fix the applications in case they don't work without conversion reenabled by setting the 'colorspace_conv' module parameter to 1
gspca: main v2.4.0 registered
usbcore: registered new interface driver dvb_usb_gp8psk
saa7146: register extension 'budget_ci dvb'.
budget_ci dvb 0000:04:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
saa7146: found saa7146 @ mem ffffc20001096c00 (revision 1, irq 21) (0x13c2,0x100f).
saa7146 (0): dma buffer size 192512
DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI)
adapter has MAC addr = 00:d0:5c:23:a3:9b
input: Budget-CI dvb ir receiver saa7146 (0) as /devices/pci0000:00/0000:00:1e.0/0000:04:00.0/input/input7
DVB: registering adapter 0 frontend 0 (ST STV0299 DVB-S)...
Marvell M88ALP01 'CAFE' Camera Controller version 2
cafe_ccic unable to set up debugfs
OmniVision ov7670 sensor driver, at your service
usbcore: registered new interface driver pctv452e
usbcore: registered new interface driver dvb-usb-tt-connect-s2-3600-01.fw
saa7146: register extension 'budget dvb'.
usbcore: registered new interface driver dvb_usb_digitv
Zoran MJPEG board driver version 0.9.5
No known MJPEG cards found.
usbcore: registered new interface driver dvb_usb_dtt200u
w9968cf: V4L driver for W996[87]CF JPEG USB Dual Mode Camera Chip 1:1.33-basic
usbcore: registered new interface driver w9968cf
usbcore: registered new interface driver dvb_usb_gl861
usbcore: registered new interface driver vicam
usbcore: registered new interface driver dvb_usb_vp7045
usbcore: registered new interface driver zr364xx
zr364xx: Zoran 364xx
usbcore: registered new interface driver dvb_usb_dtv5100
usbcore: registered new interface driver opera1
usbcore: registered new interface driver dvb_usb_cxusb
usbcore: registered new interface driver stkwebcam
zc0301: V4L2 driver for ZC0301[P] Image Processor and Control Chip v1:1.10
usbcore: registered new interface driver zc0301
et61x251: V4L2 driver for ET61X[12]51 PC Camera Controllers v1:1.09
usbcore: registered new interface driver et61x251
usbcore: registered new interface driver dvb_usb_vp702x
dib0700: loaded with support for 8 different device-types
usbcore: registered new interface driver dvb_usb_dib0700
usbcore: registered new interface driver dvb_usb_m920x
usbcore: registered new interface driver dvb_usb_au6610
usbcore: registered new interface driver cinergyT2
vivi: V4L2 device registered as /dev/video0
Video Technology Magazine Virtual Video Capture Board ver 0.5.0 successfully loaded.
usbcore: registered new interface driver b2c2_flexcop_usb
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
usbcore: registered new interface driver stv680
stv680 [usb_stv680_init:1555] 
STV(i): usb camera driver version v0.25 registering<6>stv680: v0.25:STV0680 USB Camera Driver
pwc: Philips webcam module version 10.0.13 loaded.
pwc: Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
pwc: Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
pwc: the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
pwc: Trace options: 0x0001
usbcore: registered new interface driver Philips webcam
usbcore: registered new interface driver dvb_usb_anysee
SE401 usb camera driver version 0.24 registering
usbcore: registered new interface driver se401
usbcore: registered new interface driver dw2102
usbcore: registered new interface driver ov511
ov511: v1.64 for Linux 2.5:ov511 USB Camera Driver
saa7146: register extension 'budget_patch dvb'.
usbcore: registered new interface driver vc032x
vc032x: registered
usbcore: registered new interface driver pac207
pac207: registered
usbcore: registered new interface driver zc3xx
zc3xx: registered
usbcore: registered new interface driver tv8532
tv8532: registered
usbcore: registered new interface driver em28xx
em28xx driver loaded
saa7146: register extension 'hexium gemini'.
usbcore: registered new interface driver ibmcam
usbcore: registered new interface driver STV06xx
STV06xx: registered
bttv: driver version 0.9.17 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
usbcore: registered new interface driver dvb_usb_a800
saa7130/34: v4l2 driver version 0.2.14 loaded
usbcore: registered new interface driver pac7311
pac7311: registered
usbcore: registered new interface driver spca500
spca500: registered
usbcore: registered new interface driver ultracam
usbcore: registered new interface driver ov519
ov519: registered
usbcore: registered new interface driver sonixj
sonixj: registered
saa7146: register extension 'budget_av'.
usbcore: registered new interface driver dvb_usb_dibusb_mb
cpia2: V4L-Driver for Vision CPiA2 based cameras v2.0.0
usbcore: registered new interface driver cpia2
saa7146: register extension 'dvb'.
usbcore: registered new interface driver ov534
ov534: registered
cx2388x alsa driver version 0.0.6 loaded
cx88_audio 0000:04:02.1: PCI INT A -> GSI 23 (level, low) -> IRQ 23
cx88[0]: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,autodetected], frontend(s): 2
cx88[0]: TV tuner type 63, Radio tuner type -1
wm8775' 8-001b: chip found @ 0x36 (cx88[0])
tuner' 8-0061: chip found @ 0xc2 (cx88[0])
tuner' 8-0063: chip found @ 0xc6 (cx88[0])
tveeprom 8-0050: Hauppauge model 69009, rev B2A0, serial# 1241151
tveeprom 8-0050: MAC address is 00-0D-FE-12-F0-3F
tveeprom 8-0050: tuner model is Philips FMD1216ME (idx 100, type 63)
tveeprom 8-0050: TV standards PAL(B/G) PAL(I) SECAM(L/L') PAL(D/D1/K) ATSC/DVB Digital (eeprom 0xf4)
tveeprom 8-0050: audio processor is CX882 (idx 33)
tveeprom 8-0050: decoder processor is CX882 (idx 25)
tveeprom 8-0050: has radio, has IR receiver, has no IR transmitter
cx88[0]: hauppauge eeprom: model=69009
tuner-simple 8-0061: creating new instance
tuner-simple 8-0061: type set to 63 (Philips FMD1216ME MK3 Hybrid Tuner)
input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:04:02.1/input/input8
cx88[0]/1: CX88x/0: ALSA support for cx2388x boards
usbcore: registered new interface driver spca501
spca501: registered
usbcore: registered new interface driver spca506
spca506: registered
usbcore: registered new interface driver usbvision
USBVision USB Video Device Driver for Linux : 0.9.9
usbcore: registered new interface driver dvb_usb_dibusb_mc
usbcore: registered new interface driver finepix
finepix: registered
quickcam_messenger: v0.01:Logitech Quickcam Messenger USB
usbcore: registered new interface driver QCM
usbcore: registered new interface driver mars
mars: registered
usbcore: registered new interface driver conex
conex: registered
usbcore: registered new interface driver spca505
spca505: registered
konicawc: v1.4:Konica Webcam driver
usbcore: registered new interface driver konicawc
USB driver for Vision CPiA based cameras v1.2.3
usbcore: registered new interface driver cpia
vpx3220' 8-0043: chip (8b:8888) found @ 0x86 (cx88[0])
usbcore: registered new interface driver etoms
etoms: registered
usbcore: registered new interface driver dvb_usb_nova_t_usb2
usbcore: registered new interface driver dvb_usb_umt_010
usbcore: registered new interface driver stk014
stk014: registered
usbcore: registered new interface driver spca561
spca561: registered
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
cx8800 0000:04:02.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23
cx88[0]/0: found at 0000:04:02.0, rev: 5, irq: 23, latency: 64, mmio: 0xdb000000
cx88[0]/0: registered device video1 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
cx8800 0000:04:05.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
cx88[1]: subsystem: 14f1:0084, board: Geniatech DVB-S [card=52,autodetected], frontend(s): 1
cx88[1]: TV tuner type 4, Radio tuner type -1
cx88[1]/0: found at 0000:04:05.0, rev: 3, irq: 20, latency: 64, mmio: 0xd9000000
cx88[1]/0: registered device video2 [v4l2]
cx88[1]/0: registered device vbi1
cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded
cx88[0]/2: cx2388x 8802 Driver Manager
cx88-mpeg driver manager 0000:04:02.2: PCI INT A -> GSI 23 (level, low) -> IRQ 23
cx88[0]/2: found at 0000:04:02.2, rev: 5, irq: 23, latency: 64, mmio: 0xdd000000
cx8802_probe() allocating 2 frontend(s)
cx88[1]/2: cx2388x 8802 Driver Manager
cx88-mpeg driver manager 0000:04:05.2: PCI INT A -> GSI 20 (level, low) -> IRQ 20
cx88[1]/2: found at 0000:04:05.2, rev: 3, irq: 20, latency: 64, mmio: 0xda000000
cx8802_probe() allocating 1 frontend(s)
usbcore: registered new interface driver sunplus
sunplus: registered
saa7146: register extension 'hexium HV-PCI6 Orion'.
saa7146: register extension 'Multimedia eXtension Board'.
cx88/2: cx2388x dvb driver version 0.0.6 loaded
cx88/2: registering cx8802 driver, type: dvb access: shared
cx88[0]/2: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68]
BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
IP: [<ffffffffa0abc15a>] vp3054_i2c_probe+0x1a/0x160 [cx88_vp3054_i2c]
PGD 69099067 PUD 69acf067 PMD 0 
Oops: 0000 [#1] PREEMPT SMP 
last sysfs file: /sys/devices/pci0000:00/0000:00:1e.0/0000:04:05.0/video4linux/video2/index
CPU 0 
Modules linked in: cx88_dvb(+) tea6415c(+) mxb hexium_orion gspca_sunplus cx8802 cx8800 mt9m001 gspca_spca561 gspca_stk014 dvb_usb_umt_010 dvb_usb_nova_t_usb2 tda9875 gspca_etoms vpx3220 cpia_usb vp27smpx konicawc upd64031a gspca_spca505 tvaudio bt819 saa7110 gspca_conex gspca_mars quickcam_messenger gspca_finepix cs53l32a dvb_usb_dibusb_mc tvp5150 cx2341x usbvision m52790 gspca_spca506 gspca_spca501 ov772x tuner cx88_alsa gspca_ov534 saa7185 dvb_ttpci ks0127 cpia2 mt9t031 dvb_usb_dibusb_mb saa7114 tw9910 tvp514x budget_av gspca_sonixj gspca_ov519 saa6752hs cs5345 saa5249 soc_camera_platform upd64083 ultracam gspca_spca500 gspca_pac7311 saa7115 saa7134 wm8775 dvb_usb_a800 tda9840 bttv gspca_stv06xx tlv320aic23b saa717x ibmcam hexium_gemini mt9m111 saa7127 msp3400 saa7111 em28xx gspca_tv8532 bt866 tea6420 gspca_zc3xx gspca_pac207 gspca_vc032x saa5246a tda7432 budget_patch ov511 dvb_usb_dw2102 stradis se401 dvb_usb_anysee pwc stv680 uvcvideo b2c2_flexcop_usb vivi dvb_usb_cinergyT2 dvb_usb_au6610 dvb_usb_m920x dvb_usb_dib0700 dvb_usb_vp702x et61x251 zc0301 stkwebcam dvb_usb_cxusb dvb_usb_opera dvb_usb_dtv5100 cx88xx mantis zr364xx saa7146_vv dvb_usb_vp7045 soc_camera vicam dvb_usb_gl861 w9968cf dvb_usb_dtt200u dvb_usb_digitv budget dvb_usb_pctv452e usbvideo ov7670 v4l2_common cafe_ccic budget_ci dvb_usb_gp8psk gspca_main b2c2_flexcop_pci cpia dvb_usb_af9005 dvb_usb_af9015 sn9c102 s2255drv dvb_usb_ttusb2 dvb_usb_dibusb_common budget_core stv0299 pluto2 au0828 dib7000m dib7000p tcm825x dm1105 b2c2_flexcop zr36050 lgdt330x zr36016 videobuf_vmalloc or51132 videodev ttusb_dec zr36060 sms1xxx dib3000mc tuner_simple dvb_usb videobuf_dma_sg dvb_ttusb_budget ir_kbd_i2c or51211 videobuf_dvb stv0288 stb0899 sp887x v4l2_compat_ioctl32 s5h1409 mt2266 tuner_types tda10023 tua6100 mt20xx btcx_risc tda18271 cx22702 videocodec tda10086 tea5767 mt312 s921 dvb_dummy_fe tda8261 qt1010 af9013 cx88_vp3054_i2c tda1004x nxt200x ves1820 bcm3510 saa6588 mxl5007t drx397xD sp8870 lnbp22 tda8290 cx24113 l64781 ir_common cx24110 tda827x saa7146 ttpci_eeprom stb6100 tda10048 tda826x ttusbdecfe s5h1411 lgdt3304 ves1x93 stv0297 dib3000mb tda8083 lnbp21 dibx000_common tda9887 isl6421 mt2060 mb86a16 zl10353 tda10021 dvb_usb_af9005_remote cx22700 s5h1420 mt352 v4l1_compat dvb_core isl6405 xc5000 cu1216 tea5761 mxl5005s dvb_pll au8522 stb6000 v4l2_int_device mt2131 videobuf_core ovcamchip tveeprom lgs8gl5 saa7191 cx24116 cx24123 dib0070 si21xx tuner_xc2028 nxt6000 itd1000 i2c_algo_bit ipv6 coretemp w83627ehf w83791d hwmon_vid hwmon nfs lockd sunrpc firewire_ohci firewire_core crc_itu_t i2c_i801 ohci1394 ieee1394 snd_hda_intel nvidia(P) usb_storage
Pid: 19983, comm: modprobe Tainted: P           2.6.28-gentoo #1
RIP: 0010:[<ffffffffa0abc15a>]  [<ffffffffa0abc15a>] vp3054_i2c_probe+0x1a/0x160 [cx88_vp3054_i2c]
RSP: 0018:ffff880056b0bd18  EFLAGS: 00010246
RAX: ffffffffa10f1080 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffff88007d34b000 R08: 0000000000000000 R09: ffff880069234420
R10: 0000000000000000 R11: 00000000807ca320 R12: ffff880069234420
R13: 0000000000000000 R14: 0000000000c53160 R15: 0000000000c53178
FS:  00007f39b078d6f0(0000) GS:ffffffff80721200(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 000000007f8a9000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process modprobe (pid: 19983, threadinfo ffff880056b0a000, task ffff88007a617a60)
Stack:
 0000000000000070 00000000ffffffed ffff88007d34b000 ffff880069234420
 0000000000000000 ffffffffa110a848 0000000000000000 0000000000000000
 ffff88002da867e0 ffff880056b0bd78 0000000000000000 ffff88007a5458c0
Call Trace:
 [<ffffffffa110a848>] ? cx8802_dvb_probe+0x78/0x1e10 [cx88_dvb]
 [<ffffffff802f3019>] ? __sysfs_add_one+0x39/0xb0
 [<ffffffffa10f272f>] ? cx8802_register_driver+0x1cf/0x258 [cx8802]
 [<ffffffffa110c6a0>] ? dvb_init+0x0/0x30 [cx88_dvb]
 [<ffffffff80209042>] ? _stext+0x42/0x1b0
 [<ffffffff802670bc>] ? load_module+0x177c/0x19b0
 [<ffffffff80247c90>] ? msleep+0x0/0x40
 [<ffffffff802673a5>] ? sys_init_module+0xb5/0x1e0
 [<ffffffff8020bbcb>] ? system_call_fastpath+0x16/0x1b
Code: 7e df 66 66 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec 28 48 89 5c 24 08 48 89 6c 24 10 4c 89 64 24 18 4c 89 6c 24 20 31 db <4c> 8b 27 48 89 fd 41 83 bc 24 c0 06 00 00 2a 74 1b 89 d8 48 8b 
RIP  [<ffffffffa0abc15a>] vp3054_i2c_probe+0x1a/0x160 [cx88_vp3054_i2c]
 RSP <ffff880056b0bd18>
CR2: 0000000000000000
---[ end trace 168efbdd3bf40990 ]---
usbcore: registered new interface driver spca508
spca508: registered
usbcore: registered new interface driver sonixb
sonixb: registered
usbcore: registered new interface driver t613
t613: registered
usbcore: registered new interface driver ALi m5602
ALi m5602: registered
usbcore: registered new interface driver pvrusb2
pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
pvrusb2: Debug mask is 31 (0x1f)
Em28xx: Initialized (Em28xx dvb Extension) extension
saa7134 ALSA driver for DMA sound loaded
saa7134 ALSA: no saa7134 cards found
bt878: AUDIO driver version 0.0.0 loaded
ivtv: Start initialization, version 1.4.0
ivtv: End initialization
Em28xx: Initialized (Em28xx Audio Extension) extension
cx18:  Start initialization, version 1.0.4
cx18:  End initialization
cx2388x blackbird driver version 0.0.6 loaded
cx88/2: registering cx8802 driver, type: blackbird access: shared
cx23885 driver version 0.0.1 loaded
ivtvfb:  no cards found

And then, no more keyboard ??? (Logitech G15 LCD).

> http://hg.kewl.org/dvb2010/ - new dvb scaner 

Thanks, didn't know this one, I'll try :-)

> for me everything is working without any problem with my hvr4000. Also patched vdr 170 works well with s2api

Then go to vdr-1.7.2, and are you like it seems all three "problematic"
users under x86_64 system like us ?
Using diseqc ?

Thanks.
-- 
Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org
               http://picasaweb.google.com/Gregoire.Favre

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sun, 04 Jan 2009 09:14:29 +0100, Goga777 <goga777@bk.ru> wrote:

>> I would suggest not using S2API as it's seems to be broken for our card
>> at this time,
>
> why do you think so ?
>
>> I did test steven s2 repo which is better that all other
>> S2API repo
>
> have you tested http://mercurial.intuxication.org/hg/s2-liplianin ?
>
>> I have tested but still worse than lipliandvb (multiproto
>> hg).
>
> please try
>
> http://mercurial.intuxication.org/hg/s2-liplianin (yesterday Igor  
> synchronized it with current v4l-dvb)
> +
> http://hg.kewl.org/dvb2010/ - new dvb scaner
>
> for me everything is working without any problem with my hvr4000. Also  
> patched vdr 170 works well with s2api

Wow that worked, thanks.
I've installed s2-liplianin and now scan and scan-s2 and http://hg.kewl.org/dvb2010/ works :)
Vdr 1.6.0 works too :)

Thank you all for your help. I hope that it will make it in kernel 2.6.29 :)

Regards,
Roman


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

Re: [linux-dvb] DVB-S Channel searching problem

[Mika Laitio]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 763 bytes --]

> http://mercurial.intuxication.org/hg/s2-liplianin (yesterday Igor synchronized it with current v4l-dvb)
> +
> http://hg.kewl.org/dvb2010/ - new dvb scaner
>
> for me everything is working without any problem with my hvr4000. Also patched vdr 170 works well with s2api

Can you test whether channel switching works for you with
following
- vdr-1.7.2
- vdr-1.7.2-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff
- vdr172_v4ldvb_2g_modulation_support.patch (attached)
- streamdev plugin

I can only watch those channels that I have previously tuned with szap or 
szap2 or vdr.1.6.0? If it works for you, what other cards than hvr-4000 
you have simultaneously connected and does the hvr-4000 be 
/dev/dvb/adapter0 or 1? (for me it's adapter1)


[-- Attachment #2: Type: TEXT/PLAIN, Size: 1598 bytes --]

diff --git a/dvbdevice.c b/dvbdevice.c
index e0b05a1..08dc63f 100644
--- a/dvbdevice.c
+++ b/dvbdevice.c
@@ -32,7 +32,7 @@
 // unpatched driver. However, with an unpatched driver it will not support
 // DVB-S2 hardware. If you have DVB-S2 hardware you need to either patch
 // the driver or modify the line that uses this macro in cDvbDevice::cDvbDevice().
-#define FE_CAN_2ND_GEN_MODULATION 0x10000000
+#define FE_CAN_2G_MODULATION 0x10000000
 
 #define DO_REC_AND_PLAY_ON_PRIMARY_DEVICE 1
 #define DO_MULTIPLE_RECORDINGS 1
@@ -491,7 +491,7 @@ cDvbDevice::cDvbDevice(int n)
   if (fd_frontend >= 0) {
      if (ioctl(fd_frontend, FE_GET_INFO, &frontendInfo) >= 0) {
         switch (frontendInfo.type) {
-          case FE_QPSK: frontendType = (frontendInfo.caps & FE_CAN_2ND_GEN_MODULATION) ? SYS_DVBS2 : SYS_DVBS; break;
+          case FE_QPSK: frontendType = (frontendInfo.caps & FE_CAN_2G_MODULATION) ? SYS_DVBS2 : SYS_DVBS; break;
           case FE_OFDM: frontendType = SYS_DVBT; break;
           case FE_QAM:  frontendType = SYS_DVBC_ANNEX_AC; break;
           case FE_ATSC: frontendType = SYS_ATSC; break;
@@ -505,6 +505,7 @@ cDvbDevice::cDvbDevice(int n)
         if (frontendType == SYS_DVBS2)
            numProvidedSystems++;
         isyslog("device %d provides %s (\"%s\")", CardIndex() + 1, DeliverySystems[frontendType], frontendInfo.name);
+	printf("device %d provides %s (\"%s\")\n", CardIndex() + 1, DeliverySystems[frontendType], frontendInfo.name);
         dvbTuner = new cDvbTuner(fd_frontend, CardIndex(), frontendType);
         }
      }

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sun, 04 Jan 2009 13:42:06 +0100, Mika Laitio <lamikr@pilppa.org> wrote:

>> http://mercurial.intuxication.org/hg/s2-liplianin (yesterday Igor  
>> synchronized it with current v4l-dvb)
>> +
>> http://hg.kewl.org/dvb2010/ - new dvb scaner
>>
>> for me everything is working without any problem with my hvr4000. Also  
>> patched vdr 170 works well with s2api
>
> Can you test whether channel switching works for you with
> following
> - vdr-1.7.2
> -  
> vdr-1.7.2-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff
> - vdr172_v4ldvb_2g_modulation_support.patch (attached)
> - streamdev plugin
>
> I can only watch those channels that I have previously tuned with szap or
> szap2 or vdr.1.6.0? If it works for you, what other cards than hvr-4000
> you have simultaneously connected and does the hvr-4000 be
> /dev/dvb/adapter0 or 1? (for me it's adapter1)
>

I've tried clean vdr 1.7.2 (without patches) and it doesn't work (works sometimes).
When I try to change channels in vdr 1.7.2 I see in log:
Jan  4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel 437, tp 110743               
Jan  4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while tuning to channel 437, tp 110743

Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.

But vdr 1.6 works

Roman

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

Re: [linux-dvb] DVB-S Channel searching problem

[Goga777]

> I've tried clean vdr 1.7.2 (without patches) and it doesn't work (works sometimes).
> When I try to change channels in vdr 1.7.2 I see in log:
> Jan  4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel 437, tp 110743               
> Jan  4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while tuning to channel 437, tp 110743
> 
> Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.
> 
> But vdr 1.6 works


can you try vdr 170 ?

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sun, 04 Jan 2009 15:56:38 +0100, Goga777 <goga777@bk.ru> wrote:

>> I've tried clean vdr 1.7.2 (without patches) and it doesn't work (works  
>> sometimes).
>> When I try to change channels in vdr 1.7.2 I see in log:
>> Jan  4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel  
>> 437, tp 110743
>> Jan  4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while tuning  
>> to channel 437, tp 110743
>>
>> Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.
>>
>> But vdr 1.6 works
>
>
> can you try vdr 170 ?
>

Doesn't compile
dvbdevice.h:34: error: ‘dvbfe_delsys’ does not name a type

Roman

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

Re: [linux-dvb] DVB-S Channel searching problem

[Goga777]

> >> I've tried clean vdr 1.7.2 (without patches) and it doesn't work (works  
> >> sometimes).
> >> When I try to change channels in vdr 1.7.2 I see in log:
> >> Jan  4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel  
> >> 437, tp 110743
> >> Jan  4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while tuning  
> >> to channel 437, tp 110743
> >>
> >> Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.
> >>
> >> But vdr 1.6 works
> >
> >
> > can you try vdr 170 ?
> >
> 
> Doesn't compile
> dvbdevice.h:34: error: ‘dvbfe_delsys’ does not name a type


of course you should install 2 patches for vdr 170

http://www.linuxtv.org/pipermail/vdr/attachments/20080413/1054bcfb/attachment-0001.bin
vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2

http://www.linuxtv.org/pipermail/vdr/attachments/20081007/edcd3fcc/attachment-0001.obj
vdr-1.7.0-s2api-07102008-h264-clean.patch.gz


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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sun, 04 Jan 2009 22:24:04 +0100, Goga777 <goga777@bk.ru> wrote:

>> >> I've tried clean vdr 1.7.2 (without patches) and it doesn't work  
>> (works
>> >> sometimes).
>> >> When I try to change channels in vdr 1.7.2 I see in log:
>> >> Jan  4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel
>> >> 437, tp 110743
>> >> Jan  4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while  
>> tuning
>> >> to channel 437, tp 110743
>> >>
>> >> Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.
>> >>
>> >> But vdr 1.6 works
>> >
>> >
>> > can you try vdr 170 ?
>> >
>>
>> Doesn't compile
>> dvbdevice.h:34: error: ‘dvbfe_delsys’ does not name a type
>
>
> of course you should install 2 patches for vdr 170
>
> http://www.linuxtv.org/pipermail/vdr/attachments/20080413/1054bcfb/attachment-0001.bin
> vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2
>
> http://www.linuxtv.org/pipermail/vdr/attachments/20081007/edcd3fcc/attachment-0001.obj
> vdr-1.7.0-s2api-07102008-h264-clean.patch.gz
>
>

Channel switching doesn't work in 1.7.0 too

Roman

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Mon, 05 Jan 2009 18:43:23 +0100, Roman Jarosz <roman.jarosz@gmail.com> wrote:

> On Sun, 04 Jan 2009 22:24:04 +0100, Goga777 <goga777@bk.ru> wrote:
>
>>> >> I've tried clean vdr 1.7.2 (without patches) and it doesn't work
>>> (works
>>> >> sometimes).
>>> >> When I try to change channels in vdr 1.7.2 I see in log:
>>> >> Jan  4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel
>>> >> 437, tp 110743
>>> >> Jan  4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while
>>> tuning
>>> >> to channel 437, tp 110743
>>> >>
>>> >> Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.
>>> >>
>>> >> But vdr 1.6 works
>>> >
>>> >
>>> > can you try vdr 170 ?
>>> >
>>>
>>> Doesn't compile
>>> dvbdevice.h:34: error: ‘dvbfe_delsys’ does not name a type
>>
>>
>> of course you should install 2 patches for vdr 170
>>
>> http://www.linuxtv.org/pipermail/vdr/attachments/20080413/1054bcfb/attachment-0001.bin
>> vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2
>>
>> http://www.linuxtv.org/pipermail/vdr/attachments/20081007/edcd3fcc/attachment-0001.obj
>> vdr-1.7.0-s2api-07102008-h264-clean.patch.gz
>>
>>
>
> Channel switching doesn't work in 1.7.0 too
>
> Roman
>

Sorry it works, i've forgot that I've changed hostname.
So only 1.7.2 doesn't work (and maybe 1.7.1)

Regards,
Roman


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

Re: [linux-dvb] DVB-S Channel searching problem

[Goga777]

> >>> >> I've tried clean vdr 1.7.2 (without patches) and it doesn't work
> >>> (works
> >>> >> sometimes).
> >>> >> When I try to change channels in vdr 1.7.2 I see in log:
> >>> >> Jan  4 13:57:43 blackbox vdr: [3250] frontend 0 lost lock on channel
> >>> >> 437, tp 110743
> >>> >> Jan  4 13:57:45 blackbox vdr: [3250] frontend 0 timed out while
> >>> tuning
> >>> >> to channel 437, tp 110743
> >>> >>
> >>> >> Btw I don't use hvr-4000 I have only one TeVii S460 DVB-S/S2 card.
> >>> >>
> >>> >> But vdr 1.6 works
> >>> >
> >>> >
> >>> > can you try vdr 170 ?
> >>> >
> >>>
> >>> Doesn't compile
> >>> dvbdevice.h:34: error: ‘dvbfe_delsys’ does not name a type
> >>
> >>
> >> of course you should install 2 patches for vdr 170
> >>
> >> http://www.linuxtv.org/pipermail/vdr/attachments/20080413/1054bcfb/attachment-0001.bin
> >> vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2
> >>
> >> http://www.linuxtv.org/pipermail/vdr/attachments/20081007/edcd3fcc/attachment-0001.obj
> >> vdr-1.7.0-s2api-07102008-h264-clean.patch.gz
> >>
> >>
> >
> > Channel switching doesn't work in 1.7.0 too
> >
> > Roman
> >
> 
> Sorry it works, i've forgot that I've changed hostname.
> So only 1.7.2 doesn't work (and maybe 1.7.1)

nobody nowhere promised that vdr 172 will work on dvb-s2 budget cards currently 
please waiting for update version of vdr-xine/xineliboutput/softdevice and using vdr 170 now

Goga



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

Re: [linux-dvb] DVB-S Channel searching problem

[Mika Laitio]

> of course you should install 2 patches for vdr 170
>
> http://www.linuxtv.org/pipermail/vdr/attachments/20080413/1054bcfb/attachment-0001.bin
> vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2
>
> http://www.linuxtv.org/pipermail/vdr/attachments/20081007/edcd3fcc/attachment-0001.obj
> vdr-1.7.0-s2api-07102008-h264-clean.patch.gz

Ok tested now with S2API drivers from liplianis repository with
vdr-1.7.0 and those 2 patches applied. Result is that the scanning fails 
just in a similar way than what it happens with vdr-1.7.2 either with 
dv4-v4l or with liplianis version of S2API drivers.

If I had first tuned for example to arte with vdr-1.6.0 or szap and then 
closed vdr-1.6.0/szap, I can watch arte with vdr-1.7.0 or with vdr-1.7.2

But switching to some other dvb-t or dvb-s channels will fail.

(hvr-1300 + hvr-4000)

Mika

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sat, 03 Jan 2009 19:58:45 +0100, Alex Betis <alex.betis@gmail.com> wrote:

>> I use scan from dvb-apps, the command is
>> "scan -o vdr /root/dvb/Astra-19.2E > /etc/vdr/channels.conf"
>> where /root/dvb/Astra-19.2E is file with "S 11567500 V 22000000 5/6"
>
> I think that's the main issue. *BOUWSMA w*rote that its ok to rely on
> astra's maintainers and connect to any transponder is enough to get a  
> list
> of all others. I personaly don't trust those maintainers since I saw too
> many errors in NIT messages that specify the transponder, so I specify  
> all
> the frequencies I want to scan. I don't have a dish to 19.2, but there  
> were
> many errors with 5 other satellites I have.
> You can get a list of those frequencies here:
> http://www.lyngsat.com/astra19.html

Could you tell me how? I've tried with S 12188000 H 27500000 3/4 and
it doesn't find anything.

>
>
>>
>> I use cx88-dvb driver but many modules are loaded with it see
>> http://kedge.wz.cz/dvb/lsmod.txt
>
> I meant to ask what is the origin of the driver. I use Igor's driver  
> from:
> http://mercurial.intuxication.org/hg/s2-liplianin/

I use driver from vanilla kernel 2.6.28 which have DVB api version 5.0.

> If you have a S2API driver (or will use Igor's driver), you can use my
> scan-s2 application with many changes in NIT parsing that might resolve  
> your
> issue.
> http://mercurial.intuxication.org/hg/scan-s2/
>

See below.

>>
>> Scan console output is in file http://kedge.wz.cz/dvb/channels.conf
>> and the result in http://kedge.wz.cz/dvb/channels.conf
>
> You've posted the same link for both outputs. Please post console output
> when you run scan with "-v" parameter. Maybe even with "-vv".
>

The console output should be http://kedge.wz.cz/dvb/scanconsoleout.txt.

I've tried to run scan and scan-s2 on "S 12188000 H 27500000 3/4"
were the "RTL 2 Deutschland" channel should be and neither scan found anything.

The console outputs are here:
http://kedge.wz.cz/dvb/scan.txt
http://kedge.wz.cz/dvb/scans2.txt


If you want me to run the whole scan for "S 11567500 V 22000000 5/6" with -vv
let me know and I'll do it.

>>
>> When console shows
>> __tune_to_transponder:1508: ERROR: Setting frontend parameters failed:  
>> 22
>> Invalid argument
>>
>> the dmesg prints
>> DVB: adapter 0 frontend 0 frequency 8175750 out of range  
>> (950000..2150000)
>
> It could be anything. Bad NIT message (most probably) or a memory  
> smashing
> in scan application.
>
>
>>
>>
>> Roman
>>
>> _______________________________________________
>> 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] DVB-S Channel searching problem

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 3263 bytes --]

On Sat, Jan 3, 2009 at 9:39 PM, Roman Jarosz <roman.jarosz@gmail.com> wrote:

> On Sat, 03 Jan 2009 19:58:45 +0100, Alex Betis <alex.betis@gmail.com>
> wrote:
>
> >> I use scan from dvb-apps, the command is
> >> "scan -o vdr /root/dvb/Astra-19.2E > /etc/vdr/channels.conf"
> >> where /root/dvb/Astra-19.2E is file with "S 11567500 V 22000000 5/6"
> >
> > I think that's the main issue. *BOUWSMA w*rote that its ok to rely on
> > astra's maintainers and connect to any transponder is enough to get a
> > list
> > of all others. I personaly don't trust those maintainers since I saw too
> > many errors in NIT messages that specify the transponder, so I specify
> > all
> > the frequencies I want to scan. I don't have a dish to 19.2, but there
> > were
> > many errors with 5 other satellites I have.
> > You can get a list of those frequencies here:
> > http://www.lyngsat.com/astra19.html
>
> Could you tell me how? I've tried with S 12188000 H 27500000 3/4 and
> it doesn't find anything.

Try also scan-s2 with:
S 12188000 H 27500000 3/4 AUTO QPSK


>
> >
> >
> >>
> >> I use cx88-dvb driver but many modules are loaded with it see
> >> http://kedge.wz.cz/dvb/lsmod.txt
> >
> > I meant to ask what is the origin of the driver. I use Igor's driver
> > from:
> > http://mercurial.intuxication.org/hg/s2-liplianin/
>
> I use driver from vanilla kernel 2.6.28 which have DVB api version 5.0.
>
> > If you have a S2API driver (or will use Igor's driver), you can use my
> > scan-s2 application with many changes in NIT parsing that might resolve
> > your
> > issue.
> > http://mercurial.intuxication.org/hg/scan-s2/
> >
>
> See below.
>
> >>
> >> Scan console output is in file http://kedge.wz.cz/dvb/channels.conf
> >> and the result in http://kedge.wz.cz/dvb/channels.conf
> >
> > You've posted the same link for both outputs. Please post console output
> > when you run scan with "-v" parameter. Maybe even with "-vv".
> >
>
> The console output should be http://kedge.wz.cz/dvb/scanconsoleout.txt.
>
> I've tried to run scan and scan-s2 on "S 12188000 H 27500000 3/4"
> were the "RTL 2 Deutschland" channel should be and neither scan found
> anything.
>
> The console outputs are here:
> http://kedge.wz.cz/dvb/scan.txt
> http://kedge.wz.cz/dvb/scans2.txt

I don't see any problem with scan output. I don't have the same card as
yours, so only guessing...

Do you have a diseqc on the way?


>
>
>
> If you want me to run the whole scan for "S 11567500 V 22000000 5/6" with
> -vv
> let me know and I'll do it.

No, no need.

>
>
> >>
> >> When console shows
> >> __tune_to_transponder:1508: ERROR: Setting frontend parameters failed:
> >> 22
> >> Invalid argument
> >>
> >> the dmesg prints
> >> DVB: adapter 0 frontend 0 frequency 8175750 out of range
> >> (950000..2150000)
> >
> > It could be anything. Bad NIT message (most probably) or a memory
> > smashing
> > in scan application.
> >
> >
> >>
> >>
> >> Roman
> >>
> >> _______________________________________________
> >> 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
>

[-- Attachment #1.2: Type: text/html, Size: 5706 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] DVB-S Channel searching problem

[Roman Jarosz]

On Sat, 03 Jan 2009 21:48:45 +0100, Alex Betis <alex.betis@gmail.com> wrote:

> On Sat, Jan 3, 2009 at 9:39 PM, Roman Jarosz <roman.jarosz@gmail.com>  
> wrote:
>
>> On Sat, 03 Jan 2009 19:58:45 +0100, Alex Betis <alex.betis@gmail.com>
>> wrote:
>>
>> >> I use scan from dvb-apps, the command is
>> >> "scan -o vdr /root/dvb/Astra-19.2E > /etc/vdr/channels.conf"
>> >> where /root/dvb/Astra-19.2E is file with "S 11567500 V 22000000 5/6"
>> >
>> > I think that's the main issue. *BOUWSMA w*rote that its ok to rely on
>> > astra's maintainers and connect to any transponder is enough to get a
>> > list
>> > of all others. I personaly don't trust those maintainers since I saw  
>> too
>> > many errors in NIT messages that specify the transponder, so I specify
>> > all
>> > the frequencies I want to scan. I don't have a dish to 19.2, but there
>> > were
>> > many errors with 5 other satellites I have.
>> > You can get a list of those frequencies here:
>> > http://www.lyngsat.com/astra19.html
>>
>> Could you tell me how? I've tried with S 12188000 H 27500000 3/4 and
>> it doesn't find anything.
>
> Try also scan-s2 with:
> S 12188000 H 27500000 3/4 AUTO QPSK

No luck :( http://kedge.wz.cz/dvb/scans2_2.txt


> Do you have a diseqc on the way?

No. I don't.



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

Re: [linux-dvb] DVB-S Channel searching problem

[Alex Betis]

[-- Attachment #1.1: Type: text/plain, Size: 1631 bytes --]

On Sat, Jan 3, 2009 at 10:59 PM, Roman Jarosz <roman.jarosz@gmail.com>wrote:

> On Sat, 03 Jan 2009 21:48:45 +0100, Alex Betis <alex.betis@gmail.com>
> wrote:
>
> > On Sat, Jan 3, 2009 at 9:39 PM, Roman Jarosz <roman.jarosz@gmail.com>
> > wrote:
> >
> >> On Sat, 03 Jan 2009 19:58:45 +0100, Alex Betis <alex.betis@gmail.com>
> >> wrote:
> >>
> >> >> I use scan from dvb-apps, the command is
> >> >> "scan -o vdr /root/dvb/Astra-19.2E > /etc/vdr/channels.conf"
> >> >> where /root/dvb/Astra-19.2E is file with "S 11567500 V 22000000 5/6"
> >> >
> >> > I think that's the main issue. *BOUWSMA w*rote that its ok to rely on
> >> > astra's maintainers and connect to any transponder is enough to get a
> >> > list
> >> > of all others. I personaly don't trust those maintainers since I saw
> >> too
> >> > many errors in NIT messages that specify the transponder, so I specify
> >> > all
> >> > the frequencies I want to scan. I don't have a dish to 19.2, but there
> >> > were
> >> > many errors with 5 other satellites I have.
> >> > You can get a list of those frequencies here:
> >> > http://www.lyngsat.com/astra19.html
> >>
> >> Could you tell me how? I've tried with S 12188000 H 27500000 3/4 and
> >> it doesn't find anything.
> >
> > Try also scan-s2 with:
> > S 12188000 H 27500000 3/4 AUTO QPSK
>
> No luck :( http://kedge.wz.cz/dvb/scans2_2.txt

Have no more ideas. Probably a driver problem.



>
>
> > Do you have a diseqc on the way?
>
> No. I don't.


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

[-- Attachment #1.2: Type: text/html, Size: 3068 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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

Re: [linux-dvb] DVB-S Channel searching problem

[BOUWSMA Barry]

On Sat, 3 Jan 2009, Roman Jarosz wrote:

> > I think that's the main issue. *BOUWSMA w*rote that its ok to rely on
> > astra's maintainers and connect to any transponder is enough to get a  
> > list
> > of all others. I personaly don't trust those maintainers since I saw too
> > many errors in NIT messages that specify the transponder, so I specify  
> > all
> > the frequencies I want to scan. I don't have a dish to 19.2, but there  

Another reason why one might want to list all the frequencies
particularly for 19E2 is that presently quite a few transponders
are still analogue, but within a year or so will become digital.
Often a digital transponder is fired up but not added to the
NIT tables until officially going into service.

The frequencies used at 19E2 are well known, as are the related
parameters -- present analogue channels will use the same
frequencies with steps 14750kHz, SR22000, and 5/6, as the
existing ex-analogue channels -- unless they get put into
DVB-S2 service.  There have been a small number of temporary
variants, though:  12728 was SR 19890 for a short while...

I have seen one or two mistakes added to the NIT tables at
this position; somehow a 11475+27500 alleged transponder was
added, and I also have seen an Intermediate Frequency added
in one or two cases, which is clearly human error.



> Could you tell me how? I've tried with S 12188000 H 27500000 3/4 and
> it doesn't find anything.
> The console outputs are here:
> http://kedge.wz.cz/dvb/scan.txt

For some reason, your card is unable to lock onto that
transponder, at least from `scan' -- seen by the tuning
status values never going above 0x1 or 0x3, which is
usually the case when no transponder is present, or the
parameters given are incorrect.

But then you said early that you could manually zap to
this frequency and see RTL...

In fact, as I look at the result of your scan, you are
only able to tune in very few of the transponders which
you should receive -- perhaps less than a third.

Oh, your bogus IF is still present toward the end of the
scan:
>>> tune to: 1574:h:S19.2E:22000:
DVB-S IF freq is 8175750
Obviously 1,574GHz is not a Ku-band transponder, but
rather the IF of the local oscillator at 9,75GHz, for
a frequency of 11,324GHz, or at 10,6GHz for 12,174GHz
which is in the band where SR27500 is used -- though
I vaguely recall there also being a frequency provided
well above 12750...

I see no regular pattern in transponders that fail to
tune.  `scan -v' will show how many attempts it takes
to tune those transponders with success; I believe the
`-5' option does not lengthen the time permitted for
a lock to be obtained, but it wouldn't hurt to try it,
I think (it normally is used where the data sent does
not cycle around in a short time as it should).

In general, I expect my tuners to lock onto a good signal
such as Astra in one, and no more than two tuning status
lines.  But I've seen other scan results where lock is not
obtained so quickly...


barry bouwsma
needs sleep badly

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

Re: [linux-dvb] DVB-S Channel searching problem

[Eduard Huguet]

[-- Attachment #1.1: Type: text/plain, Size: 1203 bytes --]

>
> ---------- Missatge reenviat ----------
> From: "Alex Betis" <alex.betis@gmail.com>
> To: kedgedev@centrum.cz
> Date: Sat, 3 Jan 2009 22:48:45 +0200
> Subject: Re: [linux-dvb] DVB-S Channel searching problem


Hi,
    I've been more or less following this message thread. I just wanted to
share that I've never been able to perform a succesfult channel scan for
Astra 19.2 with my DVB-S card (which is an Avermedia DVB-S Pro, absolutely
not related to yours, but anyway...).

I suspect that it's some kind of driver problem that makes the card unable
to lock onto any of the frecuencies listed in default dvb-utils supplied
Astra-19.2 file. This file seems to contain a very small set of basic
frecuencies (only 2 im I'm not wrong, at least in Gentoo...). I don't know
if this should be enough, but anyway never worked for me.

However, I discovered a page that seems to maintain a more complete set of
frecuency files. Here you have the link for them:

    http://joshyfun.peque.org/transponders/kaffeine.html

Although they are referred as "Kaffeine" format they are perfectly
compatible with dvb-utils 'scan' program. Give them a try, they worked
perfect for me :D

Best regards,
  Eduard Huguet

[-- Attachment #1.2: Type: text/html, Size: 1725 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

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