Re: SV: [linux-dvb] How do I install properly (Fedora 5 andnova-t-500)?
On Tue, 26 Sep 2006, [EMAIL PROTECTED] wrote: > On Mon, 25 Sep 2006 22:37:57 +0200 (CEST), Patrick Boettcher wrote > > > DVB: registering frontend 1 (DiBcom 3000MC/P)... > > > MT2060: successfully identified (IF1 = 1220) > > > dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and > connected. > > > usbcore: registered new driver dvb_usb_dib0700 > > > ... > > > > What is not working? up to here it looks very good. > > Yes, but the problem is that I have to go to the root directory of the v4l > tree and "make reload" to get there after I "make install" and reboot. I want > the card to be recognised during boot, but at that point I get the message > about kernel being tainted and missing symbols. I tried rebooting a couple of > times to see if the drivers needed to "settle in", but it's the same thing > every time. Remove everything from /lib/modules//kernel/drivers/media and run make install in v4l-dvb/v4l. best regards, 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] cannot tune some frequences on hauppauge nova-se2
hello, i've tried to tune some frequences on hotbird like 12207 hz H... tried xine and koffeine and some others and it still does not work... tried it under windows xp and it works perfect, so the problem is not the card... but what else? i'm using ubuntu 6, 2.6.15-26-386 kernel, hauppauge nova-se2 hope anyone can help me thx bye marsellus ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cannot tune some frequences on hauppauge nova-se2
Hello, I had this kind of issue with a another card. In my case the card wasn't able to tune because the handling of vertical polarization was broken. What you can do is to test all the combination of high/low frequencies and vertical/horizontal polarization. In my case, i found that each time the polarization was vertical it didn't work. hope this will help you. regars, Raymond. On Tue, 2006-09-26 at 09:36 +0200, Marsellus Wallace wrote: > hello, > > i've tried to tune some frequences on hotbird like 12207 hz H... > tried xine and koffeine and some others and it still does not work... > tried it under windows xp and it works perfect, so the problem is not > the card... > but what else? > > i'm using ubuntu 6, 2.6.15-26-386 kernel, hauppauge nova-se2 > > hope anyone can help me > > thx > bye > marsellus > > ___ > 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] Artec T1 tuning problems w. 2.6.18
Tuning fails with 2.6.18 kernel, firmware gets loaded. Box is Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs) works fine with 2.6.17.13 Tuning with tzap gives: [...] tuning to 57800 Hz video pid 0x0161, audio pid 0x0162 status 00 | signal | snr | ber 001f | unc | status 04 | signal | snr | ber 001f | unc | status 04 | signal | snr | ber 001f | unc | status 04 | signal | snr | ber 001f | unc | status 04 | signal | snr | ber 001f | unc | status 04 | signal | snr | ber 001f | unc | [...] dmesg output: usb 1-1.3: new full speed USB device using ehci_hcd and address 13 usb 1-1.3: configuration #1 chosen from 1 choice dvb-usb: found a 'Artec T1 USB1.1 TVBOX with AN2235 (faulty USB IDs)' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-dibusb-an2235-01.fw' usbcore: registered new driver dvb_usb_dibusb_mb usb 1-1.1: USB disconnect, address 12 dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. usb 1-1.1: new full speed USB device using ehci_hcd and address 14 usb 1-1.1: configuration #1 chosen from 1 choice dvb-usb: found a 'DiBcom USB1.1 DVB-T reference design (MOD3000)' in warm state. dvb-usb: will use the device's hardware PID filter (table count: 16). DVB: registering new adapter (DiBcom USB1.1 DVB-T reference design (MOD3000)). DVB: registering frontend 0 (DiBcom 3000M-B DVB-T)... dibusb: This device has the Thomson Cable onboard. Which is default. input: IR-receiver inside an USB DVB receiver as /class/input/input7 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: DiBcom USB1.1 DVB-T reference design (MOD3000) successfully initialized and connected. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Flooding interrupts
On Mon, 2006-09-25 at 23:40 +0200, Hartmut Hackmann wrote: > Hi, > > Jimmy Hedman wrote: > > Hi, > > I have a Compro DVB-T 300 which uses the saa7134-dvb-driver. When it's > > tuned it is flooding my system with between 12000 and 16000 interrupts a > > second. It works, but that amout of interrupts doesn't sound healty. Any > > ideas what this could be? > > > > Many thanks in advance, > > Jimmy Hedman > > > The streaming DMA causes loads of interrupts, but not that many. > For DVB-T you should expect about 70 per sec, and for analog, its > up to 50 per sec for 50Hz systems. > The only other valid interrupt source are the GPIOs (Remote control). > If there really are so many interrupts, there must be something wrong > with the GPIO config but i don't think so. I actually have a problem with the remote! It's giving the last pressed key plus the current key every time which makes it impossible to use. The first key goes through, but all the following keys gets duplicated on the next key press. For example, if I press DOWN, DOWN, UP, LEFT, i get DOWN, DOWN+DOWN, DOWN+UP, UP+LEFT. Can I debug this in any way? // Jimmy ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cannot tune some frequences on hauppauge nova-se2
hi, i tried some other frequencies and everything works fine except some freq... don't know why... On 9/26/06, Raymond mantchala <[EMAIL PROTECTED]> wrote: Hello, I had this kind of issue with a another card. In my case the card wasn't able to tune because the handling of vertical polarization was broken. What you can do is to test all the combination of high/low frequencies and vertical/horizontal polarization. In my case, i found that each time the polarization was vertical it didn't work. hope this will help you. regars, Raymond. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Flooding interrupts
Hartmut Hackmann wrote: > Hi, > > Jimmy Hedman wrote: >> Hi, >> I have a Compro DVB-T 300 which uses the saa7134-dvb-driver. When it's >> tuned it is flooding my system with between 12000 and 16000 interrupts a >> second. It works, but that amout of interrupts doesn't sound healty. Any >> ideas what this could be? >> >> Many thanks in advance, >> Jimmy Hedman >> > The streaming DMA causes loads of interrupts, but not that many. Whether it be consistent or streaming, this has nothing to do with the interrupt count. The only case when you have too many interrupts is when your buffers are too small, causing the device requesting the host to read from the DMA buffers. > For DVB-T you should expect about 70 per sec, and for analog, its > up to 50 per sec for 50Hz systems. > The only other valid interrupt source are the GPIOs (Remote control). > If there really are so many interrupts, there must be something wrong > with the GPIO config but i don't think so. Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Problem tuning H frequencies on different DVB-S cards
Title: Problem tuning H frequencies on different DVB-S cards Hello, I've got a problem tuning on horizontal freq. on both KNC-1 and WinTV Nova SE2 cards using the latest drivers from HG tree v4l-dvb-1ec2f18a9505.tar.bz2. I have the same problem with v4l-dvb-f2a8b79d6dc0.tar.bz2 - Kernel version 2.6.17.11. (The default drivers in this kernel don't have this problem) Just fyi, the cards are OK (no polarization problems) because they are working fine with the previous kernel. (2.6.16.16) Any idea? Thanks, Atti ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
SV: SV: [linux-dvb] How do I install properly (Fedora 5 andnova-t-500)?
> -Oprindelig meddelelse- > Fra: Patrick Boettcher [mailto:[EMAIL PROTECTED] > Sendt: 26. september 2006 09:01 > Til: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; hermann pitton; linux-dvb@linuxtv.org > Emne: Re: SV: [linux-dvb] How do I install properly (Fedora 5 > andnova-t-500)? > ... > Remove everything from /lib/modules//kernel/drivers/media > > and run > > make install > > in v4l-dvb/v4l. Once I realised I also had to delete the /updates/drivers/media that did the trick:-) Thank you both for your help! Regards Thomas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Pinnacle 310i DVB-T Linux
Hi, i have an Pinnacle 310i but i don't want analoge TV! Is there an chance to get it runnning in DVB-T ? linuxtv.org means: only work analogue tv, not digital. :-( Please give a sign if anyone has a advice Thanks Mark ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital problems
Hi Mark, Not much help, but some sympathy, and some "out there" ideas. I am having similar problems in Brisbane with 9 and SBS in Brisbane, until one day they magically started working, though the PCI can be slow to lock. Given that most people that reported problems are using FC5 (both the FC5 kernels and vanilla kernels) I used a separate HDD and installed Ubuntu. It magically worked after installing a 2.6.17.?? (can't remember - I think it was the last before 2.6.18 was released) vaniall kernel, and apply Chris Pascoe's test branch drivers (see below). Strange, but even stranger was when I put back my old HDD with fedora, it magically worked as well! The only possible explanation (however implausable) is that the case was somehow acting as an antenna for the signal/noise (i.e. the case was off), which was killing the signal. If anyone has a better suggestion, I'm all ears. But now, the case is back on and it's still reasonable... though the PCI can be quite slow to lock at times. A friend of mine, also with a dual digital, experiences the same problem under FC5, though he is debating whether it's a signal strength issue or not. I have very good signal strength in windows too. There is a way around the 16667Hz offset problem - Chris Pascoe's repository has an experimental driver version to fix the divider error what causes the need for the 16667Hz offset. Follow the mercurial instructions, except change the hg branch to the following: hg clone http://linuxtv.org/hg/~pascoe/v4l-dvb-test/ And this will at least fix the offset. You will probably get an error compiling complaining about dependencies dst(ca) or something like that. Just make install anyway and it will install the drivers. Out of curiorsity, when trying to lock, do you get a lot of kernel messages saying something like: cx88 timeout or similar? That's what I am getting when it is failing to tune. Let us know if you have any luck, and if you do have a spare HDD kicking around somewhere, try Ubuntu or something else and see if that works - I have no idea why mine suddenly started working (not that I am complaining!). I have no idea why the distro would have any bearing if you are using a vanilla kernel, but I am grasping at straws here myself... Cheers Damien. Kielogl wrote: Just added a new DViCO FusionHDTV DVB-T Dual Digital tuner card for MythTV on FC5 and have come across some problems. The card seems to be initializing ok, as per dmesg | grep -i dvb: cx2388x dvb driver version 0.0.6 loaded CORE cx88[0]: subsystem: 18ac:db50, board: DViCO FusionHDTV DVB-T Dual Digital [card=44,autodetected] cx88[0]/2: cx2388x based dvb card DVB: registering new adapter (cx88[0]). DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)... dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in cold state, will try to load a firmware dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw' usbcore: registered new driver dvb_usb_cxusb dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual USB). DVB: registering frontend 1 (Zarlink ZL10353 DVB-T)... input: IR-receiver inside an USB DVB receiver as /class/input/input2 dvb-usb: schedule remote query interval to 150 msecs. dvb-usb: DViCO FusionHDTV DVB-T Dual USB successfully initialized and connected. I am using the current FC5 kernel, 2.6.17-1.2187_FC5, and last built v4l-dvb from the mercurial source at linuxtv.org earlier this week (24 Sept 2006). Both receivers initially work fine in MythTV, except the PCI receiver is not able to receive the SBS channel here in Melbourne, Australia. SBS works fine on the USB receiver. (To get SBS and channel Nine to work at all, I had to add the +17Hz offset to the channel frequency, as per http://www.linuxtv.org/pipermail/linux-dvb/2006-July/011623.html.) It seemed like a signal strength problem with the SBS channel, as lock can be slow and frame updates are delayed/pixelated/corrupt. However, I tried the card/antenna in a WinXP machine and all channels are received perfectly. The Windows receiver app shows the signal strength is 100% for all channels: ABC - 100% (29.1dB) Seven - 100% (30.1dB) Nine - 100% (30.6dB) Ten - 100% (29.0dB) SBS - 100% (25.3dB) After working ok initially for anywhere up to a day or so (except for SBS on PCI), the second problem happens. The USB receiver suddenly stops working and syslog is flooded with "bulk message failed" messages: dvb-usb: recv bulk message failed: -71 dvb-usb: bulk message failed: -32 (1/0) last message repeated 14 times dvb-usb: bulk message failed: -32 (1/0) last message repeated 19 times dvb-usb: bulk message failed: -32 (1/0) last message repeated 20 times ... If I just reboot, the /dev/dvb/adapter
[linux-dvb] pctv452e driver second try
Yeeha, Attached patch (mp-stb0899 tree snapshot version 2dcc2689f994 again) enables support for: "Pinnacle PCTV HDTV Sat Pro USB" (short: "PCTV452e") - DVB-S only. (TODO: DVB-S2) - 0/13/18 Volt ok - diseqc works - tested with symrates 27500 and 22000 - continuos/burst tone (22kHz) not tested - some parts are hacked to DVB-S - legacy ioctl FE_SET_FRONTEND not supported, use DVBFE_SET_PARAMS. - reading sections and watching tv works, so all should work. This stuff comes with no warranty, if you trash some or all of your equipment its your problem ;-) Dominik my_pctv452e_dvbs_ok.patch.bz2 Description: BZip2 compressed data ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital problems
Kielogl wrote: > Just added a new DViCO FusionHDTV DVB-T Dual Digital tuner card for MythTV on > FC5 and have come across some problems. The card seems to be initializing ok, > as per dmesg | grep -i dvb: > > cx2388x dvb driver version 0.0.6 loaded > CORE cx88[0]: subsystem: 18ac:db50, board: DViCO FusionHDTV DVB-T Dual > Digital [card=44,autodetected] > cx88[0]/2: cx2388x based dvb card > DVB: registering new adapter (cx88[0]). > DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)... > dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in cold state, will try to > load a firmware > dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw' > usbcore: registered new driver dvb_usb_cxusb > dvb-usb: generic DVB-USB module successfully deinitialized and disconnected. > dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in warm state. > dvb-usb: will pass the complete MPEG2 transport stream to the software > demuxer. > DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual USB). > DVB: registering frontend 1 (Zarlink ZL10353 DVB-T)... > input: IR-receiver inside an USB DVB receiver as /class/input/input2 > dvb-usb: schedule remote query interval to 150 msecs. > dvb-usb: DViCO FusionHDTV DVB-T Dual USB successfully initialized and > connected. > > I am using the current FC5 kernel, 2.6.17-1.2187_FC5, and last built v4l-dvb > from the mercurial source at linuxtv.org earlier this week (24 Sept 2006). > > Both receivers initially work fine in MythTV, except the PCI receiver is not > able to receive the SBS channel here in Melbourne, Australia. SBS works fine > on the USB receiver. (To get SBS and channel Nine to work at all, I had to > add the +17Hz offset to the channel frequency, as per > http://www.linuxtv.org/pipermail/linux-dvb/2006-July/011623.html.) > > It seemed like a signal strength problem with the SBS channel, as lock can be > slow and frame updates are delayed/pixelated/corrupt. However, I tried the > card/antenna in a WinXP machine and all channels are received perfectly. The > Windows receiver app shows the signal strength is 100% for all channels: > > ABC - 100% (29.1dB) > Seven - 100% (30.1dB) > Nine - 100% (30.6dB) > Ten - 100% (29.0dB) > SBS - 100% (25.3dB) > > After working ok initially for anywhere up to a day or so (except for SBS on > PCI), the second problem happens. The USB receiver suddenly stops working and > syslog is flooded with "bulk message failed" messages: > > dvb-usb: recv bulk message failed: -71 > dvb-usb: bulk message failed: -32 (1/0) > last message repeated 14 times > dvb-usb: bulk message failed: -32 (1/0) > last message repeated 19 times > dvb-usb: bulk message failed: -32 (1/0) > last message repeated 20 times > ... > > If I just reboot, the /dev/dvb/adapter1/* devices are missing. The only way I > can get it working again is by shutting down the system, and pulling the > power before restarting, so the firmware for the USB receiver is reloaded. > > Would much appreciate any advice on how to get some stability back with the > new card's USB receiver and on the SBS channel reception for the PCI receiver. > AFAIK, These problems have all been fixed in our development tree hosted on linuxtv.org ... You have to change around some #ifdef kernel version tests in the code if you want it to build correctly against fc5's backported 2.6.18 kernel, (which reports itself as 2.6.17). For info, see: http://linuxtv.org/repo There was an email recently on the list that explains what code needs to be changed to make it work on FC5, but an easier way to install those modules would be using ATrpms ... just do: yum install video4linux-kmdl-`uname -r` ...after a reboot, you should be all fixed. Cheers, Mike ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] TwinhanDTV Mantis drivers
Is there still active developement on the mantis driver for TwinhanDTV 2033 and others? In April and July there were some discussion here, and the mails from the developer seemed pretty positive. The reason I'm asking, is that I bought the card today after the salesman said it would be supported in Linux. I can ofcourse take the card back. If the driver is still being developed when can I espect to have some code to test? I'm not asking for a date or anything, just an estimate like in weeks/months/"when ever I have time". -Riku ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] MSI Megasky 580 using Uli m9206 -- http://linuxtv.org/hg/~mkrufky/m920x
Patrick, Could you look over the changesets in this tree and let me know whether or not you approve of this? Aapo, After you sent your patch in to the linux-dvb mailing list, Patrick had some comments and requests for certain things to be cleaned up. I have not seen any response from you about those requests. In an effort to move things along, I have taken it upon myself to clean up your patch. I've updated it to comply with some of the recent changes in the dvb-usb structure, and to use the new dvb_attach() method. I have also separated the qt1010 tuner code into a separate header file. It has come to my attention, thanks to Markus Rechberger, that there may be more fixing to do with regards to the qt1010 stuff... but that can be done later, in a separate patch. I'd like it if you could test the updated tree and confirm that it works as expected with your device. Please clone the following tree: http://linuxtv.org/hg/~mkrufky/m920x You will notice that I have decided to rename the driver from megasky to m920x -- I did this for a few reasons: 1) There are probably other devices out there based on the m9205, m9206 and m9207 chipsets ... Adding support for those devices will probably be a matter of updating the code in this driver, in which case, the name 'megasky' may be inappropriate. 2) There is another device out there, called "MSI Megasky 580", based on the gl861 chipset, using the same exact usb id as your device based on the m9206 chipset. This means that MSI released two completely different devices, each with the same exact name and USB ID! 3) We should name the driver based on the chipset it uses, rather than the Vendor's retail name of the product. Please let me know what happens. Regards, Michael Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] RE: Strange problem with Vision DTV-CI (1030A)
Is some body have such problem or not? Also is some body have such DVB-S like me please test it. May be i do something wrong. I think it can`t be realyy standart DVB-S tuner work okey but all 5 PC tuners some times read errors :( -- Евгений Бендяк ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Hauppauge WinTV NOVA T USB2 not working any more
I've tried the patch you sent to the mailing list but there is no difference. Reading the code it seems to me that the problem is into the value of "agc->setup" If I revert changes to dib3000mc_setup_pwm_state (and I do not apply the patch) the card works again. It looks to me (just reading the code, no idea of what the values mean) that the value stored in agc->setup is now used twice. 1) in dib3000mc_init (register 37) 2) in dib3000mc_setup_pwm_state (reg_52) in the new version of the code the same value is shared for those 2 purposes, while in the old code the 2 functions used different values. If I am not wrong, with the latest patch dib3000mc_setup_pwm_state gets the same values af before wihle dib3000mc_init does not. I don't know whether it makes sense but in my case it matters. Any idea? Hi, Mario, can you please try the attached patch and see, if this fixes your problem ? Thanks Jose for finding it. I knew I would forget this thing when changing the set_pwm-function... Sorry, Patrick. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: dvb-t hdtv trials in the uk?
I used the following scan file to scan for HDTV signals T 55400 8MHz 2/3 1/2 QPSK 8k 1/32 NONE It is not working anymore now, but instead I use T 55400 8MHz 2/3 1/2 QAM_64 8k 1/32 NONE (which btw does not give any more the full list) I'm not sure what is the problem, maybe is the card. Anyway, those are the channels I could scan BBC HD1a:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:1502:1505:36932 BBC HD1b:554167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:1502:1505:36932 ITV HD Triala:522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:161:162:41029 Ch4 HD Triala:522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:181:182:41152 five HD Triala:522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:201:202:41168 ITV HD Trialb:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:161:162:41029 Ch4 HD Trialb:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:181:182:41152 five HD Trialb:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:201:202:41168 You need to manually set the video pid since it is not MPEG2 but H262 and scan does not like it. If you read the mailing list in the last 4/5 months you should find somehting on how to play those signals. MPlayer is fooled by the fact that the video is not MPEG2 but H262 (which it does not expects), there was a patch to manually specify the codec. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] HDTV tuning.
Hi how should I interpret the output of scan, trying to scan for HDTV in London? initial scan file T 55400 8MHz 2/3 2/3 QAM64 8k 1/32 NONE (I had found those values in this mailing list some months ago) output: scanning /opt/dvb/uk-CrystalPalace using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 55400 0 2 2 3 1 0 0 tune to: 55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE tuning status == 0x0f tuning status == 0x1f PAT PMT 0x0258 for service 0x9044 SDT (actual TS) 0x 0x9044: pmt_pid 0x0258 BBC -- BBC HD1 (running) NIT (actual TS) Network Name 'Crystal Palace B' tune to: 554167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE tuning status == 0x07 tuning status == 0x1f PAT PMT 0x0258 for service 0x9044 SDT (actual TS) 0x9004 0x9044: pmt_pid 0x0258 BBC -- BBC HD1 (running) NIT (actual TS) Network Name 'Crystal Palace B' tune to: 522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 WARNING: >>> tuning failed!!! tune to: 522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 tuning status == 0x05 WARNING: >>> tuning failed!!! dumping lists (2 services) BBC HD1:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:36932 BBC HD1:554167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:36932 Done. Whet it says "WARNING: tuning failed" what does it mean? Where does it get the frequency 522167000? If it is given by the initial trasponder, why is it empty? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV tuning.
Le Mardi 26 Septembre 2006 21:03, Mario Rossi a écrit : > Hi > > how should I interpret the output of scan, trying to scan for HDTV in > London? > > initial scan file > > T 55400 8MHz 2/3 2/3 QAM64 8k 1/32 NONE > > (I had found those values in this mailing list some months ago) > > output: > > scanning /opt/dvb/uk-CrystalPalace > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > initial transponder 55400 0 2 2 3 1 0 0 > > >>> tune to: > >>> 55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMI > >>>SSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE tuning status == 0x0f > >>> tuning status == 0x1f > > PAT > PMT 0x0258 for service 0x9044 > SDT (actual TS) > 0x 0x9044: pmt_pid 0x0258 BBC -- BBC HD1 (running) > NIT (actual TS) > Network Name 'Crystal Palace B' > > >>> tune to: > >>> 554167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMI > >>>SSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE tuning status == 0x07 > >>> tuning status == 0x1f > > PAT > PMT 0x0258 for service 0x9044 > SDT (actual TS) > 0x9004 0x9044: pmt_pid 0x0258 BBC -- BBC HD1 (running) > NIT (actual TS) > Network Name 'Crystal Palace B' > > >>> tune to: > >>> 522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISS > >>>ION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > > WARNING: >>> tuning failed!!! > > >>> tune to: > >>> 522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISS > >>>ION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE > > (tuning failed) > > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > >>> tuning status == 0x05 > > WARNING: >>> tuning failed!!! > dumping lists (2 services) > BBC > HD1:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMI >SSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:36932 BBC > HD1:554167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMI >SSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:36932 Done. > > Whet it says "WARNING: tuning failed" what does it mean? It means "tuning failed" :) > Where does it get the frequency 522167000? From the Network Information Table (NIT) that is supposed to give a list of available mplex on that network. > If it is given by the initial trasponder, why is it empty? Well, NIT with wrong/outdated infos are very common through all networks (s,c,t) ;) -- Christophe Thommeret ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] advanced LNB power features
Hi, Just got inspired by LNBP21 and LNBP22 features: Are there any plans to support fancy LNB power features like: - Current limit selection (e.g. switchable to 350mA or 450mA limit) - Short circuit detection - Short circuit handling (eg.: limit current to max, or do PWM like limitation) There are only two function pointer in dvb_frontend_ops which handle LNB power. The new options would require at least one more. The most flexible way would be a generic "set_lnb_power_feature" function. Don't know whether someone needs this but you'll never know:-) Any comments are welcome, Dominik ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV tuning.
Hi, > > how should I interpret the output of scan, trying to scan for HDTV in > > London? > > > > initial scan file > > > > T 55400 8MHz 2/3 2/3 QAM64 8k 1/32 NONE These settings are correct and doing dvbscan from the command-line myself works, so I have to ask what is your aerial setup like and how far are you from the transmitter? You are aware that the HD trial in London is using a low-power transmitter intended to only be receivable inside the north and south circular road (though people as far afield have reported receiving it). Also might I recommend using a recent CVS of Kaffeine. It's able to scan and find the HD trial channels, and can easily record them too (it does a much better job of recording ITV/Ch4/five than VLC does). You can't watch the video (hint, hint Christophe), but sound works. > > Where does it get the frequency 522167000? > > From the Network Information Table (NIT) that is supposed to give a list of > available mplex on that network. That's right and it's also the frequency for the ITV/Ch4/five multiplex. Just for your info, below is my output from dvbscan. Regards, Soyeb # dvbscan uk-CrystalPalace -a 1 scanning uk-CrystalPalace using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' initial transponder 55400 0 2 1 0 1 0 0 >>> tune to: 55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE 0x 0x9044: pmt_pid 0x0258 BBC -- BBC HD1 (running) Network Name 'Crystal Palace B' >>> tune to: 554167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE 0x 0x9044: pmt_pid 0x0258 BBC -- BBC HD1 (running) Network Name 'Crystal Palace B' >>> tune to: 522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE 0x 0xa045: pmt_pid 0x00a0 ITV -- ITV HD Trial (running) 0x 0xa0c0: pmt_pid 0x00b4 Channel 4 -- Ch4 HD Trial (running) 0x 0xa0d0: pmt_pid 0x00c8 Channel 5 -- five HD Trial (running) Network Name 'Crystal Palace B' >>> tune to: 52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE 0x 0xa045: pmt_pid 0x00a0 ITV -- ITV HD Trial (running) 0x 0xa0c0: pmt_pid 0x00b4 Channel 4 -- Ch4 HD Trial (running) 0x 0xa0d0: pmt_pid 0x00c8 Channel 5 -- five HD Trial (running) Network Name 'Crystal Palace B' dumping lists (8 services) BBC HD1:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:36932 BBC HD1:554167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:36932 ITV HD Trial:522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:162:41029 Ch4 HD Trial:522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:182:41152 five HD Trial:522167000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:202:41168 ITV HD Trial:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:162:41029 Ch4 HD Trial:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:182:41152 five HD Trial:52200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:202:41168 Done. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle 310i DVB-T Linux
Hi, Mark Mark Schwarz wrote: Hi, i have an Pinnacle 310i but i don't want analoge TV! Is there an chance to get it runnning in DVB-T ? linuxtv.org means: only work analogue tv, not digital. :-( Please give a sign if anyone has a advice We had a preliminary patch. Unfortunately, it no longer applies. I intend to add support for this card very soon. Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV tuning.
> T 55400 8MHz 2/3 2/3 QAM64 8k 1/32 NONE I can only scan if I set QAM64 not QPSK (which worked 3/4 months ago when I tried the first time). Since then, I moved, before I was in Victoria and I used a T cable aerial (the one that is often sold for FM radios), while now I live in Aldgate East and I use the aerial of the building. Maybe I was closer to the transmitter before and now there is not enough power to get the signal. I've tried kaffeine 0.8.2 but scanning both for AUTO and uk-CrystalPalace only finds 8 TVs and 1 Radio, while scan (from dvb-apps) finds many channels (and BBC HD1). How do you tell kaffeine to scan for HDTV? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Flooding interrupts
Hi, Manu Abraham wrote: Hartmut Hackmann wrote: Hi, Jimmy Hedman wrote: Hi, I have a Compro DVB-T 300 which uses the saa7134-dvb-driver. When it's tuned it is flooding my system with between 12000 and 16000 interrupts a second. It works, but that amout of interrupts doesn't sound healty. Any ideas what this could be? Many thanks in advance, Jimmy Hedman The streaming DMA causes loads of interrupts, but not that many. Whether it be consistent or streaming, this has nothing to do with the interrupt count. The only case when you have too many interrupts is when your buffers are too small, causing the device requesting the host to read from the DMA buffers. For DVB-T you should expect about 70 per sec, and for analog, its up to 50 per sec for 50Hz systems. The only other valid interrupt source are the GPIOs (Remote control). If there really are so many interrupts, there must be something wrong with the GPIO config but i don't think so. The buffer size for DVB is fixed, at 14MBit it gives the number of buffer full IRQs i mentioned above (70 per sec). For analog, its easier. The buffers always hold fields / frames. I forgot the sound DMA buffers, which give about 32 IRQs per sec. So the streaming causes about 150 IRQs per second if everything is running. Hartmut ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV tuning.
OK, I've tried again changing aerial (I was suign the FM signal, now TV). It does not matter for watching (same quality) but kaffeine cannot scan properly using the former. Anyway, no way to scan or tune Channel 4, ITV or five HDTV. BBC HD1 works, but it seems that my laptop if too slow: mplayer keeps saying that it is using 400% of the CPU and image goes very slow. VLC does not work properly, only the first frame and then those errors libdvbpsi error (PSI decoder): TS duplicate (received 0, expected 1) for PID 0 libdvbpsi error (PSI decoder): TS duplicate (received 0, expected 1) for PID 100 libdvbpsi error (PSI decoder): TS duplicate (received 0, expected 1) for PID 0 libdvbpsi error (PSI decoder): TS duplicate (received 0, expected 1) for PID 100 What is the status of the art for HDTV? On 9/26/06, Mario Rossi <[EMAIL PROTECTED]> wrote: > > T 55400 8MHz 2/3 2/3 QAM64 8k 1/32 NONE I can only scan if I set QAM64 not QPSK (which worked 3/4 months ago when I tried the first time). Since then, I moved, before I was in Victoria and I used a T cable aerial (the one that is often sold for FM radios), while now I live in Aldgate East and I use the aerial of the building. Maybe I was closer to the transmitter before and now there is not enough power to get the signal. I've tried kaffeine 0.8.2 but scanning both for AUTO and uk-CrystalPalace only finds 8 TVs and 1 Radio, while scan (from dvb-apps) finds many channels (and BBC HD1). How do you tell kaffeine to scan for HDTV? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: %5Blinux-dvb%5D%20Twinhan%20Cab%2FCI%202031%3A%20frontend%20entry%20sometimes%20missing
Manu Abraham wrote: Zoilo Gomez wrote: Hi Marcus, The problems with 2031 were unfortunately never fixed. IIRC we were left with the following problems: 1) tuner device sometimes missing in /dev/dvb/adapterX/ on boot (app. 20% of the boots, tested on 2 different machines) 2) needed to tune twice in case of freq change; the first time would almost never give a lock (but sometimes it did strangely enough) 3) unstable signal, where signal would be lost after some time (hours); this problem I never investigated thoroughly, because of 1) and 2) which needed a solution first <> http://linuxtv.org/hg/v4l-dvb?f=4f65bdd94527;file=linux/drivers/media/dvb/bt8xx/dst.c;style=gitweb at line #1648, does adding a msleep(20) or something around that order help ? for your problem (2) mentioned for (1) try using dst_addons=0x20 as module parameter. You will need this patch as well (for fixing the dvb-attach). Apply this patch first http://article.gmane.org/gmane.linux.drivers.dvb/27792/match= Alongwith one of the previous patches, commenting out one line for DCT-CI cards Unfortunately using dst_addons=0x20 for problem (1) does not seem to help. I dug up 2 of my 2031 cards, and put them in a machine. First time after boot, both cards did show a tuner; but the second time the tuner of adapter0 failed as follows: /dev/dvb/ /dev/dvb/adapter1 /dev/dvb/adapter1/frontend0 /dev/dvb/adapter1/ca0 /dev/dvb/adapter1/net0 /dev/dvb/adapter1/dvr0 /dev/dvb/adapter1/demux0 /dev/dvb/adapter0 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/demux0 Here is how I loaded my modules: dvb_core dvb_shutdown_timeout=0 bttv i2c_hw=1 card=0x71 bt878 dst verbose=5 dst_addons=0x20 dst_ca dvb-bt8xx Relevant part of dmesg: Linux video capture interface: v2.00 bttv: driver version 0.9.16 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). ACPI: PCI Interrupt :00:09.0[A] -> GSI 17 (level, low) -> IRQ 16 bttv0: Bt878 (rev 17) at :00:09.0, irq: 16, latency: 32, mmio: 0xef00 bttv0: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID is 1822:0001 bttv0: using: Twinhan DST + clones [card=113,insmod option] bttv0: gpio: en=, out= in=00f100fd [init] bttv0: using tuner=4 bttv0: add subdevice "dvb0" bttv: Bt8xx card found (1). ACPI: PCI Interrupt :00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18 bttv1: Bt878 (rev 17) at :00:0a.0, irq: 18, latency: 32, mmio: 0xee00 bttv1: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID is 1822:0001 bttv1: using: Twinhan DST + clones [card=113,autodetected] bttv1: gpio: en=, out= in=00f100fd [init] bttv1: using tuner=4 bttv1: add subdevice "dvb1" bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). ACPI: PCI Interrupt :00:09.1[A] -> GSI 17 (level, low) -> IRQ 16 bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB functions. bt878(0): Bt878 (rev 17) at 00:09.1, irq: 16, latency: 32, memory: 0xee80 bt878: Bt878 AUDIO function found (1). ACPI: PCI Interrupt :00:0a.1[A] -> GSI 18 (level, low) -> IRQ 18 bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB functions. bt878(1): Bt878 (rev 17) at 00:0a.1, irq: 18, latency: 32, memory: 0xed80 DVB: registering new adapter (bttv0). dst(0) rdc_8820_reset: Resetting DST dst(0) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[] dst(0) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[0004] dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 00 06 00 00 00 00 00 fa ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 1 dst(0) read_dst: reply is 0x0 0x44 0x43 0x54 0xd 0x43 0x49 0x6c dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) dst_get_device_id: Checksum failure! dst(0) dst_probe: unknown device. frontend_init: Could not find a Twinhan DST. dvb-bt8xx: A frontend driver was not found for device 109e/0878 subsystem 1822/0001 DVB: registering new adapter (bttv1). dst(1) rdc_8820_reset: Resetting DST dst(1) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[] dst(1) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[0004] dst(1) dst_comm_init: Initializing DST. dst(1) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(1) rdc_reset_state: Resetting state machine dst(1) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(1) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 00 06 00 00 00 00 00 fa ] dst(1) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(1) read_dst: reply is 0xff dst(1) dst_wait_dst_ready: dst wait ready after 1 dst(1) read_dst:
Re: [linux-dvb] Re: %5Blinux-dvb%5D%20Twinhan%20Cab%2FCI%202031%3A%20frontend%20entry%20sometimes%20missing
Zoilo Gomez wrote: > Manu Abraham wrote: > >> Zoilo Gomez wrote: >> >> >>> Hi Marcus, >>> >>> The problems with 2031 were unfortunately never fixed. IIRC we were left >>> with the following problems: >>> 1) tuner device sometimes missing in /dev/dvb/adapterX/ on boot (app. >>> 20% of the boots, tested on 2 different machines) >>> 2) needed to tune twice in case of freq change; the first time would >>> almost never give a lock (but sometimes it did strangely enough) >>> 3) unstable signal, where signal would be lost after some time (hours); >>> this problem I never investigated thoroughly, because of 1) and 2) which >>> needed a solution first >>> > <> > >> http://linuxtv.org/hg/v4l-dvb?f=4f65bdd94527;file=linux/drivers/media/dvb/bt8xx/dst.c;style=gitweb >> >> >> at line #1648, does adding a msleep(20) or something around that order >> help ? for your problem (2) mentioned >> for (1) try using dst_addons=0x20 as module parameter. >> >> You will need this patch as well (for fixing the dvb-attach). Apply this >> patch first >> http://article.gmane.org/gmane.linux.drivers.dvb/27792/match= >> >> Alongwith one of the previous patches, commenting out one line for >> DCT-CI cards >> >> >> >> > > Unfortunately using dst_addons=0x20 for problem (1) does not seem to help. > > I dug up 2 of my 2031 cards, and put them in a machine. First time after > boot, both cards did show a tuner; but the second time the tuner of > adapter0 failed as follows: > >> /dev/dvb/ >> /dev/dvb/adapter1 >> /dev/dvb/adapter1/frontend0 >> /dev/dvb/adapter1/ca0 >> /dev/dvb/adapter1/net0 >> /dev/dvb/adapter1/dvr0 >> /dev/dvb/adapter1/demux0 >> /dev/dvb/adapter0 >> /dev/dvb/adapter0/dvr0 >> /dev/dvb/adapter0/net0 >> /dev/dvb/adapter0/demux0 >> >> > > Here is how I loaded my modules: > >> dvb_core dvb_shutdown_timeout=0 >> bttv i2c_hw=1 card=0x71 >> bt878 >> dst verbose=5 dst_addons=0x20 >> dst_ca >> dvb-bt8xx >> >> > > Relevant part of dmesg: > >> Linux video capture interface: v2.00 >> bttv: driver version 0.9.16 loaded >> bttv: using 8 buffers with 2080k (520 pages) each for capture >> bttv: Bt8xx card found (0). >> ACPI: PCI Interrupt :00:09.0[A] -> GSI 17 (level, low) -> IRQ 16 >> bttv0: Bt878 (rev 17) at :00:09.0, irq: 16, latency: 32, mmio: >> 0xef00 >> bttv0: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID >> is 1822:0001 >> bttv0: using: Twinhan DST + clones [card=113,insmod option] >> bttv0: gpio: en=, out= in=00f100fd [init] >> bttv0: using tuner=4 >> bttv0: add subdevice "dvb0" >> bttv: Bt8xx card found (1). >> ACPI: PCI Interrupt :00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18 >> bttv1: Bt878 (rev 17) at :00:0a.0, irq: 18, latency: 32, mmio: >> 0xee00 >> bttv1: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID >> is 1822:0001 >> bttv1: using: Twinhan DST + clones [card=113,autodetected] >> bttv1: gpio: en=, out= in=00f100fd [init] >> bttv1: using tuner=4 >> bttv1: add subdevice "dvb1" >> bt878: AUDIO driver version 0.0.0 loaded >> bt878: Bt878 AUDIO function found (0). >> ACPI: PCI Interrupt :00:09.1[A] -> GSI 17 (level, low) -> IRQ 16 >> bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB >> functions. >> bt878(0): Bt878 (rev 17) at 00:09.1, irq: 16, latency: 32, memory: >> 0xee80 >> bt878: Bt878 AUDIO function found (1). >> ACPI: PCI Interrupt :00:0a.1[A] -> GSI 18 (level, low) -> IRQ 18 >> bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB >> functions. >> bt878(1): Bt878 (rev 17) at 00:0a.1, irq: 18, latency: 32, memory: >> 0xed80 >> DVB: registering new adapter (bttv0). >> dst(0) rdc_8820_reset: Resetting DST >> dst(0) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[] >> dst(0) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[0004] >> dst(0) dst_comm_init: Initializing DST. >> dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] >> dst(0) rdc_reset_state: Resetting state machine >> dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] >> dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] >> writing [ 00 06 00 00 00 00 00 fa ] >> dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] >> dst(0) read_dst: reply is 0xff >> dst(0) dst_wait_dst_ready: dst wait ready after 1 >> dst(0) read_dst: reply is 0x0 >> 0x44 0x43 0x54 0xd 0x43 0x49 0x6c >> dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] >> dst(0) dst_get_device_id: Checksum failure! >> dst(0) dst_probe: unknown device. >> frontend_init: Could not find a Twinhan DST. >> dvb-bt8xx: A frontend driver was not found for device 109e/0878 >> subsystem 1822/0001 >> DVB: registering new adapter (bttv1). >> dst(1) rdc_8820_reset: Resetting DST >> dst(1) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[] >> dst(1) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[0004] >> dst(1) dst_comm_init: Initializing DST. >> dst(1) dst_gpio_outb: mask=[], enbb=[0001], outh
[linux-dvb] Error building latest sources
Ho humm... I just grabbed the latest sources amd tried to build them # hg clone http://linuxtv.org/hg/v4l-dvb # cd v4l-dvb # make The compilation fails with In file included from /home/mark/v4l-dvb/v4l/cpia2_v4l.c:42: /home/mark/v4l-dvb/v4l/cpia2.h:408: error: field 'vp' has incomplete type /home/mark/v4l-dvb/v4l/cpia2.h:409: error: field 'vw' has incomplete type /home/mark/v4l-dvb/v4l/cpia2_v4l.c:91:2: error "VID_HARDWARE_CPIA2 should have been defined in linux/videodev.h" / ... plus more. Where should I be looking to fix this (and is the hg command above the right one to use to grab the sources?) Cheers Mark smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV tuning.
> Since then, I moved, before I was in Victoria and I used a T cable > aerial (the one that is often sold for FM radios), while now I live in > Aldgate East and I use the aerial of the building. With a decent aerial you should easily be able to get the signal from Aldgate East. I live in North East Hackney which is even further and my signal is fine. That said, I'm on top of a hill and I have a roof mounted aerial all to myself. > Maybe I was closer to the transmitter before and now there is not > enough power to get the signal. The signal is strong enough, you just need a capable aerial. Have you tried a set-top/indoor aerial? Just get a cheap one for a couple of quid and give it a try. It'll give you an idea if the buildings aerial is dud. > I've tried kaffeine 0.8.2 but scanning both for AUTO and > uk-CrystalPalace only finds 8 TVs and 1 Radio, while scan (from > dvb-apps) finds many channels (and BBC HD1). > > How do you tell kaffeine to scan for HDTV? DVB->Configure DVB->DVB Device set to auto, then go back to the scan page and Kaffeine should scan all frequencies without an initial tuning file. As for watching DVB, don't expect to watch it live, I don't think a computer is commonly available that is powerful enough to decode the signals in real-time. I record them, reencode to XviD, and then play that. It's long-winded, takes time (about 12hours per hour of recording), but it can be worth it :) BBC's natural history program Planet Earth looks particularly good, and they're due to start broadcasting Galapagos on Friday which looks to be even better. Regards, Soyeb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV tuning.
On 26 Sep 2006, at 22:34, Mario Rossi wrote: > T 55400 8MHz 2/3 2/3 QAM64 8k 1/32 NONE I can only scan if I set QAM64 not QPSK (which worked 3/4 months ago when I tried the first time). Since then, I moved, before I was in Victoria and I used a T cable aerial (the one that is often sold for FM radios), while now I live in Aldgate East and I use the aerial of the building. Not much luck here in N7 (Holloway road) using the signal from the buildings aerials. [EMAIL PROTECTED] src]# ./linuxtv-dvb-apps-1.1.1/util/scan/scan -5 hdtv3.conf scanning hdtv3.conf using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 55400 0 2 2 3 1 0 0 >>> tune to: 55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMIS SION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: >>> tuning failed!!! >>> tune to: 55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMIS SION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: >>> tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. I am suspecting this might be due to me using the wall socket signal though, since in order to receive dvb-t services, I have to manually put different frequency information into my vdr channel.conf file. Am assuming it has to do with missing repeater amplifiers for anything but the standard uk television channels. What kind of antenna would be required to receive these signals? -- Torgeir Veimo [EMAIL PROTECTED] ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Advice: which DVB-S card to buy?
Manu Abraham wrote: Rudy Zijlstra wrote: Dear, I'll be extending my setup with a new DVB-S card. As DVB-S2 is being used more and more, it seems a pity not to include DVB-S2 capability. The driver is still not complete yet. In pre-alpha state. Any idea on when it would reach alpha state? Which DVB-S2 card is currently best supported, and from which tree? Can anyone share experience? Once done , most of the cards should be supported, (card support should be trivial) won't make much of a difference though. But need to fix some more things in there Which one(s) are you using for development? Thanks, Rudy Manu ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] HDTV tuning.
> I am suspecting this might be due to me using the wall socket signal > though, since in order to receive dvb-t services, I have to manually > put different frequency information into my vdr channel.conf file. Am > assuming it has to do with missing repeater amplifiers for anything > but the standard uk television channels. > > What kind of antenna would be required to receive these signals? The HD trials run on standard UK frequencies. An aerial that can receive normal dvb-t channels should be able to get the HD channels subject to having a strong enough signal. Soyeb ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Re: %5Blinux-dvb%5D%20Twinhan%20Cab%2FCI%202031%3A%20frontend%20entry%20sometimes%20missing
Manu Abraham wrote: Zoilo Gomez wrote: Manu Abraham wrote: Zoilo Gomez wrote: Hi Marcus, The problems with 2031 were unfortunately never fixed. IIRC we were left with the following problems: 1) tuner device sometimes missing in /dev/dvb/adapterX/ on boot (app. 20% of the boots, tested on 2 different machines) 2) needed to tune twice in case of freq change; the first time would almost never give a lock (but sometimes it did strangely enough) 3) unstable signal, where signal would be lost after some time (hours); this problem I never investigated thoroughly, because of 1) and 2) which needed a solution first <> http://linuxtv.org/hg/v4l-dvb?f=4f65bdd94527;file=linux/drivers/media/dvb/bt8xx/dst.c;style=gitweb at line #1648, does adding a msleep(20) or something around that order help ? for your problem (2) mentioned for (1) try using dst_addons=0x20 as module parameter. You will need this patch as well (for fixing the dvb-attach). Apply this patch first http://article.gmane.org/gmane.linux.drivers.dvb/27792/match= Alongwith one of the previous patches, commenting out one line for DCT-CI cards Unfortunately using dst_addons=0x20 for problem (1) does not seem to help. I dug up 2 of my 2031 cards, and put them in a machine. First time after boot, both cards did show a tuner; but the second time the tuner of adapter0 failed as follows: /dev/dvb/ /dev/dvb/adapter1 /dev/dvb/adapter1/frontend0 /dev/dvb/adapter1/ca0 /dev/dvb/adapter1/net0 /dev/dvb/adapter1/dvr0 /dev/dvb/adapter1/demux0 /dev/dvb/adapter0 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/demux0 Here is how I loaded my modules: dvb_core dvb_shutdown_timeout=0 bttv i2c_hw=1 card=0x71 bt878 dst verbose=5 dst_addons=0x20 dst_ca dvb-bt8xx Relevant part of dmesg: Linux video capture interface: v2.00 bttv: driver version 0.9.16 loaded bttv: using 8 buffers with 2080k (520 pages) each for capture bttv: Bt8xx card found (0). ACPI: PCI Interrupt :00:09.0[A] -> GSI 17 (level, low) -> IRQ 16 bttv0: Bt878 (rev 17) at :00:09.0, irq: 16, latency: 32, mmio: 0xef00 bttv0: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID is 1822:0001 bttv0: using: Twinhan DST + clones [card=113,insmod option] bttv0: gpio: en=, out= in=00f100fd [init] bttv0: using tuner=4 bttv0: add subdevice "dvb0" bttv: Bt8xx card found (1). ACPI: PCI Interrupt :00:0a.0[A] -> GSI 18 (level, low) -> IRQ 18 bttv1: Bt878 (rev 17) at :00:0a.0, irq: 18, latency: 32, mmio: 0xee00 bttv1: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID is 1822:0001 bttv1: using: Twinhan DST + clones [card=113,autodetected] bttv1: gpio: en=, out= in=00f100fd [init] bttv1: using tuner=4 bttv1: add subdevice "dvb1" bt878: AUDIO driver version 0.0.0 loaded bt878: Bt878 AUDIO function found (0). ACPI: PCI Interrupt :00:09.1[A] -> GSI 17 (level, low) -> IRQ 16 bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB functions. bt878(0): Bt878 (rev 17) at 00:09.1, irq: 16, latency: 32, memory: 0xee80 bt878: Bt878 AUDIO function found (1). ACPI: PCI Interrupt :00:0a.1[A] -> GSI 18 (level, low) -> IRQ 18 bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB functions. bt878(1): Bt878 (rev 17) at 00:0a.1, irq: 18, latency: 32, memory: 0xed80 DVB: registering new adapter (bttv0). dst(0) rdc_8820_reset: Resetting DST dst(0) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[] dst(0) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[0004] dst(0) dst_comm_init: Initializing DST. dst(0) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(0) rdc_reset_state: Resetting state machine dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(0) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 00 06 00 00 00 00 00 fa ] dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) read_dst: reply is 0xff dst(0) dst_wait_dst_ready: dst wait ready after 1 dst(0) read_dst: reply is 0x0 0x44 0x43 0x54 0xd 0x43 0x49 0x6c dst(0) dst_gpio_outb: mask=[], enbb=[], outhigh=[] dst(0) dst_get_device_id: Checksum failure! dst(0) dst_probe: unknown device. frontend_init: Could not find a Twinhan DST. dvb-bt8xx: A frontend driver was not found for device 109e/0878 subsystem 1822/0001 DVB: registering new adapter (bttv1). dst(1) rdc_8820_reset: Resetting DST dst(1) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[] dst(1) dst_gpio_outb: mask=[0004], enbb=[0004], outhigh=[0004] dst(1) dst_comm_init: Initializing DST. dst(1) dst_gpio_outb: mask=[], enbb=[0001], outhigh=[] dst(1) rdc_reset_state: Resetting state machine dst(1) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[] dst(1) dst_gpio_outb: mask=[0002], enbb=[0002], outhigh=[0002] writing [ 00 06 00 00 00 00 00 fa ] dst(1) dst_gpio_outb: mask=[], enbb=[], outhigh=[] ds
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital problems
Thanks for your suggestions Damien and Mike.I installed the atrpms video4linux-kmdl-2.6.17-1.2187_FC5 package and it has the same problems as the build I did from the v4l-dvb development tree: - USB tuner stops working after a while and will not work again until I shutdown and turn of the power - PCI tuner can't receive SBS channelI also tried Chris Pascoe's tree http://linuxtv.org/hg/~pascoe/v4l-dvb-test/ and it has the same problems with USB tuner stability and with SBS on the PCI tuner. But it does not require the +17Hz offset for Nine and SBS (thanks Damien) as the current development tree does, so it looks like all of Chris's changes have not been merged as yet.Are there any other patches, etc I should be trying? I had a look at http://www.itee.uq.edu.au/~chrisp/Linux-DVB/DVICO/ but can't see anything obvious.Thanks again,Mark.Michael Krufky <[EMAIL PROTECTED]> wrote: AFAIK, These problems have all been fixed in our development tree hostedon linuxtv.org ... You have to change around some #ifdef kernel versiontests in the code if you want it to build correctly against fc5'sbackported 2.6.18 kernel, (which reports itself as 2.6.17).For info, see: http://linuxtv.org/repoThere was an email recently on the list that explains what code needs tobe changed to make it work on FC5, but an easier way to install thosemodules would be using ATrpms ... just do:yum install video4linux-kmdl-`uname -r`...after a reboot, you should be all fixed.Cheers,Mike Stay in the know. Pulse on the new Yahoo.com. Check it out. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
RE: [linux-dvb] Error building latest sources
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark HowellsSent: 27 September 2006 00:27 I just grabbed the latest sources amd tried to build them # hg clone http://linuxtv.org/hg/v4l-dvb # cd v4l-dvb # make The compilation fails with In file included from /home/mark/v4l-dvb/v4l/cpia2_v4l.c:42: /home/mark/v4l-dvb/v4l/cpia2.h:408: error: field 'vp' has incomplete type /home/mark/v4l-dvb/v4l/cpia2.h:409: error: field 'vw' has incomplete type /home/mark/v4l-dvb/v4l/cpia2_v4l.c:91:2: error "VID_HARDWARE_CPIA2 should have been defined in linux/videodev.h" / ... I solved this by running make config and just configuring for my device (hence configuring out the cpia2) However, I'm still puzzled as to why I need to do this... Mark smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Configuring for a Hauppauge Nova-T PCI
I'm puzzled about how to configure the kernel for this device. I have one of the old PCI Nova-T cards with SAA7146 / TDA10046 devices. When I configure my kernel ( 2.6.16-gentoo-r7 ) I see that the section labelled Supported SAA7146 based PCI Adapters has three dashes '---' and is not selectable. So, how can I compile for this device? Can I even compile this in and still use the latest drivers and a module based install for a range of USB devices I'm working with? Any help would be appreciated Cheers Mark smime.p7s Description: S/MIME cryptographic signature ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DViCO FusionHDTV DVB-T Dual Digital problems
Kielogl wrote: I also tried Chris Pascoe's tree http://linuxtv.org/hg/~pascoe/v4l-dvb-test/ and it has the same problems with USB tuner stability and with SBS on the PCI tuner. But it does not require the +17Hz offset for Nine and SBS (thanks Damien) as the current development tree does, so it looks like all of Chris's changes have not been merged as yet. I have both tuners working fine under 2.6.16.19 with the hg tree using the ZL10353 based version, with the following transports for SBS and Nine in Melbourne: Nine: 191791667 SBS: 53667 Perhaps try a stock kernel instead of the FC-rolled version? Cheers, Pete ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: R: [linux-dvb] Requesting help to configure remote forSAA7134_BOARD_FLYDVB_TRIO
Hi! Am Dienstag, den 26.09.2006, 23:42 +0200 schrieb Eddi: > I can't get remote working yet using rc5 patch too! > > I've found an interesting topic about my card on > "http://archives.devshed.com/forums/linux-97/saa7134-reserving-a-card-number > -1694848.html" and should be already passed on one of this mailing list. > > Chip on my card: > be5v1h 4410 4+4 pin > 4231 fm/tv switch > 8275a + tda10046 (DVBT) > a8262 + tda10086 (DVBS) > isl6421 - Single Output LNB Supply and Control Voltage Regulator with I2C > mdt10p55b - ROM size 1.0kx14 RAM size 72 bytes I/O pin 11 INT RC (4MHZ) > Pin count 14 (should be equivalent to PIC 16C505) > > Someone tell about theat the uC may be for ir purpose. > > So perhaps RC5 doesn't work. > > Any other idea? > > Eddi Ah yes, Peter mentioned a pic and mdt types are quite common, do a search on bttv-gallery.de. Just having a short look at my backlash, since I'm away from PCs next days, but sorry for might have sending you in a wrong direction. After removing the tuner shielding later on the asus p7131 dual I discovered only the same 4231 switch and nothing else new and forgot the mentioned PIC. There are examples in saa7134-input where the IR controller must be enabled by a gpio switch. Peter had the card only for a very short time, but he called then for testers with m$ using maybe regspy of DScaler to find something, IIRC. It might be more complicated and not unlikely he went already through pulling gpios, but can't say. Cheers, Hermann ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Re: MSI Megasky 580 using Uli m9206 -- http://linuxtv.org/hg/~mkrufky/m920x
On Tue, 26 Sep 2006 14:21:08 -0400
Michael Krufky <[EMAIL PROTECTED]> wrote:
> Patrick,
>
> Could you look over the changesets in this tree and let me know
> whether or not you approve of this?
>
> Aapo,
>
> After you sent your patch in to the linux-dvb mailing list, Patrick
> had some comments and requests for certain things to be cleaned up.
> I have not seen any response from you about those requests.
Hehe, it's not like I have heard any reports from the users either...
> In an effort to move things along, I have taken it upon myself to
> clean up your patch. I've updated it to comply with some of the
> recent changes in the dvb-usb structure, and to use the new
> dvb_attach() method.
Couple improvements in this patch:
-hardware pid filtering no longed enabled unless in usb 1.x mode
-more responsive rc handling
-some minor bug fixes and code refolding
-m9206_write delay dropped(doesn't seem to be needed)
Signed-off-by: Aapo Tahkola <[EMAIL PROTECTED]>
> I have also separated the qt1010 tuner code into a separate header
> file. It has come to my attention, thanks to Markus Rechberger, that
> there may be more fixing to do with regards to the qt1010 stuff...
> but that can be done later, in a separate patch.
I lost the perl scripts used analyse the tuner data so I'm not
really interested in rewriting them just for this. I would probably use
the gl861 based mega sky to check the odd frequencies as it has
slightly simpler i2c.
> I'd like it if you could test the updated tree and confirm that it
> works as expected with your device. Please clone the following tree:
>
> http://linuxtv.org/hg/~mkrufky/m920x
It stalls with silence if I modprobe the driver and plug in the stick.
If I plug in and then modprobe, nothing happens.
Compiling linux-2.6.18 to see if that sorts it out. Doesn't seem to be
related to m920x code though...
>
> You will notice that I have decided to rename the driver from megasky
> to m920x -- I did this for a few reasons:
>
> 1) There are probably other devices out there based on the m9205,
> m9206 and m9207 chipsets ... Adding support for those devices will
> probably be a matter of updating the code in this driver, in which
> case, the name 'megasky' may be inappropriate.
I think m9207 just fixes the isoch hardware bug.
> 2) There is another device out there, called "MSI Megasky 580", based
> on the gl861 chipset, using the same exact usb id as your device
> based on the m9206 chipset. This means that MSI released two
> completely different devices, each with the same exact name and USB
> ID!
Actually, I think the newer version has pid of 0x5581, at least
according to the windows driver.
> 3) We should name the driver based on the chipset it uses, rather than
> the Vendor's retail name of the product.
I first thought it would be better to use retail name because of 2).
--
Aapo Tahkola
diff -r f955dadfe5bc linux/drivers/media/dvb/dvb-usb/m920x.c
--- a/linux/drivers/media/dvb/dvb-usb/m920x.c Sat Sep 23 23:40:20 2006
+++ b/linux/drivers/media/dvb/dvb-usb/m920x.c Wed Sep 27 04:51:39 2006
@@ -62,23 +62,38 @@
ret = usb_control_msg(udev, usb_sndctrlpipe(udev, 0),
request, USB_TYPE_VENDOR | USB_DIR_OUT,
value, index, NULL, 0, 2000);
- msleep(3);
-
+ //msleep(3);
+
+ return ret;
+}
+
+static int m9206_rc_init(struct usb_device *udev)
+{
+ int ret = 0;
+
+ /* Remote controller init. */
+ if ((ret = m9206_write(udev, M9206_CORE, 0xa8, M9206_RC_INIT2)) != 0)
+ return ret;
+
+ if ((ret = m9206_write(udev, M9206_CORE, 0x51, M9206_RC_INIT1)) != 0)
+ return ret;
+
return ret;
}
static int m9206_rc_query(struct dvb_usb_device *d, u32 *event, int *state)
{
+ struct m9206_state *m = d->priv;
int i, ret = 0;
u8 rc_state[2];
if (mutex_lock_interruptible(&d->i2c_mutex) < 0)
return -EAGAIN;
- if ((ret = m9206_read(d->udev, 0x22, 0x0, 0xff51, rc_state, 1)) != 0)
+ if ((ret = m9206_read(d->udev, M9206_CORE, 0x0, M9206_RC_STATE, rc_state, 1)) != 0)
goto unlock;
- if ((ret = m9206_read(d->udev, 0x22, 0x0, 0xff52, rc_state + 1, 1)) != 0)
+ if ((ret = m9206_read(d->udev, M9206_CORE, 0x0, M9206_RC_KEY, rc_state + 1, 1)) != 0)
goto unlock;
for (i = 0; i < ARRAY_SIZE(megasky_rc_keys); i++)
@@ -92,11 +107,14 @@
case 0x93:
case 0x92:
+m->rep_count = 0;
*state = REMOTE_KEY_PRESSED;
goto unlock;
case 0x91:
-*state = REMOTE_KEY_REPEAT;
+/* For comfort. */
+if (++m->rep_count > 2)
+ *state = REMOTE_KEY_REPEAT;
goto unlock;
default:
@@ -124,6 +142,12 @@
struct dvb_usb_device *d = i2c_get_adapdata(adap);
int i;
int ret = 0;
+
+ /* Need to access d->adapter[0] */
+ if (d->num_adapters_initialized != 1) {
+ deb_rc("Impossible happened!\n");
+ return -EINVAL;
+ }
if (mutex_lock_interruptible(&d->i2c_mutex) < 0)
return -EAGAIN;
@@ -134,22 +158,23 @@
for (i = 0; i < num; i++) {
u8 w_len;
- if ((ret = m9206_write(d->udev, 0x23, msg[i].addr, 0x80)) != 0)
+ if ((ret = m920
[linux-dvb] Signal Strength for lgdt330x
I have attached a patch for the LGDT330X frontend, to allow for signal strength reporting. It also reports snr in dB using the dvb_math functions. This change to SNR reporting still fits within the current interpretation of the return value, it just gives more meaning to the numbers for those of us who want it. The change is applied to both 3302 and 3303 frontends. I have passed it around for limited testing, and it is reported to work, so I'm posting it here for consideration. Thanks, Rusty ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Signal Strength for lgdt330x
(I guess it would help if I actually attached the patch before sending...)
Here it is...
I have attached a patch for the LGDT330X frontend, to allow for signal strength
reporting. It also reports snr in dB using the dvb_math functions. This
change to SNR reporting still fits within the current interpretation of the
return value, it just gives more meaning to the numbers for those of us who
want it. The change is applied to both 3302 and 3303 frontends. I have passed
it around for limited testing, and it is reported to work, so I'm posting it
here for consideration.
Thanks,
Rusty# HG changeset patch
# User Rusty Scott <[EMAIL PROTECTED]>
# Node ID f4de0afd4a56499607adf29bb5f7859cbeafe118
# Parent fae890aee0c365fe8741b166690c9f0a81c495a1
lgdt330x signal strength reporting
From: Rusty Scott <[EMAIL PROTECTED]>
Change read_snr to report in dB using dvb_math functions
Add signal strength reporting as 0 to 100% of 35 dB SNR signal
Signed-off-by: Rusty Scott <[EMAIL PROTECTED]>
diff -r fae890aee0c3 -r f4de0afd4a56 linux/drivers/media/dvb/frontends/lgdt330x.c
--- a/linux/drivers/media/dvb/frontends/lgdt330x.c Tue Sep 19 12:51:56 2006 -0300
+++ b/linux/drivers/media/dvb/frontends/lgdt330x.c Tue Sep 19 21:18:20 2006 -0600
@@ -46,6 +46,7 @@
#include
#include "dvb_frontend.h"
+#include "dvb_math.h"
#include "lgdt330x_priv.h"
#include "lgdt330x.h"
@@ -549,130 +550,135 @@ static int lgdt3303_read_status(struct d
return 0;
}
-static int lgdt330x_read_signal_strength(struct dvb_frontend* fe, u16* strength)
-{
- /* not directly available. */
- *strength = 0;
- return 0;
-}
-
static int lgdt3302_read_snr(struct dvb_frontend* fe, u16* snr)
{
-#ifdef SNR_IN_DB
/*
* Spec sheet shows formula for SNR_EQ = 10 log10(25 * 24**2 / noise)
- * and SNR_PH = 10 log10(25 * 32**2 / noise) for equalizer and phase tracker
- * respectively. The following tables are built on these formulas.
- * The usual definition is SNR = 20 log10(signal/noise)
- * If the specification is wrong the value retuned is 1/2 the actual SNR in db.
- *
- * This table is a an ordered list of noise values computed by the
- * formula from the spec sheet such that the index into the table
- * starting at 43 or 45 is the SNR value in db. There are duplicate noise
- * value entries at the beginning because the SNR varies more than
- * 1 db for a change of 1 digit in noise at very small values of noise.
- *
- * Examples from SNR_EQ table:
- * noise SNR
- * 043
- * 142
- * 239
- * 337
- * 436
- * 535
- * 634
- * 733
- * 833
- * 932
- * 10 32
- * 11 31
- * 12 31
- * 13 30
+ * and SNR_PH = 10 log10(25 * 32**2 / noise) for equalizer and phase
+ * tracker respectively.
*/
- static const u32 SNR_EQ[] =
- { 1, 2, 2, 2, 3, 3, 4, 4, 5, 7,
- 9, 11, 13, 17, 21, 26, 33,41,52,65,
- 81,102,129,162, 204,257,323, 406, 511, 644,
- 810, 1020, 1284, 1616, 2035, 2561, 3224, 4059, 5110, 6433,
- 8098, 10195, 12835, 16158, 20341, 25608, 32238, 40585, 51094, 64323,
- 80978, 101945, 128341, 161571, 203406, 256073, 0x4
- };
-
- static const u32 SNR_PH[] =
- { 1, 2, 2, 2, 3, 3, 4, 5, 6, 8,
- 10,12, 15, 19, 23, 29, 37,46,58,73,
- 91,115,144,182,229,288, 362, 456, 574, 722,
- 909, 1144, 1440, 1813, 2282, 2873, 3617, 4553, 5732, 7216,
- 9084, 11436, 14396, 18124, 22817, 28724, 36161, 45524, 57312, 72151,
- 90833, 114351, 143960, 181235, 228161, 0x08
- };
-
- static u8 buf[5];/* read data buffer */
- static u32 noise; /* noise value */
- static u32 snr_db; /* index into SNR_EQ[] */
- struct lgdt330x_state* state = (struct lgdt330x_state*) fe->demodulator_priv;
-
- /* read both equalizer and phase tracker noise data */
- i2c_read_demod_bytes(state, EQPH_ERR0, buf, sizeof(buf));
-
- if (state->current_modulation == VSB_8) {
- /* Equalizer Mean-Square Error Register for VSB */
- noise = ((buf[0] & 7) << 16) | (buf[1] << 8) | buf[2];
-
- /*
- * Look up noise value in table.
- * A better search algorithm could be used...
- * watch out there are duplicate entries.
- */
- for (snr_db = 0; snr_db < sizeof(SNR_EQ); snr_db++) {
- if (noise < SNR_EQ[snr_db]) {
-*snr = 43 - snr_db;
-break;
- }
- }
- } else {
- /* Phase Tracker Mean-Square Error Register for QAM */
- noise = ((buf[0] & 7<<3) << 13) | (buf[3] << 8) | buf[4];
-
- /* Look up noise value in table. */
- for (snr_db = 0; snr_db < sizeof(SNR_PH); snr_db++) {
- if (noise < SNR_PH[snr_db]) {
-*snr = 45 - snr_db;
-break;
- }
- }
- }
-#else
/* Return the raw noise value */
static u8 buf[5];/* read data buffer */
static u32 noise; /* noise value */
+ static s32 value; /* full precision converted va
[linux-dvb] KWorld VStream XPert DVB-T card fails to lock kernel 2.6.18
Hello, I just upgraded to kernel 2.6.18 and my Kworld V-Stream DVB-T card now fails to lock, whereas everything was fine with 2.6.17. Here is a copy of dmesg & lsmod -- Ben # dmesg 1fff8000 (ACPI data) BIOS-e820: 1fff8000 - 2000 (ACPI NVS) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff8 - 0001 (reserved) 0MB HIGHMEM available. 511MB LOWMEM available. found SMP MP-table at 000fb880 On node 0 totalpages: 131056 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 126960 pages, LIFO batch:31 DMI 2.3 present. ACPI: RSDP (v000 AMI ) @ 0x000fa710 ACPI: RSDT (v001 AMIINT VIA_K7 0x0010 MSFT 0x0097) @ 0x1fff ACPI: FADT (v001 AMIINT VIA_K7 0x0011 MSFT 0x0097) @ 0x1fff0030 ACPI: MADT (v001 AMIINT VIA_K7 0x0009 MSFT 0x0097) @ 0x1fff00c0 ACPI: DSDT (v001VIA VIA_K7 0x1000 MSFT 0x010d) @ 0x ACPI: PM-Timer IO Port: 0x808 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 6:6 APIC version 16 ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 17, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 3000 (gap: 2000:dec0) Detected 1399.849 MHz processor. Built 1 zonelists. Total pages: 131056 Kernel command line: root=/dev/hda2 ro mapped APIC to d000 (fee0) mapped IOAPIC to c000 (fec0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 2048 (order: 11, 8192 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 516700k/524224k available (1543k kernel code, 6972k reserved, 560k data, 152k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 2801.09 BogoMIPS (lpj=1400547) Security Framework v1.0.0 initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 0383fbff c1cbfbff CPU: After vendor identify, caps: 0383fbff c1cbfbff CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 256K (64 bytes/line) CPU: After all inits, caps: 0383fbff c1cbfbff 0420 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Compat vDSO mapped to e000. CPU: AMD Athlon(tm) XP 1600+ stepping 02 Checking 'hlt' instruction... OK. ACPI: Core revision 20060707 ENABLING IO-APIC IRQs ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfdb21, last bus=1 Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Power Resource [URP1] (off) ACPI: Power Resource [URP2] (off) ACPI: Power Resource [FDDP] (off) ACPI: Power Resource [LPTP] (off) ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11 *12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 9 devices PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report PCI: Bridge: :00:01.0 IO window: disabled. MEM window: d1e0-d3ef PREFETCH window: c1c0-d1cf PCI: Bus 2, cardbus bridge: :00:06.0 IO window: 1000-10ff IO window: 1400-14ff PREFETCH window: 3000-31ff MEM window: 3200-33ff PCI: Setting latency timer of device :00:01.0 to 64 PCI: Enabling device :00:06.0 ( -> 0003) ACPI: PCI Interrupt :00:06.0[A] -> GSI 17 (level, low) -> IRQ 169 PCI: Setting latency timer of device :00:06.0 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables
Re: [linux-dvb] Pinnacle 310i DVB-T Linux
Hartmut Hackmann schrieb: Hi, Mark Mark Schwarz wrote: Hi, i have an Pinnacle 310i but i don't want analoge TV! Is there an chance to get it runnning in DVB-T ? linuxtv.org means: only work analogue tv, not digital. :-( Please give a sign if anyone has a advice We had a preliminary patch. Unfortunately, it no longer applies. I intend to add support for this card very soon. Hartmut Is there a date when the patch release or can i try it before ? Greetings Mark ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
