The Lan card in one of our UIII WS's seem doesn't work,so with ping command i can not see any of the machines in LAN and with some other tests i'm sure it's not OK.
I tried to use the second card on PCI port ,but the replaced card was one of the ordinary card for PC's ...by the way after... (1 Reply)
Dear all
Im facing one problem in SCO 5.0.5 , its that in the server there are three LAN cards INTEL PRO 100 series but when we configure all the three cards then LAN stops working . self ping is possible but no one can ping the server. If we remove driver of any one card LAN starts working.
Is... (1 Reply)
hi all
i have installed SCO 5.0.5 on a "Netfinity 5000" IBM server. But the OS is not detecting the lan card. how can i detect it.... help and thanks in advance .
bidhayak (3 Replies)
Hi,
I've recently moved my pci LAN card from Slot2 Slot5 on my sun x4270_m2 server (solaris 10).
I've done the touch / reconfigure and devfsadm, however my issue is that im able to configure the e1000g7 port with an ip address (192.168.0.1) but if i plug my laptop (set with static ip... (7 Replies)
we have red hat 6 linux box
There are two lan card
one lan card eth0 have ip 10.82.190.31/24 GW 10.82.190.254
2th lan card eth1 have ip 10.82.188.33/24 GW 10.82.188.254
I have below route ... I use two route table
root@xxx# netstat -rn
Kernel IP routing table
Destination Gateway ... (5 Replies)
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
LEARN ABOUT NETBSD
de
DE(4) BSD Kernel Interfaces Manual DE(4)NAME
de -- DECchip 21040, 21140, 21141, 21142, and 21143 PCI Ethernet interface driver
SYNOPSIS
de* at pci? dev ? function ?
Configuration of PHYs may also be necessary. See mii(4).
DESCRIPTION
The de driver supports Ethernet and Fast Ethernet interfaces based on the Digital Equipment Corporation DECchip 21040, 21140, 21141, 21142,
and 21143 model controllers for PCI bus.
21040 10BASE-T and AUI/BNC
21140 10BASE-T and 100BASE-TX
21141 10BASE-T and 100BASE-TX
21142 10BASE-T and 100BASE-TX
21143 10BASE-T and 100BASE-TX
Supported Network Interface Cards (NIC) include, but are not limited to:
Accton EN1207i
Cogent EM100
Asante AsanteFAST
DEC DE435
DEC DE450
DEC DE500
SMC 9332
Znyx NetBlaster ZX340 series (345, 348, 346)
Generally, if the NIC is for PCI bus, and the major controller chip has the DIGITAL logo on it, with one of the model numbers above, the de
driver should recognize and control it. Beware, however, that many NIC manufacturers change the Ethernet controller chip without changing
the product model number, and a physical inspection of the NIC, or a probe of the NIC with a PCI diagnostic tool is the only way to tell if a
real DEC TULIP controller is present.
Multi-port interfaces are typically configured as a PCI-PCI bridge with multiple de instances on the PCI bus on the other side of the bridge.
DEC sold its semiconductor division to Intel. In addition, there are many "knock-offs" of the DEC TULIP Ethernet controller chips; NICs
based on these chips are handled by the tlp(4) driver.
This de driver should not be confused with the NetBSD VAX de driver for the DEC DEUNA/DELUA Ethernet controller for UniBus.
SEE ALSO ifmedia(4), intro(4), mii(4), pci(4), tlp(4), ifconfig(8)
http://www.adaptec.com/, http://www.asante.com/, http://www.smc.com/, http://www.znyx.com/
HISTORY
The de driver first appeared in NetBSD 1.1
AUTHORS
Matt Thomas <matt@3am-software.com>.
BSD February 11, 2000 BSD