Thread: Re: Ann : Capture & Ether1394
Brought to you by:
aeb,
bencollins
Menu
▾
▴
linux1394-devel
|
From: <fra...@ya...> - 2000-05-23 07:51:30
|
> I have been trying to get your ethernet driver to > work on my machines, > but have had no luck. I can insmod the driver and > do an ifup no problem, > but when I try to do anything on the network between > the two machines the > kernel generates an oops and then panics. > > I have noticed that the ethernet address always > comes up as: > HWaddr 00:00:69:65:65:00 > on both machines. > You should insmod the IEEE 1394 subsystem modules (ieee1394.o and ohci1394.o) FIRST on ALL the machines. And then insmod eth1394.o and ifup interfaces on all the machines. This will fix the problem with HW address. I have updated the README file of http://www.chez.com/kayle/IEEE_1394/ether_1394.tgz if you need more informations. ----- Franck Bonin ___________________________________________________________ Do You Yahoo!? Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr |
|
From: <fra...@ya...> - 2000-05-24 11:18:13
|
--- fir...@se... a écrit : >
>
> On Tue, 23 May 2000, [iso-8859-1] Franck Bonin
> wrote:
>
> > You should insmod the IEEE 1394 subsystem modules
> > (ieee1394.o and
> > ohci1394.o) FIRST on ALL the machines.
> >
> > And then insmod eth1394.o and ifup interfaces on
> all
> > the machines.
> >
> > This will fix the problem with HW address.
>
> Ok, I did the following:
>
> Machine 1:
> insmod ieee1394.o
> insmod pcilynx.o
> insmod raw1394.o
>
> Machine 2:
> insmod ieee1394.o
> insmod pcilynx.o
> insmod raw1394.o
>
> Machine 1:
> insmod eth1394.o
> ifup eth3
>
> Machine 2:
> insmod eth1394.o
> ifup eth3
>
> Now when I do a ifconfig eth3 I get:
>
> Machine 1:
> eth3 Link encap:Ethernet HWaddr
00:00:69:65:65:00
> inet addr:192.168.3.10 Bcast:192.168.3.255
Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:186
Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0
frame:0
> TX packets:0 errors:0 dropped:0 overruns:0
carrier:0
> collisions:0 txqueuelen:100
>
> Machine 2:
> eth3 Link encap:Ethernet HWaddr
00:00:69:65:65:00
> inet addr:192.168.3.11 Bcast:192.168.3.255
Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:186
Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0
frame:0
> TX packets:0 errors:0 dropped:0 overruns:0
carrier:0
> collisions:0 txqueuelen:100
>
> This driver does not rely on any type of card does
> it?
>
> Judd Tracy
> jt...@is...
>
This is very strange because the last byte of each HW
address should
be the node number. See line 481 of file eth1384.c :
dev->dev_addr[ETH_ALEN-1] = priv->host->node_id &
0x3f;
This should works but I haven't tested with pcilynx
driver...
So I may ask few questions :
1/ Are nodes numbers correctly generated ? (See with
gscanbus)
1.1/ If yes, is eth1394 find your card ? (See with
dmesg when you insmod
eth1394 and send me the output if you want)
Card detection is handle by function add_host(),
line 354
and cards found are used by function
ether1394_init(), near line 735.
1.2/ If no, did you try with the modules I have
include with eth1394 archive ?
2/ If the driver init correctly except for HW address,
you could
assign one to each node yourself line 481.
-----
Franck Bonin
___________________________________________________________
Do You Yahoo!?
Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr
|
|
From: <fir...@se...> - 2000-05-23 17:42:31
|
On Tue, 23 May 2000, [iso-8859-1] Franck Bonin wrote:
> You should insmod the IEEE 1394 subsystem modules
> (ieee1394.o and
> ohci1394.o) FIRST on ALL the machines.
>
> And then insmod eth1394.o and ifup interfaces on all
> the machines.
>
> This will fix the problem with HW address.
Ok, I did the following:
Machine 1:
insmod ieee1394.o
insmod pcilynx.o
insmod raw1394.o
Machine 2:
insmod ieee1394.o
insmod pcilynx.o
insmod raw1394.o
Machine 1:
insmod eth1394.o
ifup eth3
Machine 2:
insmod eth1394.o
ifup eth3
Now when I do a ifconfig eth3 I get:
Machine 1:
eth3 Link encap:Ethernet HWaddr 00:00:69:65:65:00
inet addr:192.168.3.10 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:186 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Machine 2:
eth3 Link encap:Ethernet HWaddr 00:00:69:65:65:00
inet addr:192.168.3.11 Bcast:192.168.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:186 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
This driver does not rely on any type of card does it?
Judd Tracy
jt...@is...
|
|
From: Andreas B. <and...@mu...> - 2000-05-24 11:51:41
|
On Tue, May 23, 2000 at 01:39:42PM -0400, fir...@se... wrote: > Ok, I did the following: > > Machine 1: > insmod ieee1394.o > insmod pcilynx.o > insmod raw1394.o [...] > Machine 1: > insmod eth1394.o > ifup eth3 [...] > Now when I do a ifconfig eth3 I get: > > Machine 1: > eth3 Link encap:Ethernet HWaddr 00:00:69:65:65:00 > inet addr:192.168.3.10 Bcast:192.168.3.255 Mask:255.255.255.0 [...] > Machine 2: > eth3 Link encap:Ethernet HWaddr 00:00:69:65:65:00 > inet addr:192.168.3.11 Bcast:192.168.3.255 Mask:255.255.255.0 [...] > This driver does not rely on any type of card does it? If it does rely on the GUID being unique, then sorry, that's not true for the PCILynx yet. I found nothing in the chip holding the GUID so the PCILynx config ROM contains a fixed GUID for now (and violates the 1394 standard by doing this). -- Andreas E. Bombe <and...@mu...> DSA key 0x04880A44 http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/ |
Thanks for helping keep SourceForge clean.
X