Re: [ivtv-devel] Re: 0.5.0 progress report
I'm cross-posting this at V4L mailing list, since this subject is better handled at V4L list. The basic idea for shapshot is to provide a stable snapshot of V4L from my point of view. It doesn't mean that it will works with every kernel release. If you guys are willing to test V4L against other versions, that would help us to improve the snapshot process. If so, please, send me patches to fix broken stuff against these versions and I'll be happy in applying it to V4L CVS. I can also generate a snap that would fit better the needs you're addressing, and recall it as release, providing that you guys helps us. We do, from time to time, a code freezing on CVS. We may agree to code freeze by about a week, to allow better testing, including testing with older kernel versions. After the end, I can generate such release. Em Qui, 2005-11-10 às 10:45 -0500, Tyler Trafford escreveu: Axel Thimm wrote: snip:v4l These are cvs snapshots, not releases. They should be more stable than checking out cvs at a random time like I tried yesterday. FWIW, my understanding is that Mauro is planning on making these monthly releases to be known working, and not just a snapshot from some random day of the month. -- Mauro Carvalho Chehab [EMAIL PROTECTED] ___ Yahoo! Acesso Grátis: Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] [ANNOUNCEMENT]: released unstable ivtv-0.5.0: please test!
Hi all, I've just released ivtv-0.5.0, the first release in the 0.5.x development series. It can be downloaded here: http://dl.ivtvdriver.org/ivtv/archive/0.5.x/ivtv-0.5.0.tar.gz Please test this version: especially on 2.4 or older 2.6 platforms. The main focus of this release is to see if it compiles on older platforms: not only the driver itself but also the v4l CVS repository. The latter hasn't been tested very extensively and this makes a good test case. Note that the firmware is now uploaded through the hotplug mechanism, so the location is changed to the firmware directory used by the hotplug tools. Look for the file 'firmware.agent' (usually somewhere in /etc/hotplug) and look for the line containing: FIRMWARE_DIR=/usr/lib/hotplug/firmware This is the directory where the firmware should be placed. Also note that the firmware names have changed: ivtv-fw-enc.bin- v4l-cx2341x-enc.fw ivtv-fw-dec.bin- v4l-cx2341x-dec.fw HcwMakoA.ROM - v4l-cx25840.fw ivtv_init_mpeg.bin - v4l-cx2341x-init-mpeg.bin Please report any problems on the ivtv-devel list! Enjoy, Hans Verkuil IVTV changes: - removed tveeprom, tuner, v4l1-compat, msp3400 and tda9887 in favor of the versions in v4l. - moved saa7115, saa7127, cx25840, wm8775 and cs53l32a to v4l. - use v4l2 API to communicate with those modules (in preparation of phasing out v4l1 support). - renamed firmwares/init-mpeg to be more consistent: ivtv-fw-enc.bin- v4l-cx2341x-enc.fw ivtv-fw-dec.bin- v4l-cx2341x-dec.fw HcwMakoA.ROM - v4l-cx25840.fw ivtv_init_mpeg.bin - v4l-cx2341x-init-mpeg.bin - lots of smaller ivtv cleanups. - added internals documentation (used to float around on several internet pages, it's now part of the driver documentation). - setting a register of the saa7115 or saa7127 now requires root permissions. - hotplug support is required to load the firmware. You should place the firmware files in the hotplug directory. - add support for old-style PVR350 (with a saa7114 instead of a saa7115). - fix a few misdetected Hauppauge cards. - fix MODULE_AUTHOR lists. - fix VBI support in the passthrough mode. - cx25840ctl now uses the raw I2C API to access the cx25840. - updated several utilities to use getopt for better commandline handling. - utils/videodev2.h copy removed in favor of v4l supplied header. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] problems playing video directly from /dev/video0
paul wrote: I have some difficulties with playing video from my PVR350 directly from /dev/video0 using mplayer. After a few minutes, the screen gets updated very slowly and will hang shortly after. I can play DVD's without problems. When I do cat /dev/video0 file.mpg and mplayer file.mpg I do not have any issues either. There are no message in dmesg or in /var/log. mplayer says my 2.4GHz P4 is too slow(?) and suggests to use different output drivers (ao and vo) but I am unable to get to a working solution. Is this a known issue? Is there maybe a solution? If not, how can I help debugging this? Thanks, Paul I found that when I use debug=3 (ivtvctl -D 3) I do not have above problem anymore ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] ivtv framebuffer is broken with PVR350
I have been posting about freezing playback and ivtv-osd warnings, and ivtv DEC warnings in the ivtv-users list sinsce I am using 0.4.0 stable. I tried to provide enough detail to solicit some help but nobody has responded.I think I have done enough debugging to narrow the problem down to the ivtv driver andbased on that have filed abug report (#53) in the Trac system. Ticket URL: http://ivtvdriver.org/trac/ticket/53 You can find my previous poststo ivtv-users here: http://www.ivtvdriver.org/pipermail/ivtv-users/2005-November/000184.html http://www.ivtvdriver.org/pipermail/ivtv-users/2005-November/000239.html If I need to post somewhere else, let me know where. If you need more infomation "". Yesterday I went so far as to disable tvout, and not load ivtv-fb and just playback directly to my monitor without using framebuffer or xdriver. When I did this I was able to playback a two hour movie without any freezes. This to me indicates the problem is somewhere in either the framebuffer or xdriver interface. I would like to do whatever I can to support the development of this project, I am willing and able to capture any kind of debug information that might be requested. Are there any develpers out there that have any interest in this failure? It may be specific to smp cores, I don't know how many are developing systems with smp processors. Regards,Steve Regards,Steve ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] Dual PVR 250s detected as 350s
Hello, I am running ivtv version 0.4.0, and I have dual PVR-250s. Problem is, both of these cards are detected as 350s. I think the warnings reported below are because the ivtv driver thinks I have 350s so it is trying to set up the onboard decoder? Other than the weirdness of the messages, both 250s seem to work fine. I have tried to override this in my modprobe.conf, but it has not worked. If I leave out the options ivtv line, or put it in, it behaves the same either way. Maybe I should just leave well enough alone? Any ideas? Thanks! ivtv: START INIT IVTV ivtv: version 0.4.0 (tagged release) loading ivtv: Linux version: 2.6.12-1.1378_FC3 686 REGPARM 4KSTACKS gcc-3.4 ivtv: In case of problems please include the debug info ivtv: between the START INIT IVTV and END INIT IVTV lines when ivtv: mailing the ivtv-devel mailinglist. ivtv0: User specified WinTV PVR 350 card (detected iTVC16 based chip) ACPI: PCI Interrupt :01:06.0[A] - Link [LNK1] - GSI 11 (level, low) - IRQ 11 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tveeprom: Hauppauge: model = 32062, rev = C182, serial# = 2909019 tveeprom: tuner = LG TAPC H791F (idx = 82, type = 39) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio_processor = MSP3445 (type = 12) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] msp34xx: init: chip=MSP3445G-B8 +nicam +simple +simpler +radio mode=simpler ivtv0: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40] msp34xxg: daemon started ivtv0: loading /lib/modules/ivtv-fw-enc.bin ivtv0: Encoder revision: 0x02050032 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv0: Create encoder radio stream ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) ivtv0: Create decoder VOUT stream ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) ivtv0 warning: Failed api call 0x001a with result 0xfff0 ivtv0: ivtv_init_mpeg_decoder failed to set decoder source tuner 0-0061: type set to 39 (LG NTSC (newer TAPC series)) ivtv0 warning: i2c client addr: 0x44 not found for command 0x40046502! ivtv0 warning: Failed api call 0x0010 with result 0xfff0 ivtv0: Initialized WinTV PVR 350, card #0 ivtv: == NEXT CARD == ivtv1: User specified WinTV PVR 350 card (detected iTVC16 based chip) ACPI: PCI Interrupt :01:07.0[A] - Link [LNK2] - GSI 3 (level, low) - IRQ 3 ivtv1: Unreasonably low latency timer, setting to 64 (was 32) ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50] ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1) saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #1) ivtv1: i2c attach to card #1 ok [client=saa7115, addr=21] msp34xx: init: chip=MSP3448W-A2 +nicam +simple +simpler +radio mode=simpler ivtv1: i2c attach to card #1 ok [client=MSP3448W-A2, addr=40] msp34xxg: daemon started tveeprom: Hauppauge: model = 32032, rev = B326, serial# = 7193996 tveeprom: tuner = Temic 4036FY5 (idx = 26, type = 8) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio_processor = MSP3440 (type = 11) ivtv1: loading /lib/modules/ivtv-fw-enc.bin ivtv1: Encoder revision: 0x02050032 ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv1: Create encoder radio stream ivtv1: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) ivtv1: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) ivtv1: Create decoder VOUT stream ivtv1: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) ivtv1 warning: Failed api call 0x001a with result 0xfff0 ivtv1: ivtv_init_mpeg_decoder failed to set decoder source tuner 1-0061: type set to 8 (Temic NTSC (4036 FY5)) ivtv1 warning: i2c client addr: 0x44 not found for command 0x40046502! ivtv1 warning: Failed api call 0x0010 with result 0xfff0 ivtv1: Initialized WinTV PVR 350, card #1 ivtv: END INIT IVTV alias char-major-61 lirc_i2c alias eth0 forcedeth alias snd-card-0 snd-intel8x0 options snd-card-0 index=0
Re: [ivtv-devel] Noob question about ivtv driver version
Just wanted to follow up on this thread to let everyone know what became of this issue. First, I gave up on the 500 and returned it in exchange for another 250. So now, I have dual 250s. I installed one of the 250s and went through the motions of trying to validate the feed on /dev/video0 using the methods described in Jarods guide (http://wilsonet.com/mythtv/fcmyth.php). I was never able to get this to work (I have the 0.4.0 driver). I was able to do this quite successfully when I was on the old 0.2.x driver. Rather than continue to struggle with this validation step, I decided to just fire up mythtvsetup and configure this capture card, and, voila, it worked! Then, I added the second 250, configured it, and it worked too. I was never able to get a satisfactory test by running mplayer on a sampling of either /dev/video0 or /dev/video1. I suspect that the 500 I ended up returning would have worked as well, but I never got past the diagnostics to find out whether it would have worked in myth. I should have done this, but it's too late now (sigh). I think the ultimate problem is that with the upgrade from 0.2.x to 0.4.0, the diagnostics procedure I was trying to use is now obsolete. If anyone can elaborate on the proper methodology to test a capture card with the ivtv 0.4.0 driver, it might help those who are still trying to solve this issue. A search of this database seems to suggest I was not the only one fighting this issue. Maybe if we are all nice to Jarod (or send him gobs of money), he will update his How-to :) LarryOn 10/19/05, Timothy McFadden [EMAIL PROTECTED] wrote: On 10/18/05, Larry K [EMAIL PROTECTED] wrote:5) Installed the mkinitrd changes and recreated my boot image.Can anyone explain why this is necessary for the PVR-500?Based on Jarod's site, it appears this change is necessary for the PVR-350 since it has on-board TV-out and piping X over that requires some modules be made available in the boot image?Hi Larry.I don't think this was neccessary because you are using a PVR-500. You are right in that it's only for PVR-350 users who are usingTV-OUT.The purpose is to get IVTV loaded soon enough that you cansee the machine boot up ( rhgb, log in, etc ).It's not arequirement.In fact, I don't use it anymore.It's just nice to have. ( I'll probably wind up putting it back in to mine ).It's been a while, but do you need the following lines in modprobe.conf?install tveeprom /sbin/modprobe tveeprominstall ivtv /sbin/modprobe --ignore-install ivtv; /sbin/modprobe ivtv-fb install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2cI'm not using ivtv_4.0 yet so I don't know if this was changed.-Tim___ ivtv-devel mailing listivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] Re: Dual PVR 250s detected as 350s
Doh! Looks like I had two entries in my modprobe.conf to set the cardtype. Once I removed the duplicate entry and did a shutdown/reboot, the system came up and detected dual 250s. Thanks for listening :)On 11/12/05, Larry K [EMAIL PROTECTED] wrote: Hello, I am running ivtv version 0.4.0, and I have dual PVR-250s. Problem is, both of these cards are detected as 350s. I think the warnings reported below are because the ivtv driver thinks I have 350s so it is trying to set up the onboard decoder? Other than the weirdness of the messages, both 250s seem to work fine. I have tried to override this in my modprobe.conf, but it has not worked. If I leave out the options ivtv line, or put it in, it behaves the same either way. Maybe I should just leave well enough alone? Any ideas? Thanks! ivtv: START INIT IVTV ivtv: version 0.4.0 (tagged release) loading ivtv: Linux version: 2.6.12-1.1378_FC3 686 REGPARM 4KSTACKS gcc-3.4 ivtv: In case of problems please include the debug info ivtv: between the START INIT IVTV and END INIT IVTV lines when ivtv: mailing the ivtv-devel mailinglist. ivtv0: User specified WinTV PVR 350 card (detected iTVC16 based chip) ACPI: PCI Interrupt :01:06.0[A] - Link [LNK1] - GSI 11 (level, low) - IRQ 11 ivtv0: Unreasonably low latency timer, setting to 64 (was 32) ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] tveeprom: Hauppauge: model = 32062, rev = C182, serial# = 2909019 tveeprom: tuner = LG TAPC H791F (idx = 82, type = 39) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio_processor = MSP3445 (type = 12) ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] tuner 0-0061: chip found @ 0xc2 (ivtv i2c driver #0) saa7115 0-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] msp34xx: init: chip=MSP3445G-B8 +nicam +simple +simpler +radio mode=simpler ivtv0: i2c attach to card #0 ok [client=MSP3445G-B8, addr=40] msp34xxg: daemon started ivtv0: loading /lib/modules/ivtv-fw-enc.bin ivtv0: Encoder revision: 0x02050032 ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv0: Create encoder radio stream ivtv0: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) ivtv0: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) ivtv0: Create decoder VOUT stream ivtv0: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) ivtv0 warning: Failed api call 0x001a with result 0xfff0 ivtv0: ivtv_init_mpeg_decoder failed to set decoder source tuner 0-0061: type set to 39 (LG NTSC (newer TAPC series)) ivtv0 warning: i2c client addr: 0x44 not found for command 0x40046502! ivtv0 warning: Failed api call 0x0010 with result 0xfff0 ivtv0: Initialized WinTV PVR 350, card #0 ivtv: == NEXT CARD == ivtv1: User specified WinTV PVR 350 card (detected iTVC16 based chip) ACPI: PCI Interrupt :01:07.0[A] - Link [LNK2] - GSI 3 (level, low) - IRQ 3 ivtv1: Unreasonably low latency timer, setting to 64 (was 32) ivtv1: i2c attach to card #1 ok [client=tveeprom, addr=50] ivtv1: i2c attach to card #1 ok [client=(tuner unset), addr=61] tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #1) saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #1) ivtv1: i2c attach to card #1 ok [client=saa7115, addr=21] msp34xx: init: chip=MSP3448W-A2 +nicam +simple +simpler +radio mode=simpler ivtv1: i2c attach to card #1 ok [client=MSP3448W-A2, addr=40] msp34xxg: daemon started tveeprom: Hauppauge: model = 32032, rev = B326, serial# = 7193996 tveeprom: tuner = Temic 4036FY5 (idx = 26, type = 8) tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) tveeprom: audio_processor = MSP3440 (type = 11) ivtv1: loading /lib/modules/ivtv-fw-enc.bin ivtv1: Encoder revision: 0x02050032 ivtv1: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) ivtv1: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) ivtv1: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) ivtv1: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB total) ivtv1: Create encoder radio stream ivtv1: Allocate DMA decoder MPEG stream: 16 x 65536 buffers (1024KB total) ivtv1: Allocate DMA decoder VBI stream: 512 x 2048 buffers (1024KB total) ivtv1: Create decoder VOUT stream ivtv1: Allocate DMA decoder YUV stream: 24 x 43200 buffers (1024KB total) ivtv1 warning: Failed api call 0x001a with result 0xfff0 ivtv1: ivtv_init_mpeg_decoder failed to set decoder source tuner 1-0061: type set to 8 (Temic NTSC (4036 FY5)) ivtv1 warning: i2c client addr: 0x44 not found for command 0x40046502! ivtv1 warning: Failed api call
RE: [ivtv-devel] ivtv framebuffer is broken with PVR350
Title: Re: [ivtv-devel] ivtv framebuffer is broken with PVR350 My box runs pretty cool, lots of air blowing past the PVR350. It does not get worse when the box warms up as opposed to when first booted an nice and chilly. Steve -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Jim ReithSent: Saturday, November 12, 2005 4:29 PMTo: Discussion list for development of the IVTV driverSubject: Re: [ivtv-devel] ivtv framebuffer is broken with PVR350 I have been posting about freezing playback and ivtv-osd warnings, and ivtv DEC warnings in the ivtv-users list sinsce I am using 0.4.0 stable. I tried to provide enough detail to solicit some help but nobody has responded.I think I have done enough debugging to narrow the problem down to the ivtv driver andbased on that have filed abug report (#53) in the Trac system. Ticket URL: http://ivtvdriver.org/trac/ticket/53 You can find my previous poststo ivtv-users here: http://www.ivtvdriver.org/pipermail/ivtv-users/2005-November/000184.html http://www.ivtvdriver.org/pipermail/ivtv-users/2005-November/000239.html If I need to post somewhere else, let me know where. If you need more infomation "". Yesterday I went so far as to disable tvout, and not load ivtv-fb and just playback directly to my monitor without using framebuffer or xdriver. When I did this I was able to playback a two hour movie without any freezes. This to me indicates the problem is somewhere in either the framebuffer or xdriver interface. I would like to do whatever I can to support the development of this project, I am willing and able to capture any kind of debug information that might be requested. Are there any develpers out there that have any interest in this failure? It may be specific to smp cores, I don't know how many are developing systems with smp processors. I will admit to not reading through your previous threads but you've eliminated the 350 overheating as a possible problem? Regards,Steve Regards,Steve ___ivtv-devel mailing listivtv-devel@ivtvdriver.orghttp://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
Re: [ivtv-devel] ivtv framebuffer is broken with PVR350
Le Samedi 12 Novembre 2005 20:34, Steve Laurie Sanders a écrit : I have been posting about freezing playback and ivtv-osd warnings, and ivtv DEC warnings in the ivtv-users list sinsce I am using 0.4.0 stable. I have the same problem, but no logs after the freeze, I have to reboot my PC. -- Jacques Facquet. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
[ivtv-devel] Multiple tuners: No sound on PVR-250 when PVR-350 added.
Greetings, I didn't get any response from ivtv-users so I'm hoping that there may be an answer here. I am at the end of my rope having gone over all the documentation, FAQ's and lists. I am having trouble configuring sound with a dual input setup. I have installed a PVR-250 and PVR-350 individually and they both work fine by themselves. When I put both cards in at the same time, I lose sound on the PVR-250. I am using ivtvdriver 0.4.0 and have been following Jarrod's instructions. I am using Fedora Core 4 Here is my lspci -v output for the cards and sound lspci -v start 00:1f.5 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio (rev 02) Subsystem: Hewlett-Packard Company: Unknown device 1249 Flags: bus master, medium devsel, latency 0, IRQ 9 I/O ports at 1200 [size=256] I/O ports at 1300 [size=64] 01:00.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR-350 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at ec00 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 01:01.0 Multimedia video controller: Internext Compression Inc iTVC16 (CX23416) MPEG-2 Encoder (rev 01) Subsystem: Hauppauge computer works Inc. WinTV PVR 250 Flags: bus master, medium devsel, latency 64, IRQ 10 Memory at f000 (32-bit, prefetchable) [size=64M] Capabilities: [44] Power Management version 2 lspci -v end Here is my dmesg output Nov 10 21:00:03 mythbox kernel: ivtv: START INIT IVTV Nov 10 21:00:03 mythbox kernel: ivtv: version 0.4.0 (tagged release) loading Nov 10 21:00:03 mythbox kernel: ivtv: Linux version: 2.6.13-1.1532_FC4 686 REGPARM 4KSTACKS gcc-4.0 Nov 10 21:00:03 mythbox kernel: ivtv: In case of problems please include the debug info Nov 10 21:00:03 mythbox kernel: ivtv: between the START INIT IVTV and END INIT IVTV lines when Nov 10 21:00:03 mythbox kernel: ivtv: mailing the ivtv-devel mailinglist. Nov 10 21:00:03 mythbox kernel: ivtv0: Autodetected WinTV PVR 350 card (iTVC15 based) Nov 10 21:00:03 mythbox kernel: PCI: Enabling device :01:00.0 (0014 - 0016) Nov 10 21:00:03 mythbox kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11 Nov 10 21:00:03 mythbox kernel: PCI: setting IRQ 11 as level-triggered Nov 10 21:00:03 mythbox kernel: ACPI: PCI Interrupt :01:00.0[A] - Link [LNKD] - GSI 11 (level, low) - IRQ 11 Nov 10 21:00:03 mythbox kernel: tveeprom: The eeprom says no radio is present, but the tuner type 68 Nov 10 21:00:03 mythbox kernel: tveeprom: indicates otherwise. I will assume that radio is present. Nov 10 21:00:03 mythbox kernel: tveeprom: ivtv version Nov 10 21:00:03 mythbox kernel: tveeprom: Hauppauge: model = 48132, rev = K268, serial# = 8207794 Nov 10 21:00:03 mythbox kernel: tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47) Nov 10 21:00:03 mythbox kernel: tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x1000) Nov 10 21:00:03 mythbox kernel: tveeprom: audio processor = MSP4448 (type = 1b) Nov 10 21:00:03 mythbox kernel: tveeprom: decoder processor = SAA7115 (type = 13) Nov 10 21:00:03 mythbox kernel: ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] Nov 10 21:00:03 mythbox kernel: tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 Nov 10 21:00:03 mythbox kernel: ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] Nov 10 21:00:03 mythbox kernel: saa7115 1-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) Nov 10 21:00:03 mythbox kernel: ivtv0: i2c attach to card #0 ok [client=saa7115, addr=21] Nov 10 21:00:03 mythbox kernel: saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) Nov 10 21:00:03 mythbox kernel: ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44] Nov 10 21:00:03 mythbox kernel: msp34xx: ivtv version Nov 10 21:00:03 mythbox kernel: msp34xx: init: chip=MSP3448W-A2, has NICAM support, simple (D) mode, simpler (G) no-thread mode Nov 10 21:00:03 mythbox kernel: msp34xx: $Id$ compiled on: Oct 21 2005 02:12:13 Nov 10 21:00:03 mythbox kernel: ivtv0: i2c attach to card #0 ok [client=MSP3448W-A2, addr=40] Nov 10 21:00:03 mythbox kernel: tda9885/6/7: (ivtv) chip found @ 0x86 Nov 10 21:00:03 mythbox kernel: ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43] Nov 10 21:00:03 mythbox kernel: ivtv0: loading /lib/modules/ivtv-fw-enc.bin Nov 10 21:00:03 mythbox kernel: ivtv0: loading /lib/modules/ivtv-fw-dec.bin Nov 10 21:00:03 mythbox kernel: ivtv0: Encoder revision: 0x02050032 Nov 10 21:00:03 mythbox kernel: ivtv0: Decoder revision: 0x02020023 Nov 10 21:00:03 mythbox kernel: ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB total) Nov 10 21:00:03 mythbox kernel: ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) Nov 10 21:00:03 mythbox kernel: ivtv0:
RE: [ivtv-devel] ivtv framebuffer is broken with PVR350
maybe not the same problem then, but probably even more frustrating. I am hoping to hear from John Harvey on this. It may still be something wrong with the way that the driver is installed. There is not a huge volume of documentation available for the installation of the xdriver. Does anybody know if the fbdev driver will still work? Steve -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jacques Facquet Sent: Saturday, November 12, 2005 7:08 PM To: ivtv-devel@ivtvdriver.org Subject: Re: [ivtv-devel] ivtv framebuffer is broken with PVR350 Le Samedi 12 Novembre 2005 20:34, Steve Laurie Sanders a écrit : I have been posting about freezing playback and ivtv-osd warnings, and ivtv DEC warnings in the ivtv-users list sinsce I am using 0.4.0 stable. I have the same problem, but no logs after the freeze, I have to reboot my PC. -- Jacques Facquet. ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel ___ ivtv-devel mailing list ivtv-devel@ivtvdriver.org http://ivtvdriver.org/mailman/listinfo/ivtv-devel
