Sponsored Content
Special Forums Hardware My NIC driver didn't pass high pressure test! Post 302824247 by hicksd8 on Thursday 20th of June 2013 12:18:30 PM
Old 06-20-2013
One or both of the test systems doesn't happen to be Windows, does it?

Seeing bandwidth drop off down to almost nothing when transfering a very large amount of data is a known Windows problem.
 

9 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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

9. Solaris

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... (0 Replies)
Discussion started by: cambridge
0 Replies
ddi-forceattach(9P)					   Kernel Properties for Drivers				       ddi-forceattach(9P)

NAME
ddi-forceattach, ddi-no-autodetach - properties controlling driver attach/detach behavior DESCRIPTION
Solaris device drivers are attached by devfsadm(1M) and by the kernel in response to open(2) requests from applications. Drivers not cur- rently in use can be detached when the system experiences memory pressure. The ddi-forceattach and ddi-no-autodetach properties can be used to customize driver attach/detach behavior. The ddi-forceattach is an integer property, to be set globally by means of the driver.conf(4) file. Drivers with this property set to 1 are loaded and attached to all possible instances during system startup. The driver will not be auto-detached due to system memory pressure. The ddi-no-autodetach is an integer property to be set globally by means of the driver.conf(4) file or created dynamically by the driver on a per-instance basis with ddi_prop_update_int(9F). When this property is set to 1, the kernel will not auto-detach driver due to system memory pressure. Note that ddi-forceattach implies ddi-no-autodetach. Setting either property to a non-integer value or an integer value not equal to 1 pro- duces undefined results. These properties do not prevent driver detaching in response to reconfiguration requests, such as executing com- mands cfgadm(1M), modunload(1M), rem_drv(1M), and update_drv(1M). SEE ALSO
driver.conf(4) Writing Device Drivers SunOS 5.11 18 May 2001 ddi-forceattach(9P)
All times are GMT -4. The time now is 08:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy