depmod from busybox
Johannes Schwanzer
currently working on the integration of the closed source dvb drivers
from TBS.
During testing i found out that the "depmod" util from busybox does NOT
work like the "normal" depmod from the package "module-init-tools" !
When i create the /lib/modules/$(kernel-version)/modules.* files with
busybox-depmod then the whole TBS drivers dont work.
It only works when i use the "normal" depmod.
-> to be clear with this -> i am not talking about building the system
within openbricks. I am talking about executing depmod in a running
geexbox environment.
I would like to propose the use "normal" depmod and to put it in /sbin
instead of busybox-depmod.
BTW, and just for information i put the TBS drivers as a whole in a
seperate directory, not to override the original kernel modules and to
be able to add and remove this package without losing anything:
means i put it in /lib/modules/3.2.13/tbs
This is working great and i will send a patch for the TBs driver
support soon.
So please some feedback on the depmod issue... thanks.
Thomas Genty
> Hi guys,
>
> currently working on the integration of the closed source dvb drivers
> from TBS.
>
> During testing i found out that the "depmod" util from busybox does
> NOT work like the "normal" depmod from the package "module-init-tools" !
>
> When i create the /lib/modules/$(kernel-version)/modules.* files with
> busybox-depmod then the whole TBS drivers dont work.
> It only works when i use the "normal" depmod.
> -> to be clear with this -> i am not talking about building the system
> within openbricks. I am talking about executing depmod in a running
> geexbox environment.
>
> I would like to propose the use "normal" depmod and to put it in /sbin
> instead of busybox-depmod.
But where did you get "depmod" ? from modules-init-tools package ?
Or did you create a new package ?
>
> BTW, and just for information i put the TBS drivers as a whole in a
> seperate directory, not to override the original kernel modules and to
> be able to add and remove this package without losing anything:
> means i put it in /lib/modules/3.2.13/tbs
> This is working great and i will send a patch for the TBs driver
> support soon.
Do you have write access to push your commit ?
Ben ?
>
> So please some feedback on the depmod issue... thanks.
>
Tom
Johannes Schwanzer
Am 05.04.2012 21:12, schrieb Thomas Genty:
> Le 05/04/2012 20:01, Johannes Schwanzer a ï¿œcrit :
>> Hi guys,
>>
>> currently working on the integration of the closed source dvb drivers
>> from TBS.
>>
>> During testing i found out that the "depmod" util from busybox does
>> NOT work like the "normal" depmod from the package "module-init-tools" !
>>
>> When i create the /lib/modules/$(kernel-version)/modules.* files with
>> busybox-depmod then the whole TBS drivers dont work.
>> It only works when i use the "normal" depmod.
>> -> to be clear with this -> i am not talking about building the
>> system within openbricks. I am talking about executing depmod in a
>> running geexbox environment.
>>
>> I would like to propose the use "normal" depmod and to put it in
>> /sbin instead of busybox-depmod.
> Ok for me, if nobody else complains, do this :-)
> But where did you get "depmod" ? from modules-init-tools package ?
yes , but it is not installed in the iso, it is only for the toolschain.
so the modules-init-tools package maybe needs to be modified, so that
depmod is not only used for the toolchain but also installed to the
rootfs/iso.
Any idea for this? (busybox package also needs to be modified to not
install depmod)
Thomas Genty
>
>
> Am 05.04.2012 21:12, schrieb Thomas Genty:
>> Le 05/04/2012 20:01, Johannes Schwanzer a ï¿œcrit :
>>> Hi guys,
>>>
>>> currently working on the integration of the closed source dvb
>>> drivers from TBS.
>>>
>>> During testing i found out that the "depmod" util from busybox does
>>> NOT work like the "normal" depmod from the package
>>> "module-init-tools" !
>>>
>>> When i create the /lib/modules/$(kernel-version)/modules.* files
>>> with busybox-depmod then the whole TBS drivers dont work.
>>> It only works when i use the "normal" depmod.
>>> -> to be clear with this -> i am not talking about building the
>>> system within openbricks. I am talking about executing depmod in a
>>> running geexbox environment.
>>>
>>> I would like to propose the use "normal" depmod and to put it in
>>> /sbin instead of busybox-depmod.
>> Ok for me, if nobody else complains, do this :-)
>> But where did you get "depmod" ? from modules-init-tools package ?
> yes , but it is not installed in the iso, it is only for the toolschain.
> so the modules-init-tools package maybe needs to be modified, so that
> depmod is not only used for the toolchain but also installed to the
> rootfs/iso.
> Any idea for this? (busybox package also needs to be modified to not
> install depmod)
then create a new one for target
same as Python, one for toolchain, one for host
for busybox, just the config file to change
Tom
Johannes Schwanzer
Von meinem iPad gesendet
Am 05.04.2012 um 23:22 schrieb Thomas Genty <toml...@gmail.com>:
> Le 05/04/2012 21:51, Johannes Schwanzer a écrit :
>>
>>
>> Am 05.04.2012 21:12, schrieb Thomas Genty:
>>> Le 05/04/2012 20:01, Johannes Schwanzer a écrit :
>>>> Hi guys,
>>>>
>>>> currently working on the integration of the closed source dvb drivers from TBS.
>>>>
>>>> During testing i found out that the "depmod" util from busybox does NOT work like the "normal" depmod from the package "module-init-tools" !
>>>>
>>>> When i create the /lib/modules/$(kernel-version)/modules.* files with busybox-depmod then the whole TBS drivers dont work.
>>>> It only works when i use the "normal" depmod.
>>>> -> to be clear with this -> i am not talking about building the system within openbricks. I am talking about executing depmod in a running geexbox environment.
>>>>
>>>> I would like to propose the use "normal" depmod and to put it in /sbin instead of busybox-depmod.
>>> Ok for me, if nobody else complains, do this :-)
>>> But where did you get "depmod" ? from modules-init-tools package ?
>> yes , but it is not installed in the iso, it is only for the toolschain.
>> so the modules-init-tools package maybe needs to be modified, so that depmod is not only used for the toolchain but also installed to the rootfs/iso.
>> Any idea for this? (busybox package also needs to be modified to not install depmod)
> move module-init-tools to host-module-init-tools ? and 3 files to modify
> then create a new one for target
> same as Python, one for toolchain, one for host
> for busybox, just the config file to change
Not sure if i understand. Can you Show me?
Johannes Schwanzer
lsmod-good.txt -> output of lsmod after running (and reboot) the
"good" depmod from "modules-init-tools"
lsmod-bas.txt -> output of lsmod after running (and reboot) the
busybox's depmod
tbs-mods-good.tar -> the files depmod from "modules-init-tools"
created
tbs-mods-bad.tar -> the files depmod from busybox created
Tom can you verfiy this?
Just cp the "good" depmod to your geexbox installation or usb-stick...
... boot geexbox
rm /lib/modules/$(kernel-version)/modules.*
run the good or the bad depmod (bad one in /sbin/depmod)
reboot and compare...
Thomas Genty
> Attached the prove that busybox's depmod is not working well:
>
> lsmod-good.txt -> output of lsmod after running (and reboot) the
> "good" depmod from "modules-init-tools"
> lsmod-bas.txt -> output of lsmod after running (and reboot) the
> busybox's depmod
> tbs-mods-good.tar -> the files depmod from "modules-init-tools"
> created
> tbs-mods-bad.tar -> the files depmod from busybox created
>
> Tom can you verfiy this?
> Just cp the "good" depmod to your geexbox installation or usb-stick...
> ... boot geexbox
> rm /lib/modules/$(kernel-version)/modules.*
> run the good or the bad depmod (bad one in /sbin/depmod)
> reboot and compare...
and select module-init-tools in menuconfig
Tom
Thomas Genty
> Le 06/04/2012 09:37, Johannes Schwanzer a ï¿œcrit :
>> Attached the prove that busybox's depmod is not working well:
>>
>> lsmod-good.txt -> output of lsmod after running (and reboot) the
>> "good" depmod from "modules-init-tools"
>> lsmod-bas.txt -> output of lsmod after running (and reboot) the
>> busybox's depmod
>> tbs-mods-good.tar -> the files depmod from "modules-init-tools"
>> created
>> tbs-mods-bad.tar -> the files depmod from busybox created
>>
>> Tom can you verfiy this?
> arf, no , not build for x86-64 ...
>> Just cp the "good" depmod to your geexbox installation or usb-stick...
>> ... boot geexbox
>> rm /lib/modules/$(kernel-version)/modules.*
>> run the good or the bad depmod (bad one in /sbin/depmod)
>> reboot and compare...
> Please test the attached diff
> and select module-init-tools in menuconfig
>
> Tom
--- a/packages/busybox/config/busybox.conf Thu Apr 05 20:23:10 2012 +0200
+++ b/packages/busybox/config/busybox.conf Fri Apr 06 19:22:53 2012 +0200
@@ -488,7 +488,7 @@
CONFIG_FEATURE_LSMOD_PRETTY_2_6_OUTPUT=y
CONFIG_MODPROBE=y
CONFIG_FEATURE_MODPROBE_BLACKLIST=y
-CONFIG_DEPMOD=y
+# CONFIG_DEPMOD is not set
tom
Johannes Schwanzer
your patches for "busybox" and "module-init-tools" are working well.
plz apply your patches to the repo.
I send my tbs-drivers patch with next email.