On Mon, 18 Sep 2000, Ben Smithurst wrote:
> Does anyone have any clue what could cause errors like this? I've
> been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure
> there's more information I should be giving, so just let me know what
> to find. dmesg is at the end.
...
> ep0:
On Mon, 18 Sep 2000, Ben Smithurst wrote:
> Does anyone have any clue what could cause errors like this? I've
> been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure
> there's more information I should be giving, so just let me know what to
> find. dmesg is at the end.
Does anyone have any clue what could cause errors like this? I've
been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure
there's more information I should be giving, so just let me know what to
find. dmesg is at the end.
Sep 18 07:56:01 lithium last message repeated 17 times
Sep
On Wed, 10 Nov 1999, Doug Ambrisko wrote:
> On one out of 8 machines, I ran into this problem. My network is running
> at 100BaseTX. I noticed that ifconfig showed OACTIVE flag set and I
> was running in autosense mode. So I setup the media to 100BaseTX and now
> it works okay.
>
> My guess is
Bill Marquette writes:
| For the last week and a half or so I've been trying to track this down
| assuming it was a configuration error on my part or a problem with my
| ISP's DHCP configuration. After switching from a DEC 20141 chipset card
| to a 3com 3c905, I found I was still having problems
For the last week and a half or so I've been trying to track this down
assuming it was a configuration error on my part or a problem with my
ISP's DHCP configuration. After switching from a DEC 20141 chipset card
to a 3com 3c905, I found I was still having problems although the error
message had
