Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This question is specifically for submitting a package in the Software Center.

If I wish to submit a package that contains a kernel module (*.ko) which will install in /lib/modules/ and there is a kernel update with a new patch level number, i.e. 3.2.0-, how will my package's module be handled as it will not be installed in the new /lib/modules/?

Is this something that I have to maintain myself maybe via a startup script/check and manually copy/install the *.ko file to the new kernel modules location?

share|improve this question

In general, kernel modules have to be built for the current kernel and not simply copied.

If you need a custom module, either file a bug report or consider building a custom kernel.

share|improve this answer
Well, this is my module that I had written and is needed by the application that accompanies it. I do agree, in most cases, on a kernel update, it should be rebuilt. Although the subsystem that this module resides in is rarely if at all touched in the majority of patch releases for a specific kernel tree. – pkoutoupis May 7 '13 at 14:32
Why not submit your module to ? Probably better then a .deb – bodhi.zazen May 7 '13 at 17:26
I have thought about it but they [ developers] work on a pretty fast and demanding pace, one that may be difficult for me to keep up with. Although it is worth another consideration. – pkoutoupis May 7 '13 at 18:48
Well, if your kernel module is as stable as you claim, the work should be minimal. – bodhi.zazen May 7 '13 at 18:52

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.