> Found that in 2.4.6, Natsetmi card I have doesn't receive > traffic anymore. It worked in 2.4.5, though. > > The natsemi card is forced to 10/half via mii-diag at boot, > and given a different MAC address (due to some problems I had with > the original MAC address and netbooting a sparc). Forcing it to > 100/full didn't work, either. Could you try what happens without any special options? Default MAC address, without mii-diag. > Basic mode control register 0x2100: Auto-negotiation disabled, with > Speed fixed at 100 mbps, full-duplex. > [PC Linux 2.4.6] <--> p10/100 hub] <--> [SS4 NetBSD 1.5] > Speed fixed at 100 mbps, full-duplex. > I'm advertising 05e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT > Advertising no additional info pages. > IEEE 802.3 CSMA/CD protocol. > Link partner capability is 45e1: Flow-control 100baseTx-FD 100baseTx > 10baseT-FD. 10baseT. Negotiation completed. Something is wrong. Are you sure it's a hub? The link partner ability says FullDuplex capable, it's either a switch or the negotiation produced wrong results. The natsemi nic advertises 5e1, but the speed is fixed at 100 mbps. Probably a forced renegotiation after mii-diag changes is missing, and the forced settings aren't used properly. I'll look at it. -- Manfred - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: natsemi.c failure in 2.4.6
Studierende der Universitaet des Saarlandes Fri, 06 Jul 2001 03:35:27 -0700
- natsemi.c failure in 2.4.6 Daniel A. Nobuto
- Re: natsemi.c failure in ... Studierende der Universitaet des Saarlandes
- Re: natsemi.c failure... Daniel A. Nobuto
- Re: natsemi.c fai... Daniel A. Nobuto