The Lan card in one of our UIII WS's seem doesn't work,so with ping command i can not see any of the machines in LAN and with some other tests i'm sure it's not OK.
I tried to use the second card on PCI port ,but the replaced card was one of the ordinary card for PC's ...by the way after... (1 Reply)
Dear all
Im facing one problem in SCO 5.0.5 , its that in the server there are three LAN cards INTEL PRO 100 series but when we configure all the three cards then LAN stops working . self ping is possible but no one can ping the server. If we remove driver of any one card LAN starts working.
Is... (1 Reply)
hi all
i have installed SCO 5.0.5 on a "Netfinity 5000" IBM server. But the OS is not detecting the lan card. how can i detect it.... help and thanks in advance .
bidhayak (3 Replies)
Hi,
I've recently moved my pci LAN card from Slot2 Slot5 on my sun x4270_m2 server (solaris 10).
I've done the touch / reconfigure and devfsadm, however my issue is that im able to configure the e1000g7 port with an ip address (192.168.0.1) but if i plug my laptop (set with static ip... (7 Replies)
we have red hat 6 linux box
There are two lan card
one lan card eth0 have ip 10.82.190.31/24 GW 10.82.190.254
2th lan card eth1 have ip 10.82.188.33/24 GW 10.82.188.254
I have below route ... I use two route table
root@xxx# netstat -rn
Kernel IP routing table
Destination Gateway ... (5 Replies)
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
LEARN ABOUT CENTOS
pci_create_slot
PCI_CREATE_SLOT(9) Hardware Interfaces PCI_CREATE_SLOT(9)NAME
pci_create_slot - create or increment refcount for physical PCI slot
SYNOPSIS
struct pci_slot * pci_create_slot(struct pci_bus * parent, int slot_nr, const char * name, struct hotplug_slot * hotplug);
ARGUMENTS
parent
struct pci_bus of parent bridge
slot_nr
PCI_SLOT(pci_dev->devfn) or -1 for placeholder
name
user visible string presented in /sys/bus/pci/slots/<name>
hotplug
set if caller is hotplug driver, NULL otherwise
DESCRIPTION
PCI slots have first class attributes such as address, speed, width, and a struct pci_slot is used to manage them. This interface will
either return a new struct pci_slot to the caller, or if the pci_slot already exists, its refcount will be incremented.
Slots are uniquely identified by a pci_bus, slot_nr tuple.
There are known platforms with broken firmware that assign the same name to multiple slots. Workaround these broken platforms by renaming
the slots on behalf of the caller. If firmware assigns name N to
MULTIPLE SLOTS
The first slot is assigned N The second slot is assigned N-1 The third slot is assigned N-2 etc.
PLACEHOLDER SLOTS
In most cases, pci_bus, slot_nr will be sufficient to uniquely identify a slot. There is one notable exception - pSeries (rpaphp), where
the slot_nr cannot be determined until a device is actually inserted into the slot. In this scenario, the caller may pass -1 for slot_nr.
The following semantics are imposed when the caller passes slot_nr == -1. First, we no longer check for an existing struct pci_slot, as
there may be many slots with slot_nr of -1. The other change in semantics is user-visible, which is the 'address' parameter presented in
sysfs will
CONSIST SOLELY OF A DDDD
bb tuple, where dddd is the PCI domain of the struct pci_bus and bb is the bus number. In other words, the devfn of the 'placeholder' slot
will not be displayed.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 PCI_CREATE_SLOT(9)