Subject: Re: ex0 driver attaching to something not an ex0?
To: None <deichert@wrench.com>
From: maximum entropy <entropy@tappedin.com>
List: port-i386
Date: 01/15/2002 10:12:55
>Recebido-para: <entropy@tappedin.com>
>X-Authentication-Warning: inago.swcp.com: deichert owned process doing -bs
>Date: Tue, 15 Jan 2002 07:40:14 -0700 (MST)
>From: Diana Eichert <deichert@wrench.com>
>X-Sender: deichert@inago.swcp.com
>Content-Type: TEXT/PLAIN; charset=US-ASCII
>Sender: port-i386-owner@netbsd.org
>Precedence: list
>
>On Tue, 15 Jan 2002, Steven M. Bellovin wrote:
>
>> >--- Greywolf <greywolf@starwolf.com> wrote:
>> >> Greetings,
>> >> 
>> >> I have a dell-410 at work which has what the kernel
>> >> thinks is an ex
>> >> on board.  I'm not convinced it IS an ex for real,
>> >> because as soon
>> >> as I ifconfig the interface up, the lights go out.
>> >> 
>> >> ...is this a quirk?
>> >
>> 
>> I missed the original post.  However, I've had problems with the 
>> built-in 3c905b in my Dell Precision-410.  The fix is to specify the 
>> media type explicitly -- the fault is in the autonegotiation.
>
>My experience with Dells using this onboard NIC is the same.
>Autonegotiation didn't work, in fact one system I remember having to
>force it to 10Base2 even though it didn't have thinwire ethernet on
>it.  My suggestion try all the media options.

When I encountered this, no combination of media options would get the
card working.  My solution is in PR kern/13653.  Works fine with
autonegotiation, IIRC.  I no longer have access to that box.

Cheers,
entropy

--
entropy -- it's not just a good idea, it's the second law.