FS#10607 - Error inserting vboxadd and vboxvfs.
Attached to Project:
Community Packages
Opened by X (xeonic) - Sunday, 08 June 2008, 08:00 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 16 July 2008, 07:47 GMT
Opened by X (xeonic) - Sunday, 08 June 2008, 08:00 GMT
Last edited by Roman Kyrylych (Romashka) - Wednesday, 16 July 2008, 07:47 GMT
|
Details
Description:
When I try to insert vboxadd or vboxvfs I get an error. The same with vboxvfs Additional info: # dmesg | tail -1 - the most interesting line No module found in object # pacman -Qs Virtualbox kernel26 | grep local local/virtualbox-modules 1.6.2-2 local/virtualbox-ose 1.6.2-1 local/virtualbox-ose-additions 1.6.2-1 local/virtualbox-ose-additions-modules 1.6.2-2 local/kernel26 2.6.25.4-1 (base) Steps to reproduce: # modprobe vboxadd FATAL: Error inserting vboxadd (/lib/modules/2.6.25-ARCH/misc/vboxadd.ko): Invalid module format or # modprobe vboxvfs WARNING: Error inserting vboxadd (/lib/modules/2.6.25-ARCH/misc/vboxadd.ko): Invalid module format FATAL: Error inserting vboxvfs (/lib/modules/2.6.25-ARCH/misc/vboxvfs.ko): Invalid module format |
This task depends upon
# modprobe vboxadd
FATAL: Error inserting vboxadd (/lib/modules/2.6.25-ARCH/misc/vboxadd.ko): No such device
# dmesg | tail -n 1
vboxadd: VirtualBox PCI device not found.
I'm trying to solve it
Regards
André
FATAL: Error inserting vboxadd (/lib/modules/2.6.25-ARCH/misc/vboxadd.ko): Invalid module format
Dmesg shows:
"No module found in object"
http://forums.virtualbox.org/viewtopic.php?t=7152
Maybe you could also report it on their bug tracker if they have one?
Anyway, thanks to bash and darose for having tried to investigate this issue even if it hasn't been solved yet :)
I think bash mentioned at one point that he had opened a bug at their site about this, but I don't know the #, and wasn't able to find it in a search. Can you confirm this, bash?
Problem with opening a bug report on their site is: I'm not sure if it's their bug or ours.
Maybe 2.6.25 is not widely used yet, and that is why that issue hasn't been noticed somewhere else?
I don't know.
I'm going to try downgrading my kernel & kernel-headers to test this theory.
I'll see if I can downgrade a bunch of things. If not, then I'll have to create a new guest OS with an earlier kernel. Feh.
Perhaps the mismatch of kernel and kernel-headers versions is responsible now? I don't know. I didn't seem to have kernel2.6.24.3 in my cache to test with though.
If anyone's got earlier stuff in their cache and want to give this a shot, be my guest. I don't think there's any more back testing I can do.
I tried to build and use vboxadd module that are in VBoxLinuxAdditions.run but I get the same error.
Very thanks to darose for your effort.
So then ... what's different between what that install program is doing and what we're doing? And/or what's different between what the PUEL version of the additions is doing and what the OSE version of the additions is doing?
# modprobe vboxadd
FATAL: Error inserting vboxadd
(/lib/modules/2.6.25-ARCH/kernel/drivers/misc/vboxadd.ko): No such
device
# dmesg | tail -n 1
vboxadd: VirtualBox PCI device not found.
but still don't work
Trying to get the xorg driver stuff setup correctly right now so that I can test this all out together to see if the mouse integration works properly.
finally I think this can be closed
for get mouse and video modules you must install virtualbox-ose-xorg-drivers
very thanks for your grants David
[af@andre ~]$ sudo modprobe vboxadd
Adgangskode:
FATAL: Error inserting vboxadd (/lib/modules/2.6.25-ARCH/misc/vboxadd.ko): No such device
You can say that it does not work for YOU, in this case at least give some details about your system, architecture, whatever...
I was getting that too, but found a way to solve it. The cause for me was that I was that the guest additions inside the guest were v1.6.2, while the actual virtual box software I was running on the host (Windows) was 1.5.x. Once I upgraded the software on the Windows host to 1.6.2, all was fine.
Not sure if this is the cause of you guys' problems, but it fixed it for me.
So I also have a windows host at 1.6.2
virtualbox-modules 1.6.2-2
virtualbox-ose 1.6.2-1
virtualbox-ose-additions 1.6.2-1
virtualbox-ose-additions-modules 1.6.2-5
virtualbox-ose-xorg-drivers 1.6.2-2
kernel26 2.6.25.6-1
Are you trying to say you use both an uptodate Arch Linux system as host and as guest?
Please try to be clearer.