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
EEPROM(8)						    BSD System Manager's Manual 						 EEPROM(8)

NAME
eeprom -- display or modify contents of the EEPROM or openprom SUN 3 SYNOPSIS eeprom [-] [-c] [-f device] [-i] [field[=value] ...] SPARC, SPARC64, MACPPC and PREP SYNOPSIS eeprom [-] [-c] [-f device] [-i] [-v] [field[=value] ...] DESCRIPTION
eeprom provides an interface for displaying and changing the contents of the EEPROM or openprom. The eeprom tool is only installed on sup- ported platforms. Without any arguments, eeprom will list all of the known fields and their corresponding values. When given the name of a specific field, eeprom will display that value or set it if the field name is followed by '=' and a value. Only the super-user may modify the contents of the EEPROM or openprom. The options are as follows: - Commands are taken from stdin and displayed on stdout. -c eeprom will fix incorrect checksum values and exit. This flag is quietly ignored on systems with an openprom. -f device On systems with an EEPROM, use device instead of the default /dev/eeprom. On systems with an openprom, use device instead of the default /dev/openprom. -i If checksum values are incorrect, eeprom will ignore them and continue after displaying a warning. This flag is quietly ignored on systems with an openprom. The following options are valid only on the SPARC and will produce an error when used on a Sun 3: -v On systems with an openprom, be verbose when setting a value. Systems with an EEPROM are always verbose. The -v option is also present on sparc64, macppc, and prep systems. FIELDS AND VALUES
The following fields and values are for systems with an EEPROM: hwupdate A valid date, such as ``7/12/95''. The strings ``today'' and ``now'' are also acceptable. memsize How much memory, in megabytes, is installed in the system. memtest How much memory, in megabytes, is to be tested upon power-up. scrsize The size of the screen. Acceptable values are ``1024x1024'', ``1152x900'', ``1600x1280'', and ``1440x1440''. watchdog_reboot If true, the system will reboot upon reset. Otherwise, the system will fall into the monitor. default_boot If true, the system will use the boot device stored in bootdev. bootdev Specifies the default boot device in the form cc(x,x,x), where 'cc' is a combination of two letters such as 'sd' or 'le' and each 'x' is a hexadecimal number between 0 and ff, less the prepending '0x'. kbdtype This value is ``0'' for all Sun keyboards. console Specifies the console type. Valid values are ``b&w'', ``ttya'', ``ttyb'', ``color'', and ``p4opt''. keyclick If true, the keys click annoyingly. diagdev This is a string very similar to that used by bootdev. It specifies the default boot device when the diagnostic switch is turned on. diagpath A 40-character, NULL-terminated string specifying the kernel or standalone program to load when the diagnostic switch is turned on. columns An 8-bit integer specifying the number of columns on the console. rows An 8-bit integer specifying the number of rows on the console. ttya_use_baud Use the baud rate stored in ttya_baud instead of the default 9600. ttya_baud A 16-bit integer specifying the baud rate to use on ttya. ttya_no_rtsdtr If true, disables RTS/DTR. ttyb_use_baud Similar to ttya_use_baud, but for ttyb. ttyb_baud Similar to ttya_baud, but for ttyb. ttyb_no_rtsdtr Similar to ttya_no_rtsdtr, but for ttyb. banner An 80-character, NULL-terminated string to use at power-up instead of the default Sun banner. Note that the secure, bad_login, and password fields are not currently supported. Since the openprom is designed such that the field names are arbitrary, explaining them here is dubious. Below are field names and values that one is likely to see on a system with an openprom. NOTE: this list may be incomplete or incorrect due to differences between revisions of the openprom. sunmon-compat? If true, the old EEPROM-style interface will be used while in the monitor, rather than the openprom-style interface. selftest-#megs A 32-bit integer specifying the number of megabytes of memory to test upon power-up. oem-logo A 64bitx64bit bitmap in Sun Iconedit format. To set the bitmap, give the pathname of the file containing the image. NOTE: this property is not yet supported. oem-logo? If true, enables the use of the bitmap stored in oem-logo rather than the default Sun logo. oem-banner A string to use at power up, rather than the default Sun banner. oem-banner? If true, enables the use of the banner stored in oem-banner rather than the default Sun banner. ttya-mode A string of five comma separated fields in the format ``9600,8,n,1,-''. The first field is the baud rate. The sec- ond field is the number of data bits. The third field is the parity; acceptable values for parity are 'n' (none), 'e' (even), 'o' (odd), 'm' (mark), and 's' (space). The fourth field is the number of stop bits. The fifth field is the 'handshake' field; acceptable values are '-' (none), 'h' (RTS/CTS), and 's' (Xon/Xoff). ttya-rts-dtr-off If true, the system will ignore RTS/DTR. ttya-ignore-cd If true, the system will ignore carrier detect. ttyb-mode Similar to ttya-mode, but for ttyb. ttyb-rts-dtr-off Similar to ttya-rts-dtr-off, but for ttyb. ttyb-ignore-cd Similar to ttya-ignore-cd, but for ttyb. sbus-probe-list Four digits in the format ``0123'' specifying which order to probe the sbus at power-up. It is unlikely that this value should ever be changed. screen-#columns An 8-bit integer specifying the number of columns on the console. screen-#rows An 8-bit integer specifying the number of rows on the console. auto-boot? If true, the system will boot automatically at power-up. watchdog-reboot? If true, the system will reboot upon reset. Otherwise, system will fall into the monitor. input-device One of the strings ``keyboard'', ``ttya'', or ``ttyb'' specifying the default console input device. output-device One of the strings ``screen'', ``ttya'', or ``ttyb'' specifying the default console output device. keyboard-click? If true, the keys click annoyingly. sd-targets A string in the format ``31204567'' describing the translation of physical to logical target. st-targets Similar to sd-targets, but for tapes. The default translation is ``45670123''. scsi-initiator-id The SCSI ID of the on-board SCSI controller. hardware-revision A 7-character string describing a date, such as ``25May95''. last-hardware-update Similar to hardware-revision, describing when the CPU was last updated. diag-switch? If true, the system will boot and run in diagnostic mode. FILES
/dev/eeprom The EEPROM device on systems with an EEPROM. /dev/openprom The openprom device on systems with an openprom. /dev/nvram The nvram device on PReP systems. SEE ALSO
ofctl(8) BUGS
The fields and their values are not necessarily well defined on systems with an openprom. Your mileage may vary. There are a few fields known to exist in some revisions of the EEPROM and/or openprom that are not yet supported. Most notable are those relating to password protection of the EEPROM or openprom. Avoid gratuitously changing the contents of the EEPROM. It has a limited number of write cycles. The date parser isn't very intelligent. BSD
February 27, 2007 BSD
All times are GMT -4. The time now is 07:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy