Sponsored Content
Operating Systems Solaris OpenBoot Firmware Password Recovery Post 302395109 by adelsin on Monday 15th of February 2010 03:27:36 AM
Old 02-15-2010
Solution

Thanks again for the quick responses.

Here's what worked for me and I don't know why I didn't think of this sooner.

I had two V210's, 1 firmware, 1 not. Basically, I just removed the drives from the one that had firmware and stuck them into the Open one.
Did the precedure to get in the harddrive via root.

I then put the harddrives back and proceeded with the

"
eeprom security-mode=none
"

Thanks you and I look forward to being a proud member of this forum.
Tad Kammeyer
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Password recovery

We recently terminated a developer at my place of employment who created scripts on a windows server (that i do not have access to) that invoke FTP sessions on my UnixWare 7.1.1 servers. I need to know the password that is being used. Does anyone know of a good password crack? (8 Replies)
Discussion started by: rm -r *
8 Replies

2. Shell Programming and Scripting

help for db password recovery

hi,all my database (.db) is created by sysbase adaptive server anywhere7.0 ! the user id is DBA. but I lost the password . Could you recovery the passwrod of this db file? thanks ! iwind (1 Reply)
Discussion started by: northwind
1 Replies

3. UNIX for Dummies Questions & Answers

Password Recovery

Hi, I am new to unix and I set a password for a user and now I need to recover what that password was. Is there a way, where as root, I can view what a users passwords is? Thanks, Eric (2 Replies)
Discussion started by: ejbrever
2 Replies

4. Forum Support Area for Unregistered Users & Account Problems

password recovery

hello, my password got lost - and your service to generate new passwords does not work -ive tried it out 50 times the last week or so, never got a single mail from it... please generate a new password for my account "congo" with mailadress. thanks. Thomas (3 Replies)
Discussion started by: congo00000001
3 Replies

5. Solaris

Firmware password

Hi: I have a Sun Blade 1500 and when I do the Jumpstart with command "boot net - install" asking for the password of the firmware and I was not that password. There any way to reset this password. Thank you very much (7 Replies)
Discussion started by: ea1fch
7 Replies

6. Cybersecurity

password recovery

I am trying to access an old email account but cannot recall the password and the backup email account has been closed, also. I need instructions or an expert who can assist recovering my password for web-based email account. (4 Replies)
Discussion started by: pp_mcgee
4 Replies

7. Cybersecurity

Password Recovery

Perderabo has made posted a good thread in the FAQ section here: Lost root password / Can't login as root | Unix Linux Forums | Answers to Frequently Asked Questions (6 Replies)
Discussion started by: norsk hedensk
6 Replies

8. 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

9. AIX

Password for Firmware woes!

Hi All, On wanting to re-install AIX 6.1 on to an RS 6000 Power 9111 285 station, I've tried to get in to SMS and also to boot from the DVD drive, but now the Firmware is locked and asking for the password. I originally set the password about 6 years ago and have forgotten it because I've never... (14 Replies)
Discussion started by: Box_the_Jack_in
14 Replies
obpsym(1M)						  System Administration Commands						obpsym(1M)

NAME
obpsym - Kernel Symbolic Debugging for OpenBoot Firmware SYNOPSIS
modload -p misc/obpsym DESCRIPTION
obpsym is a kernel module that installs OpenBoot callback handlers that provide kernel symbol information to OpenBoot. OpenBoot firmware user interface commands use the callbacks to convert numeric addresses to kernel symbol names for display purposes, and to convert kernel symbol names to numeric literals allowing symbolic names to be used as input arguments to user interface commands. Once obpsym is installed, kernel symbolic names may be used anywhere at the OpenBoot firmware's user interface command prompt in place of a literal (numeric) string. For example, if obpsym is installed, the OpenBoot firmware commands ctrace and dis typically display symbolic names and offsets in the form modname:symbolname + offset. User interface Commands such as dis can be given a kernel symbolic name such as ufs:ufs_mount instead of a numeric address. Placing the command forceload: misc/obpsym into the system(4) file forces the kernel module misc/obpsym to be loaded and activates the kernel callbacks during the kernel startup sequence. obpsym may be useful as a kernel debugger in situations where other kernel debuggers are not useful. For example, on SPARC machines, if obpsym is loaded, you may be able to use the OpenBoot firmware's ctrace command to display symbolic names in the stack backtrace after a watchdog reset. Kernel Symbolic Name Syntax The syntax for a kernel symbolic name is: [ module-name : ] symbol-name Where module-name is the name of the kernel module that the symbol symbol-name appears in. A NULL module name is taken as "all modules, in no particular order" by obpsym. The module name unix is equivalent to a NULL module name, so that conflicts with words defined in the firmware's vocabulary can be avoided. Typically, OpenBoot firmware reads a word from the input stream and looks the word up in its internal vocabulary before checking if the word is a literal. Thus, kernel symbols, such as reset may be given as unix:reset to avoid the unexpected side effect of the firmware find- ing and executing a matching word in its vocabulary. FILES
/etc/system system configuration information file /platform/platform-name/kernel/misc/obpsym ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcar | +-----------------------------+-----------------------------+ SEE ALSO
kadb(1M), kernel(1M), modload(1M), modunload(1M), uname(1), system(4), attributes(5) OpenBoot 2.x Command Reference Manual WARNINGS
Some OpenBoot firmware user interface commands may use system resources incompatibly with the way they are used by the Unix kernel. These commands and the use of this feature as a kernel debugger may cause interactions that the Unix kernel is not prepared to deal with. If this occurs, the Unix kernel and/or the OpenBoot firmware user interface commands may react unpredictably and may panic the system, or may hang or may cause other unpredictable results. For these reasons, the use of this feature is only minimally supported and recommended to be used only as a kernel debugger of "last resort". If a breakpoint or watchpoint is triggered while the console frame buffer is powered off, the system can crash and be left in a state from which it is difficult to recover. If one of these is triggered while the monitor is powered off, you will not be able to see the debugger output. NOTES
platform-name can be found using the -i option of uname(1) obpsym is supported only on architectures that support OpenBoot firmware. On some systems, OpenBoot must be completely RAM resident so the obpsym symbol callback support can be added to the firmware, if the firmware doesn't include support for the symbol callbacks. On these systems, obpsym may complain that it requires that "you must use ram- forth to use this module". See the OpenBoot 2.x Command Reference Manual for details on how to use the ramforth command, how to place the command into nvramrc, and how to set use-nvramrc? to true. On systems with version 1.x OpenBoot firmware, nvramrc doesn't exist, and the ramforth command must be typed manually after each reset, in order to use this module. Once installed, the symbol table callbacks can be disabled by using the following OpenBoot firmware command: 0 0 set-symbol-lookup SunOS 5.10 13 Dec 2001 obpsym(1M)
All times are GMT -4. The time now is 04:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy