It appears this e-mail got "buried" by gmail....didn't see it until now.
I have some answers: On Mon, Mar 17, 2008 at 5:57 PM, Andy Walls <[EMAIL PROTECTED]> wrote: > 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? No; same PSU. (Silverstone; should be sufficient) > 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? I have not explicitly reviewed them. It should be sufficient, as this case/psu was intended for systems such as I just put in. I replaced a P4 1.3Ghz with an AMD Athlon XP 1.8Ghz. I replaced 3 IDE hard drives with 1 SATA hard drive (and the PSU has native SATA support), but this configuration worked in the old system too. I have one fewer expansion cards installed presently. > 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? This system cannot dual-boot presently. > > 5. Can you test the subject PVR-500 into another system with a known > good PVR-500 configuration? I don't have access to any known-good pvr-500 systems. > 6. Can you test the subject PVR-500 with the old motherboard and power > supply configuration? Yes, I intend to mount the motherboard and configure it for a testing platform; I will try to do that tomorrow night. > > > 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. Any partular modules? [EMAIL PROTECTED]:/home/mythtv# lsmod |grep i2c i2c_algo_bit 12296 1 ivtv i2c_i801 11020 0 i2c_nforce2 10240 0 i2c_core 20864 15 ivtv,saa7115,msp3400,tuner,tea5767,tda8290,tuner_simple,mt20xx,i2c_algo_bit,tveeprom,cx25840,nvidia,i2c_i801,wm8775,i2c_nforce2 Thanks! --Jim _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
