You are not logged in.

Pages: 1

#1 2015-01-27 01:25:35

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

Cannot start X on a new install on Virtualbox

Hi,

I've been following wiki https://wiki.archlinux.org/index.php/Vi … nux_guests to install Arch linux as virtualbox guest on my Mac.

I've installed virtualbox-guest-utils and have vboxvideo module loaded:

[user@vbox ~]$ lsmod | grep vbox
vboxvideo              12437  0
drm                   263481  2 vboxvideo
vboxsf                 41351  0
vboxguest             206352  1 vboxsf

Here is Xorg.0.log

[    26.349]
X.Org X Server 1.16.3
Release Date: 2014-12-20
[    26.349] X Protocol Version 11, Revision 0
[    26.349] Build Operating System: Linux 3.18.1-1-ARCH x86_64
[    26.349] Current Operating System: Linux vbox 3.18.2-2-ARCH #1 SMP PREEMPT Fri Jan 9 07:37:51 CET 2015 x86_64
[    26.349] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=16a46eed-4db4-43cc-92c1-a12e869795b3 rw quiet
[    26.349] Build Date: 29 December 2014  01:09:58PM
[    26.349]
[    26.350] Current version of pixman: 0.32.6
[    26.350]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    26.350] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    26.350] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 26 17:10:58 2015
[    26.355] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    26.355] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    26.360] (==) No Layout section.  Using the first Screen section.
[    26.360] (==) No screen section available. Using defaults.
[    26.360] (**) |-->Screen "Default Screen Section" (0)
[    26.360] (**) |   |-->Monitor "<default monitor>"
[    26.362] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    26.362] (==) Automatically adding devices
[    26.362] (==) Automatically enabling devices
[    26.362] (==) Automatically adding GPU devices
[    26.376] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/TTF/".
[    26.376]    Entry deleted from font path.
[    26.376]    (Run 'mkfontdir' on "/usr/share/fonts/TTF/").
[    26.379] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[    26.379]    Entry deleted from font path.
[    26.379]    (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[    26.379] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[    26.379]    Entry deleted from font path.
[    26.380] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[    26.380]    Entry deleted from font path.
[    26.380]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[    26.380] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[    26.380]    Entry deleted from font path.
[    26.380]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[    26.380] (==) FontPath set to:
        /usr/share/fonts/misc/
[    26.381] (==) ModulePath set to "/usr/lib/xorg/modules"
[    26.381] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    26.382] (II) Loader magic: 0x818d80
[    26.382] (II) Module ABI versions:
[    26.382]    X.Org ANSI C Emulation: 0.4
[    26.382]    X.Org Video Driver: 18.0
[    26.382]    X.Org XInput driver : 21.0
[    26.382]    X.Org Server Extension : 8.0
[    26.389] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[    26.389] (II) xfree86: Adding drm device (/dev/dri/card0)
[    26.390] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[    26.390] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Invalid argument
[    26.390] (II) systemd-logind: releasing fd for 226:0
[    26.398] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/67108864
[    26.398] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    26.399] (II) LoadModule: "glx"
[    26.409] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    26.467] (II) Module glx: vendor="X.Org Foundation"
[    26.467]    compiled for 1.16.3, module version = 1.0.0
[    26.467]    ABI class: X.Org Server Extension, version 8.0
[    26.467] (==) AIGLX enabled
[    26.467] (==) Matched vboxvideo as autoconfigured driver 0
[    26.467] (==) Matched modesetting as autoconfigured driver 1
[    26.467] (==) Matched fbdev as autoconfigured driver 2
[    26.467] (==) Matched vesa as autoconfigured driver 3
[    26.467] (==) Assigned the driver to the xf86ConfigLayout
[    26.468] (II) LoadModule: "vboxvideo"
[    26.468] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
[    26.470] (II) Module vboxvideo: vendor="Oracle Corporation"
[    26.470]    compiled for 10.6.99, module version = 1.0.1
[    26.470]    Module class: X.Org Video Driver
[    26.470]    ABI class: X.Org Video Driver, version 18.0
[    26.470] (**) Load address of symbol "VBOXVIDEO" is 0x7f041f3eb8c0
[    26.470] (II) LoadModule: "modesetting"
[    26.471] (WW) Warning, couldn't open module modesetting
[    26.471] (II) UnloadModule: "modesetting"
[    26.471] (II) Unloading modesetting
[    26.471] (EE) Failed to load module "modesetting" (module does not exist, 0)
[    26.471] (II) LoadModule: "fbdev"
[    26.471] (WW) Warning, couldn't open module fbdev
[    26.471] (II) UnloadModule: "fbdev"
[    26.471] (II) Unloading fbdev
[    26.471] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    26.471] (II) LoadModule: "vesa"
[    26.471] (WW) Warning, couldn't open module vesa
[    26.471] (II) UnloadModule: "vesa"
[    26.471] (II) Unloading vesa
[    26.471] (EE) Failed to load module "vesa" (module does not exist, 0)
[    26.471] (II) VBoxVideo: guest driver for VirtualBox: vbox
[    26.471] (++) using VT number 1
[    26.471] (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.3.20_OSE
[    26.471] (II) Loading sub module "ramdac"
[    26.471] (II) LoadModule: "ramdac"
[    26.471] (II) Module "ramdac" already built-in
[    26.471] (II) Loading sub module "fb"
[    26.471] (II) LoadModule: "fb"
[    26.472] (II) Loading /usr/lib/xorg/modules/libfb.so
[    26.475] (II) Module fb: vendor="X.Org Foundation"
[    26.476]    compiled for 1.16.3, module version = 1.0.0
[    26.476]    ABI class: X.Org ANSI C Emulation, version 0.4
[    26.476] (II) Loading sub module "shadowfb"
[    26.476] (II) LoadModule: "shadowfb"
[    26.476] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[    26.477] (II) Module shadowfb: vendor="X.Org Foundation"
[    26.477]    compiled for 1.16.3, module version = 1.0.0
[    26.477]    ABI class: X.Org ANSI C Emulation, version 0.4
[    26.477] (II) Loading sub module "vgahw"
[    26.477] (II) LoadModule: "vgahw"
[    26.477] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[    26.479] (II) Module vgahw: vendor="X.Org Foundation"
[    26.479]    compiled for 1.16.3, module version = 0.1.0
[    26.479]    ABI class: X.Org Video Driver, version 18.0
[    26.479] (II) Loading sub module "dri2"
[    26.479] (II) LoadModule: "dri2"
[    26.479] (II) Module "dri2" already built-in
[    26.481] (II) VBoxVideo(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    26.482] (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
[    26.482] (--) VBoxVideo(0): Virtual size is 32000x32000 (pitch 32000)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBoxInitialMode": 20.8 MHz (scaled from 0.0 MHz), 30.8 kHz, 60.0 Hz
[    26.482] (II) VBoxVideo(0): Modeline "VBoxInitialMode"x0.0   20.85  670 672 674 676  508 510 512 514 (30.8 kHz b)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBoxDynamicMode": 20.8 MHz (scaled from 0.0 MHz), 30.8 kHz, 60.0 Hz
[    26.482] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0   20.85  670 672 674 676  508 510 512 514 (30.8 kHz b)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBoxDynamicMode": 20.8 MHz (scaled from 0.0 MHz), 30.8 kHz, 60.0 Hz
[    26.482] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0   20.85  670 672 674 676  508 510 512 514 (30.8 kHz b)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBox-1600x1200": 116.2 MHz (scaled from 0.0 MHz), 72.4 kHz, 60.0 Hz
[    26.482] (II) VBoxVideo(0): Modeline "VBox-1600x1200"x0.0  116.21  1600 1602 1604 1606  1200 1202 1204 1206 (72.4 kHz b)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBox-1440x1050": 91.6 MHz (scaled from 0.0 MHz), 63.4 kHz, 60.0 Hz
[    26.482] (II) VBoxVideo(0): Modeline "VBox-1440x1050"x0.0   91.62  1440 1442 1444 1446  1050 1052 1054 1056 (63.4 kHz b)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBox-1280x960": 74.5 MHz (scaled from 0.0 MHz), 58.0 kHz, 60.0 Hz
[    26.482] (II) VBoxVideo(0): Modeline "VBox-1280x960"x0.0   74.54  1280 1282 1284 1286  960 962 964 966 (58.0 kHz b)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBox-1024x768": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
[    26.482] (II) VBoxVideo(0): Modeline "VBox-1024x768"x0.0   47.83  1024 1026 1028 1030  768 770 772 774 (46.4 kHz b)
[    26.482] (**) VBoxVideo(0):  Built-in mode "VBox-800x600": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
[    26.483] (II) VBoxVideo(0): Modeline "VBox-800x600"x0.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    26.483] (**) VBoxVideo(0):  Built-in mode "VBox-640x480": 18.8 MHz (scaled from 0.0 MHz), 29.2 kHz, 60.0 Hz
[    26.483] (II) VBoxVideo(0): Modeline "VBox-640x480"x0.0   18.84  640 642 644 646  480 482 484 486 (29.2 kHz b)
[    26.483] (II) VBoxVideo(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0
[    26.483] (==) VBoxVideo(0): RGB weight 888
[    26.483] (==) VBoxVideo(0): Default visual is TrueColor
[    26.483] (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
[    26.483] (==) VBoxVideo(0): DPI set to (96, 96)
[    26.483] (--) Depth 24 pixmap format is 32 bpp
[    26.495] (II) VBoxVideo(0): [DRI2] Setup complete
[    26.496] (II) VBoxVideo(0): [DRI2]   DRI driver: vboxvideo
[    26.501] (II) VBoxVideo(0): Requested monitor count: 1
[    26.501] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[    26.501] (II) VBoxVideo(0): Output VBOX0 has no monitor section
[    26.502] (II) VBoxVideo(0): EDID for output VBOX0
[    26.502] (II) VBoxVideo(0): Manufacturer: VBX  Model: 0  Serial#: 33292958
[    26.502] (II) VBoxVideo(0): Year: 1990  Week: 1
[    26.502] (II) VBoxVideo(0): EDID Version: 1.3
[    26.502] (II) VBoxVideo(0): Digital Display Input
[    26.502] (II) VBoxVideo(0): Indeterminate output size
[    26.502] (II) VBoxVideo(0): Gamma: 2.20
[    26.502] (II) VBoxVideo(0): DPMS capabilities: StandBy Suspend Off
[    26.502] (II) VBoxVideo(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[    26.502] (II) VBoxVideo(0): Default color space is primary color space
[    26.502] (II) VBoxVideo(0): First detailed timing is preferred mode
[    26.502] (II) VBoxVideo(0): redX: 0.640 redY: 0.330   greenX: 0.300 greenY: 0.600
[    26.502] (II) VBoxVideo(0): blueX: 0.150 blueY: 0.060   whiteX: 0.312 whiteY: 0.329
[    26.502] (II) VBoxVideo(0): Manufacturer's mask: 0
[    26.502] (II) VBoxVideo(0): Supported detailed timing:
[    26.502] (II) VBoxVideo(0): clock: 20.8 MHz   Image Size:  0 x 0 mm
[    26.502] (II) VBoxVideo(0): h_active: 670  h_sync: 672  h_sync_end 674 h_blank_end 676 h_border: 0
[    26.502] (II) VBoxVideo(0): v_active: 508  v_sync: 510  v_sync_end 512 v_blanking: 514 v_border: 0
[    26.502] (II) VBoxVideo(0): Ranges: V min: 0 V max: 200 Hz, H min: 0 H max: 200 kHz, PixClock max 1005 MHz
[    26.502] (II) VBoxVideo(0): Monitor name: VBOX monitor
[    26.502] (II) VBoxVideo(0): EDID (in hex):
[    26.502] (II) VBoxVideo(0):         00ffffffffffff00585800009e02fc01
[    26.502] (II) VBoxVideo(0):         0100010380000078eeee91a3544c9926
[    26.502] (II) VBoxVideo(0):         0f505400000001010101010101010101
[    26.502] (II) VBoxVideo(0):         01010101010124089e0620fc06100202
[    26.502] (II) VBoxVideo(0):         2200000000000000000000fd0000c800
[    26.502] (II) VBoxVideo(0):         c864000a202020202020000000fc0056
[    26.502] (II) VBoxVideo(0):         424f58206d6f6e69746f720a00000010
[    26.502] (II) VBoxVideo(0):         000a20202020202020202020202000a0
[    26.503] (II) VBoxVideo(0): Printing probed modes for output VBOX0
[    26.503] (II) VBoxVideo(0): Modeline "670x508"x60.0   20.85  670 672 674 676  508 510 512 514 (30.8 kHz Pb)
[    26.503] (II) VBoxVideo(0): Modeline "1600x1200"x60.0  116.21  1600 1602 1604 1606  1200 1202 1204 1206 (72.4 kHz b)
[    26.503] (II) VBoxVideo(0): Modeline "1440x1050"x60.0   91.62  1440 1442 1444 1446  1050 1052 1054 1056 (63.4 kHz b)
[    26.503] (II) VBoxVideo(0): Modeline "1280x960"x60.0   74.54  1280 1282 1284 1286  960 962 964 966 (58.0 kHz b)
[    26.503] (II) VBoxVideo(0): Modeline "1024x768"x60.0   47.83  1024 1026 1028 1030  768 770 772 774 (46.4 kHz b)
[    26.503] (II) VBoxVideo(0): Modeline "800x600"x60.0   29.31  800 802 804 806  600 602 604 606 (36.4 kHz b)
[    26.503] (II) VBoxVideo(0): Modeline "640x480"x60.0   18.84  640 642 644 646  480 482 484 486 (29.2 kHz b)
[    26.503] (II) VBoxVideo(0): Output VBOX0 connected
[    26.503] (II) VBoxVideo(0): Using exact sizes for initial modes
[    26.503] (II) VBoxVideo(0): Output VBOX0 using initial mode 670x508
[    26.504] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    26.504] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    26.511] (==) VBoxVideo(0): DPMS enabled
[    26.511] (--) RandR disabled

And this is the stderr when i ran startx:

X.Org X Server 1.16.3
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.18.1-1-ARCH x86_64
Current Operating System: Linux vbox 3.18.2-2-ARCH #1 SMP PREEMPT Fri Jan 9 07:37:51 CET 2015 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=16a46eed-4db4-43cc-92c1-a12e869795b3 rw quiet
Build Date: 29 December 2014  01:09:58PM

Current version of pixman: 0.32.6
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 26 17:10:58 2015
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Inconsistency detected by ld.so: dl-open.c: 678: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed!
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error

My .xinitrc is:

#!/bin/sh

/usr/bin/VBoxClient-all

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then







    xrdb -merge $sysresources

fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f "$userresources" ]; then







    xrdb -merge "$userresources"

fi

if [ -f "$usermodmap" ]; then
    xmodmap "$usermodmap"
fi

# start some nice programs

if [ -d /etc/X11/xinit/xinitrc.d ] ; then
 for f in /etc/X11/xinit/xinitrc.d/?*.sh ; do
  [ -x "$f" ] && . "$f"
 done
 unset f
fi

twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login

Any ideas? Thanks in advance.

o.O

Offline

#2 2015-01-27 09:27:20

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: Cannot start X on a new install on Virtualbox

Did you install xf86-video-fbdev,  xf86-video-vesa in the vbox ?

$ pacman -Qs fbdev
$ pacman -Qs vesa

do it good first, it will be faster than do it twice the saint wink

Offline

#3 2015-01-27 09:45:53

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

Re: Cannot start X on a new install on Virtualbox

Thanks.

I just tried installed both of them, still cannot start X.

The log is pretty much the same, except for those 2 EEs regarding to fbdev and vesa.

TheSaint wrote:

Did you install xf86-video-fbdev,  xf86-video-vesa in the vbox ?

$ pacman -Qs fbdev
$ pacman -Qs vesa

o.O

Offline

#4 2015-01-27 16:51:31

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: Cannot start X on a new install on Virtualbox

See what you find in ~/.xsession-errors.

$ ls -l ~/.x*
$ ls -l ~/.X*

do it good first, it will be faster than do it twice the saint wink

Offline

#5 2015-01-27 20:06:47

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

Re: Cannot start X on a new install on Virtualbox

There is no .xsession-errors file under ~.

Only thing started with .x is .Xauthority (empty) and .xinitrc (posted before)

I feel like the error is on 

Inconsistency detected by ld.so: dl-open.c: 678: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed!

but i have no clue how it may happen.

TheSaint wrote:

See what you find in ~/.xsession-errors.

$ ls -l ~/.x*
$ ls -l ~/.X*

o.O

Offline

#6 2015-01-27 21:08:19

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: Cannot start X on a new install on Virtualbox

If you leave us without any information, means that you'll be able to solve your problem.
Knowing the files permissions, it might show a clue.
Furthermore, that error where's from ?
Don't you have a ~/.session like this ?

#!/bin/sh

/bin/bash --login -i ~/.xinitrc

do it good first, it will be faster than do it twice the saint wink

Offline

#7 2015-01-27 23:13:00

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

Re: Cannot start X on a new install on Virtualbox

No I don't have ~/.session

The permission on .xinitrc is 

-rw-r--r-- 1 user users 764 Jan 26 16:49 /home/user/.xinitrc

The error I got was on the stderr when I ran startx from the console.

o.O

Offline

#8 2015-01-27 23:19:59

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

Re: Cannot start X on a new install on Virtualbox

I also tried ~/.session with the content you provided.. Still no luck..

Also I noticed this on dmesg:

[   76.339528] ------------[ cut here ]------------
[   76.339547] WARNING: CPU: 3 PID: 322 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x17e/0x190 [drm]()
[   76.339552] No drm_driver.set_busid() implementation provided by vboxvideo_exit [vboxvideo]. Use drm_dev_set_unique() to set the unique name explicitly.
[   76.339555] Modules linked in:
[   76.339558]  cfg80211 rfkill snd_intel8x0 snd_ac97_codec ac97_bus ppdev snd_pcm snd_timer parport_pc snd parport soundcore intel_agp e1000 intel_gtt joydev pcspkr psmouse mousedev serio_raw mac_hid i2c_piix4 processor button ac battery evdev sch_fq_codel vboxvideo(O) drm i2c_core vboxsf(O) vboxguest(O) ext4 crc16 mbcache jbd2 hid_generic usbhid hid sr_mod cdrom ata_generic sd_mod pata_acpi ata_piix atkbd ahci libps2 libahci ohci_pci ohci_hcd libata usbcore usb_common i8042 scsi_mod serio
[   76.339587] CPU: 3 PID: 322 Comm: Xorg.bin Tainted: G           O   3.18.2-2-ARCH #1
[   76.339590] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
[   76.339594]  0000000000000000 0000000005744f7c ffff88007bbf7c98 ffffffff8154f134
[   76.339598]  0000000000000000 ffff88007bbf7cf0 ffff88007bbf7cd8 ffffffff81072bc1
[   76.339602]  0000000000000000 ffff88007bbf7df0 ffff880037995800 ffff88007b306480
[   76.339606] Call Trace:
[   76.339616]  [<ffffffff8154f134>] dump_stack+0x4e/0x71
[   76.339625]  [<ffffffff81072bc1>] warn_slowpath_common+0x81/0xa0
[   76.339631]  [<ffffffff81072c35>] warn_slowpath_fmt+0x55/0x70
[   76.339640]  [<ffffffffa025e37e>] drm_setversion+0x17e/0x190 [drm]
[   76.339648]  [<ffffffffa025de0c>] drm_ioctl+0x2cc/0x680 [drm]
[   76.339656]  [<ffffffffa025e200>] ? drm_noop+0x40/0x40 [drm]
[   76.339664]  [<ffffffff811ce8fe>] ? new_sync_write+0x8e/0xd0
[   76.339671]  [<ffffffff811e23e0>] do_vfs_ioctl+0x2d0/0x4b0
[   76.339678]  [<ffffffff811d1925>] ? __sb_end_write+0x35/0x70
[   76.339684]  [<ffffffff811cf2e2>] ? vfs_write+0x1c2/0x200
[   76.339713]  [<ffffffff811e2641>] SyS_ioctl+0x81/0xa0
[   76.339721]  [<ffffffff811ed5d2>] ? __close_fd+0x82/0xa0
[   76.339729]  [<ffffffff81554ca9>] system_call_fastpath+0x12/0x17
[   76.339733] ---[ end trace c30f1a5dfd66847d ]---

o.O

Offline

#9 2015-01-28 18:37:31

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: Cannot start X on a new install on Virtualbox

The ~/.xinitrc needs execution bit set wink

ls -l .x*
-rwxrwxr-- 1 user users 344 17 apr  2014 .xinitrc
-rwxrwxr-x 1 user users 100  3 feb  2012 .xsession

Then there's a crash on drm yikes

do it good first, it will be faster than do it twice the saint wink

Offline

#10 2015-01-29 14:18:00

rkaretas
Member
Registered: 2015-01-29
Posts: 1

Re: Cannot start X on a new install on Virtualbox

I was having similar trouble, and managed to find another forum thread about this. It suggested that libxcomposite was missing. I checked on my system and did not see it installed. So I added it, and startx began working.

Hope this helps.

Offline

#11 2015-01-31 06:40:10

jan-jan
Member
From: Sydney
Registered: 2015-01-30
Posts: 1

Re: Cannot start X on a new install on Virtualbox

rkaretas wrote:

I was having similar trouble, and managed to find another forum thread about this. It suggested that libxcomposite was missing. I checked on my system and did not see it installed. So I added it, and startx began working.

Hope this helps.

I'm dealing with the exact same issue as the OP on a vanilla installation (arch as guest in Virtualbox, Ubuntu host), identical logs.

Installing libxcomposite fixed the assertion error, X now starts.

(Deleted a bunch of lines that suggested that there is a subsequent error. Found the the reason was a missing command in my .xinitrc)

Last edited by jan-jan (2015-01-31 07:14:18)

Offline

#12 2015-02-01 07:22:56

docwlad
Member
Registered: 2015-02-01
Posts: 1

Re: Cannot start X on a new install on Virtualbox

jan-jan wrote:
rkaretas wrote:

I was having similar trouble, and managed to find another forum thread about this. It suggested that libxcomposite was missing. I checked on my system and did not see it installed. So I added it, and startx began working.

Hope this helps.

I'm dealing with the exact same issue as the OP on a vanilla installation (arch as guest in Virtualbox, Ubuntu host), identical logs.

Installing libxcomposite fixed the assertion error, X now starts.

(Deleted a bunch of lines that suggested that there is a subsequent error. Found the the reason was a missing command in my .xinitrc)

Had the same issue on VirtualBox, and libxcomposite fixed it for me too. Thanks!
As a sidenote, I installed Arch into both VMWare and VirtualBox today: X ran fine in VMWare without the libxcomposite fix (or, at the very least, without me having to explicitly install it. I guess it's possible it got pulled in when I installed the vmware-specific drivers).

Last edited by docwlad (2015-02-01 07:45:01)

Offline

#13 2015-02-01 18:36:02

ruidc
Member
Registered: 2014-10-16
Posts: 9

Re: Cannot start X on a new install on Virtualbox

Man i wasted a lot of time the last few days with this, thanks for the fix. I found i also had an error from the xinitrc calling xterm which was missing, installing xterm fixed it.

Offline

#14 2015-02-02 07:01:12

TheSaint
Member
From: my computer
Registered: 2007-08-19
Posts: 1,523

Re: Cannot start X on a new install on Virtualbox

So the packager should add libxcomposite as dependency to virtualbox, I think.

do it good first, it will be faster than do it twice the saint wink

Offline

#15 2015-02-02 20:44:42

JanVonNebenan
Member
Registered: 2015-02-02
Posts: 12

Re: Cannot start X on a new install on Virtualbox

TheSaint wrote:

So the packager should add libxcomposite as dependency to virtualbox, I think.

https://bugs.archlinux.org/task/43678

(*)
I'm on day 3 with Arch, and this is the first issue I've reported. Would be great if someone more experienced would quickly look over it and add more details if required.

Offline

#16 2015-02-03 19:52:31

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

Re: Cannot start X on a new install on Virtualbox

JanVonNebenan wrote:
TheSaint wrote:

So the packager should add libxcomposite as dependency to virtualbox, I think.

https://bugs.archlinux.org/task/43678

(*)
I'm on day 3 with Arch, and this is the first issue I've reported. Would be great if someone more experienced would quickly look over it and add more details if required.

Thanks! Installing libxcomposite works for me.

o.O

Offline

#17 2015-02-04 10:24:10

ruidc
Member
Registered: 2014-10-16
Posts: 9

Re: Cannot start X on a new install on Virtualbox

JanVonNebenan wrote:
TheSaint wrote:

So the packager should add libxcomposite as dependency to virtualbox, I think.

https://bugs.archlinux.org/task/43678

(*)
I'm on day 3 with Arch, and this is the first issue I've reported. Would be great if someone more experienced would quickly look over it and add more details if required.

It's now been added to the package so should no longer be an issue, thx.

Offline

#18 2015-02-11 21:05:40

jmontano
Member
From: Colombia
Registered: 2013-04-29
Posts: 9

Re: Cannot start X on a new install on Virtualbox

Installing libxcomposite worked for me.

Last edited by jmontano (2015-02-11 21:05:57)

Offline

#19 2015-09-26 09:08:11

francois.e
Member
Registered: 2011-11-02
Posts: 61

Re: Cannot start X on a new install on Virtualbox

This is my case. But libxcomposite does not seem to be an issue. Output of /var/log/Xorg.0.log:

[   807.088] 
X.Org X Server 1.17.2
Release Date: 2015-06-16
[   807.089] X Protocol Version 11, Revision 0
[   807.089] Build Operating System: Linux 4.0.4-2-ARCH x86_64 
[   807.090] Current Operating System: Linux fl-archlinux 4.1.6-1-ARCH #1 SMP PREEMPT Mon Aug 17 08:52:28 CEST 2015 x86_64
[   807.090] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=c685245e-8391-4e79-9c30-9b58e7efa664 rw quiet
[   807.091] Build Date: 17 July 2015  05:38:19PM
[   807.092]  
[   807.092] Current version of pixman: 0.32.8
[   807.093] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[   807.093] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   807.095] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 26 00:59:29 2015
[   807.097] (==) Using config file: "/etc/X11/xorg.conf"
[   807.097] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[   807.099] (==) ServerLayout "X.org Configured"
[   807.099] (**) |-->Screen "Screen0" (0)
[   807.099] (**) |   |-->Monitor "Monitor0"
[   807.100] (**) |   |-->Device "Card0"
[   807.100] (**) |-->Input Device "Mouse0"
[   807.100] (**) |-->Input Device "Keyboard0"
[   807.100] (==) Automatically adding devices
[   807.100] (==) Automatically enabling devices
[   807.100] (==) Automatically adding GPU devices
[   807.101] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   807.101] 	Entry deleted from font path.
[   807.102] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   807.102] 	Entry deleted from font path.
[   807.102] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   807.102] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   807.102] 	Entry deleted from font path.
[   807.102] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   807.102] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[   807.102] 	Entry deleted from font path.
[   807.102] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[   807.102] 	Entry deleted from font path.
[   807.102] 	(Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[   807.102] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[   807.102] 	Entry deleted from font path.
[   807.102] 	(Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[   807.102] (**) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF/,
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/OTF/
[   807.102] (**) ModulePath set to "/usr/lib/xorg/modules"
[   807.102] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[   807.102] (WW) Disabling Mouse0
[   807.102] (WW) Disabling Keyboard0
[   807.102] (II) Loader magic: 0x817d60
[   807.102] (II) Module ABI versions:
[   807.102] 	X.Org ANSI C Emulation: 0.4
[   807.103] 	X.Org Video Driver: 19.0
[   807.103] 	X.Org XInput driver : 21.1
[   807.103] 	X.Org Server Extension : 9.0
[   807.105] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[   807.106] (II) xfree86: Adding drm device (/dev/dri/card0)
[   807.106] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 8 paused 0
[   807.109] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216
[   807.109] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[   807.110] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
[   807.110] (II) LoadModule: "glx"
[   807.111] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   807.126] (II) Module glx: vendor="X.Org Foundation"
[   807.126] 	compiled for 1.17.2, module version = 1.0.0
[   807.126] 	ABI class: X.Org Server Extension, version 9.0
[   807.126] (==) AIGLX enabled
[   807.126] (II) LoadModule: "modesetting"
[   807.126] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   807.127] (II) Module modesetting: vendor="X.Org Foundation"
[   807.127] 	compiled for 1.17.2, module version = 1.17.2
[   807.127] 	Module class: X.Org Video Driver
[   807.127] 	ABI class: X.Org Video Driver, version 19.0
[   807.127] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   807.127] (++) using VT number 1

[   807.127] (--) controlling tty is VT number 1, auto-enabling KeepTty
[   807.127] (WW) Falling back to old probe method for modesetting
[   807.127] (EE) Screen 0 deleted because of no matching config section.
[   807.127] (II) UnloadModule: "modesetting"
[   807.127] (EE) Device(s) detected, but none match those in the config file.
[   807.127] (EE) 
Fatal server error:
[   807.127] (EE) no screens found(EE) 
[   807.127] (EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
[   807.127] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[   807.127] (EE) 
[   807.130] (EE) Server terminated with error (1). Closing log file.

I followed this strategy:
http://www.linuxquestions.org/questions … ll-894681/

# mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old

Last edited by francois.e (2015-10-02 03:38:38)

Offline

#20 2016-03-02 12:26:07

palazzo
Member
Registered: 2016-03-02
Posts: 1

Re: Cannot start X on a new install on Virtualbox

I used to have the same problem as interskh. After following all steps here, I am still unable to startx with the following error in the log:

Floating point exception at address 0xb7258772
Caught signal 8 (floating point exception). Server aborting

Offline

#21 2016-03-10 09:55:32

wma
Member
Registered: 2015-09-07
Posts: 10

Re: Cannot start X on a new install on Virtualbox

palazzo wrote:

I used to have the same problem as interskh. After following all steps here, I am still unable to startx with the following error in the log:

Floating point exception at address 0xb7258772
Caught signal 8 (floating point exception). Server aborting

I was having this problem on a VM running Arch. What fixed it for me was enabling 3D acceleration under the VM's settings.
Sorry, it wasn't that. I've just disabled 3D accel and it still works. Then the only thing I did was restarting the VM, which I assume you've already done.

Last edited by wma (2016-03-10 10:06:26)

Offline

Pages: 1

Board footer

Powered by FluxBB