Solaris

Dear all,

Every time I boot my Ultra 60, after initializing the memory I always have to type boot at the ok>

Rebooting with command boot
Boot device: disk0 File and args :
Trap 3e
(0) ok

I've tried to re-installed the machine but result is the same...

What would be the problem?

Thx
Regards

Hi,
dunno if this things i've learned about Solaris...helps, it says your superblock (disk) may be damaged

@andryk

I've read your link.. It says that I have to create newfs on c0t0d0s0.. If I do that will it erase the O/S and have to be re-installed the O/S?

Thx

Well, it says to locate alternative superblock (newfs -N) not to create a new filesystem, with that information you might be able to do some solaris voodoo trick to get your disk up agen... but i admit im no solaris expert and cant help you further

When there is nowhere else to turn to, go check sunsolve.

Document Audience: PUBLIC
Document ID: 200515
Old Document ID: (formerly 101391)
Title: Sun Systems With a XVR-100 Graphics Accelerator Connected to Certain Third Party Monitors May Fail to Boot
Copyright Notice: Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved
Update Date: Tue May 31 00:00:00 MDT 2005
Solution Type Sun Alert

Solution 200515 : Sun Systems With a XVR-100 Graphics Accelerator Connected to Certain Third Party Monitors May Fail to Boot

Related Categories

* Home>Content>Sun Alert Criteria Categories>Availability
* Home>Content>Sun Alert Release Phase>Resolved



Previously Published As

101391



Product

Sun XVR-100 Graphics Accelerator



Bug ID

4933514



Date of Resolved Release

21-NOV-2003



SA Document Body

OR1PMID Internal ID use only.


Impact

Sun systems equipped with a XVR-100 Graphics Accelerator may fail to boot if certain third party monitors are attached to the HD15 interface.

Contributing Factors

This issue can occur on the following platforms:

SPARC Platform

* XVR-100 Graphics Accelerator for 32MB without PROM version 1.10
* XVR-100 Graphics Accelerator for 64MB without PROM version 2.3

The described issue only occurs if both of the the following are true:

* The Sun system has a XVR-100 Graphics Accelerator installed
* The third party monitor is connected to the XVR-100 Graphics Accelerator via the HD15 interface

To determine if the XVR-100 Graphics Accelerator is installed, use the following command:

# /usr/platform/sun4u/sbin/prtdiag

An output line containing "SUNW,XVR-100" in the "Name" column indicates a XVR-100 Graphics Accelerator is installed.

To determine the XVR-100 PROM revision, type the following command:

# fbconfig -dev /dev/fbs/pfb0 -prconf | grep PROM

If there is more than one XVR-100 in the system, "pfb0" can be replaced by "pfb1", "pfb2", ect.

Note: The XVR-1200 Graphics Accelerator is not supported on Solaris 7.

Symptoms

Should the described issue occur, the system will not boot and the screen remains black. There is no output from the Open Boot Prom or from Solaris. If a serial terminal is connected to the system, the PCI check in POST aborts with "trap 3e".

probing /pci@8,700000 Device 3 SUNW,XVR-100 Trap 3e
{0} ok boot
FATAL: OpenBoot initialization sequence prematurely terminated.
FATAL: system is not bootable, boot command is disabled


Workaround

To work around the described issue, boot the system without the monitor connected to the XVR-100 HD15 interface, then reconnect the monitor after the system has booted.

Resolution

This issue is addressed with the following components:

* XVR-100 Graphics Accelerator for 32MB with PROM version 1.10
* XVR-100 Graphics Accelerator for 64MB with PROM version 2.3



Modification History

MWQHESP Internal ID use only.


Date: 31-MAR-2004

* Updated Contributing Factors and Resolution sections



Attachments

This solution has no attachment