<div class="gmail_quote">On Tue, Jan 26, 2010 at 2:11 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Tue, Jan 26, 2010 at 4:44 PM, Eric Sharkey <<a href="mailto:eric@lisaneric.org">eric@lisaneric.org</a>> wrote:<br>
> On Tue, Jan 26, 2010 at 4:24 PM, Jarod Wilson <<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>> wrote:<br>
>>> I installed an old PCI firewire controller (VIA Technologies, Inc.<br>
>>> VT6306 Fire II) and everything just worked.<br>
>><br>
>> Is that Via chip reporting as OHCI 1.0 or 1.1? Trying to prove out my<br>
>> theory that OHCI 1.1's dual-buffer isochronous receive is generally<br>
>> boned...<br>
><br>
> The Via chip is reporting as OHCI 1.0 and the TI is reporting as OHCI 1.1.<br>
<br>
</div>Would be very interesting then to see if you're previously non-working<br>
TI chip starts working in 2.6.33 (or in an earlier kernel respun with<br>
a one-line change that'll keep ohci 1.1 cards from using<br>
dual-buffer)...<font color="#888888"></font><br></blockquote><div><br>Is there some way to know what versions of the TI chipsets (and how do you even find the version) have the issue?<br><br>I have a TI chip on a Gigabyte motherboard and since upgrading to Fedora 11 64-bit Kernel (2.6.30.10-105.fc11.x86_64) it has been rock solid. Initially I had numerous issues with it but I thought it was due to the amount of memory installed and weird behavior that I was seeing then. I upgraded from 2GB to 4GB and the firewire card would not receive anything from the cablebox at all. Doing memory tests also showed problems during some iterations and it didn't matter what the DIMMs were or in which banks they were placed (4GB in 1GB and 2GB DIMMs in any combination would cause the issue but 2GB rotating the DIMMs in the four banks was always passing).<br>
<br>In the end I thought it was a bad motherboard and decided to live with only 2GB RAM which was anyway sufficient, I just can't run a Windows VM on the box.<br><br>Now after 7 months Firewire recordings have never been more reliable since the 2+ years that I've had it before.<br>
<br>Below is the data from lspci and dmesg related to the card.<br><br>--dejan<br><br>05:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) (prog-if 10 [OHCI])<br> Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard<br>
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-<br> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-<br>
Latency: 32 (500ns min, 1000ns max), Cache Line Size: 32 bytes<br> Interrupt: pin A routed to IRQ 23<br> Region 0: Memory at f7004000 (32-bit, non-prefetchable) [size=2K]<br> Region 1: Memory at f7000000 (32-bit, non-prefetchable) [size=16K]<br>
Capabilities: [44] Power Management version 2<br> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold-)<br> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME+<br> Kernel driver in use: firewire_ohci<br>
Kernel modules: firewire-ohci<br><br># dmesg|grep firewire<br><br>firewire_ohci 0000:05:07.0: PCI INT A -> GSI 23 (level, low) -> IRQ 23<br>firewire_ohci: Added fw-ohci device 0000:05:07.0, OHCI version 1.10<br>
firewire_core: created device fw0: GUID 00c9e2cc00001a4d, S400<br>firewire_core: created device fw1: GUID 001c11fffe9d1690, S400<br>firewire_core: phy config: card 0, new root=ffc1, gap_count=5<br><br></div></div>