Sponsored Content
Operating Systems Solaris Solaris 10 on Dell R710 server Post 302507193 by DukeNuke2 on Wednesday 23rd of March 2011 03:55:50 AM
Old 03-23-2011
while dell hardware has even half the features of oracle/sun hardware... like no ilom or only one network port and powersupply (depending on the modell).
 

5 More Discussions You Might Find Interesting

1. Solaris

Installing Solaris 10 on Dell PowerEdge 2800

hi, i am trying to install solaris 10 (on 4 cd's downloaded from the sun website) on my dell poweredge 2800 server. 2 xeon processors, 2GB of RAM and 2 NICS, 73 GB SCSI (maxtor ultra320, 3.5 series), i can give more details on request... the installation crashes when trying to detect the NICS... (0 Replies)
Discussion started by: xinugeek
0 Replies

2. Filesystems, Disks and Memory

Linux and Dell 1500sc Poweredge Server

Does anybody no how to get around the fact that the Red Hat installation does not see the SCSI hard drives. It lets you manually pick the proper device, but still fails saying no drive detected (or something to that effect). I was going to install windows 2003 Server and use VMware...but again,... (1 Reply)
Discussion started by: Fatflea
1 Replies

3. UNIX for Dummies Questions & Answers

Dell monitor blinking with the Solaris

Hi I have experienced some problems with the new monitor on my Solaris WS (Solaris5.4). Old monitor (Sony ES200) died an we installed a new one (Dell Ultrascan P780) The system booted but the monitor statrted blinking at the rate about once in 5-7 seconds. This is espetially strange that the... (0 Replies)
Discussion started by: Andrey Malishev
0 Replies

4. Solaris

Solaris 10 and DELL TL-2000 Tape Library with ISCSI

Hello, i am trying to get following configuration up running, but get no access to the library roboter. Server: SunOS 5.10 Generic_138889-03 i86pc i386 i86pc DELL TL-2000: 1 Tape: IBM ULT3580-HH4 and Robot: 3573-TL, connected via ISCSI Bridge (build into the TL) ... (1 Reply)
Discussion started by: austin73
1 Replies

5. Solaris

Solaris 10 installation on dell power edge 1950

Hi, I am about to try Solaris 10 on a dell power edge 1950 server. I have googled and found some articles(2007) saying its not supported. Anybody tried this recently? Thanks in advance (2 Replies)
Discussion started by: ./hari.sh
2 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:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy