[eepro100] Twin laptops - one good NIC configuration - one bad

[Donald Becker]

On Tue, 18 Jun 2002, John Sved wrote:
> Donald Becker wrote:
>  > On Tue, 18 Jun 2002, John Sved wrote:
>  >
>  >>>>How can the e100 driver be removed ?
>  >>>>
>  >>>Delete the entry from /etc/modules.conf
>  >>>
>  >>I removed all occurances in /etc/modules.conf, saved and restarted.
>  >>
>  >>The e100 entry in the boot.msg still appears.  No change to the
>  >>indicated NIC status on the hub.
..
>  > Run 'lsmod'.  The driver e100 driver should show up.
> shows e100   69272 Used 1 as the last item in the list.

> In /etc/sysconfig/kernel
> there was
> INITRD_MODULES="e100"
> I set this to
> INITRD_MODULES=""

Hmmm, I don't know what else loads modules..  anyone else have an idea?

> Jun 17 12:18:51 john1 kernel: e100: eth0 NIC Link is Down
> Jun 17 12:18:55 john1 kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
> Jun 17 12:25:13 john1 kernel: e100: eth0 NIC Link is Down
> Jun 17 12:25:19 john1 kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
...
> The UP DOWN messages appear frequently.  Are they a cause of the Hub
> Link/Act LED flashing ?

They are a symptom of a serious link problem.  These messages are just a
report, not a cause.

> Is IRQ11 "overused" ?

...unrelated.  The transceiver handles autonegotiation
without needing the driver to deal with the timing.  The IRQ shouldn't
come into play

The best diagnostic is
   eepro100-diag --watch
or
   mii-diag --watch

-- 
Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Second Generation Beowulf Clusters
Annapolis MD 21403			410-990-9993