Created attachment 397226 [details, diff] Adapted patch x11-drivers/xf86-video-virtualbox fails to build with kernel 3.18.7 I've found and applied a patch found here: http://anonscm.debian.org/cgit/pkg-virtualbox/virtualbox.git/commit/src/VBox/Additions/linux/drm/vboxvideo_drm.c?id=c923f4d32f4c80cf283dd3a53e109335a8e8d9f8 After that it compiles without error and works. I've attached the patch adapted for Gentoo.
Created attachment 397228 [details] adapted ebuild
Ok, it seems not to work 100 % But I'm really not a kernel developer I have this in my journal: Feb 22 16:02:45 touhami3 kernel: ------------[ cut here ]------------ Feb 22 16:02:45 touhami3 kernel: WARNING: CPU: 0 PID: 2942 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0xba/0x14b [drm]() Feb 22 16:02:45 touhami3 kernel: No drm_driver.set_busid() implementation provided by cleanup_module [vboxvideo]. Use drm_dev_set_unique() to set the unique name explicitly. Feb 22 16:02:45 touhami3 kernel: Modules linked in: Feb 22 16:02:45 touhami3 kernel: cfg80211 rfkill ppdev processor intel_agp battery snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_timer snd serio_raw pcspkr parport_pc parpo Feb 22 16:02:45 touhami3 kernel: CPU: 0 PID: 2942 Comm: X Tainted: G W O 3.18.7-gentoo #1 Feb 22 16:02:45 touhami3 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Feb 22 16:02:45 touhami3 kernel: 00000000 efd4de58 efd4de30 c0408de5 efd4de48 c0125f05 f8415022 00000000 Feb 22 16:02:45 touhami3 kernel: f5eda000 efd4deac efd4de60 c0125f42 00000009 efd4de58 f8430f98 efd4de74 Feb 22 16:02:45 touhami3 kernel: efd4de88 f8415022 f843100e 0000008f f8430f98 f8a9b0f8 efd4deac efd4deac Feb 22 16:02:45 touhami3 kernel: Call Trace: Feb 22 16:02:45 touhami3 kernel: [<c0408de5>] dump_stack+0x16/0x18 Feb 22 16:02:45 touhami3 kernel: [<c0125f05>] warn_slowpath_common+0x5a/0x71 Feb 22 16:02:45 touhami3 kernel: [<f8415022>] ? drm_setversion+0xba/0x14b [drm] Feb 22 16:02:45 touhami3 kernel: [<c0125f42>] warn_slowpath_fmt+0x26/0x2a Feb 22 16:02:45 touhami3 kernel: [<f8415022>] drm_setversion+0xba/0x14b [drm] Feb 22 16:02:45 touhami3 kernel: [<f8414f68>] ? drm_version+0x75/0x75 [drm] Feb 22 16:02:45 touhami3 kernel: [<f8414e17>] drm_ioctl+0x3b1/0x400 [drm] Feb 22 16:02:45 touhami3 kernel: [<f8414f68>] ? drm_version+0x75/0x75 [drm] Feb 22 16:02:45 touhami3 kernel: [<c0106407>] ? native_calibrate_tsc+0x324/0x439 Feb 22 16:02:45 touhami3 kernel: [<c0167ed7>] ? audit_filter_syscall+0x73/0x8b Feb 22 16:02:45 touhami3 kernel: [<c01c99b7>] ? dput+0x17/0xe3 Feb 22 16:02:45 touhami3 kernel: [<c01ce4b9>] ? mntput+0x24/0x26 Feb 22 16:02:45 touhami3 kernel: [<c016868b>] ? __audit_syscall_exit+0x1d6/0x1ed Feb 22 16:02:45 touhami3 kernel: [<c0168496>] ? __audit_syscall_entry+0x9f/0xbe Feb 22 16:02:45 touhami3 kernel: [<f8414a66>] ? drm_copy_field+0x4f/0x4f [drm] Feb 22 16:02:45 touhami3 kernel: [<c01c7158>] do_vfs_ioctl+0x337/0x3e6 Feb 22 16:02:45 touhami3 kernel: [<c0106407>] ? native_calibrate_tsc+0x324/0x439 Feb 22 16:02:45 touhami3 kernel: [<c0109258>] ? syscall_trace_enter_phase1+0xe5/0xee Feb 22 16:02:45 touhami3 kernel: [<c01cd39b>] ? fd_install+0x1a/0x1d Feb 22 16:02:45 touhami3 kernel: [<c01c5140>] ? putname+0x24/0x26 Feb 22 16:02:45 touhami3 kernel: [<c01ba5fc>] ? do_sys_open+0x1a7/0x1b1 Feb 22 16:02:45 touhami3 kernel: [<c0106407>] ? native_calibrate_tsc+0x324/0x439 Feb 22 16:02:45 touhami3 kernel: [<c01c7245>] SyS_ioctl+0x3e/0x60 Feb 22 16:02:45 touhami3 kernel: [<c0106407>] ? native_calibrate_tsc+0x324/0x439 Feb 22 16:02:45 touhami3 kernel: [<c040c351>] syscall_call+0x7/0x7 Feb 22 16:02:45 touhami3 kernel: [<c0106407>] ? native_calibrate_tsc+0x324/0x439 Feb 22 16:02:45 touhami3 kernel: [<c0106407>] ? native_calibrate_tsc+0x324/0x439 Feb 22 16:02:45 touhami3 kernel: ---[ end trace e42e3f2e897ef313 ]---
Found this: https://www.virtualbox.org/ticket/13772 I'll try the patch offered there, two and if it works I will update my patch.
Created attachment 397238 [details, diff] updated patch to fix kernel warnings
(In reply to Heiko Schäfer from comment #0) > I've attached the patch adapted for Gentoo. When reporting such bugs please attach full build log, emerge --info output and your kernel config.
(In reply to Andrew Savchenko from comment #5) > (In reply to Heiko Schäfer from comment #0) > > I've attached the patch adapted for Gentoo. > > When reporting such bugs please attach full build log, emerge --info output > and your kernel config. I filed the bug *AFTER* I had solved it, so an emerge --info of a auccessful build would be at bit strange.
According to the upstream bug report this is fixed in virtualbox-4.3.22 and higher. So I gonna keep this bug open until virtualbox-4.3.24 got stabilized (virtualbox-4.3.22 had other issues so it never went into the portage tree).
(In reply to Lars Wendler (Polynomial-C) from comment #7) > According to the upstream bug report this is fixed in virtualbox-4.3.22 and > higher. So I gonna keep this bug open until virtualbox-4.3.24 got stabilized > (virtualbox-4.3.22 had other issues so it never went into the portage tree). But the 4.2 branch of the driver will get the patches as well? I'm currently using the 4.2 branch of VirtualBox to run my Gentoo as guest, so it would be nice to have it working in there too. The next kernel release will cause the same problem again, if not fixed in 4.2.26.
(In reply to Heiko Schäfer from comment #8) > (In reply to Lars Wendler (Polynomial-C) from comment #7) > > According to the upstream bug report this is fixed in virtualbox-4.3.22 and > > higher. So I gonna keep this bug open until virtualbox-4.3.24 got stabilized > > (virtualbox-4.3.22 had other issues so it never went into the portage tree). > > But the 4.2 branch of the driver will get the patches as well? > > I'm currently using the 4.2 branch of VirtualBox to run my Gentoo as guest, > so it would be nice to have it working in there too. > > The next kernel release will cause the same problem again, if not fixed in > 4.2.26. I am sorry, but I removed all virtualbox-4.2 ebuilds from portage with the update to virtualbox-4.3.24. I am the only active virtualbox Gentoo maintainer and I don't have the ressources to maintain two branches of virtualbox simultaneously.
(In reply to Lars Wendler (Polynomial-C) from comment #9) > (In reply to Heiko Schäfer from comment #8) > > (In reply to Lars Wendler (Polynomial-C) from comment #7) > > > According to the upstream bug report this is fixed in virtualbox-4.3.22 and > > > higher. So I gonna keep this bug open until virtualbox-4.3.24 got stabilized > > > (virtualbox-4.3.22 had other issues so it never went into the portage tree). > > > > But the 4.2 branch of the driver will get the patches as well? > > > > I'm currently using the 4.2 branch of VirtualBox to run my Gentoo as guest, > > so it would be nice to have it working in there too. > > > > The next kernel release will cause the same problem again, if not fixed in > > 4.2.26. > > I am sorry, but I removed all virtualbox-4.2 ebuilds from portage with the > update to virtualbox-4.3.24. I am the only active virtualbox Gentoo > maintainer and I don't have the ressources to maintain two branches of > virtualbox simultaneously. Just applying my patch and to keep that version is no possibility? To have at least that version of the branch working for future kernel updates?
*** Bug 541388 has been marked as a duplicate of this bug. ***
Created attachment 400528 [details, diff] OpenGL Accelaration works now too My previous patch worked, but actually opengl accelaration didn't work. The patch in the duplicate bug #541388 finally brought even the opengl accelaration back to work. I know the 4.2.26 version has been removed from portage, but I may set up an overlay on GitHub. If it is done I will let it be known in this bug.
A basic overlay can be found here: https://github.com/velnias75/x11-video-driver-for-VBox-4.2.26
this is resolved in all the versions in gentoo according to this bug.
(In reply to Rick Farina (Zero_Chaos) from comment #14) > this is resolved in all the versions in gentoo according to this bug. Beside from being obsolete now, the 4.2 branch is already deleted from the portage tree :-(
(In reply to Heiko Schäfer from comment #13) > A basic overlay can be found here: > https://github.com/velnias75/x11-video-driver-for-VBox-4.2.26 FYI: just updated it for 4.2.34