Configure Power Settings on Boot Post: 302820773

Sponsored Content

Operating Systems Solaris Configure Power Settings on Boot Post 302820773 by Wrongway on Thursday 13th of June 2013 12:14:19 PM

06-13-2013

Registered User

Configure Power Settings on Boot

Hi all, this is my first question on this forum, so if it isn't in the correct location, please let me know where to post.

We are using Solaris 8 and with the power setting enabled the monitor will not wake up. It can take anywhere from 5 to 30 minutes for the monitor to display.

One of the individuals here thinks that the machine needs to have the configuration reset and then reconfigure to disable. I thought this was kind of extreme and since it has been over 20 years since I worked on UNIX and have never really done much with Solaris, I wasn't comfortable doing this.

After doing some research, I noticed that the power settings for the display are enabled, when I disable them the monitor responds better. But, after a while it goes back to the original settings. Especially when rebooting.

I contacted a collage colleague who has worked on Solaris for most of her career. She talked to someone that she works with who was having the same problem some time ago. He suggested using the following commands:

Code:

xset -dpms
xset s 0 0

When I enter these commands in the term window the monitor works fine and never goes to sleep. We turn off the monitor by hand. The problem comes in when we reboot the system; the commands need to be manually re-entered.

So, the question is what script(s) needs to be modified with these commands so they are executed on startup? A link to where this could be done will help greatly.

Thanks
Larry

Wrongway

View Public Profile for Wrongway

Find all posts by Wrongway

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

boot fails after power faliure

Hi, i was installing solaris 8 on sunfire v250 and the power fails :mad: , now it does not boot from cd rom and get the next msg: � Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard OpenBoot 4.0, 512 MB memory installed, Serial #56338483. Ethernet address 0:3:ba:5b:a8:33, Host ID: 835ba833. ...

2. AIX

AIX does not boot after power on

We have a RS6000, model B50, type 7046, where I installed AIX 4.3.3 But, if the power goes off, the operating system does not restart, and I have to go there and push the button to start AIX again. Is there any way this procedure to be avoided, this is, I want the AIX to start automatically...

3. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and...

4. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless.

5. AIX

IBM Power Pseries Open Firmware boot / VIOS POWERVM VET CODE

Hello, I installed PowerVM IVM Virtual I/O on P-550 but later found out that the machine isn't activated for CoD VET code for virtualization. So when booted , it goes into OPEN Firmware I/O Hosting requires a hosting partition boot not permitted exit called > ok Panel shows > IO...

6. Cybersecurity

TrustedGrub Configure and boot

Is TrustedGrub can be setup and boot on Grub2? I am actually trying to setup TrustedGrub-1.1.5 on fedora-16. How it can be done?

7. AIX

System can't boot up after power outage

Hello Forum, I am very newbie with AIX. We have 2 AIX 9111-285 servers. The OS version is 5.3. After the power outage, they did not come up. I try to unplug the power cable and re-connect after 1 minutes but do not help. Both display the same reference code 110000AC on the front panel...

8. AIX

IBM Power 740 won't boot after firmware update

A team member installed the wrong version of License Code on a Power 740 system used in our Development environment. The system will no longer boot. Does anyone have IBM documentation or experience to share on recovering a system that currently reports "Unsupported License Code version...

LEARN ABOUT OPENSOLARIS

root_archive

root_archive(1M)					  System Administration Commands					  root_archive(1M)

NAME

       root_archive - manage bootable miniroot archives

SYNOPSIS

       /boot/solaris/bin/root_archive  pack archive root

       /boot/solaris/bin/root_archive  unpack archive root

       /boot/solaris/bin/root_archive  packmedia solaris_image root

       /boot/solaris/bin/root_archive  unpackmedia solaris_image root

DESCRIPTION

       The  root_archive  utility  is  used to manage bootable miniroot archives and is currently only available on x86 platforms. The utility can
       pack and unpack boot/root archives in both ufs and hsfs (iso9660) format. It will always generate ufs archives.

       root_archive also uses the lofi file driver to export a file as a block device (see lofi(7D)) and mount to mount or  unmount  file  systems
       and remote resources (see mount(1M)). root_archive requires the same privileges that are needed to run these commands.

SUBCOMMANDS

       The root_archive command has the following subcommands:

       pack archive root    Pack from the image found under the root directory to the archive.

       unpack archive root

	   Unpack from the archive to an unpacked image under the root directory.

       packmedia solaris_image root

	   Pack the solaris image to the root directory.

       unpackmedia solaris_image root

	   Unpack the solaris image from the root directory.

       For  packmedia  and  unpackmedia,  other items that do not go into the ramdisk image are copied or uncopied (see cpio(1)) as well. Specifi-
       cally, this includes all the packaging databases needed for pkgadd and the other packaging utilities to succeed which are not used  in  the
       running and hence pruned to conserve memory.

EXAMPLES

       Example 1 Unpacking the Solaris x86 install image

       The following command unpacks the current Solaris image from the root directory:

	 # root_archive unpackmedia 
	 /export/nv/solarisdvd.nvx_dvd/latest /export/Boot

       Where  /export/nv/solarisdvd.nvx_dvd/latest  represents	a path to a Solaris x86 install image and /export/Boot is a directory that will be
       purged or created, as necessary.

       Example 2 Packing the Solaris x86 install image

       The following command packs the current Solaris image to the root directory:

	 # root_archive packmedia 
	 /export/nv/solarisdvd.nvx_dvd/latest /export/Boot

EXIT STATUS

       The following exit values are returned:

       0    The command completed successfully.

       1    The command exited due to an error.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Stable			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       cpio(1), bootadm(1M), mount(1M), attributes(5), lofi(7D)

SunOS 5.11							    26 Sep 2005 						  root_archive(1M)