Sponsored Content
Operating Systems Solaris Firmware password Solaris Sun Fire v440 Post 302536851 by beta17 on Wednesday 6th of July 2011 11:10:10 AM
Old 07-06-2011
hmm the password is stored in the NVRAM (eeprom)
don't know if there is a way to reset them (or just replace the eeprom)
 

10 More Discussions You Might Find Interesting

1. Solaris

Sun Fire V440 and Patch 109147-39

Got an curious issue. I applied 109147-39 to, oh 15 or so various systems all running Jumpstarted Solaris 8. When I hit the first two V440s, they both failed with Return code 139. All non shell commands segfaulted from then on. The patch modified mainly the linker libraries and commands. ... (2 Replies)
Discussion started by: BOFH
2 Replies

2. Solaris

Sun Fire v440 keeps shutting down

Hello, I hope you can help me. I am new to Sun servers and we have a Sun Fire v440 server in which one power supply failed, we are waiting for new one. But now our server is shutting down constantly. Is there any setting with which we can prevent this behaviour? (1 Reply)
Discussion started by: Tibor
1 Replies

3. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

4. Solaris

Sun Fire v440 hardware problem (can't get ok>)

First of all it's shut down 60 second after power on and write on console : SC Alert: Correct SCC not replaced - shutting managed system down! This is cured by moving out battery from ALOM card. Now server start to loop during the testing. That's on the console: >@(#) Sun Fire V440,Netra... (14 Replies)
Discussion started by: Alisher
14 Replies

5. Solaris

error messages in Sun Fire V440

Hello, I am seeing error messages in V440 (OS = solaris 8). I have copied here : The system does not reboot constantly and it is up for last 67 days. One more interesting thing I found, I see errors start appearing at 4:52AM last until 6am and again start at 16:52am on same day.. I... (5 Replies)
Discussion started by: upengan78
5 Replies

6. Solaris

ALOM wont work when KVM connected to Sun Fire V440 server

Hi, I was asked to connect a KVM screen to a Sun Fire V440 last night so I connected it up but no joy and nothing on the KVM screen. I was told that a reboot may fix the problem so connected to the ALOM and rebooted. On the plus side, the KVM screen now works but I lost the ALOM connection. ... (0 Replies)
Discussion started by: jimmy54321
0 Replies

7. Solaris

Sun Fire v440 Over heat Problem.

Dear Team, I need some expert advice to my problem. We have a Sun Fire v440 in our customer Place. Server is working fine and no hardware deviations are found except one problem that processors generating too much heat. I have verified and found that the room temperature was 26-27 degree.... (5 Replies)
Discussion started by: sudhansu
5 Replies

8. Solaris

Sun-Fire V440 boot disk issue

Hi, I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

9. Solaris

Removing a disk from SUN Fire V440 running Solaris 8

Hi, I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either. Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies

10. Solaris

Sun Fire v440 Hard disk or controller broken? WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1)

Hi, I have a Sun Fire V440 server that fails to boot up correctly. A lot of services are not started and the sytems acts really slow to commands. During boot I can see the following Error: WARNING: /pci@1f,700000/scsi@2/sd@0,0 (sd1): SCSI transport failed: reason 'reset': retrying... (15 Replies)
Discussion started by: oliwei
15 Replies
FTDI-EEPROM(1)						      General Commands Manual						    FTDI-EEPROM(1)

NAME
ftdi_eeprom - Tool for reading/erasing/flashing FTDI USB chip eeproms SYNOPSIS
ftdi_eeprom [commands] config-file DESCRIPTION
ftdi_eeprom is a small tool for reading/erasing/flashing FTDI USB chip eeproms. It uses libftdi to access the chip, so you will need to have the required permissions on the device. The ftdi_sio module should not be loaded. You can prevent it to be automatically loaded by adding it to /etc/modprobe.d/blacklist. You have to unplug and replug your device to get the new values to be read. Otherwise, you will still get the old values. COMMANDS
--read-eeprom Read eeprom and write to -filename- from config-file. --erase-eeprom Erase eeprom. --flash-eeprom Flash eeprom. CONFIGURATION FILE
The configuration file contains a list of key-value pairs which will be used to flash an FTDI USB chip eeprom. Comments start with #. The beginning of such a file might look like the following: vendor_id=0x0403 # Vendor ID product_id=0x6001 # Product ID max_power=0 # Max. power consumption: value * 2 mA. Use 0 if self_powered = true. ########### # Strings # ########### manufacturer="ACME Inc" # Manufacturer product="USB Serial Converter" # Product serial="08-15" # Serial The example configuration file that could be found in /usr/share/doc/ftdi-eeprom/examples is quite well commented so you should be able to use it as a basis. The following keys are supported: vendor_id Set the vendor ID of the device. This value could be entered in decimal or hexadecimal form, and should be in the range 0-65535 or 0x0000-0xffff, respectively. product_id Set the product ID of the device. This value could be entered in decimal or hexadecimal form, and should be in the range 0-65535 or 0x0000-0xffff, respectively. max_power Set the maximum current the device will use, in 2 mA unit. Use 0 if self_powered = true. manufacturer Set the manufacturer string which normally holds the name of the manufacturer. product Set the product string which normally holds the name of the product. serial Set the serial string which normally holds the serial number of the product. self_powered Specify if the device is self-powered or not. The value should be true or false. remote_wakeup Specify if the device supports remote wake-ups. The value should be true or false. use_serial If this value is set to true, the serial string will be used. Otherwise the default serial string will be used. BM_type_chip This value have to be set to true if you are using a BM chip. in_is_isochronous If set to true this option specify that the input endpoint is in isochronous mode. out_is_isochronous If set to true this option specify that the output endpoint is in isochronous mode. suspend_pull_downs If this value is set to true the pull downs are enabled during suspend for lower power consumption. change_usb_version This value has to be set to true if you want to force the USB version using the usb_version key. Otherwise the default USB version will be used. usb_version Set the USB version of the device. The change_usb_version value has to be set to true. filename Specify a filename if you want to dump the content of the eeprom into it. AUTHOR
ftdi_eeprom was written by Intra2net AG <opensource@intra2net.com>. This manual page was written by Aurelien Jarno <aurel32@debian.org> for the Debian GNU/Linux system (but may be used by others). March 31, 2004 FTDI-EEPROM(1)
All times are GMT -4. The time now is 10:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy