[openbeosnetteam] Re: Testing
- From: "David Reid" <dreid@xxxxxxxxxxxx>
- To: <openbeosnetteam@xxxxxxxxxxxxx>
- Date: Sun, 10 Feb 2002 12:49:09 -0000
I don't think you're doing anything wrong, in fact I think you did pretty
well for someone who's never used CVS before!
It's not a dumb question so I guess you miss that honour this time (maybe
next time??) :)
The problem is probably that the card is in use by the existing net_server.
If you have /dev/net/tulip/0 then you have indeed got a tulip compatible
card in your system. Go to the network preferences and disable the card
there, restart and then try the test again.
I'm lucky in that I have 2 supported network cards on my system, so I have
one disabled and therefore testable for the new code and the other able to
connect me to the outside world.
Also, try the new net_srv test app (do a cvs update -dP to get the new
code).
david
>
> OK, someone said there are no dumb questions, so I'll do my best to
> come up with the first one.
>
> I'm trying to test all the updates on my system. I've never used CVS
> before tonight, but I managed to get it setup and download everything
> in anonymous mode, so that's good. I have a built-in Intel Ethernet
> card that never worked and a linksys PCI that I added that does work.
> When I go into Devices, neither card is listed by name, but I'm pretty
> sure the Linksys is DEC-based and therefore a tulip card (but you know
> what they say about assuming). I have the device listed is "/dev/net/
> tulip/0" in testread. When I run testread, I get:
>
> -----------------------------------------------------------------------
> ---------------
> $ testread
> allocated a 4096 byte block starting at 0xa0000000
> allocated a 4096 byte block starting at 0xa0001000
> Network Card Read Test
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Have you set the device path to point at your card=3F
> If not you probably won't see anything!
>
> Couldn't open the device! General OS error
> -----------------------------------------------------------------------
> ---------------
>
> Obviously, that's not right, so I changed the dev line to point to "/
> dev/net/ether/0", which is also available, thinking maybe my linsys
> isn't a tulip card, and I get the following:
>
> -----------------------------------------------------------------------
> ---------------
> $ testread
> allocated a 4096 byte block starting at 0xa0000000
> allocated a 4096 byte block starting at 0xa0001000
> Network Card Read Test
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Have you set the device path to point at your card=3F
> If not you probably won't see anything!
>
> Opened the device.
> MAC address 00:00:00:00:00:00
> Unable to set promiscuous. General OS error
> It's an 802.x encapsulated packet - type 0000
> Ethernet packet from 00:00:00:00:00:00 to 00:00:00:00:00:00: proto
> unknown (0000)
>
> It's an 802.x encapsulated packet - type 0000
> Ethernet packet from 00:00:00:00:00:00 to 00:00:00:00:00:00: proto
> unknown (0000)
> -----------------------------------------------------------------------
> ---------------
>
>
> The 802.x message is repeated over and over really fast. OK, that's
> not it either, so I must not be doing something wrong. Is it just a
> matter of compiling the new stuff and then running teasread=3F Or Am I
> supposed to be killing the current net=5Fserver and running the new one I
> compiled or anything like that=3F Any ideas=3F
>
>
> Peder
>
>
>
>
>
Other related posts:
