Sponsored Content
Operating Systems Solaris Weird behavior on a Sun Fire V120 running solaris 10. Post 302139186 by jsandova on Thursday 4th of October 2007 07:28:18 PM
Old 10-04-2007
Weird behavior on a Sun Fire V120 running solaris 10.

All,
After a power loss I went to power on our sun fire v120 that is running solaris 10 and now it will not boot. I tried power cycling it from the lom and pulling the cord but nothing works. All it does is after a power cycle it will start to boot and then start to spit out a bunch of hex characters spewing in a single line, like this non stop:

f00010034000001fff000b9e4000001fff000b9e8000000500000000000000015000001ff

Has anyone seen this before?
 

10 More Discussions You Might Find Interesting

1. Solaris

Help - Accessing Sun Fire V120 A/LOM

Hi All, My company has three V120 servers and two V245 servers. Currently we access ALOM on v245 thru NET MGT port. There are no NET MGT on V120. We use to access A/LOM on the V120s thru Windows Hyper Terminal connected to the Serial A port of v120. Since all of our Windows boxed are... (6 Replies)
Discussion started by: glieu
6 Replies

2. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

3. Solaris

Solaris 9 to Solaris 10 upgrade on Sun Fire 3800

Hello there! I have Sun Fire 3800 with very old Solaris 9 and I need to perform upgrade to concurrent Solaris 10 version, preserving current OS configuration. I supose to make it using Live Upgrade, but according to Solaris Live Upgrade Software: Minimum Patch Requirements page, I need to... (5 Replies)
Discussion started by: Sapfeer
5 Replies

4. Solaris

Sun Fire v120 memory compatibility

Hi, I recently acquired an old Sun Fire v120 from work. I plan to play around with this at home whilst I'm studying for my SCSA exams. Only problem is it currently has no memory installed. I believe the memory modules required are 168 pin PC133 DIMMs. Unfortunately, the original Sun modules are... (3 Replies)
Discussion started by: skinyana
3 Replies

5. Solaris

Running Sun Fire V480R on a single cpu-Urgent

I have a sun fire v480r server. it has 2 cpu. One of cpu have become faulty. Now i want to run server on a single cpu. My service provider says it cant be done, you have to replace the motherboard. Can it be done? If so do some settings need to be changed in solaris. I have search for documentation... (6 Replies)
Discussion started by: krabu
6 Replies

6. Solaris

Firmware password Solaris Sun Fire v440

Hi: I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies

7. Solaris

Removing a disk from SUN Fire V440 running Solaris 8

Hi, I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either. Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies

8. Solaris

Sun-Fire-V490 Printer Issue After Upgrade of Solaris

Hey Guys I am new here, dont know if any one can assist me with this issue. I have a Sun-Fire-V490 machine that was upgraded to version 9 and patched a few months back. Problem is a few network printers managed by the server is printing an extra page that comes out before and after every print... (0 Replies)
Discussion started by: mprogams
0 Replies

9. Solaris

Help with Solaris 8 10/00 Installation on Sun Fire V490 Server

cat note Hi Sun Solaris Experts, When I try to install Solaris 8 10/00 OS via the Solaris 8 Installation Disk on our Sun Fire V490 Server using the command , I get: boot: cannot open kernel/sparcv9/unix which means it can't find the unix kernel file on the installation disk . By the way, I... (5 Replies)
Discussion started by: ssabet
5 Replies

10. Solaris

Solaris 10 1/13 & Sun Fire V490 Server

Hi Solaris/Unix Experts, I've installed Oracle Solaris 10 1/13 on a Sun Fire V490 Server via its external Serial Port using a Cisco Console Cable connected to my Laptop PC running SecureCRT terminal emulation software emulating VT100 Terminal. The Sun Fire V490 server has two on-board... (1 Reply)
Discussion started by: ssabet
1 Replies
power(9E)							Driver Entry Points							 power(9E)

NAME
power - power a device attached to the system SYNOPSIS
#include <sys/ddi.h> #include <sys/sunddi.h> int prefixpower(dev_info_t *dip, int component, int level); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). This entry point is required. If the driver writer does not supply this entry point, the value NULL must be used in the cb_ops(9S) structure instead. PARAMETERS
dip Pointer to the device's dev_info structure. component Component of the driver to be managed. level Desired component power level. DESCRIPTION
The power(9E) function is the device-specific Power Management entry point. This function is called when the system wants the driver to set the power level of component to level. The level argument is the driver-defined power level to which the component needs to be set. Except for power level 0, which is interpreted by the framework to mean "powered off," the interpretation of level is entirely up to the driver. The component argument is the component of the device to be power-managed. The interpretation of component is entirely up to the driver. When a requested power transition would cause the device to lose state, the driver must save the state of the device in memory. When a requested power transition requires state to be restored, the driver must restore that state. If a requested power transition for one component requires another component to change power state before it can be completed, the driver must call pm_raise_power(9F) to get the other component changed, and the power(9E) entry point must support being re-entered. If the system requests an inappropriate power transition for the device (for example, a request to power down a device which has just become busy), then the power level should not be changed and power should return DDI_FAILURE. RETURN VALUES
The power() function returns: DDI_SUCCESS Successfully set the power to the requested level. DDI_FAILURE Failed to set the power to the requested level. CONTEXT
The power() function is called from user or kernel context only. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
attach(9E), detach(9E), pm_busy_component(9F), pm_idle_component(9F), pm_raise_power(9F), cb_ops(9S) Writing Device Drivers Using Power Management SunOS 5.11 12 Dec 2003 power(9E)
All times are GMT -4. The time now is 07:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy