Hi
Thanks to
Jim.Zelenka_at_cs.cmu.edu
Alan.Davis_at_digital.com
Knut.Hellebo_at_nho.hydro.com
Nick.Batchelor_at_unilever.com
Stephen.Walter_at_hawke.co.uk
Valentin.Nakov_at_physik.tu-ilmenau.de
aideen_at_persimmon.co.uk
alan_at_nabeth.cxo.dec.com
bensond_at_ucdavis.edu
campa_at_ge.INFM.it
jsurlow_at_hydra.acs.uci.edu
lucio_at_ifctr.mi.cnr.it
merrill_at_stsci.edu
phwatso_at_cooper-energy-services.com
russel_at_maths.unsw.EDU.AU
sidney_at_ifi.unicamp.br
simon.reavell_at_bbsrc.ac.uk
steinberg_at_acphyz.physik.rwth-aachen.de
tpb_at_zk3.dec.com
who all replied to my question.
As most suggested, setting the ewa0_mode env var in the PROM to
Twisted-Pair was part of the solution. Connecting to a live ethernet
port was the second part!! If I now move the 2 small switches back to
the normal (not reset RTC and NVRAM) position I presume (hope) that
this info will remain stored.
Thanks to all
Kevin
On Fri, 13 Mar 1998, Kevin Maguire wrote:
> I have inherited an AS 255. I have no owners manual, in fact no docs
> at all on the machine itself. When I tried to boot it tried to use an
> external disk drive, a drive which is completely dead. I tried to
> boot from another device, but the console was password secured. The
> password (if it is the same as my 3000/300) is a 16 digit hex number,
> no chance of guessing it. We did have the root pasword from the
> previous owner, but had no easy way to get the kernel up and running.
>
> Looking inside the box we found some switches. One allowed us to
> "Reset the RTC and NVRAM". Presuming this also made the system
> "non-secure" we moved the switches, and tried to boot. Booting from
> the internal disk we got DUnix 3.2D-1 up and running, success!!!
>
> We wanted to install 4.0D anyway, so I booted from the CDROM, told it
> it could overwrite the internal disk (RZ26), and let it do a default
> installation. The OS seems to be okay, so I reset the console env
> vars so it would boot from that device as default.
>
> Now we have the problem. Trying to configure networking I can not get
> it to talk to the outside world. It reports the ethernet card as
> device tu0, and ifconfig tells us that device is up and running.
> Everything else on the Checklist is much the same as my other DEC
> systems. But netstat -r hangs, and "netstat -Itu0 -z" tells us all
> packets fail due to "collision detect check failure".
>
> Looking at /var/adm/messages it seems to think the device is 10base5,
> and it says there is no carrier, but our network ports are all
> 10baseT. How do I change the software to match? Is it a software
> (DYUbnix) thing, or is it a NVRAM varaibale that must be changed.
>
> Thanks for any help in advance
>
> Kev
> --
> \\\|///
> \\ - - //
> ( _at_ _at_ )
> +-----------------oOOo-(_)-oOOo---------------------+
> | Kevin Maguire Daresbury Laboratory |
> | K.Maguire_at_dl.ac.uk Warrington |
> | Tel: (01925) 603221 Cheshire |
> | Fax: (01925) 603634 United Kingdom |
> +-------------------------Oooo----------------------+
> oooO ( )
> ( ) ) /
> \ ( (_/
> \_)
Received on Mon Mar 16 1998 - 16:29:09 NZST