| 1 |
Am Freitag, 15. September 2017, 20:35:03 schrieb Alexander Kapshuk: |
| 2 |
> On Fri, Sep 15, 2017 at 5:47 PM, Alexander Puchmayr |
| 3 |
<alexander.puchmayr@×××××××.at> wrote: |
| 4 |
> [list with log dumps cutted] |
| 5 |
> > Obviously, something is going terribly wrong here, and I'm getting stuck |
| 6 |
> > as I |
| 7 |
> > do not have any Idea where to start. The only thing that changed is a |
| 8 |
> > kernel |
| 9 |
> > upgrade and a rebuild of the virtual box modules. |
| 10 |
> > |
| 11 |
> > Any ideas? |
| 12 |
> > |
| 13 |
> > Thanks in advance, |
| 14 |
> > |
| 15 |
> > Alex |
| 16 |
> |
| 17 |
> The Gentoo wiki article referenced below emphasizes the fact that certain |
| 18 |
> kernel config options need enabling in order to have proper hardware |
| 19 |
> emulation. So you want to make sure you have those enabled in your kernel |
| 20 |
> config. Then take it from there. |
| 21 |
> |
| 22 |
> https://wiki.gentoo.org/wiki/VirtualBox |
| 23 |
> |
| 24 |
|
| 25 |
Thanks for your hint, the kernel config was as it should be (except that I used |
| 26 |
modules wherever possible). |
| 27 |
|
| 28 |
My assumption was that the kernel frame buffer device and X driver conflict and |
| 29 |
the X server does not load because the kernel frame buffer driver was active. |
| 30 |
So, I removed the kernel driver by blacklisting vboxvideo |
| 31 |
|
| 32 |
$ cat /etc/modprobe.d/blacklist.conf |
| 33 |
blacklist vboxvideo |
| 34 |
$ genkernel initramfs |
| 35 |
[...] |
| 36 |
$ reboot |
| 37 |
|
| 38 |
After reboot: sddm showed a login screen, X was working (with VboxVideo |
| 39 |
driver), I could log in successfully. |
| 40 |
|
| 41 |
Problem solved :-) |
| 42 |
|
| 43 |
Thanks to all who spent a thought on this! |
| 44 |
|
| 45 |
Regards |
| 46 |
Alex |
| 47 |
|
| 48 |
PS: The question, why a framebuffer device for virtualbox is automatically |
| 49 |
created just to cause a conflict with X later on, still remains. Do other |
| 50 |
installations have the same problem? |
Archives