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

[Robbie Dinn]

Donald Becker wrote:
>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?

This is SuSE 8.0 distribution, right?
I use this too.

Could it be that John Sved forgot to run the mk_initrd shell
script? Note the underscore between the 'k' and 'i'.
I think this recreates the /boot/initrd and /boot/initrd.suse
ramdisk images based on what has been assigned to the
INITRD_MODULES config value.

I think you need to run lilo as well if the ramdisk images
change.

I make this mistake often.

----------
From:  Donald Becker
Sent:  18 June 2002 16:43
To:  Robbie Dinn; john sved
Cc:  forum eepro100
Subject:  Re: [eepro100] Twin laptops - one good NIC configuration - one bad


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

_______________________________________________
eepro100 mailing list
eepro100@scyld.com
http://www.scyld.com/mailman/listinfo/eepro100

<<< ====================  Original Email Header  ==================== >>>

Delivered-To: dial.pipex.com-microbus@dial.pipex.com
Return-Path: <eepro100-admin@scyld.com>
X-Envelope-To: microbus@dial.pipex.com
X-Envelope-From: eepro100-admin@scyld.com
X-Delivery-Time: 1024433954
Received: (qmail 16722 invoked from network); 18 Jun 2002 20:59:14 -0000
Received: from gatun.mail.pipex.net (158.43.192.45)
  by firestorm.mail.pipex.net with SMTP; 18 Jun 2002 20:59:14 -0000
Received: (qmail 19598 invoked from network); 18 Jun 2002 20:59:42 -0000
Received: from hub.mail.gxn.net (195.147.246.56)
  by depot-6.dial.pipex.com with SMTP; 18 Jun 2002 20:59:42 -0000
Received: from dsl093-058-083.blt1.dsl.speakeasy.net ([66.93.58.83] helo=blueraja.scyld.com)
	by hub.mail.gxn.net with esmtp (Exim 3.34 #3)
	id 17KQ3W-00029T-00
	for robbie@microbus.co.uk; Tue, 18 Jun 2002 21:58:26 +0100
Received: from dsl093-058-083.blt1.dsl.speakeasy.net (localhost.localdomain [127.0.0.1])
	by blueraja.scyld.com (8.11.6/8.11.6) with ESMTP id g5IKu4O24412;
	Tue, 18 Jun 2002 16:56:04 -0400
Received: from localhost.localdomain (dsl093-058-082.blt1.dsl.speakeasy.net [66.93.58.82])
	by blueraja.scyld.com (8.11.6/8.11.6) with ESMTP id g5IKhGO23996
	for <eepro100@scyld.com>; Tue, 18 Jun 2002 16:43:16 -0400
Received: from localhost (becker@localhost)
	by localhost.localdomain (8.9.3/8.8.7) with ESMTP id QAA06363;
	Tue, 18 Jun 2002 16:43:08 -0400
From: Donald Becker <becker@scyld.com>
X-X-Sender:  <becker@presario>
To: John Sved <johnsved@compuserve.com>
cc: forum eepro100 <eepro100@scyld.com>
Subject: Re: [eepro100] Twin laptops - one good NIC configuration - one bad
In-Reply-To: <3D0F89FB.5040002@compuserve.com>
Message-ID: <Pine.LNX.4.33.0206181639240.22269-100000@presario>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: eepro100-admin@scyld.com
Errors-To: eepro100-admin@scyld.com
X-BeenThere: eepro100@scyld.com
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:eepro100-request@scyld.com?subject=help>
List-Post: <mailto:eepro100@scyld.com>
List-Subscribe: <http://www.scyld.com/mailman/listinfo/eepro100>,
	<mailto:eepro100-request@scyld.com?subject=subscribe>
List-Id: Linux driver development for the Intel PCI/CardBus EEPro 100 <eepro100.scyld.com>
List-Unsubscribe: <http://www.scyld.com/mailman/listinfo/eepro100>,
	<mailto:eepro100-request@scyld.com?subject=unsubscribe>
List-Archive: <http://www.scyld.com/pipermail/eepro100/>
X-Original-Date: Tue, 18 Jun 2002 16:43:08 -0400 (EDT)
Date: Tue, 18 Jun 2002 16:43:08 -0400 (EDT)



----------
robbie@microbus.co.uk