[mythtv-users] Firewire causes DCX-3200 to continuously "reboot" or disappears from plugreport

John Weekley weekleyj at foobarlabs.net
Mon Aug 30 17:44:11 UTC 2010


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.
My setup is a single FE/BE, kernel 2.6.32.19-163.fc12.x86_64 #1 SMP.
I've noticed this in /var/adm/messages each time firewire goes south:

ug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response 
(source ffc0, tlabel 0)
Aug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response 
(source ffc0, tlabel 1)
Aug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response 
(source ffc0, tlabel 2)
Aug 29 10:39:44 localhost kernel: firewire_core: Unsolicited response 
(source ffc0, tlabel 3)
Aug 29 10:39:46 localhost kernel: firewire_core: phy config: card 0, new 
root=ffc1, gap_count=5
Aug 29 10:39:46 localhost kernel: firewire_core: phy config: card 0, new 
root=ffc1, gap_count=5
Aug 29 10:39:47 localhost kernel: firewire_core: phy config: card 0, new 
root=ffc1, gap_count=5
Aug 29 10:39:58 localhost kernel: firewire_core: rediscovered device fw1
Aug 29 10:40:01 localhost kernel: firewire_core: Unsolicited response 
(source ffc0, tlabel 21)
Aug 29 10:40:01 localhost kernel: firewire_core: Unsolicited response 
(source ffc0, tlabel 22)
Aug 29 10:40:01 localhost kernel: firewire_core: Unsolicited response 
(source ffc0, tlabel 23)


/dev/fw2 s my cable box which doesn't return unless I power cycle both 
the myth box and the cable box


Has anyone else experienced this, or have any ideas on what I can try?


Thanks,

John



More information about the mythtv-users mailing list