Re: re0 no carrier problem - Patches found in archives didn't work.
[04:12 19-06-2005] Tom Pepper [EMAIL PROTECTED] 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. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: re0 no carrier problem - Patches found in archives didn't work.
At 07:09 AM 6/19/2005, Marcin Koziej wrote: [04:12 19-06-2005] Tom Pepper [EMAIL PROTECTED] 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? I may be replying to the wrong thread, but if I remember a previous post, this is for a realtek gig-e card going to a gig-e switch... Just another obvious point but you are using either Cat-5e or Cat-6 cables, right? Just thought I'd offer another obvious suggestion. :) Vinny Abello Network Engineer Server Management [EMAIL PROTECTED] (973)300-9211 x 125 (973)940-6125 (Direct) PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A Tellurian Networks - The Ultimate Internet Connection http://www.tellurian.com (888)TELLURIAN Courage is resistance to fear, mastery of fear - not absence of fear -- Mark Twain ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: re0 no carrier problem - Patches found in archives didn't work.
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... 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? Not sure if it is solely switch related. I encountered the very same problem for months now using different links ans switches. Moreover, it seems to be FreeBSD specific since the same machine works better with others OSes. See PR kern/80005 for a more long description on a very similar problem. -- -jpeg. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: re0 no carrier problem - Patches found in archives didn't work.
At 07:09 AM 19/06/2005, Marcin Koziej wrote: 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 Both sides have to agree to the setting. ie if the switch is set to autoneg, your network card must also be set to autoneg and vice versa.Unless its a managed switch, leave the NIC as autonegotiate. If its still failing, I suspect its something with the re driver. Its possible the NIC and switch dont like each other (it has happened in the past with certain vendors) but this is pretty rare these days. ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
