On Tue, Feb 23, 2010 at 06:58:11PM +0200, Aioanei Rares wrote:
Yes, I am sure, and anyway, since I have virtualbox-ose as a service
to start at boot, it always checks if it has modules for the running
kernel and if not, the script does that. I have tried this with all
the kernels installed and
Michael Meskes wrote:
On Tue, Feb 23, 2010 at 06:58:11PM +0200, Aioanei Rares wrote:
Yes, I am sure, and anyway, since I have virtualbox-ose as a service
to start at boot, it always checks if it has modules for the running
kernel and if not, the script does that. I have tried this with all
On Wed, Feb 24, 2010 at 01:35:50PM +0200, Aioanei Rares wrote:
As long as you don't care giving us more information about which script shall
do what, what kind of output it genererates and why you are sure that the
modules are bein build accordingly there is simply no way for us to help you
Of
Michael Meskes wrote:
On Wed, Feb 24, 2010 at 01:35:50PM +0200, Aioanei Rares wrote:
As long as you don't care giving us more information about which script shall
do what, what kind of output it genererates and why you are sure that the
modules are bein build accordingly there is simply no
which translates that VirtualBox can't build a .ko for neither of my
installed kernels (2.6.30-1-amd64, 2.6.32-trunk-amd64,
2.6.33-rc8-00113-gf8b55f2) hence it's useless.
No, this only translates to you insmod'ing a module that does not fit into the
kernel you're running. There is no info
Michael Meskes wrote:
No, this only translates to you insmod'ing a module that does not fit into the
kernel you're running. There is no info whatsoever in your email about your
build process. Please rebuild your modules for your running kernel and try
again. Are you sure the headers you have
6 matches
Mail list logo
