Zoilo Gomez wrote:
P. van Gaans wrote:
P. van Gaans wrote:
Christoph Pfister wrote:
2007/7/7, P. van Gaans [EMAIL PROTECTED]:
P. van Gaans wrote:
e9hack wrote:
P. van Gaans wrote
Christoph Pfister wrote:
Hi,
Am Dienstag, 24. Juli 2007 11:45 schrieb Marvin Hankley:
Hi!
Please find attached a more complete tuning file for Astra 28.2E.
Is that really needed? NIT linking exists which allows the scan apps to find
the other transponders (ideally from a single
Manuel Kampert wrote:
Hi!
Nice to know that I am not the only one in the world having such issues
:-)
In the meantime I have done some logging to track the problem down.
Logging for DST.C is enabled via:
modprobe dst verbose=4
I have also enabled i2c debugging in the kernel.
!
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Zoilo Gomez wrote:
I have one KNC DVB-S card, and 3 Cineview decoders + flat-cables; none
of them seem to work.
Without any CAM module inserted, FTA reception is OK.
But when I
I have one KNC DVB-S card, and 3 Cineview decoders + flat-cables; none
of them seem to work.
Without any CAM module inserted, FTA reception is OK.
But when I insert an official Mediaguard Canal Digitaal, or Aston Seca2
1.7, in both cases all data stops, including FTA channels (BVN);
sometimes
Thank you for pointing out the obvious !
Mauro Carvalho Chehab wrote:
Em Seg, 2007-05-28 às 19:08 +0200, Zoilo Gomez escreveu:
While trying to compile a new kernel I just noticed that many modules /
drivers seem to be missing in make menuconfig?
Also the mercurial download does
While trying to compile a new kernel I just noticed that many modules /
drivers seem to be missing in make menuconfig?
Also the mercurial download does not seem to fix this: only 19 modules
are being linked. Some of the missing stuff includes bt8xx, budget_av etc.
The software is in the tree,
Nico Sabbi wrote:
Nico Sabbi wrote:
Zoilo Gomez wrote:
The Diseqc-specs at
http://www.eutelsat.com/satellites/pdf/Diseqc/Reference%20docs/bus_spec.pdf
(table on page 13) confirm that dvbtune is in fact sending the
wrong command.
With a patched dvbtune (pol-bit and band-bit both inverted
Hi Manu,
Any chance we can finish this issue soon?
Please let me know how I can help; without proper chip-set documentation
it seems to me that I can only wait for you to fix it for me ... but I
can test your patches of course.
Thank you and best regards,
Zoilo.
=
Zoilo Gomez wrote
Hi Michel,
Michel Verbraak wrote:
Zoilo Gomez schreef:
I am also at loss now
Michel: can you confirm that DiSEqC is working for you using the
Mantis driver? Are you 100% that it is DiSEqC that is doing the work,
and not some conventional compatibility function like 18/13V+22kHz
etc
and borrow an oscilloscope somehow, so I can
measure what is going on at the coax level ...
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Manu,
Any chance we can finish this issue soon?
What i don't understand is.. Michel has diseqc working. Quite a bit lost.
Please let me know how I
Michel Verbraak wrote:
Zoilo,
Which program are you using and does the setting of your switch?
dvbtune (slightly modified because DiSEqC implementation of dvbtune-0.5
contains a bug, see my emails about this a couple of days ago) and also
szap.
With KNC1 DVB-S (stv2099 driver) these utils
Hi Manu,
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Michel Verbraak wrote:
Manu, list,
I
Manu Abraham wrote:
Freq+symrate is correct; I tried several freqs / pols / symbol rates on
sat=2.
I am quite sure that the problem is simple and diseqc related, for the
several reasons:
= my normal sat receiver is working fine on all 16 sat feeds (4*4)
= KNC1 DVB-C is also working fine on
Manu Abraham wrote:
sounds like you don't have the tone burst working. Looking in there..
Can you please try the modified burst callback ? You may/may not need to
play a bit with a bit of sleep after the break in each case.
Sorry Manu, but this is not about diseqc-burst either ...
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
sounds like you don't have the tone burst working. Looking in there..
Can you please try the modified burst callback ? You may/may not
need to
play a bit with a bit of sleep after the break in each case
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
sounds like you don't have the tone burst working. Looking in there..
Can you please try the modified burst callback ? You may/may not
need
Nico Sabbi wrote:
Zoilo Gomez wrote:
dvbtune-0.5 source apparently contains a bug where it inverts both
the polarization and high/low band bits in the diseqc command ... as
I cannot find any info on this anywhere, I am posting my results here.
I discovered this while using a KNC1 DVB-S card
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Michel Verbraak wrote:
Manu, list,
I was testing DiseqC to control my rotor (Palm H-H 2100A) and because i
could not get a scan done I finally pulled my rotor from my roof top and
placed it next to the pc.
I found
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Michel Verbraak wrote:
Manu, list,
I was testing DiseqC to control my rotor (Palm H-H 2100A) and
because i
could not get a scan done I finally
After some months of other activities, I am finally in the position to
pick up on DVB stuff again, hurray!
Just for the record: I have now downloaded the (latest?) Mantis sources
from http://jusst.de/manu/mantis-v4l-dvb.tar.bz2.
It seems to work immediately, identifying my 2 Twinhan 1034
successfully to transponders High/Low and Hor/Vert on Hotbird 13.0E.
Thank you Marko.
Zoilo Gomez wrote:
After some months of other activities, I am finally in the position to
pick up on DVB stuff again, hurray!
Just for the record: I have now downloaded the (latest?) Mantis
sources from http
Manu,
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Marcus,
The problems with 2031 were unfortunately never fixed. IIRC we
were left
with the following problems:
1) tuner device sometimes missing in /dev/dvb/adapterX
Hi Manu,
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
...
2) needed to tune twice in case of freq change; the first time would
almost never give a lock (but sometimes it did strangely enough)
...
msleep(20) does not seem
Manu Abraham wrote:
Zoilo Gomez wrote:
===
0 5 0 20 136 75 0 20
dst_ca_ioctl: --CA_GET_SLOT_INFO Success !
dst_ca_ioctl: Sending message
ca_send_message: ca_send_message: Command=[0x9f8020]
ca_send_message: Getting Cam Application information
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
===
0 5 0 20 136 75 0 20
dst_ca_ioctl: --CA_GET_SLOT_INFO Success !
dst_ca_ioctl: Sending message
ca_send_message: ca_send_message: Command=[0x9f8020
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Marcus,
The problems with 2031 were unfortunately never fixed. IIRC we were left
with the following problems:
1) tuner device sometimes missing in /dev/dvb/adapterX/ on boot (app.
20% of the boots, tested on 2 different machines)
2) needed to tune
Manu Abraham wrote:
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Marcus,
The problems with 2031 were unfortunately never fixed. IIRC we were left
with the following problems:
1) tuner device sometimes missing in /dev/dvb/adapterX/ on boot (app.
20
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Marcus,
The problems with 2031 were unfortunately never fixed. IIRC we were left
with the following problems:
1) tuner device sometimes missing in /dev/dvb/adapterX/ on boot (app.
20% of the boots, tested on 2 different machines)
2) needed to tune
Hi Marcus,
The problems with 2031 were unfortunately never fixed. IIRC we were left
with the following problems:
1) tuner device sometimes missing in /dev/dvb/adapterX/ on boot (app.
20% of the boots, tested on 2 different machines)
2) needed to tune twice in case of freq change; the first
Hi Raido,
Good to hear your results.
I can confirm your periodic crashing problem with CAM-modules
(Nagravision in my case); if I wait long enough then eventually the
system will recover though. I use 'vlc' (http://www.videolan.org); with
'-v' flag (verbose) I find that in those cases all
I am quite unhappy about the performance of my Twinhan Cab/CI 2031 DVB-C
cards.
Besides the still unresolved issue of 'tuning needed twice', I have
noticed that in app. 1 out of each 10 times,
/dev/dvb/adapterX/frontend0 and /dev/dvb/adapterX/ca0 appear to be
missing after boot / modprobe.
Hi Raido,
Do you have this problem as well, when switching frequencies?
It only happens when the tuner is sent to a different freq; there is no
problem when switching PIDs within a freq.
Regards,
Z.
Zoilo Gomez wrote:
With the locking problem fixed, it's time to move to the next problem
Hi Manu,
Manu Abraham wrote:
Zoilo Gomez wrote:
I decided to do some tests using kernel 2.6.13.3, with following results:
1) locking problems occur using dvbscan -v (nut also (vlc -v) in the
following situations:
= 2.6.13.3 kernel with downloaded snapshot 20051202: locks fine,
dvb-scan
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Manu,
Manu Abraham wrote:
Zoilo Gomez wrote:
I decided to do some tests using kernel 2.6.13.3, with following
results:
1) locking problems occur using dvbscan -v (nut also (vlc -v) in the
following situations:
= 2.6.13.3 kernel
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Manu,
Manu Abraham wrote:
Zoilo Gomez wrote:
I decided to do some tests using kernel 2.6.13.3, with following
results:
1) locking problems occur using dvbscan -v (nut also (vlc -v) in the
following situations:
= 2.6.13.3 kernel
Hurray, I am not the only one !
( just when I thought I was getting crazy ..)
Raido wrote:
Ok, attached my dmesg from scan -v myscanfile. scan didn't return
anything, only tuning status == 0x00. But get this, strangely
scan -c returns the channels that are on that frequency. Tried
Got it!
Line 1360 in dst_get_tuna checks for !(state-dst_type ==
DST_TYPE_IS_CABLE); if I drop that condition the tuning problem seems fixed.
Zoilo Gomez wrote:
Manu Abraham wrote:
Zoilo Gomez wrote:
Hi Manu,
Manu Abraham wrote:
Zoilo Gomez wrote:
I decided to do some
Manu Abraham wrote:
Zoilo Gomez wrote:
Hurray, I am not the only one !
( just when I thought I was getting crazy ..)
Saw that as well.
Just try this out ..
in dst.c line 1360
!(state-dst_type == DST_TYPE_IS_CABLE)
comment out that line and see whether you are getting
With the locking problem fixed, it's time to move to the next problem
with the Twinhan Cab/CI 2031 card.
I have a Twinhan Cab/CI 2031 (well, actually I have 3 of them) and a KNC1.
Using vlc, on the KNC1, when I tell the card to start streaming a
program, it may take several seconds before it
: Zoilo Gomez [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Dave Schile [EMAIL PROTECTED]
CC: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Please see if you can help: Twinhan VP 1025
DVB-S PCICard
Date: Mon, 14 Aug 2006 03:27:27 +0200
MIME-Version: 1.0
Received: from smtp-vbr17.xs4all.nl
I wonder if you might be experiencing the same problem that I have been
describing over the last week.
It seems to me that hg (and in fact all snapshots after January 2006)
are broken with respect to tuning by dst: whenever I run 'dvbscan -v
freqlist', I get tuning value 0x00 all the time.
: the first time there seems to be no lock.
Ctrl-C, restart and ... locked ! If I pick another PID in the same TS,
there works the first time, so it seems clearly tuner related.
Any help is very much appreciated!
Z.
==
Zoilo Gomez wrote:
I still have some weird problems with the Twinhan Cab/CI
43 matches
Mail list logo
