Re: [linux-dvb] Hauppauge WinTV Nova-TD DVB-T USB stick reception problems
On Mon, 17 Dec 2007 at 1:46pm, Henrik Beckman wrote: > Hi, Hello, > I assume that it´s me you mention. Yeah, sorry about misspelling your last name. > I have my htpc running with a nova-TD and it´s working ok with > the exception of SVT1 which for some reasons occasionaly > generates disconnects as seen on the Nova-T 500. To note here > is that I have a VIA usb card, using my onboard nvidia USB led > to hard hangs within ~4 hours with the nova-TD. I remember reading your posts about those problems, but figured I might be spared from them as I'm using an AMD based motherboard. Haven't seen any disconnects so far, but I haven't been using the stick too much either... > Reception is a tad better with the nova-T 500 (which also > chokes on SVT1). Contact me if you need more detailed > information about my kernel . Yes, I'd appreciate it if you could tell me what kernel version you're using on the htpc (downgrading the kernel should be no problem for me) and if you're using the kernel drivers or the hg ones (and if it's the hg ones, what version?). I can't get neither the kernel drivers nor the hg ones to work, and I've got both antennaes connected (and, as I wrote, scanning works so I do have some kind of reception and working firmware etc.). (Mailing me those details off-list is perfectly ok for me, if for some reason you don't want to post them here.) /Tomas > On Dec 16, 2007 5:07 PM, Tomas <[EMAIL PROTECTED]> wrote: > > > Hello, > > > > I'm having problems tuning my Hauppauge WinTV Nova-TD USB DVB > > receiver. > > > > Scanning for channels works fine with the 'scan' utility, I have > > compared the result with the result from a scan performed using > > my Twinhan DTV Alpha USB stick (7045, not 7045A, which is another > > story...) and they are identical. > > > > But when it's time to record, using the same program I use with > > the Twinhan stick, I get (almost) no output, just a ridiculously > > high bit error rate (2097151) and SNR=0. I'm very surprised by > > this, as the channel scanning works just fine. > > > > As far as I understand, and as previously reported by Henrik > > Backman, the Nova-TD should work with the DVB-T broadcasts here > > in Sweden. > > > > Could my problems be caused by the important bug mentioned > > yesterday by Patrick Boettcher? If so, is there an earlier > > version of the driver which doesn't have this bug? > > > > The command used to test recording: > > > > ~# /usr/local/bin/dvbstream -f 49 -p V -s 27500 -c 0 -o:test.ts 1029 > > 1028 > > dvbstream v0.6 - (C) Dave Chapman 2001-2004 > > Released under the GPL. > > Latest version available from http://www.linuxstb.org/ > > Processing -o:test.ts > > Open file test.ts > > Using DVB card "DiBcom 7000PC" > > tuning DVB-T (Stockholm Nacka) to 49000 Hz, Bandwidth: 8 > > polling > > Getting frontend event > > FE_STATUS: > > polling > > Getting frontend event > > FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC > > Event: Frequency: 49000 > > Bit error rate: 2097151 > > Signal strength: 65535 > > SNR: 0 > > FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_SYNC > > MAP 0, file test.ts: From -1 secs, To -1 secs, 2 PIDs - 1029 1028 > > dvbstream will stop after -1 seconds (71582788 minutes) > > Setting filter for PID 1029 > > Setting filter for PID 1028 > > Using 224.0.1.2:5004:2 > > version=2 > > Streaming 2 streams > > Caught signal 2 - closing cleanly. > > ~# ls -la test.ts > > -rw-r--r-- 1 ath ath 188 Dec 16 16:43 test.ts > > ~# > > > > (I'm terminating the program by pressing Ctrl-C). Whether I get > > any packets at all seems totally random. In this attempt I got > > one single packet from several minutes of running dvbstream! > > > > A sample from the scan output: > > > > ~# grep '^SVT2:' .dvb_channels > > > > SVT2:49000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:1029:1028:5060 > > ~# > > > > I have also tried tuning with tzap and recording using cat, but > > tzap gives this: > > > > ~# tzap -a 0 -c ~/.dvb_channels 'SVT2' > > using '/dev/dvb/adapter0/frontend0' and > > '/dev/dvb/adapter0/demux0' > > tuning to 49000 Hz > > video pid 0x0405, audio pid 0x0404 > > status 0f | signal b496 | snr | ber 001f | unc | > > status 1e | signal | snr 000
[linux-dvb] Hauppauge WinTV Nova-TD DVB-T USB stick reception problems
b0700 The firmware is a renamed dvb-usb-dib0700-03-pre1.fw : ~# ls -la /lib/firmware/dvb* -rw-r--r-- 1 root root 33277 2007-12-04 15:51 /lib/firmware/dvb-usb-dib0700-03-pre1.fw -rw-r--r-- 1 root root 33277 2007-12-04 15:51 /lib/firmware/dvb-usb-dib0700-1.10.fw ~# cmp /lib/firmware/dvb-usb-dib0700-* ~# I've just spent over an hour fighting with mythtv configuration (I installed the Debian packages) and would appreciate suggestions that do not involve mythtv, as I can't get the thing working. /Tomas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Pinnacle Dual DVB-T Diversity - 2001e version?
Hello list I'm looking for a dual tuner device for DVB-T reception with USB 2.0 connectivity. Pinnacle PCTV Dual DVB-T Diversity (PCTV 2000e USB) came to my sight. I have learned, that it should work under linux: http://www.linuxtv.org/wiki/index.php/Pinnacle_PCTV_Dual_DVB-T_Diversity_%28PCTV_2000e_USB%29 However nowadays, different version called 2001e is saled under the same name. (On the official pages there is even newer version showed with dark case.) http://www.pinnaclesys.com/PublicSite/uk/Products/Consumer+Products/PCTV+Tuners/PCTV+Digital+PVR+%28DVB-S_DVB-T%29/PCTV+Dual+DVB-T+Diversity+Stick.htm My question is: Will it work? Does someone have an experience with this version? I have downloaded windows drivers from: http://cdn.pinnaclesys.com/SupportFiles/PCTV%20Drivers/ReadmePCTV.htm and after looking into it, PCTVDiB.inf states, that it is driver for * PCTV 2000e * PCTV 2001e * PCTV DVB-T Flash Stick and there is only one driver file mod7700.sys assigned to all three versions. Does that mean, that existing driver (after adding new USB IDs to the kernel) will work with this stick? Should I buy it and try, or am I completly wrong? Thanks for advice -- Tomáš Bláha e-mail: tomas.blaha at kapsa.cz JabberID: tomiiik at jabber.cz ICQ: 76239430___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Genius TVGo DVB-T02Q
Hello, I'm investigating status of this DVB-T tuner support. I've found some discussions about it in the archive, namely these two threads http://www.mail-archive.com/linux-dvb@linuxtv.org/msg20295.html http://www.mail-archive.com/linux-dvb@linuxtv.org/msg24248.html but I still can't get it to work as the repository http://linuxtv.org/hg/~mkrufky/megasky is not available anymore - I'm using 2.6.22 kernel and the experimental patch does not fit. The device I've received might be a little bit different, as the idProduct is 0x7040 and not 0x702b as in the patch. What is the current status of this patch? thanks Tomas lsusb -v output - Bus 001 Device 002: ID 0458:7040 KYE Systems Corp. (Mouse Systems) Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0458 KYE Systems Corp. (Mouse Systems) idProduct 0x7040 bcdDevice0.01 iManufacturer 1 Genius iProduct2 DVB-T02Q MCE iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 50 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Devices bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 1 Keyboard iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 63 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 7 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] KNC-1 DVB-T + Cineview + Conax cam == ERROR
I have the same combination except that I have a KNC1 DVB-C Plus card. Also my Conax CAM does not work, see my post at http://www.linuxtv.org/pipermail/linux-dvb/2007-February/016097.html What did you do to get the debugging output? Is there any DVB budget card that works with a Conax CAM? I have seen reports that FF DVB cards work with Conax CAMs, but so far I have only seen problem reports with DVB budget cards and Conax CAMs. Best regards, Tomas Lindén ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Random kernel oopses using TwinhanDTV Alpha and dvb-usb-vp7045
On Sat, 3 Mar 2007 at 9:52am, Marko Ristola wrote: > Hello, Hi, > The randomness of problems suggest that the problem is bad > memory hardware. Good idea. I hadn't thought about that, but there's a reason why (and I still don't believe that the cause): the only time I experience any problems is when loading and unloading the DVB modules. Not when I load/unload other modules (usb-related or otherwise; some examples are usb-storage, cdrom, ide-cd, forcedeth, nvidia etc.), compile new kernels, edit stuff recorded with my DVB cards, surf, mail... I simply haven't noticed any other problems that could be due to bad RAM. > I'd suggest to use some memory testing tool to check that your > memory works. > > You might find a memory testing tool on Linux distribution's > recovery CD or install CD. > I think that Knoppix CD has that also. > > The tool is named memtest. I have run the latest Debian unstable versions of memtest86+ (for 1.5 hours), memtest86 (for 2 hours), and memmxtest (for 1 hours) and none of them have found any errors. True, they can miss things (as they mention in the docs), but, like I wrote earlier, my system is solid except when loading/unloading DVB modules. So my money is still on some subtle error in the modules. Unfortunately. Does anyone have any ideas on how what my next step should be? (Except giving up or switching to another receiver, of course. :) /Tomas > Regards, > Marko Ristola > > Tomas kirjoitti: > > Hello, > > > > First of all, I apologize in advance for a long post, but I > > figure it's better to provide some error messages instead of just > > writing a stupid "help, TwinhanDTV doesn't work, why?" post. I > > find it hard to believe I'm the only one experiencing these > > problems, but digging around with google and on linuxtv.org > > haven't been of any help. > > > > Here goes: > > > > I'm experiencing random kernel errors with my TwinhanDTV Alpha > > USB 2.0 DVB-T receiver using the dvb-usb-vp7045 kernel module: > > > > 1. Sometimes the kernel completely freezes up. Powercycle needed. > > > > 2. Sometimes the kernel completely freezes up with the CapsLock > >and ScrLk LEDs on my keyboard blinking. Powercycle needed. > > > > 3. Sometimes the keyboard/mouse stops working in X but pressing > >the power button makes acpid initiate a shutdown (so at least > >the kernel isn't completely hosed). The shutdown hangs at > >"Unmounting local filesystems" at which point the keyboard is > >working again (I guess it was only dead in X) so I can do a > >Alt-SysRq-S followed by Alt-SysRq-B. > > > > 4. And very rarely not even the keyboard/mouse stops working in > >X, but I get all the syslog error messages printed to every > >xterm. > > > > Any one of these errors (though very rarely number 4) happens > > about 30%-50% of the time when I'm using the DVB receiver. > > > > My experience as a programmer tells me that when such random > > errors occur they're usually due to something simple such as an > > uninitialized variable being used (but there are no such warnings > > when compiling the modules) or a pointer that has an incorrect > > value. > > > > The freezes all seem to occur either when the dvb-usb-vp7045 > > module gets loaded by modprobe or when it's unloaded. At least > > that's what I'm guessing after reading through the error messages > > in /var/log/kern.log . > > > > The crashes occur with both kernel 2.6.18.2 and 2.6.20.1 . (AMD > > Athlon XP 2500+ with 512MB RAM on an ASUS A7N8X Deluxe > > motherboard.) > > > > Today's crash (of type 2) occurred when I was trying to start a > > recording scheduled by crontab at 12:58. I discovered the crash > > at 16:18. It left these traces in /var/log/kern.log : > > > > Mar 2 07:03:20 miguel kernel: usb 1-1: USB disconnect, address 4 > > Mar 2 12:58:01 miguel logger: Initializing recording > > Mar 2 12:58:01 miguel logger: rmmod dvb-usb-vp7045 > > Mar 2 12:58:15 miguel kernel: usbcore: deregistering interface driver > > dvb_usb_vp7045 > > Mar 2 12:58:15 miguel kernel: dvb-usb: Twinhan USB2.0 DVB-T receiver > > (TwinhanDTV Alpha/MagicBox II) successfully deinitialized and disconnected. > > Mar 2 12:58:15 miguel logger: rmmod dvb-usb > > Mar 2 12:58:15 miguel logger: rmmod dvb-usb-vp7045 > > Mar 2 12:58:15 miguel logger: rmmod dvb-usb > > Mar 2 12:58:15 miguel logger: modprobe dvb-usb > > Mar 2 12:58:15 miguel logger: modprobe dvb-usb-vp7045 > > Mar 2 16
[linux-dvb] Random kernel oopses using TwinhanDTV Alpha and dvb-usb-vp7045
. (Cleaning up modules is necessary on my other machine which has my Twinhan PCI card and a Hauppauge PVR-150 card, as those two cards seem to share some modules, so I've adopted that strategy on my TwinhanDTV Alpha-equipped machine as well.) I like using crontab and dvbstream instead of a MythTV or some other available solution. I'll write better scripts when the kernel quits crashing. When everything works the quality of recordings made with the TwinhanDTV Alpha using the crappy bundled indoor antenna is way better than recordings of the same TV program made with my Twinhan PCI DVB-T card using a big grid antenna. We're talking 0-20 errors compared to 100-1000 errors (as reported by ProjectX). So I'd really like to get the TwinhanDTV Alpha working reliably. Again, sorry for the long post. I can supply more info (full kernel config etc.) on request, but I figure if this mail gets any larger noone will even bother opening it in the first place. :) /Tomas ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C+, CineView v. 3.0 and Conax CAM: PC card did not respond
On Thu, 22 Feb 2007, Jeroen Asselman wrote: > Hi. > > > How can one get debugging information from the CI-module, CAM and the > > PC-card to see why the initialization fails? > > I added the following lines to my modprobe.conf for more debugging info: > options dvb-core cam_debug=1,1 debug=1,1 > options budget-core debug=1,1 I added the following debug options to /etc/modprobe.conf options dvb-core cam_debug=1,1 debug=1,1 options budget-core debug=1,1 modprobe budget_av gives then these messages: saa7146: register extension 'budget_av'. ACPI: PCI Interrupt :04:08.0[A] -> Link [LNKA] -> GSI 18 (level, low) -> IRQ 21 saa7146: found saa7146 @ mem f8ab4400 (revision 1, irq 21) (0x1894,0x0021). saa7146 (0): dma buffer size 192512 DVB: registering new adapter (KNC1 DVB-C Plus). adapter failed MAC signature check encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff budget_av: saa7113_init(): saa7113 detected and initializing budget_av: saa7113_init(): saa7113 status=d0 saa7146_vv: saa7146 (0): registered device video1 [v4l2] KNC1-0: MAC addr = 00:09:d6:6d:5c:c4 DVB: registering frontend 0 (Philips TDA10021 DVB-C)... dvb_ca_en50221_init budget-av: ci interface initialised. dvb_ca_en50221_thread Inserting the Conax CAM with the Conax card gives these messages: budget-av: cam inserted B budget_av: ciintf_slot_reset(): ciintf_slot_reset dvb_ca adaptor 0: PC card did not respond :( Removing it gives these messages: budget_av: ciintf_slot_shutdown(): ciintf_slot_shutdown budget-av: cam ejected 5 dvb_ca_en50221_slot_shutdown budget_av: ciintf_slot_shutdown(): ciintf_slot_shutdown Slot 0 shutdown rmmod budget_av gives this message: ACPI: PCI interrupt for device :04:08.0 disabled What can be learned from this? Best regards, Tomas Lindén___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] KNC1 DVB-C+, CineView v. 3.0 and Conax CAM: PC card did not respond
I have a KNC1 TV-Station DVB-C Plus card http://www.knc1.com/img/presse_big/karte_dvb_c_plus.jpg with a CineView CI-interface version 3.0 instead of the version 1.1 shown here http://www.knc1.de/img/presse_big/karte_cineview.jpg and a Conax 4.00e Rev 1.1 CAM http://www.koodinvuoksi.net/catalog/resize.php?image=images/cam_conax.jpg&width= I'm using Fedora Core 6 with this kernel Linux asterix 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 19:28:18 EST 2007 i686 athlon i386 GNU/Linux Reception of free to air broadcasts work fine. The problem is that the Conax card is not initialized. Inserting and removing the Conax CAM always results in the error message dvb_ca adaptor 0: PC card did not respond :( The Conax card works fine in a Handan DVB-C 5000 box. modprobe budget_av gives: saa7146: register extension 'budget_av'. ACPI: PCI Interrupt :04:08.0[A] -> Link [LNKA] -> GSI 18 (level, low) -> IRQ 21 saa7146: found saa7146 @ mem f8a16400 (revision 1, irq 21) (0x1894,0x0021). saa7146 (0): dma buffer size 192512 DVB: registering new adapter (KNC1 DVB-C Plus). adapter failed MAC signature check encoded MAC from EEPROM was ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff saa7146_vv: saa7146 (0): registered device video1 [v4l2] KNC1-0: MAC addr = 00:09:d6:6d:5c:c4 DVB: registering frontend 0 (Philips TDA10021 DVB-C)... budget-av: ci interface initialised. budget-av: cam inserted A dvb_ca adaptor 0: PC card did not respond :( Output of lspci -vvv: 04:08.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Subsystem: KNC One Unknown device 0021 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- ls -l /dev/dvb/adapter0/ total 0 crw--- 1 tlinden root 212, 6 Feb 21 10:20 ca0 crw--- 1 tlinden root 212, 4 Feb 21 10:20 demux0 crw--- 1 tlinden root 212, 5 Feb 21 10:20 dvr0 crw--- 1 tlinden root 212, 3 Feb 21 10:20 frontend0 crw--- 1 tlinden root 212, 7 Feb 21 10:20 net0 I have seen other descriptions of similar problems with Conax CAMs, but I have not yet seen any solution. http://www.dvbforum.com/ubbthreads/ubbthreads.php?ubb=showflat&Number=31907&page=21 It seems that the CineView is working well for people who don't have Conax encryption. How can one get debugging information from the CI-module, CAM and the PC-card to see why the initialization fails? Is the pcsc-lite package of any use in connection with these kinds of smart cards? http://pcsclite.alioth.debian.org/ Best regards,Tomas Lindén___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Recording using a TwinHan VisionDVT terrestial card
Hello, (If these are FAQs I'd appreciate links. The search engine at http://www.linuxtv.org/cgi-bin/htwrap.pl doesn't give any results at all when searching for "record", so I suspect there's some error there, and googling doesn't give any real useful hits either. I've looked through linuxtv.org, linuxdvb.tv and a few other sites without finding what I want.) I want to to record using my TwinHan VisionDVT terrestial card. Using mplayer -dumpfile file.ts -dumpstream dvb://CHANNEL as described on http://www.mplayerhq.hu/DOCS/HTML-single/en/MPlayer.html works, but I'm wondering if there's a better way of doing this that people on this list prefer. I've been using nvrec with transcode for several months to record analog stuff, and am looking for similar solutions for digital recording. What I want are simple command-line tools that can easily be put in scripts run through crontab. DVR and ProjectX looks like overkill for what I want (although ProjectX's A/V sync stuff sounds good). The recording is to be done on a headless machine without TV-out, and the files are then transferred to another machine for viewing. When using mplayer on a fast Athlon XP machine the CPU utilization stays below 1% according to top, and the file size is somewhere aroung 2GB/hour, which is fine, as I want to put the card into an older and much slower machine which also has other tasks such as acting as an ssh and www server, and thus don't want to waste CPU cycles on anything but that which is needed to dump the stream to disk (well, I guess A/V sync is worth spending some CPU time on). Any processing (with the possible exception of A/V sync) is done on the transport stream file when the recording finishes, not while recording. Also, is there some way of recording two channels simultaneously using only one card? Is such a thing dependent on the card or the drivers? I just get error messages from mplayer when I start up a second recording, or try to view a second channel while recording: DVB CONFIGURATION IS EMPTY, exit Failed to open dvb://CHANNEL2 The TwinHan web page for the card, located at http://www.twinhan.com/visiontv-2_2.htm , mentions "Viewing and Recording Different DTV Channels Simultaneously" which to me sounds like it should be possible to record two channels simultaneously, as it seems the card should be able to deliver (at least) two channel streams simultaneously. >From what I can understand of the Metzler brothers' "The Linux DVB API" paper, recording simultaneoulsy from two different channels should be possible if the separation of transport streams is done in software and not hardware, and one manages to grab data from the frontend instead of the demux. Am I wrong about this? Using Linux kernel 2.6.6 with the included DVB drivers: # lsmod Module Size Used by dst14732 1 dvb_bt8xx 8068 0 dvb_core 87080 2 dst,dvb_bt8xx crc32 4352 1 dvb_core bt878 11568 2 dst,dvb_bt8xx tuner 18444 0 bttv 152364 3 dvb_bt8xx,bt878 video_buf 21060 1 bttv i2c_algo_bit9736 1 bttv btcx_risc 4808 1 bttv i2c_core 23492 4 dvb_bt8xx,tuner,bttv,i2c_algo_bit nvidia 2071432 22 rtc12664 0 # ls -l /dev/dvb/adapter0 total 0 crw-rw1 root video250, 1 Jun 8 16:15 audio0 crw-rw1 root video250, 6 Jun 8 16:15 ca0 crw-rw1 root video250, 4 Jun 8 16:15 demux0 crw-rw1 root video250, 5 Jun 8 16:15 dvr0 crw-rw1 root video250, 3 Jun 8 16:15 frontend0 crw-rw1 root video250, 7 Jun 8 16:15 net0 crw-rw1 root video250, 8 Jun 8 16:15 osd0 crw-rw1 root video250, 0 Jun 8 16:15 video0 # Finally (yes!), a question about image quality: when I view live, or play back a recording, there seems to be some interlacing problem or similar. Fast vertical movements reveal horizontal lines, most obvious when a TV program is using a blue screen background for adding graphics, such as a weather report, but disturbing also when watching regular programs. /Tomas
[linux-dvb] Re: grr.. Any DVB-T adaptors which work reliably?
Hi Ragge I have the same card as you have but now it works OK. When I used the offical pre2 driver I had disturbances in both sound and picture but now when I:m using the .25 driver with your nice plugin for undertext all distubances are gone. The card likes a stable strong signal from the antenna. When disturbed for some reason VDR often crashes. I then need to use tzap to tune in the card again. I haven´t had time to investigate what is the problem. Now to my question: As you pointed out many cannels in Sweden are coded. VDR works OK for the free SVT channels but I can´t get it work for the other coded channels. My ViaAccess card reader is recognized by VDR and I can open the card under Setup in VDR. But no decoding. The advice from the VDR people was to use firmware decoding but I just couldn´t get that to work. VDR behaves strangely. I don´t know if this is a question for the VDR mailing list but I hope you have solved the problem. Tomas Sävenstedt citerar Ragnar Sundblad <[EMAIL PROTECTED]>: > > --On den 30 juni 2003 22:44 +0100 Edward Wildgoose <[EMAIL PROTECTED]> > wrote: > > > I just can't get this wretched TT DVB-T 1.2 card to work reliably > > at all!! > > > > Has ANYONE managed to get a DVB-T card working with VDR in a completely > > reliable way? > > I have had a bunch of problems with my TT DVB-T 1.2 too. > It now works quite reliably, but it still picks up of > interference from somewhere, I have audio clicks and picture > problems on some, but not all, channels. I very seldom have > firmware craches now. > > - At first I had lots of problem with just getting it to > tune at all. I think that it needs a very stable 12V that also > should preferably be a little bit above 12V, not 11.8V or lower. > I bought a new power supply and moved away a 12V fan connection > from the main board and got better results with the card. > I think the DC/DC converter for the tuning power is to weak, > it is some homebrew with a 555, and the voltage dips at higher > frequencies. > > - With a oscilloscope I see strange spikes on the I/F line from > the tuner to the demodulator. They are spaced at about 18,3MHz > which happens to be a third of the demodulators clock frequency. > Though it could be something else that I pick up with the scope > some strange way, I suspect that it is real and that it is a > hardware bug. Sadly, data sheets on these things are hard to > get, I suspect that there is a biasing problem on the demod > input or something like that, at least I would like to have > enough documentation to be able exclude those ideas that I have. > > - I have lines traveling down the tv screen when using the > composite output from the DVB-T card. I heard from another guy > that has both a DVB-T and a DVB-C that he has the same on the > DVB-T, but that the DVB-C is OK. > > - When I have the driver loaded/firmware booted/whatever does it, > my last tv in the antenna chain gets vertical or sloping lines > over the screen on analog channels. When I unload the driver, > the lines disappear. > > All in all, I am not very impressed by this card. > > > Now when I have some DVB-T friends on the line: > > Usa-x says that their DVB-T 1.2 cards look like this: > <http://www.usa-x.org/1shop/popup_image.php?pID=7&language=en> > My 1.2 card does not look like that, it has an ALPS tuner and > a SP8870 demodulator on the main board, like the one here: > <http://www.technotrend.de/english/products/pcproducts2-2.html>. > Does anyone know if the design has changed and they don't > really mean 1.2, or if they just have wrong picture? > > I have also been thinking of bying a Nova-T to see if I at least > can get better reception with that. There is a possibly new one > called 1.3, which could be studied here: > <http://www.usa-x.org/1shop/product_info.php? cPath=3&products_id=34&languag > e=en>, pdf here: <http://www.usa-x.org/1/T1300.pdf>. > This one looks like it could at least be fitted with a > CI connector (yes, some DVB-T channels in Sweden are encrypted). > Does anyone know if one gets this card if you buy a Hauppauge > Nova-T, or if you get one without a CI connection? > Does anyone know if this card is supported by the driver? > Any recommendations? > > /ragge > > > > > -- > Info: > To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe > linux-dvb" as subject. > > Kets -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
[linux-dvb] Re: Help on use of DMX_OUT_TAP (II)
On Thu, 2003-06-05 at 00:27, James Green wrote: > What is special about ~9KB? The least common multiple of 188 and 204 is 9588. ;-) Tomas -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
