07-25-2008
Quote:
Originally Posted by
reborg
What exactly do you mean my open? Is it unused?
Correct. We're trying to find open pci slots to fill up. I'm planning to run a script that provides a report on all the open pci slots available in our vast array of sun and hp servers.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Does anyone know the command to configure HP tape slots. I have tried the following on Sun, but its notworking. This is the first time I have configured a tape drive with muiltple slots.
root@ssdb0009 # cfgadm -l
Ap_Id Type Receptacle Occupant Conditio... (3 Replies)
Discussion started by: dennisca
3 Replies
2. Filesystems, Disks and Memory
Hello,
I'm running Red Hat Linux on a Dell Poweredge 2650 Rack Server and wondered if anyone knew of a tool or command I could use to probe the memory slots on the motherboard.
I know the machine has six memory slots and currently contains 1GB RAM, what I don't know however, is if it contains... (3 Replies)
Discussion started by: cw1972
3 Replies
3. Solaris
Has anyone ever relocated an HBA card after already having it configured in another PCI slot? I've found that the HBA instance #'s start incrementing past the previous. It results in me having to have my instance numbers in /kernel/drv/qla2300.conf be 4,5,6,7 instead of 0,1,2,3. Cleanup with... (5 Replies)
Discussion started by: kduffin
5 Replies
4. Solaris
Due to speed mismatch, the server kept crashing. Sun suggests that I need to move the two HBA cards from the 66Mhz to the 33Mhz slots. There are tons of disks that are connected to these HBAs and I have Veritas volume manager.
Does anyone have a list of what I need to do prior/after moving to... (3 Replies)
Discussion started by: kiem
3 Replies
5. Solaris
I've got lots of scsi transport errors on the E2900 - the HBA was replaced once out of curiosity but the problem still exists.
Feb 15 07:03:11 ivsdbch2 scsi: WARNING: /ssm@0,0/pci@18
,600000/SUNW,jfca@1,1/fp@0,0/ssd@w5005076300c889cb,4 (ssd21):
Feb 15 07:03:11 ivsdbch2 SCSI transport... (1 Reply)
Discussion started by: kiem
1 Replies
6. Solaris
Hi All,
Can Any body tell me how to find out the how many memory slots are there in SUN server ??
Thanks and Regards, (2 Replies)
Discussion started by: lbreddy
2 Replies
7. AIX
A while back I had a command that shows the memory slots (and info on the modules inserter) in an IBM AIX machine. I cannot remember it at this time, can someone help me out with this command please? (4 Replies)
Discussion started by: bbbngowc
4 Replies
8. AIX
Hi, all. I was wondering if there's a command or log file that will tell me how much RAM is in the system and, more specifically, the size of each stick.
Thanks,
Jason (3 Replies)
Discussion started by: JasonRkr
3 Replies
9. Solaris
How do I find any available PCI slots on a v440?
When I run prtconf, I get the following output? But I am not able to make out whether all the PCI slots are used.
================================= IO Devices =================================
Bus Freq
Brd Type MHz Slot ... (1 Reply)
Discussion started by: jtamminen
1 Replies
10. Solaris
I tried to reinstall GRUB2 on my previous Solaris 11.3 installation but could not figure out why "bootadm install-bootloader" failed. Now I am trying to reinstall Solaris 11.3 instead, over my old Solaris partition. I am using the USB Live media ISO with the GUI. Installation fails with this... (0 Replies)
Discussion started by: kebabbert
0 Replies
LEARN ABOUT NETBSD
pcibus_conf_write
PCI(3) BSD Library Functions Manual PCI(3)
NAME
pci -- library interface for PCI bus access
LIBRARY
PCI Bus Access Library (libpci, -lpci)
SYNOPSIS
#include <pci.h>
int
pcibus_conf_read(int pcifd, u_int bus, u_int dev, u_int func, u_int reg, pcireg_t *valp);
int
pcibus_conf_write(int pcifd, u_int bus, u_int dev, u_int func, u_int reg, pcireg_t val);
int
pcidev_conf_read(int devfd, u_int reg, pcireg_t *valp);
int
pcidev_conf_write(int devfd, u_int reg, pcireg_t val);
char *
pci_findvendor(pcireg_t id_reg);
void
pci_devinfo(pcireg_t id_reg, pcireg_t class_reg, char *devinfo, size_t len);
void
pci_conf_print(int pcifd, u_int bus, u_int dev, u_int func);
DESCRIPTION
The pci library provides support for accessing the PCI bus by user programs.
These functions are available in the libpci library. Programs should be linked with -lpci.
CONFIGURATION SPACE FUNCTIONS
The following functions are used to access PCI configuration space:
pcibus_conf_read()
Access the PCI configuration register reg on the device located at bus, dev, func, and place the result in *valp. pcifd must be an
open file descriptor to a PCI bus within the target PCI domain.
pcibus_conf_write()
Write the value specified by val into the PCI configuration register reg on the device located at bus, dev, func. pcifd must be an
open file descriptor to a PCI bus within the target PCI domain.
pcidev_conf_read()
Access the PCI configuration register reg on the device associated with the open file descriptor devfd and place the result in *valp.
pcidev_conf_write()
Write the value specified by val into the PCI configuration register reg on the device associated with the open file descriptor devfd.
MISCELLANEOUS FUNCTIONS
The following miscellaneous functions are available:
pci_findvendor()
Return an ASCII description of the PCI vendor in the PCI ID register id_reg.
pci_devinfo()
Return an ASCII description of the PCI vendor, PCI product, and PCI class specified by the PCI ID register id_reg and PCI class ID reg-
ister class_reg. The description is placed into the buffer pointed to by devinfo; the size of that buffer is specified in len.
pci_conf_print()
Print the PCI configuration information for the device located at bus, dev, func. pcifd must be an open file descriptor to a PCI bus
within the target PCI domain.
RETURN VALUES
The pcibus_conf_read(), pcibus_conf_write(), pcidev_conf_read(), and pcidev_conf_write() functions return 0 on success and -1 on failure.
The pci_findvendor() function returns NULL if the PCI vendor description cannot be found.
SEE ALSO
pci(4)
HISTORY
The pcibus_conf_read(), pcibus_conf_write(), pcidev_conf_read(), pcidev_conf_write(), pci_findvendor(), pci_devinfo(), and pci_conf_print()
functions first appeared in NetBSD 1.6.
BSD
April 24, 2004 BSD