Sponsored Content
Full Discussion: Screen blank on boot up
Operating Systems Solaris Screen blank on boot up Post 302569378 by sonic72 on Monday 31st of October 2011 05:31:46 AM
Old 10-31-2011
In the end I set the eeprom parameters to output-device=screen and input-device=keyboard and that did the trick.

Not sure how they'd been set to ttya but they may well have always been like that. It's not a server we reboot very often!

Thanks
Paul
 

10 More Discussions You Might Find Interesting

1. HP-UX

Data protector GUI gives Blank screen

Hi, Haveing a little trouble with data protector (5.5) on HP-UX (11.11, 11.23) under Xwindows Chameleon UNIX 97 (7.0 - its a old version) I am trying to get the GUI for DP up and running on a HP-UX cell manager and I have the following problem. The GUI starts up with no errors that I can... (2 Replies)
Discussion started by: Andrek
2 Replies

2. Solaris

Blank GRUB Screen

Hello. I had installed solaris 10 in morning , and all was running fine... I just logged out and logged in with another user ID oracle - It got stuck and then I pressed the button for restart. Now I see only word GRUB written in top line rest everything is black. What to do? (2 Replies)
Discussion started by: panchpan
2 Replies

3. Solaris

Solaris box shows blank screen after power up

Hi All, I have a solaris machine that powers up and displays a blank screen? All the keyboard, monitor and mouse are plugged in. It was booting fine before and when it was disconnected and re-connected (mouse/keyboard/monitor) it just powered on and came up with a blank screen. Please... (5 Replies)
Discussion started by: tlee
5 Replies

4. Solaris

Blank screen on crt

Hello I'm new in sun and i have a liitle problem. I buy sun enterprise 420r and connect keyboard and monitor crt (non Sun). But when i start server i have blank screen on crt. I'm new in sun servers and i dont know why its doin this. (11 Replies)
Discussion started by: elmik
11 Replies

5. Shell Programming and Scripting

Bash script [Press Tab] Screen Blank..

Dear Member, OLD Question --> disable-completion not solved My bash Menu script ping process problem. If ping still running and users press SCREEN is Blank... Cant Members help me.. kill signal or others scripting for my case, btw i use Linux.. Thanks, Rico My Bash Script : ... (1 Reply)
Discussion started by: carnegiex
1 Replies

6. AIX

xp to aix - telnet blank screen

hello, i am trying to test connection to a 5.3 box. from an xp machine, telnet connects but shows only a blank screen. cursor moves as i type, but no response back. have used telnet, putty and accuterm - all same result verified that telnet services are active in xp xp windoze firewall is... (10 Replies)
Discussion started by: allenhibbert
10 Replies

7. Ubuntu

Blank screen after upgrade from 11.10 to 12.04!

Hello, I got blank screen when reboot after I tried to upgrade Ubuntu (64 bit server version) from 11.10 to 12.04 at update manager. The normal login GUI is missing, but mouse cursor is fine. Then I switched to terminal (tty1 ~ tty6), which looked fine and showed it is Ubuntu 12.04 ! (Forgot how... (4 Replies)
Discussion started by: yifangt
4 Replies

8. Ubuntu

Blank Screen after logoff server via vnc Viewer.

Hello All, I have installed VNC Server on Ubuntu system to access this system from windows machine i'm using VNC Viewer. When i logged off the server from windows machine through VNC Viewer its showing blank screen only... Kindly help. Regards, Purushottam Aher (0 Replies)
Discussion started by: purushottamaher
0 Replies

9. Solaris

System reboot shows blank screen

we are using sun solaris sunfire v445, yesterday improperly shutdown the server and now while restart the system show a screen which is blank and the hard disc drive indicator light is also not glowing. (10 Replies)
Discussion started by: mrdb
10 Replies

10. HP-UX

Get blank screen when killing a UNIX session on HP-UX

Hi, I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen? Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second... (5 Replies)
Discussion started by: rm-r
5 Replies
dxpause(1X)															       dxpause(1X)

NAME
dxpause - locks (pauses) an X display SYNOPSIS
dxpause [-autopause] [-time n] [-wait] OPTIONS
If the -autopause option is set, when the display is unlocked, dxpause does not exit but instead becomes an icon. In this case, dxpause automatically locks the display when the X server goes into screensaver mode if the X Screensaver extension is present in the X server. De-iconifying dxpause also causes the display to be locked. The -time option only has meaning if the -autopause option is also set. The -time n option sets the autolock timeout period to n minutes. The default period is whatever the X server's screensaver timeout is set to, and the latter defaults to 5 minutes. The -wait option only has meaning if the -autopause option is also set, and causes dxpause to start in the iconified state rather than immediately locking the display. Without any of these options set, dxpause locks the display immediately when invoked and exits when the display is unlocked. DESCRIPTION
The dxpause program must be invoked explicitly by users (typically those running the generic X display manager rather than CDE). The dxpause program places a blank screen over the workstation screen and displays a dialog box that prompts for the password of the person whose session was paused. When you enter the correct password, the blank screen is removed and the session resumes. In the file, the following resources are used by the dxpause program: The first name for lines that apply only to the Pause task should be labeled DXpause. When this resource is True, dxpause executes an XGrabServer library call, thereby inhibiting all processing of requests or close downs on any other connection. Although this action absolutely insures that no information is displayed "through" the pause screen, it also effectively suspends other tasks that need to output information to their windows. When this resource is False, the pro- tective pause screen is raised to the top of the display stack 20 times per second, thus re-covering any other window that might have been displayed. Tasks that need to output to their own windows will not be suspended. The default is False. When this resource is True, dxpause behaves as if it were run with the -autopause option. See the OPTIONS section, above. The default is False. When this resource is set to a numeric value n, dxpause behaves as if it were run with the -time n option. See the OPTIONS section, above. This resource only has meaning if the autoPause resource is set, or if dxpause is started with the -autopause option. The value n defaults to whatever the X server's screensaver timeout is set to, and the latter defaults to 5 minutes. When this resource is True, dxpause behaves as if it were run with the -wait option. See the OPTIONS section, above. This resource only has meaning if the autoPause resource is set, or if dxpause is started with the -autopause option. The default is False. FILES
SEE ALSO
X(1X) dxpause(1X)
All times are GMT -4. The time now is 03:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy