Sponsored Content
Full Discussion: Poblem with libX11.so.4
Operating Systems Solaris Poblem with libX11.so.4 Post 302306017 by incredible on Friday 10th of April 2009 12:01:13 PM
Old 04-10-2009
Can you serial in to the machine and capture the console message. Try to halt the system and boot it to failsafe mode and fsck on the filesystem. first fix the rebooting problem
 

2 More Discussions You Might Find Interesting

1. Solaris

libX11.so.4 - how do i get this ?

Hi there I am trying to install the prerequisites for sunfreeware apache/php, one of which is apparrantly libX11.so.4 bash-3.2# ldd /usr/local/apache2/modules/libphp5.so librt.so.1 => /usr/lib/librt.so.1 libsybdb.so.5 => /usr/local/freetds/lib/libsybdb.so.5 ... (6 Replies)
Discussion started by: hcclnoodles
6 Replies

2. Hardware

USB power cycling poblem on RPI

I am having a problem with cycling USB bus power on the RPI B+ (3.18.7+). Each time I power the USB bus off and on, a device plugged into it gets a higher Device number, and eventually the bus crashes (does not enumerate new devices any more) As a demonstration, I wrote the python script... (4 Replies)
Discussion started by: vthielen
4 Replies
ucodeadm(1M)						  System Administration Commands					      ucodeadm(1M)

NAME
ucodeadm - update processor microcode SYNOPSIS
/usr/sbin/ucodeadm -v /usr/sbin/ucodeadm -umicrocode-text-file /usr/sbin/ucodeadm -i [-R path] microcode-text-file DESCRIPTION
The ucodeadm utility can be used to report running microcode revision on the processors, update microcode, or install microcode on the tar- get system to be used during the boot process. The microcode-text-file can be obtained from processor vendors. OPTIONS
-v Report microcode revision. -u microcode-text-file Update microcode on all cross-call interrupt ready processors. -i microcode-text-file Install microcode files on target system to be used during the next boot cycle. The text file name must have the vendor name prefix, such as "intel" or "amd". By default the microcode files will be installed at: /platform/i86pc/ucode/$VENDORSTR/ where VENDORSTR is either "GenuineIntel" or "AuthenticAMD". -R alternate path Install microcode path in the alternate path. EXAMPLES
Example 1 Reporting the Microcode Revision The following example displays the microcode revision that is currently running: # ucodeadm -v Example 2 Updating the Processor Microcode The following example updates the processor microcode to intel-ucode.txt: # ucodeadm -u intel-ucode.txt Example 3 Installing the Microcode on the Target System The following example installs the microcode on the target system, /export/ucode-path: # ucodeadm -i -R /export/ucode-path intel-ucode.txt If an alternate path is used when installing the microcode on the target system, the installed microcode file is not used on the next boot cycle. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ SEE ALSO
psradm(1M), psrinfo(1M), attributes(5) SunOS 5.11 10 Jul 2007 ucodeadm(1M)
All times are GMT -4. The time now is 04:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy