Thread: DFW-500 Help!
Brought to you by:
aeb,
bencollins
From: Sundar A. <rad...@ya...> - 2002-01-24 16:06:53
|
Hi, I have installed a D-Link DFW-500 firewire pci adapter in my smp athlon machine. I am running 2.4.17. I am not able to get the card recognized with ohci1394? The hardware compatibility list says that the card is compatible! I was trying to get a pocket hard drive working to start with. This one works perfectly with my iBook running 2.4.17 with ohci1394 and sbp2. But in my new machine, the messages I get as soon as I load ohci1394 - +++++++++++++ ohci1394: $Revision: 1.80 $ Ben Collins <bco...@de...> ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[5] MMIO=[f0009000-f0009800] Max Packet=[2048] ieee1394: got invalid ack 3 from node 65473 (tcode 4) ieee1394: ConfigROM quadlet transaction error for node 1:1023 ieee1394: got invalid ack 3 from node 65473 (tcode 4) ieee1394: ConfigROM quadlet transaction error for node 1:1023 ieee1394: got invalid ack 3 from node 65473 (tcode 4) ieee1394: ConfigROM quadlet transaction error for node 1:1023 ieee1394: Giving up on node 1:1023 for ConfigROM probe, too many errors +++++++++++++ I am not sure whether the card has been detected yet! OR is it a problem with my pocket drive? If so why would it work with my ibook? I would be very grateful for any (all the) help. Thank you very much. --Aman __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com |
From: Stefan R. <ric...@ba...> - 2002-01-24 19:56:37
|
On 24 Jan, Sundar Amancherla wrote: > ieee1394: ConfigROM quadlet transaction error for node 1:1023 This has been reported by other users, too, and it could be a newly introduced bug. You can (a) wait for when this problem got solved or (b) download an older drivers/ieee1394 directory from CVS (and make dep/ recompile/ reinstall/ reboot the kernel and modules). I'm still using drivers from mid October '01 and haven't ever seen those mentioned messages. > I am not sure whether the card has been detected yet! Simply --- if you don't get these messages if no device is plugged onto your card, then you can be fairly sure the card is fine. -- Stefan Richter - = = = = = - = - - = - - - - = = = - - - http://www.bauwesen.tu-cottbus.de/~richtest/ |
From: Sundar A. <rad...@ya...> - 2002-01-24 20:25:33
|
--- Stefan Richter <ric...@ba...> wrote: > > ieee1394: ConfigROM quadlet transaction error for > node 1:1023 > > This has been reported by other users, too, and it > could be a > newly introduced bug. You can (a) wait for when this > problem got > solved or (b) download an older drivers/ieee1394 > directory from > CVS (and make dep/ recompile/ reinstall/ reboot the > kernel and > modules). > > I'm still using drivers from mid October '01 and > haven't ever > seen those mentioned messages. > > > I am not sure whether the card has been detected > yet! > > Simply --- if you don't get these messages if no > device is > plugged onto your card, then you can be fairly sure > the card is > fine. I am using same kernel on my ibook and I do not get these messages! IS this the card? __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com |
From: Sundar A. <rad...@ya...> - 2002-02-14 18:08:23
|
--- Stefan Richter <ric...@ba...> wrote: > On 24 Jan, Sundar Amancherla wrote: > > ieee1394: ConfigROM quadlet transaction error for > node 1:1023 > > This has been reported by other users, too, and it > could be a > newly introduced bug. You can (a) wait for when this > problem got > solved or (b) download an older drivers/ieee1394 > directory from > CVS (and make dep/ recompile/ reinstall/ reboot the > kernel and > modules). > > I'm still using drivers from mid October '01 and > haven't ever > seen those mentioned messages. > > > I am not sure whether the card has been detected > yet! > > Simply --- if you don't get these messages if no > device is > plugged onto your card, then you can be fairly sure > the card is > fine. > -- > Stefan Richter > - = = = = = - = - - = - - - - = = = - - - > http://www.bauwesen.tu-cottbus.de/~richtest/ > > > _______________________________________________ > mailing list Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux1394-user _______________________ Hi, This is a bit late though! I have been trying various ways of getting my card working. When I ran testlibraw - ++++++++++++++++++++++++++++++++++++ [root@mse-p014 aman]# testlibraw successfully got handle current generation number: 2 1 card(s) found nodes on bus: 3, card name: ohci1394 using first card found: 3 nodes on bus, local ID is 0, IRM is 63 doing transactions with custom tag handler trying to send read request to node 0... completed with value 0xcc1a2251 trying to send read request to node 1... failed with error: Resource temporarily unavailable trying to send read request to node 2... failed with error: Resource temporarily unavailable using standard tag handler and synchronous calls trying to read from node 0... completed with value 0x12432251 trying to read from node 1... failed with error: Resource temporarily unavailable trying to read from node 2... failed with error: Resource temporarily unavailable testing FCP monitoring on local node got fcp command from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef got fcp response from node 0 of 8 bytes: 01 23 45 67 89 ab cd ef polling for leftover messages +++++++++++++++++++++++++++++++++++++++++++++++ Does this mean that the card is OK and I still have some hope! As per your previous suggestion I would like to try some older drivers. Which ones I should try? Thanks for all the help indeed. -- Aman __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com |