[Solved]Virtualbox Gentoo, Start X No screens found and more

[Hironatashima]

So I've been fighting with X window for a week or more trying to get it to run. I built into the Make.conf the use flags for it, I've compiled the kernel for it to work with Virtualbox. Emerged Virtualbox AND the virtual box guest addons, etc. etc. etc., I followed the handbook for it too. The gentoo environment is running beautifully... minus X window. Everything is set as far as I can figure.... I'm trying to run it with Gnome, since I've never used Gnome much before, mostly I just use KDE, but this is a severe headache and a half. So to the point, here's my pastebins of what I figure yall need to help me out:

Xorg.0.log https://paste.pound-python.org/show/BIcte5WQU75kW993oJ1o/

xorg.conf https://paste.pound-python.org/show/4o3AaoMdRKeYbLAxi82y/

make.conf https://paste.pound-python.org/show/8VnRZgTurlEA2EXNadgS/

If there's any other pastebin you guys need, let me know, and I'll throw it up here with the quickness. I've looked at a number of other issues that I thought were similar, but none of their fixes helped me out at all.

Thanks in advance for the help!

[Maxxx]

I had same problem...

Try to put "modesetting" instead of "vboxvideo" in your xorg.conf - Section "Device":

[Hironatashima]

Thanks for the response Maxxx,

I've made the suggested changes, and the results have not changed too drastically. Shall I try the X -configure option? I've heard that command no longer works effectively... Here's the pastebins at any rate:

Xorg.0.log - https://paste.pound-python.org/show/wGhycVH562LTy69wNImD/

xorg.conf - https://paste.pound-python.org/show/iilTQRfHZmM6eOryLsiF/

make.conf - https://paste.pound-python.org/show/mupwK4O4k3WNEHOv1KIg/

[Maxxx]

Could you post the output of:

[guitou]

Hello.

Check the first error (the dbus one), try and fix it (starting dbus service for example?..)
Then regarding second error, whether using vboxdriver or modsetting, it must be installed to be available (emerge x11-drivers/xf86-video-vboxvideo)

++
Gi)

[Hironatashima]

[Hironatashima]

guitou,

Thank you for chiming in and helping also.

The first error I haven't yet cracked yet.

The second: I tried to emerge the vbox driver, said something about unmasking, fixed that, and emerged again, and it got to the end, but stopped because it'd create a 'collision' with /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so

I think there's some progress happening, but... not quite sure where, yet.

[NeddySeagoon]

Hironatashima,

[guitou]

Thanks neddy: always a better knowledge and a so much better way to tell
And to Hiro: as a general rule, when encountering errors, it is better to address first error first (often happen to some errors to be due to previous ones / besides, these 2 don't seem to depend on one another though)

++
Gi)

[Hironatashima]

NeddySeagoon,

You are indeed a guru.

That said, some headway was made with your advice. I had no idea that I had to manually add DBUS to default. I renamed the xorg.conf like you said, it started, and terminated with a screen flicker... that was it... Here's the log output:

[Hironatashima]

Further Troubleshooting update for you wonderful gurus out there!

So I had to change my grub2 config to allow for Systemd, and found a nice walkthrough for that here:

https://wiki.gentoo.org/wiki/Systemd#Bootloader

and combined it with the initial install handbook for gentoo to rebuild my grub in accordance with Systemd.

so that fixed my systemd error, and I'm trudging on to figure out what the actual @$!!@#$ to do with the rest. I lost the Systemd error and added this error:

[Hironatashima]

Another update, I've done a bit of research, it seems that fbdev and vesa are errors from when X autodetects drivers. Unfortunately, the fix to eliminate those errors is to either a) ignore them, or b) install the packages with those particular drivers/scripts.

Now I'm looking to fix glamor, and the AIGLX of OpenGL. Remaining troubleshooting:

glamor
AIGLX.

I've tried to startx again, the screen blinks, resizes, and then X closes, but no fatal errors anymore.

[Hironatashima]

Final update, at least on this matter:

I've determined that my critical error that was blocking my advancement was ultimately DBUS not starting.

All the research that I have done on following errors to this end points to that being the culprit. The errors that I was seeing was caused by autodetection, ultimately.

my proof of concept was adding the following lines to my test user's .xinitrc:

[Hironatashima]

Final update for getting Gnome up and running:

The point I was at, was legit the very end of the line..... through systemd:

[NeddySeagoon]

Hironatashima,

Check your Xorg.0.log one more time.
There are degrees of working. Has the glamour error gone away?

Software rendering works but is very slow. You can also try

[Hironatashima]

the lines that are relevant:

[NeddySeagoon]

Hironatashima,

At an educated guess, you need to set the egl USE flag in make.conf and rebuild all affected packages.

Check your

[Hironatashima]

interesting.

Pastebin:

[NeddySeagoon]

Hironatashima,

Try

[Hironatashima]

NeddySeagoon,

Thank you again, your advice has been so helpful.

I am in the midst of rebuilding mesa right now, actually. It's a pretty lengthy emerge, that's for sure. It just finished, and I'm going to go ahead and reboot the system to test the results.

[Hironatashima]

Here's the pastebin, currently:

https://paste.pound-python.org/show/KqboU48xUepcyI9oVLqf/

it still fails, and I'm not sure how to fix it. rebuilding MESA did improve the graphics flow of the VBox exponentially, however. but still....

[NeddySeagoon]

Hironatashima,

The preferred list of video drivers, in order is

[Hironatashima]

NeddySeagoon,

Thanks for seeing this through,

So, the only way I know of to set modesetting is in the xorg.conf file, and I renamed that, so it wouldn't have anything but the default to work with. So how do I force it to use vboxvideo?

second, I'm having some dependency issues with doing any emerges that are affecting @world, right now, that I'm trying to take care of. I've been trying to figure out how to solve the dependency conflict that has net-libs/webkit-gtk locked up. says it has umet requirements with a whole lot of USE flags following it. I guess I have to try them out. What does it mean when a USE flag is in blue? such as displayed here:

(-aqua) -coverage -doc -nsplugin -test

[NeddySeagoon]

Hironatashima,

A USE flag in Red is on, a USE flag in Blue is off
A USE flag in Green, with a * has had its setting changed since the package was built.
That means the new setting does not yet apply to the package.

The brackets ( ) around a USE setting means that the setting is forced in your profile.
That's not to say you can't change it but it requires some extra steps.
You also get to keep all the pieces if it breaks, since USE settings are usually forced for good reasons.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[Hironatashima]

localhost ~ # emerge -uDUav @world
here's the raw dump from my attempted @world emerge: