Sponsored Content
Operating Systems Solaris console -f not working in ALOM Post 302238363 by Perderabo on Friday 19th of September 2008 05:16:43 PM
Old 09-19-2008
I think it will switch over automatically like that, but I would become root and do:

eeprom output-device=ttya
eeprom input-device=ttya
init 5

Now disconnect keyboard at least.
Power on.
 

10 More Discussions You Might Find Interesting

1. Solaris

Creating SNMP Strings To Trap ALOM Console Messages

Greetings To All! I am trying to accomplish the following: Using a public SNMP string, create a trap which will trap ALOM console messages on a Solaris Sunfire T-1000 ALOM console. The platform is Solaris 10. These newly created traps need to be configured in such a way that they will send... (0 Replies)
Discussion started by: RobSand
0 Replies

2. Solaris

how to go to system console through ALOM in Sunfire V245

Hello , I am connecting sumfire v245 server to my laptop Through ALOM method.i got the ALOM prompt but after that i am typing sc> console to go to system console but i am not able to,after typing console only this line is coming Type #. to go back to ALOM. What to do ?? That server having... (5 Replies)
Discussion started by: avi157
5 Replies

3. UNIX for Advanced & Expert Users

console /dev/console get image

We are using software (Pegasys) which runs on SunOS 5.8 and reads images from a Philips nuclear camera. The software is designed to run from the console. I need to be able to capture the images it produces on the display. The caveat is that I cannot use the X Windows display because the X Server... (3 Replies)
Discussion started by: sreyes27
3 Replies

4. UNIX for Dummies Questions & Answers

Windows to Linux remote console using VNC brings up blank console screen with only mouse pointer

:confused:Hi This was installed on the Linux box a few weeks back by a guy that no longer works for us. All worked fine until last week. Now when we connect its just a blank screen with no icons. I get a whole bunch of errors when starting the service too: Tue Feb 23 14:29:45 2010 ... (1 Reply)
Discussion started by: wbdevilliers
1 Replies

5. Solaris

Reset ALOM from OS

Hi guys, I'm in trouble with a Sunfire T2000. The OS (Solaris10) is up and running, but I can't log in the sc>I think the terminal server is crashed! Does anyone know if I can reset the sc> from the OS? How can I do that? Thx (6 Replies)
Discussion started by: cecco16
6 Replies

6. Solaris

Difference b/n ALOM and ALOM CMT

Hi Everyone. What is the differece b/n ALOM and ALOM CMT Service processor. I am trying reset ALOM login/passwd using scadm utility on T2000, while I am googling I came cross ALOM CMT doesnt support scadm utility, but ALOM supports. Not sure how different are these. Thanks, (0 Replies)
Discussion started by: bobby320
0 Replies

7. Solaris

ALOM - Console -

Hello forum, I have a SUN v250 at home that I have to practice Solaris. I currently have Solaris 9 installed and the ALOM Sun(tm) Advanced Lights Out Manager 1.5.2. From the ALOM I want to access the console. sc> console -f Enter #. to return to ALOM. after that there is no response.... (19 Replies)
Discussion started by: br1an
19 Replies

8. Solaris

Alom

Hi, How to set ip address on eth0 for access ssh from ALOM? Is it possible? Now i cannot access it because don't have VGA. I keep try to access using ssh. Please guide me. Thanks. (16 Replies)
Discussion started by: mzainal
16 Replies

9. Red Hat

RHEL 7: Backup Space and Delete is not working in console

Hi All, During my virtual machine power on i have rc3.d script to accept user inputs like IP address. This script gets executed during first time boot up. It was working fine till my VM is using RHEL6.5. Now we migrated to RHEL 7 environment. While accepting the user inputs in console, I... (4 Replies)
Discussion started by: kalpeer
4 Replies

10. Hardware

Alom ?

Hi all, I have some problems with the fan FT0.F0, which looks like has a problem with the PROM/ALOM ( I am nor sure who).....but, in fact, the fan is working properly even in other V440 Sparc Server. We checked HW comunication between Fan and the MotherBoard, and we think is a problem of... (8 Replies)
Discussion started by: proof_enrique
8 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 12:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy