< Previous | Next > |
![For For](https://www.picclickimg.com/d/l400/pict/123473115667_/OEM-Adaptec-AFW-4300A-3-Port-FireWire-IEEE-1394.jpg)
Problem: FireWire-Installation (Adaptec, AFW-4300A)
- From: Roman Langolf <suse-ml@xxxxxxx>
- Date: Mon, 15 Sep 2003 19:51:07 +0200
- Message-id: <200309151951.07272.suse-ml@xxxxxxx>
Adaptec FireConnect Plus kit provides FireWire/1394 connectivity for PC and Macintosh desktop PCs. It includes a 3 port FireWire PCI Card adapter (AFW-4300) and FireWire cable, for easy plug-and-play to 1394 devices such as hard drives, CD-RWs and DV camcorders. ADAPTEC AFW 4300 DRIVER FOR WINDOWS 7 - If anything, you're far better off buying a used card than a new one. Sabon font free download mac. You are covered by the appropriate driver from the seller-provided price. A NO in this column indicates that this product will not be supported for use with. Aug 16, 2020 With the Adaptec AFW-4300 Host Adapter or AFW-4300, you can connect Digital Video DV camcorders or other devices with a 1394 also known as FireWire or i.LINK digital interface to any PC compatible or Power Macintosh computer with PCI expansion slots. 0 Items Online ordering is enabled again!, please note that we will resume shipping on. Mazak integrex operation manual. ADAPTEC AFW-2100 DRIVER FOR WINDOWS - Information in this document is subject to change without notice. Be the first to review this item. Compare with similar items. Read more about the condition. Sold by Woodcraft Patterns. ComiXology Thousands of Digital Comics. Get an immediate offer. Uploader: Shaktishakar Date Added: 21 October 2004 File Size: 17.4. Troubleshooting FireWire Driver Installation Contents. Adaptec FireConnect3 AFW1430A 3 6-pin FW 400 Ports. Adaptec AFW-4300A 3 FireWire 400 ports (Discontinued) PCI Express Cards Recommended Manufacturer Mfr Part No. Comment Belkin F5U504ea 2 6-pin FW 400 ports.
Hallo ihr alle,
ich habe Adaptec (AFW-4300A) FireWire-Karte gekauft, laut:
http://www.linux1394.org/view_device.php?id=476
funktioniert die Karte einwandfrei, bei mir aber leider nicht.
Was ich schon gemacht habe:
lspci:
00:0a.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8024
_____
Ich habe neuen Kernel (2.4.23-pre4) mit folgenden Optionen kompiliert:
#######
<M> IEEE 1394 (FireWire) support (EXPERIMENTAL)
--- Device Drivers
<M> Texas Instruments PCILynx support
<M> OHCI-1394 support
--- Protocol Drivers
<M> OHCI-1394 Video support
<M> SBP-2 support (Harddisks etc.)
[*] Enable Phys DMA support for SBP2 (Debug)
<M> Ethernet over 1394
<M> OHCI-DV I/O support
<M> Raw IEEE1394 I/O support
<M> IEC61883-1 Plug support
<M> IEC61883-6 (Audio transmission) support
[*] Excessive debugging output
[*] OUI Database built-in
Dann habe ich module geladen:
modprobe ohci1394
modprobe raw1394
#######
lsmod:
raw1394 23020 0 (unused)
ohci1394 28160 0 (unused)
ieee1394 185824 0 [raw1394 ohci1394]
#######
dmesg:
ohci1394: $Rev: 1010 $ Ben Collins <bcollins@xxxxxxxxxx>
ohci1394_0: Remapped memory spaces reg 0xd0a72000
ohci1394_0: Soft reset finished
ohci1394_0: Iso contexts reg: 000000a8 implemented: 0000000f
ohci1394_0: 4 iso receive contexts available
ohci1394_0: Iso contexts reg: 00000098 implemented: 000000ff
ohci1394_0: 8 iso transmit contexts available
ohci1394_0: GUID: 00309500:a0020ffd
ohci1394_0: Receive DMA ctx=0 initialized
ohci1394_0: Receive DMA ctx=0 initialized
ohci1394_0: Transmit DMA ctx=0 initialized
ohci1394_0: Transmit DMA ctx=1 initialized
ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=[5] MMIO=[ee004000-ee0047ff]
Max Packet=[2048]
ohci1394_0: request csr_rom address: c367b000
ohci1394_0: IntEvent: 00020010
ohci1394_0: irq_handler: Bus reset requested
ohci1394_0: Cancel request received
ohci1394_0: Got RQPkt interrupt status=0x00008409
ohci1394_0: Single packet rcv'd
ohci1394_0: Got phy packet ctx=0 . discarded
ohci1394_0: IntEvent: 00010000
ohci1394_0: SelfID interrupt received (phyid 0, root)
ohci1394_0: SelfID packet 0x807f8c56 received
ieee1394: Including SelfID 0x568c7f80
ohci1394_0: SelfID for this node is 0x807f8c56
ohci1394_0: SelfID complete
ohci1394_0: PhyReqFilter=ffffffffffffffff
ieee1394: selfid_complete called with successful SelfID stage .
irm_id: 0xFFC0 node_id:
0xFFC0
ieee1394: NodeMgr: Processing host reset for knodemgrd_0
ieee1394: Initiating ConfigROM request for node 0-00:1023
ieee1394: send packet local: ffc00140 ffc0ffff f0000400
[..]
ieee1394: NodeMgr: raw=0xe000a002 irmc=1 cmc=1 isc=1 bmc=0 pmc=0
cyc_clk_acc=0 max_rec=204 8 gen=0 lspd=2
[..]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00309500a0020ffd]
ieee1394: send packet 100: ffff0100 ffc0ffff f0000234 1f0000c0
ohci1394_0: Inserting packet for node 0-63:1023, tlabel=0, tcode=0x0,
speed=0
ohci1394_0: Starting transmit DMA ctx=0
ohci1394_0: IntEvent: 00000001
ohci1394_0: Got reqTxComplete interrupt status=0x00008011
ohci1394_0: Packet sent to node 63 tcode=0x0 tLabel=0x00 ack=0x11
spd=0 data=0x1F0000C0 ct
x=0
raw1394: /dev/raw1394 device initialized
#######
testlibraw meint:
couldn't get handle: No such device
This probably means that you don't have raw1394 support in the kernel
or that you haven't loaded the raw1394 module.
Zur Not habe ich noch pcilynx probiert hochzuladen:
#######
$: modprobe pcilynx
/lib/modules/2.4.23-pre4/kernel/drivers/ieee1394/pcilynx.o:
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters
/lib/modules/2.4.23-pre4/kernel/drivers/ieee1394/pcilynx.o: insmod
/lib/modules/2.4.23-pre4/kernel/drivers/ieee1394/pcilynx.o failed
/lib/modules/2.4.23-pre4/kernel/drivers/ieee1394/pcilynx.o: insmod
pcilynx failed
####
ls -ahl /dev/video1394
crw-rw-rw- 1 root root 172, 0 Sep 15 18:48 /dev/video1394
ls -ahl /dev/raw1394
crw-rw-rw- 1 root root 172, 0 Sep 15 18:49 /dev/raw1394
Ich verstehe nicht wo das Problem ist, wieso findet er die Karte
nicht?
THX
Roman
--
http://www.jesus.de
http://www.thehope.de
http://www.ec-thueringen.de
Adaptec Afw-4300
< Previous | Next > |