11-13-2008
Hi
I have tried ilom.X4500-1.1.8.ima and ilom.X4500-2.0.2.5-r37042_42606a.ima as well. But nothing worked. Actually I am accessing it using cli and from a remote computer with root privileges. I did not try serial connection to SP.
I will try to work on it. But if you can please let me know what might be the problem with cli.
Thank you
8 More Discussions You Might Find Interesting
1. Solaris
I have solaris X4500 with ILOM version 1.1.1. I want to update the firmware. I know that we need to use
load -source tftp://tftpserver/image file
But I do not understand what is the IP address of the tftp server that we need to type in there.
Kindly, help me with this.
Thank you (5 Replies)
Discussion started by: bharu_sri
5 Replies
2. Solaris
I have X4500 machine with solaris 10 OS and software version 5.10. The firmware version is 1.1.1 and I am planning to upgrade the firmware.
C H A P T E R 1 - Flash Upgrading Your Server to Software Release 1.2
I referred to the above link to do so. But, I do not understand what is the... (6 Replies)
Discussion started by: bharu_sri
6 Replies
3. Solaris
when I type start /SP/console... the console shows up but i cannot type anything over there. I do not understand what might be the reason for that.
-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y
Serial console started. To stop, type ESC (
I pressed enter many... (8 Replies)
Discussion started by: bharu_sri
8 Replies
4. Solaris
I have X4500 running solaris 10 with 5.10 version. The ILOM version is 1.1.1 and I want to upgrade the firmware. I setup the TFTP server on my machine using the following link.
A P P E N D I X C - Updating the Firmware
I could install the tftp server and could transfer a file as well. When I... (1 Reply)
Discussion started by: bharu_sri
1 Replies
5. Solaris
Hi guys I have a Sun Fire X4500 running Solaris 10 OS. It has 48 TB Hard Disk. I need to format it and make 3 partitions. Could someone give me a link or help me with this.
Thank you (1 Reply)
Discussion started by: bharu_sri
1 Replies
6. AIX
this error is appear in my server . please can anyone help me with it .
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
BFE4C025 0323100711 P H sysplanar0 UNDETERMINED ERROR
BFE4C025 0323100611 P H sysplanar0 UNDETERMINED ERROR
BFE4C025 0323090711 P H sysplanar0 ... (4 Replies)
Discussion started by: thecobra151
4 Replies
7. SuSE
Hi all
We've had an issue over the weekend when one of the SUSE Linux Enterprise Server 11 hung and had to be rebooted. The thing is that I got the ticket alert for a FS exceeding its usage at about 22:41:49 PM on 23 March. I checked the dmesg, the messages log and the boot.msg but all I found... (1 Reply)
Discussion started by: hedkandi
1 Replies
8. Solaris
hi every one , i am facing a problem and i am stuck i need you help :
i am trying to upgrade apache 2.0.63 to apache 2.0.64 with ssl option enabled when i try to compile by using make command i face the below error :
ssl_engine_init.c: In function `ssl_init_ctx_protocol':
... (3 Replies)
Discussion started by: core99
3 Replies
LEARN ABOUT NETBSD
firmware_close
FIRMLOAD(9) BSD Kernel Developer's Manual FIRMLOAD(9)
NAME
firmload -- Firmware loader API for device drivers
SYNOPSIS
#include <dev/firmload.h>
int
firmware_open(const char *drvname, const char *imgname, firmware_handle_t *fhp);
int
firmware_close(firmware_handle_t fh);
off_t
firmware_get_size(firmware_handle_t fh);
int
firmware_read(firmware_handle_t fh, off_t offset, void *buf, size_t size);
void *
firmware_malloc(size_t size);
void
firmware_free(void *buf, size_t size);
DESCRIPTION
firmload provides a simple and convenient API for device drivers to load firmware images from files residing in the file system that are nec-
essary for the devices that they control. Firmware images reside in sub-directories, one for each driver, of a series of colon-separated
path prefixes specified by the sysctl variable hw.firmware.path.
FUNCTIONS
The following functions are provided by the firmload API:
firmware_open(drvname, imgname, fhp)
Open then firmware image imgname for the driver drvname. The path to the firmware image file is constructed by appending the string
``/drvname/imgname'' to each configured path prefix until opening the firmware image file succeeds. Upon success, firmware_open()
returns 0 and stores a firmware image handle in the location pointed to by fhp. Otherwise, an error code is returned to indicate the
reason for failure.
firmware_close(fh)
Close the firmware image file associated with the firmware handle fh. Returns 0 upon success or an error code to indicate the reason
for failure.
firmware_get_size(fh)
Returns the size of the image file associated with the firmware handle fh.
firmware_read(fh, offset, buf, size)
Reads from the image file associated with the firmware handle fh beginning at offset offset for length size. The firmware image data
is placed into the buffer specified by buf. Returns 0 upon success or an error code to indicate the reason for failure.
firmware_malloc(size)
Allocates a region of wired kernel memory of size size. Note: firmware_malloc() may block.
firmware_free(buf, size)
Frees a region of memory previously allocated by firmware_malloc().
SEE ALSO
autoconf(9), malloc(9), vnsubr(9)
HISTORY
The firmload framework first appeared in NetBSD 4.0.
AUTHORS
Jason Thorpe <thorpej@NetBSD.org>
BSD
January 17, 2006 BSD