Question: Autonegotiation Failure from dmesg 

Forum: PCMCIA on Toshiba laptops
Date: 2000, Aug 31
From: Scott Monet obscue

When I insert the etherexpress pro100, or the xircom rem56G, I get the initialization "beep" followed by another similar beep. In dmesg it gives me an autonegotiation failure. Everything else seems OK. What to do?

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ 1 ] 

It isn't a problem Re: Question: Autonegotiation Failure from dmesg (Scott Monet) Date: 2000, Aug 31 From: David Hinds <dhinds@pcmcia.sourceforge.org>

When you say everything else seems OK, do you mean that the network works fine? An autonegotiation failure is not necessarily even an error. It means that whatever you are connected to did not autonegotiate the link speed (10baseT versus 100baseT) and duplex. This is normal if you are connected to a single-speed hub, for example. So, there is probably no reason to do anything. -- Dave

Question: No network Re: It isn't a problem (David Hinds) Date: 2000, Aug 31 From: Scott Monet obscue

When I go into the network host config and look for the module to associate with eth0, I can't find the corresponding module. For the Xircom it is xirc2ps_cs, but that's not an option. We are running a 10/100 network over TCP/IP. Is there more for me to load?

PCMCIA modules do not show up on that list Re: Question: No network (Scott Monet) Date: 2000, Aug 31 From: David Hinds <dhinds@pcmcia.sourceforge.org>

That field should be left blank: PCMCIA modules are always loaded automatically as needed. This is mentioned in the PCMCIA-HOWTO section for Red Hat. The right module was loaded correctly. -- Dave

[ Add Message ]  to: "Autonegotiation Failure from dmesg"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]