Hello list,

I installed VirtualBox (2.0.6, PUEL RPM) on my OpenSuSE 11.0 laptop. I
use a BuildService kernel (kernel-pae-2.6.27.4-3.1) instead of the
default one -- I need it to support the latest Intel chipset in my brand
new Dell E6500.

Compilation of the vboxdrv kernel module is successful, but the module
then refuses to load with the following message:

"vboxdrv: disagrees about version of symbol struct_module"

The headers for that specific kernel version were not provided on the
BuildService, so what I did is the following:

- get the matching kernel sources from kernel.org
- copy the .config provided by the BuildService kernel into the kernel
source tree
- rebuild the kernel + all modules. Build was successful.
- based on the log it produces, the vboxdrv module compilation process
clearly uses this compiled source tree for its headers (which is what I
wanted).

Any idea why it doesn't work ?

TIA

Ph. A.

-- 

*Philippe Andersson*
Unix System Administrator
IBA Particle Therapy |
Tel: +32-10-475.983
Fax: +32-10-487.707
eMail: [EMAIL PROTECTED]
<http://www.iba-worldwide.com>


The contents of this e-mail message and any attachments are intended solely for 
the recipient (s) named above. This communication is intended to be and to 
remain confidential and may be protected by intellectual property rights. Any 
use of the information contained herein (including but not limited to, total or 
partial reproduction, communication or distribution of any form) by persons 
other than the designated recipient(s) is prohibited. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. E-mail transmission cannot be guaranteed to be 
secure or error-free. Ion Beam Applications does not accept liability for any 
such errors. Thank you for your cooperation.

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users

Reply via email to