Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[SOLVED] Xorg virtualbox no screens found
View unanswered posts
View posts from last 24 hours

Goto page 1, 2  Next  
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Wed May 24, 2017 6:04 am    Post subject: [SOLVED] Xorg virtualbox no screens found Reply with quote

Hello!

I'm trying to run Gentoo as VirtualBox guest.
For that I have emerged virtualbox-guest-additions-5.1.22


At first Xorg started, but additions didn't work because of vboxvideo kernel module
Here's the interesting part of dmesg
Code:
[    3.231898] vboxguest: misc device minor 57, IRQ 20, I/O port d020, MMIO at 00000000f0400000 (size 0x400000)
[    3.231899] vboxguest: Successfully loaded version 5.1.22 (interface 0x00010004)
[    3.266371] vboxvideo: Unknown symbol ttm_bo_mmap (err 0)
[    3.266382] vboxvideo: Unknown symbol ttm_bo_global_release (err 0)
[    3.266385] vboxvideo: Unknown symbol ttm_pool_unpopulate (err 0)
[    3.266388] vboxvideo: Unknown symbol ttm_bo_manager_func (err 0)
[    3.266390] vboxvideo: Unknown symbol ttm_bo_global_init (err 0)
[    3.266395] vboxvideo: Unknown symbol ttm_bo_device_release (err 0)
[    3.266403] vboxvideo: Unknown symbol ttm_bo_kunmap (err 0)
[    3.266405] vboxvideo: Unknown symbol ttm_bo_del_sub_from_lru (err 0)
[    3.266409] vboxvideo: Unknown symbol ttm_bo_device_init (err 0)
[    3.266410] vboxvideo: Unknown symbol ttm_bo_init_mm (err 0)
[    3.266410] vboxvideo: Unknown symbol ttm_bo_dma_acc_size (err 0)
[    3.266413] vboxvideo: Unknown symbol ttm_tt_init (err 0)
[    3.266414] vboxvideo: Unknown symbol ttm_bo_kmap (err 0)
[    3.266418] vboxvideo: Unknown symbol ttm_bo_add_to_lru (err 0)
[    3.266420] vboxvideo: Unknown symbol ttm_bo_unref (err 0)
[    3.266421] vboxvideo: Unknown symbol ttm_mem_global_release (err 0)
[    3.266422] vboxvideo: Unknown symbol ttm_mem_global_init (err 0)
[    3.266423] vboxvideo: Unknown symbol ttm_bo_default_lru_tail (err 0)
[    3.266424] vboxvideo: Unknown symbol ttm_bo_default_swap_lru_tail (err 0)
[    3.266429] vboxvideo: Unknown symbol ttm_bo_init (err 0)
[    3.266430] vboxvideo: Unknown symbol ttm_bo_validate (err 0)
[    3.266433] vboxvideo: Unknown symbol ttm_bo_move_memcpy (err 0)
[    3.266435] vboxvideo: Unknown symbol ttm_tt_fini (err 0)
[    3.266436] vboxvideo: Unknown symbol ttm_pool_populate (err 0)


It appears, that vboxvideo depends on DRM_TTM module, which you can't turn on youself.
It's enabled automatically if you enable any module, which depends on it, in make menuconfig.
Code:
config DRM_TTM
   tristate
   depends on DRM
   help
     GPU memory management subsystem for devices with multiple
     GPU memory types. Will be enabled automatically if a device driver
     uses it.

Those modules are - ast, cirrus, mgag200, nouveau, radeon, vmwgfx.
So, unless you enable one of these modules, you can't use virtualbox-guest-additions :).
I have decided to enable vmwgfx (at leas it has something in common wiht virtualbox) and dmesg became better.
The messages about unknown symbols are gone.
Also, console window became larger, so I'm sure vboxvideo actually started working.

But Xorg is not starting now.
Here's my /var/log/Xorg.log.0 file
Code:
[   853.555]
X.Org X Server 1.19.2
Release Date: 2017-03-02
[   853.558] X Protocol Version 11, Revision 0
[   853.558] Build Operating System: Linux 4.9.16-gentoo x86_64 Gentoo
[   853.561] Current Operating System: Linux gentoo_vm 4.9.16-gentoo #12 SMP Wed May 24 04:51:24 -00 2017 x86_64
[   853.561] Kernel command line: BOOT_IMAGE=/vmlinuz-4.9.16-gentoo root=/dev/sda4 ro
[   853.563] Build Date: 23 May 2017  01:20:36PM
[   853.564] 
[   853.564] Current version of pixman: 0.34.0
[   853.566]    Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
[   853.566] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   853.569] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 24 05:06:08 2017
[   853.570] (==) Using config directory: "/etc/X11/xorg.conf.d"
[   853.571] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   853.571] (==) ServerLayout "Default Layout"
[   853.571] (**) |-->Screen "Screen-vboxvideo" (0)
[   853.571] (**) |   |-->Monitor "<default monitor>"
[   853.571] (**) |   |-->Device "Device-vboxvideo"
[   853.571] (==) No monitor specified for screen "Screen-vboxvideo".
   Using a default monitor configuration.
[   853.571] (==) Automatically adding devices
[   853.571] (==) Automatically enabling devices
[   853.571] (==) Automatically adding GPU devices
[   853.571] (==) Max clients allowed: 256, resource mask: 0x1fffff
[   853.571] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[   853.571]    Entry deleted from font path.
[   853.571] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[   853.571]    Entry deleted from font path.
[   853.571] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   853.571]    Entry deleted from font path.
[   853.571] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   853.571]    Entry deleted from font path.
[   853.571]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   853.571] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   853.571]    Entry deleted from font path.
[   853.571]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   853.571] (==) FontPath set to:
   /usr/share/fonts/misc/
[   853.571] (==) ModulePath set to "/usr/lib64/xorg/modules"
[   853.571] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
[   853.571] (II) Loader magic: 0x813c80
[   853.571] (II) Module ABI versions:
[   853.571]    X.Org ANSI C Emulation: 0.4
[   853.571]    X.Org Video Driver: 23.0
[   853.571]    X.Org XInput driver : 24.1
[   853.571]    X.Org Server Extension : 10.0
[   853.571] (II) xfree86: Adding drm device (/dev/dri/card0)
[   853.574] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216, BIOS @ 0x????????/131072
[   853.574] (II) LoadModule: "glx"
[   853.574] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[   853.575] (II) Module glx: vendor="X.Org Foundation"
[   853.575]    compiled for 1.19.2, module version = 1.0.0
[   853.575]    ABI class: X.Org Server Extension, version 10.0
[   853.575] (II) LoadModule: "vboxvideo"
[   853.575] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
[   853.575] (II) Module vboxvideo: vendor="Oracle Corporation"
[   853.575]    compiled for 1.19.2, module version = 1.0.1
[   853.575]    Module class: X.Org Video Driver
[   853.575]    ABI class: X.Org Video Driver, version 23.0
[   853.575] (**) Load address of symbol "VBOXVIDEO" is 0x7f08e0e22380
[   853.575] (II) VBoxVideo: guest driver for VirtualBox: vbox
[   853.575] (--) using VT number 7

[   853.578] (II) vboxvideo: kernel driver found, not loading.
[   853.578] (EE) No devices detected.
[   853.578] (EE)
Fatal server error:
[   853.578] (EE) no screens found(EE)
[   853.578] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[   853.578] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   853.578] (EE)
[   853.583] (EE) Server terminated with error (1). Closing log file.


So, kernel driver is found, but no devices detected.
Does anyone know what to do about that?

I have virtualbox-guest-additions.5.1.22 installed and kernel version 4.9.16


Last edited by poxu on Fri Jun 02, 2017 12:46 pm; edited 4 times in total
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7251
Location: Saint Amant, Acadiana

PostPosted: Wed May 24, 2017 12:09 pm    Post subject: Reply with quote

You get "unknown symbol" error when you try to insert a module into a kernel it was not built against.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Apheus
Guru
Guru


Joined: 12 Jul 2008
Posts: 420

PostPosted: Wed May 24, 2017 12:22 pm    Post subject: Reply with quote

Here is a part of Xorg.0.log from a working guest: same vbox and kernel versions, also with vmwgfx driver enabled to get ttm:

Code:
[   103.521] (II) LoadModule: "vboxvideo"
[   103.521] (II) Loading /usr/lib64/xorg/modules/drivers/vboxvideo_drv.so
[   103.521] (II) Module vboxvideo: vendor="Oracle Corporation"
[   103.521]    compiled for 1.19.2, module version = 1.0.1
[   103.521]    Module class: X.Org Video Driver
[   103.521]    ABI class: X.Org Video Driver, version 23.0
[   103.521] (**) Load address of symbol "VBOXVIDEO" is <sanitized>
[   103.521] (II) LoadModule: "modesetting"
[   103.521] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[   103.521] (II) Module modesetting: vendor="X.Org Foundation"
[   103.521]    compiled for 1.19.2, module version = 1.19.2
[   103.521]    Module class: X.Org Video Driver
[   103.521]    ABI class: X.Org Video Driver, version 23.0
[   103.521] (II) LoadModule: "fbdev"
[   103.521] (WW) Warning, couldn't open module fbdev
[   103.521] (II) UnloadModule: "fbdev"
[   103.521] (II) Unloading fbdev
[   103.521] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   103.521] (II) LoadModule: "vesa"
[   103.522] (WW) Warning, couldn't open module vesa
[   103.522] (II) UnloadModule: "vesa"
[   103.522] (II) Unloading vesa
[   103.522] (EE) Failed to load module "vesa" (module does not exist, 0)
[   103.522] (II) VBoxVideo: guest driver for VirtualBox: vbox
[   103.522] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   103.522] (++) using VT number 7

[   103.524] (II) vboxvideo: kernel driver found, not loading.
[   103.524] (II) vboxvideo: kernel driver found, not loading.
[   103.525] (II) modeset(0): using drv /dev/dri/card0
[   103.525] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[   103.525] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[   103.525] (==) modeset(0): RGB weight 888
[   103.525] (==) modeset(0): Default visual is TrueColor


I see there is no mention of "kms" or "kernel mode setting" in your Xorg log. Do you have it enabled in kernel?

Code:
# zgrep KMS /proc/config.gz
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y


Also, do you have a "Driver" in Xorg.conf "Device" Section? You don't need any. You don't even need a "Device" section.
_________________
My phrenologist says I'm stupid.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Wed May 24, 2017 2:06 pm    Post subject: Reply with quote

I have that in .config, which I used to build my kernel
Code:
CONFIG_DRM_KMS_HELPER=y
CONFIG_DRM_KMS_FB_HELPER=y


But X is not loading modesetting_drv .

Maybe I should have some drivers installed. I have installed Virtio as per VirtualBox section of Gentoo wiki.
Back to top
View user's profile Send private message
Apheus
Guru
Guru


Joined: 12 Jul 2008
Posts: 420

PostPosted: Wed May 24, 2017 2:21 pm    Post subject: Reply with quote

poxu wrote:
But X is not loading modesetting_drv .


This is /usr/lib64/xorg/modules/drivers/modesetting_drv.so and belongs to x11-base/xorg-server. Do you have the file? If not, what are your use flags for xorg-server?

Quote:
Maybe I should have some drivers installed. I have installed Virtio as per VirtualBox section of Gentoo wiki.


The wiki says "VIRTIO_GPU". Interesting, I have never heard of it and have not enabled it in my config. Not even visible because it depends on CONFIG_VIRTIO which is not enabled.
_________________
My phrenologist says I'm stupid.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Wed May 24, 2017 2:35 pm    Post subject: Reply with quote

Apheus wrote:
This is /usr/lib64/xorg/modules/drivers/modesetting_drv.so and belongs to x11-base/xorg-server. Do you have the file? If not, what are your use flags for xorg-server?


The file is there
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Thu May 25, 2017 5:47 am    Post subject: Reply with quote

Ok, I still have no idea what's going on, but after some thinking I have realized, that I have rebuilt my kernel several times, after emerging virtualbox-guest-additions. So, maybe rebuilding the package with all dependencies against new kernel configuration would help.
Code:
emerge -ae virtualbox-guest-additions
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Thu May 25, 2017 8:18 am    Post subject: Reply with quote

And it didn't help.
Back to top
View user's profile Send private message
Apheus
Guru
Guru


Joined: 12 Jul 2008
Posts: 420

PostPosted: Thu May 25, 2017 9:30 am    Post subject: Reply with quote

Please post the output of

Code:
lsmod


and

Code:
emerge -pv virtualbox-guest-additions


And get rid of any config in /etc/X11/xorg.conf.d, let Xorg and kernel DRM handle everything.
_________________
My phrenologist says I'm stupid.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Thu May 25, 2017 4:15 pm    Post subject: Reply with quote

lsmod
Code:
Module                  Size  Used by
vboxsf                 31526  0
vboxvideo              34632  1
vboxguest             198885  3 vboxsf,vboxvideo


emerge -pv virtualbox-guest-additions

Code:

These are the packages that would be merged, in order:

Calculating dependencies  .... done!
[ebuild   R   ~] app-emulation/virtualbox-guest-additions-5.1.22::gentoo  USE="X" 0 KiB

Total: 1 package (1 reinstall), Size of downloads: 0 KiB
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7251
Location: Saint Amant, Acadiana

PostPosted: Thu May 25, 2017 4:17 pm    Post subject: Reply with quote

After installing a new kernel you are supposed to do emerge @module-rebuild.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Thu May 25, 2017 4:19 pm    Post subject: Reply with quote

Quote:
After installing a new kernel you are supposed to do emerge @module-rebuild.


Yes, I did that a couple of times already :) .
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7251
Location: Saint Amant, Acadiana

PostPosted: Thu May 25, 2017 4:20 pm    Post subject: Reply with quote

You still getting the unknown symbol error?
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Fri May 26, 2017 5:24 am    Post subject: Reply with quote

Quote:
You still getting the unknown symbol error?

No, I'm not . I have fixed that by enabling DRM_TTM in the kernel. Perhaps I wasn't clear enough in my first post. I'll fix that, thanks.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43753
Location: 56N 3W

PostPosted: Fri May 26, 2017 8:02 am    Post subject: Reply with quote

poxu,

Can we have a clean self consistent data set to work with please?
All from your guest system.

lspci
the outputut of dmesg
your kernel .config
the content of /var/log/Xorg.0.log

lspci will fit into a post, the other things need to be go to a pastebin.
wgetpaste is your friend.

The output of
Code:
uname -a
and
Code:
ls -l /boot
might be interesting too.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Fri May 26, 2017 10:42 am    Post subject: Reply with quote

dmesg
.config
Xorg.0.log

lspci
Code:

00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02)
00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
00:05.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 01)
00:06.0 USB controller: Apple Inc. KeyLargo/Intrepid USB
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:0d.0 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 02)


uname -a
Code:

Linux gentoo_vm 4.9.16-gentoo #21 SMP Thu May 25 16:18:22 -00 2017 x86_64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz GenuineIntel GNU/Linux


ls -l /boot
Code:

total 19148
-rw-r--r-- 1 root root 3450494 May 25 16:18 System.map-4.9.16-gentoo
-rw-r--r-- 1 root root 3452589 May 25 15:51 System.map-4.9.16-gentoo.old
-rw-r--r-- 1 root root  108840 May 25 16:18 config-4.9.16-gentoo
-rw-r--r-- 1 root root  108928 May 25 15:51 config-4.9.16-gentoo.old
drwxr-xr-x 6 root root    4096 May 17 05:33 grub
drwx------ 2 root root   16384 May 16 12:22 lost+found
-rw-r--r-- 1 root root 6204944 May 25 16:18 vmlinuz-4.9.16-gentoo
-rw-r--r-- 1 root root 6210352 May 25 15:51 vmlinuz-4.9.16-gentoo.old


Thank's for wpastebin by the way, it helped :) . And thank all of you for showing interest in my problem.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43753
Location: 56N 3W

PostPosted: Fri May 26, 2017 12:43 pm    Post subject: Reply with quote

poxu,

This is good. It shows that the kernel part of the video driver is loaded and is providing your console framebuffer.
dmesg:
[    3.843315] [TTM] Zone  kernel: Available graphics memory: 2024366 kiB
[    3.843315] [TTM] Initializing pool allocator
[    3.843317] [TTM] Initializing DMA pool allocator
[    3.850938] fbcon: vboxdrmfb (fb0) is primary device
[    3.858839] Console: switching to colour frame buffer device 100x37
[    3.863459] vboxvideo 0000:00:02.0: fb0: vboxdrmfb frame buffer device
[    3.863461] [drm] Initialized vboxvideo 1.0.0 20130823 for 0000:00:02.0 on minor 0


Your boot and uname -a looks reasonable too. Build number #21 eww but ar lest the kernel build time, Thu May 25 16:18:22, is recent.
We have seen two week old kernels there, so it was just to check your kernel install process was working.

It was all looking good until
Xorg.0.log:
[    20.178] (--) using VT number 7

[    20.179] (II) vboxvideo: kernel driver found, not loading.
[    20.179] (EE) No devices detected.

The kernel driver found, not loading, is correct. You are using the kernel driver for the console.

Let me boot SystemRescueCD in VBox and see what it does.

I'm not sure if CONFIG_DRM_VIRTIO_GPU=y is harmless or not.
VIRTIO can used by kernel virtual machines to speed up I/O. Its in place of the emulated hardware that you see in the guest lspci.
However, both the host and guest must support VIRTIO, so it can't support unmodified guest operating systems.

--- edit ---

Reading between the lines ..
Xorg.0.log:
[    19.890] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    19.890] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    19.932] (==) ServerLayout "Default Layout"
[    19.932] (**) |-->Screen "Screen-vboxvideo" (0)
[    19.932] (**) |   |-->Monitor "<default monitor>"
[    19.932] (**) |   |-->Device "Device-vboxvideo"

you are trying to tell Xorg how the start. Don't do that.

A default startup long includes
SystemRescueCD Xorg.0.log:
[   252.209] (==) Matched vboxvideo as autoconfigured driver 0
[   252.209] (==) Matched modesetting as autoconfigured driver 1
[   252.209] (==) Matched fbdev as autoconfigured driver 2
[   252.209] (==) Matched vesa as autoconfigured driver 3"

Which is the list of auto detected open source drivers Xorg will try for the hardware its finds itself on.
Since your Xorg.conf.log is missing that list, somewhere in your /etc/X11/xorg.conf.d you are telling Xorg to use
Code:
[    19.932] (**) |-->Screen "Screen-vboxvideo" (0)
[    19.932] (**) |   |-->Device "Device-vboxvideo"
and maybe other non default things.
Remove those settings.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Fri May 26, 2017 2:38 pm    Post subject: Reply with quote

Since my last post I have made a clean install of Gentoo, but chose not to use virtualbox-5.1.22 and used 5.0.32 instead.
And X was working. I got suspicious and made a clean install with virtualbox-5.1.22, and it worked too.

And then I read your reply.
Code:
somewhere in your /etc/X11/xorg.conf.d you are telling Xorg to use and maybe other non default things. Remove those settings.

I didn't put anything to /etc/X11/xorg.conf.d , but virtualbox-guest-additions had instructed me to put /usr/share/doc/virtualbox-guest-additions-5.1.22/xorg.conf.vbox to my configuration. And I put it to /usr/share/X11/xorg.conf.d ! I totally forgot about that. After I removed it, X started working!

Thank you so much for your help!
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43753
Location: 56N 3W

PostPosted: Fri May 26, 2017 2:52 pm    Post subject: Reply with quote

poxu,

Check that your vbox guest is working for the right reasons.

Look in /var/log/Xorg.0.log and see which driver its using.
vboxvideo is the right answer.

Reinstalling never fixes Gentoo. It only provides the opportunity to make a different mistake :)
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Fri May 26, 2017 3:05 pm    Post subject: Reply with quote

Quote:
Look in /var/log/Xorg.0.log and see which driver its using.

Here's a link to my current Xorg.0.log. Is it ok?

This part is weird
Code:
[    28.415] (II) vboxvideo: kernel driver found, not loading.
[    28.417] (II) modeset(0): using drv /dev/dri/card0
[    28.417] (WW) Falling back to old probe method for fbdev
[    28.417] (II) Loading sub module "fbdevhw"
[    28.417] (II) LoadModule: "fbdevhw"
[    28.427] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[    28.437] (II) Module fbdevhw: vendor="X.Org Foundation"
[    28.438]    compiled for 1.19.2, module version = 0.0.2
[    28.438]    ABI class: X.Org Video Driver, version 23.0
[    28.438] (WW) Falling back to old probe method for vesa
[    28.438] (II) modeset(0): Creating default Display subsection in Screen section
   "Default Screen Section" for depth/fbbpp 24/32
[    28.438] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    28.438] (==) modeset(0): RGB weight 888
[    28.438] (==) modeset(0): Default visual is TrueColor
[    28.438] (II) Loading sub module "glamoregl"
[    28.438] (II) LoadModule: "glamoregl"
[    28.438] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[    28.497] (II) Module glamoregl: vendor="X.Org Foundation"
[    28.497]    compiled for 1.19.2, module version = 1.0.0
[    28.497]    ABI class: X.Org ANSI C Emulation, version 0.4
[    28.497] (II) glamor: OpenGL accelerated X.org driver based.
[    29.949] (II) glamor: EGL version 1.4 (DRI2):
[    29.949] EGL_MESA_drm_image required.
[    29.959] (EE) modeset(0): glamor initialization failed
[    29.959] (II) modeset(0): ShadowFB: preferred NO, enabled NO
[    29.961] (II) modeset(0): Output VGA-1 has no monitor section
[    29.961] (II) modeset(0): EDID for output VGA-1
[    29.961] (II) modeset(0): Manufacturer: VBX  Model: 0  Serial#: 58983840


Quote:

Reinstalling never fixes Gentoo. It only provides the opportunity to make a different mistake :)


I totally agree! Just wanted to make sure it's not the unstable version of virtualbox-guest-additions I was using.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43753
Location: 56N 3W

PostPosted: Fri May 26, 2017 4:37 pm    Post subject: Reply with quote

poxu,

Check your log for this snippet.
Code:
[   252.209] (==) Matched vboxvideo as autoconfigured driver 0
[   252.209] (==) Matched modesetting as autoconfigured driver 1
[   252.209] (==) Matched fbdev as autoconfigured driver 2
[   252.209] (==) Matched vesa as autoconfigured driver 3


Modesetting is the second on the list. Xorg should try the drivers on that list in order until one loads.
It implies that the the Xorg part of vboxvideo is not loading for some reason.

The driver is provided by xorg-drivers, if you list virtualbox in VIDEO_CARDS=
You can avoid some rebuilds by using
Code:
emerge -1av x11-drivers/xf86-video-virtualbox


Is that a new package?
Be sure you get the version that matches your VBox version. Mix and match might work but you get to keep the pieces if it doesn't.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Tue May 30, 2017 10:25 am    Post subject: Reply with quote

Quote:
Modesetting is the second on the list. Xorg should try the drivers on that list in order until one loads.
It implies that the the Xorg part of vboxvideo is not loading for some reason.

I thought, that vboxvideo driver uses modesetting.

I have added the following to my make.conf
Code:
VIDEO_CARDS="virtualbox"


I don't have any drivers, except for vboxvideo in my system and X still works. Modesetting is on though.

Quote:
Be sure you get the version that matches your VBox version.

Versions match.

So the question is now if it's ok, if I have modesetting in my Xorg.0.log
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43753
Location: 56N 3W

PostPosted: Tue May 30, 2017 12:40 pm    Post subject: Reply with quote

poxu,

Pastebin your Xorg.0.log please.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
poxu
n00b
n00b


Joined: 19 May 2017
Posts: 21

PostPosted: Thu Jun 01, 2017 7:16 am    Post subject: Reply with quote

Quote:
Pastebin your Xorg.0.log please.


Here it is :) .Xorg.0.log
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43753
Location: 56N 3W

PostPosted: Thu Jun 01, 2017 7:26 am    Post subject: Reply with quote

poxu,

Code:
[    22.474] (==) Matched vboxvideo as autoconfigured driver 0
[    22.474] (==) Matched vboxvideo as autoconfigured driver 1
[    22.474] (==) Matched modesetting as autoconfigured driver 2
[    22.474] (==) Matched fbdev as autoconfigured driver 3
[    22.474] (==) Matched vesa as autoconfigured driver 4
[    22.474] (==) Assigned the driver to the xf86ConfigLayout
...
[    22.501] (II) VBoxVideo: guest driver for VirtualBox: vbox
[    22.501] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    22.501] (--) using VT number 7


Looks OK.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Goto page 1, 2  Next
Page 1 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum