Sponsored Content
Operating Systems AIX Power8 S812L:HMC issue and ... Post 302962011 by MichaelFelt on Monday 7th of December 2015 11:26:11 AM
Old 12-07-2015
Try a different version of Redhat - 6.X level. From a faint discussion some time back, I recall RedHat 7.X requires a higher level of POWER firmware than some early systems came with.

As you said you got it from ebay - your's might be a system with early firmware.

And my experience with RedHat is that they are quite particular about the machine. As you are just getting started try a net-boot image (if you have direct access then the image to burn is quite small). If you need/want a full image of 'something' - again, a RH 6.X, or SLES, or Ubuntu.

I do not have access to POWER8 - so I can only suggest, not pre-test.

Hope this helps!

Michael
This User Gave Thanks to MichaelFelt For This Post:
 

10 More Discussions You Might Find Interesting

1. AIX

Hmc

Well i am right now working on an IBM P550 risc server with an HMC connected.. The server has 2 logical partitions (Lpar). both lpar is having Aix 5.3 installed. Now I have a doubt.. is it possible to have Aix in one lpar and windows 2003 in another.. cheers Bala (4 Replies)
Discussion started by: balaji_prk
4 Replies

2. AIX

Hmc

Hello everybody, had a question. Iam having a p650 box here, System Model: IBM,7038-6M2 Machine Serial Number: 1078DCC managed system - 1 which has 2 lpars on it i added memory to the box(made sure that memory added was in proper quads and was verified by a CE) after i rebooted the box, the... (4 Replies)
Discussion started by: karthikosu
4 Replies

3. AIX

CDROM Issue on LPAR HMC VIO

Whenever I assign/unassign a CDROM ( RAID CTRL ) to Active LPAR from HMC, I have to reboot the LPAR. How can I do it without rebooting the LPARS. POWER6 with HMC LPARS = AIX 6.1 Any info developerWorks : AIX and UNIX : PowerVM Forum : Moving CD-ROM/DVD-ROM dynamically ... But... (5 Replies)
Discussion started by: filosophizer
5 Replies

4. AIX

AIX and HMC installation issue

I started the AIX install with a fiber channel disk, and let it run: restricted by GSA ADP Schedule Contract with IBM Corp. . . . . . << End of copyright notice for perfagent.tools >>. . . . ... (2 Replies)
Discussion started by: Gideon1a
2 Replies

5. AIX

HMC Commands

Hello All, Can anybody knows a command, what I can check the processes in the HMC restricted shell? :wall: (1 Reply)
Discussion started by: kalaso
1 Replies

6. AIX

[TIP] Migration to POWER8

Read "Migration to POWER8" article to get prepared for migration to POWER8: link removed, advertisement (0 Replies)
Discussion started by: pave01
0 Replies

7. AIX

New IBM Power8 (S822) and StorWiz V3700 SAN, best practices for production setup/config?

Hello, Got a IBM Power8 box (S822) that I am configuring for replacement of our existing IBM machine. Wanted to touch base with the expert community here to ensure I don't miss anything critical in my setup/config of AIX. Did a fresh AIX 7.1 install on the internal scsi hdisk, mirror'ed... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

8. AIX

StorWize v3700 and Power8 (S822) AIX, configuration best practice for LUNs?

Hello, We have an Power8 System (S822) and a IBM StorWize v3700 SAN. The OS is AIX 7.1. With this hardware from what I read I need to download/install special SDDPCM drivers, so I did (SDDPCM VERSION 2.6.6.0 (devices.sddpcm.71.rte). I carved my volumes in the StorWize and presented to... (3 Replies)
Discussion started by: c3rb3rus
3 Replies

9. AIX

HMC in VmWare NIC sl0 issue.

Hi There, First of all I'm new to *nix world, so bear with me and English is not my native tongue :) Now I'm working on the HMC 7.3.3.0 ServPack:0 base_version:20080402.1 to make it work in VmWare (testing in Workstation) I've got HMC installed and realized that network options in GUI... (8 Replies)
Discussion started by: JKat
8 Replies

10. AIX

IBM Power Linux Cluster Fence device on Power8 Platform

wasn't quite sure which forum to post in. What typical fence device to configure for a Power Linux PaceMaker Cluster running on the Power8 Platform (S822 Model of hardware), or what should be ordered with the S822 for use as a Fence Device? (5 Replies)
Discussion started by: mrmurdock
5 Replies
FIRMWARE(9)						   BSD Kernel Developer's Manual					       FIRMWARE(9)

NAME
firmware_register, firmware_unregister, firmware_get, firmware_put -- firmware image loading and management SYNOPSIS
#include <sys/param.h> #include <sys/systm.h> #include <sys/linker.h> #include <sys/firmware.h> struct firmware { const char *name; /* system-wide name */ const void *data; /* location of image */ size_t datasize; /* size of image in bytes */ unsigned int version; /* version of the image */ }; const struct firmware * firmware_register(const char *imagename, const void *data, size_t datasize, unsigned int version, const struct firmware *parent); int firmware_unregister(const char *imagename); const struct firmware * firmware_get(const char *imagename); void firmware_put(const struct firmware *fp, int flags); DESCRIPTION
The firmware abstraction provides a convenient interface for loading firmware images into the kernel, and for accessing such images from ker- nel components. A firmware image (or image for brevity) is an opaque block of data residing in kernel memory. It is associated to a unique imagename which constitutes a search key, and to an integer version number, which is also an opaque piece of information for the firmware subsystem. An image is registered with the firmware subsystem by calling the function firmware_register(), and unregistered by calling firmware_unregister(). These functions are usually (but not exclusively) called by specially crafted kernel modules that contain the firmware image. The modules can be statically compiled in the kernel, or loaded by /boot/loader, manually at runtime, or on demand by the firmware subsystem. Clients of the firmware subsystem can request access to a given image by calling the function firmware_get() with the imagename they want as an argument. If a matching image is not already registered, the firmware subsystem will try to load it using the mechanisms specified below (typically, a kernel module with the same name as the image). API DESCRIPTION
The kernel firmware API is made of the following functions: firmware_register() registers with the kernel an image of size datasize located at address data, under the name imagename. The function returns NULL on error (e.g. because an image with the same name already exists, or the image table is full), or a const struct firmware * pointer to the image requested. firmware_unregister() tries to unregister the firmware image imagename from the system. The function is successful and returns 0 if there are no pending references to the image, otherwise it does not unregister the image and returns EBUSY. firmware_get() returns the requested firmware image. If the image is not yet registered with the system, the function tries to load it. This involves the linker subsystem and disk access, so firmware_get() must not be called with any locks (except for Giant). Note also that if the firmware image is loaded from a filesystem it must already be mounted. In particular this means that it may be necessary to defer requests from a driver attach method unless it is known the root filesystem is already mounted. On success, firmware_get() returns a pointer to the image description and increases the reference count for this image. On failure, the func- tion returns NULL. firmware_put() drops a reference to a firmware image. The flags argument may be set to FIRMWARE_UNLOAD to indicate that firmware_put is free to reclaim resources associated with the firmware image if this is the last reference. By default a firmware image will be deferred to a taskqueue(9) thread so the call may be done while holding a lock. In certain cases, such as on driver detach, this cannot be allowed. FIRMWARE LOADING MECHANISMS
As mentioned before, any component of the system can register firmware images at any time by simply calling firmware_register(). This is typically done when a module containing a firmware image is given control, whether compiled in, or preloaded by /boot/loader, or man- ually loaded with kldload(8). However, a system can implement additional mechanisms to bring these images in memory before calling firmware_register(). When firmware_get() does not find the requested image, it tries to load it using one of the available loading mechanisms. At the moment, there is only one, namely Loadable kernel modules: A firmware image named foo is looked up by trying to load the module named foo.ko, using the facilities described in kld(4). In particular, images are looked up in the directories specified by the sysctl variable kern.module_path which on most systems defaults to /boot/kernel;/boot/modules. Note that in case a module contains multiple images, the caller should first request a firmware_get() for the first image contained in the module, followed by requests for the other images. BUILDING FIRMWARE LOADABLE MODULES
A firmware module is built by embedding the firmware image into a suitable loadable kernel module that calls firmware_register() on loading, and firmware_unregister() on unloading. Various system scripts and makefiles let you build a module by simply writing a Makefile with the following entries: KMOD= imagename FIRMWS= image_file:imagename[:version] .include <bsd.kmod.mk> where KMOD is the basename of the module; FIRMWS is a list of colon-separated tuples indicating the image_file's to be embedded in the mod- ule, the imagename and version of each firmware image. If you need to embed firmware images into a system, you should write appropriate entries in the <files.arch> file, e.g. this example is from sys/arm/xscale/ixp425/files.ixp425: ixp425_npe_fw.c optional npe_fw compile-with "${AWK} -f $S/tools/fw_stub.awk IxNpeMicrocode.dat:npe_fw -mnpe -c${.TARGET}" no-implicit-rule before-depend local clean "ixp425_npe_fw.c" # # NB: ld encodes the path in the binary symbols generated for the # firmware image so link the file to the object directory to # get known values for reference in the _fw.c file. # IxNpeMicrocode.fwo optional npe_fw dependency "IxNpeMicrocode.dat" compile-with "${LD} -b binary -d -warn-common -r -d -o ${.TARGET} IxNpeMicrocode.dat" no-implicit-rule clean "IxNpeMicrocode.fwo" IxNpeMicrocode.dat optional npe_fw dependency ".PHONY" compile-with "uudecode < $S/contrib/dev/npe/IxNpeMicrocode.dat.uu" no-obj no-implicit-rule clean "IxNpeMicrocode.dat" Note that generating the firmware modules in this way requires the availability of the following tools: awk, Make, the compiler and the linker. SEE ALSO
module(9), kld(4) /usr/share/examples/kld/firmware HISTORY
The firmware system was introduced in FreeBSD 6.1. AUTHORS
This manual page was written by Max Laier <mlaier@FreeBSD.org>. BSD
August 2, 2008 BSD
All times are GMT -4. The time now is 04:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy