Kernel 2.4.2

Kernel 2.4.2

[Ted Gervais]

A simple question for you guru's..

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

Anyways - to get things to work, I have put added this statement to the
top of my /etc/rc.d/rc.inet1 file:

insmod /usr/src/linux/drivers/net/8139too.o.

That seems to get things working but why should I do that.

By the way - I do have  'alias eth0 8139too.o'  in my /etc/modules.conf
file.

Any thoughts on where I might be going wrong. And I do have
'CONFIG_KMOD=y' in my kernel configuration..

---
Earth is a beta site. 
                
Ted Gervais <ve1drg@ve1drg.com>
44.135.34.201 linux.ve1drg.ampr.org

Re: Kernel 2.4.2

[John Jasen]

On Thu, 15 Mar 2001, Ted Gervais wrote:

> Anyways - to get things to work, I have put added this statement to the
> top of my /etc/rc.d/rc.inet1 file:
>
> insmod /usr/src/linux/drivers/net/8139too.o.

install a later version of modutils, as the /lib/modules directory tree
has changed between 2.2.x and 2.4.x

Re: Kernel 2.4.2

[Guennadi Liakhovetski]

I do have the latest version of modutils (at least, the one required by
Documentation/Changes - 2.4.2), but I still have to all the line add
path=/lib/modules/`uname -r`/kernel/* to /etc/modules.conf. 
ONLY then it works. At least it worked until yesterday... Yesterday I
found out that I can't use CD-ROM on one of the machines, and, in
particular, when I am trying to access it - together with ide.o,
iso9660.o, also get loaded lp.o, parport.o and parport-pc.o... with no
visible reason... But I am not sure if this should be associated with
modutils or whatever... Why did I need that line?

Thanks
Guennadi

On Thu, 15 Mar 2001, John Jasen wrote:

> On Thu, 15 Mar 2001, Ted Gervais wrote:
> 
> > Anyways - to get things to work, I have put added this statement to the
> > top of my /etc/rc.d/rc.inet1 file:
> >
> > insmod /usr/src/linux/drivers/net/8139too.o.
> 
> install a later version of modutils, as the /lib/modules directory tree
> has changed between 2.2.x and 2.4.x
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 

___

Dr. Guennadi V. Liakhovetski
Department of Applied Mathematics
University of Sheffield, U.K.
email: G.Liakhovetski@sheffield.ac.uk

Re: Kernel 2.4.2and 8139too

[Brian May]

>>>>> "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>

Re: Kernel 2.4.2and 8139too

[Jeff Garzik]

Brian May wrote:
> 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.

They are logged at the kernel debug level, but nobody seems to notice
this fact.  Oh well.  The messages are for debugging only and
informational.  They occur whenever an Rx or Tx error occurs.

The latest version of 8139too hides this message behind RTL8139_DEBUG.

	Jeff


-- 
Jeff Garzik       | May you have warm words on a cold evening,
Building 1024     | a full mooon on a dark night,
MandrakeSoft      | and a smooth road all the way to your door.