--------Original post--------
> Every time that I boot my AlphaServer 200 (DU v3.2D-1), the tu0 ethernet
> device toggles between UTP (10BASET) and AUI (10BASE5). I'm connected to
> the network via tu0's UTP connector.
>
> More specifically, during the boot process it toggles between..
>
> tu0: auto sensing: selected AUI (10BASE5) port: no carrier
>
> and the next boot would appear as..
>
> tu0: auto sensing: selected UTP (10BASET) port
>
> How do I turn off this auto sensing?
>
> At the console level, I have "ewa0_mode Twisted-Pair" set (visible with the
> >>> SHOW CONFIG command), but the auto sensing seems to take precedence.
>
> How do I disable this auto sensing, and/or, why would it select the port
> with no carrier?
>
> I did power down the machine, thinking this may be necesary for the
> "ewa0_mode Twisted-Pair" to take effect. No luck.
The fix involved upgrading to the latest and greatest SRM firmware, that which
can be obtained from
http://ftp.digital.com:80/pub/Digital/Alpha/firmware.
This advise was sent by Digital Unix engineer Rajul Shah (rajul_at_zk3.dec.com),
I'll include his reply below...
Thanks to Rajul and to all the others who replied!
-Bill Sadvary
Dickinson College
> Hi Bill,
>
> This is the Digital Unix engineer responsible for the tu driver. Not
> entirely sure why the driver toggles between the two ports. I presume
> you're using the UTP port and have it connected to a proper repeater
> or whatever. The driver relies on the Link Integrity Test passing on
> this port to select UTP. Some boxes do not support the Link test.
> Perhaps this is why the driver is not auto sensing correctly.
>
> In any event, if you upgrade your firmware to the latest SRM console,
> the driver will quit auto sensing and always select whatever you set
> with the EWA0_MODE variable. The driver output will look like this:
>
> tu0: console mode: selecting UTP (10BaseT) port
>
> If you continue to have problems with this, let me know.
>
> Regards.
> Rajul Shah
Received on Thu Mar 21 1996 - 16:36:02 NZST