Hi friends of suse,
I have a problem with my suse11.1 and virtualbox by SUN. 
On my notebook(Lenovo 300 N200) there run a Suse11.1. In SUNs VirtualBox there run a XP. Because I have have trouble with my internal webcam, I made a kernel-update (without success). Since this time, I can’t start the VirtualBox yet.
http://k26260.gmxhome.de/foto/Bildschirmfoto-VirtualBox - Fehler.png kein Link
short after this, there is another popup
http://k26260.gmxhome.de/foto/Bildschirmfoto-VirtualBox - Error In suplibOsInit.png kein Link
now I made the follow
linux:/home/norbert # /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module failed
(Look at /var/log/vbox-install.log to find out what went wrong)
linux:/home/norbert # cat /var/log/vbox-install.log
Makefile:172: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop.
but it isn’t possible (see the logfile). I don’t know what to do, because I’m a Newbeeee… coming from MS.
I have deinstalled vbox and reinstalled it, but the error is still…
Is there anybody can help me?
kind regards
Norbert
You need to go to a console and as root type:
/etc/init.d/vboxdrv setup
whenever you update the kernel when you use the SUN Vbox instead of the one in the repository. Have you done this?
See if you have installed kernel headers.
zypper install linux-kernel-headers
ist already installed…
linux:/home/norbert # zypper install linux-kernel-headers
Daten des Repositorys laden...
Installierte Pakete lesen...
'linux-kernel-headers' ist bereits installiert.
Paketabhängigkeiten auflösen...
Keine auszuführenden Aktionen.
linux:/home/norbert #
You said your kernel update was aborted. How did it happen? Was it from the online update? Can you see if you can complete that first?
sorry ( my error with the language…), the update was not successfully for the webcam :(.
The kernel-update for suse works properly,
I presume your kernel source matches the kernel you’ve got?
you mean this?
norbert@linux:~> rpm -qa | grep kernel
linux-kernel-headers-2.6.27-2.28
kernel-default-2.6.27.23-0.1.1
kernel-default-extra-2.6.27.23-0.1.1
kernel-default-base-2.6.27.23-0.1.1
norbert@linux:~>
there are different numbers. what should i have to do?
Norbert
Afaik the headers are fine (Don’t ask me) but you don’t have the source installed. Try
zypper in kernel-source or using yast, just make sure this adds up to your kernel I notice a couple of versions about on update you need .23
o.k.
norbert@linux:~> rpm -qa | grep kernel
linux-kernel-headers-2.6.27-2.28
kernel-source-2.6.27.23-0.1.1
kernel-default-2.6.27.23-0.1.1
kernel-default-extra-2.6.27.23-0.1.1
kernel-default-base-2.6.27.23-0.1.1
norbert@linux:~>
can I do something else to be able to run VirtualBox?
Now go back to the original command /etc/init.d/vboxdrv setup that should do it. If it doesn’t then I noticed a translated page do it as ./vboxdrv setup but I’ve not got a clue where from.
it doesn’t
norbert@linux:~> /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module done
Recompiling VirtualBox kernel module/etc/init.d/vboxdrv: line 272: /var/log/vbox-install.log: Permission denied
failed
(Look at /var/log/vbox-install.log to find out what went wrong)
norbert@linux:~> cat /var/log/vbox-install.log
Makefile:172: *** Error: unable to find the include directory for your current Linux kernel. Specify KERN_INCL=<directory> and run Make again. Stop.
norbert@linux:~> ./vboxdrv setup
bash: ./vboxdrv: Datei oder Verzeichnis nicht gefunden
norbert@linux:~>
good night
Norbert
Unless I’m mistaken you tried that as the normal user you can’t do it as a normal user you have to su first.
you are right. I do it as root, and it works. Great!
Special thanks to you.
peace an a long life
Norbert<:)
danduese adjusted his/her AFDB on Friday 19 Jun 2009 21:46 to write:
>
> FeatherMonkey;2001893 Wrote:
>> Now go back to the original command /etc/init.d/vboxdrv setup that
>> should do it. If it doesn’t then I noticed a translated page do it as
>> ./vboxdrv setup but I’ve not got a clue where from.
> it doesn’t
>
> Code:
> --------------------
> norbert@linux:~> /etc/init.d/vboxdrv setup
you need to be root, your command prompt shows a -> which means you are
still a user, if you were root it would end in a #.
HTH
–
Mark
Nullus in verba
Nil illegitimi carborundum