On Mon, Oct 21, 2002 at 07:29:03PM +0200, frederic.lafosse@eye-lab.net wrote:
> Hi
> 
> this is an onboard chip from a POS (Point Of Sale) integrated PC, a 
> JARLTECH 8100 with Pentium 200MMX and AT-style hardware in it. The 
> ethernet chip appears as a PCI device but I can't open that integrated box 
> to read the description on the chip itself.
> 
> For the first time as I'm a freebsd newbie, I have recompiled the kernel 
> and disable dc0 support. At reboot, de0 is used instead and can I manually 
> set the media to 10baseT/UTP and it works fine because de0 deals correctly 
> with 10BaseT and that ethernet hardware on a passive 10Mb/s HUB. It does 
> not work with autodetection on my CISCO catalyst switch. I think that DEC 

which cisco ? some have very broken MII negotiation.

> or Intel 31143 chip is kind of faulty at detecting the media type, as I can read 
> many bug report on many OSs related to it. And I'm not a specialist  of 
> MII and PHY interfaces matters.
> 
> The other media types do not work at all, particularily any 100Mb/s type 
> (note : neither with the Linux driver 'tulip.c' nor MS Win2K drivers, I've 
> already tried). 

So maybe you have a network issue too. Check cables. I've already seen
several cable work at 10Mbs but fail at 100Mbs.

> 
> With dc0 (freebsd 4.6.2) or tlp0(netbsd 1.6) none of the media type works. 
> does freebsd handle also a 'tlp' driver?

I don't think.

> 
> DMESG gives, with freebsd generic kernel (i.e defaulting to 'dc' driver, 
> so, identical to 'tlp' driver AFAIU)

dc and tlp are not the same, they have been written by different authors.

> 
> 
> dc0: <Intel 21143 10/100BaseTX> port 0xfc80-0xfcff mem 
> 0x7efbff80-0x7efbffff irq 11 at device 6.0 on pci0
> dc0: Ethernet address: 00:40:d0:04:01:07
> miibus0: <MII bus> on dc0
> ukphy0: <Generic IEEE 802.3u media interface> on miibus0
> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

I'd prefer a NetBSD dmesg, it gives more details about the PHY :)

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
--