[Solved] Unable to start X (Mali-400 / Odroid U3)

[Enverex]

I've installed all the usual software but I can't get X to start:

$this->bbcode_second_pass_code('', '[ 586.611] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 586.611] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 586.611] compiled for 1.16.3, module version = 0.0.2
[ 586.611] ABI class: X.Org Video Driver, version 18.0
[ 586.611] (II) FBTURBO(0): using /dev/fb0
[ 586.611] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 586.611] (II) FBTURBO(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 586.611] (==) FBTURBO(0): Depth 24, (==) framebuffer bpp 32
[ 586.611] (==) FBTURBO(0): RGB weight 888
[ 586.611] (==) FBTURBO(0): Default visual is TrueColor
[ 586.611] (==) FBTURBO(0): Using gamma correction (1.0, 1.0, 1.0)
[ 586.611] (II) FBTURBO(0): hardware: (video memory: 27648kB)
[ 586.611] (**) FBTURBO(0): Option "fbdev" "/dev/fb0"
[ 586.611] (**) FBTURBO(0): Option "SwapbuffersWait" "true"
[ 586.612] (II) FBTURBO(0): processor: ARM Cortex-A9
[ 586.612] (II) FBTURBO(0): checking modes against framebuffer device...
[ 586.612] (II) FBTURBO(0): checking modes against monitor...
[ 586.612] (--) FBTURBO(0): Virtual size is 1024x768 (pitch 1024)
[ 586.612] (**) FBTURBO(0): Built-in mode "current"
[ 586.612] (==) FBTURBO(0): DPI set to (96, 96)
[ 586.612] (II) Loading sub module "fb"
[ 586.612] (II) LoadModule: "fb"
[ 586.612] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 586.613] (II) Module fb: vendor="X.Org Foundation"
[ 586.613] compiled for 1.16.3, module version = 1.0.0
[ 586.613] ABI class: X.Org ANSI C Emulation, version 0.4
[ 586.613] (==) Depth 24 pixmap format is 32 bpp
[ 586.613] (EE) FBTURBO(0): mmap fbmem: Invalid argument
[ 586.613] (EE) FBTURBO(0): mapping of video memory failed
[ 586.613] (EE)
Fatal server error:
[ 586.613] (EE) AddScreen/ScreenInit failed for driver 0')

There are a few mentions of this on the issue tracker for Arch Linux ARM but they are all closed claiming that it's fixed upstream. I'm on the latest versions of everything and the problem is still happening to clearly it's not fixed.

Anyone else experiencing this or know any way around it?

[WarheadsSE]

Perhaps it _was_ fixed, and has broken, again?

[Enverex]

Possibly. I can't be the only one running Arch with XOrg though yet I've seen no other mention of this issue.

[Enverex]

Fixed. I should have been using the armsoc X11 driver and not FBTurbo.