Sponsored Content
Operating Systems Solaris Solaris commands to retrieve chipset information Post 302972229 by gull04 on Tuesday 3rd of May 2016 05:52:35 AM
Old 05-03-2016
Hi,

If you run prtconf -pv you should be able to find most of what you are looking for.

Regards

Gull04
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

C-Media 8738 chipset for FBSD 4.4

HI i'm compiling my kernel with the support of this chipset. In FreeBSD 4.2 and 4.3 I got no problem with the kernel, but with 4.4 I just can't get the kernel compiled with the soundcard support. i added this to my kernel device pcm device snd something wrong... (2 Replies)
Discussion started by: Stormpie
2 Replies

2. Shell Programming and Scripting

A script pls( To retrieve database information)

KSH - Unix -AIX - db2 ************** Get the input from the user say '123' (It varies) Then i want to connect to a database say "D1" then i want th extract from the database by giving "select * from tablename where input = '123' I also want to connect to another database "D2" then i... (3 Replies)
Discussion started by: rollthecoin
3 Replies

3. Solaris

Solaris on AMD 770 chipset

hi is there anyone out there who has experience with installing Solaris on this chipset? there is one entry in the HCL doc about it (BigAdmin - HCL: Gigabyte GA-MA770-DS3 rev1.0 ) but that person apparently doesnt reply when another asks him some questions. im looking to install on... (3 Replies)
Discussion started by: Landser
3 Replies

4. Solaris

command to retrieve user information

Hi, I want the command to retrieve the existing user information such as * authorization * Profile * role * exipre(expiration date of login) * inactive please tell me how to do that Thank you. (3 Replies)
Discussion started by: S_venkatesh
3 Replies

5. Solaris

realteak HD Audio Chipset

I am wondering if there is a way to get opensolaris to accept my realteck hd audio chip set. dmesg Thu Oct 23 22:47:38 EDT 2008 Oct 23 22:34:49 opensolaris Use is subject to license terms. Oct 23 22:34:49 opensolaris unix: features:... (1 Reply)
Discussion started by: FloridaBSD
1 Replies

6. Shell Programming and Scripting

Retrieve old file in Solaris 10

Hello guys, I mistakely updated a file on Solaris 10. Any idea on how can I get the older version of file(File before being updated) back? Note: I do not have root access & have logged in as a user on the system. Thanks in advance, -Nithin. (3 Replies)
Discussion started by: bsnithin
3 Replies

7. Shell Programming and Scripting

Execute a C program and retrieve information

Hi I have the following script: #!/bin/sh gcc -o program program.c ./program & PID=$! where i execute a C program and i get its pid. I want to retrieve information about this program (e.g memory consumption) using command top. So far i have: top -d 1.0 -p $PID But i dont know how to... (6 Replies)
Discussion started by: nteath
6 Replies

8. Shell Programming and Scripting

Retrieve information Text/Word from HTML code using awk/sed

awk/sed newbie here. I have a HTML file and from that file and I would like to retrieve a text word. <font face=arial size=-1><li><a href=/value_for_clients/Tokyo/abc_process.txt>abc</a> NDK Version: 4.0 </li> <font face=arial size=-1><li><a... (6 Replies)
Discussion started by: sk2code
6 Replies

9. Shell Programming and Scripting

Match and retrieve information from file

Hello I just want to ask how to get the match of information column 2 file 1 and retrieve information from column 2 file 2. The column exon in file 1 and column color code in file 2. File 1 //NODECOLORCODE "Exon 1" "ENST00000595813" //NODECOLORCODE "Exon 1" ... (4 Replies)
Discussion started by: Wan Fahmi
4 Replies

10. Shell Programming and Scripting

Obfuscating sensitive information in EXPORT commands

Hi. Been a while since I posted last time, and I hope you all are doing well. I'm automating a Data Integration process end to end using Shell programming over Linux 2.6x platform, and I'm accessible to Korn and Bash shells with provision to use Perl 5.1 also. What we do as a common practice... (4 Replies)
Discussion started by: kumarjt
4 Replies
prtconf(1M)															       prtconf(1M)

NAME
prtconf - print system configuration SYNOPSIS
/usr/sbin/prtconf [-V] | [-F] | [-x] | [-bpv] | [-acDPv] [dev_path] The prtconf command prints the system configuration information. The output includes the total amount of memory, and the configuration of system peripherals formatted as a device tree. If a device path is specified on the command line for those command options that can take a device path, prtconf will only display informa- tion for that device node. The following options are supported: -a Display all the ancestors device nodes, up to the root node of the device tree, for the device specified on the command line. -b Display the firmware device tree root properties for the purpose of platform identification. These properties are "name", "compat- ible", "banner-name" and "model". -c Display the device subtree rooted at the device node specified on the command line, that is, display all the children of the device node specified on the command line. -D For each system peripheral in the device tree, displays the name of the device driver used to manage the peripheral. -F Returns the device path name of the console frame buffer, if one exists. If there is no frame buffer, prtconf returns a non-zero exit code. This flag must be used by itself. It returns only the name of the console, frame buffer device or a non-zero exit code. For example, if the console frame buffer on a SUNW,Ultra-30 is ffb, the command returns: /SUNW,ffb@1e,0:ffb0. This option could be used to create a symlink for /dev/fb to the actual console device. -p Displays information derived from the device tree provided by the firmware (PROM) on SPARC platforms or the booting system on platforms.The device tree information displayed using this option is a snapshot of the initial configuration and may not accu- rately reflect reconfiguration events that occur later. -P Includes information about pseudo devices. By default, information regarding pseudo devices is omitted. -v Specifies verbose mode. -V Displays platform-dependent PROM (on SPARC platforms) or booting system (on platforms) version information. This flag must be used by itself. The output is a string. The format of the string is arbitrary and platform-dependent. -x Reports if the firmware on this system is 64-bit ready. Some existing platforms may need a firmware upgrade in order to run the 64-bit kernel. If the operation is not applicable to this platform or the firmware is already 64-bit ready, it exits silently with a return code of zero. If the operation is applicable to this platform and the firmware is not 64-bit ready, it displays a descriptive message on the standard output and exits with a non-zero return code. The hardware platform documentation contains more information about the platforms that may need a firmware upgrade in order to run the 64-bit kernel. This flag overrides all other flags and must be used by itself. The following operands are supported: dev_path The path to a target device minor node, device nexus node, or device link for which device node configuration information is displayed The following exit values are returned: 0 No error occurred. non-zero With the -F option (SPARC only), a non-zero return value means that the output device is not a frame buffer. With the -x option, a non-zero return value means that the firmware is not 64-bit ready. In all other cases, a non-zero return value means that an error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWesu | +-----------------------------+-----------------------------+ |Interface Stability |Unstable | +-----------------------------+-----------------------------+ fuser(1M), modinfo(1M), sysdef(1M), attributes(5) Sun Hardware Platform Guide SPARC Only openprom(7D) The output of the prtconf command is highly dependent on the version of the PROM installed in the system. The output will be affected in potentially all circumstances. The driver not attached message means that no driver is currently attached to that instance of the device. In general, drivers are loaded and installed (and attached to hardware instances) on demand, and when needed, and may be uninstalled and unloaded when the device is not in use. On platforms, the use of prtconf -vp provides a subset of information from prtconf -v. The value of integer properties from prtconf -vp might require byte swapping for correct interpretation. 9 Aug 2005 prtconf(1M)
All times are GMT -4. The time now is 02:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy