[mythtv-users] IEEE-1394 Woes

[Kirk Bocek]

I'm having an issue getting a DCT-6200 hooked up to one of my frontends. I'm
using the ATRpms updated IEEE-1394 packages. I have posted on the atrpms-users
list but haven't received a response.

Is anyone here using Axel's IEEE-1394 drivers?

I have ieee1394-kmdl-2.6.18-164.10.1.el5-2.6.18-2.el5 installed on a
CentOS x64 host. The 1394 card is a 32-bit PCI Via VT6306:

02:03.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE
1394 OHCI Link Layer Controller (rev 46) (prog-if 10 [OHCI])
         Subsystem: VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI
Link Layer Controller
         Flags: bus master, stepping, medium devsel, latency 32, IRQ 217
         Memory at fdeff000 (32-bit, non-prefetchable) [size=2K]
         I/O ports at ef00 [size=128]
         Capabilities: [50] Power Management version 2

When I attach the DCT6200 STB to the card I get:

ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00110666000000d6]
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ieee1394: The root node is not cycle master capable; selecting a new
root node and resetting...
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: SelfIDs failed monotony check with 2
ieee1394: Error in SelfID stage, resetting
BUG: warning at
/var/tmp/bach-build/BUILD/ieee1394-2.6.18/ohci1394.c:234/get_phy_reg()
(Tainted: P     )

Call Trace:
  <IRQ>  [<ffffffff881e06f1>] :ohci1394:get_phy_reg+0x93/0x10b
  [<ffffffff881e1f2f>] :ohci1394:ohci_devctl+0x49/0x49e
  [<ffffffff881ae020>] :ieee1394:hpsb_reset_bus+0x20/0x24
  [<ffffffff881e4217>] :ohci1394:ohci_irq_handler+0x708/0x779
  [<ffffffff80010b81>] handle_IRQ_event+0x51/0xa6
  [<ffffffff800b9fdd>] __do_IRQ+0xa4/0x103
  [<ffffffff8006c9a3>] do_IRQ+0xe7/0xf5
  [<ffffffff8005722b>] mwait_idle+0x0/0x4a
  [<ffffffff8005d615>] ret_from_intr+0x0/0xa
  <EOI>  [<ffffffff80057261>] mwait_idle+0x36/0x4a
  [<ffffffff8004943c>] cpu_idle+0x95/0xb8
  [<ffffffff8007708a>] start_secondary+0x498/0x4a7

BUG: warning at
/var/tmp/bach-build/BUILD/ieee1394-2.6.18/ohci1394.c:263/set_phy_reg()
(Tainted: P     )

Call Trace:
  <IRQ>  [<ffffffff881e0600>] :ohci1394:set_phy_reg+0xa9/0x107
  [<ffffffff881e1f42>] :ohci1394:ohci_devctl+0x5c/0x49e
  [<ffffffff881ae020>] :ieee1394:hpsb_reset_bus+0x20/0x24
  [<ffffffff881e4217>] :ohci1394:ohci_irq_handler+0x708/0x779
  [<ffffffff80010b81>] handle_IRQ_event+0x51/0xa6
  [<ffffffff800b9fdd>] __do_IRQ+0xa4/0x103
  [<ffffffff8006c9a3>] do_IRQ+0xe7/0xf5
  [<ffffffff8005722b>] mwait_idle+0x0/0x4a
  [<ffffffff8005d615>] ret_from_intr+0x0/0xa
  <EOI>  [<ffffffff80057261>] mwait_idle+0x36/0x4a
  [<ffffffff8004943c>] cpu_idle+0x95/0xb8
  [<ffffffff8007708a>] start_secondary+0x498/0x4a7

ieee1394: SelfIDs failed monotony check with 2
ieee1394: Error in SelfID stage, resetting
ieee1394: SelfIDs failed monotony check with 2
ieee1394: Error in SelfID stage, resetting
ieee1394: Error parsing configrom for node 0-01:1023
ieee1394: Node suspended: ID:BUS[0-00:1023]  GUID[00110666000000d6]
ieee1394: Node resumed: ID:BUS[0-00:1023]  GUID[00110666000000d6]
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...

And plugreport comes back empty. There are no other IEEE-1394 devices
attached.

Can anyone provide any guidance? Is the error between keyboard and chair
or is it somewhere else?

Thanks,
Kirk