07-30-2001
re: problems with nic card
Andy/Neo,
Thanks for the direction. I know that my card is supported, and I'm sure those sites you sent me will help. I downloaded eepro100.diag.c and compiled it, but I don't know what to do with it now. Is there a specific directory it needs to be in? Simply keying in 'eepro100-diag' does nothing ('command not found')....I am WAY new to this....sorry. BTW, I ran the compile as recommended in the source, and received no errors, and eepro100.diag was created in the same directory.
Kevin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
2. IP Networking
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
3. SCO
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
4. Red Hat
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
5. UNIX for Advanced & Expert Users
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
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
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. UNIX for Advanced & Expert Users
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... (0 Replies)
Discussion started by: liklstar
0 Replies
9. Programming
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
10. Solaris
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
TL(4) BSD Kernel Interfaces Manual TL(4)
NAME
tl -- Texas Instruments ThunderLAN Ethernet device driver
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device miibus
device tl
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_tl_load="YES"
DESCRIPTION
The tl driver provides support for PCI Ethernet adapters based on the Texas Instruments ThunderLAN Ethernet controller chip.
The ThunderLAN controller has a standard MII interface that supports up to 32 physical interface devices (PHYs). It also has a built-in
10baseT PHY hardwired at MII address 31, which may be used in some 10Mbps-only hardware configurations. In 100Mbps configurations, a
National Semiconductor DP83840A or other MII-compliant PHY may be attached to the ThunderLAN's MII bus. If a DP83840A or equivalent is
available, the ThunderLAN chip can operate at either 100Mbps or 10Mbps in either half-duplex or full-duplex modes. The ThunderLAN's built-in
PHY and the DP83840A also support autonegotiation.
The tl driver supports the following media types:
autoselect Enable autoselection of the media type and options. Note that this option is only available on those PHYs that support
autonegotiation. Also, the PHY will not advertise those modes that have been explicitly disabled using the following
media options.
10baseT/UTP Set 10Mbps operation
100baseTX Set 100Mbps (Fast Ethernet) operation
10base5/AUI Enable AUI/BNC interface (useful only with the built-in PHY).
The tl driver supports the following media options:
full-duplex Force full duplex operation
half-duplex Force half duplex operation.
hw-loopback Enable hardware loopback mode.
Note that the 100baseTX media type is only available if supported by the PHY. For more information on configuring this device, see
ifconfig(8).
HARDWARE
The tl driver supports Texas Instruments ThunderLAN based Ethernet and Fast Ethernet adapters including a large number of Compaq PCI Ethernet
adapters. Also supported are:
o Olicom OC-2135/2138 10/100 TX UTP adapter
o Olicom OC-2325/OC-2326 10/100 TX UTP adapter
o Racore 8148 10baseT/100baseTX/100baseFX adapter
o Racore 8165 10/100baseTX adapter
The tl driver also supports the built-in Ethernet adapters of various Compaq Prosignia servers and Compaq Deskpro desktop machines including:
o Compaq Netelligent 10
o Compaq Netelligent 10 T PCI UTP/Coax
o Compaq Netelligent 10/100
o Compaq Netelligent 10/100 Dual-Port
o Compaq Netelligent 10/100 Proliant
o Compaq Netelligent 10/100 TX Embedded UTP
o Compaq Netelligent 10/100 TX UTP
o Compaq NetFlex 3P
o Compaq NetFlex 3P Integrated
o Compaq NetFlex 3P w/BNC
DIAGNOSTICS
tl%d: couldn't map memory A fatal initialization error has occurred.
tl%d: couldn't map interrupt A fatal initialization error has occurred.
tl%d: device timeout The device has stopped responding to the network, or there is a problem with the network connection (cable).
tl%d: no memory for rx list The driver failed to allocate an mbuf for the receiver ring.
tl%d: no memory for tx list The driver failed to allocate an mbuf for the transmitter ring when allocating a pad buffer or collapsing an
mbuf chain into a cluster.
SEE ALSO
arp(4), miibus(4), netintro(4), ng_ether(4), ifconfig(8)
HISTORY
The tl device driver first appeared in FreeBSD 2.2.
AUTHORS
The tl driver was written by Bill Paul <wpaul@ctr.columbia.edu>.
BSD
July 16, 2005 BSD