11-01-2016
You haven't added the Broadcom device yet? Is this because you tried, and the device is not either of the ones for which there is a SCO driver.
HP does not have any SCO drivers for the z400.
For the Realtek card you probably have to supply the PCI Slot number, the Bus Number and the Device Number. These are sometimes available in the CMOS, or are displayed during POST.
This User Gave Thanks to jgt For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Our shops server runs SCO Openserver 5 release 5. It has two network cards in it (one on 10.0.0.6 and one on 90.0.0.99). When I run scoadmin and look at the network settings it show both my 3com network cards and a loop back driver http://theentertainer.com/james/untitled.jpg
Can anyone tell... (1 Reply)
Discussion started by: potter
1 Replies
2. SCO
I have got a Sco Unix Server, i want to connect some windows workstations. What configurations do i need to make on server and or workstation? (1 Reply)
Discussion started by: tpurazi1
1 Replies
3. AIX
I have an LPAR in a P5 machine which has been setup in an HACMP cluster. The person who set it up allocated the wrong network adapter (en) to the persistent network. For the life of me I cannot find where I can re-assign this adapter. Anyone able to help me as I am tearing my hair out and do not... (1 Reply)
Discussion started by: johnf
1 Replies
4. SCO
Hello Guys,
We have an old PC running on SCO Unix V. Is there any sites where i can get manual/procedures on how to install and configure Network. Thanks (2 Replies)
Discussion started by: nrcuevas
2 Replies
5. AIX
hello
i've need to change network adapter on machine H80 aix 4.3.3 hacmp ( ent0 )
what i need to do after the new adapter installed on the machine?
thanks
best regards
ariec (1 Reply)
Discussion started by: ariec
1 Replies
6. AIX
When I configure two VIO Servers, VIOS1 used to ping its gateway, after I configured second VIOS2, VIOS1 cannpt ping its gateway, when I run this command:
entstat -all ent#|grep -i priority
Priority: 5 Active: False
How to make Active to True? (1 Reply)
Discussion started by: rainbow_bean
1 Replies
7. UNIX for Dummies Questions & Answers
Hi All,
I am new here - this is my first post.
I have installed Solaris 10 5/09 on my Dell M6300. The install went well, but the Dell's onboard network card is the Broadcom BCM5756ME Gigabit Ethernet - and sadly no Solaris driver exists for it. The Solaris 10 install just jumped by the... (1 Reply)
Discussion started by: soulmerchant
1 Replies
8. UNIX for Dummies Questions & Answers
Hi All
I P2Vd a Unixware 7.1.4 box with VMWare Vsphere. I try to add a network adapter under Network Configuration Manager and it comes up with the error attached.
I've added a virtual adapter using the "E1000" option. It detects both the AMD PCI NET and E1000 virtual adapters under Network... (8 Replies)
Discussion started by: flashinwrx
8 Replies
9. SCO
hi
i installed sco unix open server 5.0.7 on virtual machine vmware and runing it,
its work perfect and good.
now how i can configuare network at scoadmin that i able to access nework ?
---------- Post updated at 08:56 AM ---------- Previous update was at 01:47 AM ----------
nobody can... (2 Replies)
Discussion started by: farzad226
2 Replies
10. Red Hat
Hello community, I have a Proliant HP DL380P with the following network adapters:
NetXtreme BCM5719 Gigabit Ethernet PCIe (Ethernet 1Gb 4-port 331FLR Adapter)
82580 Gigabit Network Connection (NC365T 4-port Ethernet Server Adapter)
I installed Red Hat 7.2 but it recognizes only the... (9 Replies)
Discussion started by: Lord Spectre
9 Replies
LEARN ABOUT HPUX
gvid_no_claim_dev
gvid_no_claim_dev(5) File Formats Manual gvid_no_claim_dev(5)
NAME
gvid_no_claim_dev - PCI Vendor/Device ID that the gvid graphics driver will not claim
VALUES
Failsafe
Default
Allowed values
Recommended values
Specific to the device you wish to prevent from claiming.
DESCRIPTION
This tunable specifies the PCI Vendor ID and/or Device ID of a graphics device that the HP graphics driver should not claim.
The graphics driver was designed to be a general purpose driver for all PCI graphics cards. As a result, the driver will attempt to claim
any PCI graphics display device found on the system. This can be a problem for graphics device developers who need their own graphics
driver to claim their own graphics device.
The value of will specify a PCI Vendor ID and/or Device ID of a graphics card that the gvid graphics driver should not claim. It is a 32
bit number, with the upper 16 bits containing the PCI Vendor ID and the lower 16 bits containing the PCI Device ID. Either the Vendor ID
or Device ID can use a wildcard value of
For example, if is set to the value the driver will ignore graphics devices with a PCI Vendor ID of and a Device ID of If is set to the
driver will not claim any graphics cards with a Vendor ID of regardless of the Device ID.
Who Is Expected to Change This Tunable?
Anyone who wishes the graphics driver to ignore a specific graphics device. This will typically be someone writing their own graphics
driver for their own hardware.
Restrictions on Changing
Changes to this tunable take effect at the next reboot.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
Tunable Kernel Parameters gvid_no_claim_dev(5)