mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian May <bam@snoopy.apana.org.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.2and 8139too
Date: 16 Mar 2001 10:49:14 +1100	[thread overview]
Message-ID: <84u24ufv9h.fsf@snoopy.apana.org.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0103151527420.2382-100000@ve1drg.com>
In-Reply-To: <Pine.LNX.4.21.0103151527420.2382-100000@ve1drg.com>

>>>>> "Ted" == Ted Gervais <ve1drg@ve1drg.com> writes:

    Ted> A simple question for you guru's..  I just installed kernel
    Ted> 2.4.2 on a slackware system and have a problem with loading a
    Ted> module. It is the 8139too.o module previously the rtl8139.o.
    Ted> It seems that this new driver is not being loaded with this
    Ted> new kernel. Obviously something has changed but I can't seem
    Ted> to see where that is.  I noticed though that the directories
    Ted> in /lib/modules for this kernel is different than 2.2.18.

Sorry, this is not related to your problem...

However, I have just put a 8139 based card into my Linux 2.4.2
system. At one stage, these lines were logged:

Mar 15 09:42:56 snoopy kernel: eth0: Abnormal interrupt, status 00000020.
Mar 15 09:43:04 snoopy kernel: eth0: Abnormal interrupt, status 00002020.
Mar 15 10:06:52 snoopy kernel: eth0: Abnormal interrupt, status 00000020.
Mar 15 10:06:58 snoopy kernel: eth0: Abnormal interrupt, status 00002020.

The card seems to be reliable apart from these messages. It could be
that I was playing around with the network cable or something at the
time... However, any messages "Abnormal interrupt" make me slightly
nervous.

Anyway, further information:

Mar 14 16:10:22 snoopy kernel: 8139too Fast Ethernet driver 0.9.13 loaded
Mar 14 16:10:22 snoopy kernel: PCI: Found IRQ 12 for device 00:0a.0
Mar 14 16:10:22 snoopy kernel: eth0: RealTek RTL8139 Fast Ethernet at 0xc8800000, 00:48:54:1d:b2:85, IRQ 12
Mar 14 16:10:22 snoopy kernel: eth0:  Identified 8139 chip type 'RTL-8139C'

[...]

Mar 14 16:10:23 snoopy kernel: eth0: Setting full-duplex based on MII #32 link partner ability of 45e1.

(sorry if this problem has already been reported...)
-- 
Brian May <bam@snoopy.apana.org.au>

  parent reply	other threads:[~2001-03-15 23:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15 19:35 Kernel 2.4.2 Ted Gervais
2001-03-15 19:56 ` John Jasen
2001-03-15 21:40   ` Guennadi Liakhovetski
2001-03-15 23:49 ` Brian May [this message]
2001-03-16 13:06   ` Kernel 2.4.2and 8139too Jeff Garzik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=84u24ufv9h.fsf@snoopy.apana.org.au \
    --to=bam@snoopy.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®