From owner-freebsd-alpha Thu Apr 20 11:19:33 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 46BB037BA91 for ; Thu, 20 Apr 2000 11:19:29 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA00765; Thu, 20 Apr 2000 14:19:27 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA04668; Thu, 20 Apr 2000 14:19:27 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 20 Apr 2000 14:19:27 -0400 (EDT) To: Gheorghe Ardelean Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: firmware updating problems In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14591.18469.739521.636337@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gheorghe Ardelean writes: > > Hello, > > I have (at our Univ) a DEC3000 Model400 and I'd like to install > FreeBSD on it. > > Just now I'm experincing problems with firmware upgrade. > There is no floppy drive on if so I managed to upgrade via BOOTP > from an PC running FreeBSD 3.4-RELEASE Be VERY VERY careful. Upgrading past a certain revision of the firmware without upgrading the SROM chip will make a 3000/400 unusable. Unfortunately, its been years since I've dealt with machines this old, so I don't know the firmware revisions off the top of my head. A www search will probably turn up something in the osf1 managers mailing lists about this. Again, upgrading a 3000/400 to a modern firmware revisions (anything in the last 4-5 years or so) should be undertaken with extreeme caution. > 21:04:27.771579 jad2.uvt.ro.60581 > phys-ppp-gw.uvt.ro.tftp: 24 tftp-#0 > [tos 0x1] (ttl 30, id 2447, bad cksum c976!) Some revisions of the dec firmware generate bad checksums when netbooting via bootp. Mop might be an option.. Cheers, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message