insmod problem after modutils upgrading
i've upgraded modutils from 2.3.14 (originally installed by RH7,kernel 2.2.16) to 2.3.22 using "rpm -Fvh modultils2.3.22-1.i386.rpm*" as required by the kernel 2.4test12 compilation. after upgrading, the network module refused to load anymore (was working fine with insmod 2.3.14) with kernel 2.2.16/RH7. during boot process, the following error message was shown:
insmod: /lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o insmod eth0 failed.
executing "insmod 8139too" at the command prompt shows the following error message:
using /lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o /lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o: symbol for parameter debug not found.
pls kindly advise if i've done something wrong during the upgrade or are there known compatibility issues with modutils 2.3.22?
how can i make insmod load the network module again pls?
thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
* Corisen schrieb am Donnerstag, 14.12.2000:
Quoted 7 lines
executing "insmod 8139too" at the command prompt shows the following error message:
using/lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o/lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o: symbol for parameter debug not found.how can i make insmod load the network module again pls?
I "fixed" the same problem in 2.2.18 by commenting out the line
MODULE_PARM (debug, "i");
near the end of drivers/net/8139too.c. Since I run modutils 2.3.22 as well, it can't be related to the modutils.
Signature · 7 lines
Christian Ullrich Registrierter Linux-User #125183 "Sie können nach R'ed'mond fliegen -- aber Sie werden sterben" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines
Quoted 1 line
how can i make insmod load the network module again pls?
I "fixed" the same problem in 2.2.18 by commenting out the line
MODULE_PARM(debug, "i");near the end of
drivers/net/8139too.c. Since I run modutils 2.3.22 as well, it can't be related to the modutils.
It is modutils. Their behaviour changed in a non back compatible way. Do not use modutils 2.3.22 with Linux 2.2.* is the simple answer. Perhaps Keith can make this a warning in 2.3.23
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 5 lines · Alan Cox
Quoted 5 lines
Quoted 2 lines
how can i make insmod load the network module again pls?
I "fixed" the same problem in 2.2.18 by commenting out the line
Quoted 8 lines
Quoted 4 lines
MODULE_PARM(debug, "i");near the end of
drivers/net/8139too.c. Since I run modutils 2.3.22 as well, it can't be related to the modutils.It is modutils. Their behaviour changed in a non back compatible way. Do not use modutils 2.3.22 with Linux 2.2.* is the simple answer. Perhaps Keith can make this a warning in 2.3.23
That, and/or allow "insmod -f" to load the module. '-f' has become pretty useless lately... :)
Jeff
Signature · 7 lines
Jeff Garzik | Building 1024 | These are not the J's you're lookin' for. MandrakeSoft | It's an old Jedi mind trick. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 3 lines · Alan Cox
It is modutils. Their behaviour changed in a non back compatible way. Do not use modutils 2.3.22 with Linux 2.2.* is the simple answer. Perhaps Keith can make this a warning in 2.3.23
Adding persistent module data to modutils meant that insmod had to be a lot more picky about MODULE_PARM() entries. There were a few modules that had invalid MODULE_PARM() entries, nobody had spotted them previously because nobody used those options. Since these are bugs in the modules and only a few modules are affected (less than 5 reported), the fix is to correct the modules that have coding errors.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 3 lines
previously because nobody used those options. Since these are bugs in the modules and only a few modules are affected (less than 5 reported), the fix is to correct the modules that have coding errors.
That wont be happening in 2.2 until 2.2.19 which probably means 6 months. If this is your decision please make it abundantly clear that the new modutils are a 2.4 only package.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 7 lines · Alan Cox
Quoted 3 lines
previously because nobody used those options. Since these are bugs in the modules and only a few modules are affected (less than 5 reported), the fix is to correct the modules that have coding errors.
That wont be happening in 2.2 until 2.2.19 which probably means 6 months. If this is your decision please make it abundantly clear that the new modutils are a 2.4 only package.
Well, if it is going to take that long to fix 2.2 ... modutils 2.3.23 will make this a semi-warning. modules with invalid MODULE_PARM for options that are not used will load, but the module will not support persistent data. If somebody actually tries to use one of the invalid options then insmod will fail, it already does this.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 1 line
Well, if it is going to take that long to fix 2.2 ... modutils 2.3.23
It may do. 2.2.18 took a long time.
Quoted 4 lines
will make this a semi-warning. modules with invalid
MODULE_PARMfor options that are not used will load, but the module will not support persistent data. If somebody actually tries to use one of the invalid options then insmod will fail, it already does this.
That sounds fine. Warning is sensible, not supporting persistent data is obvious enough and 2.2 doesnt do that yet so it isnt a problem.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 9 lines · Alan Cox
In-Reply-To: <[email protected]> from "Keith Owens" at Dec 14, 2000 0
***9:05:13 AMQuoted 3 lines
previously because nobody used those options. Since these are bugs in the modules and only a few modules are affected (less than 5 reported), the fix is to correct the modules that have coding errors.
That wont be happening in 2.2 until 2.2.19 which probably means 6 months. If this is your decision please make it abundantly clear that the new modutils are a 2.4 only package.
Why can't you make a fast 2.2.19 with _just_ safe bug fixes (as the fixing of these module problems certainly is)?
Signature · 8 lines
Dr. Horst H. von Brand mailto:[email protected] Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/
Quoted 2 lines
Why can't you make a fast 2.2.19 with _just_ safe bug fixes (as the fixing of these module problems certainly is)?
Shall I do a 2.2 release for every trivia. I think not.
There is plenty to get into 2.2.19 already
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/
Quoted 9 lines · Christian Ullrich
* Corisen schrieb am Donnerstag, 14.12.2000:
Quoted 5 lines
executing "insmod 8139too" at the command prompt shows the following error message:
using/lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o/lib/modules/2.4.0-test12/kernel/drivers/net/8139too.o: symbol for parameter debug not found.
Quoted 8 lines
Quoted 1 line
how can i make insmod load the network module again pls?
I "fixed" the same problem in 2.2.18 by commenting out the line
MODULE_PARM(debug, "i");near the end of
drivers/net/8139too.c. Since I run modutils 2.3.22 as well, it can't be related to the modutils.
Yep, that's the correct fix -- remove that line.
My apologies to Keith Owens for originally saying the opposite (I deal with so many net drivers they all get jumbled up in my mind)
Jeff
Signature · 7 lines
Jeff Garzik | Building 1024 | These are not the J's you're lookin' for. MandrakeSoft | It's an old Jedi mind trick. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] Please read the FAQ at http://www.tux.org/lkml/