Sponsored Content
Full Discussion: ioscan command
Operating Systems HP-UX ioscan command Post 302481711 by fpmurphy on Sunday 19th of December 2010 10:51:46 AM
Old 12-19-2010
There are a number of different commands that you can use on GNU/Linux for the same purpose. lspci is probably what you are looking for.
This User Gave Thanks to fpmurphy For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

ioscan

Hi, I am looking for a similar 'ioscan' command in solaris 2.7. Is there any ? (5 Replies)
Discussion started by: guest100
5 Replies

2. HP-UX

ioscan

Hi, what is the difference in these two commands/ #ioscan -funC disk #ioscan -knfC disk To me both the commands produce the same information. regards jennifer:( (1 Reply)
Discussion started by: jennifer
1 Replies

3. What is on Your Mind?

IOSCAN Command

I need to know what is the differance between ioscan comand and search command ,in addition I search in your site for more details on ioscan command but I found nothing. (1 Reply)
Discussion started by: Kaswara
1 Replies

4. Solaris

SUN Solaris "ioscan"

Hi, What is the equivelent command for ioscan from HP in SUN, i.e I need to display all hardware devies with path/driver/stats etc. regards, Ahmed (2 Replies)
Discussion started by: Ahmad
2 Replies

5. HP-UX

Question about UNIX ioscan command

Hello there. I have a question regarding the ioscan commnad. When you execute the line ioscan -fnC processor it outputs a list of all processors in the machine. Does this list displays only physical CPUs or does it displays each core? For example, if i have a server with 1 Dual Core... (10 Replies)
Discussion started by: Spilson
10 Replies

6. HP-UX

ioscan on HP-UX 9.1

I am trying to work out the logical device name on a HP 9000 system running HP-UX 9.1. I see that ioscan-fnC disk looks like the command on later versions of HP-UX unfortunately it seems the n option is not available on 9.1. The output from ioscan -fC disk is:- Class H/W Path Driver H/W... (3 Replies)
Discussion started by: malcqv
3 Replies

7. Solaris

Solaris equivalent of the ioscan command

What is the Solaris equivalent of the HP-UX "ioscan -funC" command which lists all hardware on the system? (5 Replies)
Discussion started by: etc
5 Replies

8. Solaris

How to solve "ioscan -En" hardware errors

Hi, I found devices errors in #ioscan -En. it is showing that soft errors = 0 and hard errors= 5. what should i do for hard errors=0. Thanks. (4 Replies)
Discussion started by: arjunreddy3
4 Replies

9. Solaris

ioscan -En how to exclude tapes?

i would like to list all disks, but this command with these options list tapes too. i donīt find out an option which list only the class like ioscan in hp-ux. could anybody help me? thanks a lot. (2 Replies)
Discussion started by: pabloli150
2 Replies

10. UNIX for Dummies Questions & Answers

passing command output from one command to the next command in cshell

HI Guys, I hope you are well. I am trying to write a script that gets executed every time i open a shell (cshell). I have two questions about that 1) I need to enter these commands $ echo $DISPLAY $ setenv $DISPLAY output_of_echo_$display_command How can i write a... (2 Replies)
Discussion started by: kaaliakahn
2 Replies
lspci(8)							Linux PCI Utilities							  lspci(8)

NAME
lspci - list all PCI devices SYNOPSIS
lspci [options] DESCRIPTION
lspci is a utility for displaying information about all PCI buses in the system and all devices connected to them. To make use of all the features of this program, you need to have Linux kernel 2.1.82 or newer which supports the /proc/bus/pci interface. With older kernels, the PCI utilities have to use direct hardware access which is available only to root and it suffers from numerous race conditions and other problems. If you are going to report bugs in PCI device drivers or in lspci itself, please include output of "lspci -vvx". OPTIONS
-v Tells lspci to be verbose and display detailed information about all devices. -vv Tells lspci to be very verbose and display even more information (actually everything the PCI device is able to tell). The exact meaning of these data is not explained in this manual page, if you want to know more, consult /usr/include/linux/pci.h or the PCI specs. -n Show PCI vendor and device codes as numbers instead of looking them up in the PCI ID database. -x Show hexadecimal dump of first 64 bytes of the PCI configuration space (the standard header). Useful for debugging of drivers and lspci itself. -xxx Show hexadecimal dump of whole PCI configuration space. Available only for root as several PCI devices crash when you try to read undefined portions of the config space (this behaviour probably doesn't violate the PCI standard, but it's at least very stupid). -b Bus-centric view. Show all IRQ numbers and addresses as seen by the cards on the PCI bus instead of as seen by the kernel. -t Show a tree-like diagram containing all buses, bridges, devices and connections between them. -s [[<bus>]:][<slot>][.[<func>]] Show only devices in specified bus, slot and function. Each component of the device address can be omitted or set as "*" meaning "any value". All numbers are hexadecimal. E.g., "0:" means all devices on bus 0, "0" means all functions of device 0 on any bus, "0.3" selects third function of device 0 on all buses and ".4" shows only fourth function of each device. -d [<vendor>]:[<device>] Show only devices with specified vendor and device ID. Both ID's are given in hexadecimal and may be omitted or given as "*" meaning "any value". -i <file> Use <file> as PCI ID database instead of /usr/share/hwdata/pci.ids. -p <dir> Use <dir> as directory containing PCI bus information instead of /proc/bus/pci. -m Dump PCI device data in machine readable form (both normal and verbose format supported) for easy parsing by scripts. -M Invoke bus mapping mode which scans the bus extensively to find all devices including those behind misconfigured bridges etc. Please note that this is intended only for debugging and as it can crash the machine (only in case of buggy devices, but unfortunately these happen to exist), it's available only to root. Also using -M on PCI access methods which don't directly touch the hardware has no sense since the results are (modulo bugs in lspci) identical to normal listing modes. --version Shows lspci version. This option should be used standalone. PCILIB OPTIONS
The PCI utilities use PCILIB (a portable library providing platform-independent functions for PCI configuration space access) to talk to the PCI cards. The following options control parameters of the library, especially what access method it uses. By default, PCILIB uses the first available access method and displays no debugging messages. Each switch is accompanied by a list of hardware/software configurations it's supported in. -P <dir> Use Linux 2.1 style configuration access to directory <dir> instead of /proc/bus/pci. (Linux 2.1 or newer only) -H1 Use direct hardware access via Intel configuration mechanism 1. (i386 and compatible only) -H2 Use direct hardware access via Intel configuration mechanism 2. Warning: This method is able to address only first 16 devices on any bus and it seems to be very unrealiable in many cases. (i386 and compatible only) -S Use PCI access syscalls. (Linux on Alpha and UltraSparc only) -F <file> Extract all information from given file containing output of lspci -x. This is very useful for analysis of user-supplied bug reports, because you can display the hardware configuration in any way you want without disturbing the user with requests for more dumps. (All systems) -G Increase debug level of the library. (All systems) FILES
/usr/share/hwdata/pci.ids A list of all known PCI ID's (vendors, devices, classes and subclasses). /proc/bus/pci An interface to PCI bus configuration space provided by the post-2.1.82 Linux kernels. Contains per-bus subdirectories with per-card config space files and a devices file containing a list of all PCI devices. SEE ALSO
setpci(8) AUTHOR
The Linux PCI Utilities are maintained by Martin Mares <mj@ucw.cz>. pciutils-2.1.10 30 March 2002 lspci(8)
All times are GMT -4. The time now is 05:55 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy