[mythtv-commits] Ticket #5278: Firewire Uses Bad Port Number and Fails
MythTV
mythtv at cvs.mythtv.org
Sun Apr 18 03:38:30 UTC 2010
#5278: Firewire Uses Bad Port Number and Fails
---------------------------------+------------------------------------------
Reporter: scottadmi@… | Owner: jarod
Type: defect | Status: closed
Priority: minor | Milestone: 0.24
Component: MythTV - Recording | Version: 0.21
Severity: medium | Resolution: fixed
Mlocked: 0 |
---------------------------------+------------------------------------------
Comment(by foom@…):
This bug used to affect me. However, I've since upgraded my computer, and
it's never happened since. I replaced the entire machine (motherboard,
CPU, etc), and also am running a new kernel (2.6.32.11), with the new
firewire stack (firewire_core module instead of ieee1394 module).
I'm still running MythTV 0.22, though, and still have the exact same
FireWire set-top-box (DCH3200).
So, I suspect that the fundamental problem is/was either a driver bug or
hardware bug, and not actually a bug in myth. It's of course possible that
this changeset does completely reliably work-around the issue in whatever
component was broken, but it seems like it might still be fragile, given
that the fix is apparently just to retry every 20ms, 20 times or until it
works.
I'm now using this firewire chipset, which is integrated into a GA-
MA785GM-US2H motherboard:
{{{
03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000
Controller (PHY/Link)
}}}
I don't have the name of the old chipset which wasn't reliable easily
available, but it was an integrated firewire controller on a VIA KM266
motherboard.
Hope that info helps someone...and good luck to everyone still having the
problem. :)
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/5278#comment:50>
MythTV <http://www.mythtv.org/>
MythTV
More information about the mythtv-commits
mailing list