Heino Goldenstein schrieb:
I have also a DVB-S fullfeatured 1.3 card and use the drivers
1.0.0, 1.0.1, 1.1.0 and curently 1.1.1.
They all work with DiSEqE without any problems.
This are my DiSEqC parameters
S19.2E 11700 V 9750 v [E0 10 38 F0]
S19.2E 9 V 10600 v [E0 10 38 F1]
S19.2E 1170
I have a VisionPlus (TwinHan) DVB-T card, and am using a 2.6.1 kernel with
the stock DVB drivers.
Using tzap, I get a signal strength of around 34% (5900/) and SNR of
around 38% (6200/.) Using the same card in the same machine under
windows, I get signal strength and 'quality' of around 95
On Sunday 14 March 2004 03:24, you wrote:
> On Saturday 13 March 2004 17:57, Kenneth Aafløy wrote:
> > On Saturday 13 March 2004 16:08, Andrew de Quincey wrote:
> > > On Saturday 13 March 2004 14:59, Kenneth Aafløy wrote:
> > > > On Saturday 13 March 2004 13:45, Andrew de Quincey wrote:
> > > > > W
On Saturday 13 March 2004 17:57, Kenneth Aafløy wrote:
> On Saturday 13 March 2004 16:08, Andrew de Quincey wrote:
> > On Saturday 13 March 2004 14:59, Kenneth Aafløy wrote:
> > > On Saturday 13 March 2004 13:45, Andrew de Quincey wrote:
> > > > Well, in all my tests, I've tried INVERSION_OFF, INVE
hi,
i can't initialize my card i have error "unable to determine DMA" when i
load module dvb-bt8xx
i use last linuxtv cvs and kernel 2.6.3 (debian)
details:
modprobe bttv card=0x71 i2c_hw=1
kernel: bttv: driver version 0.9.12 loaded
kernel: bttv: using 8 buffers with 2080k (520 pages) each for
On Saturday 13 March 2004 23:51, Heino Goldenstein wrote:
> Hello Andrew,
>
> Andrew de Quincey wrote:
>
> ---8<-8<-8<-8<-8<-8<-8<-8<-8<-8<---
>
> > > > What frontend does your v1.3 card have?
> > > >
> > > > If its a ves1x93, I think I'm going to go mad! :)
> >
Hello Andrew,
Andrew de Quincey wrote:
>
---8<-8<-8<-8<-8<-8<-8<-8<-8<-8<---
> >
> > > What frontend does your v1.3 card have?
> > >
> > > If its a ves1x93, I think I'm going to go mad! :)
> >
> > It is a ves1x93.
>
> ARGH!
>
> Hmm, OK this means there are de
On Saturday 13 March 2004 23:58, Heino Goldenstein wrote:
> FWIW:
> I have also a DVB-S fullfeatured 1.3 card and use the drivers
> 1.0.0, 1.0.1, 1.1.0 and curently 1.1.1.
> They all work with DiSEqE without any problems.
>
> This are my DiSEqC parameters
>
> S19.2E 11700 V 9750 v [E0 10 38 F0
On Saturday 13 March 2004 23:18, [EMAIL PROTECTED] wrote:
> Hello Andrew,
>
> Andrew de Quincey wrote:
> > On Saturday 13 March 2004 22:58, Heino Goldenstein wrote:
> > > Hello,
> > >
> > > Andrew de Quincey wrote:
>
> ---8<-8<-8<-8<-8<-8<-8<-8<-8<-8<---
>
> > Wh
Hello Andrew,
Andrew de Quincey wrote:
>
> On Saturday 13 March 2004 22:58, Heino Goldenstein wrote:
> > Hello,
> >
> > Andrew de Quincey wrote:
> >
---8<-8<-8<-8<-8<-8<-8<-8<-8<-8<---
>
> What frontend does your v1.3 card have?
>
> If its a ves1x93, I think
On Saturday 13 March 2004 22:58, Heino Goldenstein wrote:
> Hello,
>
> Andrew de Quincey wrote:
>
> ---8<-8<-8<-8<-8<-8<-8<-8<-8<-8<---
>
> > Really, it needs someone to try all possible combinations of the above to
> > find out which ones are the essential ones.
Hello,
Andrew de Quincey wrote:
>
---8<-8<-8<-8<-8<-8<-8<-8<-8<-8<---
>
> Really, it needs someone to try all possible combinations of the above to
> find out which ones are the essential ones. If I had one of those cards
> I'd do that myself, but I don't.
>
Michael Hunold wrote:
Hello Nico,
On 03/10/04 17:32, Nico wrote:
worse problems with my Twinhan DVB-T: it *never* works with kernel >
2.6.1, whatever
(reasonable) card type I choose: 0x68, 0x5e, 0x71; it always hangs my
pc.
What changed in bttv between 2.6.1 and the following versions?
Am I t
On Saturday 13 March 2004 20:59, Alfred Zastrow wrote:
> Andrew de Quincey schrieb:
> >>- ves1x93_writereg(i2c, 0x00, 0x11);
> >>+// ves1x93_writereg(i2c, 0x00, 0x11);
> >> ret = i2c->xfer (i2c, &msg, 1);
> >>- ves1x93_writereg(i2c, 0x00, 0x01);
> >>+// ves1x93_writereg(i2c, 0x00, 0x01
Andrew de Quincey schrieb:
- ves1x93_writereg(i2c, 0x00, 0x11);
+// ves1x93_writereg(i2c, 0x00, 0x11);
ret = i2c->xfer (i2c, &msg, 1);
- ves1x93_writereg(i2c, 0x00, 0x01);
+// ves1x93_writereg(i2c, 0x00, 0x01);
^^^ this diff makes no difference
The attached diff
On Saturday 13 March 2004 20:27, Alfred Zastrow wrote:
> Andrew de Quincey schrieb:
> > Hmm, weird... if the DISEQC isn't working, it might be locking on to some
> > other unrelated channel though.
>
> The same problem, only a few channels are getting tuned.
>
> > OK, this patch has the other setti
Andrew de Quincey schrieb:
Hmm, weird... if the DISEQC isn't working, it might be locking on to some
other unrelated channel though.
The same problem, only a few channels are getting tuned.
OK, this patch has the other setting changed, so it theoretically should work
with this one... unless bo
On Saturday 13 March 2004 20:02, Alfred Zastrow wrote:
> Alfred Zastrow schrieb:
> > No, ves-fix-4.patch also doesn't work properly. Sometimes I get a
> > picture after > 30 seconds, but mostly the sreen stays black.
>
> The femon-plugin show me a STR of 10%, normaly this value has about 60
> to 70
Alfred Zastrow schrieb:
No, ves-fix-4.patch also doesn't work properly. Sometimes I get a
picture after > 30 seconds, but mostly the sreen stays black.
The femon-plugin show me a STR of 10%, normaly this value has about 60
to 70 %
But it also states LOCK, SIGNAL, CARRIER, VITERBI, SYNC on RTL
Andrew de Quincey schrieb:
Can you try this last patch please so we can identify it.
No, ves-fix-4.patch also doesn't work properly. Sometimes I get a
picture after > 30 seconds, but mostly the sreen stays black.
Alfred
Andreas, I swapped the inversion readings round in this one in FE_GET_FR
On Saturday 13 March 2004 19:13, Alfred Zastrow wrote:
> Andrew de Quincey schrieb:
> > Argh :( Thanks for testing
> >
> > OK, this new version has all the parameters set back to what they were.
> >
> > (I've not changed the kmalloc thing yet; want to find the problem out
> > first)
>
> Bingo, this
Andrew de Quincey schrieb:
Argh :( Thanks for testing
OK, this new version has all the parameters set back to what they were.
(I've not changed the kmalloc thing yet; want to find the problem out first)
Bingo, this one is working :-)
Alfred
--
Info:
To unsubscribe send a mail to [EM
On Saturday 13 March 2004 18:29, Alfred Zastrow wrote:
> Andrew de Quincey schrieb:
> > Can someone try the attached patch (against CVS HEAD). It returns most of
> > the values to how they were previously. There are a few left changed, but
> > I don't want to go too fast.
>
> I test your changes an
Andrew de Quincey schrieb:
Can someone try the attached patch (against CVS HEAD). It returns most of the
values to how they were previously. There are a few left changed, but I don't
want to go too fast.
I test your changes and they also doesn't work for me.
Black screen on every channel.
Alfred
On Sat, 2004-03-13 at 19:12, Andrew de Quincey wrote:
+#pragma pack(1)
+struct ves1x93_state {
+u8 inversion:2;
+};
+#pragma pack()
+
I think this is quite ugly and I'd prefer
struct ves1x93_state {
fe_spectral_inversion_t inversion;
};
without those pragmas.
Regards,
Andre
On Sat, 2004-03-13 at 19:12, Andrew de Quincey wrote:
> Can someone try the attached patch (against CVS HEAD). It returns most of the
> values to how they were previously. There are a few left changed, but I don't
> want to go too fast.
in ves1x93_attach() 'state' is a local variable and you are
On Saturday 13 March 2004 17:28, you wrote:
> Alfred Zastrow schrieb:
> > Copy the "alps_bsrv2.c" and "compat.h" from the DVB-tree to "build-2.4"
>
> Attached is a errorfree compiling diff against dvb-kernel from today
> witch revivals the old alps_bsrv2 frontend driver.
>
> If you want to use it,
> I loaded up the 20040224 cvs drivers and did a quick mod to myth to print
> the returned frontend params from fe_get_frontend, and that reports
> inversion off
Thank you very much for testing that! You've just found another bug in the
stv0299.c. When it reads the inversion from the chip, it ge
On Saturday 13 March 2004 16:08, Andrew de Quincey wrote:
> On Saturday 13 March 2004 14:59, Kenneth Aafløy wrote:
> > On Saturday 13 March 2004 13:45, Andrew de Quincey wrote:
> > > Well, in all my tests, I've tried INVERSION_OFF, INVERSION_ON, and
> > > INVERSION_AUTO. INVERSION_OFF/INVERSION_ON
Alfred Zastrow schrieb:
Copy the "alps_bsrv2.c" and "compat.h" from the DVB-tree to "build-2.4"
Attached is a errorfree compiling diff against dvb-kernel from today
witch revivals the old alps_bsrv2 frontend driver.
If you want to use it, don't load the "ves1x93.o".
For me it works pretty real
Hello Nico,
On 03/10/04 17:32, Nico wrote:
worse problems with my Twinhan DVB-T: it *never* works with kernel >
2.6.1, whatever
(reasonable) card type I choose: 0x68, 0x5e, 0x71; it always hangs my pc.
What changed in bttv between 2.6.1 and the following versions?
Am I the only one that can't u
Andrew de Quincey schrieb:
Index: linux/drivers/media/dvb/frontends/ves1x93.c
===
RCS file: /cvs/linuxtv/dvb-kernel/linux/drivers/media/dvb/frontends/ves1x93.c,v
retrieving revision 1.6
diff -u -r1.6 ves1x93.c
--- linux/drivers/media/
Andrew de Quincey wrote:
>
> On Saturday 13 March 2004 15:00, you wrote:
> > Andrew de Quincey wrote:
> > > OK, this is getting far too confusing. Need to summarise this:
> > >
> > > We're trying two types of DVB-S-fullfeatured cards: the 1.3 and the 1.6
> > >
> > > The 1.3 works fine with the alp
On Saturday 13 March 2004 15:32, you wrote:
> On Saturday 13 March 2004 15:00, you wrote:
> > Andrew de Quincey wrote:
> > > OK, this is getting far too confusing. Need to summarise this:
> > >
> > > We're trying two types of DVB-S-fullfeatured cards: the 1.3 and the 1.6
> > >
> > > The 1.3 works f
On Saturday 13 March 2004 09:43, Alfred Zastrow wrote:
> It is definitely a ves1x93-problem. For testing purposes I load the
> following modules for my rev 1.3-cards:
> ,,,
> #insmod ves1x93 <--- commented out
> insmod alps_bsrv2 <--- from the DVB-Tree
>...
Just an idea:
Have you
On Saturday 13 March 2004 15:00, you wrote:
> Andrew de Quincey wrote:
> > OK, this is getting far too confusing. Need to summarise this:
> >
> > We're trying two types of DVB-S-fullfeatured cards: the 1.3 and the 1.6
> >
> > The 1.3 works fine with the alps_bsrv2(101) driver
> > The 1.3 fails with
On Saturday 13 March 2004 15:00, Klaus Schmidinger wrote:
> Andrew de Quincey wrote:
> > OK, this is getting far too confusing. Need to summarise this:
> >
> > We're trying two types of DVB-S-fullfeatured cards: the 1.3 and the 1.6
> >
> > The 1.3 works fine with the alps_bsrv2(101) driver
> > The
On Saturday 13 March 2004 14:59, Kenneth Aafløy wrote:
> On Saturday 13 March 2004 13:45, Andrew de Quincey wrote:
> > Well, in all my tests, I've tried INVERSION_OFF, INVERSION_ON, and
> > INVERSION_AUTO. INVERSION_OFF/INVERSION_ON are passed directly through to
> > the driver, and work as expecte
Andrew de Quincey schrieb:
OK, this is getting far too confusing. Need to summarise this:
We're trying two types of DVB-S-fullfeatured cards: the 1.3 and the 1.6
The 1.3 works fine with the alps_bsrv2(101) driver
The 1.3 fails with the ves1x93(110) (polarisation switching)
The 1.3 fails with the
> 00:09.0 Class 0480: 1131:7146 (rev 01)
> Subsystem: 13c2:
> Flags: bus master, medium devsel, latency 32, IRQ 17
> Memory at de00 (32-bit, non-prefetchable) [size=512]
>
> 00:0a.0 Class 0480: 1131:7146 (rev 01)
> Subsystem: 13c2:
> Flags: bus master, med
Andrew de Quincey wrote:
>
> OK, this is getting far too confusing. Need to summarise this:
>
> We're trying two types of DVB-S-fullfeatured cards: the 1.3 and the 1.6
>
> The 1.3 works fine with the alps_bsrv2(101) driver
> The 1.3 fails with the ves1x93(110) (polarisation switching)
> The 1.3
On Saturday 13 March 2004 13:45, Andrew de Quincey wrote:
> Well, in all my tests, I've tried INVERSION_OFF, INVERSION_ON, and
> INVERSION_AUTO. INVERSION_OFF/INVERSION_ON are passed directly through to
> the driver, and work as expected for me. INVERSION_AUTO works fine as well.
> And I've had no
Andrew de Quincey schrieb:
Hi, could anyone with the problem please tell me the PCI device IDs for the
cards which aren't working (You can get it with lspci -vn).
Here is a 'lspci -vn' from my vdr-machine:
00:00.0 Class 0600: 1106:3099
Subsystem: 1
OK, this is getting far too confusing. Need to summarise this:
We're trying two types of DVB-S-fullfeatured cards: the 1.3 and the 1.6
The 1.3 works fine with the alps_bsrv2(101) driver
The 1.3 fails with the ves1x93(110) (polarisation switching)
The 1.3 fails with the ves1x93(cvs) (polarisation
On Saturday 13 March 2004 14:45, Helmut Auer wrote:
> It's getting more and more interesting. In my case this doesn't change a
> thing.
> I have the same problems, when I use the alps_bsrv2 instead of the ves1x93.
> Then I tried a dvb-s 1.6 with the grundig tuner and then strange things
> ( in my
Helmut Auer wrote:
>
> Hi Andreas,
>
> >-0x80, 0x00, 0x31, 0xb0, 0x14, 0x00, 0xDC, 0x00,
> >+0x80, 0x00, 0x31, 0xb0, 0x14, 0x00, 0xDC, 0x20,
> >
> just to clarify: my ves1x93.c has the following contens:
>
> 0x80, 0x00, 0x21, 0xb0, 0x14, 0x00, 0xDC, 0x00,
> ^
> What
Hi Andreas,
-0x80, 0x00, 0x31, 0xb0, 0x14, 0x00, 0xDC, 0x00,
+0x80, 0x00, 0x31, 0xb0, 0x14, 0x00, 0xDC, 0x20,
just to clarify: my ves1x93.c has the following contens:
0x80, 0x00, 0x21, 0xb0, 0x14, 0x00, 0xDC, 0x00,
^
What should I try now ?
--
Helmut Auer, [EMAI
Andreas Share wrote:
>
> >
> > > Be careful. The new code _works_ with BSRU6 (stv0299) and the old BSRV2
> > > module. Remember that DiSEqC is _always_ done by the av7110 on
> > > full-featured cards.
> >
> > That is very weird.. So the new-ves1x93 must be in some mode that is
> > interfering with
On Saturday 13 March 2004 13:45, you wrote:
> Hi,
>
> > Helmut Auer schrieb:
> >> Once again ( I don't give up too fast . Isn't here anyone
> >> experiencing the same problem ? On vdrportal the same error is reported.
> >> Do I have to use different diseqc settings ? What has changed from
> >> 1.01
On Saturday 13 March 2004 14:38, Andrew de Quincey wrote:
> > Be careful. The new code _works_ with BSRU6 (stv0299) and the old BSRV2
> > module. Remember that DiSEqC is _always_ done by the av7110 on
> > full-featured cards.
>
> That is very weird.. So the new-ves1x93 must be in some mode that is
Andrew de Quincey schrieb:
Hi, could anyone with the problem please tell me the PCI device IDs for the
cards which aren't working (You can get it with lspci -vn).
I have only limited access to my vdr-machine.
Is the information from "/proc/bus/pci/devices" usefull?
11063099 0 e008 000
>
> > Be careful. The new code _works_ with BSRU6 (stv0299) and the old BSRV2
> > module. Remember that DiSEqC is _always_ done by the av7110 on
> > full-featured cards.
>
> That is very weird.. So the new-ves1x93 must be in some mode that is
> interfering with the DISEQC being sent by the av7110.
Hi,
Helmut Auer schrieb:
Once again ( I don't give up too fast . Isn't here anyone
experiencing the same problem ? On vdrportal the same error is reported.
Do I have to use different diseqc settings ? What has changed from
1.01 to 1.10 in that region ?
It is definitely a ves1x93-problem. For
> Be careful. The new code _works_ with BSRU6 (stv0299) and the old BSRV2
> module. Remember that DiSEqC is _always_ done by the av7110 on
> full-featured cards.
That is very weird.. So the new-ves1x93 must be in some mode that is
interfering with the DISEQC being sent by the av7110... I can't t
On Saturday 13 March 2004 14:18, Andrew de Quincey wrote:
> On Saturday 13 March 2004 12:56, you wrote:
> > On Friday 12 March 2004 20:28, Helmut Auer wrote:
> > > > Helmut Auer wrote:
> > > >> Hello, I have a reproducable error with the 1.1.1 release. When
> > > >> zapping: ARD, ZDF, RTL1, RTL2, V
Hi, could anyone with the problem please tell me the PCI device IDs for the
cards which aren't working (You can get it with lspci -vn).
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
On Saturday 13 March 2004 12:56, you wrote:
> On Friday 12 March 2004 20:28, Helmut Auer wrote:
> > > Helmut Auer wrote:
> > >> Hello, I have a reproducable error with the 1.1.1 release. When
> > >> zapping: ARD, ZDF, RTL1, RTL2, VOX, SAT1 the screen gets black when
> > >> reaching SAT1, and afterw
On Friday 12 March 2004 20:28, Helmut Auer wrote:
> > Helmut Auer wrote:
> >> Hello, I have a reproducable error with the 1.1.1 release. When
> >> zapping: ARD, ZDF, RTL1, RTL2, VOX, SAT1 the screen gets black when
> >> reaching SAT1, and afterwards I can tzap to whatever I want. The
> >> screen st
On Saturday 13 March 2004 12:44, Oliver Endriss wrote:
> On Saturday 13 March 2004 13:30, Andrew de Quincey wrote:
> > One thing that worries me though; if you're using 1.1.1, there isn't an
> > alps_bsrv2 driver any more; it was merged into the stv0299 one a while
> > back.
>
> ???
> He stated tha
On Saturday 13 March 2004 13:30, Andrew de Quincey wrote:
> One thing that worries me though; if you're using 1.1.1, there isn't an
> alps_bsrv2 driver any more; it was merged into the stv0299 one a while back.
???
He stated that he tried the alps_bsrv2 module from DVB.
The alps_bsrv2 is _not_ ba
On Saturday 13 March 2004 03:28, Kenneth Aafløy wrote:
> On Friday 12 March 2004 22:49, you wrote:
> > On Friday 12 March 2004 21:27, Kenneth Aafløy wrote:
> > > On Friday 12 March 2004 22:16, you wrote:
> > > > On Friday 12 March 2004 20:42, Kenneth Aafløy wrote:
> > > > > Hi,
> > > > >
> > > > >
On Saturday 13 March 2004 09:43, Alfred Zastrow wrote:
> Helmut Auer schrieb:
>
> > Once again ( I don't give up too fast :-). Isn't here anyone
> > experiencing the same problem ? On vdrportal the same error is reported.
> > Do I have to use different diseqc settings ? What has changed from 1.01
On Saturday 13 March 2004 12:30, Andrew de Quincey wrote:
> On Saturday 13 March 2004 08:43, Alfred Zastrow wrote:
> > Helmut Auer schrieb:
> > > Once again ( I don't give up too fast :-). Isn't here anyone
> > > experiencing the same problem ? On vdrportal the same error is
> > > reported. Do I ha
On Saturday 13 March 2004 08:43, Alfred Zastrow wrote:
> Helmut Auer schrieb:
> > Once again ( I don't give up too fast :-). Isn't here anyone
> > experiencing the same problem ? On vdrportal the same error is reported.
> > Do I have to use different diseqc settings ? What has changed from 1.01
> >
Hello,
My setup:
hush m1 with SkyStar 2 TV, Fedora Core 1 with 2.6.3 kernel and XFree
4.3.x unichrome drivers for cle266. Worldsat magic positioner DiSEqC 1.0
feeding the SkyStar and a Worldsat analog receiver.
I am using xine (gxine is way too bad - bad image stuttering) to watch
TV. mplaye
Johannes Stezenbach wrote:
>
> Klaus Schmidinger wrote:
> > Ok, so I've set up a machine with SuSE 8.2, kernel 2.4.20,
> > fetched the dvb-kernel driver from today's CVS and the firmware
> > from http://www.linuxtv.org:81/download/dvb/dvb-ttpci-01.fw.
> ^^
> Why?
>
>
Klaus Schmidinger schrieb:
Maybe timing has changed slightly (for whatever reason).
Try to optimize your DiSEqC setup. This might speed-up tuning:
full DiSEqC sequence:
S19.2E 11700 V 9750 [E0 10 38 F0] [E1 10 38 F0] [E1 10 38 F0]
S19.2E 9 V 10600 [E0 10 38 F1] [E1 10 38 F1] [E1 10 38 F1]
>
> And yes: The Technisat Skystar2 is definitely supported by the 1.1.1 driver.
>
> Niklas
i am i am not being irritating. after spending some time on the url u recommended here
is wat i got.
In the dvb-s card section (i guess this is where i should be) the two manafcturers u
recommended
1)
Helmut Auer wrote:
>
> Hi Oliver,
>
> >>>diseqc.conf
> >>>S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 9 V
> >>>...
> >>>
> >>>
> >
> >
> >
> >>>It seems to be that switching to vertical position kills everything.
> >>>
> >>>
> >
> >Maybe timing has changed slightly (for w
Hi Oliver,
diseqc.conf
S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W15 A W15 t S19.2E 9 V
...
It seems to be that switching to vertical position kills everything.
Maybe timing has changed slightly (for whatever reason).
Try to optimize your DiSEqC setup. This might speed-up
Helmut Auer schrieb:
Once again ( I don't give up too fast :-). Isn't here anyone
experiencing the same problem ? On vdrportal the same error is reported.
Do I have to use different diseqc settings ? What has changed from 1.01
to 1.10 in that region ?
It is definitely a ves1x93-problem. For test
71 matches
Mail list logo
