Am Freitag, 15. September 2017, 20:35:03 schrieb Alexander Kapshuk:
> On Fri, Sep 15, 2017 at 5:47 PM, Alexander Puchmayr
<alexander.puchm...@linznet.at> wrote:
> [list with log dumps cutted]
> > Obviously, something is going terribly wrong here, and I'm getting stuck
> > as I
> > do not have any Idea where to start. The only thing that changed is a
> > kernel
> > upgrade and a rebuild of the virtual box modules.
> >
> > Any ideas?
> >
> > Thanks in advance,
> >
> > Alex
>
> The Gentoo wiki article referenced below emphasizes the fact that certain
> kernel config options need enabling in order to have proper hardware
> emulation. So you want to make sure you have those enabled in your kernel
> config. Then take it from there.
>
> https://wiki.gentoo.org/wiki/VirtualBox
>
Thanks for your hint, the kernel config was as it should be (except that I used
modules wherever possible).
My assumption was that the kernel frame buffer device and X driver conflict and
the X server does not load because the kernel frame buffer driver was active.
So, I removed the kernel driver by blacklisting vboxvideo
$ cat /etc/modprobe.d/blacklist.conf
blacklist vboxvideo
$ genkernel initramfs
[...]
$ reboot
After reboot: sddm showed a login screen, X was working (with VboxVideo
driver), I could log in successfully.
Problem solved :-)
Thanks to all who spent a thought on this!
Regards
Alex
PS: The question, why a framebuffer device for virtualbox is automatically
created just to cause a conflict with X later on, still remains. Do other
installations have the same problem?
