[linux-dvb] MSI 580 MegaSky - cannot lock channel
Greetz, I have Ubuntu-Edgy kernel 2.6.17-10-generic USB Device: MSI MegaSky 580 id 5580 Compiled Installed latest drivers and loaded module as follows: [17179598.452000] dvb-usb: downloading firmware from file 'dvb-usb-megasky-02.fw' [17179599.064000] dvb_usb_m920x: probe of 5-5:1.0 failed with error 64 [17179599.064000] usbcore: registered new driver usb-storage [17179599.068000] usbcore: registered new driver dvb_usb_m920x [17179599.172000] usb 5-5: USB disconnect, address 4 [17179599.412000] usb 5-5: new high speed USB device using ehci_hcd and address 6 [17179599.556000] usb 5-5: configuration #1 chosen from 1 choice [17179599.556000] dvb-usb: found a 'MSI Mega Sky 580 DVB-T USB2.0' in warm state. [17179599.556000] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [17179599.704000] dvb-usb: schedule remote query interval to 100 msecs. [17179599.704000] dvb-usb: MSI Mega Sky 580 DVB-T USB2.0 successfully initialized and connected. Problem: Using Kaffeine to scan for channels in Australia, cannot lock lock onto channels. I can see it trying, the USB device LED lights up while scanning and I can see SNR up to 75% while scanning, but no lock on. Any help would be appreciated. ~Sam. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Another Nova-T 500 Dual DVB-T Oops
Matt Doran wrote: Torgeir Veimo wrote: Can you include some output from /var/log/messages before the oops itself? In my case I see USB disconnects, then an oops from something unrelated just after that. You're right. There's a USB disconnect before this occurs. The messages are attached. The same occurs with the other set oops's I've seen too. Thanks, Matt This oops seems to be fairly regular. I got another one today. I see the USB disconnect again, but a slightly different stack. See attached. Some more info: * From the timing of this oops, I know that Myth was just about to start recording with this tuner. * My machine is a dual core AMD 3600+ AM2. Thanks, Matt usb 2-1: USB disconnect, address 2 mt2060 I2C write failed mt2060 I2C write failed dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully deinitialized and disconnected. BUG: unable to handle kernel paging request at virtual address 322e384c printing eip: f8ac3bc3 *pde = Oops: [#1] SMP Modules linked in: binfmt_misc rfcomm l2cap bluetooth powernow_k8 cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_conservative video sbs i2c_ec dock button battery container ac asus_acpi backlight mt352 saa7134_dvb video_buf_dvb tda1004x lirc_imon(F) lirc_dev sbp2 ieee1394 lp mt2060 ipv6 saa7134_alsa dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc dibx000_common snd_hda_intel snd_hda_codec saa7134 sg video_buf compat_ioctl32 ir_kbd_i2c ir_common videodev v4l2_common psmouse snd_pcm_oss snd_mixer_oss snd_mpu401 snd_mpu401_uart snd_rawmidi snd_seq_device v4l1_compat serio_raw snd_pcm snd_timer snd analog gameport ata_generic i2c_nforce2 floppy parport_pc parport pcspkr evdev shpchp pci_hotplug soundcore snd_page_alloc k8temp nvidia(P) agpgart i2c_core usbhid hid ext3 jbd mbcache uhci_hcd forcedeth ohci_hcd ehci_hcd usbcore ide_generic ide_cd cdrom sd_mod sata_nv libata scsi_mod generic amd74xx thermal process fan fbcon tileblit font bitblit softcursor vesafb capability commoncap CPU:1 EIP:0060:[pg0+946133955/1069057024]Tainted: PF VLI EFLAGS: 00010282 (2.6.20-4-generic #2) EIP is at dvb_dmxdev_buffer_read+0x13/0x1a0 [dvb_core] eax: 322e384c ebx: 322e384c ecx: aa243008 edx: 0800 esi: edi: f44bbfa0 ebp: 002b07a0 esp: f44bbf34 ds: 007b es: 007b ss: 0068 Process mythbackend (pid: 13886, ti=f44ba000 task=ca50da90 task.ti=f44ba000) Stack: f44bbf68 aa243008 0800 f44bbf68 c02e5862 0001 f44bbf68 f44bbfa0 aa243008 f44bbfa0 002b07a0 f8ac3d81 002b07a0 f44bbfa0 cf7f6440 aa243008 c017331c f44bbfa0 f8ac3d50 cf7f6440 fff7 a348826c Call Trace: [do_nanosleep+82/112] do_nanosleep+0x52/0x70 [pg0+946134401/1069057024] dvb_dvr_read+0x31/0x40 [dvb_core] [vfs_read+188/400] vfs_read+0xbc/0x190 [pg0+946134352/1069057024] dvb_dvr_read+0x0/0x40 [dvb_core] [sys_read+65/112] sys_read+0x41/0x70 [sysenter_past_esp+95/137] sysenter_past_esp+0x5f/0x89 === Code: c7 04 24 18 e3 ac f8 e8 8c 10 66 c7 eb 9c 8d 76 00 8d bc 27 00 00 00 00 55 57 56 31 f6 53 89 c3 83 ec 20 89 54 24 08 89 4c 24 04 8b 10 85 d2 0f 84 f7 00 00 00 8b 40 10 85 c0 0f 85 e3 00 00 00 EIP: [pg0+946133955/1069057024] dvb_dmxdev_buffer_read+0x13/0x1a0 [dvb_core] SS:ESP 0068:f44bbf34 6usb 2-1: new high speed USB device using ehci_hcd and address 3 usb 2-1: configuration #1 chosen from 1 choice dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Some more infos about Terratec Cinergy T USB XE
Greetings, after sending the required data (photos, etc) to Gunther I'm posting here the (very poors) informations I discovered by opening the chassis of the device: From what I see nor the USB interface chip neither the DVB receiver are from well-known vendors. The first has the following signature: Wellmax UT2000 062401 from a short Internet search I wasn't able to find any interesting reference to this product/vendor. The second has a logo like a square radiating from one edge and the following: M/2060F 0JF2 0007J 1006-A4 Again, I was not able to retrieve any further infos, so it would be very appreciated if anyone reading this thread could give me some more. Many Thanks, Marco ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Pinnacle 250i(?) can someone provide tips for me to create a patch for this?]]
---BeginMessage--- Hans-Frieder Vogt wrote: Hello Dougie, nice to hear that somebody else in the list also has one of these new Pinnacle DVB cards. I own a PCTV 2000i (or PCTV Dual DVB-t Pro PCI) for which I would like to provide a driver at some time. The main task is in my eyes to support the Pinnacle DTV bridge, which is/will be used in a number of cards, single and dual tuner DVB-t, DVB-S and DVB-S2 cards. However, at the moment I am in a very early stage of driver development (precisely: still trying to understand how that DTV bridge works) and so I expect that it will need quite a while (weeks, months, ...) until I will be able to even start writing the driver. I see... I was hoping that the individual chips were already supported somewhere, making the process easier. I read somewhere that Pinnacle were quite helpful in the development of other drivers. Can't find the page again, but their statement on the page below suggests they might offer technical information on the chip. I'd like to see the information they supply, but I probably don't have enough time to commit to it at the moment :( http://tinyurl.com/392abd Cheers, Dougie ---End Message--- ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] dvico fusionhdtv dbvt-nano2
Nils Winkler wrote: Hi, I have a new LG W1 notebook, which has a built in DViCO FusionHDTV DVBT-Nano2 (that's what the Windows hardware manager says). I'm running Fedora Core 6 and installed the HG version of v4l-dvb (including the Bluebird firmware), but the card doesn't work, no sign of it in dmesg whatsoever. I have attached the output of lsmod and lsusb -v. Can someone please check if this card is supported by v4l? The device will never be supported by v4l. This is a DVB device, which provides digital streams. V4L only deals with analog video, which this device does not provide. Luckily, you've written to the linux-dvb mailing list, and this is the right place for questions about DVB devices. Unfortunately, your device is not yet supported, and the dvb-usb-bluebird-01.fw version of the Bluebird firmware is not compatible with your device. Adding support for this device is on my to-do list, but it is going to be a while before I get there. If you want to help speed along the process, then please take a usbsnoop of the driver traffic while in windows, and post it to a web server somewhere for me to look at. Cheers, Michael Krufky ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [PATCH] Add PHYS-string and connecton to pci-device for nicer usage by udev
Matthias Schwarzott wrote: Hi Oliver, hi Mailing list! Sent second time, this time with signed-off-by, and to maintainer of changed code. Sorry for the delay. I'm very busy these days. On Wednesday 10 January 2007 18:34, Matthias Schwarzott wrote: The attached patch a PHYS-string and a connection to the relevant pci-device to let udev now this and create more user-friendly/persistent links on the event-device. Code with some changes taken from budget-ci.c With that patch, udev-103 creates: /dev/input/by-path/pci-\:00\:0a.0--event-ir Thanks, applied. Nevertheless input-handling for av7110 needs some changes: one can for example only use input-connector of first card. Not quite correct. You can use the ir receiver of *any* card (tested!). All receivers share the same (1) input device (2) keymap (3) protocol type, inversion setting, device address It is easy to fix (1) and (2), but I have no good idea how to fix (3) for multiple av7110 cards. Oliver -- VDR Remote Plugin 0.3.9 available at http://www.escape-edv.de/endriss/vdr/ ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Fw: Bug with video cards.
Begin forwarded message: Date: Sun, 21 Jan 2007 11:28:38 +0100 From: [EMAIL PROTECTED] To: linux-kernel@vger.kernel.org Subject: Bug with video cards. Dear reader, I would like to report a bug with video cards of which I guess it is located in the kernel (but not certain). It is only happening in FC6 not in Suse 10.2). However I like FC6 better as Suse 10.2 and I would like to see this bug fixed. I tried to install a bluecherry PV149 video capture card and after a lot of investigations it turns out the framebuffer address is wrongly set. The link on which you can follow the issue: http://www.zoneminder.com/forums/viewtopic.php?t=7836 Also other people with other HW are experiencing the same kind of issues. Here are some logs: [EMAIL PROTECTED] ~]# dmesg |grep -2 bttv audit(1168711540.490:2): selinux=0 auid=4294967295 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 :03:08.0[A] - GSI 21 (level, low) - IRQ 169 bttv0: Bt878 (rev 17) at :03:08.0, irq: 169, latency: 32, mmio: 0xef00 bttv0: detected: Provideo PV150A-1 [card=98], PCI subsystem ID is aa00:1460 bttv0: using: ProVideo PV150 [card=98,autodetected] bttv0: gpio: en=, out= in=00ff [init] bttv0: using tuner=-1 bttv0: i2c: checking for TDA9875 @ 0xb0... not found bttv0: i2c: checking for TDA7432 @ 0x8a... not found bttv0: i2c: checking for TDA9887 @ 0x86... not found bttv0: registered device video0 bttv0: registered device vbi0 bttv0: PLL: 28636363 = 35468950 .. ok bttv: Bt8xx card found (1). ACPI: PCI Interrupt :03:09.0[A] - GSI 22 (level, low) - IRQ 193 bttv1: Bt878 (rev 17) at :03:09.0, irq: 193, latency: 32, mmio: 0xee00 bttv1: detected: Provideo PV150A-2 [card=98], PCI subsystem ID is aa01:1461 bttv1: using: ProVideo PV150 [card=98,autodetected] bttv1: gpio: en=, out= in=00ff [init] bttv1: using tuner=-1 bttv1: i2c: checking for TDA9875 @ 0xb0... not found bttv1: i2c: checking for TDA7432 @ 0x8a... not found bttv1: i2c: checking for TDA9887 @ 0x86... not found bttv1: registered device video1 bttv1: registered device vbi1 bttv1: PLL: 28636363 = 35468950 .. ok bttv: Bt8xx card found (2). ACPI: PCI Interrupt :03:0a.0[A] - GSI 23 (level, low) - IRQ 177 bttv2: Bt878 (rev 17) at :03:0a.0, irq: 177, latency: 32, mmio: 0xed00 bttv2: detected: Provideo PV150A-3 [card=98], PCI subsystem ID is aa02:1462 bttv2: using: ProVideo PV150 [card=98,autodetected] bttv2: gpio: en=, out= in=00ff [init] bttv2: using tuner=-1 bttv2: i2c: checking for TDA9875 @ 0xb0... not found bttv2: i2c: checking for TDA7432 @ 0x8a... not found bttv2: i2c: checking for TDA9887 @ 0x86... not found bttv2: registered device video2 bttv2: registered device vbi2 bttv2: PLL: 28636363 = 35468950 .6hdc: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.20 bt878: Unknown symbol bttv_read_gpio bt878: Unknown symbol bttv_write_gpio bt878: Unknown symbol bttv_gpio_enable .4bt878: Unknown symbol bttv_read_gpio bt878: Unknown symbol bttv_write_gpio bt878: Unknown symbol bttv_gpio_enable ok bttv: Bt8xx card found (3). ACPI: PCI Interrupt :03:0b.0[A] - GSI 20 (level, low) - IRQ 201 bttv3: Bt878 (rev 17) at :03:0b.0, irq: 201, latency: 32, mmio: 0xec00 bttv3: detected: Provideo PV150A-4 [card=98], PCI subsystem ID is aa03:1463 bttv3: using: ProVideo PV150 [card=98,autodetected] bttv3: gpio: en=, out= in=00ff [init] bttv3: using tuner=-1 bttv3: i2c: checking for TDA9875 @ 0xb0... not found bttv3: i2c: checking for TDA7432 @ 0x8a... not found bttv3: i2c: checking for TDA9887 @ 0x86... not found bttv3: registered device video3 bttv3: registered device vbi3 bttv3: PLL: 28636363 = 35468950 .6hdd: ATAPI 32X CD-ROM CD-R/RW drive, 4096kB Cache, DMA . ok bt878: AUDIO driver version 0.0.0 loaded [EMAIL PROTECTED] ffmpeg]# xawtv This is xawtv-3.95, running on Linux/i686 (2.6.18-1.2849.fc6) WARNING: v4l-conf is compiled without DGA support. WARNING: couldn't find framebuffer base address, try manual configuration (v4l-conf -a addr) ioctl: VIDIOC_OVERLAY(int=1): Invalid argument ioctl: VIDIOC_OVERLAY(int=1): Invalid argument ioctl: VIDIOC_OVERLAY(int=1): Invalid argument ioctl: VIDIOC_OVERLAY(int=1): Invalid argument [EMAIL PROTECTED] dev]# xawtv -hwscan This is xawtv-3.95, running on Linux/i686 (2.6.18-1.2849.fc6) looking for available devices /dev/video0: OK [ -device /dev/video0 ] type : v4l2 name : BT878 video (ProVideo PV150) flags: overlay capture /dev/video1: OK [ -device /dev/video1 ] type : v4l2 name : BT878 video (ProVideo PV150) flags: overlay capture /dev/video2: OK [ -device /dev/video2 ] type : v4l2 name : BT878 video (ProVideo PV150) flags: overlay capture /dev/video3: OK [ -device /dev/video3 ] type : v4l2 name : BT878 video (ProVideo PV150) flags: overlay capture No it is not the HW. I have
Re: [linux-dvb] Another Nova-T 500 Dual DVB-T Oops
Hi, On my myth box I have a simple script that checks messages every 10sec and reboots if the usb disconnect line appears, I collect timestamped copies of the messages files. A distinct pattern i still to occur, but some channels are worse than others, but that might be time of day caused reception variations. Starting recording 3min ahead gives the box time to reboot and resume recording. /Henrik On 1/24/07, Matt Doran [EMAIL PROTECTED] wrote: Matt Doran wrote: Torgeir Veimo wrote: Can you include some output from /var/log/messages before the oops itself? In my case I see USB disconnects, then an oops from something unrelated just after that. You're right. There's a USB disconnect before this occurs. The messages are attached. The same occurs with the other set oops's I've seen too. Thanks, Matt This oops seems to be fairly regular. I got another one today. I see the USB disconnect again, but a slightly different stack. See attached. Some more info: - From the timing of this oops, I know that Myth was just about to start recording with this tuner. - My machine is a dual core AMD 3600+ AM2. Thanks, Matt usb 2-1: USB disconnect, address 2 mt2060 I2C write failed mt2060 I2C write failed dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully deinitialized and disconnected. BUG: unable to handle kernel paging request at virtual address 322e384c printing eip: f8ac3bc3 *pde = Oops: [#1] SMP Modules linked in: binfmt_misc rfcomm l2cap bluetooth powernow_k8 cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_ondemand freq_table cpufreq_conservative video sbs i2c_ec dock button battery container ac asus_acpi backlight mt352 saa7134_dvb video_buf_dvb tda1004x lirc_imon(F) lirc_dev sbp2 ieee1394 lp mt2060 ipv6 saa7134_alsa dvb_usb_dib0700 dib7000m dib7000p dvb_usb dvb_core dvb_pll dib3000mc dibx000_common snd_hda_intel snd_hda_codec saa7134 sg video_buf compat_ioctl32 ir_kbd_i2c ir_common videodev v4l2_common psmouse snd_pcm_oss snd_mixer_oss snd_mpu401 snd_mpu401_uart snd_rawmidi snd_seq_device v4l1_compat serio_raw snd_pcm snd_timer snd analog gameport ata_generic i2c_nforce2 floppy parport_pc parport pcspkr evdev shpchp pci_hotplug soundcore snd_page_alloc k8temp nvidia(P) agpgart i2c_core usbhid hid ext3 jbd mbcache uhci_hcd forcedeth ohci_hcd ehci_hcd usbcore ide_generic ide_cd cdrom sd_mod sata_nv libata scsi_mod generic amd74xx thermal process fan fbcon tileblit font bitblit softcursor vesafb capability commoncap CPU:1 EIP:0060:[pg0+946133955/1069057024]Tainted: PF VLI EFLAGS: 00010282 (2.6.20-4-generic #2) EIP is at dvb_dmxdev_buffer_read+0x13/0x1a0 [dvb_core] eax: 322e384c ebx: 322e384c ecx: aa243008 edx: 0800 esi: edi: f44bbfa0 ebp: 002b07a0 esp: f44bbf34 ds: 007b es: 007b ss: 0068 Process mythbackend (pid: 13886, ti=f44ba000 task=ca50da90 task.ti=f44ba000) Stack: f44bbf68 aa243008 0800 f44bbf68 c02e5862 0001 f44bbf68 f44bbfa0 aa243008 f44bbfa0 002b07a0 f8ac3d81 002b07a0 f44bbfa0 cf7f6440 aa243008 c017331c f44bbfa0 f8ac3d50 cf7f6440 fff7 a348826c Call Trace: [do_nanosleep+82/112] do_nanosleep+0x52/0x70 [pg0+946134401/1069057024] dvb_dvr_read+0x31/0x40 [dvb_core] [vfs_read+188/400] vfs_read+0xbc/0x190 [pg0+946134352/1069057024] dvb_dvr_read+0x0/0x40 [dvb_core] [sys_read+65/112] sys_read+0x41/0x70 [sysenter_past_esp+95/137] sysenter_past_esp+0x5f/0x89 === Code: c7 04 24 18 e3 ac f8 e8 8c 10 66 c7 eb 9c 8d 76 00 8d bc 27 00 00 00 00 55 57 56 31 f6 53 89 c3 83 ec 20 89 54 24 08 89 4c 24 04 8b 10 85 d2 0f 84 f7 00 00 00 8b 40 10 85 c0 0f 85 e3 00 00 00 EIP: [pg0+946133955/1069057024] dvb_dmxdev_buffer_read+0x13/0x1a0 [dvb_core] SS:ESP 0068:f44bbf34 6usb 2-1: new high speed USB device using ehci_hcd and address 3 usb 2-1: configuration #1 chosen from 1 choice dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state. dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T). ___ 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] Nova-T 500 Dual DVB-T Remote control
Since kernel 2.6.20-rc4 Nova-T 500 Dual DVB-T are almost usable (only one usb disconnect with the following kernel oops since 10 Jan until now). So I thought that I should try to get the included remote control to work as well but can't find any info on what type of interface it's using. Does anyone have a clue? /Richard ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
