whiteley@nadc.arpa (D. Whiteley) (12/20/88)
We just bought a Sun 3/280 running SunOS 4.0. When I boot the machine, I
get the following error message:
EEPROM boot device...xy(0,0,0)
xy: cannot exec first read.
Device not found
>
Then I type a 'b' to trying booting it again and everything is fine. Has
anyone ever seen this error before?
Thanks,
Denice Whiteley
whiteley@nadc.arpabrent@tis.llnl.gov (Brent Chapman) (01/04/89)
> We just bought a Sun 3/280 running SunOS 4.0. When I boot the machine, I > get the following error message: > > EEPROM boot device...xy(0,0,0) > xy: cannot exec first read. > > Device not found > > > > Then I type a 'b' to trying booting it again and everything is fine. Has > anyone ever seen this error before? I've been having this same problem intermittently on a 3/280 running SunOS 3.5 since Sun swapped my CPU board a month or so ago. It seems to hang on about 10-20% of the automatic (post-crash) or manual reboots. My Sun engineer and I suspect a PROM bug (we've got Rev 2.7 now), but he hasn't been able to confirm that for me yet. Questions for the rest of you having this problem (so that we can help Sun track it down and fix it): 1) What hardware are you using? Does this only affect 3/2x0s? 2) What PROM level do you have? Unfortunately, I don't think that the revision level is printed anywhere except in the power-on self-test banner. 3) Did the problem appear shortly or immediately _after_ your PROM (or perhaps your whole CPU board) was upgraded or replaced? Thanks! -Brent -- Brent Chapman Capital Market Technology, Inc. Computer Operations Manager 1995 University Ave., Suite 390 brent@capmkt.com Berkeley, CA 94704 {cogsci,lll-tis,uunet}!capmkt!brent Phone: 415/540-6400