Some particular NICs can be driven by either de and tlp. It's my
understanding tlp has better support for newer NICs and is generally
better. Recently, Charles Hannum eliminated couple tlp bugs in support
for the older NICs, and the default has been switched so that tlp is
matched in preference to de.

Jaromir

Martti Kuparinen wrote:
> Hi!
> 
> I upgraded one host remotely and had to call someone to go to the console
> because the node didn't respond to ping. It turned out to be a problem
> with network device driver.
> 
> Before the reboot (1.5ZC from March 2002) we had these ethernet interfaces:
> 
> de0 at pci0 dev 14 function 0
> de0: interrupting at irq 11
> de0: ZNYX ZX312 21040 [10Mb/s] pass 2.3
> de0: address 00:c0:95:ec:28:c7
> de1 at pci0 dev 15 function 0
> de1: interrupting at irq 10
> de1: ZNYX ZX312 21040 [10Mb/s] pass 2.3
> de1: address 00:c0:95:ec:52:18
> 
> but after reboot (1.5ZC from today) they were detected as tlpN:
> 
> tlp0 at pci0 dev 14 function 0: DECchip 21040 Ethernet, pass 2.3
> tlp0: interrupting at irq 11
> tlp0: ZNYX ZX312, Ethernet address 00:c0:95:ec:28:c7
> tlp0: 10baseT, 10baseT-FDX, 10base5, manual
> tlp1 at pci0 dev 15 function 0: DECchip 21040 Ethernet, pass 2.3
> tlp1: interrupting at irq 10
> tlp1: ZNYX ZX312, Ethernet address 00:c0:95:ec:52:18
> tlp1: 10baseT, 10baseT-FDX, 10base5, manual
> 
> Any ideas why the driver was changed to tlp? Did I miss some "heads up"
> mail to warn about this?
> 
> Martti
> 
> ---
> Martti Kuparinen <martti.kuparinen@iki.fi>      NetBSD - No media hype
> http://www.iki.fi/kuparine/                     http://www.netbsd.org/
> 


-- 
Jaromir Dolecek <dolecek@ics.muni.cz>	http://www.ics.muni.cz/~dolecek/
-------------------------------------------------------------------------
It is better never to have been born.  But who among us has such luck?
One in a million, perhaps.