08-25-2009
check ur /etc/path_to_inst ... i have sol10 installed in vmware server on my laptop and i can see e1000g0 interface .. it could be different for u but it should be in /etc/path_to_inst
9 More Discussions You Might Find Interesting
1. IP Networking
Hi Folks,
I've just installed solaris 8, but i cannot add my network card.
i've reboot the box, got into the configmode, and try'd to add a network card. but it doesn't work. I can't add a ip address to the card, an error occurs. Who do i add it.
Kind Regards (3 Replies)
Discussion started by: noripsni
3 Replies
2. Solaris
Hello,
I have just installed Solaris 9 x86 in a VMWare and the 1st problem I have is to enable the networking. I can only see the loopback interface and nothing else.
- I dont have any /etc/hostnames.xxx
- ifconfig -a shows only the loopback
- kstat -c net shows only the loopback ...
Any... (11 Replies)
Discussion started by: Tex-Twil
11 Replies
3. Solaris
Installed solaris 10 and now i want to connect to internet,to make work this i need to NIC drivers can some body tell me is it possible to get drivers and how to install. I am dying to get rid of this problem..please help me (1 Reply)
Discussion started by: srinivas2828
1 Replies
4. Solaris
Dear all,
I am a newbie in solaris and I need your advice.
I have a Solaris version 5.9 installed on Sunfire V240.
I am able to ssh the machine from putty remotely.
My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI... (2 Replies)
Discussion started by: mbouster
2 Replies
5. Solaris
Hi All,
does any body know how to create Virtual NIC in Solaris 10
if any one have good article or reference
kindly provide me
i try to Google
but i didn't find good one (7 Replies)
Discussion started by: jamisux
7 Replies
6. Solaris
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Discussion started by: vectrum
0 Replies
7. Solaris
hi guys,
is there any way to change the nic link_speed in Solaris 10? now my box is running degraded performance of the link speed as the switch is upgraded from 100m to 1000m.
dladm show-dev
e1000g0 link: up speed: 100 Mbps duplex: full
e1000g1 link: up ... (10 Replies)
Discussion started by: freshmeat
10 Replies
8. AIX
Hi,
is there any method to check the interface collisions on ethernet NIC in AIX. I know that in Solaris it's netstat -i but I've written that in AIX it doesn't show this.
Thanks®ards,
p (1 Reply)
Discussion started by: pitmod
1 Replies
9. Solaris
Hi All
I would need to do hard code of nxge0 nic to full duplex & 1000mbps. So that whenever solaris server come up after reboot. it will show full duplex & 1000mbps setting only.
Please also let me know how to do it online through command.
regards (0 Replies)
Discussion started by: amity
0 Replies
LEARN ABOUT SUSE
path_to_inst
path_to_inst(4) File Formats path_to_inst(4)
NAME
path_to_inst - device instance number file
SYNOPSIS
/etc/path_to_inst
DESCRIPTION
/etc/path_to_inst records mappings of physical device names to instance numbers.
The instance number of a device is encoded in its minor number, and is the way that a device driver determines which of the possible
devices that it may drive is referred to by a given special file.
In order to keep instance numbers persistent across reboots, the system records them in /etc/path_to_inst.
This file is read only at boot time, and is updated by add_drv(1M) and drvconfig(1M).
Note that it is generally not necessary for the system administrator to change this file, as the system will maintain it.
The system administrator can change the assignment of instance numbers by editing this file and doing a reconfiguration reboot. However,
any changes made in this file will be lost if add_drv(1M) or drvconfig(1M) is run before the system is rebooted.
Each instance entry is a single line of the form:
"physical name" instance number "driver binding name"
where
physical name is the absolute physical pathname of a device. This pathname must be enclosed in double quotes.
instance number is a decimal or hexadecimal number.
driver binding name is the name used to determine the driver for the device.
This name may be a driver alias or a driver name. The driver binding name must be enclosed in double quotes.
EXAMPLES
Example 1: Sample path_to_inst Entries
Here are some sample path_to_inst entries:
"/iommu@f,e0000000" 0 "iommu"
"/iommu@f,e0000000/sbus@f,e0001000" 0 "sbus"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@e,0" 14 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/sbusmem@f,0" 15 "sbusmem"
"/iommu@f,e0000000/sbus@f,e0001000/ledma@f,400010" 0 "ledma"
"/obio/serial@0,100000" 0 "zs"
"/SUNW,sx@f,80000000" 0 "SUNW,sx"
FILES
/etc/path_to_inst
SEE ALSO
add_drv(1M), boot(1M), drvconfig(1M), mknod(1M)
WARNINGS
If the file is removed the system may not be bootable (as it may rely on information found in this file to find the root, usr or swap
device). If it does successfully boot, it will regenerate the file, but after rebooting devices may end up having different minor numbers
than they did before, and special files created via mknod(1M) may refer to different devices than expected.
For the same reasons, changes should not be made to this file without careful consideration.
NOTES
This document does not constitute an API. path_to_inst may not exist or may have a different content or interpretation in a future
release. The existence of this notice does not imply that any other documentation that lacks this notice constitutes an API.
SunOS 5.10 2 Nov 1995 path_to_inst(4)