Finding the NIC driver version on Solaris 11


 
Thread Tools Search this Thread
Operating Systems Solaris Finding the NIC driver version on Solaris 11
# 1  
Old 03-19-2013
Oracle Finding the NIC driver version on Solaris 11

In Solaris 10 it was easy, a simple grep through modinfo output and you'd have the version of any loaded module, including your NIC drivers. In my career I've seen many people relying on this information in their scripts. Now I'm on Solaris 11, and where have the version numbers gone? The modinfo output on Solaris 11 no longer yields version numbers.

To save others from the trouble of having to figure this one out, I've written up my notes on how to solve this particular puzzle that I hope will be of use to someone else.

Technical Prose: Finding Solaris 11 NIC driver versions
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Programming

My NIC driver cannot send and recieve in parallel!

Hi, all: My writed NIC driver for rtl8139d adapter on linux 3.0.4 cannot send and recieve simultaneously but is able to send or recieve in parallel respectively. As soon as it send and recieve at the same time, the transmmition rate on both directions gradually decrease to zero b/s and report... (1 Reply)
Discussion started by: liklstar
1 Replies

2. Solaris

Packaging driver for NIC

Hi guys My friend needs nfo driver for his Solaris box. I installed that driver for myself from scratch and he needs that driver in SVR4 format. I downloaded source code and run make and this is the point I don't how to proceed. How can I recognize which needs go to the package ? Does make... (0 Replies)
Discussion started by: solaris_user
0 Replies

3. Solaris

x86 Solaris 10 nic driver added but not attached. NIC is not detected.

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

4. UNIX for Advanced & Expert Users

How does a NIC driver activate with upper layer mutually?

Hi, all: How can I know whether the packets recieved from network by my own NIC driver are transmitted to upper layer(IP layer) or not? How can I know if the packets come from upper layer are passed to my own NIC driver and go out further? Is there any shell command or utility show... (9 Replies)
Discussion started by: liklstar
9 Replies

5. Red Hat

How to verify the current NIC driver version installed in RHEL5.3??

Guys, Can you help me how to verify the current installed NIC driver version in RHEL5.3? Thanks.:D (1 Reply)
Discussion started by: shtobias
1 Replies

6. SCO

install NIC driver for Intel Pro 1000

hi I have a fresh installation of SCO 5.0.6 and I have download a NIC driver for Intel Pro 1000: ftp://ftp.sco.com/pub/openserver5/507/drivers/eeG_5.0.7g/VOL.000.000 Howto install it using floppy? ---------- Post updated at 04:02 PM ---------- Previous update was at 02:18 PM... (0 Replies)
Discussion started by: ccc
0 Replies

7. Solaris

After update Solaris version, HBA driver still need to install?

Hi all I had update a server from Solaris 8 to Solaris 10 is it the HBA driver still need to reinstall? since i can get the driver info as below: root@sgerpdev # fcinfo hba-port HBA Port WWN: 21000003ba9b58a3 OS Device Name: /dev/cfg/c1 Manufacturer: QLogic Corp. ... (1 Reply)
Discussion started by: SmartAntz
1 Replies

8. IP Networking

NIC driver guide

Hi I need to know how a driver for a network interface card works, I want to learn the basic principles since I know that every driver has its specific implementation. For example when we speak about the scheduler, we can read an operating system book and learn general design concepts e.g.... (0 Replies)
Discussion started by: Puntino
0 Replies

9. UNIX for Advanced & Expert Users

NIC Driver

Hi:- I am trying to install a device driver for Intel NIC card on TurboLinux, but getting following errors, cc -O -Wall -o eepro100-diag eepro100-diag.c eepro100-diag.c:72: unistd.h: No such file or directory eepro100-diag.c:73: stdio.h: No such file or directory eepro100-diag.c:74:... (1 Reply)
Discussion started by: s_aamir
1 Replies

10. UNIX for Dummies Questions & Answers

NIC driver building question

I'm way confused. I loaded RH 7.1 on an old P-75 Compaq. IT has an EtherExpress pro/100 card in it and I have that attached to the optional port on our firewall with a crossover....I can't seem to get the card to negotiate with the firewall...it's currently 100Meg at Half duplex. I'm at a loss... (3 Replies)
Discussion started by: kwalter
3 Replies
Login or Register to Ask a Question
ESHCONFIG(8)						    BSD System Manager's Manual 					      ESHCONFIG(8)

NAME
eshconfig -- configure Essential Communications' HIPPI network interface SYNOPSIS
eshconfig [-estx] [-b bytes] [-c bytes] [-d filename] [-i usecs] [-m bytes] [-r bytes] [-u filename] [-w bytes] [interface] DESCRIPTION
eshconfig is used to configure device-specific parameters and download new firmware to the Essential Communications RoadRunner-based HIPPI network interface. The interface is very sensitive to the DMA performance characteristics of the host, and so requires careful tuning to achieve reasonable performance. In addition, firmware is likely to change frequently, which necessitates a reasonably easy way to update that firmware. Available operands for eshconfig: -b bytes Adjust the burst size for read (by NIC of host memory) DMA. -c bytes Adjust the burst size for write (by NIC of host memory) DMA. -d filename Filename for file to download into NIC firmware. This must be a file in the standard Essential format, with :04 preceding every line, and a tag line at the end indicating the characteristics of the firmware file. -e Write data to EEPROM. Normally, setting tuning parameters will only persist until the system is rebooted. Setting this parameter ensures that the changes will be written to EEPROM. -i usecs Interrupt delay in microseconds. -m bytes Minimum number of bytes to DMA in one direction (read or write) before allowing a DMA in the other direction. Tuning this prevents one direction from dominating the flow of bytes, and artificially throttling the NIC. -r bytes Bytes before DMA starts for read (from host to NIC). This controls how soon the DMA is triggered; until this many bytes are requested, the DMA will not begin. -s Show statistics for the HIPPI NIC. Repeat the option to suppress non-zero statistics. -t Show current tuning parameters on the host. -u filename Name of file to which the NIC firmware should be uploaded. Not currently supported. -w bytes Number of bytes required before write (from NIC to host) DMA is started. Until this many bytes are ready to be written, the DMA will not start. -x Reset the NIC. This is necessary for the HIPPI-FP support, as ifconfig(8) will no longer physically reset the NIC when the inter- faces goes up and down. Only the super-user may modify the configuration of a network interface. DIAGNOSTICS
Messages indicating the specified interface does not exist or the user is not privileged and tried to alter an interface's configuration. SEE ALSO
esh(4), ifconfig(8) HISTORY
The eshconfig command first appeared in NetBSD 1.4. BSD
June 17, 2005 BSD