Re: [linux-dvb] Problem with dvb_ttpci
On Wednesday 07 November 2007 22:19:54 Trent Piepho wrote: > On Wed, 7 Nov 2007, VDR User wrote: > > With recent copies of fresh v4l I started getting the following error > > upon trying to load drivers for my nexus-s: > > > > dvb_ttpci: Unknown symbol ttpci_eeprom_parse_mac > > > > After searching on google I found that this problem existed once > > before and here is a patch that reflects the fix > > Did you remember to run depmod after installed new modules? The > ttpci-eeprom module should be automatically loaded by modprobe. > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, I did experience the same issue. When you are upgrading the v4l source from repository do not forget to verify that the old .config is still valid. Unfortunately there is no make oldconfig option available. the only way to enable ttpci_eeprom config is to do a make menu config and to deselect ttpci support and select it back. If you compare the 2 .config file you will see that the ttpci_eeprom is now selected. Is it possible to create a "oldconfig" label to check the .config file integrity? (in make_kconfig.pl or make_myconfig.pl) In the past it was working, I don't know why it was dropped. Cheers, Alex ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TT Cynergy 1200 DVB-C Device 1176
Thomas Kaiser wrote: > Hi > > I read this thread > http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015663.html but I > can > not figure out if this card is now supported by linux-dvb? Should be supported by the budget-av driver. Oliver -- VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Help. VIDIOC_S_FMT
Dear everyone: I wonder why v4l2 driver cancel all the urbs in VIDIOC_S_FMT and then reinit all the urbs to submit. VIDIOC_S_FMT only negotiate frame format with application like mplayer and has nothing to do with our v4l2 driver. And in my driver I follow the way most drivers have taken, but when I use usb_submit_urb() in VIDIOC_S_FMT to submit all the urbs successfully reinited, my Ubuntu crashes. Caps and Scroll flash during my Ubuntu crashes. I can't get any value message from my syslog. Could somebody help me with this issue? Thank you in advance! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVICO NANO Australia
Thanks for the fast response - yes it does work in windows. - Original Message - From: "Michael Krufky" <[EMAIL PROTECTED]> To: "Collier Family" <[EMAIL PROTECTED]> Cc: Sent: Thursday, November 08, 2007 2:58 PM Subject: Re: [linux-dvb] DVICO NANO Australia > Michael Krufky wrote: >> Collier Family wrote: >>> I have a DVICO NANO but I am having the same troubles others had in >>> June. It appears it is not being recognised as being cold. >>> >>> I have followed the instructions at >>> http://fremnet.net/article/228/dvico-fusionhdtv-dual-digital-4-under-linux >>> and all went well except the frontend not set. dmesg follows >>> >>> usb 5-8: new high speed USB device using ehci_hcd and address 9 >>> usb 5-8: configuration #1 chosen from 1 choice >>> dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2' in warm state. >>> dvb-usb: bulk message failed: -22 (2/0) >>> dvb-usb: will pass the complete MPEG2 transport stream to the software >>> demuxer. >>> DVB: registering new adapter (DViCO FusionHDTV DVB-T NANO2) >>> dvb-usb: bulk message failed: -110 (1/0) >>> dvb-usb: bulk message failed: -110 (3/0) >>> dvb-usb: bulk message failed: -110 (3/0) >>> dvb-usb: bulk message failed: -110 (5/0) >>> dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T NANO2' >>> dvb-usb: DViCO FusionHDTV DVB-T NANO2 successfully initialized and >>> connected. >>> >>> Is there any other information that may help I am running vanilla >>> 2.6.23.1 kernel on Scientific linux 5.0 >>> >>> Thanks a lot for the work so far. >> >> The DVB-T NANO2 does not require the bluebird firmware -- the fx2 boots >> it from the eeprom. So, the device does not have a "cold" state. The >> only firmware that you need for it is the xc3028 firmware that was used >> in Markus' xc3028 kernel driver. >> >> However, there is alternate firmware required for the xc3028 for use in >> Australia. I assume that you already have that. > > Sorry, I forgot to add the "helpful advice" ;-) > > ...It looks like the driver is having trouble accessing the zl10353. Can > you check to make sure the device works in windows? > > -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVICO NANO Australia
Michael Krufky wrote: > Collier Family wrote: >> I have a DVICO NANO but I am having the same troubles others had in June. >> It appears it is not being recognised as being cold. >> >> I have followed the instructions at >> http://fremnet.net/article/228/dvico-fusionhdtv-dual-digital-4-under-linux >> and all went well except the frontend not set. dmesg follows >> >> usb 5-8: new high speed USB device using ehci_hcd and address 9 >> usb 5-8: configuration #1 chosen from 1 choice >> dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2' in warm state. >> dvb-usb: bulk message failed: -22 (2/0) >> dvb-usb: will pass the complete MPEG2 transport stream to the software >> demuxer. >> DVB: registering new adapter (DViCO FusionHDTV DVB-T NANO2) >> dvb-usb: bulk message failed: -110 (1/0) >> dvb-usb: bulk message failed: -110 (3/0) >> dvb-usb: bulk message failed: -110 (3/0) >> dvb-usb: bulk message failed: -110 (5/0) >> dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T NANO2' >> dvb-usb: DViCO FusionHDTV DVB-T NANO2 successfully initialized and connected. >> >> Is there any other information that may help I am running vanilla 2.6.23.1 >> kernel on Scientific linux 5.0 >> >> Thanks a lot for the work so far. > > The DVB-T NANO2 does not require the bluebird firmware -- the fx2 boots it > from the eeprom. So, the device does not have a "cold" state. The only > firmware that you need for it is the xc3028 firmware that was used in Markus' > xc3028 kernel driver. > > However, there is alternate firmware required for the xc3028 for use in > Australia. I assume that you already have that. Sorry, I forgot to add the "helpful advice" ;-) ...It looks like the driver is having trouble accessing the zl10353. Can you check to make sure the device works in windows? -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVICO NANO Australia
Collier Family wrote: > I have a DVICO NANO but I am having the same troubles others had in June. It > appears it is not being recognised as being cold. > > I have followed the instructions at > http://fremnet.net/article/228/dvico-fusionhdtv-dual-digital-4-under-linux > and all went well except the frontend not set. dmesg follows > > usb 5-8: new high speed USB device using ehci_hcd and address 9 > usb 5-8: configuration #1 chosen from 1 choice > dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2' in warm state. > dvb-usb: bulk message failed: -22 (2/0) > dvb-usb: will pass the complete MPEG2 transport stream to the software > demuxer. > DVB: registering new adapter (DViCO FusionHDTV DVB-T NANO2) > dvb-usb: bulk message failed: -110 (1/0) > dvb-usb: bulk message failed: -110 (3/0) > dvb-usb: bulk message failed: -110 (3/0) > dvb-usb: bulk message failed: -110 (5/0) > dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T NANO2' > dvb-usb: DViCO FusionHDTV DVB-T NANO2 successfully initialized and connected. > > Is there any other information that may help I am running vanilla 2.6.23.1 > kernel on Scientific linux 5.0 > > Thanks a lot for the work so far. The DVB-T NANO2 does not require the bluebird firmware -- the fx2 boots it from the eeprom. So, the device does not have a "cold" state. The only firmware that you need for it is the xc3028 firmware that was used in Markus' xc3028 kernel driver. However, there is alternate firmware required for the xc3028 for use in Australia. I assume that you already have that. -Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVICO NANO Australia
I have a DVICO NANO but I am having the same troubles others had in June. It appears it is not being recognised as being cold. I have followed the instructions at http://fremnet.net/article/228/dvico-fusionhdtv-dual-digital-4-under-linux and all went well except the frontend not set. dmesg follows usb 5-8: new high speed USB device using ehci_hcd and address 9 usb 5-8: configuration #1 chosen from 1 choice dvb-usb: found a 'DViCO FusionHDTV DVB-T NANO2' in warm state. dvb-usb: bulk message failed: -22 (2/0) dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DViCO FusionHDTV DVB-T NANO2) dvb-usb: bulk message failed: -110 (1/0) dvb-usb: bulk message failed: -110 (3/0) dvb-usb: bulk message failed: -110 (3/0) dvb-usb: bulk message failed: -110 (5/0) dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T NANO2' dvb-usb: DViCO FusionHDTV DVB-T NANO2 successfully initialized and connected. Is there any other information that may help I am running vanilla 2.6.23.1 kernel on Scientific linux 5.0 Thanks a lot for the work so far. Stephen Collier ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problems with DVB-S using Hauppauge HVR-3000
Hi all, I've been fighting this card for weeks now. I have this card running with CentOS5 and the 2.6.24-rc1 kernel. I have a UNIVERSAL LNB Sat dish pointed at Astra28.2E The problem is that I can't scan for channels on the lo-band only on the hi-band. I'm using the latest hg clone of the v4l-dvb tree, with the exception of adjusting the cx88-dvb driver to start the cx24123 frontend and not the cx22702 by default. I have tried the stoth hvr3000 drivers with the 2.6.18 kernel and suffer the same problem. The dish works perfectly with the sky digibox. In the current setup if I use dvbstream/dvbtune i can lock and stream from any channel hi or lo band. However if i use scan to build a channel list I only get channels on the hi-band. Mythtv wont scan either and kaffeine wont scan or even lock to the provided channel details. I'm totally stumped as to why dvbtune and stream both work but nothing else does. Can any one give me any pointers? TIA Mark Guz ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB tuning in JNI does not work (solved)
Duh. 2 days of hunting, and I find the problem right after I post - typical.
I used the wrong order of magnitude for the frequencies (incl. LNB) and
symbol rate.
And that although I in the beginning tried to make extra sure they are
correct, remembering that it was a major problem a few years ago when I
implemented the original DVB support for MythTV. The MHz vs. KHz vs. Hz
is a mess, same for symbolrate.
Correct is, for 12817 MHz and Universal LNB, to tune to 1587000, LNB
hiband true, in my case with pol H and symbolrate 2750.
// LNB
boolean hiband = false;
int frequency = c.frequency;
final int lnb_low_val = 975; // Universal LNB
final int lnb_high_val = 1060;
final int lnb_switch_val = 1170;
if (frequency >= lnb_switch_val)
hiband = true;
if (hiband)
frequency = frequency - lnb_high_val;
else
{
if (frequency < lnb_low_val)
frequency = lnb_low_val - frequency;
else
frequency = frequency - lnb_low_val;
}
int satNo = 0;
CoreServer.me.debug("Tuning to " + c.frequency + " (" + frequency
+ " considering LNB), LNB hiband " + hiband
+ ", pol " + (polarity_v ? "V" : "H") + ", symbolrate " +
symbolrate);
myFrontendFD = tuneToNative(myFrontendFilename, frequency,
symbolrate, polarity_v, hiband, satNo, false);
tuneToNative:
...
p.frequency = frequency;
p.u.qpsk.symbol_rate = symbolrate;
...
says: Tuning to 12187000 (1587000 considering LNB), LNB hiband true, pol
H, symbolrate 2750
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] TT Cynergy 1200 DVB-C Device 1176
Hi I read this thread http://www.linuxtv.org/pipermail/linux-dvb/2007-February/015663.html but I can not figure out if this card is now supported by linux-dvb? Thomas -- http://www.kaiser-linux.li ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DVB tuning in JNI does not work
I'm trying to write a DVB recording application in Java. I chose JNI and
a small native C/C++ function for tuning. However, I can't get tuning to
work - I get no tuning lock and nothing on dvr either.
As a test, I also copied the szap code verbatim into my file and just
called zap_to() instead of my code, and it did not work either. Plain
szap on commandline works.
This suggests JVM/JNI as culprit, but dvbcentral also uses JNI and it
seems to work (at least for its author, haven't tried myself).
Does anybody have an idea what's going on? I suspect I'm just doing
*something* wrong, but I have no idea what, and no targetted way (like
error messages) to find out.
Source attached. Hints appreciated. Thanks!
Ben
/**
* DVB card access on the OS level (system function ioctl()), to tune.
*
* This needs to happen in C/C++, because ioctl() is not accessible from Java.
* This implements the JNI library libzeipisdvbtune.so, a native C++ library
* accessible from Java. It implements the |native| methods from the
* org.bucksch.zeipis.recorder.DVBTunerNativeJNILinux Java class.
* We do as little as possible in C++.
*/
#include "DVBTunerNativeJNILinux.h"
#include
#include
#include
#include
#include
void throwEx(JNIEnv* env, const char* message)
{
jclass eClass = env->FindClass("org/bucksch/zeipis/recorder/CantUseTVCard");
if (eClass == 0) // can't find exception class; unexpected
return;
env->ThrowNew(eClass, message);
}
#define CHECK_RV(message) \
if (rv < 0) \
{ \
throwEx(env, message); \
close(frontendFD); \
return -1; \
}
/**
* Called with e.g. "/dev/dvb/adapter0/frontend0", false, 12187000, false, 2750 (=VOX in Germany)
*/
JNIEXPORT jint JNICALL Java_org_bucksch_zeipis_recorder_DVBTunerNativeJNILinux_tuneToNative
(JNIEnv* env, jobject self, jstring frontendFilename, jboolean dvbs2, jint frequency, jboolean polv, jint symbolrate)
{
// Open frontend device
const char* frontendFilenameC = env->GetStringUTFChars(frontendFilename, 0);
int frontendFD = open(frontendFilenameC, O_RDWR | O_NONBLOCK);
env->ReleaseStringUTFChars(frontendFilename, frontendFilenameC);
if (frontendFD < 0)
{
throwEx(env, "Can't get info from device");
return -1;
}
/* from szap
// Remove stale events
struct dvb_frontend_event ev;
while (ioctl(frontendFD, FE_GET_EVENT, &ev) >= 0)
;
*/
// Get info from device
int rv;
dvb_frontend_info info;
rv = ioctl(frontendFD, FE_GET_INFO, &info);
CHECK_RV("Can't get info from device");
#ifdef FE_GET_EXTENDED_INFO
dvb_fe_caps_extended info2;
if (dvbs2 && info.caps & FE_HAS_EXTENDED_INFO) // TODO
{
rv = ioctl(frontendFD, FE_GET_EXTENDED_INFO, &info2);
CHECK_RV("Can't get extended info from device");
if (info2.modulations & MOD_8PSK)
{
// set card to DVB-S2 mode
rv = ioctl(frontendFD, FE_SET_STANDARD, FE_DVB_S2)
CHECK_RV("Failed to set card to DVB-S2 mode");
// get new info
rv = ioctl(frontendFD, FE_GET_INFO, &info);
CHECK_RV("Can't get info from device after setting to DVB-S2 mode");
}
}
#endif
// Disecq
int sat_no = 0;
bool hiband = false;
// LNB config from szap
// Universal LNB
const int lnb_low_val = 9750;
const int lnb_high_val = 10600;
const int lnb_switch_val = 11700;
if (lnb_switch_val && lnb_high_val &&
frequency >= lnb_switch_val)
hiband = true;
if (hiband)
frequency = frequency - lnb_high_val;
else
{
if (frequency < lnb_low_val)
frequency = lnb_low_val - frequency;
else
frequency = frequency - lnb_low_val;
}
rv = ioctl(frontendFD, FE_SET_TONE, SEC_TONE_OFF);
CHECK_RV("Cound not turn disecq tone");
rv = ioctl(frontendFD, FE_SET_VOLTAGE, polv ? SEC_VOLTAGE_13 : SEC_VOLTAGE_18);
CHECK_RV("Could not set disecq voltage for polarity");
usleep(15 * 1000);
rv = ioctl(frontendFD, FE_SET_TONE, SEC_TONE_OFF);
CHECK_RV("Cound not turn off disecq tone");
usleep(15 * 1000);
struct dvb_diseqc_master_cmd disecq_cmd = {{0xe0, 0x10, 0x38, 0xf0, 0x00, 0x00}, 4};
disecq_cmd.msg[3] = 0xf0 | (((sat_no * 4) & 0x0f) | (hiband ? 1 : 0) | (polv ? 0 : 2));
rv = ioctl(frontendFD, FE_DISEQC_SEND_MASTER_CMD, &disecq_cmd);
CHECK_RV("Cound send disecq master command");
usleep(15 * 1000);
rv = ioctl(frontendFD, FE_DISEQC_SEND_BURST, (sat_no / 4) % 2 ? SEC_MINI_B : SEC_MINI_A);
CHECK_RV("Cound set satellite on disecq");
usleep(15 * 1000);
rv = ioctl(frontendFD, FE_SET_TONE, hiband ? SEC_TONE_ON : SEC_TONE_OFF);
CHECK_RV("Cound set disecq tone");
// TODO diseqc power on?
// TODO more diseqc?
// CAM start
// TODO
// Put tuning data into struct
#ifdef FE_GET_EXTENDED_INFO
#define dvb_fe_params dvb_frontend_parameters_new
#else
#define dvb_fe_params dvb_frontend_parameters
#endif
dvb_fe_params p;
// DVB-S
p.frequency = frequency;
p.u.qpsk.symbol_rate = symbolrate / 1000;
// TODO inversion
p.inversion = INVERSION_AUTO;
if (info.caps & FE_CAN_FEC
Re: [linux-dvb] Strage SkyStar HD modprobe
Hi, Manu Abraham schrieb: > Can someone verify whether the STB6100 has component values as in > this image ? http://abraham.manu.googlepages.com/snapshot9.png > in the problematic case ? > > If one is seeing ANALOG CARRIER from what i can see, this is due to a > large Noise Floor, the large noise floor can be caused from phase errors > between the I and Q inputs. This can happen as far as i can guess a > wrong setting in the pump setting. The pump settings are calculated >>from default reference values. If the design has been changed from > the default then there can be issues, based on the explained. > > (This is a guess, as currently i can't see clearly why there can be an > issue. Definitely i need more proper inputs, from the users) > > To verify this: Will require inputs from all STB0899 users what they are > seeing. As I'm not used to electronic stuff, I had someone else to look at such a card. Well, it was not a SkyStar HD, but a TT 3200, but the SkyStar HD's PCB shows the label 'TT 3200' too. Here are the results to your previous questions: http://www.vdr-portal.de/board/thread.php?postid=667017#post667017 Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] dvb-s encryption - how to capture a stream
Hi, I have a dvb-s card with a CAM and my subscription card. I get the message in syslog that shows the CAM is detected and initialized. However... I'm not sure how to get the encrypted video. Since it's a DVB-S card I thought szap would work, but although I "get" something, I can't view it, probably because it's the encrypted stream. What tool would I use? I have seem mention of ca_zap or something similar, but, I can't find the binary or source anywhere. Any pointers would be appreciated. Also would it be possible to decrypt an entire mux if I have a subscription for all the channels in the mux? -- Patrick Bulteel ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem with dvb_ttpci
On Wed, 7 Nov 2007, VDR User wrote: > With recent copies of fresh v4l I started getting the following error > upon trying to load drivers for my nexus-s: > > dvb_ttpci: Unknown symbol ttpci_eeprom_parse_mac > > After searching on google I found that this problem existed once > before and here is a patch that reflects the fix Did you remember to run depmod after installed new modules? The ttpci-eeprom module should be automatically loaded by modprobe. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Need help with Nova-S-Plus
Hi all, for a while, I haven't used my Hauppauge Nova-S-Plus which used to work fine. Now, it doesn't :-( Whenever I try to tune it, it fails: # scan -vvv /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2E scanning /usr/share/doc/dvb-utils/examples/scan/dvb-s/Astra-19.2E using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 12551500 V 2200 5 >>> tune to: 12551:v:0:22000 DiSEqC: switch pos 0, 13V, hiband (index 2) diseqc_send_msg:59: DiSEqC: e0 10 38 f1 00 00 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 WARNING: >>> tuning failed!!! >>> tune to: 12551:v:0:22000 (tuning failed) DiSEqC: switch pos 0, 13V, hiband (index 2) diseqc_send_msg:59: DiSEqC: e0 10 38 f1 00 00 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 >>> tuning status == 0x01 WARNING: >>> tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. The cable is fine and a satellite finder indicates a signal. The LNB is a quattro-switch-type and the other receivers (a digital twin and an analogue one) work fine as well. Operating system is Debian SID aka unstable, kernel 2.6.22 and 2.6.23. I also tried Knoppix 5.2. # cat /proc/version Linux version 2.6.22-3-k7 (Debian 2.6.22-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Mon Oct 22 22:51:54 UTC 2007 scan is from dvb-utils 1.1.1-3 # lspci ... 00:0f.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 00:0f.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) 00:0f.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 00:0f.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05) ... # dmesg ... cx2388x alsa driver version 0.0.6 loaded ACPI: PCI Interrupt :00:0f.1[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 CORE cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S [card=37,autodetected] TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe tveeprom 1-0050: Hauppauge model 92001, rev B1B1, serial# 247072 tveeprom 1-0050: MAC address is 00-0D-FE-03-C5-20 tveeprom 1-0050: tuner model is Conexant_CX24109 (idx 111, type 4) tveeprom 1-0050: TV standards ATSC/DVB Digital (eeprom 0x80) tveeprom 1-0050: audio processor is CX883 (idx 32) tveeprom 1-0050: decoder processor is CX883 (idx 22) tveeprom 1-0050: has no radio, has IR receiver, has no IR transmitter cx88[0]: hauppauge eeprom: model=92001 input: cx88 IR (Hauppauge Nova-S-Plus as /class/input/input3 cx88[0]/1: CX88x/0: ALSA support for cx2388x boards drivers/media/video/ov511.c: Sensor is an OV7620 cx2388x cx88-mpeg Driver Manager version 0.0.6 loaded cx88[0]/2: cx2388x 8802 Driver Manager ACPI: PCI Interrupt :00:0f.2[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 cx88[0]/2: found at :00:0f.2, rev: 5, irq: 11, latency: 32, mmio: 0xea00 cx2388x v4l2 driver version 0.0.6 loaded ACPI: PCI Interrupt :00:0f.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 cx88[0]/0: found at :00:0f.0, rev: 5, irq: 11, latency: 32, mmio: 0xe800 cx88[0]/0: registered device video0 [v4l2] cx88[0]/0: registered device vbi0 ACPI: PCI Interrupt :00:0b.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11 cx2388x dvb driver version 0.0.6 loaded cx8802_register_driver() ->registering driver type=dvb access=shared CORE cx88[0]: subsystem: 0070:9202, board: Hauppauge Nova-S-Plus DVB-S [card=37] cx88[0]/2: cx2388x based dvb card drivers/media/video/ov511.c: Device at usb-:00:11.2-2 registered to minor 1 usbcore: registered new interface driver ov511 drivers/media/video/ov511.c: v1.64 for Linux 2.5 : ov511 USB Camera Driver DVB: registering new adapter (cx88[0]). DVB: registering frontend 0 (Conexant CX24123/CX24109)... Any ideas? Thanks in advance. Chris. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 API vs. HVR4000: When?
Manu Abraham wrote: > frankio wrote: >> Manu Abraham wrote: >>> Francesco Schiavarelli wrote: >>> Johannes Stezenbach wrote: > On Sat, Nov 03, 2007, Manu Abraham wrote: > >> If you see H.2 and H.3, the difference is between CCM and VCM >> (Note: that both are cases of multiple "TS's") >> >> H.2 (CCM) is applicable for DVB-T muxes. Here there is a HP/LP stream >> selection in some fashion combined with the merger/slicer where >> stream id is used. > What makes you think there is HP/LP involved? All H.2 says > is that two DVB-T streams are transmitted using one > DVB-S2 transponder to a DVB-T transmitter. The DVB-T transmitter > could then transmit them on two different frequencies in > non-hierarchical mode. > > (Indeed H.2 says "two DTT MUXes at 24 Mbit/s each" indicating > they are not hierarchical because you can't get that > bitrate in DVB-T hierarchical mode. But even if it were DVB-T > hierarchical mode it has nothing to do with DVB-S2 backwards > compatible mode hierarchical modulation.) > > I agree with you, Johannes. There is no evidence of hierarchical modulation, nevertheless the two streams I was looking at had the same channel protection that is no HP/LP, and I was told it was DVB-S2 CCM. When the transponder will be up again I'll be able to do more tests. >>> Yeah, looks more like that, will have a patch soon to do some tests >>> for it. >>> STM's comments confirm that. >>> >>> Manu >>> >>> >> Now the beam is up on 13.0E 11373 H 27500 8PSK 2/3 >> It is made up of 2 DTT muxes (no HP/LP) >> ISI1 16QAM 1/2 1/49.953 Mbps >> ISI2 64QAM 5/6 1/424.882 Mbps >> >> Unfortunately I don't know how long it will last, so let the tests >> begin! :-) >> I'll wait for the patch. >> > > In the meantime, can you please pull a copy of the multiproto tree > http://jusst.de/hg/multiproto/ > Just try whether you can acquire a lock. > and try to parse the S2 satellite delivery system descriptor ? > dvbsnoop, or even libucsi will be able to do this. > Was too fast about this one. :-( Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 API vs. HVR4000: When?
frankio wrote: > Manu Abraham wrote: >> Francesco Schiavarelli wrote: >> >>> Johannes Stezenbach wrote: >>> On Sat, Nov 03, 2007, Manu Abraham wrote: > If you see H.2 and H.3, the difference is between CCM and VCM > (Note: that both are cases of multiple "TS's") > > H.2 (CCM) is applicable for DVB-T muxes. Here there is a HP/LP stream > selection in some fashion combined with the merger/slicer where > stream id is used. What makes you think there is HP/LP involved? All H.2 says is that two DVB-T streams are transmitted using one DVB-S2 transponder to a DVB-T transmitter. The DVB-T transmitter could then transmit them on two different frequencies in non-hierarchical mode. (Indeed H.2 says "two DTT MUXes at 24 Mbit/s each" indicating they are not hierarchical because you can't get that bitrate in DVB-T hierarchical mode. But even if it were DVB-T hierarchical mode it has nothing to do with DVB-S2 backwards compatible mode hierarchical modulation.) >>> I agree with you, Johannes. >>> There is no evidence of hierarchical modulation, nevertheless the two >>> streams I was looking at had the same channel protection that is no >>> HP/LP, and I was told it was DVB-S2 CCM. >>> >>> When the transponder will be up again I'll be able to do more tests. >>> >> >> Yeah, looks more like that, will have a patch soon to do some tests >> for it. >> STM's comments confirm that. >> >> Manu >> >> > Now the beam is up on 13.0E 11373 H 27500 8PSK 2/3 > It is made up of 2 DTT muxes (no HP/LP) > ISI1 16QAM 1/2 1/49.953 Mbps > ISI2 64QAM 5/6 1/424.882 Mbps > > Unfortunately I don't know how long it will last, so let the tests > begin! :-) > I'll wait for the patch. > In the meantime, can you please pull a copy of the multiproto tree http://jusst.de/hg/multiproto/ and try to parse the S2 satellite delivery system descriptor ? dvbsnoop, or even libucsi will be able to do this. > thanks, > Francesco > > Regards, Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S2 API vs. HVR4000: When?
Manu Abraham wrote: > Francesco Schiavarelli wrote: > >> Johannes Stezenbach wrote: >> >>> On Sat, Nov 03, 2007, Manu Abraham wrote: >>> If you see H.2 and H.3, the difference is between CCM and VCM (Note: that both are cases of multiple "TS's") H.2 (CCM) is applicable for DVB-T muxes. Here there is a HP/LP stream selection in some fashion combined with the merger/slicer where stream id is used. >>> What makes you think there is HP/LP involved? All H.2 says >>> is that two DVB-T streams are transmitted using one >>> DVB-S2 transponder to a DVB-T transmitter. The DVB-T transmitter >>> could then transmit them on two different frequencies in >>> non-hierarchical mode. >>> >>> (Indeed H.2 says "two DTT MUXes at 24 Mbit/s each" indicating >>> they are not hierarchical because you can't get that >>> bitrate in DVB-T hierarchical mode. But even if it were DVB-T >>> hierarchical mode it has nothing to do with DVB-S2 backwards >>> compatible mode hierarchical modulation.) >>> >>> >> I agree with you, Johannes. >> There is no evidence of hierarchical modulation, nevertheless the two >> streams I was looking at had the same channel protection that is no >> HP/LP, and I was told it was DVB-S2 CCM. >> >> When the transponder will be up again I'll be able to do more tests. >> > > Yeah, looks more like that, will have a patch soon to do some tests for it. > STM's comments confirm that. > > Manu > > Now the beam is up on 13.0E 11373 H 27500 8PSK 2/3 It is made up of 2 DTT muxes (no HP/LP) ISI1 16QAM 1/2 1/49.953 Mbps ISI2 64QAM 5/6 1/424.882 Mbps Unfortunately I don't know how long it will last, so let the tests begin! :-) I'll wait for the patch. thanks, Francesco ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] A-link DTU no tuning
> heis, > Can you say what are used modules or device usb-id? Demodulator seems to > be zl10353, but what are tuner and usb-bridge (probably tuner qt1010? > and usb-bridge gl861 or m9206?). Terve! The drivers involved are: usb-bridge gl861 Tuner: qt1010 Best Dag ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] A-link DTU no tuning
heis, Can you say what are used modules or device usb-id? Demodulator seems to be zl10353, but what are tuner and usb-bridge (probably tuner qt1010? and usb-bridge gl861 or m9206?). regards Antti Dag Nygren wrote: > Still more info on this issue: > > Downloaded and compiled the newest CVS (Mercurial). > The driver is built in a different way, but it still doesn't work > with this stick. > Adding the "magical" : > zl10353_single_write(fe, 0x5A, 0x0c); > > after zl10353_single_write(fe, 0x6D, 0x7E); > in zl10353_set_parameters() > once again makes it tune, except from the one Mux reported > earlier. It also seem to need an extra -5 in the scandvb command > to have enough time for the filtering. > > Here is a scandvb session log: > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] A-link DTU no tuning
Still more info on this issue: Downloaded and compiled the newest CVS (Mercurial). The driver is built in a different way, but it still doesn't work with this stick. Adding the "magical" : zl10353_single_write(fe, 0x5A, 0x0c); after zl10353_single_write(fe, 0x6D, 0x7E); in zl10353_set_parameters() once again makes it tune, except from the one Mux reported earlier. It also seem to need an extra -5 in the scandvb command to have enough time for the filtering. Here is a scandvb session log: % scandvb -5 -a 1 /home/dag/fi-Espoo scanning /home/dag/fi-Espoo using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' initial transponder 56200 0 2 9 3 1 2 0 initial transponder 65800 0 2 9 3 1 2 0 initial transponder 67400 0 2 9 3 1 2 0 initial transponder 73000 0 2 9 3 1 2 0 >>> tune to: 56200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:T RANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x 0x0011: pmt_pid 0x0100 YLE -- YLE TV1 (running) 0x 0x0021: pmt_pid 0x0101 YLE -- YLE TV2 (running) 0x 0x0051: pmt_pid 0x0103 YLE -- YLE FST5 (running) 0x 0x0081: pmt_pid 0x0104 YLE -- YLE Extra (running) 0x 0x0091: pmt_pid 0x0102 YLE -- YLE Teema (running) 0x 0x0d13: pmt_pid 0x010e Digita Oy -- Ohjelmistop?vitykset (running) 0x 0x: pmt_pid 0x0105 YLE -- YLE PEILI (running) 0x 0x1131: pmt_pid 0x0107 YLE -- YLEN KLASSINEN (running) 0x 0x1141: pmt_pid 0x0108 YLE -- YLE FSR+ (running) 0x 0x1151: pmt_pid 0x0109 YLE -- YLEMONDO (running) 0x 0x1181: pmt_pid 0x010a YLE -- YLE X3M (running) Network Name 'Digita Finland' >>> tune to: 65800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TR ANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 65800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TR ANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! >>> tune to: 67400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TR ANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x3001 0x01c1: pmt_pid 0x010b CANAL+ -- CANAL+ SPORT 1 (running, scrambled) 0x3001 0x01d1: pmt_pid 0x010e CANAL+ -- CANAL+ SPORT 2 (running, scrambled) 0x3001 0x01e1: pmt_pid 0x0111 CANAL+ -- Canal69 (running, scrambled) 0x3001 0x0331: pmt_pid 0x0100 Etel?Pohjanmaan viestint?Oy -- Iskelm?V Harju & P?tinen (running) 0x3001 0x0341: pmt_pid 0x0110 SBS Finland -- ISKELM?(running) 0x3001 0x0441: pmt_pid 0x010f Fiamax Oy -- klubi.tv (running) 0x3001 0x0451: pmt_pid 0x010c Fiamax Oy -- DIGIVIIHDE (running) 0x3001 0x0071: pmt_pid 0x0104 Suomen Urheilutelevisio Oy -- Urheilukanava (running) 0x3001 0x00a1: pmt_pid 0x0103 SBS -- The Voice (running) 0x3001 0x00c1: pmt_pid 0x010d Suomen Urheilutelevisio OY -- URHEILU+KANAVA (running) 0x3001 0x0143: pmt_pid 0x Turun Kaapelitelevisio Oy -- Turku TV (running) 0x3001 0x0191: pmt_pid 0x0105 CANAL+ -- Disney Channel (running, scrambled) 0x3001 0x01a1: pmt_pid 0x010a CANAL+ -- CANAL+ FIRST (running, scrambled) 0x3001 0x01b1: pmt_pid 0x0109 CANAL+ -- CANAL+ HITS (running, scrambled) WARNING: filter timeout pid 0x0010 >>> tune to: 73000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TR ANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE 0x5001 0x00e1: pmt_pid 0x0100 MTV OY -- MTV3 Fakta (running, scrambled) 0x5001 0x0111: pmt_pid 0x0101 Discovery Communications Europe -- Discovery (running, scrambled) 0x5001 0x0121: pmt_pid 0x0102 Eurosport SA -- Eurosport (running, scrambled) 0x5001 0x0131: pmt_pid 0x0103 MTV Networks Europe -- MTV Music Television (running, scrambled) 0x5001 0x0151: pmt_pid 0x0104 Nickelodeon International Ltd. -- Nickelodeon (running, scrambled) 0x5001 0x0161: pmt_pid 0x0105 YLE -- SVT Europa (running, scrambled) 0x5001 0x0171: pmt_pid 0x0107 MTV OY -- Big Brother 12/7 (running, scrambled) 0x5001 0x0181: pmt_pid 0x0106 SW Television Oy -- KinoTV (running, scrambled) Network Name 'Digita Finland' dumping lists (33 services) % Best Dag ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Record endlessly, split based on EPG, maybe transcoding
Hi, I have the following scenario. I'm using a Skystar 2 DVB-S card on Debian. I want to record one station endlessly/forever. I need a script that records all of time, AND splits files based on EPG (just don't want to have one huge file). I hope you understand what I mean. I want files like: channel1_11-07-07_0-00_title-of-show1 channel1_11-07-07_2-00_title-of-show2 if there is a show from 0:00 to 2:00 and from 2:00 on. can you tell me how to do this best? i just want the files. no vdr etc. it's just a headless server in a dark corner that should make an archive of my favorite station. because of the large file sizes it would also be advisable to recode movies. i'm thinking about making width and height half of the original (then i also dont have to care about deinterlacing). can this be done without much processing with mpeg-data? or do i have to re-encode to xvid or h264? how can this be done on the fly? record and transcode with ffmpeg? something else? i would be great if somebody of you could help me! cheers! ernesto ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem with dvb_ttpci
With recent copies of fresh v4l I started getting the following error upon trying to load drivers for my nexus-s: dvb_ttpci: Unknown symbol ttpci_eeprom_parse_mac After searching on google I found that this problem existed once before and here is a patch that reflects the fix i found: diff -ruN v4l-dvb-orig/linux/drivers/media/dvb/ttpci/Makefile v4l-dvb/linux/drivers/media/dvb/ttpci/Makefile --- v4l-dvb-orig/linux/drivers/media/dvb/ttpci/Makefile 2007-11-07 09:21:57.0 -0800 +++ v4l-dvb/linux/drivers/media/dvb/ttpci/Makefile 2007-11-07 09:22:35.0 -0800 @@ -3,7 +3,7 @@ # and the AV7110 DVB device driver # -dvb-ttpci-objs := av7110_hw.o av7110_v4l.o av7110_av.o av7110_ca.o av7110.o av7110_ipack.o av7110_ir.o +dvb-ttpci-objs := av7110_hw.o av7110_v4l.o av7110_av.o av7110_ca.o av7110.o av7110_ipack.o av7110_ir.o ttpci-eeprom.o obj-$(CONFIG_TTPCI_EEPROM) += ttpci-eeprom.o obj-$(CONFIG_DVB_BUDGET_CORE) += budget-core.o Please re-fix this problem and remember to -test- changes before applying them! Thanks fellas. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Is SkyStar2 Rev 2.7V supported?
Hello, I just was about to add a TechniSat SkyStar 2 Rev 2.7V to my VDR-Server which already has a Hauppauge Nexus 2.1 and a Nova-S. Unfortunately the driver doesn't seem to recoginze the SkyStar correctly and therefore no /dev/dvb/adapterX/... is created for this card. The drivers I use are from the "MASTER v4l-dvb development repository" of today (v4l-dvb-09fcd9084746). The card is recogized by the system: # lspci -v 05:01.0 Network controller: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card (rev 02) Subsystem: Techsan Electronics Co Ltd B2C2 FlexCopII DVB chip / Technisat SkyStar2 DVB card Flags: slow devsel, IRQ 17 Memory at febf (32-bit, non-prefetchable) [size=64K] I/O ports at ec00 [size=32] The following lines are probably the most interesting lines in syslog when calling "make insmod": Nov 7 15:50:48 core flexcop-pci: will use the HW PID filter. Nov 7 15:50:48 core flexcop-pci: card revision 2 Nov 7 15:50:48 core ACPI: PCI Interrupt :05:01.0[A] -> GSI 17 (level, low) -> IRQ 17 Nov 7 15:50:48 core DVB: registering new adapter (FlexCop Digital TV device) Nov 7 15:50:48 core b2c2-flexcop: MAC address = 00:d0:d7:13:b7:54 Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core i2c-adapter i2c-4: SMBus Quick command not supported, can't probe for chips Nov 7 15:50:48 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core mt352_read_register: readreg error (reg=127, ret==-121) Nov 7 15:50:49 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core nxt200x: nxt200x_readbytes: i2c read error (addr 0x0a, err == -121) Nov 7 15:50:49 core Unknown/Unsupported NXT chip: 00 00 00 00 00 Nov 7 15:50:49 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core lgdt330x: i2c_read_demod_bytes: addr 0x59 select 0x02 error (ret == -121) Nov 7 15:50:49 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core stv0297_readreg: readreg error (reg == 0x80, ret == -121) Nov 7 15:50:49 core b2c2-flexcop: i2c master_xfer failed Nov 7 15:50:49 core mt312_read: ret == -121 Nov 7 15:50:49 core b2c2-flexcop: no frontend driver found for this B2C2/FlexCop adapter Nov 7 15:50:49 core ACPI: PCI interrupt for device :05:01.0 disabled So my questions are: Is the SkyStar2 Rev 2.7V supposed to work with the current dvb-drivers? If yes: Could you please give me some hints on which drivers to load? greetings, Alex ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] hvr4000 patch for your multiproto tree
Hello, where is this patch to be found ? I would really like to be abble to finaly test DVB-S2 with VDR :-) -- Grégoire FAVRE http://gregoire.favre.googlepages.com http://www.gnupg.org http://picasaweb.google.com/Gregoire.Favre ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] VideoMate S350, need community advice
Greeting, Matthias! Tue, Nov 06, 2007 at 05:48:57PM +0100, zzam wrote: > > Well, last line saying that my card is hopeless under linux? Or I need dig > > more?! > > Best you first provide good pictures (both sides of the card) and a list of > contained ICs. (I suggest to add it to the linuxtv.org dvb-wiki). here is the image (identical with my): http://www.ixbt.com/monitor/images/compro-s350/compro-s350-front.jpg http://www.ixbt.com/monitor/images/compro-s350/compro-s350-back.jpg http://www.ixbt.com/monitor/images/compro-s350/chip-1.jpg http://www.ixbt.com/monitor/images/compro-s350/chip-2.jpg QPSK demodulator: ZL10313 CPU: SAA7130HL > Please alsa add lspci -vvnn output, and dmesg after using modprobe saa7134 > i2c_scan=1 lspci: 01:00.0 Multimedia controller [0480]: Philips Semiconductors SAA7130 Video Broadcast Decoder [1131:7130] (rev 01) Subsystem: Compro Technology, Inc. Unknown device [185b:c900] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- If I am right this card is based on similar chips as the AverTV DVB-S Pro > A700, that I try to add support for at the moment. > http://www.linuxtv.org/wiki/index.php/AVerMedia_AVerTV_DVB-S_Pro_(A700) i2c output seems differ, but I am not really hardware proffi in that... PS. Sorry for long puse. I am ready to help you. -- Anton P. Linevich ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] A-link DTU no tuning
Following up myself a bit: > Just bought myself such a USB DVB tuner and > it installs fine in Linus 2.6.23.1, but when trying to > use scandvb with it I only get "tuning failed!!!" > No errors in the logs though. It just doesn't tune. I found this mail: http://linuxtv.org/pipermail/linux-dvb/2007-January/015518.html and adding that extra zl10353_single_write(fe, 0x5A, 0x0C); does give me occasional (3/4) tuning on Mux A here in Espoo. Mux B will never tune though and the rest C and D? will work occasionally, about 1 out of 3 times. The tune file for the muxes is: # automatically generated from http://www.digitv.fi/sivu.asp?path=1;8224;9519 # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 56200 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 65800 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 67400 8MHz 2/3 NONE QAM64 8k 1/8 NONE T 73000 8MHz 2/3 NONE QAM64 8k 1/8 NONE Additional info: Adding a -5 to the scandvb command doesn't seem to give me any improvement even if the scan out put indicates a filter timeout.: % scandvb -5 -a 1 /home/dag/fi-Espoo scanning /home/dag/fi-Espoo using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' initial transponder 56200 0 2 9 3 1 2 0 initial transponder 65800 0 2 9 3 1 2 0 initial transponder 67400 0 2 9 3 1 2 0 initial transponder 73000 0 2 9 3 1 2 0 >>> tune to: 56200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:T RANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE Network Name 'Digita Finland' WARNING: filter timeout pid 0x0011 >>> tune to: 65800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TR ANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 65800:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TR ANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! Best Dag ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
