How to know whether the network driver alredy installed in my system

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat How to know whether the network driver alredy installed in my system
# 1  
Old 03-29-2009
How to know whether the network driver alredy installed in my system

I am using NVIDIA nforce: Networking controllers

And Redhat enterprice linux ws version 4 32 bit: OS

I want to connect my system to Broadband internet using linux.

From where can I download the driver for nertwork.

How to know whether the network driver alredy installed in my system.


Thanks
Rijas PA
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Programming

The simplest network driver

Hi, I am trying to write the simplest network driver that would send whatever through cable. My configuration is: Linux machine with some Intel network adapter Another machine with WireShark I connected Intel network adapter to second machine and want anything to pop up at wireshark. ... (12 Replies)
Discussion started by: Chrisdot
12 Replies

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

3. UNIX for Dummies Questions & Answers

Simulated driver for Network Interface Adapter

Hi all, I got sort of a task to do. I have to write in C "simulated network driver". What does it mean? - It has to run on all network adapters - It has to be as simple as it can be - It has to run on all linux distributions (or at least most of them) - It does not have to run a network... (4 Replies)
Discussion started by: Chrisdot
4 Replies

4. Solaris

Solaris 10 crashes upon boot after TUN driver installed

Hey! I compiled TUN 1.1 driver on my Solaris 10 64bit, and everything was working fine, all the commands for installation were successfull (add_drv, devfsadm -i tun ... etc.) and the driver was working fine as I got OpenVPN server up and running with successful clients attached. My only problem... (2 Replies)
Discussion started by: TomSu
2 Replies

5. AIX

how to know if my aix have multi-path driver installed?

I have an aix server, it is not a VIO server or client. I need to check if it has multi-path driver installed, how to check it? (1 Reply)
Discussion started by: rainbow_bean
1 Replies

6. Solaris

Can I Install the Gani Network Driver Using the Application that Came on the CD?

When I boot up the Solaris 10 5/09 install CD and select 'Solaris' from the GRUB menu that comes up, a menu loads. Option 5 is 'Apply Driver Updates'. Can I install the Gani driver using that? I tried using the tar file (the way it came) that I wrote to a floppy but when I asked it to look at the... (8 Replies)
Discussion started by: Bradj47
8 Replies

7. Solaris

Installing Network on Computer, might be driver

Hi All, Just completing my second Solaris installation, in the previous one which was on a Dell X64 machine, I went through the Network configuration setting, on the current computer which I am installing Solaris on, its a custom built machine and for some reason, I didnt see the screen where I... (1 Reply)
Discussion started by: platforminc
1 Replies

8. Solaris

network driver cpu usage

Hello all, Needed a suggestion from you all, if you know anything about this stuff. We have a high network traffic application. Close to around 700Meg /sec on one NIC. When the traffic is around 200Meg on the NIC, the VCPU(not the CPU, cause we have 24 VCPU) utilization by the NIC driver... (5 Replies)
Discussion started by: Naanu
5 Replies

9. Programming

Network device driver

HI, I am writing a network device driver for RTL8139c card on 2.6.18 kernel ... I am facing few queries listed below 1. Can i able to at all write a driver for RTL8139C or Realtek had designed new chip for 2.6 series kernel? 2. If no then which driver file 2.6.18 uses .. Is it 8139too.c or... (1 Reply)
Discussion started by: niketan
1 Replies
Login or Register to Ask a Question
NFE(4)							   BSD Kernel Interfaces Manual 						    NFE(4)

NAME
nfe -- NVIDIA nForce MCP Ethernet driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device miibus device nfe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_nfe_load="YES" DESCRIPTION
The nfe driver supports PCI Ethernet adapters based on the NVIDIA nForce Media and Communications Processors (MCP), such as the nForce, nForce 2, nForce 3, CK804, MCP04, MCP51, MCP55, MCP61, MCP65, MCP67, MCP73, MCP77 and MCP79 Ethernet controller chips. Supported features include (hardware support provided): o Receive/Transmit IP/TCP/UDP checksum offload o Hardware VLAN tag insertion/stripping o TCP segmentation offload (TSO) o MSI/MSI-X o Jumbo Frames Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. The nfe driver supports the following media types: autoselect Enable autoselection of the media type and options. 10baseT/UTP Set 10Mbps operation. 100baseTX Set 100Mbps (Fast Ethernet) operation. 1000baseT Set 1000Mbps (Gigabit Ethernet) operation (recent models only). The nfe driver supports the following media options: half-duplex Force half duplex operation. full-duplex Force full duplex operation. For more information on configuring this device, see ifconfig(8). HARDWARE
The nfe driver supports the following NVIDIA MCP onboard adapters: o NVIDIA nForce MCP Networking Adapter o NVIDIA nForce MCP04 Networking Adapter o NVIDIA nForce 430 MCP12 Networking Adapter o NVIDIA nForce 430 MCP13 Networking Adapter o NVIDIA nForce MCP51 Networking Adapter o NVIDIA nForce MCP55 Networking Adapter o NVIDIA nForce MCP61 Networking Adapter o NVIDIA nForce MCP65 Networking Adapter o NVIDIA nForce MCP67 Networking Adapter o NVIDIA nForce MCP73 Networking Adapter o NVIDIA nForce MCP77 Networking Adapter o NVIDIA nForce MCP79 Networking Adapter o NVIDIA nForce2 MCP2 Networking Adapter o NVIDIA nForce2 400 MCP4 Networking Adapter o NVIDIA nForce2 400 MCP5 Networking Adapter o NVIDIA nForce3 MCP3 Networking Adapter o NVIDIA nForce3 250 MCP6 Networking Adapter o NVIDIA nForce3 MCP7 Networking Adapter o NVIDIA nForce4 CK804 MCP8 Networking Adapter o NVIDIA nForce4 CK804 MCP9 Networking Adapter LOADER TUNABLES
Tunables can be set at the loader(8) prompt before booting the kernel or stored in loader.conf(5). hw.nfe.msi_disable Whether or not MSI support is enabled in the driver. The default value is 0. hw.nfe.msix_disable Whether or not MSI-X support is enabled in the driver. The default value is 0. SYSCTL VARIABLES
The following sysctl(8) variables can be used to modify or monitor nfe behavior. dev.nfe.%d.process_limit Maximum number of Rx events to be processed in the event loop before rescheduling a taskqueue. The accepted range is 50 to 255, the default value is 192. The interface does not need to be brought down and up again before a change takes effect. SEE ALSO
altq(4), arp(4), intro(4), miibus(4), netintro(4), pci(4), polling(4), rgephy(4), sysctl(8), ifconfig(8) HISTORY
The nfe device driver first appeared in OpenBSD 3.9, and then in FreeBSD 7.0. AUTHORS
The nfe driver was written by Jonathan Gray <jsg@openbsd.org> and Damien Bergamini <damien@openbsd.org>. The nfe driver was ported to FreeBSD by Shigeaki Tagashira <shigeaki@se.hiroshima-u.ac.jp>. BSD
January 15, 2011 BSD