Re: [linux-dvb] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
Thanx! I can watch the channels from my channels.conf with super picture quality. Only the channel scanning doesn't work yet. It now only finds channels from the 1st transponder, after that is just gives timeout's. Is there anyone on this list that has the channels from canaldigitaal (the netherlands) in his/her channels.conf? If so, please send a copy to me :) Thanx Joep Op maandag 6 november 2006 19:47, schreef u: joep admiraal wrote: Hello, I installed libxine-dvb and now I can watch the channels from channels.conf with xine!! The picture quality ist very bad. It looks like the signal quality is very bad. I see a lot of mpeg blocks. With the Twinhan tool under Windows the picture quality is perfect. Am I the only one with this problem? I downloaded the latest daily rpm from Kaffeine. I can't find a way to watch dvb channels with Kaffeine. I see only dvd or cd options in the menus. After looking at http://www.linuxtv.org/wiki/index.php/Dvbtools I found out that the scan binary you were talking about is the same tool as dvbscan I am using. The parameters you gave for the scan utility are for dvb-c. I am using a 1034 card with dvb-s. So I don't think those parameters are going to work with my card :) The only change that you should be bothered with should be about the TS packet length, just revert this one line from Marko 's patch (for your 1034 DVB-S) - (mantis-ts_size ? dvb_dmx_swfilter_204: dvb_dmx_swfilter) + (mantis-ts_size ? dvb_dmx_swfilter: dvb_dmx_swfilter_204) and you are a winner. Manu Op zaterdag 4 november 2006 14:48, schreef Marko Ristola: Hi Joep, Scanning with Kaffeine works for me now also :) Ealier Livna repository Kaffeine didn't support setting QAM128. It used QAM64 always (HTV cable TV operator provides channel information on QAM128 mode here). I'm using kernel 2.6.18-1.2798.fc6 from Fedora Core 6. I use the stock FC6 kernel as a base. Then I install mantis drivers with #make all #cp v4l/cu1216.ko /lib/modules/2.6.18-1.2798.fc6/kernel/drivers/media/dvb/mantis/ #make install #reboot I use also Livna RPM repository for Xine and Kaffeine and for all other DVB stuff. I use scan binary from http://www.linuxtv.org/wiki/index.php/Dvbtools I installed it under /usr/local/ #ls /usr/local/lib libdvbapi.a libdvbcfg.a libdvben50221.a libdvbsec.a libucsi.a libdvbapi.so libdvbcfg.so libdvben50221.so libdvbsec.so libucsi.so I have for scanning fi-HTV file: # cat fi-HTV C 27400 690 AUTO QAM128 I have modified this by myself. The orginal fi-HTV is obsolete and doesn't work for me. You might get a complete channels.conf file from your TV channel provider. So for scanning you need to know the following parameters: One frequency: 274Mhz Symbol rate for that frequency: 6.9 Msyms/s Inversion: AUTO (this is ok for you too) Modulation: QAM128 I use scan binary like this (librarys are installed under /usr/local/lib): cd dvb-apps/util/scan #export LD_LIBRARY_PATH=/usr/local/lib #./scan -A 3 fi-HTV (-A 3 checks both cable and terrestial modes). You get help with the parameters with #export LD_LIBRARY_PATH=/usr/local/lib #./scan --help Regards, Marko joep admiraal wrote: I'm using OpenSuse 10.1 Kernel 2.6.16.21-0.13 What kernel are you using Marko? If I run dvbscan the second time doesn't find any channels. It only gives filter timeouts. I don't have a scan binary on my machine. How can I watch TV channel's with xine? When I choose playlist-get from-dvb xine just locks up ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb --- ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] not the same results about a station with tzap
Hartmut Hackmann a écrit : Hi, tomlohave wrote: Hello, I'm testing an hvr1110 and only with one channel there is some problems (little squares on screen and disturb sound): tzap -c .mplayer/channels.conf France-2 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 586166000 Hz video pid 0x0078, audio pid 0x0082 status 00 | signal | snr | ber 0001fffe | unc | status 00 | signal 9494 | snr 4f4f | ber 0001fffe | unc | status 1f | signal 9494 | snr fdfd | ber 047a | unc | FE_HAS_LOCK status 1f | signal 9393 | snr f5f5 | ber 050a | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0508 | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 0500 | unc | FE_HAS_LOCK status 1f | signal 9595 | snr fafa | ber 04dc | unc | FE_HAS_LOCK status 1f | signal 9595 | snr f7f7 | ber 04a8 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 067c | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fdfd | ber 04dc | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 04bc | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 04b4 | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 04c0 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 046a | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0434 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0482 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 04b4 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fafa | ber 04a8 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fdfd | ber 0494 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0480 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr f9f9 | ber 04da | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fbfb | ber 04ac | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 04f4 | unc | FE_HAS_LOCK ^ Here, all is good, but on the channel called M6 : tzap -c .mplayer/channels.conf M6 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 522166000 Hz video pid 0x0078, audio pid 0x0082 status 00 | signal a9a9 | snr 4747 | ber 0001fffe | unc | status 1f | signal abab | snr fbfb | ber 286a | unc | FE_HAS_LOCK status 1f | signal | snr fcfc | ber 2dda | unc 0028 | FE_HAS_LOCK status 1f | signal a8a8 | snr fbfb | ber 2c5a | unc | FE_HAS_LOCK status 1f | signal afaf | snr f4f4 | ber bfaa | unc | FE_HAS_LOCK status 1f | signal a7a7 | snr f0f0 | ber 9892 | unc | FE_HAS_LOCK status 1f | signal | snr fdfd | ber 2bf0 | unc | FE_HAS_LOCK status 1f | signal a9a9 | snr fefe | ber 2b18 | unc 0016 | FE_HAS_LOCK status 1f | signal a8a8 | snr fdfd | ber b134 | unc | FE_HAS_LOCK status 1f | signal a7a7 | snr fefe | ber 9798 | unc | FE_HAS_LOCK status 1f | signal a8a8 | snr fbfb | ber 3d44 | unc | FE_HAS_LOCK status 1f | signal | snr fefe | ber 28c6 | unc | FE_HAS_LOCK status 1f | signal | snr fefe | ber 29fe | unc | FE_HAS_LOCK status 1f | signal | snr f7f7 | ber 4212 | unc | FE_HAS_LOCK status 1f | signal a4a4 | snr e3e3 | ber e6a4 | unc | FE_HAS_LOCK status 1f | signal | snr fafa | ber 37fc | unc | FE_HAS_LOCK status 1f | signal a8a8 | snr f9f9 | ber 5908 | unc | FE_HAS_LOCK status 1f | signal a9a9 | snr f9f9 | ber 385a | unc | FE_HAS_LOCK status 1f | signal a1a1 | snr f4f4 | ber 0001137a | unc | FE_HAS_LOCK status 1f | signal | snr fcfc | ber 2b62 | unc | FE_HAS_LOCK status 1f | signal | snr fdfd | ber 30a2 | unc | FE_HAS_LOCK status 1f | signal a4a4 | snr f9f9 | ber 3f5e | unc 0015 | FE_HAS_LOCK status 1f | signal abab | snr fdfd | ber 30c6 | unc 0010 | FE_HAS_LOCK status 1f | signal acac | snr fafa | ber 36ee | unc 007c | FE_HAS_LOCK so why this difference ? other thing, i' ve got the same results with an hauppauge hybrid pro stick, but with another PC all is good. Mine is an athlon 800 (maybe not enought ?) Your PC definitely is fast enough. 2 possible reasons: - there is something wrong with the configuration data for this multiplex. you can set all options to AUTO in your channels.conf file except bandwidth and exact frquency (and the PIDs of corse) - The signal amplitude might be too high. Not sure but yout tuner might have a configuration option that is not yet supported in the tuner driver. This is something i urgently need to work on. Can you please try and give feedback? Hartmut i'm not sure i 'm very
Re: [linux-dvb] Pinnacle PCTV Hybrid Pro Stick model 330E - detection problem
Hi,
try to add
{ USB_DEVICE(0x2304, 0x0226), .driver_info =
EM2881_BOARD_PINNACLE_HYBRID_PRO },
in em28xx-cards.c (~line 1359); recompile, test and report what's going on..
cheers,
Markus
On 11/6/06, Davide Guidi [EMAIL PROTECTED] wrote:
Hi all,
i just bought this device and i'm wondering if it is actually supported by
linux.
It seems to be different from the previous Pinnacle PCTV Hybrid Pro Stick
model, in fact the vendor/product is
2304:0226 Pinnacle Systems, Inc. [hex]
Any ideas about how to make it work?
Thanx,
Davide
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
--
Markus Rechberger
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] dib7000H
Hi to everyone, I'd like to know if is possible to use dib7000-H (using SDIO DVB-H receiver module) on linux, I'm not able to find anything on internet, just I red there is a working release of dib7000m/p driver, but I'm not sure it'll work with 7000H. Can someone help me??? Thank you very much Giovanni ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dib7000H
On Tue, 7 Nov 2006, [EMAIL PROTECTED] wrote: Hi to everyone, I'd like to know if is possible to use dib7000-H (using SDIO DVB-H receiver module) on linux, I'm not able to find anything on internet, just I red there is a working release of dib7000m/p driver, but I'm not sure it'll work with 7000H. Can someone help me??? Normally, when you receive a DiBcom SDIO card (with the DiB7000H) you also get some software (depending on your request). If you received the SDK you have a linux driver (not related to linux-dvb). There are no plans to release anything about the 7000H to the public. IMPO unfortunately, but somehow understandable. Patrick. -- Mail: [EMAIL PROTECTED] WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Virtual diversity DVB adapter
Is there any tool or virtual driver to combine multiple real DVB adapter to one virtual diversity adapter? Input from /dev/dvb/adapter0 and /dev/dvb/adapter1 and error free output to virtual adapter /dev/dvb/adapter2 Or input form /dev/dvb/adapter0, /dev/dvb/adapter1, /dev/dvb/adapter2, /dev/dvb/adapter3 and combined error free output to /dev/dvb/adapter5 It can help in long-range DVB-T receiving (DX) or in car (train). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Hanftek UMT-010 DVB-T USB2.0 Stick with Kubuntu Edgy Eft, Kernel 2.6.17-10-generic
Hello, I am sorry in case you think I haven't been polite. My Name is Richard and this post here (you could have recieved it some days before) is my first one. So I will ask you to help me, if you can. Please read this mail (again), because I added an important point. Thursday last week I bought a DVD-Stick, named 'Hanftek UMT-010 DVB-T USB2.0'. I installed it under Windows XP and I could recieve channels. Now I wanted to make it run with my linux OS, Kubuntu Edgy Eft / Kernel 2.6.17-10-generic. I cloned the last v4l-Directories from linuxtv.org and integrated the modules into my sytem with 'make' and make 'install' After that I rebooted my Laptop and stuck in my DVB-T-stick and with 'dmesg' I recieved: -quote: Nov 2 21:27:51 sedna kernel: [4294854.693000] usb 3-1: new high speed USB device using ehci_hcd and address 3 -- Nov 2 21:27:51 sedna kernel: [4294855.02] dvb-usb: found a 'Hanftek UMT-010 DVB-T USB2.0' in cold state, will try to load a firmware Nov 2 21:27:51 sedna kernel: [4294855.099000] dvb_usb_umt_010: probe of 3-1:1.0 failed with error -22 Nov 2 21:27:51 sedna kernel: [4294855.099000] usbcore: registered new driver dvb_usb_umt_010 Nov 2 21:30:46 sedna kernel: [4295030.075000] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Nov 2 21:30:46 sedna kernel: [4295030.076000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Nov 2 21:32:31 sedna kernel: [4295134.987000] usb 3-1: USB disconnect, address 3 Ok, I should copy the 'dvb-usb-umt-010-02.fw' firmware file into /lib/firmware. I loaded it from linuxtv.org again and copied it. After reboot, I stuck in again my stick and dmesg displayed now: -quote: Nov 2 21:34:21 sedna kernel: [4295244.943000] usb 3-1: new high speed USB device using ehci_hcd and address 4 Nov 2 21:34:21 sedna kernel: [4295245.057000] dvb-usb: found a 'Hanftek UMT-010 DVB-T USB2.0' in cold state, will try to load a firmware Nov 2 21:34:21 sedna kernel: [4295245.075000] dvb-usb: downloading firmware from file 'dvb-usb-umt-010-02.fw' Nov 2 21:34:22 sedna kernel: [4295245.237000] usb 3-1: USB disconnect, address 4 Nov 2 21:34:22 sedna kernel: [4295245.237000] dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. Nov 2 21:34:23 sedna kernel: [4295246.943000] usb 3-1: new high speed USB device using ehci_hcd and address 5 Nov 2 21:34:23 sedna kernel: [4295247.058000] dvb-usb: found a 'Hanftek UMT-010 DVB-T USB2.0' in warm state. Nov 2 21:34:23 sedna kernel: [4295247.069000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. Nov 2 21:34:23 sedna kernel: [4295247.069000] DVB: registering new adapter (Hanftek UMT-010 DVB-T USB2.0). Everything seems to be loaded properly. But my LED is not burning! Some dvb-t description websites expected it should burn. And though I have a proper channel-table file (de-KoelnBonn) I cannot scan for stations. The scan runs within 10 seconds (too fast!) without finding any station. It's telling 'tuning failed' 6 times. With another pc and a build-in pci-card (ttpci) the scan runs well. In Kaffeine I find the device 'Zarlink MT352' but scanning is unsuccessful here, too. What I can see, that there is no signal beeing recieved while scanning. I followed the advice to rename the usb-dibusb-6.0.0.8.fw file into usb-umt-010-02.fw, copied it into /lib/firmware to load this firmware file instead of the original one. The result is worse then before. Do you have any idea? Can I use an original Windows firmware dll or sys file from the OEM-cd and rename it into usb-umt-010-02.fw, or what can I do else. To point the problem: My LED doesn't begin to burn after sticking in. With Windows the LED is burning, and with linux it should burn when using the right dirmware file. Maybe important for you: Output of lsusb: Bus 005 Device 003: ID 15f4:0015 HanfTek Thank you in advance. -Richard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Question relating to media players (GXine in particular) and DVB-S channels
Hello I've got a DVB-S (satellite) card which I've properly installed in my Linux box which I can tune to various channels using the dvbtune utility and I've created a channels.conf file and placed it in the .xine directory. When I use gxine however it reports that there is no lock. I know that this does in fact lock but the scan utility uses the -l DBS (local oscillator frequency DBS = 12500MHz) and there does not seem to be any way to set this crucial piece of info up in gxine from what I can tell. I know I'm missing something as I see many people using this as a viewer but I 'm stumped... Can someone please point me to the correct info? Thanks Mark ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] nova-t 500 tuning problems
On Mon, 2006-11-06 at 17:41 +0100, Patrick Boettcher wrote: Maybe there is something wrong in the mt2060 calculation for offset frequencies. Trying to find BBC ONE;BBC:506000:B8:T:27500:600:601=eng,602=eng:0:0:4164:9018:4100:0 with w_scan gives me this log output when tuning with mt2060 debug=1; Nov 7 14:40:58 htpc kernel: MT2060: PLL freq=506000kHz f_lo1=1726000kHz f_lo2=1183850kHz Nov 7 14:40:58 htpc kernel: MT2060: PLL div1=107 num1=56 div2=73 num2=8115 Nov 7 14:40:58 htpc kernel: MT2060: PLL [1..5]: 5e 6b 3 fb 93 Nov 7 14:40:59 htpc kernel: MT2060: IF1: 1220MHz This seems to look ok? Is there any way of finding the PLL values the tuner uses when running under windows? Trying to tune to original frequency with offset applied gives this log output; Nov 7 14:45:34 htpc kernel: MT2060: IF1: 1220MHz Nov 7 14:45:34 htpc kernel: MT2060: PLL freq=505833kHz f_lo1=1725750kHz f_lo2=1183750kHz Nov 7 14:45:34 htpc kernel: MT2060: PLL div1=107 num1=55 div2=73 num2=8064 Nov 7 14:45:34 htpc kernel: MT2060: PLL [1..5]: 5d 6b 30 f8 93 tzap seems to be unable to tune to 506000khz, even with a modified channel conf file it insists on tuning to 505833khz. Maybe it tries to interpret the stream and retunes to that frequency? -- Torgeir Veimo [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Freecom DVB-T card tuning, Re: [linux-dvb] Trouble with Pinnacle 310i DVB-T
It depends. If you use an initial config file i.e. for scan, it should be possible to do this separately for each transponder. Adding this in the driver is not a good solution: This is country depending and the offset is not constant. A better solution would be either to handle this in the scanning program or in an extended offset search in the driver. I have not heard anything more on this issue? I have the Freecom stick, and I find that I need to offset the transponder frequency for the initial scan. BUT - if I use auto scan (so I don't select a transponder) in the latest Kaffine it all works fine. Is this a solution for Benjamin? Thanks, Tim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
Joep, What is the content of the file you are using to test your scan, even if it only does one transponder. I'm testing with the default one and only get the following result: scanning /usr/share/dvb-apps/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 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. Content of the Astra-19.2E file is: # Astra 19.2E SDT info service transponder # freq pol sr fec S 12551500 V 2200 5/6 Regards, Michel. joep admiraal schreef: Thanx! I can watch the channels from my channels.conf with super picture quality. Only the channel scanning doesn't work yet. It now only finds channels from the 1st transponder, after that is just gives timeout's. Is there anyone on this list that has the channels from canaldigitaal (the netherlands) in his/her channels.conf? If so, please send a copy to me :) Thanx Joep ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
Hello Michel, I am using the same file you are. It contains the same info as your's. After I do a reboot it does find some channels. Before I applied the patch it did find channels on a few transponders. Now it only finds channels on the first transponder. I am doing some tests with Mythtv now. From mythtv I can also scan for channels. It generates a list of tranponders and I can perform a scan per transponder. So I do a scan and after that I do a reboot so I can scan the next transponder. This seems to work for all vertical transponders. For some reason it gives me timeout's for all the horizontal transponders. regards, joep Op dinsdag 7 november 2006 17:52, schreef Michel Verbraak: Joep, What is the content of the file you are using to test your scan, even if it only does one transponder. I'm testing with the default one and only get the following result: scanning /usr/share/dvb-apps/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 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. Content of the Astra-19.2E file is: # Astra 19.2E SDT info service transponder # freq pol sr fec S 12551500 V 2200 5/6 Regards, Michel. joep admiraal schreef: Thanx! I can watch the channels from my channels.conf with super picture quality. Only the channel scanning doesn't work yet. It now only finds channels from the 1st transponder, after that is just gives timeout's. Is there anyone on this list that has the channels from canaldigitaal (the netherlands) in his/her channels.conf? If so, please send a copy to me :) Thanx Joep ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033
joep admiraal schreef: Hello Michel, I am using the same file you are. It contains the same info as your's. After I do a reboot it does find some channels. Before I applied the patch it did find channels on a few transponders. Now it only finds channels on the first transponder. I am doing some tests with Mythtv now. From mythtv I can also scan for channels. It generates a list of tranponders and I can perform a scan per transponder. So I do a scan and after that I do a reboot so I can scan the next transponder. This seems to work for all vertical transponders. For some reason it gives me timeout's for all the horizontal transponders. Looks like a lot of work to reboot every time. Manu any solutions? I know it is still Alpha release. regards, joep Op dinsdag 7 november 2006 17:52, schreef Michel Verbraak: Joep, What is the content of the file you are using to test your scan, even if it only does one transponder. I'm testing with the default one and only get the following result: scanning /usr/share/dvb-apps/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 WARNING: filter timeout pid 0x0011 WARNING: filter timeout pid 0x WARNING: filter timeout pid 0x0010 dumping lists (0 services) Done. Content of the Astra-19.2E file is: # Astra 19.2E SDT info service transponder # freq pol sr fec S 12551500 V 2200 5/6 Regards, Michel. joep admiraal schreef: Thanx! I can watch the channels from my channels.conf with super picture quality. Only the channel scanning doesn't work yet. It now only finds channels from the 1st transponder, after that is just gives timeout's. Is there anyone on this list that has the channels from canaldigitaal (the netherlands) in his/her channels.conf? If so, please send a copy to me :) Thanx Joep ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: Freecom DVB-T card tuning, Re: [linux-dvb] Trouble with Pinnacle 310i DVB-T
When I last used the card (which makes my machine unstable for some reason, so I don't use at present... see PS), I used Kaffeine to scan, and it found many but not all channels. I intend to use the card with my working mythtv setup, I do not want to have to have 2 lots of channel configs (twice the channels) when the frequencies should be the same for all cards. [I also have a different Freecom stick, which has worked perfectly for a long time.] I just want the same tuning to occur on both Freecom sticks, the old and the new, seems like a sensible thing to do...? At the moment I have to change the frequency for just the new stick. Regards, Benjie Gillam. PS: Instability issues. I get a lot of the recv bulk message failed: -22 type messages (normally -110 seems to be harmless, -75 is a bit iffy, but generally OK, and -22 means stuff is really messing around... I have no idea what these numbers really mean, and there are more than just these 3 displayed... Also, my quote is from memory). Recently after having my computer on for more than around 24 hours, with both old and new freecom cards plugged in (plus a Pinnacle 300i PCI and an old WinTV analog PCI card) the keyboard and mouse would freeze. This would mean that I could not wake X back up. The kernel was not dead, as by using magic keys (alt+SysRq+[RSEIUB]) I was able to restart my machine (fairly) cleanly. I still get this problem now from time to time, though it is far less often now I have stopped using both Freecom cards. I wonder if it is related to the usb bulk-recv errors? Please tell me if I can be of help. Tim Chick wrote: It depends. If you use an initial config file i.e. for scan, it should be possible to do this separately for each transponder. Adding this in the driver is not a good solution: This is country depending and the offset is not constant. A better solution would be either to handle this in the scanning program or in an extended offset search in the driver. I have not heard anything more on this issue? I have the Freecom stick, and I find that I need to offset the transponder frequency for the initial scan. BUT - if I use auto scan (so I don't select a transponder) in the latest Kaffine it all works fine. Is this a solution for Benjamin? Thanks, Tim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Medion SAA7134 and DVB-S - How?
hermann pitton schrieb: Hi! Am Dienstag, den 07.11.2006, 00:35 +0100 schrieb Hartmut Hackmann: Hi Chris Winger wrote: [...] If I start kaffeine, I get DVB-T to work. Kaffeine recognisez the card as: Using DVB device 0:0 Philips TDA10046H DVB-T Why TDA10046H instead of FMD1216ME? TDA10046 is the channel decoder which is the center of the frontend: Thats correct. Why is there no other device for DVB-S available? Hm, does anybody know which channel decoder and tuner are used in the DVB-S section? Remember, we had this one on the video4linux-list. It has a conventional DVB-S can tuner, likely covered by dvb-pll or easy to add, at least all questions were asked. The problem was the not yet supported tda10086 channel decoder. This has changed and also no problems with the dual PCI bridge are expected, except Mike took care to disable it ;) Should be worth to dig it out. Cheers, Hermann Hi, Are you referring to this thread? https://www.redhat.com/mailman/private/video4linux-list/2006-August/msg00386.html Just for clarification: My card is part of the Medion MD8386 PC, it's not the MD8800 Quad card. I also found this: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc7/2.6.18-rc7-mm1/broken-out/git-dvb.patch but honestly I don't know how to aply that... Kind regards Chris ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Question relating to media players (GXine in particular) and DVB-S channels
I demand that Mark Cianfaglione may or may not have written... I've got a DVB-S (satellite) card which I've properly installed in my Linux box which I can tune to various channels using the dvbtune utility and I've created a channels.conf file and placed it in the .xine directory. When I use gxine however it reports that there is no lock. xine-lib is responsible for tuning; gxine knows nothing about it. I know that this does in fact lock but the scan utility uses the -l DBS (local oscillator frequency DBS = 12500MHz) and there does not seem to be any way to set this crucial piece of info up in gxine from what I can tell. Feel free to send patches for xine-lib, preferably to xine-devel or to the xine project's BTS... not being a DVB-S user, I can't really help with this. And it's gxine, not GXine. :-) [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output less CO2 = avoid massive flooding.TIME IS RUNNING OUT *FAST*. Language: a system of organising and defining syntax errors. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [xine-user] [linux-dvb] Question relating to media players (GXine in particular) and DVB-S channels
Darren Thanks for the info... Feel free to send patches for xine-lib, preferably to xine-devel or to the xine project's BTS... not being a DVB-S user, I can't really help with this. And it's gxine, not GXine. :-) Sorry about that... I'm so used to marketing-speak that it slipped... Mark ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Mantis VP-3033
Hi! I got a little time to spare today, so I played around a bit with the Mantis driver for the above card. As I've mentioned earlier, Mantis loads and creates all the backend stuff but stubbornly refuses to create a frontend. I know that Mantis tries to attach the zl10353 frontend to this card but when trying to retrieve the chip ID from the card, it retuns 0x00 instead of the expected 0x14. Since I've failed to find any specs for the card, I'm having a bit trouble to find the reason as to why retrieval of chip_id fails :-( I'm not even sure that it's the correct frontend to use for this one (It's a DVB-T card with CA slot). I'm attaching modified debug printout from loading/unloading the mantis driver and hope that someone can give me a bit more information on how to get this beast running :-/ Very best regards, Joachim Holst --- CUT PASTE --- Nov 7 22:47:57 arthur ACPI: PCI Interrupt :05:08.0[A] - Link [LNK3] - GSI 7 (level, low) - IRQ 7 Nov 7 22:47:57 arthur Mantis Rev 1, irq: 7, latency: 32 Nov 7 22:47:57 arthur memory: 0xc310, mmio: 0xf8c8a000 Nov 7 22:47:57 arthur get_mac_address (1): MAC Address=[ff:ff:ff:ff:ff:ff] Nov 7 22:47:58 arthur get_subvendor_id (1): Sub Vendor ID=[0x1822] Nov 7 22:47:58 arthur get_subdevice_id (1): Sub Device ID=[0x0024] Nov 7 22:47:58 arthur mantis_alloc_buffers (1): DMA=0x1d6e cpu=0xdd6e size=65536 Nov 7 22:47:58 arthur mantis_alloc_buffers (1): RISC=0x3303c000 cpu=0xf303c000 size=1000 Nov 7 22:47:58 arthur DVB: registering new adapter (Mantis dvb adapter). Nov 7 22:47:58 arthur mantis_frontend_init (1): Mantis frontend Init Nov 7 22:47:58 arthur mantis_frontend_init (1): Device ID=24 Nov 7 22:47:58 arthur mantis_frontend_init (1): Probing for 10353 (DVB-T) Nov 7 22:47:58 arthur Trying to attach zl10353 frontend Nov 7 22:47:58 arthur zl10353_read_register: Device name: Mantis I2C Nov 7 22:47:58 arthur zl10353_read_register: Managed to read 2 messages from I2C Nov 7 22:47:58 arthur zl10353_read_register: Requested value = b0[0] = 0x7f Nov 7 22:47:58 arthur zl10353_read_register: Return value b1[0] = 0x0. Nov 7 22:47:58 arthur zl10353_attach: Failed to get chip ID Nov 7 22:47:58 arthur zl10353_attach: Ooops! Something went wrong. Returning NULL Nov 7 22:47:58 arthur mantis_frontend_init (1): !!! NO Frontends found !!! -- Unloading Nov 7 22:48:04 arthur mantis_core_exit (1): DMA engine stopping Nov 7 22:48:04 arthur mantis_dma_exit (1): DMA=0x1d6e cpu=0xdd6e size=65536 Nov 7 22:48:04 arthur mantis_dma_exit (1): RISC=0x3303c000 cpu=0xf303c000 size=1000 Nov 7 22:48:04 arthur mantis_pci_remove (1): Removing --Mantis irq: 7, latency: 32 Nov 7 22:48:04 arthur memory: 0xc310, mmio: 0xf8c8a000 --- END CUT PASTE --- ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Medion SAA7134 and DVB-S - How?
Hi, Am Dienstag, den 07.11.2006, 20:21 + schrieb Chris Winger: hermann pitton schrieb: Hi! Am Dienstag, den 07.11.2006, 00:35 +0100 schrieb Hartmut Hackmann: Hi Chris Winger wrote: [...] If I start kaffeine, I get DVB-T to work. Kaffeine recognisez the card as: Using DVB device 0:0 Philips TDA10046H DVB-T Why TDA10046H instead of FMD1216ME? TDA10046 is the channel decoder which is the center of the frontend: Thats correct. Why is there no other device for DVB-S available? Hm, does anybody know which channel decoder and tuner are used in the DVB-S section? Remember, we had this one on the video4linux-list. It has a conventional DVB-S can tuner, likely covered by dvb-pll or easy to add, at least all questions were asked. The problem was the not yet supported tda10086 channel decoder. This has changed and also no problems with the dual PCI bridge are expected, except Mike took care to disable it ;) Should be worth to dig it out. Cheers, Hermann Hi, Are you referring to this thread? https://www.redhat.com/mailman/private/video4linux-list/2006-August/msg00386.html Just for clarification: My card is part of the Medion MD8386 PC, it's not the MD8800 Quad card. no, I'm referring to Serdar Dere and the Medion CTX925_V.1 DVB-T/TV/DVB-S http://marc.theaimsgroup.com/?l=linux-videom=112033921222922w=2 I also found this: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc7/2.6.18-rc7-mm1/broken-out/git-dvb.patch but honestly I don't know how to aply that... There are no patches yet, neither for the Medion Quad nor for your card to get DVB-S working, but the components are likely supported. In your case there are two saa7134 PCI bridges, which behave like two seperate PCI cards in the special blue PCI slot. The 16be:0005 bridge is assumed to handle DVB-S and has a tda10086ht channel decoder and Andrew recently wrote support for it. Your DVB-S tuner is labeled as SD1878/SHA. Should be the same like here. http://www.knc1.com/img/presse_big/karte_tv_star_dvb_s.jpg And there were these patches recently to support it. http://www.linuxtv.org/pipermail/linux-dvb/2006-January/007511.html So this looks not bad, but maybe Hartmut can explain a little, what are the difficulties with two PCI bridges and two frontends. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Medion SAA7134 and DVB-S - How?
Hi, Am Dienstag, den 07.11.2006, 20:21 + schrieb Chris Winger: hermann pitton schrieb: Hi! Am Dienstag, den 07.11.2006, 00:35 +0100 schrieb Hartmut Hackmann: Hi Chris Winger wrote: [...] If I start kaffeine, I get DVB-T to work. Kaffeine recognisez the card as: Using DVB device 0:0 Philips TDA10046H DVB-T Why TDA10046H instead of FMD1216ME? TDA10046 is the channel decoder which is the center of the frontend: Thats correct. Why is there no other device for DVB-S available? Hm, does anybody know which channel decoder and tuner are used in the DVB-S section? Remember, we had this one on the video4linux-list. It has a conventional DVB-S can tuner, likely covered by dvb-pll or easy to add, at least all questions were asked. The problem was the not yet supported tda10086 channel decoder. This has changed and also no problems with the dual PCI bridge are expected, except Mike took care to disable it ;) Should be worth to dig it out. Cheers, Hermann Hi, Are you referring to this thread? https://www.redhat.com/mailman/private/video4linux-list/2006-August/msg00386.html Just for clarification: My card is part of the Medion MD8386 PC, it's not the MD8800 Quad card. no, I'm referring to Serdar Dere and the Medion CTX925_V.1 DVB-T/TV/DVB-S http://marc.theaimsgroup.com/?l=linux-videom=112033921222922w=2 I also found this: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc7/2.6.18-rc7-mm1/broken-out/git-dvb.patch but honestly I don't know how to aply that... There are no patches yet, neither for the Medion Quad nor for your card to get DVB-S working, but the components are likely supported. In your case there are two saa7134 PCI bridges, which behave like two seperate PCI cards in the special blue PCI slot. The 16be:0005 bridge is assumed to handle DVB-S and has a tda10086ht channel decoder and Andrew recently wrote support for it. Your DVB-S tuner is labeled as SD1878/SHA. Should be the same like here. http://www.knc1.com/img/presse_big/karte_tv_star_dvb_s.jpg And there were these patches recently to support it. http://www.linuxtv.org/pipermail/linux-dvb/2006-January/007511.html So this looks not bad, but maybe Hartmut can explain a little, what are the difficulties with two PCI bridges and two frontends. Cheers, Hermann Sorry, typo in Hartmut's address. Resent. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle PCTV Hybrid Pro Stick model 330E - detection problem
On Tuesday 07 November 2006 11:01, you wrote:
Hi,
try to add
{ USB_DEVICE(0x2304, 0x0226), .driver_info =
EM2881_BOARD_PINNACLE_HYBRID_PRO },
in em28xx-cards.c (~line 1359); recompile, test and report what's going
on..
cheers,
Markus
Thanks a lot, adding that line make my device (at least partly) works!
Summary:
Using both xawtv and mplayer i have video. I was able to have audio only using
mplayer, but audio is still not fluid.
I used the following parameters with mplayer: -tv
driver=v4l2:device=/dev/video0:input=0:immediatemode=0:adevice=/dev/audio1
tv://
At this time, no way to load the DVB module.
The remote control seems to work, even if they keys do not correspond to the
associated functions.
In the following i report some log output, hope it will be useful.
Is there something else i can do?
Davide
Mplayer output this info about my device:
Selected driver: v4l2
name: Video 4 Linux 2 input
author: Martin Olschewski [EMAIL PROTECTED]
comment: first try, more to come ;-)
Selected device: Pinnacle Hybrid Pro
Tuner cap:
Tuner rxs:
Capabilites: video capture VBI capture device tuner audio read/write
streaming
supported norms: 0 = PAL-BG; 1 = PAL-DK; 2 = PAL-I; 3 = NTSC; 4 = SECAM L; 5
= SECAM LC; 6 = SECAM K1; 7 = PAL-M;
inputs: 0 = Television; 1 = Composite1; 2 = S-Video;
Current input: 0
Current format: YUYV
v4l2: current audio mode is : MONO
Audio block size too low, setting to 5764!
Maybe the audio problem that i have is associated to this last line regarding
audio block size.
When plugging in the device:
Nov 7 23:06:49 fishtank kernel: usb 5-4: new high speed USB device using
ehci_hcd and address 6
Nov 7 23:06:49 fishtank kernel: usb 5-4: configuration #1 chosen from 1
choice
Nov 7 23:06:49 fishtank kernel: Linux video capture interface: v2.00
Nov 7 23:06:49 fishtank kernel: em28xx v4l2 driver version 0.0.1 loaded
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate settings: 8
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 0, max size= 0
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 1, max size= 0
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 2, max size=
1448
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 3, max size=
2048
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 4, max size=
2304
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 5, max size=
2580
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 6, max size=
2892
Nov 7 23:06:49 fishtank kernel: em28xx #0: Alternate setting 7, max size=
3072
Nov 7 23:06:49 fishtank kernel: i2c_adapter i2c-1: SMBus Quick command not
supported, can't probe for chips
Nov 7 23:06:49 fishtank kernel: i2c_adapter i2c-2: SMBus Quick command not
supported, can't probe for chips
Nov 7 23:06:49 fishtank kernel: i2c_adapter i2c-3: SMBus Quick command not
supported, can't probe for chips
Nov 7 23:06:50 fishtank kernel: Tuner: registering extension (Xceive 3028
Tuner)
Nov 7 23:06:50 fishtank kernel: input: em2880/em2870 remote control
as /class/input/input3
Nov 7 23:06:50 fishtank kernel: em28xx-input.c: remote control handler
attached
Nov 7 23:06:50 fishtank kernel: attach_inform: eeprom detected.
Nov 7 23:06:50 fishtank kernel: tuner 4-0061: chip found @ 0xc2 (em28xx #0)
Nov 7 23:06:50 fishtank kernel: attach inform: detected I2C address c2
Nov 7 23:06:50 fishtank kernel: Tuner: setting up tuner core extension for:
Xceive 3028 Tuner
Nov 7 23:06:50 fishtank kernel: Loading base firmware: xc3028_init0.i2c.fw
Nov 7 23:06:51 fishtank kernel: Loading default analogue TV settings:
xc3028_BG_PAL_A2_A.i2c.fw
Nov 7 23:06:51 fishtank kernel: attach_inform: tvp5150 detected.
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 00: 1a eb 67 95 04 23
26 02 d0 12 5c 03 8e 16 a4 1c
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 10: 6a 24 27 57 46 07
01 00 00 00 00 00 00 00 00 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10
02 00 b8 00 00 00 5b e0 00 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 30: 00 00 20 40 20 6e
02 20 10 01 00 00 00 00 00 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 40: 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 50: 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 60: 00 00 00 00 00 00
00 00 00 00 24 03 50 00 69 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 70: 6e 00 6e 00 61 00
63 00 6c 00 65 00 20 00 53 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 80: 79 00 73 00 74 00
65 00 6d 00 73 00 00 00 16 03
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom 90: 50 00 43 00 54 00
56 00 20 00 33 00 33 00 30 00
Nov 7 23:06:51 fishtank kernel: em28xx #0: i2c eeprom a0: 65 00 00 00 1c 03
30 00 36 00 31 00 30 00 30 00
Nov 7
[linux-dvb] kernel Oops while unloading the card
Hauppauge WinTV-NOVA-T usb2. kernel 2.6.18.2 latest v4l-dvb. I had (once) this Oops while unplugging the card with no apps accessing it. Is it possible that the code checking for the remote control should be stopped before unplugging the cable? The same as any application actually playing some video Why is the Oops occuring after the dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully deinitialized and disconnected. Shouldn't the driver be unloaded byt that time? What I mean is: should I always run make unload before unplugging? Or is it just an unlucky situation? Nov 6 22:48:45 thinkpad kernel: dvb-usb: bulk message failed: -71 (2/0) Nov 6 22:48:45 thinkpad kernel: usb 4-4: USB disconnect, address 4 Nov 6 22:48:45 thinkpad kernel: dvb-usb: bulk message failed: -22 (2/0) Nov 6 22:48:45 thinkpad kernel: dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully deinitialized and disconnected. Nov 6 22:48:45 thinkpad kernel: BUG: unable to handle kernel paging request at virtual address 74707665 Nov 6 22:48:45 thinkpad kernel: printing eip: Nov 6 22:48:45 thinkpad kernel: 74707665 Nov 6 22:48:45 thinkpad kernel: *pde = Nov 6 22:48:45 thinkpad kernel: Oops: [#1] Nov 6 22:48:45 thinkpad kernel: Modules linked in: mt2060 dvb_usb_nova_t_usb2 dvb_usb_dibusb_common dib3000mc dibx000_common dvb_usb dvb_core dvb_pll radeon drm i2c_dev i2c_core xt_tcpudp xt_state iptable_nat ip_nat ip_conntrack iptable_filter ip_tables x_tables vfat fat parport_pc parport nvram 8250_pci 8250 serial_core snd_intel8x0m snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm ohci1394 ieee1394 ehci_hcd uhci_hcd e1000 snd_timer intel_agp snd agpgart pcspkr soundcore snd_page_alloc Nov 6 22:48:45 thinkpad kernel: CPU:0 Nov 6 22:48:45 thinkpad kernel: EIP:0060:[74707665]Not tainted VLI Nov 6 22:48:45 thinkpad kernel: EFLAGS: 00010246 (2.6.18.2 #1) Nov 6 22:48:45 thinkpad kernel: EIP is at 0x74707665 Nov 6 22:48:45 thinkpad kernel: eax: dfe29f64 ebx: 0286 ecx: c14796c8 edx: c14796c8 Nov 6 22:48:45 thinkpad kernel: esi: d65b2000 edi: c14796c0 ebp: d65b2000 esp: dfe29f50 Nov 6 22:48:45 thinkpad kernel: ds: 007b es: 007b ss: 0068 Nov 6 22:48:45 thinkpad kernel: Process events/0 (pid: 3, ti=dfe28000 task=dfe0e030 task.ti=dfe28000) Nov 6 22:48:45 thinkpad kernel: Stack: e0af47a7 d65b2000 dfe29f64 dfe29f60 06fb 0286 d65b2f9c Nov 6 22:48:45 thinkpad kernel:c011ba5c d65b2000 e0af4782 c14796d0 c14796c0 c14796c8 c011bf7a Nov 6 22:48:45 thinkpad kernel:0001 dfe21f44 0001 dfe0e030 c010d018 Nov 6 22:48:45 thinkpad kernel: Call Trace: Nov 6 22:48:45 thinkpad kernel: [e0af47a7] dvb_usb_read_remote_control+0x25/0xee [dvb_usb] Nov 6 22:48:45 thinkpad kernel: [c011ba5c] run_workqueue+0x68/0x96 Nov 6 22:48:45 thinkpad kernel: [e0af4782] dvb_usb_read_remote_control+0x0/0xee [dvb_usb] Nov 6 22:48:45 thinkpad kernel: [c011bf7a] worker_thread+0xf2/0x124 Nov 6 22:48:45 thinkpad kernel: [c010d018] default_wake_function+0x0/0x15 Nov 6 22:48:45 thinkpad kernel: [c011be88] worker_thread+0x0/0x124 Nov 6 22:48:45 thinkpad kernel: [c011e045] kthread+0xb1/0xe0 Nov 6 22:48:45 thinkpad kernel: [c011df94] kthread+0x0/0xe0 Nov 6 22:48:45 thinkpad kernel: [c0100ac9] kernel_thread_helper+0x5/0xb Nov 6 22:48:45 thinkpad kernel: Code: Bad EIP value. Nov 6 22:48:45 thinkpad kernel: EIP: [74707665] 0x74707665 SS:ESP 0068:dfe29f50 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] not the same results about a station with tzap
Hi [EMAIL PROTECTED] wrote: Hartmut Hackmann a écrit : Hi, tomlohave wrote: Hello, I'm testing an hvr1110 and only with one channel there is some problems (little squares on screen and disturb sound): tzap -c .mplayer/channels.conf France-2 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 586166000 Hz video pid 0x0078, audio pid 0x0082 status 00 | signal | snr | ber 0001fffe | unc | status 00 | signal 9494 | snr 4f4f | ber 0001fffe | unc | status 1f | signal 9494 | snr fdfd | ber 047a | unc | FE_HAS_LOCK status 1f | signal 9393 | snr f5f5 | ber 050a | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0508 | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 0500 | unc | FE_HAS_LOCK status 1f | signal 9595 | snr fafa | ber 04dc | unc | FE_HAS_LOCK status 1f | signal 9595 | snr f7f7 | ber 04a8 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 067c | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fdfd | ber 04dc | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 04bc | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 04b4 | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 04c0 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 046a | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0434 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0482 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 04b4 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fafa | ber 04a8 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fdfd | ber 0494 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fefe | ber 0480 | unc | FE_HAS_LOCK status 1f | signal 9494 | snr f9f9 | ber 04da | unc | FE_HAS_LOCK status 1f | signal 9494 | snr fbfb | ber 04ac | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fefe | ber 04f4 | unc | FE_HAS_LOCK ^ Here, all is good, but on the channel called M6 : tzap -c .mplayer/channels.conf M6 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' tuning to 522166000 Hz video pid 0x0078, audio pid 0x0082 status 00 | signal a9a9 | snr 4747 | ber 0001fffe | unc | status 1f | signal abab | snr fbfb | ber 286a | unc | FE_HAS_LOCK status 1f | signal | snr fcfc | ber 2dda | unc 0028 | FE_HAS_LOCK status 1f | signal a8a8 | snr fbfb | ber 2c5a | unc | FE_HAS_LOCK status 1f | signal afaf | snr f4f4 | ber bfaa | unc | FE_HAS_LOCK status 1f | signal a7a7 | snr f0f0 | ber 9892 | unc | FE_HAS_LOCK status 1f | signal | snr fdfd | ber 2bf0 | unc | FE_HAS_LOCK status 1f | signal a9a9 | snr fefe | ber 2b18 | unc 0016 | FE_HAS_LOCK status 1f | signal a8a8 | snr fdfd | ber b134 | unc | FE_HAS_LOCK status 1f | signal a7a7 | snr fefe | ber 9798 | unc | FE_HAS_LOCK status 1f | signal a8a8 | snr fbfb | ber 3d44 | unc | FE_HAS_LOCK status 1f | signal | snr fefe | ber 28c6 | unc | FE_HAS_LOCK status 1f | signal | snr fefe | ber 29fe | unc | FE_HAS_LOCK status 1f | signal | snr f7f7 | ber 4212 | unc | FE_HAS_LOCK status 1f | signal a4a4 | snr e3e3 | ber e6a4 | unc | FE_HAS_LOCK status 1f | signal | snr fafa | ber 37fc | unc | FE_HAS_LOCK status 1f | signal a8a8 | snr f9f9 | ber 5908 | unc | FE_HAS_LOCK status 1f | signal a9a9 | snr f9f9 | ber 385a | unc | FE_HAS_LOCK status 1f | signal a1a1 | snr f4f4 | ber 0001137a | unc | FE_HAS_LOCK status 1f | signal | snr fcfc | ber 2b62 | unc | FE_HAS_LOCK status 1f | signal | snr fdfd | ber 30a2 | unc | FE_HAS_LOCK status 1f | signal a4a4 | snr f9f9 | ber 3f5e | unc 0015 | FE_HAS_LOCK status 1f | signal abab | snr fdfd | ber 30c6 | unc 0010 | FE_HAS_LOCK status 1f | signal acac | snr fafa | ber 36ee | unc 007c | FE_HAS_LOCK so why this difference ? other thing, i' ve got the same results with an hauppauge hybrid pro stick, but with another PC all is good. Mine is an athlon 800 (maybe not enought ?) Your PC definitely is fast enough. 2 possible reasons: - there is something wrong with the configuration data for this multiplex. you can set all options to AUTO in your channels.conf file except bandwidth and exact frquency (and the PIDs of corse) - The signal amplitude might be too high. Not sure but yout tuner might have a configuration option that is not yet supported in the tuner driver. This is something i urgently need to work on. Can you please try and give feedback?
Re: [linux-dvb] Medion SAA7134 and DVB-S - How?
Hi hermann pitton wrote: Hi, Am Dienstag, den 07.11.2006, 20:21 + schrieb Chris Winger: hermann pitton schrieb: Hi! Am Dienstag, den 07.11.2006, 00:35 +0100 schrieb Hartmut Hackmann: Hi Chris Winger wrote: [...] If I start kaffeine, I get DVB-T to work. Kaffeine recognisez the card as: Using DVB device 0:0 Philips TDA10046H DVB-T Why TDA10046H instead of FMD1216ME? TDA10046 is the channel decoder which is the center of the frontend: Thats correct. Why is there no other device for DVB-S available? Hm, does anybody know which channel decoder and tuner are used in the DVB-S section? Remember, we had this one on the video4linux-list. It has a conventional DVB-S can tuner, likely covered by dvb-pll or easy to add, at least all questions were asked. The problem was the not yet supported tda10086 channel decoder. This has changed and also no problems with the dual PCI bridge are expected, except Mike took care to disable it ;) Should be worth to dig it out. Cheers, Hermann Hi, Are you referring to this thread? https://www.redhat.com/mailman/private/video4linux-list/2006-August/msg00386.html Just for clarification: My card is part of the Medion MD8386 PC, it's not the MD8800 Quad card. no, I'm referring to Serdar Dere and the Medion CTX925_V.1 DVB-T/TV/DVB-S http://marc.theaimsgroup.com/?l=linux-videom=112033921222922w=2 I also found this: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc7/2.6.18-rc7-mm1/broken-out/git-dvb.patch but honestly I don't know how to aply that... There are no patches yet, neither for the Medion Quad nor for your card to get DVB-S working, but the components are likely supported. In your case there are two saa7134 PCI bridges, which behave like two seperate PCI cards in the special blue PCI slot. The 16be:0005 bridge is assumed to handle DVB-S and has a tda10086ht channel decoder and Andrew recently wrote support for it. Your DVB-S tuner is labeled as SD1878/SHA. Should be the same like here. http://www.knc1.com/img/presse_big/karte_tv_star_dvb_s.jpg And there were these patches recently to support it. http://www.linuxtv.org/pipermail/linux-dvb/2006-January/007511.html So this looks not bad, but maybe Hartmut can explain a little, what are the difficulties with two PCI bridges and two frontends. Cheers, Hermann Sorry, typo in Hartmut's address. Resent. In this case, there should be no problem. The 2 PCI bridges make 2 logically separate cards (as long as there are no funny things with the IRQ routing). If we have all components (channel decoder, tuner and LNB controller) supported, we should have a close look. Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
