[linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Moles Blanco]

Hi everyone,

i've got 2 satellite dishes home and a diseqc 2.0.

i've been using ubuntu/kubuntu for quite a while now but until hardy
came out, i couldn't use my "lifeview pci trio" pci card at all, as i
want it to work throught diseqc, to get channels from both dishes, so i
kept going back to windows, unfortunately.

The thing is that my whole setup works, as i've got a machine with dual
boot and window xp installed on one partition. Needless to say that i
can , with prodvb, altdvb, etc, tune both satellites through diseqc.

so... when hardy came out i decided to try again... i downloaded the cd,
i386 version and installed. I almost went crazy when i launched kaffeine
and i was able to tune channels from both satellites... almost out of
the box!!! i hadn't been able to do this in earlier versions (well... a
part from having to call modprobe saa7134 front_end=1 to use the
satellite chip)

so... i searched for all the channels with kaffeine and i started
watching channels without any problem.

Then, i had the bad idea of doing

apt-get update
apt-get upgrade

i didn't get any error message at all... but when i ran kaffeine
again..... no channels could be viewed.

Then i started to go crazy trying to get it working again. I deleted the
whole list of channels and tried to tune again... with no luck... i
would only get channels from one satellite, that on on switch 1 in the
diseqc.

After 2 days i loaded windows to see if i had broken something... but i
hadn't, everything was working fine there.

then i loaded the old kernel, linux-image-2.6.24-19-generic, then the
updated one again linux-image-2.6.24-22-generic

then i tried to go back to an earlier version of kaffeine (just in case)

i'm using 0.8.6-0ubuntu8.3 and i went back to 0.8.6-0ubuntu8.1 and even
0.8.6-0ubuntu8

no luck with all that.

and then i found out how to scan channels from command line, and i saw
that no matter what switch you tell saa7134 to scan on, i will always go
to "switch 1" on the diseqc.

here's what i got from scanning........

switch 1 (astra 28.2E)

********
scan -s 1 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-28.2E
>>> tune to: 10729:v:1:22000
0x0000 0x206c: pmt_pid 0x0100 BSkyB -- E4+1 (running)
0x0000 0x2071: pmt_pid 0x0103 BSkyB -- E4 (running)
0x0000 0x2077: pmt_pid 0x0101 BSkyB -- Channel 4 +1 (running)
0x0000 0x2078: pmt_pid 0x0102 BSkyB -- Channel 4 +1 (running)
0x0000 0x2079: pmt_pid 0x010f BSkyB -- Channel 4 +1 (running)
0x0000 0x207a: pmt_pid 0x0107 BSkyB -- Channel 4 +1 (running)
0x0000 0x207b: pmt_pid 0x0108 BSkyB -- Channel 4 +1 (running, scrambled)
0x0000 0x207c: pmt_pid 0x010a BSkyB -- Channel 4 +1 (running)
0x0000 0x2094: pmt_pid 0x010c BSkyB -- More4 (running)
0x0000 0x20c5: pmt_pid 0x0106 BSkyB -- 8389 (running, scrambled)
0x0000 0x23f7: pmt_pid 0x0104 BSkyB -- c4 l +1 (running)
0x0000 0x23f8: pmt_pid 0x0109 BSkyB -- e4 (running)
********

switch 2 (astra 19E)
********
scan -s 2 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E
>>> tune to: 10788:v:2:22000
0x0000 0x283d: pmt_pid 0x0100 BSkyB -- BBC 1 W Mids (running)
0x0000 0x283e: pmt_pid 0x0101 BSkyB -- BBC 1 N West (running)
0x0000 0x283f: pmt_pid 0x0102 BSkyB -- BBC 1 Yrks&Lin (running)
0x0000 0x2840: pmt_pid 0x0103 BSkyB -- BBC 1 Yorks (running)
0x0000 0x2841: pmt_pid 0x0104 BSkyB -- BBC 1 E Mids (running)
0x0000 0x2842: pmt_pid 0x0105 BSkyB -- BBC 1 East (E) (running)
0x0000 0x2851: pmt_pid 0x0106 BSkyB -- ETV5 (running)
********

And this is the problem!!! on Astra-19.2 there's no "BBC 1 W Mids". It's
getting signal from switch 1 and scanning from the correct transponders
list on  /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E

And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
3", it will always scan from "switch 1"

through kaffeine i get to the same point, i get a scan on swith 1 only.

is this a bug? has anyone experienced this? is there a warkaround for
this? how could i get it working in the first place?
what could i break by upgrading the system?

Please, let me know if i can provide any further information.

here are my system details:

********
# lsb_release -rd

Description:    Ubuntu 8.04.1
Release:        8.04
**********

i've looked through the system logs and i can't find anything, nothing
related to diseqc or kaffeine, there seem to be no errors with those words.

Thanks.



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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[BOUWSMA Barry]

On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:

> here's what i got from scanning........
> 
> switch 1 (astra 28.2E)
> 
> ********
> scan -s 1 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-28.2E
> >>> tune to: 10729:v:1:22000
> 0x0000 0x206c: pmt_pid 0x0100 BSkyB -- E4+1 (running)

> 
> switch 2 (astra 19E)
> ********
> scan -s 2 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E
> >>> tune to: 10788:v:2:22000
> 0x0000 0x283d: pmt_pid 0x0100 BSkyB -- BBC 1 W Mids (running)

You are correct, this is a transponder at 28E2 which
shares freq,pol+sr with 19E2...


> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
> 3", it will always scan from "switch 1"

Try with -s 0; I'm not sure if it is always the case,
but my unhacked `scan' uses 0-3 for DiSEqC positions
1/4 to 4/4 -- I've hacked this to use the range of 1-4
on all my `scan' and related tuning/streaming utilities.


Personally, I prefer `0' to mean no DiSEqC at all, A/B
as appropriate, and 1-4 to match all consumer equipment
I've got my hands on (or A-D), but that's me...


barry bouwsma

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Moles Blanco]

En/na BOUWSMA Barry ha escrit:
> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
>
>   
>> here's what i got from scanning........
>>
>> switch 1 (astra 28.2E)
>>
>> ********
>> scan -s 1 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-28.2E
>>     
>>>>> tune to: 10729:v:1:22000
>>>>>           
>> 0x0000 0x206c: pmt_pid 0x0100 BSkyB -- E4+1 (running)
>>     
>
>   
>> switch 2 (astra 19E)
>> ********
>> scan -s 2 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E
>>     
>>>>> tune to: 10788:v:2:22000
>>>>>           
>> 0x0000 0x283d: pmt_pid 0x0100 BSkyB -- BBC 1 W Mids (running)
>>     
>
> You are correct, this is a transponder at 28E2 which
> shares freq,pol+sr with 19E2...
>
>
>   
>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
>> 3", it will always scan from "switch 1"
>>     
>
> Try with -s 0; I'm not sure if it is always the case,
> but my unhacked `scan' uses 0-3 for DiSEqC positions
> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
> on all my `scan' and related tuning/streaming utilities.
>
>
> Personally, I prefer `0' to mean no DiSEqC at all, A/B
> as appropriate, and 1-4 to match all consumer equipment
> I've got my hands on (or A-D), but that's me...
>
>
> barry bouwsma
>   

hi, thanks for anwsering.

I've already tried that.

remember, on switch 1 i've got astra 28.2E and on switch 2 i've got 
astra 19E

no matter what i try...

scan -s 0 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-28.2E
scan -s 0 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E
scan -s 1 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E
scan -s 1 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-28.2E
scan -s 2 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-19.2E
scan -s 2 /home/servidor/.kde/share/apps/kaffeine/dvb-s/Astra-28.2E


i always get signal from Astra 28.2E

and if i switch cables and i put Astra 19E on switch 1 i'll always get 
signal from Astra 19.2.

I don't why but it looks like it doesn't know how to switch to "switch 2"

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[BOUWSMA Barry]

On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:

> > > And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
> > > 3", it will always scan from "switch 1"
> > >     
> > 
> > Try with -s 0; I'm not sure if it is always the case,
> > but my unhacked `scan' uses 0-3 for DiSEqC positions
> > 1/4 to 4/4 -- I've hacked this to use the range of 1-4


> hi, thanks for anwsering.
> I've already tried that.
> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E

I realized soon after sending my reply, that I had probably
confused myself about which inputs you had where, and my
advice, while partly correct, wouldn't help...

Anyway -- the important thing to remember, is that if your
`scan' works as I expect and your kernel modules work properly
and you have a 2/1 DiSEqC switch, that scan -s option...
 0 -- will tune to position 1/2;
 1 -- will tune to position 2/2;
 2 -- will cycle back and tune position 1/2;
 3 -- will again tune position 2/2
 4 -- should spit a warning, I think (something does)

In other words -- if your system worked properly, `-s 1'
would give you 19E2 and `-s 2' would give you 28E; the
opposite of your switch labels.



> I don't why but it looks like it doesn't know how to switch to "switch 2"

If I understand from your original post (re-reading it;
as soon as people start posting distribution or system
details my eyes sort of glaze over, while other people
will get an `aha!' moment that shall remain elusive to
me)...

An older kernel version + modules worked;
an update of those modules broke DiSEqC;
your original kernel and modules didn't support your card.

What I would suggest -- keeping in mind that the dvb kernel
modules, which you should see with `lsmod', are where you
should find correct support, are probably in some package
unknown to me which you'd need to downgrade -- would be to
either revert, if possible, whatever contains those modules,
or jump ahead several kernel versions.

If you feel comfortable compiling and installing a newer
kernel (which is now around the 2.6.28 area), you could do
that.

Alternatively, and possibly better, would be to upgrade
only the linux-dvb kernel modules, building them against
your 2.6.24-era kernel source, which you may need to
download and install.

It's simple to download and build the latest linux-dvb
modules even against a 2.6.24 kernel, and that should
make things work -- if not, then something's been broken
for a while, and some expert should be able to help you.


barryb ouwsma

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Molse]

En/na BOUWSMA Barry ha escrit:
> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
>
>   
>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
>>>> 3", it will always scan from "switch 1"
>>>>     
>>>>         
>>> Try with -s 0; I'm not sure if it is always the case,
>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
>>>       
>
>
>   
>> hi, thanks for anwsering.
>> I've already tried that.
>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
>>     
>
> I realized soon after sending my reply, that I had probably
> confused myself about which inputs you had where, and my
> advice, while partly correct, wouldn't help...
>
> Anyway -- the important thing to remember, is that if your
> `scan' works as I expect and your kernel modules work properly
> and you have a 2/1 DiSEqC switch, that scan -s option...
>  0 -- will tune to position 1/2;
>  1 -- will tune to position 2/2;
>  2 -- will cycle back and tune position 1/2;
>  3 -- will again tune position 2/2
>  4 -- should spit a warning, I think (something does)
>
> In other words -- if your system worked properly, `-s 1'
> would give you 19E2 and `-s 2' would give you 28E; the
> opposite of your switch labels.
>
>
>
>   
>> I don't why but it looks like it doesn't know how to switch to "switch 2"
>>     
>
> If I understand from your original post (re-reading it;
> as soon as people start posting distribution or system
> details my eyes sort of glaze over, while other people
> will get an `aha!' moment that shall remain elusive to
> me)...
>
> An older kernel version + modules worked;
> an update of those modules broke DiSEqC;
> your original kernel and modules didn't support your card.
>
> What I would suggest -- keeping in mind that the dvb kernel
> modules, which you should see with `lsmod', are where you
> should find correct support, are probably in some package
> unknown to me which you'd need to downgrade -- would be to
> either revert, if possible, whatever contains those modules,
> or jump ahead several kernel versions.
>
> If you feel comfortable compiling and installing a newer
> kernel (which is now around the 2.6.28 area), you could do
> that.
>
> Alternatively, and possibly better, would be to upgrade
> only the linux-dvb kernel modules, building them against
> your 2.6.24-era kernel source, which you may need to
> download and install.
>
> It's simple to download and build the latest linux-dvb
> modules even against a 2.6.24 kernel, and that should
> make things work -- if not, then something's been broken
> for a while, and some expert should be able to help you.
>
>
> barryb ouwsma
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   

Hi again,

and thanks for the info.

Unfortunately, diseqc seems broken, because no matter what i try

-s 0, 1 , 2 ,3.... i get 28.2E signal

however, 4 shows an error, as you said.

It used to work... so i'll try to get back or compile new linux-dvb 
module as you suggested.

i'm really really newbie in this, i'm using kubuntu, so imagine.... 
hahahaha.

i don't even know how to get started, i barely install thing by "apt-get"

i'll try to find the way or post instead my problem in an ubuntu forum.

thanks for the info.

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[hermann pitton]

Hi,

Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
> En/na BOUWSMA Barry ha escrit:
> > On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
> >
> >   
> >>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
> >>>> 3", it will always scan from "switch 1"
> >>>>     
> >>>>         
> >>> Try with -s 0; I'm not sure if it is always the case,
> >>> but my unhacked `scan' uses 0-3 for DiSEqC positions
> >>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
> >>>       
> >
> >
> >   
> >> hi, thanks for anwsering.
> >> I've already tried that.
> >> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
> >>     
> >
> > I realized soon after sending my reply, that I had probably
> > confused myself about which inputs you had where, and my
> > advice, while partly correct, wouldn't help...
> >
> > Anyway -- the important thing to remember, is that if your
> > `scan' works as I expect and your kernel modules work properly
> > and you have a 2/1 DiSEqC switch, that scan -s option...
> >  0 -- will tune to position 1/2;
> >  1 -- will tune to position 2/2;
> >  2 -- will cycle back and tune position 1/2;
> >  3 -- will again tune position 2/2
> >  4 -- should spit a warning, I think (something does)
> >
> > In other words -- if your system worked properly, `-s 1'
> > would give you 19E2 and `-s 2' would give you 28E; the
> > opposite of your switch labels.
> >
> >
> >
> >   
> >> I don't why but it looks like it doesn't know how to switch to "switch 2"
> >>     
> >
> > If I understand from your original post (re-reading it;
> > as soon as people start posting distribution or system
> > details my eyes sort of glaze over, while other people
> > will get an `aha!' moment that shall remain elusive to
> > me)...
> >
> > An older kernel version + modules worked;
> > an update of those modules broke DiSEqC;
> > your original kernel and modules didn't support your card.
> >
> > What I would suggest -- keeping in mind that the dvb kernel
> > modules, which you should see with `lsmod', are where you
> > should find correct support, are probably in some package
> > unknown to me which you'd need to downgrade -- would be to
> > either revert, if possible, whatever contains those modules,
> > or jump ahead several kernel versions.
> >
> > If you feel comfortable compiling and installing a newer
> > kernel (which is now around the 2.6.28 area), you could do
> > that.
> >
> > Alternatively, and possibly better, would be to upgrade
> > only the linux-dvb kernel modules, building them against
> > your 2.6.24-era kernel source, which you may need to
> > download and install.
> >
> > It's simple to download and build the latest linux-dvb
> > modules even against a 2.6.24 kernel, and that should
> > make things work -- if not, then something's been broken
> > for a while, and some expert should be able to help you.
> >
> >
> > barryb ouwsma
> >
> > _______________________________________________
> > linux-dvb mailing list
> > linux-dvb@linuxtv.org
> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> >   
> 
> Hi again,
> 
> and thanks for the info.
> 
> Unfortunately, diseqc seems broken, because no matter what i try
> 
> -s 0, 1 , 2 ,3.... i get 28.2E signal
> 
> however, 4 shows an error, as you said.
> 
> It used to work... so i'll try to get back or compile new linux-dvb 
> module as you suggested.
> 
> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
> hahahaha.
> 
> i don't even know how to get started, i barely install thing by "apt-get"
> 
> i'll try to find the way or post instead my problem in an ubuntu forum.
> 
> thanks for the info.
> 

we need a report at least from 2.6.25 or current v4l-dvb from
linuxtv.org.

Prior to this patch
http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
the Trio failed for 13 Volts and tone generation.
Don't have the hardware, but would expect BBC 1 London to work and BBC 1
CI to fail.

This patch disabled some lnpb21 boards, which have that one connected in
such a way, that diseqc forwarding is disabled. They need it from the
tda10086.

This was fixed by Hartmut with suggestions from Patrick to make it a
config option, if the tda10086 or the LNB chip in question is active.

All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
currently and it should be right for the Trio too and the isl6421 should
forward.

For looking at Ubuntu stuff, they downport a lot of things, because
always late with kernel releases, we need the exact sources to diff
against.

I still have only that single dish for initially helping Hartmut with
the isl6405 devel, but no rotors and switches yet and might be not of
much help.

Cheers,
Hermann







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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Molse]

En/na hermann pitton ha escrit:
> Hi,
>
> Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
>   
>> En/na BOUWSMA Barry ha escrit:
>>     
>>> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
>>>
>>>   
>>>       
>>>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
>>>>>> 3", it will always scan from "switch 1"
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> Try with -s 0; I'm not sure if it is always the case,
>>>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
>>>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
>>>>>       
>>>>>           
>>>   
>>>       
>>>> hi, thanks for anwsering.
>>>> I've already tried that.
>>>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
>>>>     
>>>>         
>>> I realized soon after sending my reply, that I had probably
>>> confused myself about which inputs you had where, and my
>>> advice, while partly correct, wouldn't help...
>>>
>>> Anyway -- the important thing to remember, is that if your
>>> `scan' works as I expect and your kernel modules work properly
>>> and you have a 2/1 DiSEqC switch, that scan -s option...
>>>  0 -- will tune to position 1/2;
>>>  1 -- will tune to position 2/2;
>>>  2 -- will cycle back and tune position 1/2;
>>>  3 -- will again tune position 2/2
>>>  4 -- should spit a warning, I think (something does)
>>>
>>> In other words -- if your system worked properly, `-s 1'
>>> would give you 19E2 and `-s 2' would give you 28E; the
>>> opposite of your switch labels.
>>>
>>>
>>>
>>>   
>>>       
>>>> I don't why but it looks like it doesn't know how to switch to "switch 2"
>>>>     
>>>>         
>>> If I understand from your original post (re-reading it;
>>> as soon as people start posting distribution or system
>>> details my eyes sort of glaze over, while other people
>>> will get an `aha!' moment that shall remain elusive to
>>> me)...
>>>
>>> An older kernel version + modules worked;
>>> an update of those modules broke DiSEqC;
>>> your original kernel and modules didn't support your card.
>>>
>>> What I would suggest -- keeping in mind that the dvb kernel
>>> modules, which you should see with `lsmod', are where you
>>> should find correct support, are probably in some package
>>> unknown to me which you'd need to downgrade -- would be to
>>> either revert, if possible, whatever contains those modules,
>>> or jump ahead several kernel versions.
>>>
>>> If you feel comfortable compiling and installing a newer
>>> kernel (which is now around the 2.6.28 area), you could do
>>> that.
>>>
>>> Alternatively, and possibly better, would be to upgrade
>>> only the linux-dvb kernel modules, building them against
>>> your 2.6.24-era kernel source, which you may need to
>>> download and install.
>>>
>>> It's simple to download and build the latest linux-dvb
>>> modules even against a 2.6.24 kernel, and that should
>>> make things work -- if not, then something's been broken
>>> for a while, and some expert should be able to help you.
>>>
>>>
>>> barryb ouwsma
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@linuxtv.org
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>   
>>>       
>> Hi again,
>>
>> and thanks for the info.
>>
>> Unfortunately, diseqc seems broken, because no matter what i try
>>
>> -s 0, 1 , 2 ,3.... i get 28.2E signal
>>
>> however, 4 shows an error, as you said.
>>
>> It used to work... so i'll try to get back or compile new linux-dvb 
>> module as you suggested.
>>
>> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
>> hahahaha.
>>
>> i don't even know how to get started, i barely install thing by "apt-get"
>>
>> i'll try to find the way or post instead my problem in an ubuntu forum.
>>
>> thanks for the info.
>>
>>     
>
> we need a report at least from 2.6.25 or current v4l-dvb from
> linuxtv.org.
>
> Prior to this patch
> http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
> the Trio failed for 13 Volts and tone generation.
> Don't have the hardware, but would expect BBC 1 London to work and BBC 1
> CI to fail.
>
> This patch disabled some lnpb21 boards, which have that one connected in
> such a way, that diseqc forwarding is disabled. They need it from the
> tda10086.
>
> This was fixed by Hartmut with suggestions from Patrick to make it a
> config option, if the tda10086 or the LNB chip in question is active.
>
> All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
> currently and it should be right for the Trio too and the isl6421 should
> forward.
>
> For looking at Ubuntu stuff, they downport a lot of things, because
> always late with kernel releases, we need the exact sources to diff
> against.
>
> I still have only that single dish for initially helping Hartmut with
> the isl6405 devel, but no rotors and switches yet and might be not of
> much help.
>
> Cheers,
> Hermann
>
>
>
>
>
>
>   
hi,

thanks for the info. I agree that in ubuntu there seem always to be 
"unfinished" things and then rush many things into "stable" releases 
when "it's time".

Anyway....

i tried to upgrade the system from "hardy" to "intrepid", which meant a 
lot of ports upgraded, including kernel
2.6.27.9.13

that thing you say...

"All saa7134 DVB-S drivers have this option as diseqc = 0 in the config

currently and it should be right for the Trio too and the isl6421 should
forward."


is there any way i can try this? is there any config file i can edit to 
make that happen (to make diseqc work)?

i'm not a experienced user ,but i've got the card and i'm really willing 
to help in any posible way.

just let me know what i can do.

thanks.



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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[hermann pitton]

Am Donnerstag, den 11.12.2008, 02:02 +0100 schrieb Jordi Molse:
> En/na hermann pitton ha escrit:
> > Hi,
> >
> > Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
> >   
> >> En/na BOUWSMA Barry ha escrit:
> >>     
> >>> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
> >>>
> >>>   
> >>>       
> >>>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
> >>>>>> 3", it will always scan from "switch 1"
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> Try with -s 0; I'm not sure if it is always the case,
> >>>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
> >>>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
> >>>>>       
> >>>>>           
> >>>   
> >>>       
> >>>> hi, thanks for anwsering.
> >>>> I've already tried that.
> >>>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
> >>>>     
> >>>>         
> >>> I realized soon after sending my reply, that I had probably
> >>> confused myself about which inputs you had where, and my
> >>> advice, while partly correct, wouldn't help...
> >>>
> >>> Anyway -- the important thing to remember, is that if your
> >>> `scan' works as I expect and your kernel modules work properly
> >>> and you have a 2/1 DiSEqC switch, that scan -s option...
> >>>  0 -- will tune to position 1/2;
> >>>  1 -- will tune to position 2/2;
> >>>  2 -- will cycle back and tune position 1/2;
> >>>  3 -- will again tune position 2/2
> >>>  4 -- should spit a warning, I think (something does)
> >>>
> >>> In other words -- if your system worked properly, `-s 1'
> >>> would give you 19E2 and `-s 2' would give you 28E; the
> >>> opposite of your switch labels.
> >>>
> >>>
> >>>
> >>>   
> >>>       
> >>>> I don't why but it looks like it doesn't know how to switch to "switch 2"
> >>>>     
> >>>>         
> >>> If I understand from your original post (re-reading it;
> >>> as soon as people start posting distribution or system
> >>> details my eyes sort of glaze over, while other people
> >>> will get an `aha!' moment that shall remain elusive to
> >>> me)...
> >>>
> >>> An older kernel version + modules worked;
> >>> an update of those modules broke DiSEqC;
> >>> your original kernel and modules didn't support your card.
> >>>
> >>> What I would suggest -- keeping in mind that the dvb kernel
> >>> modules, which you should see with `lsmod', are where you
> >>> should find correct support, are probably in some package
> >>> unknown to me which you'd need to downgrade -- would be to
> >>> either revert, if possible, whatever contains those modules,
> >>> or jump ahead several kernel versions.
> >>>
> >>> If you feel comfortable compiling and installing a newer
> >>> kernel (which is now around the 2.6.28 area), you could do
> >>> that.
> >>>
> >>> Alternatively, and possibly better, would be to upgrade
> >>> only the linux-dvb kernel modules, building them against
> >>> your 2.6.24-era kernel source, which you may need to
> >>> download and install.
> >>>
> >>> It's simple to download and build the latest linux-dvb
> >>> modules even against a 2.6.24 kernel, and that should
> >>> make things work -- if not, then something's been broken
> >>> for a while, and some expert should be able to help you.
> >>>
> >>>
> >>> barryb ouwsma
> >>>
> >>> _______________________________________________
> >>> linux-dvb mailing list
> >>> linux-dvb@linuxtv.org
> >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> >>>   
> >>>       
> >> Hi again,
> >>
> >> and thanks for the info.
> >>
> >> Unfortunately, diseqc seems broken, because no matter what i try
> >>
> >> -s 0, 1 , 2 ,3.... i get 28.2E signal
> >>
> >> however, 4 shows an error, as you said.
> >>
> >> It used to work... so i'll try to get back or compile new linux-dvb 
> >> module as you suggested.
> >>
> >> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
> >> hahahaha.
> >>
> >> i don't even know how to get started, i barely install thing by "apt-get"
> >>
> >> i'll try to find the way or post instead my problem in an ubuntu forum.
> >>
> >> thanks for the info.
> >>
> >>     
> >
> > we need a report at least from 2.6.25 or current v4l-dvb from
> > linuxtv.org.
> >
> > Prior to this patch
> > http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
> > the Trio failed for 13 Volts and tone generation.
> > Don't have the hardware, but would expect BBC 1 London to work and BBC 1
> > CI to fail.
> >
> > This patch disabled some lnpb21 boards, which have that one connected in
> > such a way, that diseqc forwarding is disabled. They need it from the
> > tda10086.
> >
> > This was fixed by Hartmut with suggestions from Patrick to make it a
> > config option, if the tda10086 or the LNB chip in question is active.
> >
> > All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
> > currently and it should be right for the Trio too and the isl6421 should
> > forward.
> >
> > For looking at Ubuntu stuff, they downport a lot of things, because
> > always late with kernel releases, we need the exact sources to diff
> > against.
> >
> > I still have only that single dish for initially helping Hartmut with
> > the isl6405 devel, but no rotors and switches yet and might be not of
> > much help.
> >
> > Cheers,
> > Hermann
> >
> >
> >
> >
> >
> >
> >   
> hi,
> 
> thanks for the info. I agree that in ubuntu there seem always to be 
> "unfinished" things and then rush many things into "stable" releases 
> when "it's time".
> 
> Anyway....
> 
> i tried to upgrade the system from "hardy" to "intrepid", which meant a 
> lot of ports upgraded, including kernel
> 2.6.27.9.13
> 
> that thing you say...
> 
> "All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
> 
> currently and it should be right for the Trio too and the isl6421 should
> forward."
> 
> 
> is there any way i can try this? is there any config file i can edit to 
> make that happen (to make diseqc work)?
> 
> i'm not a experienced user ,but i've got the card and i'm really willing 
> to help in any posible way.
> 
> just let me know what i can do.
> 
> thanks.
> 

Hi,

on that 2.6.27 "BBC 1 London" _and_ "BBC 1 CI" or equivalent at least
should work on 28.2. It does for me on lnpb21 and isl6405.

If something is still left for the switch then, either way connected, we
can start to scratch our heads or pull hair later, seems to me.

Cheers,
Hermann
 


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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Moles Blanco]

En/na hermann pitton ha escrit:
> Am Donnerstag, den 11.12.2008, 02:02 +0100 schrieb Jordi Molse:
>   
>> En/na hermann pitton ha escrit:
>>     
>>> Hi,
>>>
>>> Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
>>>   
>>>       
>>>> En/na BOUWSMA Barry ha escrit:
>>>>     
>>>>         
>>>>> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>>>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
>>>>>>>> 3", it will always scan from "switch 1"
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> Try with -s 0; I'm not sure if it is always the case,
>>>>>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
>>>>>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>   
>>>>>       
>>>>>           
>>>>>> hi, thanks for anwsering.
>>>>>> I've already tried that.
>>>>>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> I realized soon after sending my reply, that I had probably
>>>>> confused myself about which inputs you had where, and my
>>>>> advice, while partly correct, wouldn't help...
>>>>>
>>>>> Anyway -- the important thing to remember, is that if your
>>>>> `scan' works as I expect and your kernel modules work properly
>>>>> and you have a 2/1 DiSEqC switch, that scan -s option...
>>>>>  0 -- will tune to position 1/2;
>>>>>  1 -- will tune to position 2/2;
>>>>>  2 -- will cycle back and tune position 1/2;
>>>>>  3 -- will again tune position 2/2
>>>>>  4 -- should spit a warning, I think (something does)
>>>>>
>>>>> In other words -- if your system worked properly, `-s 1'
>>>>> would give you 19E2 and `-s 2' would give you 28E; the
>>>>> opposite of your switch labels.
>>>>>
>>>>>
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>>>> I don't why but it looks like it doesn't know how to switch to "switch 2"
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> If I understand from your original post (re-reading it;
>>>>> as soon as people start posting distribution or system
>>>>> details my eyes sort of glaze over, while other people
>>>>> will get an `aha!' moment that shall remain elusive to
>>>>> me)...
>>>>>
>>>>> An older kernel version + modules worked;
>>>>> an update of those modules broke DiSEqC;
>>>>> your original kernel and modules didn't support your card.
>>>>>
>>>>> What I would suggest -- keeping in mind that the dvb kernel
>>>>> modules, which you should see with `lsmod', are where you
>>>>> should find correct support, are probably in some package
>>>>> unknown to me which you'd need to downgrade -- would be to
>>>>> either revert, if possible, whatever contains those modules,
>>>>> or jump ahead several kernel versions.
>>>>>
>>>>> If you feel comfortable compiling and installing a newer
>>>>> kernel (which is now around the 2.6.28 area), you could do
>>>>> that.
>>>>>
>>>>> Alternatively, and possibly better, would be to upgrade
>>>>> only the linux-dvb kernel modules, building them against
>>>>> your 2.6.24-era kernel source, which you may need to
>>>>> download and install.
>>>>>
>>>>> It's simple to download and build the latest linux-dvb
>>>>> modules even against a 2.6.24 kernel, and that should
>>>>> make things work -- if not, then something's been broken
>>>>> for a while, and some expert should be able to help you.
>>>>>
>>>>>
>>>>> barryb ouwsma
>>>>>
>>>>> _______________________________________________
>>>>> linux-dvb mailing list
>>>>> linux-dvb@linuxtv.org
>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>>>   
>>>>>       
>>>>>           
>>>> Hi again,
>>>>
>>>> and thanks for the info.
>>>>
>>>> Unfortunately, diseqc seems broken, because no matter what i try
>>>>
>>>> -s 0, 1 , 2 ,3.... i get 28.2E signal
>>>>
>>>> however, 4 shows an error, as you said.
>>>>
>>>> It used to work... so i'll try to get back or compile new linux-dvb 
>>>> module as you suggested.
>>>>
>>>> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
>>>> hahahaha.
>>>>
>>>> i don't even know how to get started, i barely install thing by "apt-get"
>>>>
>>>> i'll try to find the way or post instead my problem in an ubuntu forum.
>>>>
>>>> thanks for the info.
>>>>
>>>>     
>>>>         
>>> we need a report at least from 2.6.25 or current v4l-dvb from
>>> linuxtv.org.
>>>
>>> Prior to this patch
>>> http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
>>> the Trio failed for 13 Volts and tone generation.
>>> Don't have the hardware, but would expect BBC 1 London to work and BBC 1
>>> CI to fail.
>>>
>>> This patch disabled some lnpb21 boards, which have that one connected in
>>> such a way, that diseqc forwarding is disabled. They need it from the
>>> tda10086.
>>>
>>> This was fixed by Hartmut with suggestions from Patrick to make it a
>>> config option, if the tda10086 or the LNB chip in question is active.
>>>
>>> All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
>>> currently and it should be right for the Trio too and the isl6421 should
>>> forward.
>>>
>>> For looking at Ubuntu stuff, they downport a lot of things, because
>>> always late with kernel releases, we need the exact sources to diff
>>> against.
>>>
>>> I still have only that single dish for initially helping Hartmut with
>>> the isl6405 devel, but no rotors and switches yet and might be not of
>>> much help.
>>>
>>> Cheers,
>>> Hermann
>>>
>>>
>>>
>>>
>>>
>>>
>>>   
>>>       
>> hi,
>>
>> thanks for the info. I agree that in ubuntu there seem always to be 
>> "unfinished" things and then rush many things into "stable" releases 
>> when "it's time".
>>
>> Anyway....
>>
>> i tried to upgrade the system from "hardy" to "intrepid", which meant a 
>> lot of ports upgraded, including kernel
>> 2.6.27.9.13
>>
>> that thing you say...
>>
>> "All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
>>
>> currently and it should be right for the Trio too and the isl6421 should
>> forward."
>>
>>
>> is there any way i can try this? is there any config file i can edit to 
>> make that happen (to make diseqc work)?
>>
>> i'm not a experienced user ,but i've got the card and i'm really willing 
>> to help in any posible way.
>>
>> just let me know what i can do.
>>
>> thanks.
>>
>>     
>
> Hi,
>
> on that 2.6.27 "BBC 1 London" _and_ "BBC 1 CI" or equivalent at least
> should work on 28.2. It does for me on lnpb21 and isl6405.
>
> If something is still left for the switch then, either way connected, we
> can start to scratch our heads or pull hair later, seems to me.
>
> Cheers,
> Hermann
>  
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   

hi,

well.. it doesn't work in my case.... double and triple checked, 
hehehe.... are you using the same card lifeview trio or another one with 
the same chip?

would you mind telling me what linux system are you working with? i'm 
desperate for this to work, i will change to any distro that makes 
diseqc work.

Thanks.

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[BOUWSMA Barry]

On Thu, 11 Dec 2008, Jordi Moles Blanco wrote:

> would you mind telling me what linux system are you working with? i'm 
> desperate for this to work, i will change to any distro that makes 
> diseqc work.

If you are willing to get your hands dirty with kernel
source and possibly a source-control system, then you
may be able to get a working system, without the need to
change distributions -- maybe.

The drawback to the convenience of packaged distributions
is that they are frozen at a particular point in time,
which can lock you out of improvements.  That's one of
the tradeoffs for the convenience about not having to
worry about these things, which is great, when it works.


The linux-dvb source should be self-contained for all
that you need to get your device working.  (But not
always...)  So, the easiest way would be for you to
build the linux-dvb source as modules against your
present kernel version, whatever that may be.

This will also allow you to go back in time, should
your device fail to work with the latest source, and
go back to the point where it did work -- and thereby
help the developers to get the latest source to work
again.


Anyway, you will need to update/download...
the sources for the kernel you are using
the latest linux-dvb source or tarball

The latter can be found at
http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.bz2
or, slightly larger,
http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.gz

This is the latest source; if you look around the
linuxtv.org site, you will also see a way to download
the entire history of the source which will help you
go back in time -- such as I've done today in order
to try to see if my production 2.6.14-ish machine
can use the last useable release without problems.


Are you comfortable working with the command line?
I hope so, because that's exclusively what I use.
When you've downloaded one of the above archives,
you'll need to extract it into a suitable playground,
perhaps like
% cd ~/
% mkdir src
% cd src
% tar z(or j or y)xvf ~/tip.tar.(whatever)
% cd (whatever-has-been-created)
% make

This expects you to have downloaded the source for
your kernel as well -- if you're unsure of how to get
this, someone familiar with your distribution should
be able to help, if there isn't anything on the wiki
to give details of building this.

If you don't have the proper kernel source, your attempt
to `make' will fail with lots of complaints.

If you do have the source, it's also possible your
attempted `make' will fail, and probably someone here
or elsewhere can help fix what's needed (if the source
is not found where it is expected, for example)


If all goes will, you will have the very latest kernel
modules that support your device, and can try them, to
see if they work, or if there are still problems.


barry bouwsma

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Molse]

En/na BOUWSMA Barry ha escrit:
> On Thu, 11 Dec 2008, Jordi Moles Blanco wrote:
>
>   
>> would you mind telling me what linux system are you working with? i'm 
>> desperate for this to work, i will change to any distro that makes 
>> diseqc work.
>>     
>
> If you are willing to get your hands dirty with kernel
> source and possibly a source-control system, then you
> may be able to get a working system, without the need to
> change distributions -- maybe.
>
> The drawback to the convenience of packaged distributions
> is that they are frozen at a particular point in time,
> which can lock you out of improvements.  That's one of
> the tradeoffs for the convenience about not having to
> worry about these things, which is great, when it works.
>
>
> The linux-dvb source should be self-contained for all
> that you need to get your device working.  (But not
> always...)  So, the easiest way would be for you to
> build the linux-dvb source as modules against your
> present kernel version, whatever that may be.
>
> This will also allow you to go back in time, should
> your device fail to work with the latest source, and
> go back to the point where it did work -- and thereby
> help the developers to get the latest source to work
> again.
>
>
> Anyway, you will need to update/download...
> the sources for the kernel you are using
> the latest linux-dvb source or tarball
>
> The latter can be found at
> http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.bz2
> or, slightly larger,
> http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.gz
>
> This is the latest source; if you look around the
> linuxtv.org site, you will also see a way to download
> the entire history of the source which will help you
> go back in time -- such as I've done today in order
> to try to see if my production 2.6.14-ish machine
> can use the last useable release without problems.
>
>
> Are you comfortable working with the command line?
> I hope so, because that's exclusively what I use.
> When you've downloaded one of the above archives,
> you'll need to extract it into a suitable playground,
> perhaps like
> % cd ~/
> % mkdir src
> % cd src
> % tar z(or j or y)xvf ~/tip.tar.(whatever)
> % cd (whatever-has-been-created)
> % make
>
> This expects you to have downloaded the source for
> your kernel as well -- if you're unsure of how to get
> this, someone familiar with your distribution should
> be able to help, if there isn't anything on the wiki
> to give details of building this.
>
> If you don't have the proper kernel source, your attempt
> to `make' will fail with lots of complaints.
>
> If you do have the source, it's also possible your
> attempted `make' will fail, and probably someone here
> or elsewhere can help fix what's needed (if the source
> is not found where it is expected, for example)
>
>
> If all goes will, you will have the very latest kernel
> modules that support your device, and can try them, to
> see if they work, or if there are still problems.
>
>
> barry bouwsma
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   
hi,

thanks for all the information provided, it's great!!..

i'm not and experienced user, but i get along well with command shell, 
and i'm able to run gcc and install thing form the scratch.

i'll give a try to see if i can compile and use those modules you suggest.

i'll report back with what i've found.

thanks.

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Moles Blanco]

En/na Jordi Molse ha escrit:
> En/na BOUWSMA Barry ha escrit:
>   
>> On Thu, 11 Dec 2008, Jordi Moles Blanco wrote:
>>
>>   
>>     
>>> would you mind telling me what linux system are you working with? i'm 
>>> desperate for this to work, i will change to any distro that makes 
>>> diseqc work.
>>>     
>>>       
>> If you are willing to get your hands dirty with kernel
>> source and possibly a source-control system, then you
>> may be able to get a working system, without the need to
>> change distributions -- maybe.
>>
>> The drawback to the convenience of packaged distributions
>> is that they are frozen at a particular point in time,
>> which can lock you out of improvements.  That's one of
>> the tradeoffs for the convenience about not having to
>> worry about these things, which is great, when it works.
>>
>>
>> The linux-dvb source should be self-contained for all
>> that you need to get your device working.  (But not
>> always...)  So, the easiest way would be for you to
>> build the linux-dvb source as modules against your
>> present kernel version, whatever that may be.
>>
>> This will also allow you to go back in time, should
>> your device fail to work with the latest source, and
>> go back to the point where it did work -- and thereby
>> help the developers to get the latest source to work
>> again.
>>
>>
>> Anyway, you will need to update/download...
>> the sources for the kernel you are using
>> the latest linux-dvb source or tarball
>>
>> The latter can be found at
>> http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.bz2
>> or, slightly larger,
>> http://linuxtv.org/hg/v4l-dvb/archive/tip.tar.gz
>>
>> This is the latest source; if you look around the
>> linuxtv.org site, you will also see a way to download
>> the entire history of the source which will help you
>> go back in time -- such as I've done today in order
>> to try to see if my production 2.6.14-ish machine
>> can use the last useable release without problems.
>>
>>
>> Are you comfortable working with the command line?
>> I hope so, because that's exclusively what I use.
>> When you've downloaded one of the above archives,
>> you'll need to extract it into a suitable playground,
>> perhaps like
>> % cd ~/
>> % mkdir src
>> % cd src
>> % tar z(or j or y)xvf ~/tip.tar.(whatever)
>> % cd (whatever-has-been-created)
>> % make
>>
>> This expects you to have downloaded the source for
>> your kernel as well -- if you're unsure of how to get
>> this, someone familiar with your distribution should
>> be able to help, if there isn't anything on the wiki
>> to give details of building this.
>>
>> If you don't have the proper kernel source, your attempt
>> to `make' will fail with lots of complaints.
>>
>> If you do have the source, it's also possible your
>> attempted `make' will fail, and probably someone here
>> or elsewhere can help fix what's needed (if the source
>> is not found where it is expected, for example)
>>
>>
>> If all goes will, you will have the very latest kernel
>> modules that support your device, and can try them, to
>> see if they work, or if there are still problems.
>>
>>
>> barry bouwsma
>>
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>   
>>     
> hi,
>
> thanks for all the information provided, it's great!!..
>
> i'm not and experienced user, but i get along well with command shell, 
> and i'm able to run gcc and install thing form the scratch.
>
> i'll give a try to see if i can compile and use those modules you suggest.
>
> i'll report back with what i've found.
>
> thanks.
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   

well... i did what i could....

the thing is that it seemed to work right until the end....

i extracted the files and run "make". everything worked fine. The 
problem was that i didn't now how to "load" that new compiled module 
instead of the "default one"

i mean.... if i run "modprobe saa7134"_dvb i'm accessing to the default 
module that comes with the kernel. is that right? so... i didn't how to 
load the new module.

what i did then was "make distclean"

and then i compiled with "make all"

and "make install" so that i could load the new module by just doing 
"modproe saa7134_dvb". is this right?

well....

when loading i get this message:

********************
FATAL: Error inserting saa7134 
(/lib/modules/2.6.24-19-generic/kernel/drivers/media/video/saa7134/saa7134.ko): 
Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error running install command for saa7134
FATAL: Error inserting saa7134_dvb 
(/lib/modules/2.6.24-19-generic/kernel/drivers/media/video/saa7134/saa7134-dvb.ko): 
Unknown symbol in module, or unknown parameter (see dmesg)
*********************

and this is what dmesg says about it:

*********************
[  240.715593] saa7134: disagrees about version of symbol 
v4l_compat_ioctl32
[  240.715604] saa7134: Unknown symbol v4l_compat_ioctl32
[  240.776343] saa7134_dvb: Unknown symbol saa7134_tuner_callback
[  240.776410] saa7134_dvb: Unknown symbol saa7134_ts_register
[  240.776643] saa7134_dvb: Unknown symbol saa7134_set_gpio
[  240.776703] saa7134_dvb: Unknown symbol saa7134_ts_qops
[  240.776845] saa7134_dvb: Unknown symbol saa7134_i2c_call_clients
[  240.776983] saa7134_dvb: Unknown symbol saa7134_ts_unregister

*********************


right now, i'm running on kernel 2.6.24-19-generic

any idea how to fix this?

thanks.

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[BOUWSMA Barry]

On Thu, 11 Dec 2008, Jordi Moles Blanco wrote:

> well... i did what i could....

Thanks, that I did not have to explain how to find the
kernel source  :-)



> i extracted the files and run "make". everything worked fine. The problem was
> that i didn't now how to "load" that new compiled module instead of the
> "default one"

If you want to do it the way I do, which is to test the
newly-built kernel modules without actually installing
them (in case I have more problems with the new than with
the old), the way I do it is...

% lsmod
(lists all the loaded kernel modules)

then I `rmmod' every module related to my particular
device and dvb/video/whatever is related, if I've been
updating that part of the source.

Then I load by hand, specifying the path to the
modules I've just built, like
# insmod /usr/local/src/v4l-dvb-last-before-2.6.16/v4l/[modname].ko

Keeping an eye on `dmesg' to show dependencies, which
you have experienced below...


> i mean.... if i run "modprobe saa7134"_dvb i'm accessing to the default module
> that comes with the kernel. is that right? so... i didn't how to load the new
> module.

Yes, this is correct.  If you do not care to keep your
old modules, you can do a
# make install
which should overwrite your old distro modules with the
new ones you've built, as you have done below...


> and "make install" so that i could load the new module by just doing "modproe
> saa7134_dvb". is this right?

> [  240.715593] saa7134: disagrees about version of symbol v4l_compat_ioctl32

I've seen this before on the list, but personally I don't
know the precise solution -- check the archives, if
someone else doesn't provide the answer.


> [  240.715604] saa7134: Unknown symbol v4l_compat_ioctl32
> [  240.776343] saa7134_dvb: Unknown symbol saa7134_tuner_callback
> [  240.776410] saa7134_dvb: Unknown symbol saa7134_ts_register
> [  240.776643] saa7134_dvb: Unknown symbol saa7134_set_gpio
> [  240.776703] saa7134_dvb: Unknown symbol saa7134_ts_qops
> [  240.776845] saa7134_dvb: Unknown symbol saa7134_i2c_call_clients
> [  240.776983] saa7134_dvb: Unknown symbol saa7134_ts_unregister

For the unknown symbols, as I mentioned above, that
means that needed modules aren't loaded -- as I note,
the way I do things (not recommended!) is to load
everything manually, mainly because I want to test
new hacks without losing my old modules.

I would then have to
# insmod /path/to/new/modules/[related-module].ko
where the related-modules are usually listed in the
`lsmod' output -- or else I just guess and load
anything that looks interesting and relevant.

As a wild guess, you need to load 
 ...drivers/media/video/compat_ioctl32.ko
in order to get v4l_compat_ioctl32; 
 ...drivers/media/video/saa7134/saa7134.ko
probably contains the various saa7134_foo symbols
which are needed by saa7134_dvb...


> any idea how to fix this?

Check the mailing list archives, is my suggestion,
since my personal answer is `no', not having
experienced this myself...

Anyway, I'm happy that you're able to work your way
through this without too much help, and I hope you
are learning something useful at the same time...


barry bouwsma

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[hermann pitton]

Hi,

Am Donnerstag, den 11.12.2008, 09:05 +0100 schrieb Jordi Moles Blanco:
> En/na hermann pitton ha escrit:
> > Am Donnerstag, den 11.12.2008, 02:02 +0100 schrieb Jordi Molse:
> >   
> >> En/na hermann pitton ha escrit:
> >>     
> >>> Hi,
> >>>
> >>> Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
> >>>   
> >>>       
> >>>> En/na BOUWSMA Barry ha escrit:
> >>>>     
> >>>>         
> >>>>> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
> >>>>>
> >>>>>   
> >>>>>       
> >>>>>           
> >>>>>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
> >>>>>>>> 3", it will always scan from "switch 1"
> >>>>>>>>     
> >>>>>>>>         
> >>>>>>>>             
> >>>>>>>>                 
> >>>>>>> Try with -s 0; I'm not sure if it is always the case,
> >>>>>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
> >>>>>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>   
> >>>>>       
> >>>>>           
> >>>>>> hi, thanks for anwsering.
> >>>>>> I've already tried that.
> >>>>>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> I realized soon after sending my reply, that I had probably
> >>>>> confused myself about which inputs you had where, and my
> >>>>> advice, while partly correct, wouldn't help...
> >>>>>
> >>>>> Anyway -- the important thing to remember, is that if your
> >>>>> `scan' works as I expect and your kernel modules work properly
> >>>>> and you have a 2/1 DiSEqC switch, that scan -s option...
> >>>>>  0 -- will tune to position 1/2;
> >>>>>  1 -- will tune to position 2/2;
> >>>>>  2 -- will cycle back and tune position 1/2;
> >>>>>  3 -- will again tune position 2/2
> >>>>>  4 -- should spit a warning, I think (something does)
> >>>>>
> >>>>> In other words -- if your system worked properly, `-s 1'
> >>>>> would give you 19E2 and `-s 2' would give you 28E; the
> >>>>> opposite of your switch labels.
> >>>>>
> >>>>>
> >>>>>
> >>>>>   
> >>>>>       
> >>>>>           
> >>>>>> I don't why but it looks like it doesn't know how to switch to "switch 2"
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> If I understand from your original post (re-reading it;
> >>>>> as soon as people start posting distribution or system
> >>>>> details my eyes sort of glaze over, while other people
> >>>>> will get an `aha!' moment that shall remain elusive to
> >>>>> me)...
> >>>>>
> >>>>> An older kernel version + modules worked;
> >>>>> an update of those modules broke DiSEqC;
> >>>>> your original kernel and modules didn't support your card.
> >>>>>
> >>>>> What I would suggest -- keeping in mind that the dvb kernel
> >>>>> modules, which you should see with `lsmod', are where you
> >>>>> should find correct support, are probably in some package
> >>>>> unknown to me which you'd need to downgrade -- would be to
> >>>>> either revert, if possible, whatever contains those modules,
> >>>>> or jump ahead several kernel versions.
> >>>>>
> >>>>> If you feel comfortable compiling and installing a newer
> >>>>> kernel (which is now around the 2.6.28 area), you could do
> >>>>> that.
> >>>>>
> >>>>> Alternatively, and possibly better, would be to upgrade
> >>>>> only the linux-dvb kernel modules, building them against
> >>>>> your 2.6.24-era kernel source, which you may need to
> >>>>> download and install.
> >>>>>
> >>>>> It's simple to download and build the latest linux-dvb
> >>>>> modules even against a 2.6.24 kernel, and that should
> >>>>> make things work -- if not, then something's been broken
> >>>>> for a while, and some expert should be able to help you.
> >>>>>
> >>>>>
> >>>>> barryb ouwsma
> >>>>>
> >>>>> _______________________________________________
> >>>>> linux-dvb mailing list
> >>>>> linux-dvb@linuxtv.org
> >>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> >>>>>   
> >>>>>       
> >>>>>           
> >>>> Hi again,
> >>>>
> >>>> and thanks for the info.
> >>>>
> >>>> Unfortunately, diseqc seems broken, because no matter what i try
> >>>>
> >>>> -s 0, 1 , 2 ,3.... i get 28.2E signal
> >>>>
> >>>> however, 4 shows an error, as you said.
> >>>>
> >>>> It used to work... so i'll try to get back or compile new linux-dvb 
> >>>> module as you suggested.
> >>>>
> >>>> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
> >>>> hahahaha.
> >>>>
> >>>> i don't even know how to get started, i barely install thing by "apt-get"
> >>>>
> >>>> i'll try to find the way or post instead my problem in an ubuntu forum.
> >>>>
> >>>> thanks for the info.
> >>>>
> >>>>     
> >>>>         
> >>> we need a report at least from 2.6.25 or current v4l-dvb from
> >>> linuxtv.org.
> >>>
> >>> Prior to this patch
> >>> http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
> >>> the Trio failed for 13 Volts and tone generation.
> >>> Don't have the hardware, but would expect BBC 1 London to work and BBC 1
> >>> CI to fail.
> >>>
> >>> This patch disabled some lnpb21 boards, which have that one connected in
> >>> such a way, that diseqc forwarding is disabled. They need it from the
> >>> tda10086.
> >>>
> >>> This was fixed by Hartmut with suggestions from Patrick to make it a
> >>> config option, if the tda10086 or the LNB chip in question is active.
> >>>
> >>> All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
> >>> currently and it should be right for the Trio too and the isl6421 should
> >>> forward.
> >>>
> >>> For looking at Ubuntu stuff, they downport a lot of things, because
> >>> always late with kernel releases, we need the exact sources to diff
> >>> against.
> >>>
> >>> I still have only that single dish for initially helping Hartmut with
> >>> the isl6405 devel, but no rotors and switches yet and might be not of
> >>> much help.
> >>>
> >>> Cheers,
> >>> Hermann
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>   
> >>>       
> >> hi,
> >>
> >> thanks for the info. I agree that in ubuntu there seem always to be 
> >> "unfinished" things and then rush many things into "stable" releases 
> >> when "it's time".
> >>
> >> Anyway....
> >>
> >> i tried to upgrade the system from "hardy" to "intrepid", which meant a 
> >> lot of ports upgraded, including kernel
> >> 2.6.27.9.13
> >>
> >> that thing you say...
> >>
> >> "All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
> >>
> >> currently and it should be right for the Trio too and the isl6421 should
> >> forward."
> >>
> >>
> >> is there any way i can try this? is there any config file i can edit to 
> >> make that happen (to make diseqc work)?
> >>
> >> i'm not a experienced user ,but i've got the card and i'm really willing 
> >> to help in any posible way.
> >>
> >> just let me know what i can do.
> >>
> >> thanks.
> >>
> >>     
> >
> > Hi,
> >
> > on that 2.6.27 "BBC 1 London" _and_ "BBC 1 CI" or equivalent at least
> > should work on 28.2. It does for me on lnpb21 and isl6405.
> >
> > If something is still left for the switch then, either way connected, we
> > can start to scratch our heads or pull hair later, seems to me.
> >
> > Cheers,
> > Hermann
> >  

> >   
> 
> hi,
> 
> well.. it doesn't work in my case.... double and triple checked, 
> hehehe.... are you using the same card lifeview trio or another one with 
> the same chip?
> 
> would you mind telling me what linux system are you working with? i'm 
> desperate for this to work, i will change to any distro that makes 
> diseqc work.
> 
> Thanks.

as said, I have neither the Trio with isl6421 nor any DiSEqC switches in
use.

But an Asus Tiger 3in1 with lnpb21 and several other cards with isl6405,
like Medion Quads, triple Creatix CTX948 and CTX929 DVB-S only.

All this cards work for 13/18Volts and low/high band switching, means
all broadcasts are available except DVB-S2 stuff.

The dual LNB isl6405 is totally identical to the isl6421 concerning the
programming of the first LNB and there have been reports for receiving
over 2000 services on 13.0E with the Trio cardbus. That should indicate
that at least all direct simple voltage and tone low/high switching
should work as well.

If possible, try to circumvent the switch once and connect directly to a
dish. You should be able to receive low and high band stuff on 13 and 18
Volts.

For mixed old and new modules loaded, try "make rmmod" twice and "make
rminstall" on top of mercurial v4l-dvb. Check if any modules are left in
your kernel version media modules folder or just delete/backup it
completely.

Run "make install" and "modprobe -v saa7134" assuming you have
"use_frontend=1" already in your module options.

Cheers,
Hermann



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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Molse]

En/na BOUWSMA Barry ha escrit:
> On Thu, 11 Dec 2008, Jordi Moles Blanco wrote:
>
>   
>> well... i did what i could....
>>     
>
> Thanks, that I did not have to explain how to find the
> kernel source  :-)
>
>
>
>   
>> i extracted the files and run "make". everything worked fine. The problem was
>> that i didn't now how to "load" that new compiled module instead of the
>> "default one"
>>     
>
> If you want to do it the way I do, which is to test the
> newly-built kernel modules without actually installing
> them (in case I have more problems with the new than with
> the old), the way I do it is...
>
> % lsmod
> (lists all the loaded kernel modules)
>
> then I `rmmod' every module related to my particular
> device and dvb/video/whatever is related, if I've been
> updating that part of the source.
>
> Then I load by hand, specifying the path to the
> modules I've just built, like
> # insmod /usr/local/src/v4l-dvb-last-before-2.6.16/v4l/[modname].ko
>
> Keeping an eye on `dmesg' to show dependencies, which
> you have experienced below...
>
>
>   
>> i mean.... if i run "modprobe saa7134"_dvb i'm accessing to the default module
>> that comes with the kernel. is that right? so... i didn't how to load the new
>> module.
>>     
>
> Yes, this is correct.  If you do not care to keep your
> old modules, you can do a
> # make install
> which should overwrite your old distro modules with the
> new ones you've built, as you have done below...
>
>
>   
>> and "make install" so that i could load the new module by just doing "modproe
>> saa7134_dvb". is this right?
>>     
>
>   
>> [  240.715593] saa7134: disagrees about version of symbol v4l_compat_ioctl32
>>     
>
> I've seen this before on the list, but personally I don't
> know the precise solution -- check the archives, if
> someone else doesn't provide the answer.
>
>
>   
>> [  240.715604] saa7134: Unknown symbol v4l_compat_ioctl32
>> [  240.776343] saa7134_dvb: Unknown symbol saa7134_tuner_callback
>> [  240.776410] saa7134_dvb: Unknown symbol saa7134_ts_register
>> [  240.776643] saa7134_dvb: Unknown symbol saa7134_set_gpio
>> [  240.776703] saa7134_dvb: Unknown symbol saa7134_ts_qops
>> [  240.776845] saa7134_dvb: Unknown symbol saa7134_i2c_call_clients
>> [  240.776983] saa7134_dvb: Unknown symbol saa7134_ts_unregister
>>     
>
> For the unknown symbols, as I mentioned above, that
> means that needed modules aren't loaded -- as I note,
> the way I do things (not recommended!) is to load
> everything manually, mainly because I want to test
> new hacks without losing my old modules.
>
> I would then have to
> # insmod /path/to/new/modules/[related-module].ko
> where the related-modules are usually listed in the
> `lsmod' output -- or else I just guess and load
> anything that looks interesting and relevant.
>
> As a wild guess, you need to load 
>  ...drivers/media/video/compat_ioctl32.ko
> in order to get v4l_compat_ioctl32; 
>  ...drivers/media/video/saa7134/saa7134.ko
> probably contains the various saa7134_foo symbols
> which are needed by saa7134_dvb...
>
>
>   
>> any idea how to fix this?
>>     
>
> Check the mailing list archives, is my suggestion,
> since my personal answer is `no', not having
> experienced this myself...
>
> Anyway, I'm happy that you're able to work your way
> through this without too much help, and I hope you
> are learning something useful at the same time...
>
>
> barry bouwsma
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   

Hi, thanks again for the help you are offering me.

However, i haven't been able to get diseqc working and i don't think i 
will....

let's go through all the thing...

i've got a lifeview flydvb pci trio card (saa7134) which has different 
chips, to tune satellite, digital terrestrial tv and also radio.

i used to have this card running in a dual boot with windows xp, where 
everything worked like a charm, and another one where i kept installing 
linux distros without any luck until "kubuntu hardy" came out. At that 
point, as the card with diseqc worked "out of the box", i decided to 
erase all data and move to ubuntu.

then i upgraded the system and also moved the tower from its place to 
next to the tv (to be a medicenter computer :) ). Then i couldn't view 
the channels anymore. I tried to retune with no luck... I check all the 
cables, just in case one of them was in bad shape. I even replaced the T 
connectors, just in case.

Then is when i first posted here with all my diseqc problems.

Since that moment i've reinstalled the whole system several times and 
even compiled the latest linux-dvb modules, but no matter what i do... i 
can only tune what is on switch 1 of my diseqc, never switch 2.

so... is it possible that somehow i've broken the card someone? the 
truth is that what used to work in windows... doesn't work anymore... 
this evening i went back to windows just to check if the card, the 
diseqc and everything was fine... and i had so many problems to get the 
satellite working as before. i used to use progdvb, which supported 
diseqc for my card and now it just can't tune through diseqc, none of 
the two satellites. other software does know how to get through diseqc, 
but only switch 1.

is it then possible that it's "half-broken"? i mean.. it's still able to 
tune, but not through diseqc because.....................

i'm no satellite or linux expert, but now i can confirm that while i 
still can view satellite channels in windows, it's not working as it 
used to anymore...

i've checked cables and i don't think it's an issue from the diseq 
thing, cause i've got two and both give the same problem.

well.. i guess i won't be able to use diseqc anymore... but if only 
someone could through some light on this...... at least how come i've 
broken it...

thanks.


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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Molse]

En/na hermann pitton ha escrit:
> Hi,
>
> Am Donnerstag, den 11.12.2008, 09:05 +0100 schrieb Jordi Moles Blanco:
>   
>> En/na hermann pitton ha escrit:
>>     
>>> Am Donnerstag, den 11.12.2008, 02:02 +0100 schrieb Jordi Molse:
>>>   
>>>       
>>>> En/na hermann pitton ha escrit:
>>>>     
>>>>         
>>>>> Hi,
>>>>>
>>>>> Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
>>>>>   
>>>>>       
>>>>>           
>>>>>> En/na BOUWSMA Barry ha escrit:
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>>> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
>>>>>>>
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>>>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
>>>>>>>>>> 3", it will always scan from "switch 1"
>>>>>>>>>>     
>>>>>>>>>>         
>>>>>>>>>>             
>>>>>>>>>>                 
>>>>>>>>>>                     
>>>>>>>>> Try with -s 0; I'm not sure if it is always the case,
>>>>>>>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
>>>>>>>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
>>>>>>>>>       
>>>>>>>>>           
>>>>>>>>>               
>>>>>>>>>                   
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>>>> hi, thanks for anwsering.
>>>>>>>> I've already tried that.
>>>>>>>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> I realized soon after sending my reply, that I had probably
>>>>>>> confused myself about which inputs you had where, and my
>>>>>>> advice, while partly correct, wouldn't help...
>>>>>>>
>>>>>>> Anyway -- the important thing to remember, is that if your
>>>>>>> `scan' works as I expect and your kernel modules work properly
>>>>>>> and you have a 2/1 DiSEqC switch, that scan -s option...
>>>>>>>  0 -- will tune to position 1/2;
>>>>>>>  1 -- will tune to position 2/2;
>>>>>>>  2 -- will cycle back and tune position 1/2;
>>>>>>>  3 -- will again tune position 2/2
>>>>>>>  4 -- should spit a warning, I think (something does)
>>>>>>>
>>>>>>> In other words -- if your system worked properly, `-s 1'
>>>>>>> would give you 19E2 and `-s 2' would give you 28E; the
>>>>>>> opposite of your switch labels.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>>>> I don't why but it looks like it doesn't know how to switch to "switch 2"
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> If I understand from your original post (re-reading it;
>>>>>>> as soon as people start posting distribution or system
>>>>>>> details my eyes sort of glaze over, while other people
>>>>>>> will get an `aha!' moment that shall remain elusive to
>>>>>>> me)...
>>>>>>>
>>>>>>> An older kernel version + modules worked;
>>>>>>> an update of those modules broke DiSEqC;
>>>>>>> your original kernel and modules didn't support your card.
>>>>>>>
>>>>>>> What I would suggest -- keeping in mind that the dvb kernel
>>>>>>> modules, which you should see with `lsmod', are where you
>>>>>>> should find correct support, are probably in some package
>>>>>>> unknown to me which you'd need to downgrade -- would be to
>>>>>>> either revert, if possible, whatever contains those modules,
>>>>>>> or jump ahead several kernel versions.
>>>>>>>
>>>>>>> If you feel comfortable compiling and installing a newer
>>>>>>> kernel (which is now around the 2.6.28 area), you could do
>>>>>>> that.
>>>>>>>
>>>>>>> Alternatively, and possibly better, would be to upgrade
>>>>>>> only the linux-dvb kernel modules, building them against
>>>>>>> your 2.6.24-era kernel source, which you may need to
>>>>>>> download and install.
>>>>>>>
>>>>>>> It's simple to download and build the latest linux-dvb
>>>>>>> modules even against a 2.6.24 kernel, and that should
>>>>>>> make things work -- if not, then something's been broken
>>>>>>> for a while, and some expert should be able to help you.
>>>>>>>
>>>>>>>
>>>>>>> barryb ouwsma
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> linux-dvb mailing list
>>>>>>> linux-dvb@linuxtv.org
>>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>> Hi again,
>>>>>>
>>>>>> and thanks for the info.
>>>>>>
>>>>>> Unfortunately, diseqc seems broken, because no matter what i try
>>>>>>
>>>>>> -s 0, 1 , 2 ,3.... i get 28.2E signal
>>>>>>
>>>>>> however, 4 shows an error, as you said.
>>>>>>
>>>>>> It used to work... so i'll try to get back or compile new linux-dvb 
>>>>>> module as you suggested.
>>>>>>
>>>>>> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
>>>>>> hahahaha.
>>>>>>
>>>>>> i don't even know how to get started, i barely install thing by "apt-get"
>>>>>>
>>>>>> i'll try to find the way or post instead my problem in an ubuntu forum.
>>>>>>
>>>>>> thanks for the info.
>>>>>>
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> we need a report at least from 2.6.25 or current v4l-dvb from
>>>>> linuxtv.org.
>>>>>
>>>>> Prior to this patch
>>>>> http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
>>>>> the Trio failed for 13 Volts and tone generation.
>>>>> Don't have the hardware, but would expect BBC 1 London to work and BBC 1
>>>>> CI to fail.
>>>>>
>>>>> This patch disabled some lnpb21 boards, which have that one connected in
>>>>> such a way, that diseqc forwarding is disabled. They need it from the
>>>>> tda10086.
>>>>>
>>>>> This was fixed by Hartmut with suggestions from Patrick to make it a
>>>>> config option, if the tda10086 or the LNB chip in question is active.
>>>>>
>>>>> All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
>>>>> currently and it should be right for the Trio too and the isl6421 should
>>>>> forward.
>>>>>
>>>>> For looking at Ubuntu stuff, they downport a lot of things, because
>>>>> always late with kernel releases, we need the exact sources to diff
>>>>> against.
>>>>>
>>>>> I still have only that single dish for initially helping Hartmut with
>>>>> the isl6405 devel, but no rotors and switches yet and might be not of
>>>>> much help.
>>>>>
>>>>> Cheers,
>>>>> Hermann
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>> hi,
>>>>
>>>> thanks for the info. I agree that in ubuntu there seem always to be 
>>>> "unfinished" things and then rush many things into "stable" releases 
>>>> when "it's time".
>>>>
>>>> Anyway....
>>>>
>>>> i tried to upgrade the system from "hardy" to "intrepid", which meant a 
>>>> lot of ports upgraded, including kernel
>>>> 2.6.27.9.13
>>>>
>>>> that thing you say...
>>>>
>>>> "All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
>>>>
>>>> currently and it should be right for the Trio too and the isl6421 should
>>>> forward."
>>>>
>>>>
>>>> is there any way i can try this? is there any config file i can edit to 
>>>> make that happen (to make diseqc work)?
>>>>
>>>> i'm not a experienced user ,but i've got the card and i'm really willing 
>>>> to help in any posible way.
>>>>
>>>> just let me know what i can do.
>>>>
>>>> thanks.
>>>>
>>>>     
>>>>         
>>> Hi,
>>>
>>> on that 2.6.27 "BBC 1 London" _and_ "BBC 1 CI" or equivalent at least
>>> should work on 28.2. It does for me on lnpb21 and isl6405.
>>>
>>> If something is still left for the switch then, either way connected, we
>>> can start to scratch our heads or pull hair later, seems to me.
>>>
>>> Cheers,
>>> Hermann
>>>  
>>>       
>
>   
>>>   
>>>       
>> hi,
>>
>> well.. it doesn't work in my case.... double and triple checked, 
>> hehehe.... are you using the same card lifeview trio or another one with 
>> the same chip?
>>
>> would you mind telling me what linux system are you working with? i'm 
>> desperate for this to work, i will change to any distro that makes 
>> diseqc work.
>>
>> Thanks.
>>     
>
> as said, I have neither the Trio with isl6421 nor any DiSEqC switches in
> use.
>
> But an Asus Tiger 3in1 with lnpb21 and several other cards with isl6405,
> like Medion Quads, triple Creatix CTX948 and CTX929 DVB-S only.
>
> All this cards work for 13/18Volts and low/high band switching, means
> all broadcasts are available except DVB-S2 stuff.
>
> The dual LNB isl6405 is totally identical to the isl6421 concerning the
> programming of the first LNB and there have been reports for receiving
> over 2000 services on 13.0E with the Trio cardbus. That should indicate
> that at least all direct simple voltage and tone low/high switching
> should work as well.
>
> If possible, try to circumvent the switch once and connect directly to a
> dish. You should be able to receive low and high band stuff on 13 and 18
> Volts.
>
> For mixed old and new modules loaded, try "make rmmod" twice and "make
> rminstall" on top of mercurial v4l-dvb. Check if any modules are left in
> your kernel version media modules folder or just delete/backup it
> completely.
>
> Run "make install" and "modprobe -v saa7134" assuming you have
> "use_frontend=1" already in your module options.
>
> Cheers,
> Hermann
>
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   
hey,

thanks for the info.

if i don't use diseqc, i can view every possible channels for each 
satellite, the problem appears only when it goes through diseqc.

thanks for the tips on how fixing the system, but because i have no 
patiente and i'm a newbie (and have nothing of value in this machine), i 
ended up reinstalling everything, which takes less time for me.

i just sent a message to the list, saying if it's possible i've broken 
the card somehow. Please, have a look at it and tell me what you think.

thanks.

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[hermann pitton]

Am Freitag, den 12.12.2008, 00:26 +0100 schrieb Jordi Molse:
> En/na hermann pitton ha escrit:
> > Hi,
> >
> > Am Donnerstag, den 11.12.2008, 09:05 +0100 schrieb Jordi Moles Blanco:
> >   
> >> En/na hermann pitton ha escrit:
> >>     
> >>> Am Donnerstag, den 11.12.2008, 02:02 +0100 schrieb Jordi Molse:
> >>>   
> >>>       
> >>>> En/na hermann pitton ha escrit:
> >>>>     
> >>>>         
> >>>>> Hi,
> >>>>>
> >>>>> Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
> >>>>>   
> >>>>>       
> >>>>>           
> >>>>>> En/na BOUWSMA Barry ha escrit:
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>>>> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
> >>>>>>>
> >>>>>>>   
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>>>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
> >>>>>>>>>> 3", it will always scan from "switch 1"
> >>>>>>>>>>     
> >>>>>>>>>>         
> >>>>>>>>>>             
> >>>>>>>>>>                 
> >>>>>>>>>>                     
> >>>>>>>>> Try with -s 0; I'm not sure if it is always the case,
> >>>>>>>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
> >>>>>>>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
> >>>>>>>>>       
> >>>>>>>>>           
> >>>>>>>>>               
> >>>>>>>>>                   
> >>>>>>>   
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>>>> hi, thanks for anwsering.
> >>>>>>>> I've already tried that.
> >>>>>>>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
> >>>>>>>>     
> >>>>>>>>         
> >>>>>>>>             
> >>>>>>>>                 
> >>>>>>> I realized soon after sending my reply, that I had probably
> >>>>>>> confused myself about which inputs you had where, and my
> >>>>>>> advice, while partly correct, wouldn't help...
> >>>>>>>
> >>>>>>> Anyway -- the important thing to remember, is that if your
> >>>>>>> `scan' works as I expect and your kernel modules work properly
> >>>>>>> and you have a 2/1 DiSEqC switch, that scan -s option...
> >>>>>>>  0 -- will tune to position 1/2;
> >>>>>>>  1 -- will tune to position 2/2;
> >>>>>>>  2 -- will cycle back and tune position 1/2;
> >>>>>>>  3 -- will again tune position 2/2
> >>>>>>>  4 -- should spit a warning, I think (something does)
> >>>>>>>
> >>>>>>> In other words -- if your system worked properly, `-s 1'
> >>>>>>> would give you 19E2 and `-s 2' would give you 28E; the
> >>>>>>> opposite of your switch labels.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>   
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>>>> I don't why but it looks like it doesn't know how to switch to "switch 2"
> >>>>>>>>     
> >>>>>>>>         
> >>>>>>>>             
> >>>>>>>>                 
> >>>>>>> If I understand from your original post (re-reading it;
> >>>>>>> as soon as people start posting distribution or system
> >>>>>>> details my eyes sort of glaze over, while other people
> >>>>>>> will get an `aha!' moment that shall remain elusive to
> >>>>>>> me)...
> >>>>>>>
> >>>>>>> An older kernel version + modules worked;
> >>>>>>> an update of those modules broke DiSEqC;
> >>>>>>> your original kernel and modules didn't support your card.
> >>>>>>>
> >>>>>>> What I would suggest -- keeping in mind that the dvb kernel
> >>>>>>> modules, which you should see with `lsmod', are where you
> >>>>>>> should find correct support, are probably in some package
> >>>>>>> unknown to me which you'd need to downgrade -- would be to
> >>>>>>> either revert, if possible, whatever contains those modules,
> >>>>>>> or jump ahead several kernel versions.
> >>>>>>>
> >>>>>>> If you feel comfortable compiling and installing a newer
> >>>>>>> kernel (which is now around the 2.6.28 area), you could do
> >>>>>>> that.
> >>>>>>>
> >>>>>>> Alternatively, and possibly better, would be to upgrade
> >>>>>>> only the linux-dvb kernel modules, building them against
> >>>>>>> your 2.6.24-era kernel source, which you may need to
> >>>>>>> download and install.
> >>>>>>>
> >>>>>>> It's simple to download and build the latest linux-dvb
> >>>>>>> modules even against a 2.6.24 kernel, and that should
> >>>>>>> make things work -- if not, then something's been broken
> >>>>>>> for a while, and some expert should be able to help you.
> >>>>>>>
> >>>>>>>
> >>>>>>> barryb ouwsma
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> linux-dvb mailing list
> >>>>>>> linux-dvb@linuxtv.org
> >>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> >>>>>>>   
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>> Hi again,
> >>>>>>
> >>>>>> and thanks for the info.
> >>>>>>
> >>>>>> Unfortunately, diseqc seems broken, because no matter what i try
> >>>>>>
> >>>>>> -s 0, 1 , 2 ,3.... i get 28.2E signal
> >>>>>>
> >>>>>> however, 4 shows an error, as you said.
> >>>>>>
> >>>>>> It used to work... so i'll try to get back or compile new linux-dvb 
> >>>>>> module as you suggested.
> >>>>>>
> >>>>>> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
> >>>>>> hahahaha.
> >>>>>>
> >>>>>> i don't even know how to get started, i barely install thing by "apt-get"
> >>>>>>
> >>>>>> i'll try to find the way or post instead my problem in an ubuntu forum.
> >>>>>>
> >>>>>> thanks for the info.
> >>>>>>
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> we need a report at least from 2.6.25 or current v4l-dvb from
> >>>>> linuxtv.org.
> >>>>>
> >>>>> Prior to this patch
> >>>>> http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
> >>>>> the Trio failed for 13 Volts and tone generation.
> >>>>> Don't have the hardware, but would expect BBC 1 London to work and BBC 1
> >>>>> CI to fail.
> >>>>>
> >>>>> This patch disabled some lnpb21 boards, which have that one connected in
> >>>>> such a way, that diseqc forwarding is disabled. They need it from the
> >>>>> tda10086.
> >>>>>
> >>>>> This was fixed by Hartmut with suggestions from Patrick to make it a
> >>>>> config option, if the tda10086 or the LNB chip in question is active.
> >>>>>
> >>>>> All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
> >>>>> currently and it should be right for the Trio too and the isl6421 should
> >>>>> forward.
> >>>>>
> >>>>> For looking at Ubuntu stuff, they downport a lot of things, because
> >>>>> always late with kernel releases, we need the exact sources to diff
> >>>>> against.
> >>>>>
> >>>>> I still have only that single dish for initially helping Hartmut with
> >>>>> the isl6405 devel, but no rotors and switches yet and might be not of
> >>>>> much help.
> >>>>>
> >>>>> Cheers,
> >>>>> Hermann
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>   
> >>>>>       
> >>>>>           
> >>>> hi,
> >>>>
> >>>> thanks for the info. I agree that in ubuntu there seem always to be 
> >>>> "unfinished" things and then rush many things into "stable" releases 
> >>>> when "it's time".
> >>>>
> >>>> Anyway....
> >>>>
> >>>> i tried to upgrade the system from "hardy" to "intrepid", which meant a 
> >>>> lot of ports upgraded, including kernel
> >>>> 2.6.27.9.13
> >>>>
> >>>> that thing you say...
> >>>>
> >>>> "All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
> >>>>
> >>>> currently and it should be right for the Trio too and the isl6421 should
> >>>> forward."
> >>>>
> >>>>
> >>>> is there any way i can try this? is there any config file i can edit to 
> >>>> make that happen (to make diseqc work)?
> >>>>
> >>>> i'm not a experienced user ,but i've got the card and i'm really willing 
> >>>> to help in any posible way.
> >>>>
> >>>> just let me know what i can do.
> >>>>
> >>>> thanks.
> >>>>
> >>>>     
> >>>>         
> >>> Hi,
> >>>
> >>> on that 2.6.27 "BBC 1 London" _and_ "BBC 1 CI" or equivalent at least
> >>> should work on 28.2. It does for me on lnpb21 and isl6405.
> >>>
> >>> If something is still left for the switch then, either way connected, we
> >>> can start to scratch our heads or pull hair later, seems to me.
> >>>
> >>> Cheers,
> >>> Hermann
> >>>  
> >>>       
> >
> >   
> >>>   
> >>>       
> >> hi,
> >>
> >> well.. it doesn't work in my case.... double and triple checked, 
> >> hehehe.... are you using the same card lifeview trio or another one with 
> >> the same chip?
> >>
> >> would you mind telling me what linux system are you working with? i'm 
> >> desperate for this to work, i will change to any distro that makes 
> >> diseqc work.
> >>
> >> Thanks.
> >>     
> >
> > as said, I have neither the Trio with isl6421 nor any DiSEqC switches in
> > use.
> >
> > But an Asus Tiger 3in1 with lnpb21 and several other cards with isl6405,
> > like Medion Quads, triple Creatix CTX948 and CTX929 DVB-S only.
> >
> > All this cards work for 13/18Volts and low/high band switching, means
> > all broadcasts are available except DVB-S2 stuff.
> >
> > The dual LNB isl6405 is totally identical to the isl6421 concerning the
> > programming of the first LNB and there have been reports for receiving
> > over 2000 services on 13.0E with the Trio cardbus. That should indicate
> > that at least all direct simple voltage and tone low/high switching
> > should work as well.
> >
> > If possible, try to circumvent the switch once and connect directly to a
> > dish. You should be able to receive low and high band stuff on 13 and 18
> > Volts.
> >
> > For mixed old and new modules loaded, try "make rmmod" twice and "make
> > rminstall" on top of mercurial v4l-dvb. Check if any modules are left in
> > your kernel version media modules folder or just delete/backup it
> > completely.
> >
> > Run "make install" and "modprobe -v saa7134" assuming you have
> > "use_frontend=1" already in your module options.
> >
> > Cheers,
> > Hermann
> >
> >

Hi,

> >   
> hey,
> 
> thanks for the info.
> 
> if i don't use diseqc, i can view every possible channels for each 
> satellite, the problem appears only when it goes through diseqc.

OK good.

> thanks for the tips on how fixing the system, but because i have no 
> patiente and i'm a newbie (and have nothing of value in this machine), i 
> ended up reinstalling everything, which takes less time for me.

I'm not aware of any recent change and think it doesn't matter anyway,
as long you can change the source to come back to what seemed to be
working for you.

> i just sent a message to the list, saying if it's possible i've broken 
> the card somehow. Please, have a look at it and tell me what you think.
> 
> thanks.

I really tried hard, until realized the isl6405 is behind the tda10086
i2c bridge, but think it is close to impossible with what we have around
and at all, except high voltage occurs from outside without protection.

I would try a cold boot next, say 40 seconds without any power
connected. The 13 and 18 Volts you can also easily measure at the
connector of the card.

Good Luck,

Hermann





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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Molse]

En/na hermann pitton ha escrit:
> Am Freitag, den 12.12.2008, 00:26 +0100 schrieb Jordi Molse:
>   
>> En/na hermann pitton ha escrit:
>>     
>>> Hi,
>>>
>>> Am Donnerstag, den 11.12.2008, 09:05 +0100 schrieb Jordi Moles Blanco:
>>>   
>>>       
>>>> En/na hermann pitton ha escrit:
>>>>     
>>>>         
>>>>> Am Donnerstag, den 11.12.2008, 02:02 +0100 schrieb Jordi Molse:
>>>>>   
>>>>>       
>>>>>           
>>>>>> En/na hermann pitton ha escrit:
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>>> Hi,
>>>>>>>
>>>>>>> Am Mittwoch, den 10.12.2008, 20:45 +0100 schrieb Jordi Molse:
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>>>> En/na BOUWSMA Barry ha escrit:
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>>>> On Wed, 10 Dec 2008, Jordi Moles Blanco wrote:
>>>>>>>>>
>>>>>>>>>   
>>>>>>>>>       
>>>>>>>>>           
>>>>>>>>>               
>>>>>>>>>                   
>>>>>>>>>>>> And it doesn't matter if i run "scan -s 1" or "scan -s 2" or "scan -s
>>>>>>>>>>>> 3", it will always scan from "switch 1"
>>>>>>>>>>>>     
>>>>>>>>>>>>         
>>>>>>>>>>>>             
>>>>>>>>>>>>                 
>>>>>>>>>>>>                     
>>>>>>>>>>>>                         
>>>>>>>>>>> Try with -s 0; I'm not sure if it is always the case,
>>>>>>>>>>> but my unhacked `scan' uses 0-3 for DiSEqC positions
>>>>>>>>>>> 1/4 to 4/4 -- I've hacked this to use the range of 1-4
>>>>>>>>>>>       
>>>>>>>>>>>           
>>>>>>>>>>>               
>>>>>>>>>>>                   
>>>>>>>>>>>                       
>>>>>>>>>   
>>>>>>>>>       
>>>>>>>>>           
>>>>>>>>>               
>>>>>>>>>                   
>>>>>>>>>> hi, thanks for anwsering.
>>>>>>>>>> I've already tried that.
>>>>>>>>>> remember, on switch 1 i've got astra 28.2E and on switch 2 i've got astra 19E
>>>>>>>>>>     
>>>>>>>>>>         
>>>>>>>>>>             
>>>>>>>>>>                 
>>>>>>>>>>                     
>>>>>>>>> I realized soon after sending my reply, that I had probably
>>>>>>>>> confused myself about which inputs you had where, and my
>>>>>>>>> advice, while partly correct, wouldn't help...
>>>>>>>>>
>>>>>>>>> Anyway -- the important thing to remember, is that if your
>>>>>>>>> `scan' works as I expect and your kernel modules work properly
>>>>>>>>> and you have a 2/1 DiSEqC switch, that scan -s option...
>>>>>>>>>  0 -- will tune to position 1/2;
>>>>>>>>>  1 -- will tune to position 2/2;
>>>>>>>>>  2 -- will cycle back and tune position 1/2;
>>>>>>>>>  3 -- will again tune position 2/2
>>>>>>>>>  4 -- should spit a warning, I think (something does)
>>>>>>>>>
>>>>>>>>> In other words -- if your system worked properly, `-s 1'
>>>>>>>>> would give you 19E2 and `-s 2' would give you 28E; the
>>>>>>>>> opposite of your switch labels.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>   
>>>>>>>>>       
>>>>>>>>>           
>>>>>>>>>               
>>>>>>>>>                   
>>>>>>>>>> I don't why but it looks like it doesn't know how to switch to "switch 2"
>>>>>>>>>>     
>>>>>>>>>>         
>>>>>>>>>>             
>>>>>>>>>>                 
>>>>>>>>>>                     
>>>>>>>>> If I understand from your original post (re-reading it;
>>>>>>>>> as soon as people start posting distribution or system
>>>>>>>>> details my eyes sort of glaze over, while other people
>>>>>>>>> will get an `aha!' moment that shall remain elusive to
>>>>>>>>> me)...
>>>>>>>>>
>>>>>>>>> An older kernel version + modules worked;
>>>>>>>>> an update of those modules broke DiSEqC;
>>>>>>>>> your original kernel and modules didn't support your card.
>>>>>>>>>
>>>>>>>>> What I would suggest -- keeping in mind that the dvb kernel
>>>>>>>>> modules, which you should see with `lsmod', are where you
>>>>>>>>> should find correct support, are probably in some package
>>>>>>>>> unknown to me which you'd need to downgrade -- would be to
>>>>>>>>> either revert, if possible, whatever contains those modules,
>>>>>>>>> or jump ahead several kernel versions.
>>>>>>>>>
>>>>>>>>> If you feel comfortable compiling and installing a newer
>>>>>>>>> kernel (which is now around the 2.6.28 area), you could do
>>>>>>>>> that.
>>>>>>>>>
>>>>>>>>> Alternatively, and possibly better, would be to upgrade
>>>>>>>>> only the linux-dvb kernel modules, building them against
>>>>>>>>> your 2.6.24-era kernel source, which you may need to
>>>>>>>>> download and install.
>>>>>>>>>
>>>>>>>>> It's simple to download and build the latest linux-dvb
>>>>>>>>> modules even against a 2.6.24 kernel, and that should
>>>>>>>>> make things work -- if not, then something's been broken
>>>>>>>>> for a while, and some expert should be able to help you.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> barryb ouwsma
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> linux-dvb mailing list
>>>>>>>>> linux-dvb@linuxtv.org
>>>>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>>>>>>>   
>>>>>>>>>       
>>>>>>>>>           
>>>>>>>>>               
>>>>>>>>>                   
>>>>>>>> Hi again,
>>>>>>>>
>>>>>>>> and thanks for the info.
>>>>>>>>
>>>>>>>> Unfortunately, diseqc seems broken, because no matter what i try
>>>>>>>>
>>>>>>>> -s 0, 1 , 2 ,3.... i get 28.2E signal
>>>>>>>>
>>>>>>>> however, 4 shows an error, as you said.
>>>>>>>>
>>>>>>>> It used to work... so i'll try to get back or compile new linux-dvb 
>>>>>>>> module as you suggested.
>>>>>>>>
>>>>>>>> i'm really really newbie in this, i'm using kubuntu, so imagine.... 
>>>>>>>> hahahaha.
>>>>>>>>
>>>>>>>> i don't even know how to get started, i barely install thing by "apt-get"
>>>>>>>>
>>>>>>>> i'll try to find the way or post instead my problem in an ubuntu forum.
>>>>>>>>
>>>>>>>> thanks for the info.
>>>>>>>>
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> we need a report at least from 2.6.25 or current v4l-dvb from
>>>>>>> linuxtv.org.
>>>>>>>
>>>>>>> Prior to this patch
>>>>>>> http://linuxtv.org/pipermail/linux-dvb/2007-June/018741.html
>>>>>>> the Trio failed for 13 Volts and tone generation.
>>>>>>> Don't have the hardware, but would expect BBC 1 London to work and BBC 1
>>>>>>> CI to fail.
>>>>>>>
>>>>>>> This patch disabled some lnpb21 boards, which have that one connected in
>>>>>>> such a way, that diseqc forwarding is disabled. They need it from the
>>>>>>> tda10086.
>>>>>>>
>>>>>>> This was fixed by Hartmut with suggestions from Patrick to make it a
>>>>>>> config option, if the tda10086 or the LNB chip in question is active.
>>>>>>>
>>>>>>> All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
>>>>>>> currently and it should be right for the Trio too and the isl6421 should
>>>>>>> forward.
>>>>>>>
>>>>>>> For looking at Ubuntu stuff, they downport a lot of things, because
>>>>>>> always late with kernel releases, we need the exact sources to diff
>>>>>>> against.
>>>>>>>
>>>>>>> I still have only that single dish for initially helping Hartmut with
>>>>>>> the isl6405 devel, but no rotors and switches yet and might be not of
>>>>>>> much help.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Hermann
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>> hi,
>>>>>>
>>>>>> thanks for the info. I agree that in ubuntu there seem always to be 
>>>>>> "unfinished" things and then rush many things into "stable" releases 
>>>>>> when "it's time".
>>>>>>
>>>>>> Anyway....
>>>>>>
>>>>>> i tried to upgrade the system from "hardy" to "intrepid", which meant a 
>>>>>> lot of ports upgraded, including kernel
>>>>>> 2.6.27.9.13
>>>>>>
>>>>>> that thing you say...
>>>>>>
>>>>>> "All saa7134 DVB-S drivers have this option as diseqc = 0 in the config
>>>>>>
>>>>>> currently and it should be right for the Trio too and the isl6421 should
>>>>>> forward."
>>>>>>
>>>>>>
>>>>>> is there any way i can try this? is there any config file i can edit to 
>>>>>> make that happen (to make diseqc work)?
>>>>>>
>>>>>> i'm not a experienced user ,but i've got the card and i'm really willing 
>>>>>> to help in any posible way.
>>>>>>
>>>>>> just let me know what i can do.
>>>>>>
>>>>>> thanks.
>>>>>>
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> Hi,
>>>>>
>>>>> on that 2.6.27 "BBC 1 London" _and_ "BBC 1 CI" or equivalent at least
>>>>> should work on 28.2. It does for me on lnpb21 and isl6405.
>>>>>
>>>>> If something is still left for the switch then, either way connected, we
>>>>> can start to scratch our heads or pull hair later, seems to me.
>>>>>
>>>>> Cheers,
>>>>> Hermann
>>>>>  
>>>>>       
>>>>>           
>>>   
>>>       
>>>>>   
>>>>>       
>>>>>           
>>>> hi,
>>>>
>>>> well.. it doesn't work in my case.... double and triple checked, 
>>>> hehehe.... are you using the same card lifeview trio or another one with 
>>>> the same chip?
>>>>
>>>> would you mind telling me what linux system are you working with? i'm 
>>>> desperate for this to work, i will change to any distro that makes 
>>>> diseqc work.
>>>>
>>>> Thanks.
>>>>     
>>>>         
>>> as said, I have neither the Trio with isl6421 nor any DiSEqC switches in
>>> use.
>>>
>>> But an Asus Tiger 3in1 with lnpb21 and several other cards with isl6405,
>>> like Medion Quads, triple Creatix CTX948 and CTX929 DVB-S only.
>>>
>>> All this cards work for 13/18Volts and low/high band switching, means
>>> all broadcasts are available except DVB-S2 stuff.
>>>
>>> The dual LNB isl6405 is totally identical to the isl6421 concerning the
>>> programming of the first LNB and there have been reports for receiving
>>> over 2000 services on 13.0E with the Trio cardbus. That should indicate
>>> that at least all direct simple voltage and tone low/high switching
>>> should work as well.
>>>
>>> If possible, try to circumvent the switch once and connect directly to a
>>> dish. You should be able to receive low and high band stuff on 13 and 18
>>> Volts.
>>>
>>> For mixed old and new modules loaded, try "make rmmod" twice and "make
>>> rminstall" on top of mercurial v4l-dvb. Check if any modules are left in
>>> your kernel version media modules folder or just delete/backup it
>>> completely.
>>>
>>> Run "make install" and "modprobe -v saa7134" assuming you have
>>> "use_frontend=1" already in your module options.
>>>
>>> Cheers,
>>> Hermann
>>>
>>>
>>>       
>
> Hi,
>
>   
>>>   
>>>       
>> hey,
>>
>> thanks for the info.
>>
>> if i don't use diseqc, i can view every possible channels for each 
>> satellite, the problem appears only when it goes through diseqc.
>>     
>
> OK good.
>
>   
>> thanks for the tips on how fixing the system, but because i have no 
>> patiente and i'm a newbie (and have nothing of value in this machine), i 
>> ended up reinstalling everything, which takes less time for me.
>>     
>
> I'm not aware of any recent change and think it doesn't matter anyway,
> as long you can change the source to come back to what seemed to be
> working for you.
>
>   
>> i just sent a message to the list, saying if it's possible i've broken 
>> the card somehow. Please, have a look at it and tell me what you think.
>>
>> thanks.
>>     
>
> I really tried hard, until realized the isl6405 is behind the tda10086
> i2c bridge, but think it is close to impossible with what we have around
> and at all, except high voltage occurs from outside without protection.
>
> I would try a cold boot next, say 40 seconds without any power
> connected. The 13 and 18 Volts you can also easily measure at the
> connector of the card.
>
> Good Luck,
>
> Hermann
>
>
>
>
>   
oh, i hadn't thought of that... the computer has always been powered on 
all the time. As it is not running anything critical, i will try to plug 
everything out for the whole night and try again tomorrow. We'll see 
then if magic comes for breakfast, hahaha!!!

thanks.

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[BOUWSMA Barry]

On Fri, 12 Dec 2008, Jordi Molse wrote:

> However, i haven't been able to get diseqc working and i don't think i
> will....

It is too early to give up now!!1!  At least, I shall not
give up until the sun melts away enough of the snow, so that
I can go out and get more beer, though the melted snow
will probably freeze into slick ice, and I'll probably
end up hurting more than last time, this time with broken
glass embedded into my body...  A direct infusion of that
evil alcohol into by bloodstream without the middleman of
passing the lips, gums, tongue, nose -- heck, why bother
searching to find excellent-tasting beer when I won't notice
and appreciate the difference anyway...


> i used to have this card running in a dual boot with windows xp, where
> everything worked like a charm, and another one where i kept installing linux
> distros without any luck until "kubuntu hardy" came out. At that point, as the
> card with diseqc worked "out of the box", i decided to erase all data and move

One card, worked in two boxes; the first box a 'doze box,
the second box Kubuntu Hardy...  (unsupported before then)


> then i upgraded the system and also moved the tower from its place to next to
> the tv (to be a medicenter computer :) ). Then i couldn't view the channels
> anymore. I tried to retune with no luck... I check all the cables, just in
> case one of them was in bad shape. I even replaced the T connectors, just in

System `upgraded' and stopped DiSEqC working; but also,
system moved.  No success since then.

Question:

When you moved the system, did you have to add new cable?
If so, how long was the length of cable from your machine
to the DiSEqC switch before you moved it, and how long is
this cable now, or is it the same length and same cable?

Other question, what do you mean by a `T connector'?
For satellite, I am familiar with the `F' connector, and
I am also familiar with other types of `T' connector,
but they should have no place in a satellite system...



> so... is it possible that somehow i've broken the card someone? the truth is

Not too likely -- DiSEqC switching is basically the same
as a modulated version of the 22kHz tone which is used to
switch between low (below 11700) and high (above 11700)
frequencies by the LNB.

However, I have had experience with several different
2/1 and 4/1 DiSEqC switches at the end of long cable
runs, which could not be properly switched by some DVB-S
cards, but could -- or could not be switched by a consumer
satellite receiver, but which worked flawlessly when located
a few metres from the receiver, instead of nearly 100m away.
The cable length attenuated or otherwise corrupted the
DiSEqC bursts from some devices so that they failed to work.


> that what used to work in windows... doesn't work anymore... this evening i
> went back to windows just to check if the card, the diseqc and everything was
> fine... and i had so many problems to get the satellite working as before. i
> used to use progdvb, which supported diseqc for my card and now it just can't
> tune through diseqc, none of the two satellites. other software does know how
> to get through diseqc, but only switch 1.

So, the same setup, apart from being moved, now no longer
works the same as it used to work with 'doze, and 'doze
either no longer works at all, or fails to switch DiSEqC?

Note that a typical DiSEqC switch will simply pass along
its 1/2 or 1/4 or 1/8 or 1/whatever input, when it does
not receive the switching signal to select 2/2 or whatever.



> i've checked cables and i don't think it's an issue from the diseq thing,
> cause i've got two and both give the same problem.

Two?  Two what -- DiSEqC switches, two cables to switches?

Do you have a normal consumer satellite receiver, as well
as your different computer boxes?


I'm going to guess based on where I think you are located,
that you have something like the following -- please correct
me where I ass-u-me wrong, and add any additional info that
is missing from this...

Dish+LNB pointed at 28E, large enough to receive BBC/ITV/etc
Dish+LNB pointed at 19E (or offset mounted on 28E dish)
DiSEqC switch(es) located near dishes -- or near your tuner
so you can connect directly from each LNB as a test?
Single cable run from switch to computer, or two cable runs
from two switches?

LNB19E--
        \               long cable run
         2/1 DiSEqC----------------------------Computer
        /
LNB28E--

You also mention DVB-T/radio from this card; if you could
mention how that affects the above, if at all (it should
not, but I never know for sure)

Also, if you have any spares (a pile of DiSEqC switches,
other DVB-S capable cards, etc), it would be handy for me
to know -- in the case of my 4/1 switches located more
than 50m from my tuners, it was partially a case of
swapping in other switches from my pile of them until
finding a working combination, or running an additional
several hundred metres of cable to permit me to switch
the four positions close to the tuners...


thanks,
barry bouwsma
not an expert, by any means

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Moles Blanco]

wow, how many questions in just one mail, hahaha. i'll try to answer 
everything as well as i can.


En/na BOUWSMA Barry ha escrit:
> On Fri, 12 Dec 2008, Jordi Molse wrote:
>
>   
>> However, i haven't been able to get diseqc working and i don't think i
>> will....
>>     
>
> It is too early to give up now!!1!  At least, I shall not
> give up until the sun melts away enough of the snow, so that
> I can go out and get more beer, though the melted snow
> will probably freeze into slick ice, and I'll probably
> end up hurting more than last time, this time with broken
> glass embedded into my body...  A direct infusion of that
> evil alcohol into by bloodstream without the middleman of
> passing the lips, gums, tongue, nose -- heck, why bother
> searching to find excellent-tasting beer when I won't notice
> and appreciate the difference anyway...
>
>   

hahaha, and they say I'M crazy.


>   
>> i used to have this card running in a dual boot with windows xp, where
>> everything worked like a charm, and another one where i kept installing linux
>> distros without any luck until "kubuntu hardy" came out. At that point, as the
>> card with diseqc worked "out of the box", i decided to erase all data and move
>>     
>
> One card, worked in two boxes; the first box a 'doze box,
> the second box Kubuntu Hardy...  (unsupported before then)
>
>
>   

i just realised it couldn't be worse explained... hahaha. The thing 
is... i used to have one computer with the lifeview card. In this 
computer i had dual boot. In the first partition always windows, where 
the card would work through diseqc. On the second partition i would keep 
installing different linux distros until i found that "kubuntu hardy" 
worked.
After that i erased all data and installed only kubuntu hardy on my 
computer.

>> then i upgraded the system and also moved the tower from its place to next to
>> the tv (to be a medicenter computer :) ). Then i couldn't view the channels
>> anymore. I tried to retune with no luck... I check all the cables, just in
>> case one of them was in bad shape. I even replaced the T connectors, just in
>>     
>
> System `upgraded' and stopped DiSEqC working; but also,
> system moved.  No success since then.
>
> Question:
>
> When you moved the system, did you have to add new cable?
> If so, how long was the length of cable from your machine
> to the DiSEqC switch before you moved it, and how long is
> this cable now, or is it the same length and same cable?
>
> Other question, what do you mean by a `T connector'?
> For satellite, I am familiar with the `F' connector, and
> I am also familiar with other types of `T' connector,
> but they should have no place in a satellite system...
>
>
>
>   
So... after installing everything and getting it to work properly 
through diseqc, i upgraded the whole system to the latest packages and 
also moved the tower from my room to the another room. I didn't try to 
view any channel after upgrading and before moving the computer, and 
that's why i didn't know if the upgrade had broken the system or i had 
broken the card by moving the tower from room to room... or may be had i 
used bad cables in the new place?

Then i turned on the tv and realised it was not working anymore. Then i 
went crazy and tried every possible thing until i came here to post for 
the first time.

>> so... is it possible that somehow i've broken the card someone? the truth is
>>     
>
> Not too likely -- DiSEqC switching is basically the same
> as a modulated version of the 22kHz tone which is used to
> switch between low (below 11700) and high (above 11700)
> frequencies by the LNB.
>
> However, I have had experience with several different
> 2/1 and 4/1 DiSEqC switches at the end of long cable
> runs, which could not be properly switched by some DVB-S
> cards, but could -- or could not be switched by a consumer
> satellite receiver, but which worked flawlessly when located
> a few metres from the receiver, instead of nearly 100m away.
> The cable length attenuated or otherwise corrupted the
> DiSEqC bursts from some devices so that they failed to work.
>
>
>   

I don't think distance is the problem, as now there are less meters from 
the dishes to my box.
Actually, it's the same 2 cables than before. I used to have 2 long 
cables which went from the dishes to a room (going through the room the 
computer is now). It used to be like 8-9 meters long.
Right now, the box is in this other room, closer to the dishes. I'm 
still using the same cables, but shorter, i cut 2-3 meters from each one 
as i don't need those meters anymore.
Obviuosly, i had to set the "F connectors again" (not T connectors, 
hehe) and... did i do it the right way? I don't know. I would think 
so... but that's why i asked you if there's a chance i've broken the 
card but mounting the F connectors the wrong way and causing the 
receiver to malfunction.

>> that what used to work in windows... doesn't work anymore... this evening i
>> went back to windows just to check if the card, the diseqc and everything was
>> fine... and i had so many problems to get the satellite working as before. i
>> used to use progdvb, which supported diseqc for my card and now it just can't
>> tune through diseqc, none of the two satellites. other software does know how
>> to get through diseqc, but only switch 1.
>>     
>
> So, the same setup, apart from being moved, now no longer
> works the same as it used to work with 'doze, and 'doze
> either no longer works at all, or fails to switch DiSEqC?
>
> Note that a typical DiSEqC switch will simply pass along
> its 1/2 or 1/4 or 1/8 or 1/whatever input, when it does
> not receive the switching signal to select 2/2 or whatever.
>
>
>
>   

Again, that was made me thing that i had broken something in my card or 
my diseqc switch, as i can tune from both separately but not together 
through diseqc.
It doesn't make much sense to me that the card is half-broken.... i 
mean... i can tune any satellite but not through diseqc.... but i asked 
because i'm no a hardware expert at all.

>> i've checked cables and i don't think it's an issue from the diseq thing,
>> cause i've got two and both give the same problem.
>>     
>
> Two?  Two what -- DiSEqC switches, two cables to switches?
>
> Do you have a normal consumer satellite receiver, as well
> as your different computer boxes?
>   

two diseqc switch to play with. lifeview is not working with any of them.

i've got an engel tdt 5300 receiver, but diseqc never worked there.  I 
bought it when i had only one dish. When then i set the second one, i 
also fought to get diseqc working and i ended up trying the lifeview in 
my computer, which worked in windows. I though that it might  be a 
problem with engel's tunner, so i just let it go.

i haven't tried now to make it work in the engel receiver... but if back 
then didn't use to work....

>
> I'm going to guess based on where I think you are located,
> that you have something like the following -- please correct
> me where I ass-u-me wrong, and add any additional info that
> is missing from this...
>
> Dish+LNB pointed at 28E, large enough to receive BBC/ITV/etc
> Dish+LNB pointed at 19E (or offset mounted on 28E dish)
> DiSEqC switch(es) located near dishes -- or near your tuner
> so you can connect directly from each LNB as a test?
> Single cable run from switch to computer, or two cable runs
> from two switches?
>
> LNB19E--
>         \               long cable run
>          2/1 DiSEqC----------------------------Computer
>         /
> LNB28E--
>   

i've got 2 80cm satellite dishes, one for Astra 28.2E and the other one 
for Astra 19.2E.
Then, from each dish i've got like 2-3 meters cable to where the 
computer is.
Then, next to the computer "the two become one", hehe, through the 
diseqc switch.

 From diseqc i've got a cable, like 30cm long to the computer

The diseqc switch is 2.0, like this one:

http://www.sadoun.com/Sat/Products/DiSEqC/DS21-DISEQC-SWITCH.jpg

> You also mention DVB-T/radio from this card; if you could
> mention how that affects the above, if at all (it should
> not, but I never know for sure)
>   

I don't think it affects in any way. The card has 3 different chips, or 
so i think: one for radio, one for digital tv (terrestrial) and one for 
satellite tv. In windows you install 3 different drivers. Actually, 
windows see the card as 3 different cards, and you can "tune" the three 
chips at the same time. for example, you can view satellite while 
recording digital tv, which is great :)

In Linux this doesn't happen. Linux sees the card "as one", and you have 
to keep  doing

modprobe saa7134 use_frontend=0... =1..=2 to get one chip or another to 
work.  Although it would be great to have all of them working at the 
same time.. it's not a problem for me, as i actually never used this 
feature in windows.

> Also, if you have any spares (a pile of DiSEqC switches,
> other DVB-S capable cards, etc), it would be handy for me
> to know -- in the case of my 4/1 switches located more
> than 50m from my tuners, it was partially a case of
> swapping in other switches from my pile of them until
> finding a working combination, or running an additional
> several hundred metres of cable to permit me to switch
> the four positions close to the tuners...
>
>
>   

i don't think there's any other helpful information to provide.

> thanks,
> barry bouwsma
> not an expert, by any means
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>   

thanks.

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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[hermann pitton]

Hi,

just to avoid some new myth :)

Am Freitag, den 12.12.2008, 14:22 +0100 schrieb Jordi Moles Blanco:
> wow, how many questions in just one mail, hahaha. i'll try to answer 
> everything as well as i can.
> 
> 
> En/na BOUWSMA Barry ha escrit:
> > On Fri, 12 Dec 2008, Jordi Molse wrote:
> >
> >   
> >> However, i haven't been able to get diseqc working and i don't think i
> >> will....
> >>     
> >
> > It is too early to give up now!!1!  At least, I shall not
> > give up until the sun melts away enough of the snow, so that
> > I can go out and get more beer, though the melted snow
> > will probably freeze into slick ice, and I'll probably
> > end up hurting more than last time, this time with broken
> > glass embedded into my body...  A direct infusion of that
> > evil alcohol into by bloodstream without the middleman of
> > passing the lips, gums, tongue, nose -- heck, why bother
> > searching to find excellent-tasting beer when I won't notice
> > and appreciate the difference anyway...
> >
> >   
> 
> hahaha, and they say I'M crazy.
> 
> 
> >   
> >> i used to have this card running in a dual boot with windows xp, where
> >> everything worked like a charm, and another one where i kept installing linux
> >> distros without any luck until "kubuntu hardy" came out. At that point, as the
> >> card with diseqc worked "out of the box", i decided to erase all data and move
> >>     
> >
> > One card, worked in two boxes; the first box a 'doze box,
> > the second box Kubuntu Hardy...  (unsupported before then)
> >
> >
> >   
> 
> i just realised it couldn't be worse explained... hahaha. The thing 
> is... i used to have one computer with the lifeview card. In this 
> computer i had dual boot. In the first partition always windows, where 
> the card would work through diseqc. On the second partition i would keep 
> installing different linux distros until i found that "kubuntu hardy" 
> worked.
> After that i erased all data and installed only kubuntu hardy on my 
> computer.
> 
> >> then i upgraded the system and also moved the tower from its place to next to
> >> the tv (to be a medicenter computer :) ). Then i couldn't view the channels
> >> anymore. I tried to retune with no luck... I check all the cables, just in
> >> case one of them was in bad shape. I even replaced the T connectors, just in
> >>     
> >
> > System `upgraded' and stopped DiSEqC working; but also,
> > system moved.  No success since then.
> >
> > Question:
> >
> > When you moved the system, did you have to add new cable?
> > If so, how long was the length of cable from your machine
> > to the DiSEqC switch before you moved it, and how long is
> > this cable now, or is it the same length and same cable?
> >
> > Other question, what do you mean by a `T connector'?
> > For satellite, I am familiar with the `F' connector, and
> > I am also familiar with other types of `T' connector,
> > but they should have no place in a satellite system...
> >
> >
> >
> >   
> So... after installing everything and getting it to work properly 
> through diseqc, i upgraded the whole system to the latest packages and 
> also moved the tower from my room to the another room. I didn't try to 
> view any channel after upgrading and before moving the computer, and 
> that's why i didn't know if the upgrade had broken the system or i had 
> broken the card by moving the tower from room to room... or may be had i 
> used bad cables in the new place?
> 
> Then i turned on the tv and realised it was not working anymore. Then i 
> went crazy and tried every possible thing until i came here to post for 
> the first time.
> 
> >> so... is it possible that somehow i've broken the card someone? the truth is
> >>     
> >
> > Not too likely -- DiSEqC switching is basically the same
> > as a modulated version of the 22kHz tone which is used to
> > switch between low (below 11700) and high (above 11700)
> > frequencies by the LNB.
> >
> > However, I have had experience with several different
> > 2/1 and 4/1 DiSEqC switches at the end of long cable
> > runs, which could not be properly switched by some DVB-S
> > cards, but could -- or could not be switched by a consumer
> > satellite receiver, but which worked flawlessly when located
> > a few metres from the receiver, instead of nearly 100m away.
> > The cable length attenuated or otherwise corrupted the
> > DiSEqC bursts from some devices so that they failed to work.
> >
> >
> >   
> 
> I don't think distance is the problem, as now there are less meters from 
> the dishes to my box.
> Actually, it's the same 2 cables than before. I used to have 2 long 
> cables which went from the dishes to a room (going through the room the 
> computer is now). It used to be like 8-9 meters long.
> Right now, the box is in this other room, closer to the dishes. I'm 
> still using the same cables, but shorter, i cut 2-3 meters from each one 
> as i don't need those meters anymore.
> Obviuosly, i had to set the "F connectors again" (not T connectors, 
> hehe) and... did i do it the right way? I don't know. I would think 
> so... but that's why i asked you if there's a chance i've broken the 
> card but mounting the F connectors the wrong way and causing the 
> receiver to malfunction.
> 
> >> that what used to work in windows... doesn't work anymore... this evening i
> >> went back to windows just to check if the card, the diseqc and everything was
> >> fine... and i had so many problems to get the satellite working as before. i
> >> used to use progdvb, which supported diseqc for my card and now it just can't
> >> tune through diseqc, none of the two satellites. other software does know how
> >> to get through diseqc, but only switch 1.
> >>     
> >
> > So, the same setup, apart from being moved, now no longer
> > works the same as it used to work with 'doze, and 'doze
> > either no longer works at all, or fails to switch DiSEqC?
> >
> > Note that a typical DiSEqC switch will simply pass along
> > its 1/2 or 1/4 or 1/8 or 1/whatever input, when it does
> > not receive the switching signal to select 2/2 or whatever.
> >
> >
> >
> >   
> 
> Again, that was made me thing that i had broken something in my card or 
> my diseqc switch, as i can tune from both separately but not together 
> through diseqc.
> It doesn't make much sense to me that the card is half-broken.... i 
> mean... i can tune any satellite but not through diseqc.... but i asked 
> because i'm no a hardware expert at all.
> 
> >> i've checked cables and i don't think it's an issue from the diseq thing,
> >> cause i've got two and both give the same problem.
> >>     
> >
> > Two?  Two what -- DiSEqC switches, two cables to switches?
> >
> > Do you have a normal consumer satellite receiver, as well
> > as your different computer boxes?
> >   
> 
> two diseqc switch to play with. lifeview is not working with any of them.
> 
> i've got an engel tdt 5300 receiver, but diseqc never worked there.  I 
> bought it when i had only one dish. When then i set the second one, i 
> also fought to get diseqc working and i ended up trying the lifeview in 
> my computer, which worked in windows. I though that it might  be a 
> problem with engel's tunner, so i just let it go.
> 
> i haven't tried now to make it work in the engel receiver... but if back 
> then didn't use to work....
> 
> >
> > I'm going to guess based on where I think you are located,
> > that you have something like the following -- please correct
> > me where I ass-u-me wrong, and add any additional info that
> > is missing from this...
> >
> > Dish+LNB pointed at 28E, large enough to receive BBC/ITV/etc
> > Dish+LNB pointed at 19E (or offset mounted on 28E dish)
> > DiSEqC switch(es) located near dishes -- or near your tuner
> > so you can connect directly from each LNB as a test?
> > Single cable run from switch to computer, or two cable runs
> > from two switches?
> >
> > LNB19E--
> >         \               long cable run
> >          2/1 DiSEqC----------------------------Computer
> >         /
> > LNB28E--
> >   
> 
> i've got 2 80cm satellite dishes, one for Astra 28.2E and the other one 
> for Astra 19.2E.
> Then, from each dish i've got like 2-3 meters cable to where the 
> computer is.
> Then, next to the computer "the two become one", hehe, through the 
> diseqc switch.
> 
>  From diseqc i've got a cable, like 30cm long to the computer
> 
> The diseqc switch is 2.0, like this one:
> 
> http://www.sadoun.com/Sat/Products/DiSEqC/DS21-DISEQC-SWITCH.jpg
> 
> > You also mention DVB-T/radio from this card; if you could
> > mention how that affects the above, if at all (it should
> > not, but I never know for sure)
> >   
> 
> I don't think it affects in any way. The card has 3 different chips, or 
> so i think: one for radio, one for digital tv (terrestrial) and one for 
> satellite tv. In windows you install 3 different drivers. Actually, 
> windows see the card as 3 different cards, and you can "tune" the three 
> chips at the same time. for example, you can view satellite while 
> recording digital tv, which is great :)

The latter is not true, you can`t view/record DVB-S and DVB-T at once.
That would need a second saa7131 PCI bridge you don't have.

It is one tda8275a hybrid tuner, which in this case is only used for
radio and analog TV, a second tda8275a hybrid tuner, which is only used
for DVB-T on this card with tda10046 channel decoder and a single
tda826x tuner for DVB-S with tda10086 channel decoder and isl6421 ...

> In Linux this doesn't happen. Linux sees the card "as one", and you have 
> to keep  doing
> 
> modprobe saa7134 use_frontend=0... =1..=2 to get one chip or another to 
> work.  Although it would be great to have all of them working at the 
> same time.. it's not a problem for me, as i actually never used this 
> feature in windows.
> 
> > Also, if you have any spares (a pile of DiSEqC switches,
> > other DVB-S capable cards, etc), it would be handy for me
> > to know -- in the case of my 4/1 switches located more
> > than 50m from my tuners, it was partially a case of
> > swapping in other switches from my pile of them until
> > finding a working combination, or running an additional
> > several hundred metres of cable to permit me to switch
> > the four positions close to the tuners...
> >
> >
> >   
> 
> i don't think there's any other helpful information to provide.
> 

We need to go through the code in question, investigate Ubuntu
downports, reread datasheets as far as available (!) and my first guess
is your switch worked once with diseqc enabled on the tda10086, at least
for low. On high with permanent tone from the isl6121 also enabled, I
doubt it ever came through.

Cheers,
Hermann




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

Re: [linux-dvb] lifeview pci trio (saa7134) not working through diseqc anymore

[Jordi Moles]

En/na hermann pitton ha escrit:
> Hi,
>
> just to avoid some new myth :)
>
> Am Freitag, den 12.12.2008, 14:22 +0100 schrieb Jordi Moles Blanco:
>   
>> wow, how many questions in just one mail, hahaha. i'll try to answer 
>> everything as well as i can.
>>
>>
>> En/na BOUWSMA Barry ha escrit:
>>     
>>> On Fri, 12 Dec 2008, Jordi Molse wrote:
>>>
>>>   
>>>       
>>>> However, i haven't been able to get diseqc working and i don't think i
>>>> will....
>>>>     
>>>>         
>>> It is too early to give up now!!1!  At least, I shall not
>>> give up until the sun melts away enough of the snow, so that
>>> I can go out and get more beer, though the melted snow
>>> will probably freeze into slick ice, and I'll probably
>>> end up hurting more than last time, this time with broken
>>> glass embedded into my body...  A direct infusion of that
>>> evil alcohol into by bloodstream without the middleman of
>>> passing the lips, gums, tongue, nose -- heck, why bother
>>> searching to find excellent-tasting beer when I won't notice
>>> and appreciate the difference anyway...
>>>
>>>   
>>>       
>> hahaha, and they say I'M crazy.
>>
>>
>>     
>>>   
>>>       
>>>> i used to have this card running in a dual boot with windows xp, where
>>>> everything worked like a charm, and another one where i kept installing linux
>>>> distros without any luck until "kubuntu hardy" came out. At that point, as the
>>>> card with diseqc worked "out of the box", i decided to erase all data and move
>>>>     
>>>>         
>>> One card, worked in two boxes; the first box a 'doze box,
>>> the second box Kubuntu Hardy...  (unsupported before then)
>>>
>>>
>>>   
>>>       
>> i just realised it couldn't be worse explained... hahaha. The thing 
>> is... i used to have one computer with the lifeview card. In this 
>> computer i had dual boot. In the first partition always windows, where 
>> the card would work through diseqc. On the second partition i would keep 
>> installing different linux distros until i found that "kubuntu hardy" 
>> worked.
>> After that i erased all data and installed only kubuntu hardy on my 
>> computer.
>>
>>     
>>>> then i upgraded the system and also moved the tower from its place to next to
>>>> the tv (to be a medicenter computer :) ). Then i couldn't view the channels
>>>> anymore. I tried to retune with no luck... I check all the cables, just in
>>>> case one of them was in bad shape. I even replaced the T connectors, just in
>>>>     
>>>>         
>>> System `upgraded' and stopped DiSEqC working; but also,
>>> system moved.  No success since then.
>>>
>>> Question:
>>>
>>> When you moved the system, did you have to add new cable?
>>> If so, how long was the length of cable from your machine
>>> to the DiSEqC switch before you moved it, and how long is
>>> this cable now, or is it the same length and same cable?
>>>
>>> Other question, what do you mean by a `T connector'?
>>> For satellite, I am familiar with the `F' connector, and
>>> I am also familiar with other types of `T' connector,
>>> but they should have no place in a satellite system...
>>>
>>>
>>>
>>>   
>>>       
>> So... after installing everything and getting it to work properly 
>> through diseqc, i upgraded the whole system to the latest packages and 
>> also moved the tower from my room to the another room. I didn't try to 
>> view any channel after upgrading and before moving the computer, and 
>> that's why i didn't know if the upgrade had broken the system or i had 
>> broken the card by moving the tower from room to room... or may be had i 
>> used bad cables in the new place?
>>
>> Then i turned on the tv and realised it was not working anymore. Then i 
>> went crazy and tried every possible thing until i came here to post for 
>> the first time.
>>
>>     
>>>> so... is it possible that somehow i've broken the card someone? the truth is
>>>>     
>>>>         
>>> Not too likely -- DiSEqC switching is basically the same
>>> as a modulated version of the 22kHz tone which is used to
>>> switch between low (below 11700) and high (above 11700)
>>> frequencies by the LNB.
>>>
>>> However, I have had experience with several different
>>> 2/1 and 4/1 DiSEqC switches at the end of long cable
>>> runs, which could not be properly switched by some DVB-S
>>> cards, but could -- or could not be switched by a consumer
>>> satellite receiver, but which worked flawlessly when located
>>> a few metres from the receiver, instead of nearly 100m away.
>>> The cable length attenuated or otherwise corrupted the
>>> DiSEqC bursts from some devices so that they failed to work.
>>>
>>>
>>>   
>>>       
>> I don't think distance is the problem, as now there are less meters from 
>> the dishes to my box.
>> Actually, it's the same 2 cables than before. I used to have 2 long 
>> cables which went from the dishes to a room (going through the room the 
>> computer is now). It used to be like 8-9 meters long.
>> Right now, the box is in this other room, closer to the dishes. I'm 
>> still using the same cables, but shorter, i cut 2-3 meters from each one 
>> as i don't need those meters anymore.
>> Obviuosly, i had to set the "F connectors again" (not T connectors, 
>> hehe) and... did i do it the right way? I don't know. I would think 
>> so... but that's why i asked you if there's a chance i've broken the 
>> card but mounting the F connectors the wrong way and causing the 
>> receiver to malfunction.
>>
>>     
>>>> that what used to work in windows... doesn't work anymore... this evening i
>>>> went back to windows just to check if the card, the diseqc and everything was
>>>> fine... and i had so many problems to get the satellite working as before. i
>>>> used to use progdvb, which supported diseqc for my card and now it just can't
>>>> tune through diseqc, none of the two satellites. other software does know how
>>>> to get through diseqc, but only switch 1.
>>>>     
>>>>         
>>> So, the same setup, apart from being moved, now no longer
>>> works the same as it used to work with 'doze, and 'doze
>>> either no longer works at all, or fails to switch DiSEqC?
>>>
>>> Note that a typical DiSEqC switch will simply pass along
>>> its 1/2 or 1/4 or 1/8 or 1/whatever input, when it does
>>> not receive the switching signal to select 2/2 or whatever.
>>>
>>>
>>>
>>>   
>>>       
>> Again, that was made me thing that i had broken something in my card or 
>> my diseqc switch, as i can tune from both separately but not together 
>> through diseqc.
>> It doesn't make much sense to me that the card is half-broken.... i 
>> mean... i can tune any satellite but not through diseqc.... but i asked 
>> because i'm no a hardware expert at all.
>>
>>     
>>>> i've checked cables and i don't think it's an issue from the diseq thing,
>>>> cause i've got two and both give the same problem.
>>>>     
>>>>         
>>> Two?  Two what -- DiSEqC switches, two cables to switches?
>>>
>>> Do you have a normal consumer satellite receiver, as well
>>> as your different computer boxes?
>>>   
>>>       
>> two diseqc switch to play with. lifeview is not working with any of them.
>>
>> i've got an engel tdt 5300 receiver, but diseqc never worked there.  I 
>> bought it when i had only one dish. When then i set the second one, i 
>> also fought to get diseqc working and i ended up trying the lifeview in 
>> my computer, which worked in windows. I though that it might  be a 
>> problem with engel's tunner, so i just let it go.
>>
>> i haven't tried now to make it work in the engel receiver... but if back 
>> then didn't use to work....
>>
>>     
>>> I'm going to guess based on where I think you are located,
>>> that you have something like the following -- please correct
>>> me where I ass-u-me wrong, and add any additional info that
>>> is missing from this...
>>>
>>> Dish+LNB pointed at 28E, large enough to receive BBC/ITV/etc
>>> Dish+LNB pointed at 19E (or offset mounted on 28E dish)
>>> DiSEqC switch(es) located near dishes -- or near your tuner
>>> so you can connect directly from each LNB as a test?
>>> Single cable run from switch to computer, or two cable runs
>>> from two switches?
>>>
>>> LNB19E--
>>>         \               long cable run
>>>          2/1 DiSEqC----------------------------Computer
>>>         /
>>> LNB28E--
>>>   
>>>       
>> i've got 2 80cm satellite dishes, one for Astra 28.2E and the other one 
>> for Astra 19.2E.
>> Then, from each dish i've got like 2-3 meters cable to where the 
>> computer is.
>> Then, next to the computer "the two become one", hehe, through the 
>> diseqc switch.
>>
>>  From diseqc i've got a cable, like 30cm long to the computer
>>
>> The diseqc switch is 2.0, like this one:
>>
>> http://www.sadoun.com/Sat/Products/DiSEqC/DS21-DISEQC-SWITCH.jpg
>>
>>     
>>> You also mention DVB-T/radio from this card; if you could
>>> mention how that affects the above, if at all (it should
>>> not, but I never know for sure)
>>>   
>>>       
>> I don't think it affects in any way. The card has 3 different chips, or 
>> so i think: one for radio, one for digital tv (terrestrial) and one for 
>> satellite tv. In windows you install 3 different drivers. Actually, 
>> windows see the card as 3 different cards, and you can "tune" the three 
>> chips at the same time. for example, you can view satellite while 
>> recording digital tv, which is great :)
>>     
>
> The latter is not true, you can`t view/record DVB-S and DVB-T at once.
> That would need a second saa7131 PCI bridge you don't have.
>
> It is one tda8275a hybrid tuner, which in this case is only used for
> radio and analog TV, a second tda8275a hybrid tuner, which is only used
> for DVB-T on this card with tda10046 channel decoder and a single
> tda826x tuner for DVB-S with tda10086 channel decoder and isl6421 ...
>   

sorry about that, as i said, I'm not a hardware expert, ii just though 
this worked like that but I never used it this way, so...


>   
>> In Linux this doesn't happen. Linux sees the card "as one", and you have 
>> to keep  doing
>>
>> modprobe saa7134 use_frontend=0... =1..=2 to get one chip or another to 
>> work.  Although it would be great to have all of them working at the 
>> same time.. it's not a problem for me, as i actually never used this 
>> feature in windows.
>>
>>     
>>> Also, if you have any spares (a pile of DiSEqC switches,
>>> other DVB-S capable cards, etc), it would be handy for me
>>> to know -- in the case of my 4/1 switches located more
>>> than 50m from my tuners, it was partially a case of
>>> swapping in other switches from my pile of them until
>>> finding a working combination, or running an additional
>>> several hundred metres of cable to permit me to switch
>>> the four positions close to the tuners...
>>>
>>>
>>>   
>>>       
>> i don't think there's any other helpful information to provide.
>>
>>     
>
> We need to go through the code in question, investigate Ubuntu
> downports, reread datasheets as far as available (!) and my first guess
> is your switch worked once with diseqc enabled on the tda10086, at least
> for low. On high with permanent tone from the isl6121 also enabled, I
> doubt it ever came through.
>
> Cheers,
> Hermann
>
>
>
>   

i don't know, this is too technical to me :'(
what I do know is that only for once, i got diseqc 2.0 with astra 19E 
and 28E working in kaffeine.  Ever since that  moment I've tried to 
reproduce  the scenario, but  i haven't got anymore, unfortunately.

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

I've contacted several ubuntu forums about the issue with the kernel, 
but nobody seems to know how to fix it. I will keep getting this message

****************
26.382391] saa7134: Unknown symbol videobuf_qbuf
[ 26.382468] saa7134: disagrees about version of symbol video_device_alloc
****************

again and again....

i've search in this very list and found some users who have had the same 
problem, but i haven't found anyone who got it working.
So... if anyone got it working, i would be very pleased to know, as 
right now ubuntu is for me the best option.

Thanks.

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