Help: 2.4 -> 2.6 (test11,bk2) kernel module file size (due to debug options?)
Hi,
after installing (actually - creating a debian package for) 2.6.0-test11-bk2 I have this:
2.3M /boot 366M /lib/modules/2.6.0-test11-bk2 !!! 15k /usr/share/doc/kernel-image-2.6.0-test11-bk2
Almost all .ko files are >200k in size. What kernel setting is/can be responsible for this?
N.B. I'm compiling the test11 to test it on my hardware, so ATM I'm not too worried about size if debugging is made easier. But this is _quite_ a drastic size increase compared to 2.4.22, where most driver files were 10-40k in size.
.config attached. Compiled cleanly, with a couple warnings. I'll now test it on my laptop.
Thanks!
Signature · 6 lines
Jens Benecke - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Quoted 8 lines · Jens Benecke
after installing (actually - creating a debian package for) 2.6.0-test11-bk2 I have this:
2.3M /boot 366M /lib/modules/2.6.0-test11-bk2 !!! 15k /usr/share/doc/kernel-image-2.6.0-test11-bk2Almost all .ko files are >200k in size. What kernel setting is/can be responsible for this?
IIRC CONFIG_DEBUG_INFO
[...]
Quoted 1 line
.config attached.
Not here...
bye
Signature · 1 line
Jacek Kawa **Trust practically no-one... Except trustworthy people.** ['Jingo']
Quoted 8 lines · Jens Benecke
Hi,
after installing (actually - creating a debian package for) 2.6.0-test11-bk2 I have this:
2.3M /boot 366M /lib/modules/2.6.0-test11-bk2 !!! 15k /usr/share/doc/kernel-image-2.6.0-test11-bk2
you don't use "du -cahL" when counting /lib/modules/2.6.0-test11-bk2, don you? /lib/modules/2.6.0-test11-bk2/build is a symbolic link to your kernel sources, "-L" in "du" counts them too. (man du)
evil@sheep:~$ du -cahL /lib/modules/2.6.0-test11/ | tail -n1 422M total evil@sheep:~$ du -cah /lib/modules/2.6.0-test11/ | tail -n1 2.2M total
Christian.
Signature · 3 lines
BOFH excuse #265: The mouse escaped.