X Failing to Start

edowino · 01-16-2018, 04:03 AM

Greetings gurus,

I have installed Oracle Linux 6.4 on an Oracle VM (XEN) hypervisor. I was intending to do an oracle DB installation on the virtual machine and would therefore need X forwarding. I did a minimal installation then subsequently installed the xinit, xauth & X Window System.

When I'm trying to run startx it terminates with the error

waiting for X server to shut down error setting MTRR (base = 0xf0000000, size = 0x00400000, type = 1) Invalid argument (22)

The Xorg.0.log shows me this

Quote:

[ 1745.345] compiled for 1.17.4, module version = 1.0.0
[ 1745.345] ABI class: X.Org Server Extension, version 9.0
[ 1745.345] (==) AIGLX enabled
[ 1745.345] (==) Matched cirrus as autoconfigured driver 0
[ 1745.345] (==) Matched modesetting as autoconfigured driver 1
[ 1745.345] (==) Matched fbdev as autoconfigured driver 2
[ 1745.345] (==) Matched vesa as autoconfigured driver 3
[ 1745.345] (==) Assigned the driver to the xf86ConfigLayout
[ 1745.345] (II) LoadModule: "cirrus"
[ 1745.346] (WW) Warning, couldn't open module cirrus
[ 1745.346] (II) UnloadModule: "cirrus"
[ 1745.346] (II) Unloading cirrus
[ 1745.346] (EE) Failed to load module "cirrus" (module does not exist, 0)
[ 1745.346] (II) LoadModule: "modesetting"
[ 1745.346] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 1745.346] (II) Module modesetting: vendor="X.Org Foundation"
[ 1745.346] compiled for 1.17.4, module version = 1.17.4
[ 1745.346] Module class: X.Org Video Driver
[ 1745.347] ABI class: X.Org Video Driver, version 19.0
[ 1745.347] (II) LoadModule: "fbdev"
[ 1745.347] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[ 1745.347] (II) Module fbdev: vendor="X.Org Foundation"
[ 1745.347] compiled for 1.17.4, module version = 0.4.3
[ 1745.347] Module class: X.Org Video Driver
[ 1745.347] ABI class: X.Org Video Driver, version 19.0
[ 1745.347] (II) LoadModule: "vesa"
[ 1745.347] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 1745.347] (II) Module vesa: vendor="X.Org Foundation"
[ 1745.347] compiled for 1.17.4, module version = 2.3.4
[ 1745.347] Module class: X.Org Video Driver
[ 1745.347] ABI class: X.Org Video Driver, version 19.0
[ 1745.347] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 1745.347] (II) FBDEV: driver for framebuffer: fbdev
[ 1745.347] (II) VESA: driver for VESA chipsets: vesa
[ 1745.347] (--) using VT number 8

[ 1745.372] (EE) open /dev/dri/card0: No such file or directory
[ 1745.372] (WW) Falling back to old probe method for modesetting
[ 1745.372] (EE) open /dev/dri/card0: No such file or directory
[ 1745.372] (II) Loading sub module "fbdevhw"
[ 1745.372] (II) LoadModule: "fbdevhw"
[ 1745.372] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[ 1745.373] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 1745.373] compiled for 1.17.4, module version = 0.0.2
[ 1745.373] ABI class: X.Org Video Driver, version 19.0
[ 1745.373] (EE) Unable to find a valid framebuffer device
[ 1745.373] (WW) Falling back to old probe method for fbdev

I'm a newbie and I would appreciate all the help I towards resolving this problem

Emerson · 01-16-2018, 08:49 AM

I understand you want to run an X application remotely? Then I do not understand why you want to run X locally. Or you have two different goals?

edowino · 01-16-2018, 12:56 PM

Quote:

Originally Posted by Emerson

I understand you want to run an X application remotely? Then I do not understand why you want to run X locally. Or you have two different goals?

Was trying different options to see whether I can get the GUI interface up & running but haven't been lucky, just needed a pointer on what may be wrong

Emerson · 01-16-2018, 03:30 PM

Is this in corporate environment? Why not ask your IT guy to set it up then. Otherwise, you do know X consists of two parts, client and server? They do not have to be run in same machine, you can run an X client in a headless machine (your VM) and have it connect to an X server in another machine (your host system for instance). Anyhow, all GUI troubles can be avoided by using CLI for setup and management.