8139too problem in 2.2.18

8139too problem in 2.2.18

[John Covici]

Hi.  I have a RealTech 8139 Ethernet card and I am using kernel
2.2.18.  I tried to use the new driver 8139too as a module, but when
doing an insmod or modprobe on the module I got "symbol forparameter
debug not found".  There was nothing obvious in the module source, so
any assistance would be appreciated.



-- 
         John Covici
         covici@ccs.covici.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: 8139too problem in 2.2.18

[Arnaldo Carvalho de Melo]

Em Sat, Dec 16, 2000 at 06:31:28PM -0500, John Covici escreveu:
> Hi.  I have a RealTech 8139 Ethernet card and I am using kernel
> 2.2.18.  I tried to use the new driver 8139too as a module, but when
> doing an insmod or modprobe on the module I got "symbol forparameter
> debug not found".  There was nothing obvious in the module source, so
> any assistance would be appreciated.

known bug, try this patch (adjust it to 2.2.18 if needed):

diff -dur linux-2.4.0-test12-clean/drivers/net/8139too.c linux-2.4.0-test12-fixed/drivers/net/8139too.c
--- linux-2.4.0-test12-clean/drivers/net/8139too.c      Sun Dec 10 12:55:42 2000
+++ linux-2.4.0-test12-fixed/drivers/net/8139too.c      Sun Dec 10 14:45:20 2000
@@ -74,6 +74,8 @@

                Tobias Ringström - Rx interrupt status checking suggestion

+               Gerard Sharp - bug fix for MODULE_PARM
+
        Submitting bug reports:

                "rtl8139-diag -mmmaaavvveefN" output
@@ -536,7 +538,9 @@
 MODULE_DESCRIPTION ("RealTek RTL-8139 Fast Ethernet driver");
 MODULE_PARM (multicast_filter_limit, "i");
 MODULE_PARM (max_interrupt_work, "i");
+#ifdef RTL8139_DEBUG
 MODULE_PARM (debug, "i");
+#endif /*RTL8139_DEBUG*/
 MODULE_PARM (media, "1-" __MODULE_STRING(8) "i");

 static int read_eeprom (void *ioaddr, int location, int addr_len);
diff -dur linux-2.4.0-test12-clean/fs/ntfs/fs.c linux-2.4.0-test12-fixed/fs/ntfs/fs.c


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: 8139too problem in 2.2.18

[John Covici]

On Sat, 16 Dec 2000, Arnaldo Carvalho de Melo wrote:

Thanks much -- do I have to fix the 2.4.0-test12 aswell as I am
testing with that kernel?

-- 
         John Covici
         covici@ccs.covici.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: 8139too problem in 2.2.18

[Keith Owens]

On Sat, 16 Dec 2000 18:31:28 -0500 (EST), 
John Covici <covici@ccs.covici.com> wrote:
>Hi.  I have a RealTech 8139 Ethernet card and I am using kernel
>2.2.18.  I tried to use the new driver 8139too as a module, but when
>doing an insmod or modprobe on the module I got "symbol forparameter
>debug not found".  There was nothing obvious in the module source, so
>any assistance would be appreciated.

The module has MODULE_PARM(debug) but debug is not defined.  Strictly
speaking the module should be fixed by Alan Cox has asked for modutils
to only issue a warning instead of an error for this type of bug.
modutils 2.3.23 has just been released with this change.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: 8139too problem in 2.2.18

[Alan Cox]

> Hi.  I have a RealTech 8139 Ethernet card and I am using kernel
> 2.2.18.  I tried to use the new driver 8139too as a module, but when
> doing an insmod or modprobe on the module I got "symbol forparameter
> debug not found".  There was nothing obvious in the module source, so
> any assistance would be appreciated.

Use an older version of modutils
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/