On Fri, 30 Jul 2004 21:40:24 +0200
Sascha Retzki <[EMAIL PROTECTED]> wrote:
> Ok, Thanks to the replies, I got it working ( still don't know why I
> must modprobe modules seperatly that depends on each other (?)).
I have these lines in /etc/modprobe.conf (fedora core 2 with kernel 2.6.7)
and the
Hi List,
>So the problem is not related to the skystar2 driver, but is at 95% related
>to
>2 card setups (I didn't had this while i had only the FSC Rev 1.3). I will
>try now with EPG scan disabled. Hope this is of any use for some of the
>driver developers.
I've got a TT budget card like nov
On Sunday 20 June 2004 14:30, Andreas Share wrote:
> Hi,
>
> i´m one of the others with the same problem with a new Nova (using the
> budget-ci driver).
> I have the same problem with both cards (TT budget & SS2) and i have done
> some (very little) tests around this.
>
> #1 The driver does not go
> Hi!
>
> I have a two card setup here. The first card is a FSC TT Premium Rev 1.3,
the
> second a skystar 2 2.6b card. I don't know if this is a driver issue or
> related to a two card setup, as i have seen other that seems to have the
same
> problem too with a nova as second card, otherwise th
Am Samstag, 5. Juni 2004 00:27 schrieb Valent:
> Hi. I have SkyStar 2 DVB card. First is it possible to watch satellite
> program on it with VDR?
>
> Second; I have Fedora Core 2 with kernel 2.6.5.
> 2.6 kernels come with already compiled skystar2 module. Is this a
> problem for VDR? Does VDR work
Ronaldo Richieri wrote:
Hello again!
These are lasts lines from dmesg (after ./insmod.sh
load):
--
Linux video capture interface: v1.00
skystar2.c: FlexCopII(rev.130) chip found
skystar2.c: the chip has 6 hardware filters
DVB: registering new adap
Hi,
Johannes Stezenbach wrote:
>>Is the following screenshot of the lockup helpful?
>>
>>http://home.vr-web.de/~rnissl/dvb/p5033564.jpg
>
> Well maybe. I think there were some spin_lock()s missing
> in the software demux, which I added in CVS (dvb_demux.c).
> Generally the rule is that data whi
Reinhard Nissl wrote:
>
> Is the following screenshot of the lockup helpful?
>
> http://home.vr-web.de/~rnissl/dvb/p5033564.jpg
Well maybe. I think there were some spin_lock()s missing
in the software demux, which I added in CVS (dvb_demux.c).
Generally the rule is that data which is shared
Hello again!
These are lasts lines from dmesg (after ./insmod.sh
load):
--
Linux video capture interface: v1.00
skystar2.c: FlexCopII(rev.130) chip found
skystar2.c: the chip has 6 hardware filters
DVB: registering new adapter (Technisat SkySta
Ronaldo Richieri wrote:
Hi Niklas
For running "scan", I need to pass a config file that is in a
subdirectory, right? I put in this file (I took Astra file as sample)
the configuration of my satellite, but I am not sure the units I should
usr. For example, the Frequency is in Mhz? The Symbol Ra
Ronaldo Richieri wrote:
Hellow!! I am a newby using this dvb driver.
I'd like to know if I am making something wronk because I am not able to
lock the transponder on "scan" app, or get the video with mplayer
running szap with my transponder setting.
The steps I did (I am using RedHat 9 with K
Hi,
Johannes Stezenbach wrote:
>> it seems, that current (CVS) dvb-kernel (2.6/2.4) drivers work properly
over several hours, if hyperthreading is disabled (SMP kernel reports a single
CPU).
>>
>> But with hyperthreading enabled, it happens quickly, that my system
freezes. The tests I've done so
On Sat, May 01, 2004 at 10:49:13PM +0200, Reinhard Nissl wrote:
>
> it seems, that current (CVS) dvb-kernel (2.6/2.4) drivers work properly
> over several hours, if hyperthreading is disabled (SMP kernel reports a
> single CPU).
>
> But with hyperthreading enabled, it happens quickly, that my s
I have the same problem without SMP. After ca. 30min without using my SS2
1.3 card, the driver
hangs. When a recording with VDR starts, it restarts because of a "video
data stream broken" error.
When the drivers are reloaded, it works again.
Duron 1,1, MSI KT3V-L, FF 1,6, SS2 1,3, 256MB RAM
> Hi
[EMAIL PROTECTED] wrote:
Hi!
i have some questions to the techinsat skystar2 dvb pci card,
card model is Technisat Skystar 2 ver. 2.3P, frontend is Samsung
TBDU1832IMT (TSA5059+SL1925),
in kernel 2.6.3 and in kernel 2.6.4 the stv0299 modules won't create
/dev/dvb/adapter0/frontend0.
i try to load
Eugene Kolomeetz wrote:
Niklas Peinecke wrote:
Eugene Kolomeetz wrote:
I've tried to use Skystar2 (rev 2.6) for satellite internet with
drivers 1.1.1
It works fine for some time, then traffic stops - no pings come
backs, tcpdump also shows nothing.
femon shown that frontend is locked.
Reloading
Niklas Peinecke wrote:
Eugene Kolomeetz wrote:
I've tried to use Skystar2 (rev 2.6) for satellite internet with
drivers 1.1.1
It works fine for some time, then traffic stops - no pings come
backs, tcpdump also shows nothing.
femon shown that frontend is locked.
Reloading modules helps, but the
Le mar 16/03/2004 à 08:12, Niklas Peinecke a écrit :
> Eugene Kolomeetz wrote:
> > I've tried to use Skystar2 (rev 2.6) for satellite internet with drivers
> > 1.1.1
> > It works fine for some time, then traffic stops - no pings come backs,
> > tcpdump also shows nothing.
> > femon shown that fro
Eugene Kolomeetz wrote:
I've tried to use Skystar2 (rev 2.6) for satellite internet with drivers
1.1.1
It works fine for some time, then traffic stops - no pings come backs,
tcpdump also shows nothing.
femon shown that frontend is locked.
Reloading modules helps, but the same thing happens after
Niklas Peinecke wrote:
Roberto Ragusa wrote:
On Sat, 31 Jan 2004 18:30:23 +0100 (CET)
"Dirk Wellmann" <[EMAIL PROTECTED]> wrote:
Hello @all,
I've got a new one here in my Box. The drivers loads fine, but there
is no
frontend device?
I've compiled the new drivers linuxtv-dvb-1.0.1. With the pri
Roberto Ragusa wrote:
On Sat, 31 Jan 2004 18:30:23 +0100 (CET)
"Dirk Wellmann" <[EMAIL PROTECTED]> wrote:
Hello @all,
I've got a new one here in my Box. The drivers loads fine, but there is no
frontend device?
I've compiled the new drivers linuxtv-dvb-1.0.1. With the primary DVB-S
Device from Sie
On Sat, 31 Jan 2004 18:30:23 +0100 (CET)
"Dirk Wellmann" <[EMAIL PROTECTED]> wrote:
> Hello @all,
>
> I've got a new one here in my Box. The drivers loads fine, but there is no
> frontend device?
>
> I've compiled the new drivers linuxtv-dvb-1.0.1. With the primary DVB-S
> Device from Siemens Re
Twoways wrote:
Hi,
first the card runs under my Linux, with the SuSE 9.0 Kernel and Modules.
(was a nice try from SuSE don't compile b2c2 skystar2 module, but the module
source was included)
But sometimes szap tunes and sometime it will not tune in.
Have someone an idear?
My slove from last night i
Am Donnerstag, 1. Januar 2004 12:50 schrieb Nico:
> Steffen Barszus wrote:
> >Am Mittwoch, 31. Dezember 2003 19:54 schrieb Nico:
> >>If Suse's kernel is like Mandrake's (very messy) than dvb-kernel may
> >>fail to compile.
> >>I suggest you to install a stock 2.4.23 kernel and to apply dvb-kernel:
Steffen Barszus wrote:
Am Mittwoch, 31. Dezember 2003 19:54 schrieb Nico:
If Suse's kernel is like Mandrake's (very messy) than dvb-kernel may
fail to compile.
I suggest you to install a stock 2.4.23 kernel and to apply dvb-kernel:
it's the easiest thing to do.
On Mandrake it does compile
Am Mittwoch, 31. Dezember 2003 19:54 schrieb Nico:
> If Suse's kernel is like Mandrake's (very messy) than dvb-kernel may
> fail to compile.
> I suggest you to install a stock 2.4.23 kernel and to apply dvb-kernel:
> it's the easiest thing to do.
On Mandrake it does compile without problems. And
Georg Golombek wrote:
Am Dienstag, 30. Dezember 2003 23:43 schrieb Nico:
Georg Golombek wrote:
Hello,
unfortunately i got a skystar2 rev 2.6B with Samsung Tuner because my old
"good" skystar2 was damaged.
Then i saw that it doesn't work with the existing driver.
I was looking on linuxtv.o
Am Dienstag, 30. Dezember 2003 23:43 schrieb Nico:
> Georg Golombek wrote:
> >Hello,
> >
> >unfortunately i got a skystar2 rev 2.6B with Samsung Tuner because my old
> >"good" skystar2 was damaged.
> >Then i saw that it doesn't work with the existing driver.
> >
> >I was looking on linuxtv.org for
Am Dienstag, 30. Dezember 2003 22:04 schrieb Georg Golombek:
> Hello,
>
> unfortunately i got a skystar2 rev 2.6B with Samsung Tuner because my
> old "good" skystar2 was damaged.
> Then i saw that it doesn't work with the existing driver.
>
> I was looking on linuxtv.org for a new driver because so
Georg Golombek wrote:
Hello,
unfortunately i got a skystar2 rev 2.6B with Samsung Tuner because my old
"good" skystar2 was damaged.
Then i saw that it doesn't work with the existing driver.
I was looking on linuxtv.org for a new driver because some mails told me that
there is a chance to get
On Tuesday 30 December 2003 22:04, Georg Golombek wrote:
> Hello,
>
> unfortunately i got a skystar2 rev 2.6B with Samsung Tuner because my old
> "good" skystar2 was damaged.
> Then i saw that it doesn't work with the existing driver.
>
> I was looking on linuxtv.org for a new driver because so
Hi,
the FlexCop setup looks good so far, but there seem to be no messages
from the frontend. Did you load the grundig module with debug=1? If so,
there should be more info after the
> Dec 17 19:22:28 Linux kernel: DVB: registering new adapter (Technisat
> SkyStar2 d
> river).
line.
Niklas
MeD
Hi,
I've cvs up and then modifid the grundig_29504-401.c as follows: all addresses 0x55
change to 0x54, all addresses 0x61 change to 0x63. Than commented lines 296-300 in
skystar2.c (just to allow all i2c_msg). The frontend doesn't works. I have no
knowledge of kernel or i2c programing and don't
I did some more tests with the patch and debug=1 and everything looks
fine.
Wolfgang
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Here is another patch for the skystar2.c.
Please, have a close look before committing it to cvs.
It mainly simply disables the default group filter to check pids
00-1f: IMHO, this default really isn't needed: it only adds unnecessary
complexity to the driver (and added unnecessary work to the poo
Hi!
*** REPLY SEPARATOR ***
On 12/11/2003 at 11:34 AM Niklas Peinecke wrote:
>Augusto Cardoso wrote:
>> Hi!
>>
>> Here are the registers for the "two line serial":
>>
>> Reg 0x100
>> WRITE
>> Bits 6-0 CHIPADDRESS
>> Bit 7Reserved
>> Bits 15-8 BASE ADDRESS
>> Bits
Augusto Cardoso wrote:
Hi!
Here are the registers for the "two line serial":
Reg 0x100
WRITE
Bits 6-0 CHIPADDRESS
Bit 7 Reserved
Bits 15-8 BASE ADDRESS
Bits 23-16 DATA1
Bit 24 Start transaction.
Bit 25 R/#W Read=1, Write=0
Bit 27-26 Size of transaction. 00=1, 11=4 bytes.
Bit 29-28 Port selection
On Wed, 10 Dec 2003 16:52:16 +0100
Holger Waechtler <[EMAIL PROTECTED]> wrote:
> > adapter->dmxdev.filternum = 32;
>
> You can safely set this number to 256 -- when you open the whole
Committed.
--
Roberto Ragusar.ragusa at libero.it
--
Info:
To unsubscribe send a mail to [EMAIL PRO
On Wed, 10 Dec 2003 18:28:15 +0100
Wolfgang Thiel <[EMAIL PROTECTED]> wrote:
> I'ld also vote to use just native 'int' for real counters, like pid_rc:
Right.
We haven't done the full step away from "use higher pid bits" yet. :-)
Committed.
--
Roberto Ragusar.ragusa at libero.it
--
In
I think there is a bug in remove_pid(). See patch.
I'ld also vote to use just native 'int' for real counters, like pid_rc:
this will add a few bytes to a structure, but it might as well result in
a performance improvement, and it will avoid errors coming from checking
a u8 counter for <= 0.
Or: we
Arrggghhh. I hit the wrong key again...
Here is the attachment.
--- skystar2.c.sav 2003-12-10 17:00:52.0 +
+++ skystar2.c 2003-12-10 18:11:39.0 +
@@ -1244,6 +1244,7 @@ static int remove_pid(struct adapter *ad
// remove from the list
Niklas Peinecke wrote:
Roberto Ragusa wrote:
On Wed, 10 Dec 2003 08:32:48 +0100
Niklas Peinecke <[EMAIL PROTECTED]> wrote:
Hi Roberto,
good work, indeed!
I attached a (trivial) patch that removes two empty if-clauses and
speeds up the pid removal (from O(n) to O(1)).
Thanks.
The empty "if" wa
Roberto Ragusa wrote:
On Wed, 10 Dec 2003 08:32:48 +0100
Niklas Peinecke <[EMAIL PROTECTED]> wrote:
Hi Roberto,
good work, indeed!
I attached a (trivial) patch that removes two empty if-clauses and
speeds up the pid removal (from O(n) to O(1)).
Thanks.
The empty "if" was there because it was "
On Wed, 10 Dec 2003 08:32:48 +0100
Niklas Peinecke <[EMAIL PROTECTED]> wrote:
> Hi Roberto,
>
> good work, indeed!
> I attached a (trivial) patch that removes two empty if-clauses and
> speeds up the pid removal (from O(n) to O(1)).
Thanks.
The empty "if" was there because it was "emptied" duri
Hi!
Committed to the CVS.
Thanks.
Augusto
*** REPLY SEPARATOR ***
On 12/10/2003 at 8:32 AM Niklas Peinecke wrote:
>Hi Roberto,
>
>good work, indeed!
>I attached a (trivial) patch that removes two empty if-clauses and
>speeds up the pid removal (from O(n) to O(1)).
>
>
Hi Roberto,
good work, indeed!
I attached a (trivial) patch that removes two empty if-clauses and
speeds up the pid removal (from O(n) to O(1)).
Thanks,
Niklas
Roberto Ragusa wrote:
Hi all,
I just committed a not trivial patch to skystar2.c.
Changelog:
- pid addition/removal and open_whole_ba
Hi!
Here are the registers for the "two line serial":
Reg 0x100
WRITE
Bits 6-0CHIPADDRESS
Bit 7 Reserved
Bits 15-8 BASE ADDRESS
Bits 23-16 DATA1
Bit 24 Start transaction.
Bit 25 R/#W Read=1, Write=0
Bit 27-26 Size of transaction. 00=1, 11=4 bytes.
Bit 29-28 Port selection 00=Invalid,
Hi,
well the one and only time that it occured was scary enough (I had to do
a reset of the system and fschk then)! But maybe I'll make a backup of
my system and then have a few more tries.
What do all the registers in i2c_main_write_for_flex2 mean? I pretend
0x4000 is some kind of "write su
Hi!
That's what I was thinking, but I tested in a system with multiple 2.6 only and it was
OK. I only tried couple of times. Because I didn't get a failure, I started thinking
about race conditions or other exotic problems. It could as well be something very
simple that for some reason don't sh
Hi Augusto,
maybe this is just _because_ you have multiple cards? Maybe the mt312
wants some feedback ;)
Niklas
Augusto Cardoso wrote:
Hi!
Thanks for the info.
Does it happen every time?
I have multiple cards in my system and I always load the mt312 and the stv0299. The
mt312 probe all cards
Hi!
Thanks for the info.
Does it happen every time?
I have multiple cards in my system and I always load the mt312 and the stv0299. The
mt312 probe all cards and finds the right ones. Then the stv0299 find the other cards.
This sounds like a race condition or some other odd situation.
Since I wa
Augusto Cardoso wrote:
Hi!
I haven't been able to reproduce this problem.
Can some one that has the problem provide some information?
For example, order that the modules are loaded, some system information, what version
of the driver and kernel, etc.
I experienced this last week:
System: K6/2 40
Hi!
I haven't been able to reproduce this problem.
Can some one that has the problem provide some information?
For example, order that the modules are loaded, some system information, what version
of the driver and kernel, etc.
Thanks.
Augusto
*** REPLY SEPARATOR ***
Thank you all,
we are working on student project focused on streaming of video over network. The card
was a gift of a company which test DVB-T broadcasting. Tahy gave us just a piece of
hardware and didn't tell what it is.
Now some other guys are working with the card, as soon as the return it to
Hi!
Your machine code skills are pretty good. 0x54 for the L64781 and 0x63 for the PLL.
Augusto
*** REPLY SEPARATOR ***
On 12/5/2003 at 11:20 AM Niklas Peinecke wrote:
>Niklas Peinecke wrote:
>> Hi MeDon,
>>
>> I took a look at the BBTI driver. I looks like the i2c a
Ok, everything fixed. DiSEqC re-added.
I don't know why, but ttusb did not compile anymore.
To fix it I just had to move inclusion of interrupt.h after spinlock.h
(I moved after all system includes).
Maybe I had truble compiling because smp was kernel not tested on new
ttusb changes.
Il ven, 200
The problem should be in ttusb_dec.c. It seem a .h file was removed.
/usr/src/linux-2.4.22-sata-p/include/asm/hw_irq.h
was not touched by me! old CVS compiles.
Il ven, 2003-12-05 alle 12:59, Niklas Peinecke ha scritto:
> Hmm, this has got nothing to do with the changes we made.
>
> hw_irq.h
>
Hmm, this has got nothing to do with the changes we made.
hw_irq.h
seems to be the problem.
Niklas
Vincenzo Di Massa wrote:
I'm redoing the patch but CVS does not compile!
gcc -I/home/hawk/stanzino/src/DVB-KERNEL/dvb-kernel/build-2.4/include
-D__KERNEL__ -I/usr/src/linux-2.4.22-sata-p/include
I'm redoing the patch but CVS does not compile!
gcc -I/home/hawk/stanzino/src/DVB-KERNEL/dvb-kernel/build-2.4/include
-D__KERNEL__ -I/usr/src/linux-2.4.22-sata-p/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-bound
Augusto Cardoso wrote:
Hi!
The B2C2 DVB-T that uses the Grundig 29504-401.02, was called Air2PC-DVB rev 0.2 by B2C2 and AirStar2 by Technisat.
Well, it looks like in Europe things are actually a little more complicated:
Too me it seems like the rev0.2 cards were sold as "Airstar", while the
"Air
Niklas Peinecke wrote:
Hi MeDon,
I took a look at the BBTI driver. I looks like the i2c address of the
L647818 is 0x54 on the flexcop (not 0x55 like in the frontend module).
Hope this helps.
Niklas
... and the pll address seems to be 0x63 (not 0x61). But please do not
rely too much on that in
Hi MeDon,
I took a look at the BBTI driver. I looks like the i2c address of the
L647818 is 0x54 on the flexcop (not 0x55 like in the frontend module).
Hope this helps.
Niklas
MeDon wrote:
Hi,
we have Technisat SkyStar2 FlexCopIIB(rev.195) in DVB-T version. It
doesn't work. I guess it is becau
Hi!
The B2C2 DVB-T that uses the Grundig 29504-401.02, was called Air2PC-DVB rev 0.2 by
B2C2 and AirStar2 by Technisat.
The Grundig module is no longer been manufacturer. B2C2 made about 500 of these cards.
There is a rev 0.3 that is based on the Zarlink(Mitel) part. The rev 0.3 never went in
pr
Niklas Peinecke wrote:
Holger Waechtler wrote:
MeDon wrote:
Hi,
we have Technisat SkyStar2 FlexCopIIB(rev.195) in DVB-T version. It
doesn't work. I guess it is because frontend. The mt312 writes (in
debug mode):
Dec 3 01:17:26 cooler kernel: master_xfer: read error !
Dec 3 01:17:26 cooler ke
Holger Waechtler wrote:
MeDon wrote:
Hi,
we have Technisat SkyStar2 FlexCopIIB(rev.195) in DVB-T version. It
doesn't work. I guess it is because frontend. The mt312 writes (in
debug mode):
Dec 3 01:17:26 cooler kernel: master_xfer: read error !
Dec 3 01:17:26 cooler kernel: message 2: flags=0
MeDon wrote:
Hi,
we have Technisat SkyStar2 FlexCopIIB(rev.195) in DVB-T version. It
doesn't work. I guess it is because frontend. The mt312 writes (in debug
mode):
Dec 3 01:17:26 cooler kernel: master_xfer: read error !
Dec 3 01:17:26 cooler kernel: message 2: flags=0x0, addr=0x3a,
buf=0x85,
Ooops, seems like you already solved this ;)
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Vincenzo Di Massa wrote:
Does anybody use a skystar2 on a tone burst old diseqc?
I'm trying without success.
The registers of the vp310 seem to be set up correctly, but diseqc never
switches!
I know the my diseqc is not broken, and my skystar2 is not broken.
The driver must be broken.
With the
What type of a frontend are you using? mt312?
M.
yes
D A
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
How do you play the stream (and tune the card), btw?
Maybe I'm doing something wrong ...
Read the INSTALL (or README?) file of the DVB drivers. There it says how
to use szap and mplayer or xine.
D A
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subje
On Mon, 3 Nov 2003, Dark Avenger wrote:
> > Well, I expected that, but how about the 2.3? Does anyone have it working
> > in the current (stable) release?
>
> Works nicely in my setup. Currently using kernel2.6-test9-mm1 with built
> in dvb drivers.
Have you also tried that with 2.4 (I was using
Well, I expected that, but how about the 2.3? Does anyone have it working
in the current (stable) release?
Works nicely in my setup. Currently using kernel2.6-test9-mm1 with built
in dvb drivers.
D A
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
sub
On Mon, 3 Nov 2003, Niklas Peinecke wrote:
> > I have problems with a skystar2 card (tested with the latest
> > 1.0.1 driver):
> >
> > bash# ./apps/szap/szap -c ~/Astra1 -n 73
> [...]
> >00 00 00 00
> >00 00 00 00
> >00 00 00 00
> > DVB: registering new adapter (PCI device 13d0:21
Michal Svec wrote:
Hi!
I have problems with a skystar2 card (tested with the latest
1.0.1 driver):
bash# ./apps/szap/szap -c ~/Astra1 -n 73
[...]
00 00 00 00
00 00 00 00
00 00 00 00
DVB: registering new adapter (PCI device 13d0:2103 (Techsan Electronics Co Ltd)).
mt312.c: setup for
TAZ wrote:
Jun 26 00:00:47 tazlinux kernel: skystar2.c: key =
Jun 26 00:00:47 tazlinux kernel: b2 00 00 00
Jun 26 00:00:47 tazlinux kernel: 00 00 00 00
Jun 26 00:00:47 tazlinux last message repeated 2 times
Jun 26 00:00:47 tazlinux kernel: DVB: registering new adapter (PCI device
13d0:2103 (
Hi!
Please see below.
*** REPLY SEPARATOR ***
On 10/9/2003 at 8:39 AM Niklas Peinecke wrote:
>Hi Augusto,
>
>>
>> For the Samsung tuner, the master clock should be 88MHz.
>
>Hmm, that is the default. Should be OK.
>btw. There seems to be a quartz called "KONY 03-23 45. KCH
Niklas Peinecke wrote:
Hi Augusto,
For the Samsung tuner, the master clock should be 88MHz.
Hmm, that is the default. Should be OK.
btw. There seems to be a quartz called "KONY 03-23 45. KCH089B3"
soldered to the card. Is that the origin of the XTAL_CLK signal?
Kony's spec says it is a 45 M
Hi Augusto,
For the Samsung tuner, the master clock should be 88MHz.
Hmm, that is the default. Should be OK.
btw. There seems to be a quartz called "KONY 03-23 45. KCH089B3"
soldered to the card. Is that the origin of the XTAL_CLK signal?
If you don't get Viterbi, you should check the Spectr
Hi!
For the Samsung tuner, the master clock should be 88MHz.
If you don't get Viterbi, you should check the Spectral Inversion.
Note that the version of the Samsung NIM that B2C2 uses is custom made. The "normal"
tuner is vertical mounted. The B2C2 version is horizontal mounted and there are cou
On Wed, 2003-10-08 at 13:58, Niklas Peinecke wrote:
> > Did you try the sl1935 routine from stv0299.c before? The one from
> > mt312.c uses some general purpose pins for different symbol rate ranges.
> > I don't know what effect they might have on the Samsung frontend.
> > Basically, the Samsung NI
Andreas Oberritter wrote:
On Wed, 2003-10-08 at 08:18, Niklas Peinecke wrote:
Basically I fixed a bug in skystar2.o concerning i2c-handling and put it
together with the stv0299 driver and the sl1935 tuning routine from the
mt312 driver, then I get a signal and a carrier from the card, but no
vi
On Wed, 2003-10-08 at 08:18, Niklas Peinecke wrote:
> Basically I fixed a bug in skystar2.o concerning i2c-handling and put it
> together with the stv0299 driver and the sl1935 tuning routine from the
> mt312 driver, then I get a signal and a carrier from the card, but no
> viterbi (signal too l
Niklas Peinecke wrote:
Hi all,
I'm working on a driver for the new Technisat Skystar2 rev2.6B (also
known as 2.68). It's got a different tuner than the old revision (a
Samsung TBMU24112IMB1 with a STV0299 and a SL1935).
Basically I fixed a bug in skystar2.o concerning i2c-handling and put it
to
On Tue, 2003-09-30 at 10:02, Szczepan Konieczny wrote:
>Try to use B2C2 oryginal drivers (new release compiled for newer gcc 3.2.x
> compiled kernels should apear this week at
I'd rather spend my time on fixing the detection of the STV0299 and its
SL1935 PLL. The driver is ready since months (
Hi,
Try to use B2C2 oryginal drivers (new release compiled for newer gcc 3.2.x
compiled kernels should apear this week at
http://http://www.bbti.us/support.htm),
however e.g VDR will not work, and other Linux DVB driver based tools,
but I hope I will be able to tune this SS2 tuner and watch TV
hi
> Hello,
> I have a big problems with my new DVB-S SkyStar 2 TV (rev.
2.6B/2.68)
> based on B2C2 FlexCopII
> using with dvb-20030905 drivers (I also tried other versions
unsuccessfully).
i cannot use my SS2 Rev. 2.6x also. I hope we will get a christmas
present for supporting this SS2 tuner ;)
Salve,
Am Donnerstag, 25. September 2003 23:53 schrieb Holger Waechtler:
> Can you please tell us what frontend and demodulator chip is soldered on
> your card?
I have borrowed a SkyStar2 from a friend and it is still on my todo to check
if it will run (@Nico thank you for recording the EbS softw
Robert Schlabbach wrote:
From: "Radovan Garabik" <[EMAIL PROTECTED]>
The frontend does not recognize the card, since it uses
the new TBMU24112IMB1 tuner.
http://www.gs.ru/soft/ss2/doc/TBMU24112IMB1.pdf
It says the tuner consists of an SL1935 PLL and the STV0299B demodulator.
At least the latter
From: "Radovan Garabik" <[EMAIL PROTECTED]>
> The frontend does not recognize the card, since it uses
> the new TBMU24112IMB1 tuner.
> http://www.gs.ru/soft/ss2/doc/TBMU24112IMB1.pdf
It says the tuner consists of an SL1935 PLL and the STV0299B demodulator.
At least the latter is already supported
Hi,
I have asked Technotrend for the tuner who have replied as:
the tuner is a TBMU24112IMB1 from Samsung.
To get details about it contact Samsung directly.
Support Team
Hope this helps
J
> Szczepan Konieczny wrote:
> > Hi,
> > this is newer version of rev2.3 but changes was rather cosmeti
Szczepan Konieczny wrote:
Hi,
this is newer version of rev2.3 but changes was rather cosmetic
from end user point of view:lower heat emission, and beter graphics quality...
I was sure that this SkyStar new model is used by other people
under Linux and is full supported.
It seems to work with oryg
From: "Tapio Karinsalo" <[EMAIL PROTECTED]>
> insmod skystar2.o
Isn't "skystar2" a satellite card...?
> 00:0b.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
> Subsystem: Tecnotrend Systemtechnik GmbH: Unknown device 0002
And AFAIK the TT card 0002 is a full-featured *CABLE* car
03 17:27 GMT
> To: [EMAIL PROTECTED]
> Subject: [linux-dvb] Re: Skystar2 data problem
>
> I have noticed that the pings do not return to normal until I do:
> "ifconfig dvb0_0 down" and also "dvbnet -d 0"
>
>
> >
> > From: Paul Hirons &l
I have noticed that the pings do not return to normal until I do:
"ifconfig dvb0_0 down" and also "dvbnet -d 0"
>
> From: Paul Hirons <[EMAIL PROTECTED]>
> Date: Tue 29/Jul/2003 08:53 GMT
> To: [EMAIL PROTECTED]
> Subject: [linux-dvb] Skystar2 data problem
>
> I have a dialup connection on ppp0
Am Montag, 21. Juli 2003 09:05 schrieben Sie:
> Hi again,
> i use a skystar2 in combination with a dxr3 Hollywood+ Card. I got a
> picture, but with many,many framedrops.
Hi
i have the same problem with a skystar2 rev 2.3 and a Hauppauge DVB-s 2.1.
The picture form the DVB-s 2.1 Card is ok. If i
hi
> Did you try mplayer or xine, instead of vdr ?
mplayer produced a perfect tv-picture. The OSD from vdr is perfect
also. This _must_ be a problem with skystar2 driver.
greetings
tobias
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
Did you try mplayer or xine, instead of vdr ?
On Mon, 2003-07-21 at 16:51, Tobias Faust wrote:
> hi
>
> i will get this syslogentries during playback the dvbs livestream with
> vdr
>
> Jul 21 15:45:25 mephisto vdr[1001]: switching to channel 42
> Jul 21 15:45:25 mephisto vdr[1074]: transfer thre
hi
i will get this syslogentries during playback the dvbs livestream with
vdr
Jul 21 15:45:25 mephisto vdr[1001]: switching to channel 42
Jul 21 15:45:25 mephisto vdr[1074]: transfer thread ended (pid=1074)
Jul 21 15:45:25 mephisto vdr[1075]: receiver thread ended on device 1
(pid=1075)
Jul 21 15
sorry, wrong data here is the right:
mephisto:/usr/local/vdr/DVB/apps/szap # ./szap -c
/video/channels.conf -n 43
reading channels from file '/video/channels.conf'
zapping to 'EinsMuXx':
sat 0, frequency = 12110 MHz H, symbolrate 2750, vpid = 0x012d,
apid = 0x012e
using '/dev/dvb/adapter0/
hi
> > flexcop_diseqc_ioctl: SEC_VOLTAGE_18,1
> > flexcop_diseqc_ioctl: SEC_TONE_ON,0
> this is a debug message, not an error.
ok...
> > i use a skystar2 in combination with a dxr3 Hollywood+ Card. I got
a
> > picture, but with many,many framedrops and fragments until the
> > tv-screen will be fro
1 - 100 of 123 matches
Mail list logo
