Date: Sun, 19 Jun 2005 13:09:02 +0200 From: Marcin Koziej <creep@daedalus.desk.pl> To: Tom Pepper <tom@blorp.com>;, freebsd-stable@freebsd.org Subject: Re: re0 "no carrier" problem - Patches found in archives didn't work. Message-ID: <20050619110902.GA705@daedalus.desk.pl> In-Reply-To: <BEAF69C8-DB9E-4554-A3CC-7749F5C9D2CA@blorp.com> References: <20050618234921.GA1740@daedalus.desk.pl> <BEAF69C8-DB9E-4554-A3CC-7749F5C9D2CA@blorp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[04:12 19-06-2005] Tom Pepper <tom@blorp.com> > this may seem obvious, but do you still have the same issue if you > statically define the mediatype to a fixed link speed and duplex? > lots of interfaces have problems negotiating autoselect with > switches, as protocols vary widely. the blinking is indicative of > autoselect setup woes... This wasn't obvious for me! Thanks for the answer! When I set the media by hand it showed 'active', but no data could be transmitted (yellow link diode on switch, not blinking). I then pulled the switch with my home lan from the wall and plugged my re0 instead - It worked! So this seems to be the %$R#(@%*$ switch issue. The funny thing is, that with media set manually (or sometimes with autoselect) everything works fine with this switch (i have used it all day yesterday till evening without problem). Now, when i wait some time with media manually set, it starts transmitting data and everything works fine. Why does it happen? Why is it so unpredictible? Can it be fixed in software, or should i throw the switch out the window and by a new one? Thanks and best regards, m.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050619110902.GA705>