On Qua, 2016-03-30 at 00:19 +0100, Sérgio Basto wrote: > On Qua, 2016-03-23 at 03:11 +0000, Sérgio Basto wrote: > > > > Without updated ( VirtualBox-5.0.17-r106108-r106114.patch ), X > > started > > and 3D works but kernel ooops on boot. > > With last patch update (VirtualBox-5.0.17-r106108-r106114.patch), X > > not > > started but no kernel ooops on boot. > > This are the results of my tests ... > Hi, > After many tests and builds, I understood why X doesn't start. I > found > with help of original binaries and scripts, that vboxvideo.ko is > removed, that is true ? and after remove vboxvideo.ko, all went fine > , > 3D is working. > So this Xorg.0.log message: VBoxVideo(0): kernel driver found, not > loading ... UnloadModule: "vboxvideo", now makes sense.
Hello, in VBoxGuestAdditions_5.0.17-106140.iso, ./VBoxGuestAdditions- amd64.tar.bz2, file init/vboxadd-x11, line 423 we got : # Do not install if we can use the kernel driver. case `uname -r` in 1.* | 2.* | 3.[0-9].* | 3.10.* ) ;; * ) vboxvideo_src="" ;; esac So for kernels bigger than 3.11 (we are in 4.4), /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so is deleted and not vboxvideo.ko, sorry about my mistake in my previous email. Note that remove vboxvideo.ko and add modules/drivers/vboxvideo_drv.so also worked :-) . But yes, it is working even better ! Thanks for your good work ! > Best regards, -- Sérgio M. B. _______________________________________________ vbox-dev mailing list vbox-dev@virtualbox.org https://www.virtualbox.org/mailman/listinfo/vbox-dev
