[linux-dvb] DVB-T initial tuning data file for lv-Riga
# Latvia - Riga (lv-Riga) # Generated by Raimonds Cicans # UTF8 encoding # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # DLRTC T 61000 8MHz 3/4 NONE QAM64 8k 1/8 NONE # Weak signal! VÄjÅ¡ signÄls! СлабÑй Ñигнал! # Baltkom TV T 65000 8MHz 3/4 3/4 QAM64 8k 1/16 NONE T 65800 8MHz 1/2 1/2 QPSK 8k 1/4 NONE T 66600 8MHz 3/4 3/4 QAM64 8k 1/16 NONE T 69000 8MHz 3/4 3/4 QAM64 8k 1/16 NONE T 77800 8MHz 3/4 3/4 QAM64 8k 1/16 NONE T 83400 8MHz 3/4 3/4 QAM64 8k 1/16 NONE # WARNING! # Some applications detect incorrect guard-interval. # UZMANĪBU! # Dažas programmas nekorekti nosaka guard-interval parametru. # ÐÐÐÐÐÐÐÐ! # ÐекоÑоÑÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð½ÐµÐºÐ¾ÑÑекÑно опÑеделÑÑÑ Ð¿Ð°ÑамеÑÑ guard-interval___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] reg: device drivers
Hi!! please help to find the device drivers for nova-s-plus card. thank u. Chat on a cool, new interface. No download required. Go to http://in.messenger.yahoo.com/webmessengerpromo.php ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] reg:device drivers
Hi!!! help me to find the device drivers for nova-s-plus card and the kernel version is 2.6.9. thank you. sudha Now you can chat without downloading messenger. Go to http://in.messenger.yahoo.com/webmessengerpromo.php ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Some tests on Avermedia A700
2008/2/17, Matthias Schwarzott [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: On Mittwoch, 13. Februar 2008, Eduard Huguet wrote: OK, I don't know exactly what you mean, but I'll try to measure the output voltage of the input connector. I think you mean this, don't you? BTW, ¿where is the set_voltage app? I have media-tv/linuxtv-dvb-apps package installed and there is nothing with that name... Another thing you can try is: Boot windows and look at the GPIO values. (See v4l wiki for how to do this using regspy). Use my latest diff, and try loading saa7134 with use_frontend=1 to use the alternative zl10313 driver. Regards Matthias -- Matthias Schwarzott (zzam) Hi, I've tried regspy (and regmon from sysinternals), but I really haven't found anything relevant. ¿What exactly should I look for? The V4L wiki is not very clear about it... Anyway, I also tried the use_frontend=1 option for saa7134-dvb and I got more or less the same results: $ dvbscan /usr/share/dvb/dvb-s/Astra-19.2E scanning /usr/share/dvb/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 DVB-S IF freq is 1951500 WARNING: tuning failed!!! tune to: 12551:v:0:22000 (tuning failed) DVB-S IF freq is 1951500 WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. The only difference with this frontend is that in Kaffeine I'm getting now a 0% signal level and a 99% SNR level. No idea why... BTW, I've checked again the dmesg output of modprobe saa7134 after a cold boot (full power cycle: powering off, unplugged power cord and pressed power button to ensure the capacitors are emptied, so there is absolutely no remanent voltage in the motherboard...), and this is what I get: [ 116.429358] saa7130/34: v4l2 driver version 0.2.14 loaded [ 116.431261] ACPI: PCI Interrupt :00:09.0[A] - GSI 17 (level, low) - IRQ 23 [ 116.431369] saa7133[0]: found at :00:09.0, rev: 209, irq: 23, latency: 64, mmio: 0xf7ffa800 [ 116.431435] saa7133[0]: subsystem: 1461:a7a1, board: Avermedia DVB-S Pro A700 [card=133,autodetected] [ 116.431519] saa7133[0]: board init: gpio is *202f600* [ 116.696295] saa7133[0]: i2c eeprom 00: 61 14 a1 a7 ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696321] saa7133[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696358] saa7133[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696372] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696386] saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696400] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696415] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696429] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696443] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696456] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696469] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696482] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696498] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696513] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.696535] saa7133[0]: i2c eeprom e0: *00 01 81 af ea b5* ff ff ff ff ff ff ff ff ff ff [ 116.696557] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 116.700280] saa7133[0]: i2c scan: found device @ 0x1c [???] [ 116.713245] saa7133[0]: i2c scan: found device @ 0xa0 [eeprom] [ 116.723550] saa7133[0]: registered device video0 [v4l2] [ 116.725685] saa7133[0]: registered device vbi0 [ 117.256803] demodulator: zl10313: Demodulator attached @ i2c address 0x0e [ 117.284726] zl1003x: zl1003x: Power-On-Reset bit enabled - may need to reinitialize tuner [ 117.284743] zl1003x: zl10036_init_regs [ 117.302667] zl1003x_attach: tuner initialization (Zarlink ZL10036 addr=0x60) ok [ 117.302687] DVB: registering new adapter (saa7133[0]) [ 117.302719] DVB: registering frontend 0 (Zarlink ZL10313 DVB-S)... [ 117.335612] zl1003x: zl1003x_sleep As you can see, the initial gpio value is different from what is listed in the wiki for my card (2f200). Also the contents of the eeprom are also different, and surprisingly matches the ones listed for the hybrid version. I suppose that this is mistake in the wiki entry, as I can assure you that my card is the standard DVB-S Pro... Best regards, Eduard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/16/2008 01:20 AM, P. van Gaans wrote: On 02/13/2008 09:21 PM, P. van Gaans wrote: On 02/13/2008 03:01 PM, Doru Marin wrote: Hi, Can you explain how you select those 4 positions ? DiSEqC commands or tone/voltage changes ? Also can you determine the input type of those positions (Hi/Low, H/V, etc) ? A scenario to see when and why that happens, would be more useful. P. van Gaans wrote: Hi, I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine 0.8.3). It works mostly fine, but there's a strange problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only switch without trouble to position 1 and 2. If I tune directly to position 3 it won't lock. However, if I first tune to a channel on position 1 or 2 and try a channel on position 3 after that, it will work. Position 4 however is completely unreachable. On a standalone receiver, there's no trouble with the same cable. Now Spaun is a really expensive and respected brand. So their switches possibly work in a different way, because a cheap Maximum 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 all work perfectly. I also did some dry testing indoors and it looks like a 7 euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU 41-02 probably won't. I'm guessing this could be solved in stv0299.c but I'm not much of an expert. I took a look at the code but I'm not really sure what to do. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The scan application has the same issues. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Nobody any ideas? If not, does anybody have some idea what the difference between position 1+2, pos 3 and pos 4 could be? I was thinking 1 and 2 might be working because of toneburst, but I don't think Kaffeine uses such a signal and that doesn't explain why pos 3 works if first tuning to 1 or 2 and 4 doesn't work at all. I've figured out a bit more. If I tune directly to postion 3, I get pos 1. Whenever I tune to pos 4, I get pos 2. I'll also ask people from Kaffeine as I'm not sure if the problem is in the application, driver or somewhere else. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] support for SkyStar 2.8A?
Hi, I asked this question a week ago. I bought a SkyStar2 rev. 2.8A card. I found this card is not supported by Linux. I tried to find rev 2.6D card, but everybody says technisat stopped producing it. Is there anybody else who works on support for this card? jikman ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
P. van Gaans wrote: On 02/16/2008 01:20 AM, P. van Gaans wrote: On 02/13/2008 09:21 PM, P. van Gaans wrote: On 02/13/2008 03:01 PM, Doru Marin wrote: Hi, Can you explain how you select those 4 positions ? DiSEqC commands or tone/voltage changes ? Also can you determine the input type of those positions (Hi/Low, H/V, etc) ? A scenario to see when and why that happens, would be more useful. P. van Gaans wrote: Hi, I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine 0.8.3). It works mostly fine, but there's a strange problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only switch without trouble to position 1 and 2. If I tune directly to position 3 it won't lock. However, if I first tune to a channel on position 1 or 2 and try a channel on position 3 after that, it will work. Position 4 however is completely unreachable. On a standalone receiver, there's no trouble with the same cable. Now Spaun is a really expensive and respected brand. So their switches possibly work in a different way, because a cheap Maximum 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 all work perfectly. I also did some dry testing indoors and it looks like a 7 euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU 41-02 probably won't. I'm guessing this could be solved in stv0299.c but I'm not much of an expert. I took a look at the code but I'm not really sure what to do. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The scan application has the same issues. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Nobody any ideas? If not, does anybody have some idea what the difference between position 1+2, pos 3 and pos 4 could be? I was thinking 1 and 2 might be working because of toneburst, but I don't think Kaffeine uses such a signal and that doesn't explain why pos 3 works if first tuning to 1 or 2 and 4 doesn't work at all. I've figured out a bit more. If I tune directly to postion 3, I get pos 1. Whenever I tune to pos 4, I get pos 2. I'll also ask people from Kaffeine as I'm not sure if the problem is in the application, driver or somewhere else. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, Strange scenario. You're not saying anything about input types and the switch type. Are you sure that are properly connected ? How the switch inputs are marked and from where you got the input signals ? Please elaborate, if you want a proper answer. I suggest to play with 'scandvb' from dvb-apps package instead of Kaffeine. Look into scanning results if the scanned channels match with what you wished to have on those positions. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Error compiling multiproto
Hi, After a clean install, I try to compile multiproto. But, after the make, I have this error : In file included from /opt/dvb/multiproto/v4l/em28xx-audio.c:39: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) /opt/dvb/multiproto/v4l/em28xx-audio.c:58: error: array index in initializer not of integer type /opt/dvb/multiproto/v4l/em28xx-audio.c:58: error: (near initialization for 'index') make[3]: *** [/opt/dvb/multiproto/v4l/em28xx-audio.o] Error 1 make[2]: *** [_module_/opt/dvb/multiproto/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-1-amd64' make[1]: *** [default] Erreur 2 make[1]: quittant le répertoire « /opt/dvb/multiproto/v4l » make: *** [all] Erreur 2 Google is not very helpful, so, if you have any idea ? Thank you very much. David. signature.asc Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/18/2008 02:04 PM, Doru Marin wrote: P. van Gaans wrote: On 02/16/2008 01:20 AM, P. van Gaans wrote: On 02/13/2008 09:21 PM, P. van Gaans wrote: On 02/13/2008 03:01 PM, Doru Marin wrote: Hi, Can you explain how you select those 4 positions ? DiSEqC commands or tone/voltage changes ? Also can you determine the input type of those positions (Hi/Low, H/V, etc) ? A scenario to see when and why that happens, would be more useful. P. van Gaans wrote: Hi, I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine 0.8.3). It works mostly fine, but there's a strange problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only switch without trouble to position 1 and 2. If I tune directly to position 3 it won't lock. However, if I first tune to a channel on position 1 or 2 and try a channel on position 3 after that, it will work. Position 4 however is completely unreachable. On a standalone receiver, there's no trouble with the same cable. Now Spaun is a really expensive and respected brand. So their switches possibly work in a different way, because a cheap Maximum 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 all work perfectly. I also did some dry testing indoors and it looks like a 7 euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU 41-02 probably won't. I'm guessing this could be solved in stv0299.c but I'm not much of an expert. I took a look at the code but I'm not really sure what to do. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The scan application has the same issues. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Nobody any ideas? If not, does anybody have some idea what the difference between position 1+2, pos 3 and pos 4 could be? I was thinking 1 and 2 might be working because of toneburst, but I don't think Kaffeine uses such a signal and that doesn't explain why pos 3 works if first tuning to 1 or 2 and 4 doesn't work at all. I've figured out a bit more. If I tune directly to postion 3, I get pos 1. Whenever I tune to pos 4, I get pos 2. I'll also ask people from Kaffeine as I'm not sure if the problem is in the application, driver or somewhere else. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb Hi, Strange scenario. You're not saying anything about input types and the switch type. Are you sure that are properly connected ? How the switch inputs are marked and from where you got the input signals ? Please elaborate, if you want a proper answer. I suggest to play with 'scandvb' from dvb-apps package instead of Kaffeine. Look into scanning results if the scanned channels match with what you wished to have on those positions. Hi, What do you mean with input type? Anyway, this is my config: Visiosat Bisat G3C for 19.2/28.2/23.5 + Triax 54cm for Hotbird 4 quad LNBs Spaun SAR 411F: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird Maximum 4/1: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird All works fine on a standalone so it is connected correctly. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] No results from multiproto TT3200
Hi all I am making slow progress and am still a good way off from having a working system What I have: [EMAIL PROTECTED] szap2]$ ./szap2 -c ../../channels.sat2 -t0 -n101 reading channels from file '../../channels.sat2' zapping to 101 'BBC NEWS 24;BSkyB': sat 0, frequency = 10773 MHz H, symbolrate 2200, vpid = 0x1518, apid = 0x1519 sid = 0x151b Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' -- Using 'STB0899 DVB-S' DVB-S do_tune: API version=3, delivery system = 0 do_tune: Frequency = 1023000, Srate = 2200 do_tune: Frequency = 1023000, Srate = 2200 status 00 | signal | snr 0004 | ber | unc fffe | status 1e | signal 0136 | snr 005f | ber | unc fffe | FE_HAS_LOCK status 1e | signal 0136 | snr 005f | ber | unc fffe | FE_HAS_LOCK status 1e | signal 0136 | snr 0060 | ber | unc fffe | FE_HAS_LOCK status 1e | signal 0136 | snr 005e | ber | unc fffe | FE_HAS_LOCK status 1e | signal 0136 | snr 005e | ber | unc fffe | FE_HAS_LOCK If I do cat /dev/dvb/adapter0/dv0 test.ts Then it remains empty Also the channel is locked but displaying very poor signal/snr Any help will be much appreciated Regards Mike Curtis ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Error compiling multiproto
Hi, On Mon, Feb 18, 2008 at 01:50:27PM +0100, David BERCOT wrote: Hi, After a clean install, I try to compile multiproto. But, after the make, I have this error : In file included from /opt/dvb/multiproto/v4l/em28xx-audio.c:39: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) /opt/dvb/multiproto/v4l/em28xx-audio.c:58: error: array index in initializer not of integer type /opt/dvb/multiproto/v4l/em28xx-audio.c:58: error: (near initialization for 'index') make[3]: *** [/opt/dvb/multiproto/v4l/em28xx-audio.o] Error 1 make[2]: *** [_module_/opt/dvb/multiproto/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-1-amd64' make[1]: *** [default] Erreur 2 make[1]: quittant le répertoire « /opt/dvb/multiproto/v4l » make: *** [all] Erreur 2 You have to apply this patch to be able to compile multiproto under a 2.6.24 kernel: http://linuxtv.org/hg/v4l-dvb/rev/b0815101889d Patch download link: http://linuxtv.org/hg/v4l-dvb/raw-diff/b0815101889d/v4l/compat.h Regards, Artem -- Artem Makhutov Unterort Str. 36 D-65760 Eschborn ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Error compiling multiproto
Le Mon, 18 Feb 2008 15:21:16 +0100, Artem Makhutov [EMAIL PROTECTED] a écrit : Hi, On Mon, Feb 18, 2008 at 01:50:27PM +0100, David BERCOT wrote: Hi, After a clean install, I try to compile multiproto. But, after the make, I have this error : In file included from /opt/dvb/multiproto/v4l/em28xx-audio.c:39: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) /opt/dvb/multiproto/v4l/em28xx-audio.c:58: error: array index in initializer not of integer type /opt/dvb/multiproto/v4l/em28xx-audio.c:58: error: (near initialization for 'index') make[3]: *** [/opt/dvb/multiproto/v4l/em28xx-audio.o] Error 1 make[2]: *** [_module_/opt/dvb/multiproto/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-1-amd64' make[1]: *** [default] Erreur 2 make[1]: quittant le répertoire « /opt/dvb/multiproto/v4l » make: *** [all] Erreur 2 You have to apply this patch to be able to compile multiproto under a 2.6.24 kernel: http://linuxtv.org/hg/v4l-dvb/rev/b0815101889d Patch download link: http://linuxtv.org/hg/v4l-dvb/raw-diff/b0815101889d/v4l/compat.h Regards, Artem OK. Simple ;-) I have not seen this information :-( Thank you very much. David. signature.asc Description: PGP signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
moikka I have also this device (express card). I haven't looked inside yet, but I think there is DibCOM STK7700D (in my understanding dual demod chip) and only *one* MT2266 tuner. I tried various GPIO settings but no luck yet. GPIO6 is for MT2266. GPIO9 and GPIO10 are for frontend. Looks like tuner goes to correct frequency because I got always PID-filter timeouts when tuning to correct freq. I will now try to take some usb-sniffs to see configuration used. Any help is welcome. regards Antti Albert Comerma wrote: Hi!, with Michel ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED]) who is a owner of this Yuan card we added the device to dib0700_devices, and we got it recognized without problems. The only problem is that no channel is detected on scan on kaffeine or other software... I post some dmesg. We don't know where it may be the problem... or how to detect it... usb 4-2: new high speed USB device using ehci_hcd and address 6 usb 4-2: new device found, idVendor=1164, idProduct=1edc usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2: Product: STK7700D usb 4-2: Manufacturer: YUANRD usb 4-2: SerialNumber: 01 usb 4-2: configuration #1 chosen from 1 choice dvb-usb: found a 'Yuan EC372S' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Yuan EC372S' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) dvb-usb: no frontend was attached by 'Yuan EC372S' dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input10 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Yuan EC372S successfully initialized and connected. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] dvico dual digital 4 new revision 2.0
just bought a new dvico dd4 card i has a revision 2.0 stamped on it it is not picked up by mythtv in the usb driver id the card is ID 0fe9:db78 DVICO ID 0fe9:db78 DVICO mine apperars as the same id exept on the ned not 78 so i changed the id to 98 linux picked it up as a dvico dd4 dvb card with two tuners now mythtv finds the card but no frontend i think they have changed that as well dmesg | grep dvb-usb [ 45.568438] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. [ 45.568759] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 45.676871] dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual Digital 4' [ 45.677733] dvb-usb: schedule remote query interval to 100 msecs. [ 45.677855] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. [ 45.677872] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. [ 45.678261] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 46.003003] dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual Digital 4' [ 46.003591] dvb-usb: schedule remote query interval to 100 msecs. [ 46.003900] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. lsusb -snip- Bus 002 Device 003: ID 0fe9:db98 DVICO Bus 002 Device 002: ID 0fe9:db98 DVICO lspci -snip- 05:06.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 62) 05:06.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 62) 05:06.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) 05:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 05:07.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 05:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 05:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
I'm trying to get a new Technisat Skystar HD2 working. It looks like it is a Twinhan VP-1041/Azurewave AD SP400 rebadge. The card hardware and satellite feed has been confirmed to work ok under Windows using Technisat's software. I am using the current multiproto DVB drivers, downloaded today. These were patched, built and installed successfully as described for the Azurewave AD SP400 in the linuxdvb wiki, but the card was not recognised on bootup even though it was allocated a DVB adaptor number. This appeared in dmesg: [ 57.359723] found a UNKNOWN PCI UNKNOWN device on (01:06.0), [ 57.359802] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 57.359858] memory: 0xe510, mmio: 0xc20fc000 [ 57.363015] MAC Address=[00:08:c9:e0:26:92] [ 57.363133] mantis_alloc_buffers (0): DMA=0x1b7a cpu=0x81001b7a size=65536 [ 57.363242] mantis_alloc_buffers (0): RISC=0x1ae24000 cpu=0x81001ae24000 size=1000 [ 57.363348] DVB: registering new adapter (Mantis dvb adapter) This is the output of lspci -vvn: 01:06.0 0480: 1822:4e35 (rev 01) Subsystem: 1ae4:0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at e510 (32-bit, prefetchable) [size=4K] This is the output of lsusb -vv: 01:06.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Unknown device 1ae4:0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at e510 (32-bit, prefetchable) [size=4K] Note that subsystem IDs 1ae4:0001 are different to those listed in the wiki for the Azurewave (1822:0031). I changed #define MANTIS_VP_1041_DVB_S2 in linux/drivers/media/dvb/ mantis/mantis_vp1041.h from 0x0031 to 0x0001, which changed the dmesg output on reboot to this: [ 59.546375] found a VP-1041 PCI DVB-S/DVB-S2 device on (01:06.0), [ 59.546456] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 59.546512] memory: 0xe510, mmio: 0xc20fc000 [ 59.549609] MAC Address=[00:08:c9:e0:26:92] [ 59.549719] mantis_alloc_buffers (0): DMA=0x1b7b cpu=0x81001b7b size=65536 [ 59.549827] mantis_alloc_buffers (0): RISC=0x1af43000 cpu=0x81001af43000 size=1000 [ 59.549933] DVB: registering new adapter (Mantis dvb adapter) [ 60.137583] stb0899_attach: Attaching STB0899 [ 60.137665] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2 frontend @0x68 [ 60.152161] stb6100_attach: Attaching STB6100 [ 60.168021] DVB: registering frontend 3 (STB0899 Multistandard)... So that change seemed to cause the card to be recognised. Then I tried the replacement scan and szap as suggested by the Azurewave wiki, but the card will not tune. So it appears to be almost working, but I'm not sure what tests to try or changes to make to see if it will work.___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
Hey people, we already solved this problems. I submitted a patch a few days
ago, but I think it's not on the current sources. I send again the patch.
Basically it must use the same frontend description as asus cards.
Albert
2008/2/18, Antti Palosaari [EMAIL PROTECTED]:
moikka
I have also this device (express card). I haven't looked inside yet, but
I think there is DibCOM STK7700D (in my understanding dual demod chip)
and only *one* MT2266 tuner. I tried various GPIO settings but no luck
yet.
GPIO6 is for MT2266.
GPIO9 and GPIO10 are for frontend.
Looks like tuner goes to correct frequency because I got always
PID-filter timeouts when tuning to correct freq. I will now try to take
some usb-sniffs to see configuration used. Any help is welcome.
regards
Antti
Albert Comerma wrote:
Hi!, with Michel ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED]) who
is a owner of this Yuan card we added the device to dib0700_devices, and
we got it recognized without problems. The only problem is that no
channel is detected on scan on kaffeine or other software... I post some
dmesg. We don't know where it may be the problem... or how to detect
it...
usb 4-2: new high speed USB device using ehci_hcd and address 6
usb 4-2: new device found, idVendor=1164, idProduct=1edc
usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 4-2: Product: STK7700D
usb 4-2: Manufacturer: YUANRD
usb 4-2: SerialNumber: 01
usb 4-2: configuration #1 chosen from 1 choice
dvb-usb: found a 'Yuan EC372S' in cold state, will try to load a
firmware
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
dib0700: firmware started successfully.
dvb-usb: found a 'Yuan EC372S' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
DVB: registering new adapter (Yuan EC372S)
dvb-usb: no frontend was attached by 'Yuan EC372S'
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
DVB: registering new adapter (Yuan EC372S)
DVB: registering frontend 1 (DiBcom 7000PC)...
MT2266: successfully identified
input: IR-receiver inside an USB DVB receiver as /class/input/input10
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: Yuan EC372S successfully initialized and connected.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
--
http://palosaari.fi/
diff -crB v4l-dvb-7d8558f3fc66-orig/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c v4l-dvb-7d8558f3fc66/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c
*** v4l-dvb-7d8558f3fc66-orig/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-01-27 16:23:53.0 +0100
--- v4l-dvb-7d8558f3fc66/linux/drivers/media/dvb/dvb-usb/dib0700_devices.c 2008-01-27 16:34:20.0 +0100
***
*** 905,910
--- 905,911
{ USB_DEVICE(USB_VID_ASUS, USB_PID_ASUS_U3100) },
/* 25 */ { USB_DEVICE(USB_VID_HAUPPAUGE, USB_PID_HAUPPAUGE_NOVA_T_STICK_3) },
{ USB_DEVICE(USB_VID_HAUPPAUGE, USB_PID_HAUPPAUGE_MYTV_T) },
+ { USB_DEVICE(USB_VID_YUAN, USB_PID_YUAN_EC372S) },
{ 0 } /* Terminating entry */
};
MODULE_DEVICE_TABLE(usb, dib0700_usb_id_table);
***
*** 1069,1080
},
},
! .num_device_descs = 1,
.devices = {
{ ASUS My Cinema U3000 Mini DVBT Tuner,
{ dib0700_usb_id_table[23], NULL },
{ NULL },
},
}
}, { DIB0700_DEFAULT_DEVICE_PROPERTIES,
--- 1070,1085
},
},
! .num_device_descs = 2,
.devices = {
{ ASUS My Cinema U3000 Mini DVBT Tuner,
{ dib0700_usb_id_table[23], NULL },
{ NULL },
},
+ { Yuan EC372S,
+ { dib0700_usb_id_table[27], NULL },
+ { NULL },
+ }
}
}, { DIB0700_DEFAULT_DEVICE_PROPERTIES,
diff -crB v4l-dvb-7d8558f3fc66-orig/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h v4l-dvb-7d8558f3fc66/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h
*** v4l-dvb-7d8558f3fc66-orig/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-01-27 16:23:53.0 +0100
--- v4l-dvb-7d8558f3fc66/linux/drivers/media/dvb/dvb-usb/dvb-usb-ids.h 2008-01-27 16:27:20.0 +0100
***
*** 46,53
#define USB_VID_ULTIMA_ELECTRONIC 0x05d8
#define USB_VID_UNIWILL0x1584
#define USB_VID_WIDEVIEW 0x14aa
- /* dom : pour gigabyte u7000 */
#define USB_VID_GIGABYTE 0x1044
/* Product IDs */
--- 46,53
#define USB_VID_ULTIMA_ELECTRONIC 0x05d8
#define USB_VID_UNIWILL0x1584
#define USB_VID_WIDEVIEW 0x14aa
#define USB_VID_GIGABYTE 0x1044
+ #define USB_VID_YUAN0x1164
/* Product IDs */
***
*** 183,191
#define USB_PID_OPERA1_WARM0x3829
#define USB_PID_LIFEVIEW_TV_WALKER_TWIN_COLD 0x0514
#define USB_PID_LIFEVIEW_TV_WALKER_TWIN_WARM
Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
hy, the wiki is not up2date. Twinhan VP-1041 support is now in the mantis tree (inkl. multiproto) hg clone http://jusst.de/hg/mantis but for me, the old initialization parameters works much better. with the new ones i get only a destructed picture (unwatchable). gernot On Monday 18 February 2008 20:05:03 Tim Hewett wrote: I'm trying to get a new Technisat Skystar HD2 working. It looks like it is a Twinhan VP-1041/Azurewave AD SP400 rebadge. The card hardware and satellite feed has been confirmed to work ok under Windows using Technisat's software. I am using the current multiproto DVB drivers, downloaded today. These were patched, built and installed successfully as described for the Azurewave AD SP400 in the linuxdvb wiki, but the card was not recognised on bootup even though it was allocated a DVB adaptor number. This appeared in dmesg: [ 57.359723] found a UNKNOWN PCI UNKNOWN device on (01:06.0), [ 57.359802] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 57.359858] memory: 0xe510, mmio: 0xc20fc000 [ 57.363015] MAC Address=[00:08:c9:e0:26:92] [ 57.363133] mantis_alloc_buffers (0): DMA=0x1b7a cpu=0x81001b7a size=65536 [ 57.363242] mantis_alloc_buffers (0): RISC=0x1ae24000 cpu=0x81001ae24000 size=1000 [ 57.363348] DVB: registering new adapter (Mantis dvb adapter) This is the output of lspci -vvn: 01:06.0 0480: 1822:4e35 (rev 01) Subsystem: 1ae4:0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at e510 (32-bit, prefetchable) [size=4K] This is the output of lsusb -vv: 01:06.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01) Subsystem: Unknown device 1ae4:0001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min, 63750ns max) Interrupt: pin A routed to IRQ 16 Region 0: Memory at e510 (32-bit, prefetchable) [size=4K] Note that subsystem IDs 1ae4:0001 are different to those listed in the wiki for the Azurewave (1822:0031). I changed #define MANTIS_VP_1041_DVB_S2 in linux/drivers/media/dvb/ mantis/mantis_vp1041.h from 0x0031 to 0x0001, which changed the dmesg output on reboot to this: [ 59.546375] found a VP-1041 PCI DVB-S/DVB-S2 device on (01:06.0), [ 59.546456] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 59.546512] memory: 0xe510, mmio: 0xc20fc000 [ 59.549609] MAC Address=[00:08:c9:e0:26:92] [ 59.549719] mantis_alloc_buffers (0): DMA=0x1b7b cpu=0x81001b7b size=65536 [ 59.549827] mantis_alloc_buffers (0): RISC=0x1af43000 cpu=0x81001af43000 size=1000 [ 59.549933] DVB: registering new adapter (Mantis dvb adapter) [ 60.137583] stb0899_attach: Attaching STB0899 [ 60.137665] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2 frontend @0x68 [ 60.152161] stb6100_attach: Attaching STB6100 [ 60.168021] DVB: registering frontend 3 (STB0899 Multistandard)... So that change seemed to cause the card to be recognised. Then I tried the replacement scan and szap as suggested by the Azurewave wiki, but the card will not tune. So it appears to be almost working, but I'm not sure what tests to try or changes to make to see if it will work. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
moi It does not work for me. It says same PID-filter timeout as I have got earlier. I don't have amplified antenna now, but I can say that all other DVB-T sticks I have are working with this small antenna. It could be that sensitivity of this hardware is bad or there is something wrong with driver or firmware. Lets try to test it Windows to see if it is working or not. Logs attached. regards Antti Albert Comerma wrote: Hey people, we already solved this problems. I submitted a patch a few days ago, but I think it's not on the current sources. I send again the patch. Basically it must use the same frontend description as asus cards. Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: moikka I have also this device (express card). I haven't looked inside yet, but I think there is DibCOM STK7700D (in my understanding dual demod chip) and only *one* MT2266 tuner. I tried various GPIO settings but no luck yet. GPIO6 is for MT2266. GPIO9 and GPIO10 are for frontend. Looks like tuner goes to correct frequency because I got always PID-filter timeouts when tuning to correct freq. I will now try to take some usb-sniffs to see configuration used. Any help is welcome. regards Antti Albert Comerma wrote: Hi!, with Michel ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]) who is a owner of this Yuan card we added the device to dib0700_devices, and we got it recognized without problems. The only problem is that no channel is detected on scan on kaffeine or other software... I post some dmesg. We don't know where it may be the problem... or how to detect it... usb 4-2: new high speed USB device using ehci_hcd and address 6 usb 4-2: new device found, idVendor=1164, idProduct=1edc usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2: Product: STK7700D usb 4-2: Manufacturer: YUANRD usb 4-2: SerialNumber: 01 usb 4-2: configuration #1 chosen from 1 choice dvb-usb: found a 'Yuan EC372S' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Yuan EC372S' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) dvb-usb: no frontend was attached by 'Yuan EC372S' dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input10 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Yuan EC372S successfully initialized and connected. ___ linux-dvb mailing list linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/ Bus 001 Device 005: ID 1164:1edc YUAN High-Tech Development Co., Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1164 YUAN High-Tech Development Co., Ltd idProduct 0x1edc bcdDevice1.00 iManufacturer 1 YUANRD iProduct2 STK7700D iSerial 3 01 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 4 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
Uhm... that's strange, I don't have any of this cards to test, but other people reported that this solution was working. Could you post the dib0700_devices.c you're using to have a look? Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED]: moi It does not work for me. It says same PID-filter timeout as I have got earlier. I don't have amplified antenna now, but I can say that all other DVB-T sticks I have are working with this small antenna. It could be that sensitivity of this hardware is bad or there is something wrong with driver or firmware. Lets try to test it Windows to see if it is working or not. Logs attached. regards Antti Albert Comerma wrote: Hey people, we already solved this problems. I submitted a patch a few days ago, but I think it's not on the current sources. I send again the patch. Basically it must use the same frontend description as asus cards. Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: moikka I have also this device (express card). I haven't looked inside yet, but I think there is DibCOM STK7700D (in my understanding dual demod chip) and only *one* MT2266 tuner. I tried various GPIO settings but no luck yet. GPIO6 is for MT2266. GPIO9 and GPIO10 are for frontend. Looks like tuner goes to correct frequency because I got always PID-filter timeouts when tuning to correct freq. I will now try to take some usb-sniffs to see configuration used. Any help is welcome. regards Antti Albert Comerma wrote: Hi!, with Michel ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]) who is a owner of this Yuan card we added the device to dib0700_devices, and we got it recognized without problems. The only problem is that no channel is detected on scan on kaffeine or other software... I post some dmesg. We don't know where it may be the problem... or how to detect it... usb 4-2: new high speed USB device using ehci_hcd and address 6 usb 4-2: new device found, idVendor=1164, idProduct=1edc usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2: Product: STK7700D usb 4-2: Manufacturer: YUANRD usb 4-2: SerialNumber: 01 usb 4-2: configuration #1 chosen from 1 choice dvb-usb: found a 'Yuan EC372S' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Yuan EC372S' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) dvb-usb: no frontend was attached by 'Yuan EC372S' dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input10 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Yuan EC372S successfully initialized and connected. ___ linux-dvb mailing list linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/ Bus 001 Device 005: ID 1164:1edc YUAN High-Tech Development Co., Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x1164 YUAN High-Tech Development Co., Ltd idProduct 0x1edc bcdDevice1.00 iManufacturer 1 YUANRD iProduct2 STK7700D iSerial 3 01 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 46 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
latest v4l-master + patch you give. regards Antti Albert Comerma wrote: Uhm... that's strange, I don't have any of this cards to test, but other people reported that this solution was working. Could you post the dib0700_devices.c you're using to have a look? Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: moi It does not work for me. It says same PID-filter timeout as I have got earlier. I don't have amplified antenna now, but I can say that all other DVB-T sticks I have are working with this small antenna. It could be that sensitivity of this hardware is bad or there is something wrong with driver or firmware. Lets try to test it Windows to see if it is working or not. Logs attached. regards Antti Albert Comerma wrote: Hey people, we already solved this problems. I submitted a patch a few days ago, but I think it's not on the current sources. I send again the patch. Basically it must use the same frontend description as asus cards. Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: moikka I have also this device (express card). I haven't looked inside yet, but I think there is DibCOM STK7700D (in my understanding dual demod chip) and only *one* MT2266 tuner. I tried various GPIO settings but no luck yet. GPIO6 is for MT2266. GPIO9 and GPIO10 are for frontend. Looks like tuner goes to correct frequency because I got always PID-filter timeouts when tuning to correct freq. I will now try to take some usb-sniffs to see configuration used. Any help is welcome. regards Antti Albert Comerma wrote: Hi!, with Michel ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]) who is a owner of this Yuan card we added the device to dib0700_devices, and we got it recognized without problems. The only problem is that no channel is detected on scan on kaffeine or other software... I post some dmesg. We don't know where it may be the problem... or how to detect it... usb 4-2: new high speed USB device using ehci_hcd and address 6 usb 4-2: new device found, idVendor=1164, idProduct=1edc usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2: Product: STK7700D usb 4-2: Manufacturer: YUANRD usb 4-2: SerialNumber: 01 usb 4-2: configuration #1 chosen from 1 choice dvb-usb: found a 'Yuan EC372S' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Yuan EC372S' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) dvb-usb: no frontend was attached by 'Yuan EC372S' dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input10 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Yuan EC372S successfully initialized and connected. ___ linux-dvb mailing list linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/ ___ linux-dvb mailing list linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/ Bus 001 Device 005: ID 1164:1edc YUAN High-Tech Development Co., Ltd Device Descriptor: bLength18 bDescriptorType 1 bcdUSB
Re: [linux-dvb] Yuan EC372S (STK7700D based device)
It seems ok. Could you test a scan with kaffeine instead of looking for a specific location? And if you do so it reports signal strenght? By the way, what does it mean moi and moikka? Hello in finish? Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED]: latest v4l-master + patch you give. regards Antti Albert Comerma wrote: Uhm... that's strange, I don't have any of this cards to test, but other people reported that this solution was working. Could you post the dib0700_devices.c you're using to have a look? Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: moi It does not work for me. It says same PID-filter timeout as I have got earlier. I don't have amplified antenna now, but I can say that all other DVB-T sticks I have are working with this small antenna. It could be that sensitivity of this hardware is bad or there is something wrong with driver or firmware. Lets try to test it Windows to see if it is working or not. Logs attached. regards Antti Albert Comerma wrote: Hey people, we already solved this problems. I submitted a patch a few days ago, but I think it's not on the current sources. I send again the patch. Basically it must use the same frontend description as asus cards. Albert 2008/2/18, Antti Palosaari [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: moikka I have also this device (express card). I haven't looked inside yet, but I think there is DibCOM STK7700D (in my understanding dual demod chip) and only *one* MT2266 tuner. I tried various GPIO settings but no luck yet. GPIO6 is for MT2266. GPIO9 and GPIO10 are for frontend. Looks like tuner goes to correct frequency because I got always PID-filter timeouts when tuning to correct freq. I will now try to take some usb-sniffs to see configuration used. Any help is welcome. regards Antti Albert Comerma wrote: Hi!, with Michel ([EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]) who is a owner of this Yuan card we added the device to dib0700_devices, and we got it recognized without problems. The only problem is that no channel is detected on scan on kaffeine or other software... I post some dmesg. We don't know where it may be the problem... or how to detect it... usb 4-2: new high speed USB device using ehci_hcd and address 6 usb 4-2: new device found, idVendor=1164, idProduct=1edc usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2: Product: STK7700D usb 4-2: Manufacturer: YUANRD usb 4-2: SerialNumber: 01 usb 4-2: configuration #1 chosen from 1 choice dvb-usb: found a 'Yuan EC372S' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw' dib0700: firmware started successfully. dvb-usb: found a 'Yuan EC372S' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) dvb-usb: no frontend was attached by 'Yuan EC372S' dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Yuan EC372S) DVB: registering frontend 1 (DiBcom 7000PC)... MT2266: successfully identified input: IR-receiver inside an USB DVB receiver as /class/input/input10 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: Yuan EC372S successfully initialized and connected. ___ linux-dvb mailing list linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org mailto:linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb -- http://palosaari.fi/
[linux-dvb] any solution to the endianness issue for ppc machines with usb-skystar ?
After more than two years of waiting, i decided to retry the linux dvb driver in order to use a dvb-s technisat skystar-USB box in my 667mhz macintosh powerbook G4 running debian lenny kernel 2.6.22. I obtained the latest v4l-dvb source code from linuxTV : hg clone http://linuxtv.org/hg/v4l-dvb cd v4l-dvb make make install As usual all went fine. The flexcop modules loaded very well despite the fact that my usb dvb-box still remain unusable. A quick look to dmsg log show this : usb 1-1: new full speed USB device using ohci_hcd and address 2 usb 1-1: device descriptor read/64, error -62 usb 1-1: device descriptor read/64, error -62 usb 1-1: new full speed USB device using ohci_hcd and address 3 PM: Adding info for usb:1-1 PM: Adding info for No Bus:usbdev1.3_ep00 usb 1-1: configuration #1 chosen from 1 choice PM: Adding info for usb:1-1:1.0 PM: Adding info for No Bus:usbdev1.3_ep81 PM: Adding info for No Bus:usbdev1.3 b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded successfully PM: Removing info for No Bus:usbdev1.3_ep81 PM: Adding info for No Bus:usbdev1.3_ep81 flexcop_usb: running at FULL speed. b2c2-flexcop: unkown FlexCop Revision: 8. Please report the [EMAIL PROTECTED] technisat skystar-USB box DVB: registering new adapter (FlexCop Digital TV device) PM: Adding info for No Bus:dvb0.demux0 PM: Adding info for No Bus:dvb0.dvr0 PM: Adding info for No Bus:dvb0.net0 b2c2-flexcop: MAC address = 00:d0:d7:0c:b8:1c PM: Adding info for No Bus:i2c-9 b2c2-flexcop: found the stv0299 at i2c address: 0x68 DVB: registering frontend 0 (ST STV0299 DVB-S)... PM: Adding info for No Bus:dvb0.frontend0 b2c2-flexcop: initialization of 'Sky2PC/SkyStar 2 DVB-S' at the 'USB' bus controlled by a 'Unkown chip' complete flexcop_usb: submitting urb 0 failed with -90. PM: Removing info for No Bus:dvb0.frontend0 PM: Removing info for No Bus:i2c-9 PM: Removing info for No Bus:dvb0.net0 PM: Removing info for No Bus:dvb0.demux0 PM: Removing info for No Bus:dvb0.dvr0 b2c2_flexcop_usb: probe of 1-1:1.0 failed with error -90 usbcore: registered new interface driver b2c2_flexcop_usb More than two year ago patrick.boettcher from this forum explained me this is related to the endianness issue in ppc machines...apparently the problem remain unsolved and nobody has wrote a driver taking into account this particularity. So will they be in the future a serious attempt to improve the flexcop driver in that sense ? As far as i know, this endianness issue concern only the linux skystar usb part of the driver not the pci one. And because this a common driver for both hardware (pci usb skystar2) then solving the problem for one type of hardware could alter the usability of the other type. So a trade-off was made. I don't ask to rewrite the driver from scratch for the ppc community but i wonder if someone can write a patch to overcome the issue after applying it and recompiling the driver (surely not me i'm not a developper only a hobbyist and it's beyond my modest capacities) so we could watch tv on our beloved machines. waiting to hearing from you. Best regards. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
Gernot, I have now tried the mantis tree. It also needed the MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this card, but after doing that it was recognised: [ 56.586237] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 [ 56.586330] ACPI: PCI Interrupt :01:06.0[A] - Link [APC1] - GSI 16 (level, low) - IRQ 16 [ 56.586556] irq: 16, latency: 32 [ 56.586557] memory: 0xe510, mmio: 0xc20f8000 [ 56.586708] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (01:06.0), [ 56.586791] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 56.586847] memory: 0xe510, mmio: 0xc20f8000 [ 56.589867] MAC Address=[00:08:c9:e0:26:92] [ 56.589972] mantis_alloc_buffers (0): DMA=0x1aa1 cpu=0x81001aa1 size=65536 [ 56.590081] mantis_alloc_buffers (0): RISC=0x1b7f cpu=0x81001b7f size=1000 [ 56.590187] DVB: registering new adapter (Mantis dvb adapter) [ 57.106676] stb0899_write_regs [0xf1b6]: 02 [ 57.107730] stb0899_write_regs [0xf1c2]: 00 [ 57.108781] stb0899_write_regs [0xf1c3]: 00 [ 57.110884] _stb0899_read_reg: Reg=[0xf000], data=82 [ 57.110964] stb0899_get_dev_id: ID reg=[0x82] [ 57.111040] stb0899_get_dev_id: Device ID=[8], Release=[2] [ 57.117425] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf334], Data=[0x444d4431] [ 57.123732] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf33c], Data=[0x0001] [ 57.123735] stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1] [ 57.130121] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa2c], Data=[0x46454331] [ 57.136428] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa34], Data=[0x0001] [ 57.136430] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1] [ 57.136509] stb0899_attach: Attaching STB0899 [ 57.136586] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2 frontend @0x68 [ 57.136690] stb6100_attach: Attaching STB6100 [ 57.137118] DVB: registering frontend 1 (STB0899 Multistandard)... However it still doesn't tune. e.g.: [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l UNIVERSAL -t 0 -a 1 BBC1West reading channels from file '/root/.szap/channels.conf' zapping to 1 'BBC1West': sat 0, frequency = 10818 MHz V, symbolrate 2200, vpid = 0x0901, apid = 0x0904 sid = 0x0002 Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' -- Using 'STB0899 DVB-S' DVB-S do_tune: API version=3, delivery system = 0 do_tune: Frequency = 1068000, Srate = 2200 do_tune: Frequency = 1068000, Srate = 2200 Whereas this is the result when using an ordinary Skystar 2 card (which works fine): [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l UNIVERSAL -t 0 -a 0 BBC1West reading channels from file '/root/.szap/channels.conf' zapping to 1 'BBC1West': sat 0, frequency = 10818 MHz V, symbolrate 2200, vpid = 0x0901, apid = 0x0904 sid = 0x0002 Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' -- Using 'ST STV0299 DVB-S' DVB-S do_tune: API version=3, delivery system = 0 do_tune: Frequency = 1068000, Srate = 2200 do_tune: Frequency = 1068000, Srate = 2200 couldn't find pmt-pid for sid 0002 status 1f | signal cac8 | snr cb6d | ber 61d0 | unc | FE_HAS_LOCK status 1f | signal c9f0 | snr d15e | ber | unc | FE_HAS_LOCK status 1f | signal ca1d | snr d176 | ber | unc | FE_HAS_LOCK Using szap on the Skystar HD2 caused lots of logs to dmesg: [ 97.691029] stb0899_search: set DVB-S params [ 97.691112] stb0899_search: delivery system=1 [ 97.691188] stb0899_search: Frequency=1068000, Srate=2200 [ 97.691269] stb0899_search: Parameters IN RANGE [ 97.692611] _stb0899_read_reg: Reg=[0xf1c2], data=20 [ 97.694085] _stb0899_read_reg: Reg=[0xf1c3], data=00 [ 97.694166] stb0899_set_delsys: Delivery System -- DVB-S [ 97.695848] _stb0899_read_reg: Reg=[0xf533], data=01 [ 97.695929] stb0899_write_regs [0xf533]: 09 [ 97.697420] stb0899_write_regs [0xf548]: b1 [ 97.698913] stb0899_write_regs [0xf549]: 40 [ 97.700410] stb0899_write_regs [0xf54a]: 42 [ 97.701778] stb0899_write_regs [0xf54b]: 12 [ 97.704225] _stb0899_read_reg: Reg=[0xff11], data=00 [ 97.704308] stb0899_write_regs [0xff11]: 80 [ 97.705797] stb0899_write_regs [0xf1c2]: 78 07 [ 97.707631] stb0899_set_mclk: state-config=882654a0 [ 97.707713] stb0899_set_mclk: mdiv=21 [ 97.707788] stb0899_write_regs [0xf1b3]: 15 [ 97.710338] _stb0899_read_reg: Reg=[0xf1b3], data=15 [ 97.710427] stb0899_get_mclk: div=21, mclk=9900 [ 97.710505] stb0899_set_mclk: MasterCLOCK=9900 [ 97.710582] stb0899_search: DVB-S delivery system [ 97.712051] _stb0899_read_reg:
Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)
hy, have you tried some other channel on a diffrent multiplex? i have also troubles on 2 multiplexes, but i believe that's trough my bad signal strength (it's the same on windows). otherwise there have to be some initialization registers configured differently. manu is the only guy, how knows about that and can help you. gernot On Tuesday 19 February 2008 00:51:49 Tim Hewett wrote: Gernot, I have now tried the mantis tree. It also needed the MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this card, but after doing that it was recognised: [ 56.586237] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16 [ 56.586330] ACPI: PCI Interrupt :01:06.0[A] - Link [APC1] - GSI 16 (level, low) - IRQ 16 [ 56.586556] irq: 16, latency: 32 [ 56.586557] memory: 0xe510, mmio: 0xc20f8000 [ 56.586708] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (01:06.0), [ 56.586791] Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32 [ 56.586847] memory: 0xe510, mmio: 0xc20f8000 [ 56.589867] MAC Address=[00:08:c9:e0:26:92] [ 56.589972] mantis_alloc_buffers (0): DMA=0x1aa1 cpu=0x81001aa1 size=65536 [ 56.590081] mantis_alloc_buffers (0): RISC=0x1b7f cpu=0x81001b7f size=1000 [ 56.590187] DVB: registering new adapter (Mantis dvb adapter) [ 57.106676] stb0899_write_regs [0xf1b6]: 02 [ 57.107730] stb0899_write_regs [0xf1c2]: 00 [ 57.108781] stb0899_write_regs [0xf1c3]: 00 [ 57.110884] _stb0899_read_reg: Reg=[0xf000], data=82 [ 57.110964] stb0899_get_dev_id: ID reg=[0x82] [ 57.111040] stb0899_get_dev_id: Device ID=[8], Release=[2] [ 57.117425] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf334], Data=[0x444d4431] [ 57.123732] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf33c], Data=[0x0001] [ 57.123735] stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1] [ 57.130121] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa2c], Data=[0x46454331] [ 57.136428] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa34], Data=[0x0001] [ 57.136430] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1] [ 57.136509] stb0899_attach: Attaching STB0899 [ 57.136586] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2 frontend @0x68 [ 57.136690] stb6100_attach: Attaching STB6100 [ 57.137118] DVB: registering frontend 1 (STB0899 Multistandard)... However it still doesn't tune. e.g.: [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l UNIVERSAL -t 0 -a 1 BBC1West reading channels from file '/root/.szap/channels.conf' zapping to 1 'BBC1West': sat 0, frequency = 10818 MHz V, symbolrate 2200, vpid = 0x0901, apid = 0x0904 sid = 0x0002 Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' -- Using 'STB0899 DVB-S' DVB-S do_tune: API version=3, delivery system = 0 do_tune: Frequency = 1068000, Srate = 2200 do_tune: Frequency = 1068000, Srate = 2200 Whereas this is the result when using an ordinary Skystar 2 card (which works fine): [EMAIL PROTECTED]:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l UNIVERSAL -t 0 -a 0 BBC1West reading channels from file '/root/.szap/channels.conf' zapping to 1 'BBC1West': sat 0, frequency = 10818 MHz V, symbolrate 2200, vpid = 0x0901, apid = 0x0904 sid = 0x0002 Querying info .. Delivery system=DVB-S using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' -- Using 'ST STV0299 DVB-S' DVB-S do_tune: API version=3, delivery system = 0 do_tune: Frequency = 1068000, Srate = 2200 do_tune: Frequency = 1068000, Srate = 2200 couldn't find pmt-pid for sid 0002 status 1f | signal cac8 | snr cb6d | ber 61d0 | unc | FE_HAS_LOCK status 1f | signal c9f0 | snr d15e | ber | unc | FE_HAS_LOCK status 1f | signal ca1d | snr d176 | ber | unc | FE_HAS_LOCK Using szap on the Skystar HD2 caused lots of logs to dmesg: [ 97.691029] stb0899_search: set DVB-S params [ 97.691112] stb0899_search: delivery system=1 [ 97.691188] stb0899_search: Frequency=1068000, Srate=2200 [ 97.691269] stb0899_search: Parameters IN RANGE [ 97.692611] _stb0899_read_reg: Reg=[0xf1c2], data=20 [ 97.694085] _stb0899_read_reg: Reg=[0xf1c3], data=00 [ 97.694166] stb0899_set_delsys: Delivery System -- DVB-S [ 97.695848] _stb0899_read_reg: Reg=[0xf533], data=01 [ 97.695929] stb0899_write_regs [0xf533]: 09 [ 97.697420] stb0899_write_regs [0xf548]: b1 [ 97.698913] stb0899_write_regs [0xf549]: 40 [ 97.700410] stb0899_write_regs [0xf54a]: 42 [ 97.701778] stb0899_write_regs [0xf54b]: 12 [ 97.704225] _stb0899_read_reg: Reg=[0xff11], data=00 [ 97.704308] stb0899_write_regs [0xff11]: 80 [ 97.705797]
[linux-dvb] dvico dual digital 4 new revision 2.0
just bought a new dvico dd4 card i has a revision 2.0 stamped on it it is not picked up by mythtv in the usb driver id the card is ID 0fe9:db78 DVICO ID 0fe9:db78 DVICO mine apperars as the same id exept on the ned not 78 so i changed the id to 98 linux picked it up as a dvico dd4 dvb card with two tuners now mythtv finds the card but no frontend i think they have changed that as well dmesg | grep dvb-usb [ 45.568438] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. [ 45.568759] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 45.676871] dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual Digital 4' [ 45.677733] dvb-usb: schedule remote query interval to 100 msecs. [ 45.677855] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. [ 45.677872] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. [ 45.678261] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 46.003003] dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual Digital 4' [ 46.003591] dvb-usb: schedule remote query interval to 100 msecs. [ 46.003900] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. lsusb -snip- Bus 002 Device 003: ID 0fe9:db98 DVICO Bus 002 Device 002: ID 0fe9:db98 DVICO lspci -snip- 05:06.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 62) 05:06.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 62) 05:06.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) 05:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 05:07.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 05:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 05:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11)___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [EXPERIMENTAL] cx88+xc3028 - tests are required - was: Re: When xc3028/xc2028 will be supported?
On Jan 29, 2008 9:25 AM, Mauro Carvalho Chehab [EMAIL PROTECTED] wrote: Dâniel and others, Having this tested is a very good news! I'll need to merge this patch with two other patches that adds DVB support for cx88/xc3028. If I can manage to have some time for this merge, I'll commit and ask Linus to add this to 2.6.25. :) I've merged some patches from several authors, that add xc3028 support for cx88. The experimental tree is available at: http://linuxtv.org/hg/~mchehab/cx88-xc2028 This patch series adds support for the following boards: 59 - DVICO HDTV5 PCI Nano[18ac:d530] 60 - Pinnacle Hybrid PCTV[12ab:1788] 61 - Winfast TV2000 XP Global[107d:6f18] 62 - PowerColor Real Angel 330 [14f1:ea3d] 63 - Geniatech X8000-MT DVBT [14f1:8852] 64 - DViCO FusionHDTV DVB-T PRO [18ac:db30] In thesis, both analog and DVB support (for boards with DVB/ATSC) should be working (*). Maybe analog audio may need an additional configuration for some specific board (since they may require to add cfg.mts = 1 at xc3028 initialization code, on cx88-cards). Please test. Mauro, We spoke on Thursday, and you asked me to take a look at the code in your 'cx88-xc2028' tree over the weekend and fix it, if possible. The repository is broken after and including changeset ce6afd207b71 - Make xc3028 support more generic This changeset moves the device-specific configuration out of the cx88-dvb.c device-specific switch..case block, into a generic function. This patch breaks functionality, and imho, is not a good idea. Your changes assume that the analog side of the driver will come up before the digital side of the driver, which is not necessarily the case. Additionally, in some cases, the tuner itself is hidden behind an i2c gate that is controlled by the dvb / atsc demodulator. Because of the i2c gate, communication to the tuner might not be available at the time that the i2c bus is probed. For those reasons, the attach calls to the tuner driver should be fully qualified, relative to the functionality of the side of the driver that is attaching it. The device that I used to test is the FusionHDTV 5 PCI nano. This device uses an xc3008 (yes, that is xc3008 -- not a typo) and a s5h1409 demod. The device is capable of receiving ATSC digital broadcasts and the driver does not yet support analog television. Steve Toth made the patch that adds atsc support for that card, and his patch worked without the additional changesets that were added afterwards. I made some small fixes and enabled IR support -- see the bottom of this email for my pull request. Your email above states that you've merged some patches from several authors. What I recommend, in order to properly support each device, would be to apply each patch for each card separately, as we do with all card support additions. We know that the original patches, as submitted by the original authors work properly , since those authors have conducted their own tests. I understand that you've made some attempts to optimize the code in an effort to reduce memory consumption. Unfortunately, these efforts have broken functionality of these devices. I think that it would make more sense to work on optimizations after the basic device support patches are first applied in the standard manner. This way, you would have a good point of reference for before and after that testers will be able to use for comparison (and bisection). Since the only card that I can test is the PCI nano, please pull these changesets into master for now. Please pull from: http://linuxtv.org/hg/~mkrufky/cx88-xc2028 for: (91113b8955e2) 4 weeks ago Steven Toth cx88: Add support for the Dvico PCI Nano. (394d249f03f1) 47 hours ago Michael Krufky cx88: fix FusionHDTV 5 PCI nano name and enable IR support Regards, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] NEW version of dvico digital dual 4
sorry if this has been posted a few times not getting anything back from list just bought a new dvico dd4 card it has a revision 2.0 stamped on it it is not picked up by mythtv in the usb driver id the card is ID 0fe9:db*78* DVICO ID 0fe9:db*78* DVICO mi id on new card is ID 0fe9:db*98* DVICOso i changed the id to 98 linux picked it up as a dvico dd4 dvb card with two tuners now mythtv finds the card but no frontend i think they have changed that as well dmesg | grep dvb-usb [ 45.568438] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. [ 45.568759] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 45.676871] dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual Digital 4' [ 45.677733] dvb-usb: schedule remote query interval to 100 msecs. [ 45.677855] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. [ 45.677872] dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual Digital 4' in warm state. [ 45.678261] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 46.003003] dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual Digital 4' [ 46.003591] dvb-usb: schedule remote query interval to 100 msecs. [ 46.003900] dvb-usb: DViCO FusionHDTV DVB-T Dual Digital 4 successfully initialized and connected. lsusb -snip- Bus 002 Device 003: ID 0fe9:db98 DVICO Bus 002 Device 002: ID 0fe9:db98 DVICO lspci -snip- 05:06.0 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 62) 05:06.1 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1Controller (rev 62) 05:06.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 65) 05:07.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 05:07.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 05:08.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 11) 05:08.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 11) card is back in xp box for recording i can run a protocol program to find the id just need to know what to use hope you can help ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
