Sponsored Content
Operating Systems Solaris X6799A PCI cards and Sunfire v880 Post 83951 by markdr011 on Wednesday 21st of September 2005 02:44:14 AM
Old 09-21-2005
Thanks for your reply.

Will try cards in new slots
 

10 More Discussions You Might Find Interesting

1. BSD

WLAN PCI Cards

Hi! I just wanted to know what network cards are supported in FreeBSD. I have looked at the list of supported cards but I can't find any of them in the stores. Is the list not updated, I would really preciate info about where (in EU, Sweden) I can buy them. /Peter (2 Replies)
Discussion started by: Barfly.se
2 Replies

2. AIX

PCI Ethernet Cards for IBM RISC 6000 - B50's

I am trying to find PCI Ethernet cards that are compatible with the IBM RISC 6000 - B50 Power PC. None of the regular NIC's seem to have AIX drivers. Does anyone know of AIX drivers for standard PCI Ethernet NIC's or a non IBM NIC that works with the Model B50 at 10/100 MB ? (0 Replies)
Discussion started by: rahe
0 Replies

3. Solaris

Moving HBA cards to different PCI slots

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

KVM for V880's

We have 3 V880's and we need to purchase a KVM for them. I've never purchased one before. Does anyone have a recommendation for one? (3 Replies)
Discussion started by: dangral
3 Replies

5. Solaris

Sun V880

I have two mechine, one is SUN V880 and another is IBM p570. I run the same script on V880 and p570 , why the cpu usage always under 50% on V880 but the cpu usage can growth to 100% on p570. (4 Replies)
Discussion started by: golden
4 Replies

6. Solaris

Serial Port Connection to a Sunfire V880 (having Solaris 10)

Hi, I'mtrying to connect a Device via the serial port to my Solaris 10 environment (Sunfire V880). I have setup ttyb to connect to the Device. I am getting a connected status in my Port Listing (Using a separate Module that I have in the app running in the environment) but the moment I try to... (0 Replies)
Discussion started by: Alchemist
0 Replies

7. Solaris

Host ID of v880

Hello All, I am not a sun expert, but in my network administration job I had to deal with SUN servers. We've to replace a faulty motherboard of SF V880. As per my understanding, host id of machines is programmed in PROM. So will host ID be changed with the replacement of V880 motherboard?... (6 Replies)
Discussion started by: Charagh
6 Replies

8. Solaris

Sunfire V880 Internal Disk Problem

Any help on this would be greatly appreciated. I have read other threads on similar subject but still not clear on what this is telling me and what action to take. Do I have a couple of disks that are slowly dying? While checking disk usage on the V880 I noticed the following: # format... (3 Replies)
Discussion started by: jamba1
3 Replies

9. Solaris

Attaching 1TB external drive to SunFire v880

Hi I have a 1TB external drive that I want to attach to a SunFire v880 server which runs on Solaris 9. After attaching the external drive what commands should I issue so that the drive will be seen by the server? (7 Replies)
Discussion started by: rahmantanko
7 Replies

10. Hardware

Sunfire V880

Hi Does someone have the latest firmware for a sunfire v880 I have a problem with the FC-AL disk i guess i need to upgrade the firmware but i dont have a support with oracle and i can't find it anywhere thank you (4 Replies)
Discussion started by: simplextibi
4 Replies
BIOSDEVNAME(1)						      General Commands Manual						    BIOSDEVNAME(1)

NAME
biosdevname - give BIOS-given name of a device SYNOPSIS
biosdevname [options] [args]... DESCRIPTION
biosdevname takes a kernel device name as an argument, and returns the BIOS-given name it "should" be. OPTIONS
-i, --interface Treat [args] as ethernet devs -d, --debug Enable debugging -p, --policy [physical|all_ethN] -P, --prefix [string] string use for embedded NICs in the physical policy (default=em) -x, --nopirq Do not use $PIR table for mapping PCI device to slot. Some BIOS have incorrect values. -s, --smbios [x.y] Require minimum SMBIOS version x.y POLICIES
The physical policy is the current default. However, when invoking biosdevname in udev rules, one should always specify the policy you want, as the default has changed over time. The physical policy uses the following scheme: em<port>[_<virtual instance>] for embedded NICs p<slot>p<port>[_<virtual instance>] for cards in PCI slots The all_ethN policy makes a best guess at what the device order should be, with embedded devices first, PCI cards in ascending slot order, and ports in ascending PCI bus/device/function order breadth-first. However, this policy does not work if your PCI devices are hot-plugged or hot-pluggable, including the virtual functions on an SR-IOV device. In a hot-plug scenario, each separate udev instance will be invoked in parallel, while the device tree is still being populated with new devices. Each udev instance will see a different PCI tree, and thus cannot provide consistent enumeration. Use of this policy should be limited to only scenarios where all PCI devices are present at boot (cold-plug). EXIT CODES
Returns 0 on success, with BIOS-suggested name printed to stdout. Returns 1 on provided device name lookup failure. Returns 2 if system BIOS does not provide naming information. biosdevname requires system BIOS to provide naming information, either via SMBIOS or sysfs files. Returns 3 if not run as root but requires root privileges. Returns 4 if running in a virtual machine. SEE ALSO
http://linux.dell.com/wiki/index.php/Oss/libnetdevname http://linux.dell.com/files/biosdevname/ git://linux.dell.com/biosdevname.git RELATED PROGRAMS
The dmidecode package contains two tools useful for debugging BIOS features that biosdevname uses, specifically dmidecode to read the SMBIOS Type 9 and Type 41 tables, and biosdecode to read the PCI IRQ Routing Table. Please include the output of each of these programs in any bug reports. AUTHOR
biosdevname was written by Matt Domsch <Matt_Domsch@dell.com> This manual page was written by Rudy Gevaert <Rudy.Gevaert@UGent.be>, for the Debian project (but may be used by others). Nov 28, 2010 BIOSDEVNAME(1)
All times are GMT -4. The time now is 08:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy