Discussion:
The module stripped can't be recognized by system
Sun Zongjun-E5739C
2006-10-27 03:58:36 UTC
Permalink
Hi, all

I stripped the ipv6.ko and insert it. System reports.

Ipv6: module has no symbols(stripped?)
Insmod: error inserting 'ipv6.ko': -1 Invalid module format

Why system doesno't allow me to strip kernel module? Or I use wrong
option??

Thanks
Regards
Sun Zongjun
Tel: 0086-10-65668962

-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Charlie Brady
2006-10-27 13:46:24 UTC
Permalink
Post by Sun Zongjun-E5739C
I stripped the ipv6.ko and insert it. System reports.
Ipv6: module has no symbols(stripped?)
Insmod: error inserting 'ipv6.ko': -1 Invalid module format
Why system doesno't allow me to strip kernel module?
The symbols are required for the module to be linked to the running
kernel.

Why do you want to strip the module?
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Auke Kok
2006-10-27 14:53:31 UTC
Permalink
Post by Sun Zongjun-E5739C
I stripped the ipv6.ko and insert it. System reports.
Ipv6: module has no symbols(stripped?)
Insmod: error inserting 'ipv6.ko': -1 Invalid module format
Why system doesno't allow me to strip kernel module?
The symbols are required for the module to be linked to the running kernel.
Why do you want to strip the module?
probably to make it smaller?

/*
-g -S -d --strip-debug Remove all debugging symbols & sections
--strip-unneeded Remove all symbols not needed by relocations
*/

try some of these flags to strip, and see if that works. The result will not be shocking:

$ ls -l e1000.ko
-rw-r--r-- 1 ahkok ahkok 139827 2006-10-27 07:49 e1000.ko
$ strip -g -S -d --strip-debug e1000.ko
$ ls -l e1000.ko
-rw-r--r-- 1 ahkok ahkok 139480 2006-10-27 07:50 e1000.ko

that wasn't really worth it :)


Auke
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Charlie Brady
2006-10-27 15:08:25 UTC
Permalink
Post by Auke Kok
Post by Charlie Brady
Why do you want to strip the module?
probably to make it smaller?
Disk is cheap.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Auke Kok
2006-10-27 15:25:51 UTC
Permalink
Post by Charlie Brady
Post by Auke Kok
Post by Charlie Brady
Why do you want to strip the module?
probably to make it smaller?
Disk is cheap.
but CF cards are not. If you're building a system based on something like that and want
to keep it minimal (say - booting a firewall from a 64mb flash chip), then space matters.

new kernels even accomodate this by allowing you to remove certain "core" features from
the kernel alltogether. Lets not tell all the embedded guys that they should just buy
bigger discs ok?

Auke
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Charlie Brady
2006-10-27 15:33:29 UTC
Permalink
...
Post by Auke Kok
Post by Charlie Brady
Disk is cheap.
but CF cards are not. If you're building a system based on something like
that and want to keep it minimal (say - booting a firewall from a 64mb flash
chip), then space matters.
Then don't use loadable modules.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Auke Kok
2006-10-27 15:44:42 UTC
Permalink
Post by Charlie Brady
...
Post by Auke Kok
Post by Charlie Brady
Disk is cheap.
but CF cards are not. If you're building a system based on something
like that and want to keep it minimal (say - booting a firewall from a
64mb flash chip), then space matters.
Then don't use loadable modules.
I actually strip kernel modules for my distro installer ISO - it autoloads modules based
on hardware detection. shaves off quite a bit and we need a whole bunch of modules
present for all those whacky scsi controllers, but we can't build them into the kernel
because loading an 18mb kernel is just not so nice, and we'd like the installer to also
run on older systems.

there are always good reasons for consuming less resources.

Auke
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Bernd Eckenfels
2006-10-27 18:03:46 UTC
Permalink
Post by Auke Kok
new kernels even accomodate this by allowing you to remove certain "core" features from
the kernel alltogether. Lets not tell all the embedded guys that they should just buy
bigger discs ok?
Another solution is to build static kernels for embedded usage :)

Gruss
Bernd
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Loading...