<div class="gmail_quote">On Fri, Feb 4, 2011 at 7:49 PM, Andrew Allison <span dir="ltr"><<a href="mailto:andrew.allison@gmail.com" target="_blank">andrew.allison@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div><br>
On Fri, Feb 4, 2011 at 3:55 PM, Jarod Wilson <<a href="mailto:jarod@wilsonet.com" target="_blank">jarod@wilsonet.com</a>> wrote:<br>
<br>
Could be that the card isn't getting enough juice on the new<br>
board,<br>
but I'm not really sure. Don't suppose you have a 3rd machine<br>
you could<br>
try it in, or the ability to try it on the old backend with the<br>
newer<br>
code to help narrow down if its a hardware compatibility issue<br>
or a<br>
code compatibility issue? Somewhere or another, I have a PVR-500<br>
of my<br>
own at home, I should dig it out and throw it in a machine...<br>
<br>
I'd also advise filing a bug in Red Hat's bugzilla, cc'ing me,<br>
and I can<br>
get the upstream ivtv maintainer involved, if need be.<br>
<br>
Jarod,<br>
I'll try the F14 x86_64 Live CD on my old backend and see what ivtv<br>
says. Depending on that outcome, I'll log a bugzilla, etc.<br>
<br>
Has anyone else got a PVR-500 working in a MSI P55-GD65 motherboard?<br>
<br>
/Brian/<br>
<br>
</div></div>Comparing your dmesg with mine Fedora 14 x86_64 ASUS M4A77TD Quad AMD<br>
<br>
I'm noticing that in your pasebin file between<br>
line 3 and line 4 Mine is slightly different.<br>
<br>
[ 68.775816] ivtv: Start initialization, version 1.4.1<br>
[ 68.789429] ivtv0: Initializing card 0<br>
[ 68.802791] ivtv0: Autodetected Hauppauge card (cx23416 based)<br>
[ 68.816578] alloc irq_desc for 21 on node 0<br>
[ 68.816580] alloc kstat_irqs on node 0<br>
[ 68.816586] ivtv 0000:05:06.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21<br>
<br>
<br>
I've got the extra lines with the alloc irq part. Don't know if this means anything.<br></blockquote><div><br>Andrew, Jarod,<br><br>The PVR500 works fine with the F14 x86_64 Live CD on my old backend which was running CentOS 5.<br>
<br>The ivtv-related output from dmesg is here:<br><a href="http://pastebin.com/NZhzPUyK" target="_blank">http://pastebin.com/NZhzPUyK</a><br></div></div><br>The start of the differences is where the old backend boots and says it's changing the "unreasonably low" latency timer from 32 to 64. On my new Core i5-based backend, it says the following:<br>
<br><div>tveeprom 4-0050: Huh, no eeprom present (err=-6)?<br>tveeprom 4-0050: Encountered bad packet header [a8]. Corrupt or not a Hauppauge eeprom.<br>ivtv0: Invalid EEPROM<br>cx25840 4-0044: Unable to detect h/w, assuming cx23887</div>
<br>The system power supply should be sufficient. It's a Seasonic 80+ Gold certified 650W power supply. I've got everything stuffed in a Silverstone LC17 case (6 hard drives), which means I only have 1 PCI slot where I can physically put the cards. The other PCI slots are useless for larger cards because the hard drives protrude so far back on top of the motherboard.<br>
<br><a href="http://s1124.photobucket.com/albums/l561/briandlong/?action=view&current=NewBackend.jpg">http://s1124.photobucket.com/albums/l561/briandlong/?action=view&current=NewBackend.jpg</a><br><br>/Brian/<br>