<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 08/30/10 12:44 PM, John Weekley wrote:
<blockquote cite="mid:4C7BEDEB.2000508@foobarlabs.net" type="cite">I'm
using MythDora 12 and recently switched from Dish to Charter cable,
and tried using firewire to control my cable box. The first obstacle
was that specifying DCX-3200 in the card selection didn't work as Myth
said it was unsupported. So I tried DCH-3200 , both p2p and broadcast,
which seems to work well except for the cable box rebooting or
disappearing.
<br>
My setup is a single FE/BE, kernel 2.6.32.19-163.fc12.x86_64 #1 SMP.
<br>
I've noticed this in /var/adm/messages each time firewire goes south:
<br>
<br>
ug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response
(source ffc0, tlabel 0)
<br>
Aug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response
(source ffc0, tlabel 1)
<br>
Aug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response
(source ffc0, tlabel 2)
<br>
Aug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response
(source ffc0, tlabel 3)
<br>
Aug 29 10:39:46 localhost kernel: firewire_core: phy config: card 0,
new root=ffc1, gap_count=5
<br>
Aug 29 10:39:46 localhost kernel: firewire_core: phy config: card 0,
new root=ffc1, gap_count=5
<br>
Aug 29 10:39:47 localhost kernel: firewire_core: phy config: card 0,
new root=ffc1, gap_count=5
<br>
Aug 29 10:39:58 localhost kernel: firewire_core: rediscovered device
fw1
<br>
Aug 29 10:40:01 localhost kernel: firewire_core: Unsolicited response
(source ffc0, tlabel 21)
<br>
Aug 29 10:40:01 localhost kernel: firewire_core: Unsolicited response
(source ffc0, tlabel 22)
<br>
Aug 29 10:40:01 localhost kernel: firewire_core: Unsolicited response
(source ffc0, tlabel 23)
<br>
<br>
<br>
/dev/fw2 s my cable box which doesn't return unless I power cycle both
the myth box and the cable box
<br>
<br>
<br>
Has anyone else experienced this, or have any ideas on what I can try?
<br>
<br>
</blockquote>
<br>
<br>
I was able to solve this problem by editing /lib/udev/rules.d/<a
class="companyLinkTag"
href="http://www.spoke.com/info/c6KAv/SoftwareTechnologiesInc">50-udev-default.rules</a><br>
ands adding :<br>
<br>
KERNEL=="fw[0-9]*", NAME="%k", OWNER="mythtv",
GROUP="video", MODE="0666"<br>
<br>
to the firewire device section.<br>
<br>
John<br>
<br>
</body>
</html>