Re: Twin laptops - one good NIC configuration - one bad

John Sved <[email protected]>
Newsgroups gmane.linux.drivers.eepro100.devel
Organization NSD limited
Message-ID <[email protected]>

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.
 >>
 >
 > When does the e100 driver message appear ?

 >
 > Run 'lsmod'.  The driver e100 driver should show up.

lsmod

shows e100   69272 Used 1 as the last item in the list.

 > If it doesn't, it might be built into the kernel.
 >
 >
 >
 >
In modules.conf

alias eth0 eepro100

appears at the end


In /etc/sysconfig/kernel
there was
INITRD_MODULES="e100"

I set this to

INITRD_MODULES=""

and rebooted
this had no apparent effect
the boot up on screen message ((from /var/boot.msg) still says

<5>Intel(R) PRO/100 Fast Ethernet Adapter - Loadable driver, ver 1.8.37
<5>Copyright (c) 2002 Intel Corporation
<5>
<5>eth0: Intel(R) 8255x-based Ethernet Adapter
<5>  Mem:0xfbfff000  IRQ:11  Speed:100 Mbps  Dx:Full
<5>  Hardware receive checksums enabled
<5>  cpu cycle saver enabled

During the boot up  the was also the message the e100 was loaded.


  From /var/log/messages


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:22:52 john1 ifup: Configuration 'ppp0' has STARTMODE=manual:
-> skipped
Jun 17 12:22:52 john1 ifup: 	As we are called from rcnetwork we do not set
it up, because
Jun 17 12:22:52 john1 ifup: 	it was not set up manually or by hotplug before.
Jun 17 12:23:02 john1 kernel: eth0: no IPv6 routers present
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
Jun 17 12:25:44 john1 kdm[854]: pam_unix2: session finished for user
root, service xdm


Jun 17 14:17:10 john1 kernel: e100: eth0 NIC Link is Down
Jun 17 14:17:12 john1 kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
Jun 17 14:17:14 john1 kernel: e100: eth0 NIC Link is Down
Jun 17 14:17:18 john1 kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex


Jun 17 14:17:24 john1 kernel: e100: eth0 NIC Link is Down
Jun 17 14:17:28 john1 kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
Jun 17 14:19:39 john1 smpppd[1187]: smpppd version 0.73 started
Jun 17 14:19:50 john1 ifup: Configuration 'ppp0' has STARTMODE=manual:
-> skipped
Jun 17 14:19:50 john1 ifup: 	As we are called from rcnetwork we do not set
it up, because
Jun 17 14:19:50 john1 ifup: 	it was not set up manually or by hotplug before.
Jun 17 14:21:03 john1 ifup: Configuration 'ppp0' has STARTMODE=manual:
-> skipped
Jun 17 14:21:03 john1 ifup: 	As we are called from rcnetwork we do not set
it up, because
Jun 17 14:21:03 john1 ifup: 	it was not set up manually or by hotplug before.
Jun 17 14:21:13 john1 kernel: eth0: no IPv6 routers present
Jun 17 14:21:32 john1 kernel: e100: eth0 NIC Link is Down
Jun 17 14:21:46 john1 kernel: e100: eth0 NIC Link is Up 100 Mbps Full duplex
Jun 17 14:22:12 john1 kernel: e100: eth0 NIC Link is Down


Jun 17 14:22:28 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 ?


Is IRQ11 "overused" ?

Dell No. 2 has eepro100 according to lsmod.

the /var/log/messages shows that eepro100 v1.09 is used  with eepro rev 
1.36.
a receiver lockup bug exists and -- enable work-around
plus addition information


First things first:  how the heck do we get rid of replace e100 with 
eepro100 ?



--JS
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.