Re: Size of a kernel module is different at build place and after installation
sobtwmxt wrote: I have built a custom kernel, using make-kpgk, from debian source. Using ls -l, there is difference in the size of kernel modules, .ko files, at build place and after installation of the package. I only looked at 2 unrelated modules, but I think there will be a difference in the size of other modules too. If that matters, I built the package on one machine, and installed it on another. The later machine is an x86 running Ubuntu. The former is x86 running Debian. 1) Why there is size difference? are you using the same filesystem on both (i.e. ext3)? 2) Can I compile modules on the Debian machine and copy the resulted .ko files directly to the Ubuntu machine? yes regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Size of a kernel module is different at build place and after installation
Emanoil Kotsev deloptes at yahoo.com writes: are you using the same filesystem on both (i.e. ext3)? It is ext3 on both. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Size of a kernel module is different at build place and after installation
sobtwmxt wrote: Emanoil Kotsev deloptes at yahoo.com writes: are you using the same filesystem on both (i.e. ext3)? It is ext3 on both. then may be the disks are different type? do on both machines as root fdisk -l /dev/disk i.e. fdisk -l /dev/sda Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x23f12d67 Device Boot Start End Blocks Id System /dev/sda1 * 1 17 136521 83 Linux /dev/sda2 18972978011640 83 Linux -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Size of a kernel module is different at build place and after installation
Hi, Does the install software strip extra symbols from the driver? $ ls -l /lib/modules/2.6.31/kernel/drivers/video/nvidia.ko -rw-r--r-- 1 root root 9.2M 2009-09-13 03:59 /lib/modules/2.6.31/kernel/drivers/video/nvidia.ko $ strip nvidia.ko $ ls -l nvidia.ko -rw-r--r-- 1 war users 7.9M 2009-09-22 10:45 nvidia.ko Justin. On Tue, 22 Sep 2009, Emanoil Kotsev wrote: sobtwmxt wrote: Emanoil Kotsev deloptes at yahoo.com writes: are you using the same filesystem on both (i.e. ext3)? It is ext3 on both. then may be the disks are different type? do on both machines as root fdisk -l /dev/disk i.e. fdisk -l /dev/sda Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x23f12d67 Device Boot Start End Blocks Id System /dev/sda1 * 1 17 136521 83 Linux /dev/sda2 18972978011640 83 Linux -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Size of a kernel module is different at build place and after installation
On Mon, Sep 21 2009, sobtwmxt wrote: I have built a custom kernel, using make-kpgk, from debian source. Using ls -l, there is difference in the size of kernel modules, .ko files, at build place and after installation of the package. I only looked at 2 unrelated modules, but I think there will be a difference in the size of other modules too. If that matters, I built the package on one machine, and installed it on another. The later machine is an x86 running Ubuntu. The former is x86 running Debian. 1) Why there is size difference? As mentioned in another post in this thread, the installed modules are stripped of debugging information. make-kpkg can now create a linux-debug-** package that has detached debug information, to be used for debugging, as needed. manoj -- If it has syntax, it isn't user friendly. Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Size of a kernel module is different at build place and after installation
Manoj Srivastava srivasta at ieee.org writes: As mentioned in another post in this thread, the installed modules are stripped of debugging information. make-kpkg can now create a linux-debug-** package that has detached debug information, to be used for debugging, as needed. manoj File says the modules are not stripped. The custom kernel package was created by kernel-package 12.020. I still wonder what makes the installed modules from a custom kernel deb differ (less) in size, when compared to the modules that used to build the deb. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Size of a kernel module is different at build place and after installation
On Tue, Sep 22 2009, sobtwmxt wrote: Manoj Srivastava srivasta at ieee.org writes: As mentioned in another post in this thread, the installed modules are stripped of debugging information. make-kpkg can now create a linux-debug-** package that has detached debug information, to be used for debugging, as needed. manoj File says the modules are not stripped. The custom kernel package was created by kernel-package 12.020. I still wonder what makes the installed modules from a custom kernel deb differ (less) in size, when compared to the modules that used to build the deb. $(MAKE) $(EXTRAV_ARG) INSTALL_MOD_PATH=$(INSTALL_MOD_PATH) \ INSTALL_FW_PATH=$(INSTALL_MOD_PATH)/lib/firmware/$(KERNELRELEASE) \ $(CROSS_ARG) ARCH=$(KERNEL_ARCH) INSTALL_MOD_STRIP=1 modules_install I suppose INSTALL_MOD_STRIP=1 has some effect? # # INSTALL_MOD_STRIP, if defined, will cause modules to be # stripped after they are installed. If INSTALL_MOD_STRIP is '1', then # the default option --strip-debug will be used. Otherwise, # INSTALL_MOD_STRIP will used as the options to the strip command. manoj -- One planet is all you get. Manoj Srivastava sriva...@acm.org http://www.golden-gryphon.com/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Size of a kernel module is different at build place and after installation
I have built a custom kernel, using make-kpgk, from debian source. Using ls -l, there is difference in the size of kernel modules, .ko files, at build place and after installation of the package. I only looked at 2 unrelated modules, but I think there will be a difference in the size of other modules too. If that matters, I built the package on one machine, and installed it on another. The later machine is an x86 running Ubuntu. The former is x86 running Debian. 1) Why there is size difference? 2) Can I compile modules on the Debian machine and copy the resulted .ko files directly to the Ubuntu machine? -- sobtw...@sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
