Jim Kusznir wrote: > Thanks for your reply. I'm pretty sure it wasn't static discharge; it > was fairly moist, and I was pretty careful in handling it....Of > course, anything is possible.......
OK. So assuming that neither heat nor static discharge are the problem, here are a few more questions: 1. Did you replace the power supply when you upgraded your motherboard? 2. Have your reviewed the total power and instantaneous current draw specs of the new motherboard, CPU, cards, and other peripherals with the power supply specs? 3. Does S-Video or Composite video work? (I doubt it will.) 4. If the system can dual boot to Windows, how does the card behave under Windows? 5. Can you test the subject PVR-500 into another system with a known good PVR-500 configuration? 6. Can you test the subject PVR-500 with the old motherboard and power supply configuration? > Here is the debugging info. I didn't see the firmware loading issues > I saw previously. > > I tried a cold-reboot (powered off for 5 min), and got different > problems on the other tuner...Debug info posted at end. I agree with Tyler that you probably have an i2c issue. You'll probably need to turn on i2c_* module debugging parameters in /etc/modprobe.conf to see what's really going on on the i2c bus. My kernel is different from yours, so find the i2c modules under /lib/modules and do a modinfo on them to find their debugging parameters. > root at myth:~# modinfo ivtv > filename: > /lib/modules/2.6.18-chw-13/kernel/drivers/media/video/ivtv/ivtv.ko > author: Kevin Thayer, Chris Kennedy, Hans Verkuil > description: CX23415/CX23416 driver > license: GPL > version: 1.1.0 > vermagic: 2.6.18-chw-13 SMP preempt mod_unload 586 gcc-4.1 > depends: > cx2341x,videodev,tveeprom,v4l2-common,v4l2-common,i2c-core,i2c-algo-bit,v4l1-compat,firmware_class > alias: pci:v00004444d00000803sv*sd*bc*sc*i* > alias: pci:v00004444d00000016sv*sd*bc*sc*i* > srcversion: 0C11E4A3987DE2860FD6666 > parm: newi2c:Use new I2C implementation > -1 is autodetect, 0 is off, 1 is on > Default is autodetect (int) As a stab in the dark, you may want to force newi2c to either 0 or 1 instead of using autodetect. > ----------- > Syslog: > ivtv: Start initialization, version 1.1.0 > ivtv0: Initializing card #0 > ivtv0: Autodetected Hauppauge card (cx23416 based) > PCI: Enabling device 0000:02:08.0 (0000 -> 0002) > ACPI: PCI Interrupt 0000:02:08.0[A] -> Link [APC4] -> GSI 19 (level, > high) -> IRQ 20 > wm8775 2-001b: chip found @ 0x36 (ivtv i2c driver #0) > cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) cx25840 2-0044 is the digitizer for the first tuner > tuner 2-0043: chip found @ 0x86 (ivtv i2c driver #0) > tda9887 2-0043: tda988[5/6/7] found @ 0x43 (tuner) > tuner 2-0043: type set to tda9887 > TEA5767 detected. > tuner 2-0060: chip found @ 0xc0 (ivtv i2c driver #0) > tea5767 2-0060: type set to Philips TEA5767HN FM Radio > tuner 2-0060: type set to tea5767 > tuner 2-0061: chip found @ 0xc2 (ivtv i2c driver #0) > tveeprom 2-0050: Hauppauge model 23552, rev D492, serial# 7855734 > tveeprom 2-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57) > tveeprom 2-0050: TV standards NTSC(M) (eeprom 0x08) > tveeprom 2-0050: second tuner model is Philips TEA5768HL FM Radio (idx > 101, type 62) > tveeprom 2-0050: audio processor is CX25843 (idx 37) > tveeprom 2-0050: decoder processor is CX25843 (idx 30) > tveeprom 2-0050: has radio, has no IR receiver, has no IR transmitter > ivtv0: Autodetected WinTV PVR 500 (unit #1) > tuner-simple 2-0061: type set to 57 (Philips FQ1236A MK4) > tuner 2-0061: type set to Philips FQ1236A MK4 > ivtv0: Registered device video0 for encoder MPG (16384 kB) > ivtv0: Registered device video32 for encoder YUV (2048 kB) > ivtv0: Registered device vbi0 for encoder VBI (8192 kB) > ivtv0: Registered device video24 for encoder PCM (320 kB) > ivtv0: Registered device radio0 for encoder radio > ivtv0: Initialized card #0: WinTV PVR 500 (unit #1) > ivtv1: Initializing card #1 > ivtv1: Autodetected Hauppauge card (cx23416 based) > PCI: Enabling device 0000:02:09.0 (0000 -> 0002) > ACPI: PCI Interrupt 0000:02:09.0[A] -> Link [APC1] -> GSI 16 (level, > high) -> IRQ 21 > wm8775 3-001b: chip found @ 0x36 (ivtv i2c driver #1) > cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1) cx25840 3-0044 is the digitizer for the second tuner > tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #1) > tda9887 3-0043: tda988[5/6/7] found @ 0x43 (tuner) > tuner 3-0043: type set to tda9887 > tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #1) > tveeprom 3-0050: Hauppauge model 23552, rev D492, serial# 7855734 > tveeprom 3-0050: tuner model is Philips FQ1236A MK4 (idx 92, type 57) > tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) > tveeprom 3-0050: second tuner model is Philips TEA5768HL FM Radio (idx > 101, type 62) > tveeprom 3-0050: audio processor is CX25843 (idx 37) > tveeprom 3-0050: decoder processor is CX25843 (idx 30) > tveeprom 3-0050: has radio, has no IR receiver, has no IR transmitter > ivtv1: Correcting tveeprom data: no radio present on second unit > ivtv1: Autodetected WinTV PVR 500 (unit #2) > tuner-simple 3-0061: type set to 57 (Philips FQ1236A MK4) > tuner 3-0061: type set to Philips FQ1236A MK4 > ivtv1: Registered device video1 for encoder MPG (16384 kB) > ivtv1: Registered device video33 for encoder YUV (2048 kB) > ivtv1: Registered device vbi1 for encoder VBI (8192 kB) > ivtv1: Registered device video25 for encoder PCM (320 kB) > ivtv1: Initialized card #1: WinTV PVR 500 (unit #2) > ivtv: End initialization > --- The above seems OK after a cursory read. > after cold-reboot. Symptoms: tuner2 shows black screen with red and > blue static. tuner1 untested. > --- So the second cx25840 chip is probably not receiving or accepting commands on the i2c bus. The registers on the cx25840 are read and written over the i2c bus. There is a problem with the cx23416 (I'm guessing it drives the i2c bus) or the cx25840 or the i2c bus lines connecting the two. Since the problem is intermittent, it may be due to temporary conditions and hence the card may have no permanent damage. Given that it happens to both halves of your PVR-500, I'd look to potential problem sources common to either half of the board: power supply, electrical noise, bad motherboard, antenna cables, etc. > kusznir at myth:~$ dmesg |grep cx > ivtv0: Autodetected Hauppauge card (cx23416 based) > cx25840 2-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #0) > ivtv1: Autodetected Hauppauge card (cx23416 based) > cx25840 3-0044: cx25843-23 found @ 0x88 (ivtv i2c driver #1) > cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.6 loaded > cx88/2: cx2388x dvb driver version 0.0.6 loaded > cx88/2: registering cx8802 driver, type: dvb access: shared > ivtv1: Loaded v4l-cx2341x-enc.fw firmware (376836 bytes) > cx25840 3-0044: firmware load i2c failure > --- The firmware load for the second digitizer failed. This means it is probably not responding reliably on the i2c bus or that the driving chip (the cx23416 I think) isn't outputting the data properly on the i2c bus. -Andy > Note that this is different from the last error snapshot. > > Any hints? > > Thanks! > --Jim > > On Sat, Mar 15, 2008 at 5:10 AM, Andy Walls <cwalls at radix.net> wrote: > > Jim Kusznir wrote: > > > > > The problem materializes either as video with a very heavy red/back > > > static and no audio, a black screen with "little splotches" of static > > > (with a red bias), or a fairly clear picture with no audio. I've gone > > > through the logs, and the initialization looked normal except for 1 > > > line late in the boot (after the begin/end initialization) that > > > complained about firmware for v4l-cx25840 load failed. > > > > > As far as information to help debug the problem: When I re-installed > > > the cards, the pvr-500 was next to my nvidia GeForce 4MX. On my old > > > motherboard, it was one slot further away (with a soundblaster card > > > in-between). I noticed that the video card was producing a fair > > > amount of heat, and its length seemed to encompass only one of the two > > > connextant chips on the PVR. I moved it to the end of the mobo, where > > > it should be among the coolest places in the computer. The problem > > > still persists. > > > > > > does anyone have any suggestions? Is that tuner on my 500 fried? _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
