Issues with TI XIO2213 chipset?

Discussion:

Charlie McMackin

2010-12-29 14:32:47 UTC

Hello,

I'm trying to capture video using a Canopus/GreenValley ADVC110
through a 6-pin 1394a wire to a PCIe Firewire 1394/1394b card. I
believe it is a Syba.. model number is SD-PEX30009. I noticed there
were documented problems with other TI chipsets so I was curious if
this one suffers the same fate. Or, more hopefully, this card is
supported by a more current Linux Kernel? To the best of my current
ability, I’ve narrowed the problem down to the card. I have another
older computer with a PCI-32 Creative Audigy (circa ~2001) which has a
firewire - A port. It's running the server version of ubuntu marverick
but it properly creates the /dev/fw1 device when the ADVC110 is
plugged in and I've been able to get video from it with dvgrab 3.5.
One more thing, when I plug the ADVC110 into the "faulty" 1394 card, I
do get a power light... not sure if that will shed any more light on
the problem though.

Is there any hope for it?

Here is the supporting info from the computer that is not working:

***@onyx:~$ uname -a
Linux onyx 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC
2010 x86_64 GNU/Linux

***@onyx:~$ lsmod | grep -e firewire -e 1394
firewire_ohci 24615 0
firewire_core 54327 1 firewire_ohci
crc_itu_t 1739 1 firewire_core

***@onyx:~$ lspci
00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b2)
00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1)
00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.4 RAM memory: nVidia Corporation Device 0a98 (rev b1)
00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)
00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1
Controller (rev b1)
00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0
Controller (rev b1)
00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1
Controller (rev b1)
00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0
Controller (rev b1)
00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)
00:09.0 PCI bridge: nVidia Corporation MCP79 PCI Bridge (rev b1)
00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)
00:0b.0 IDE interface: nVidia Corporation MCP79 SATA Controller (rev b1)
00:0c.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:15.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
00:16.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)
02:00.0 VGA compatible controller: ATI Technologies Inc Juniper
[Radeon HD 5700 Series]
02:00.1 Audio device: ATI Technologies Inc Juniper HDMI Audio [Radeon
HD 5700 Series]
03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express
to PCI Bridge (rev 01)
04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221
IEEE-1394b OHCI Controller (rev 01)
05:00.0 IDE interface: JMicron Technology Corp. JMB368 IDE controller

When I unplug from the card and then re-plug the ADVC110 this message
appears in /var/log/syslog:

Dec 29 07:51:57 onyx kernel: [ 1836.998018] firewire_core: skipped bus
generations, destroying all nodes
Dec 29 07:51:58 onyx kernel: [ 1837.491329] firewire_core:
rediscovered device fw0

Charlie

Stefan Richter

2010-12-29 19:33:16 UTC

Permalink

Post by Charlie McMackin
I'm trying to capture video using a Canopus/GreenValley ADVC110
through a 6-pin 1394a wire to a PCIe Firewire 1394/1394b card. I
believe it is a Syba.. model number is SD-PEX30009. I noticed there
were documented problems with other TI chipsets so I was curious if
this one suffers the same fate.

My own XIO2213A based card works perfectly with all kinds of devices
(storage, industrial video camera, audio interface, DV camcorder,
MPEG2-TS STB).

The first generation of 1394b-2002/ FireWire 800 chips from Texas
Instruments has issues (TSB82AA2 + TSB81BA3 based cards), but not the
much more recent XIO2213A.

Post by Charlie McMackin
Or, more hopefully, this card is
supported by a more current Linux Kernel? To the best of my current
ability, I’ve narrowed the problem down to the card. I have another
older computer with a PCI-32 Creative Audigy (circa ~2001) which has a
firewire - A port. It's running the server version of ubuntu marverick
but it properly creates the /dev/fw1 device when the ADVC110 is
plugged in and I've been able to get video from it with dvgrab 3.5.
One more thing, when I plug the ADVC110 into the "faulty" 1394 card, I
do get a power light... not sure if that will shed any more light on
the problem though.
Is there any hope for it?
Linux onyx 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux

Do you have the same kernel and userland on the other PC which works?

[...]

Post by Charlie McMackin
03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge (rev 01)
04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller (rev 01)

FWIW, lspci version 3.1.4 shows my PCIe card as
08:00.0 PCI bridge: Texas Instruments XIO2213A PCI Express to PCI Bridge (rev 01)
09:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A 1394b OHCI with 3-Port PHY (rev 01)

Does you PCIe card have an internal power connector? If yes, make sure
that it is attached to the PSU. If not, power the ADVC110 by a
separate PSU.

[...]

Post by Charlie McMackin
When I unplug from the card and then re-plug the ADVC110 this message
Dec 29 07:51:57 onyx kernel: [ 1836.998018] firewire_core: skipped bus generations, destroying all nodes
Dec 29 07:51:58 onyx kernel: [ 1837.491329] firewire_core: rediscovered device fw0

Some things for you to try:

1. Gather more diagnostic messages.

# echo -1 > /sys/module/firewire_ohci/parameters/debug
Then plug the ADVC110 in, watch the syslog, and post the result here.

2. Try the older FireWire kernel drivers.

# modprobe -r firewire-ohci
# modprobe ohci1394
# modprobe raw1394
# chmod a+rw /dev/raw1394
Then plug the ADVC110 in, check the syslog for "Host added.." and "Node
added..." messages from the ieee1394 core driver (the former message
being for the card, the latter for the ADVC110) and try to capture
with dvgrab.

--
Stefan Richter
-=====-==-=- ==-- ===-=
http://arcgraph.de/sr/

Charlie McMackin

2010-12-29 21:23:08 UTC

Permalink

Post by Stefan Richter
My own XIO2213A based card works perfectly with all kinds of devices
(storage, industrial video camera, audio interface, DV camcorder,
MPEG2-TS STB).

Glad to hear it is supported.

Post by Stefan Richter
Do you have the same kernel and userland on the other PC which works?

I believe so, It is pretty much a fresh install of Ubuntu 10.10 with
dvgrab and its dependencies being the first packages installed. I
don't have physical access at the time of this reply but if I find
that not to be the case, I'll follow-up again.

Post by Stefan Richter
[...]

FWIW, lspci version 3.1.4 shows my PCIe card as
08:00.0 PCI bridge: Texas Instruments XIO2213A PCI Express to PCI Bridge (rev 01)
09:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A 1394b OHCI with 3-Port PHY (rev 01)
Does you PCIe card have an internal power connector? If yes, make sure
that it is attached to the PSU. If not, power the ADVC110 by a
separate PSU.

My card does not have an internal power connector but it does appear
to be delivering power to the ADVC110 since the lights are coming on
fine... Is it still possible that the ADVC110 needs a power adapter?

Post by Stefan Richter
[...]

1. Gather more diagnostic messages.
# echo -1 > /sys/module/firewire_ohci/parameters/debug
Then plug the ADVC110 in, watch the syslog, and post the result here.

Okay, when I do this I get a constant stream of messages which all
look the same save for the trailing number. Here are the last few
entries plus the event where I unplug the cable from the box:

Dec 29 15:02:07 onyx kernel: [ 317.646314] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.646318] firewire_ohci: AR
evt_bus_reset, generation 135
Dec 29 15:02:07 onyx kernel: [ 317.646646] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.646651] firewire_ohci: AR
evt_bus_reset, generation 136
Dec 29 15:02:07 onyx kernel: [ 317.646980] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.646985] firewire_ohci: AR
evt_bus_reset, generation 137
Dec 29 15:02:07 onyx kernel: [ 317.647314] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.647319] firewire_ohci: AR
evt_bus_reset, generation 138
Dec 29 15:02:07 onyx kernel: [ 317.647616] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.647620] firewire_ohci: AR
evt_bus_reset, generation 139
Dec 29 15:02:07 onyx kernel: [ 317.647795] firewire_ohci: IRQ 00010000 selfID
Dec 29 15:02:07 onyx kernel: [ 317.647809] firewire_ohci: 1 selfIDs,
generation 140, local node ID ffc0
Dec 29 15:02:07 onyx kernel: [ 317.647812] firewire_ohci: selfID 0:
807fcc56, phy 0 [---] beta gc=63 -3W Lci
Dec 29 15:02:07 onyx kernel: [ 317.647815] firewire_core: skipped bus
generations, destroying all nodes
Dec 29 15:02:08 onyx kernel: [ 318.140068] firewire_core:
rediscovered device fw0

Post by Stefan Richter
2. Try the older FireWire kernel drivers.
# modprobe -r firewire-ohci
# modprobe ohci1394
# modprobe raw1394
# chmod a+rw /dev/raw1394
Then plug the ADVC110 in, check the syslog for "Host added.." and "Node
added..." messages from the ieee1394 core driver (the former message
being for the card, the latter for the ADVC110) and try to capture
with dvgrab.

Here is syslog entries where I remove the firewire-ohci module and
load the ochi1394 and raw1394. I get a Host added but no "Node added"
when I plug in the ADVC110

Dec 29 15:08:35 onyx kernel: [ 704.800184] firewire_ohci: Removed
fw-ohci device.
Dec 29 15:08:42 onyx kernel: [ 711.999203] ohci1394 0000:04:00.0: PCI
INT A -> Link[LN3A] -> GSI 18 (level, low) -> IRQ 18
Dec 29 15:08:42 onyx kernel: [ 712.052099] ohci1394: fw-host0:
OHCI-1394 1.1 (PCI): IRQ=[18] MMIO=[fbeff800-fbefffff] Max
Packet=[4096] IR/IT contexts=[8/8]
Dec 29 15:08:43 onyx kernel: [ 713.370480] ieee1394: Host added:
ID:BUS[0-00:1023] GUID[7856341200000280]
Dec 29 15:08:51 onyx kernel: [ 721.558889] ieee1394: raw1394:
/dev/raw1394 device initialized

I didn't try further continue dvgrab since there was no node.

Ideally I would have another motherboard with a PCIe 1x slot to test
this card on before being completely sure... but sadly I don't. In
the mean time I guess I should start looking for documentation
required to possible send this thing back eh? :(

Charlie

Stefan Richter

2010-12-29 22:18:18 UTC

Permalink

Post by Charlie McMackin

Post by Stefan Richter
Does you PCIe card have an internal power connector? If yes, make sure
that it is attached to the PSU. If not, power the ADVC110 by a
separate PSU.

If you operated this the same way on the Audigy card (which AFAIK does
not have a power connector either), then you were lucky. The 12 V
power rail of PCI is rather weak and not adequate for the minimum
requirements on a spe compliant 1394 bus power provider.

Ditto PCI Express: The +12V power rail of a PCIe x1 slot is merely
specified for 0.5 A which may not be enough to power both the card and
the ADVC110. The +12V rail of x4/x8 slots is specified for 2.1 A and
the one of x16 slots for 4.4 A but I don't know if an x1 card put into
an x4 or x8 or x16 slot can actually tap into the better supply of
those slots, if you can spare one.

Anyway, you should rather power the ADVC110 directly.

[...]

Post by Charlie McMackin
I get a constant stream of messages which all
look the same save for the trailing number. Here are the last few
Dec 29 15:02:07 onyx kernel: [ 317.646314] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.646318] firewire_ohci: AR evt_bus_reset, generation 135
Dec 29 15:02:07 onyx kernel: [ 317.646646] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.646651] firewire_ohci: AR evt_bus_reset, generation 136
Dec 29 15:02:07 onyx kernel: [ 317.646980] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.646985] firewire_ohci: AR evt_bus_reset, generation 137
Dec 29 15:02:07 onyx kernel: [ 317.647314] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.647319] firewire_ohci: AR evt_bus_reset, generation 138
Dec 29 15:02:07 onyx kernel: [ 317.647616] firewire_ohci: IRQ 00000010 AR_req
Dec 29 15:02:07 onyx kernel: [ 317.647620] firewire_ohci: AR evt_bus_reset, generation 139
Dec 29 15:02:07 onyx kernel: [ 317.647795] firewire_ohci: IRQ 00010000 selfID
Dec 29 15:02:07 onyx kernel: [ 317.647809] firewire_ohci: 1 selfIDs, generation 140, local node ID ffc0
Dec 29 15:02:07 onyx kernel: [ 317.647812] firewire_ohci: selfID 0: 807fcc56, phy 0 [---] beta gc=63 -3W Lci
Dec 29 15:02:07 onyx kernel: [ 317.647815] firewire_core: skipped bus generations, destroying all nodes
Dec 29 15:02:08 onyx kernel: [ 318.140068] firewire_core: rediscovered device fw0

Given that this endless series of bus reset IRQs happens with a known
good physical layer chip, it is a very strong indication of a hardware
fault. E.g. said power supply problem.

--
Stefan Richter
-=====-==-=- ==-- ===-=
http://arcgraph.de/sr/

Charlie McMackin

2010-12-30 21:12:26 UTC

Permalink

Post by Stefan Richter
Given that this endless series of bus reset IRQs happens with a known
good physical layer chip, it is a very strong indication of a hardware
fault. E.g. said power supply problem.

I have now tested with a dedicated power supply but I still get errors
mentioned previously. While disappointing, it also allowed me to
attempt the 4-pin 1394a connector on the ADVC110. I connected to it
using a 1394b 9-pin male to 1394a 4-pin male cable into one of the
1394b ports on the SD-PEX30009 and lo :

Dec 30 14:28:28 onyx kernel: [ 2083.963258] firewire_ohci: 1 selfIDs,
generation 248, local node ID ffc0
Dec 30 14:28:28 onyx kernel: [ 2083.963262] firewire_ohci: selfID 0:
807fcc56, phy 0 [---] beta gc=63 -3W Lci
Dec 30 14:28:28 onyx kernel: [ 2083.963265] firewire_core: skipped bus
generations, destroying all nodes
Dec 30 14:28:29 onyx kernel: [ 2084.467107] firewire_core:
rediscovered device fw0
Dec 30 14:30:54 onyx kernel: [ 2230.264154] firewire_ohci: IRQ 00000010 AR_req
Dec 30 14:30:54 onyx kernel: [ 2230.264163] firewire_ohci: AR
evt_bus_reset, generation 249
Dec 30 14:30:54 onyx kernel: [ 2230.264338] firewire_ohci: IRQ 00010000 selfID
Dec 30 14:30:54 onyx kernel: [ 2230.264352] firewire_ohci: 2 selfIDs,
generation 249, local node ID ffc1
Dec 30 14:30:54 onyx kernel: [ 2230.264356] firewire_ohci: selfID 0:
807f8890, phy 0 [p-.] S400 gc=63 +0W Lc
Dec 30 14:30:54 onyx kernel: [ 2230.264359] firewire_ohci: selfID 0:
817fcc76, phy 1 [-c-] beta gc=63 -3W Lci
Dec 30 14:30:54 onyx kernel: [ 2230.264392] firewire_core: phy config:
card 0, new root=ffc1, gap_count=5
Dec 30 14:30:54 onyx kernel: [ 2230.264413] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:54 onyx kernel: [ 2230.264420] firewire_ohci: AT
ack_complete, phy config packet, 01c50000
Dec 30 14:30:55 onyx kernel: [ 2230.283821] firewire_ohci: IRQ 00000010 AR_req
Dec 30 14:30:55 onyx kernel: [ 2230.283827] firewire_ohci: AR
evt_bus_reset, generation 250
Dec 30 14:30:55 onyx kernel: [ 2230.283832] firewire_ohci: IRQ 00010000 selfID
Dec 30 14:30:55 onyx kernel: [ 2230.283846] firewire_ohci: 2 selfIDs,
generation 250, local node ID ffc1
Dec 30 14:30:55 onyx kernel: [ 2230.283850] firewire_ohci: selfID 0:
80458890, phy 0 [p-.] S400 gc=5 +0W Lc
Dec 30 14:30:55 onyx kernel: [ 2230.283853] firewire_ohci: selfID 0:
8145cc76, phy 1 [-c-] beta gc=5 -3W Lci
Dec 30 14:30:55 onyx kernel: [ 2230.761311] firewire_ohci: IRQ
00000021 AR_resp AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761322] firewire_ohci: AR spd 0 tl
25, ffc0 -> ffc1, ack_complete, QR resp = 04048f01
Dec 30 14:30:55 onyx kernel: [ 2230.761326] firewire_ohci: AT spd 0 tl
25, ffc1 -> ffc0, pending/cancelled, QR req, fffff0000400
Dec 30 14:30:55 onyx kernel: [ 2230.761360] firewire_ohci: IRQ
00000021 AR_resp AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761367] firewire_ohci: AR spd 0 tl
26, ffc0 -> ffc1, ack_complete, QR resp = 31333934
Dec 30 14:30:55 onyx kernel: [ 2230.761371] firewire_ohci: AT spd 0 tl
26, ffc1 -> ffc0, pending/cancelled, QR req, fffff0000404
Dec 30 14:30:55 onyx kernel: [ 2230.761402] firewire_ohci: IRQ
00000021 AR_resp AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761409] firewire_ohci: AR spd 0 tl
27, ffc0 -> ffc1, ack_complete, QR resp = e0648100
Dec 30 14:30:55 onyx kernel: [ 2230.761413] firewire_ohci: AT spd 0 tl
27, ffc1 -> ffc0, pending/cancelled, QR req, fffff0000408
Dec 30 14:30:55 onyx kernel: [ 2230.761445] firewire_ohci: IRQ
00000021 AR_resp AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761451] firewire_ohci: AR spd 0 tl
28, ffc0 -> ffc1, ack_complete, QR resp = 00201101
Dec 30 14:30:55 onyx kernel: [ 2230.761455] firewire_ohci: AT spd 0 tl
28, ffc1 -> ffc0, pending/cancelled, QR req, fffff000040c
Dec 30 14:30:55 onyx kernel: [ 2230.761487] firewire_ohci: IRQ
00000021 AR_resp AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761493] firewire_ohci: AR spd 0 tl
29, ffc0 -> ffc1, ack_complete, QR resp = 15023069
Dec 30 14:30:55 onyx kernel: [ 2230.761497] firewire_ohci: AT spd 0 tl
29, ffc1 -> ffc0, pending/cancelled, QR req, fffff0000410
Dec 30 14:30:55 onyx kernel: [ 2230.761527] firewire_ohci: IRQ
00000021 AR_resp AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761533] firewire_ohci: AR spd 2 tl
2a, ffc0 -> ffc1, ack_complete, QR resp = 04048f01
Dec 30 14:30:55 onyx kernel: [ 2230.761537] firewire_ohci: AT spd 2 tl
2a, ffc1 -> ffc0, pending/cancelled, QR req, fffff0000400
Dec 30 14:30:55 onyx kernel: [ 2230.761565] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761571] firewire_ohci: AT spd 2 tl
2b, ffc1 -> ffc0, ack_pending , QR req, fffff0000414
Dec 30 14:30:55 onyx kernel: [ 2230.761594] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.761600] firewire_ohci: AR spd 2 tl
2b, ffc0 -> ffc1, ack_complete, QR resp = 0006582c
Dec 30 14:30:55 onyx kernel: [ 2230.761629] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761635] firewire_ohci: AT spd 2 tl
2c, ffc1 -> ffc0, ack_pending , QR req, fffff0000418
Dec 30 14:30:55 onyx kernel: [ 2230.761657] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.761664] firewire_ohci: AR spd 2 tl
2c, ffc0 -> ffc1, ack_complete, QR resp = 03002011
Dec 30 14:30:55 onyx kernel: [ 2230.761692] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761699] firewire_ohci: AT spd 2 tl
2d, ffc1 -> ffc0, ack_pending , QR req, fffff000041c
Dec 30 14:30:55 onyx kernel: [ 2230.761721] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.761727] firewire_ohci: AR spd 2 tl
2d, ffc0 -> ffc1, ack_complete, QR resp = 0c0083c0
Dec 30 14:30:55 onyx kernel: [ 2230.761756] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761762] firewire_ohci: AT spd 2 tl
2e, ffc1 -> ffc0, ack_pending , QR req, fffff0000420
Dec 30 14:30:55 onyx kernel: [ 2230.761785] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.761791] firewire_ohci: AR spd 2 tl
2e, ffc0 -> ffc1, ack_complete, QR resp = 8d00000a
Dec 30 14:30:55 onyx kernel: [ 2230.761820] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761826] firewire_ohci: AT spd 2 tl
2f, ffc1 -> ffc0, ack_pending , QR req, fffff0000424
Dec 30 14:30:55 onyx kernel: [ 2230.761848] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.761854] firewire_ohci: AR spd 2 tl
2f, ffc0 -> ffc1, ack_complete, QR resp = d1000003
Dec 30 14:30:55 onyx kernel: [ 2230.761883] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761889] firewire_ohci: AT spd 2 tl
30, ffc1 -> ffc0, ack_pending , QR req, fffff0000428
Dec 30 14:30:55 onyx kernel: [ 2230.761912] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.761918] firewire_ohci: AR spd 2 tl
30, ffc0 -> ffc1, ack_complete, QR resp = c3000005
Dec 30 14:30:55 onyx kernel: [ 2230.761947] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.761953] firewire_ohci: AT spd 2 tl
31, ffc1 -> ffc0, ack_pending , QR req, fffff000042c
Dec 30 14:30:55 onyx kernel: [ 2230.761976] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.761982] firewire_ohci: AR spd 2 tl
31, ffc0 -> ffc1, ack_complete, QR resp = 8100000a
Dec 30 14:30:55 onyx kernel: [ 2230.762010] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762017] firewire_ohci: AT spd 2 tl
32, ffc1 -> ffc0, ack_pending , QR req, fffff0000454
Dec 30 14:30:55 onyx kernel: [ 2230.762040] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762046] firewire_ohci: AR spd 2 tl
32, ffc0 -> ffc1, ack_complete, QR resp = 0004bac7
Dec 30 14:30:55 onyx kernel: [ 2230.762074] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762080] firewire_ohci: AT spd 2 tl
33, ffc1 -> ffc0, ack_pending , QR req, fffff0000458
Dec 30 14:30:55 onyx kernel: [ 2230.762103] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762109] firewire_ohci: AR spd 2 tl
33, ffc0 -> ffc1, ack_complete, QR resp = 00000000
Dec 30 14:30:55 onyx kernel: [ 2230.762140] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762147] firewire_ohci: AT spd 2 tl
34, ffc1 -> ffc0, ack_pending , QR req, fffff000045c
Dec 30 14:30:55 onyx kernel: [ 2230.762169] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762175] firewire_ohci: AR spd 2 tl
34, ffc0 -> ffc1, ack_complete, QR resp = 00000000
Dec 30 14:30:55 onyx kernel: [ 2230.762205] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762212] firewire_ohci: AT spd 2 tl
35, ffc1 -> ffc0, ack_pending , QR req, fffff0000460
Dec 30 14:30:55 onyx kernel: [ 2230.762235] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762241] firewire_ohci: AR spd 2 tl
35, ffc0 -> ffc1, ack_complete, QR resp = 43616e6f
Dec 30 14:30:55 onyx kernel: [ 2230.762271] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762277] firewire_ohci: AT spd 2 tl
36, ffc1 -> ffc0, ack_pending , QR req, fffff0000464
Dec 30 14:30:55 onyx kernel: [ 2230.762298] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762304] firewire_ohci: AR spd 2 tl
36, ffc0 -> ffc1, ack_complete, QR resp = 70757300
Dec 30 14:30:55 onyx kernel: [ 2230.762332] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762339] firewire_ohci: AT spd 2 tl
37, ffc1 -> ffc0, ack_pending , QR req, fffff000043c
Dec 30 14:30:55 onyx kernel: [ 2230.762361] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762367] firewire_ohci: AR spd 2 tl
37, ffc0 -> ffc1, ack_complete, QR resp = 0002c009
Dec 30 14:30:55 onyx kernel: [ 2230.762396] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762402] firewire_ohci: AT spd 2 tl
38, ffc1 -> ffc0, ack_pending , QR req, fffff0000440
Dec 30 14:30:55 onyx kernel: [ 2230.762425] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762431] firewire_ohci: AR spd 2 tl
38, ffc0 -> ffc1, ack_complete, QR resp = 17000000
Dec 30 14:30:55 onyx kernel: [ 2230.762460] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762466] firewire_ohci: AT spd 2 tl
39, ffc1 -> ffc0, ack_pending , QR req, fffff0000444
Dec 30 14:30:55 onyx kernel: [ 2230.762488] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762495] firewire_ohci: AR spd 2 tl
39, ffc0 -> ffc1, ack_complete, QR resp = 81000009
Dec 30 14:30:55 onyx kernel: [ 2230.762528] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762534] firewire_ohci: AT spd 2 tl
3a, ffc1 -> ffc0, ack_pending , QR req, fffff0000468
Dec 30 14:30:55 onyx kernel: [ 2230.762554] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762560] firewire_ohci: AR spd 2 tl
3a, ffc0 -> ffc1, ack_complete, QR resp = 0005862b
Dec 30 14:30:55 onyx kernel: [ 2230.762589] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762595] firewire_ohci: AT spd 2 tl
3b, ffc1 -> ffc0, ack_pending , QR req, fffff000046c
Dec 30 14:30:55 onyx kernel: [ 2230.762618] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762624] firewire_ohci: AR spd 2 tl
3b, ffc0 -> ffc1, ack_complete, QR resp = 00000000
Dec 30 14:30:55 onyx kernel: [ 2230.762652] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762658] firewire_ohci: AT spd 2 tl
3c, ffc1 -> ffc0, ack_pending , QR req, fffff0000470
Dec 30 14:30:55 onyx kernel: [ 2230.762681] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762687] firewire_ohci: AR spd 2 tl
3c, ffc0 -> ffc1, ack_complete, QR resp = 00000000
Dec 30 14:30:55 onyx kernel: [ 2230.762716] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762722] firewire_ohci: AT spd 2 tl
3d, ffc1 -> ffc0, ack_pending , QR req, fffff0000474
Dec 30 14:30:55 onyx kernel: [ 2230.762745] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762751] firewire_ohci: AR spd 2 tl
3d, ffc0 -> ffc1, ack_complete, QR resp = 41445643
Dec 30 14:30:55 onyx kernel: [ 2230.762779] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762786] firewire_ohci: AT spd 2 tl
3e, ffc1 -> ffc0, ack_pending , QR req, fffff0000478
Dec 30 14:30:55 onyx kernel: [ 2230.762808] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762814] firewire_ohci: AR spd 2 tl
3e, ffc0 -> ffc1, ack_complete, QR resp = 2d313130
Dec 30 14:30:55 onyx kernel: [ 2230.762843] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762849] firewire_ohci: AT spd 2 tl
3f, ffc1 -> ffc0, ack_pending , QR req, fffff000047c
Dec 30 14:30:55 onyx kernel: [ 2230.762872] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762878] firewire_ohci: AR spd 2 tl
3f, ffc0 -> ffc1, ack_complete, QR resp = 00000000
Dec 30 14:30:55 onyx kernel: [ 2230.762906] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762913] firewire_ohci: AT spd 2 tl
00, ffc1 -> ffc0, ack_pending , QR req, fffff0000430
Dec 30 14:30:55 onyx kernel: [ 2230.762935] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.762941] firewire_ohci: AR spd 2 tl
00, ffc0 -> ffc1, ack_complete, QR resp = 0002dd9e
Dec 30 14:30:55 onyx kernel: [ 2230.762970] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.762976] firewire_ohci: AT spd 2 tl
01, ffc1 -> ffc0, ack_pending , QR req, fffff0000434
Dec 30 14:30:55 onyx kernel: [ 2230.762997] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.763003] firewire_ohci: AR spd 2 tl
01, ffc0 -> ffc1, ack_complete, QR resp = 1200a02d
Dec 30 14:30:55 onyx kernel: [ 2230.763032] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.763038] firewire_ohci: AT spd 2 tl
02, ffc1 -> ffc0, ack_pending , QR req, fffff0000438
Dec 30 14:30:55 onyx kernel: [ 2230.763059] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.763065] firewire_ohci: AR spd 2 tl
02, ffc0 -> ffc1, ack_complete, QR resp = 13010001
Dec 30 14:30:55 onyx kernel: [ 2230.763093] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.763099] firewire_ohci: AT spd 2 tl
03, ffc1 -> ffc0, ack_pending , QR req, fffff0000448
Dec 30 14:30:55 onyx kernel: [ 2230.763122] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.763128] firewire_ohci: AR spd 2 tl
03, ffc0 -> ffc1, ack_complete, QR resp = 0002aa1b
Dec 30 14:30:55 onyx kernel: [ 2230.763157] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.763163] firewire_ohci: AT spd 2 tl
04, ffc1 -> ffc0, ack_pending , QR req, fffff000044c
Dec 30 14:30:55 onyx kernel: [ 2230.763184] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.763190] firewire_ohci: AR spd 2 tl
04, ffc0 -> ffc1, ack_complete, QR resp = 00201101
Dec 30 14:30:55 onyx kernel: [ 2230.763219] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.763225] firewire_ohci: AT spd 2 tl
05, ffc1 -> ffc0, ack_pending , QR req, fffff0000450
Dec 30 14:30:55 onyx kernel: [ 2230.763246] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.763252] firewire_ohci: AR spd 2 tl
05, ffc0 -> ffc1, ack_complete, QR resp = 15023069
Dec 30 14:30:55 onyx kernel: [ 2230.763454] firewire_core: created
device fw1: GUID 0020110115023069, S400
Dec 30 14:30:55 onyx kernel: [ 2230.763471] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.763478] firewire_ohci: AT spd 2 tl
06, ffc1 -> ffc0, ack_pending , QR req, fffff0000234
Dec 30 14:30:55 onyx kernel: [ 2230.763499] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.763506] firewire_ohci: AR spd 2 tl
06, ffc0 -> ffc1, ack_complete, QR resp = c000001f
Dec 30 14:30:55 onyx kernel: [ 2230.763533] firewire_ohci: IRQ 00000001 AT_req
Dec 30 14:30:55 onyx kernel: [ 2230.763540] firewire_ohci: AT spd 2 tl
07, ffc1 -> ffc0, ack_pending , QW req, fffff0000234 = c000001f
Dec 30 14:30:55 onyx kernel: [ 2230.763563] firewire_ohci: IRQ 00000020 AR_resp
Dec 30 14:30:55 onyx kernel: [ 2230.763569] firewire_ohci: AR spd 2 tl
07, ffc0 -> ffc1, ack_complete, W resp
Dec 30 14:30:55 onyx kernel: [ 2230.783595] ieee1394: raw1394:
/dev/raw1394 device initialized

At the end, the /dev/raw1394 surprised me because I had freshly booted
the machine and I knew the old ieee1394 firewire drivers were
blacklisted. To be sure, I removed the device and then rmmod'd the
modules as root and then plugged the device back in. I received the
same output -- the ieee1394 modules are being loaded automatically:

***@onyx:~#
dv1394 18602 0
ohci1394 30338 1 dv1394
raw1394 25814 0
ieee1394 95219 3 dv1394,ohci1394,raw1394
firewire_ohci 24615 0
firewire_core 54327 1 firewire_ohci
crc_itu_t 1739 1 firewire_core

I also have both a /dev/fw1 and a /dev/raw1394. I assumed, for the
time being, that might be a ubuntu configuration issue...maybe with
lshal or udev rules (?) Then I tried dvgrab 3.5 (dvgrab -buffers 300)
and it appears to select /dev/fw1 automatically -- 'lsof' shows
/dev/fw1 being 'grabbed' by dvgrab and nothing on /dev/raw1394 -- and
the video does come through fine. Yay!

I'm happy that it appears I'll be able to grab video with my desired
pipeline, but I'm still a little miffed that the 1394a port didn't
work. The next step I believe would be to test with a different 1394a
cable to see if that is the point of failure and, of course, I don't
have one at the moment :(

My final question is: are the drivers known to work with 1394a and
1394b TI XIO2213A combo cards? I ask because your 'lspci' output
doesn't mention the XIO2221 like the output from my 'lspci'. Maybe
this is just a difference in lspci 3.1.4 vs. 3.1.7? I guess for now,
I'll assume either there is something wrong with either the 1394a
cable or the 1394a port on the card.

Thanks for all the help,
Charlie

Stefan Richter

2011-01-01 17:24:14 UTC

Permalink

Post by Charlie McMackin

[...]

All of the kernel log looks good.

Post by Charlie McMackin
At the end, the /dev/raw1394 surprised me because I had freshly booted
the machine and I knew the old ieee1394 firewire drivers were
blacklisted. To be sure, I removed the device and then rmmod'd the
modules as root and then plugged the device back in. I received the
dv1394 18602 0
ohci1394 30338 1 dv1394
raw1394 25814 0
ieee1394 95219 3 dv1394,ohci1394,raw1394
firewire_ohci 24615 0
firewire_core 54327 1 firewire_ohci
crc_itu_t 1739 1 firewire_core

raw1394 and dv1394 have module aliases for the AV/C unit identifiers
which the ADVC110's configuration ROM contains, that's why they would
be auto-loaded if you had _no_ blacklist entries.

Maybe your modprobe configuration is not complete, or
an /etc/modprobe.conf exists but was not updated from /etc/modprobe.d/*
or whatever. As far as I know, the modprobe of most current
distributions accesses /etc/modprobe.d/* only if /etc/modprobe.conf
does not exist. Some distributions do not install /etc/modprobe.conf
anymore, others do and provide a script (e.g. /sbin/update-modules)
which creates /etc/modprobe.conf based on the contents
of /etc/modprobe.d/*.

ieee1394 was autoloaded because both raw1394 and dv1394 depend on it,
and ohci1394 was autoloaded because dv1394 depends on it.

Post by Charlie McMackin
I also have both a /dev/fw1 and a /dev/raw1394.

/dev/fw* is created for each node (with active link layer and regular
configuration ROM) by firewire-core¹ if firewire-ohci is bound to the
FireWire controller(s). /dev/raw1394 on the other hand is created by
raw1394¹ whenever raw1394 is beaing loaded, independently of whether
ohci1394 was loaded or not and was bound to any controller or not and
whether any IEEE 1394 nodes are present or not.

¹) actually by udev, when it gets respective events from the kernel
from firewire-core or raw1394 respectively

Post by Charlie McMackin
I assumed, for the
time being, that might be a ubuntu configuration issue...maybe with
lshal or udev rules (?) Then I tried dvgrab 3.5 (dvgrab -buffers 300)
and it appears to select /dev/fw1 automatically -- 'lsof' shows
/dev/fw1 being 'grabbed' by dvgrab and nothing on /dev/raw1394 -- and
the video does come through fine. Yay!

Libraw1394 first searches for /dev/fw* and only accesses /dev/raw1394
if no /dev/fw* could be opened.

Post by Charlie McMackin
I'm happy that it appears I'll be able to grab video with my desired
pipeline, but I'm still a little miffed that the 1394a port didn't
work. The next step I believe would be to test with a different 1394a
cable to see if that is the point of failure and, of course, I don't
have one at the moment :(
My final question is: are the drivers known to work with 1394a and
1394b TI XIO2213A combo cards? I ask because your 'lspci' output
doesn't mention the XIO2221 like the output from my 'lspci'. Maybe
this is just a difference in lspci 3.1.4 vs. 3.1.7?

For completeness,
here is what I get from my XIO2213A card with lspci -nn. (I don't want
to take the card out of the PC right now to read the label on the
chip... Maybe it is actually a XIO2213B, not a XIO2213A.)

08:00.0 PCI bridge [0604]: Texas Instruments XIO2213A PCI Express to PCI Bridge [104c:823e] (rev 01)
09:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments XIO2213A 1394b OHCI with 3-Port PHY [104c:823f] (rev 01)

XIO2213A, XIO2213B, and XIO2221 all have Vendor ID/ Device ID/ Revision
ID = 104c/ 823e/ 01 in their PCIe-PCI bridge part and 104c/ 823f/ 01 in
their PCI-OHCI1394 link layer controller part. I suppose lspci was
updated after v3.1.4 for the two newer chip variants.

It is this card, which is sold as no-name card at various places:
http://www.delock.com/produkte/gruppen/pci-express/Delock_PCI_Express_card_FireWire_A_SLASH_B_89153.html

Post by Charlie McMackin
I guess for now,
I'll assume either there is something wrong with either the 1394a
cable or the 1394a port on the card.

I find it unlikely to be an issue of chip revisions. It could be a
matter of sloppy board layout, bad cable, damaged 6-pin port on the
Canopus, or two or three out of card port -- cable -- Canopus port
being slightly off the spec so that the combination of them does not
work.

XIO2213A, XIO2213B, and XIO2221 have so-called bilingual ports (the
former ones have three and XIO2221 has one port), i.e. ports which can
operate in 1394b signal mode ("beta" mode) or 1394a signal mode
("alpha" mode, data-strobe mode, legacy mode...). This is in contrast
to monolingual 1394b ports which only operate in "beta" mode, i.e. are
not backwards compatible with 1394a devices. (9-pin sockets of
monolingual ports are keyed such that you can only plug 9-pin--9-pin
cables into them, but not the 9-pin end of a 9-pin--6-pin or
9-pin--4-pin cable.)

Card designers can thus provide a FireWire 400 port simply by putting a
6-pin connector onto the terminals of one of the bilingual ports (and
by pulling a certain control terminal high to prevent beta mode to be
used over the 6-pin port, in case that another 1394b device is
connected to that port). For system software, there is no difference
between a bilingual port with 6-pin socket + 6-pin--4/6-pin cable +
1394a device on one hand, or a bilingual port with 9-pin socket +
9-pin--4/6-pin cable + 1394a device on the other hand.

--
Stefan Richter
-=====-==-== ---= ----=
http://arcgraph.de/sr/

Stefan Richter

2011-01-01 17:42:23 UTC

Permalink

Post by Stefan Richter

Post by Charlie McMackin
My final question is: are the drivers known to work with 1394a and
1394b TI XIO2213A combo cards?

[...]

Post by Stefan Richter
For system software, there is no difference
between a bilingual port with 6-pin socket + 6-pin--4/6-pin cable +
1394a device on one hand, or a bilingual port with 9-pin socket +
9-pin--4/6-pin cable + 1394a device on the other hand.

PS: I have already used both combinations myself with my XIO2213 card
and a few different devices.

--
Stefan Richter
-=====-==-== ---= ----=
http://arcgraph.de/sr/

Stefan Richter

2011-01-16 16:50:19 UTC

Permalink

Post by Stefan Richter
Libraw1394 first searches for /dev/fw* and only accesses /dev/raw1394
if no /dev/fw* could be opened.

I misremembered. Libraw1394 first attempts to open /dev/raw1394. If this
fails /or/ if there are zero FireWire buses behind /dev/raw1394, then
libraw1394 proceeds to search for /dev/fw*.

--
Stefan Richter
-=====-==-== ---= =----
http://arcgraph.de/sr/