Starting X on Rpi2B?

[dspahn]

I have an RPi2B that I am trying to start X on. All I did was a basic stage 3 install, then emerge the packages for X and KDE. I set XDM to use KDM and tried startx. No dice, so I tried starting XDM and I'm dropping to a console login with the graphics mde even loading. Here is my Xorg.0.log:

Code: Select all

[    31.220]
X.Org X Server 1.16.4
Release Date: 2014-12-20
[    31.220] X Protocol Version 11, Revision 0
[    31.220] Build Operating System: Linux 4.1.12-v7+ armv7l Gentoo
[    31.220] Current Operating System: Linux RPiGen2 4.1.12-v7+ #1 SMP PREEMPT Wed Nov 11 18:16:49 EST 2015 armv7l
[    31.221] Kernel command line: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 bcm2708_fb.fbheight=984 bcm2709.boardrev=0x2a01041 bcm2709.serial=0xea446515 smsc95xx.macaddr=B8:27:EB:44:65:15 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=250000000 vc_mem.mem_base=0x3dc00000 vc_mem.mem_size=0x3f000000  root=/dev/mmcblk0p3 rw rootwait console=ttyAMA0,115200 console=tty1 selinux=0 plymouth.enable=0 smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200 elevator=noop
[    31.221] Build Date: 13 November 2015  02:03:34AM
[    31.221]
[    31.221] Current version of pixman: 0.32.8
[    31.221]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    31.221] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    31.222] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Nov 16 13:42:28 2015
[    31.253] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    31.268] (==) No Layout section.  Using the first Screen section.
[    31.268] (==) No screen section available. Using defaults.
[    31.268] (**) |-->Screen "Default Screen Section" (0)
[    31.268] (**) |   |-->Monitor "<default monitor>"
[    31.276] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    31.276] (==) Automatically adding devices
[    31.276] (==) Automatically enabling devices
[    31.277] (==) Automatically adding GPU devices
[    31.286] (WW) The directory "/usr/share/fonts/misc/" does not exist.
[    31.286]    Entry deleted from font path.
[    31.286] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[    31.286]    Entry deleted from font path.
[    31.286] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[    31.286]    Entry deleted from font path.
[    31.286] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[    31.286]    Entry deleted from font path.
[    31.287] (WW) The directory "/usr/share/fonts/100dpi/" does not exist.
[    31.287]    Entry deleted from font path.
[    31.287] (WW) The directory "/usr/share/fonts/75dpi/" does not exist.
[    31.287]    Entry deleted from font path.
[    31.287] (==) FontPath set to:

[    31.287] (==) ModulePath set to "/usr/lib/xorg/modules"
[    31.287] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    31.289] (II) Loader magic: 0x1e8e88
[    31.289] (II) Module ABI versions:
[    31.289]    X.Org ANSI C Emulation: 0.4
[    31.289]    X.Org Video Driver: 18.0
[    31.289]    X.Org XInput driver : 21.0
[    31.289]    X.Org Server Extension : 8.0
[    31.290] (II) no primary bus or device found
[    31.293] (II) LoadModule: "glx"
[    31.324] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    31.468] (II) Module glx: vendor="X.Org Foundation"
[    31.468]    compiled for 1.16.4, module version = 1.0.0
[    31.469]    ABI class: X.Org Server Extension, version 8.0
[    31.469] (==) AIGLX enabled
[    31.469] (==) Matched modesetting as autoconfigured driver 0
[    31.469] (==) Matched fbdev as autoconfigured driver 1
[    31.469] (==) Assigned the driver to the xf86ConfigLayout
[    31.469] (II) LoadModule: "modesetting"
[    31.471] (WW) Warning, couldn't open module modesetting
[    31.471] (II) UnloadModule: "modesetting"
[    31.471] (II) Unloading modesetting
[    31.472] (EE) Failed to load module "modesetting" (module does not exist, 0)
[    31.472] (II) LoadModule: "fbdev"
[    31.473] (WW) Warning, couldn't open module fbdev
[    31.473] (II) UnloadModule: "fbdev"
[    31.473] (II) Unloading fbdev
[    31.473] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    31.473] (EE) No drivers available.
[    31.475] (EE)
Fatal server error:
[    31.475] (EE) no screens found(EE)
[    31.475] (EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
[    31.475] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[    31.476] (EE)
[    31.476] (EE) Server terminated with error (1). Closing log file.

Looking at this, is it saying I need to activate KMS and rebuild the kernel?
I appreciate your help!

[NeddySeagoon]

dspahn,

Code: Select all

[    31.473] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    31.473] (EE) No drivers available. 

I'm not sure what video driver the Pi2 needs but framebuffer is a good one to have to get you going anyway.
That's adding fbdev to your VIDEO_CARDS and emerge -1 xf86-video-fbdev

Since its a Pi, that emerge will save you rebuilding lots of things that won't change.
fbdev is just a chunk of RAM that the CPU can draw in to get pictures on the screen.

There may be an accelerated driver for the Pi2 too. fbdev isn't it.

[dspahn]

I went back and checked- looks like I left the VIDEO_CARDS line out of my make.conf AND I forgot to add a few INPUT_DEVICE flags as well- It will take a while to emerge, but I'll post back when it's done- X should be up and running at that point. Thanks for noticing that!

[dspahn]

OK, I have had some seriously weird things happen this time around- I have installed Gentoo on a number of computers and other devices and never seen packages just not install... After I added the VIDEO_CARDS and INPUT_DEVICES, I emerged xorg-drivers (Which it said were all New packages) I chalked it up to error on my part. I tried logging in to KDE using KDM, after installing kde-meta... and startkde could not be found! also libplasmaclock and plasmaworkspace as well as startkde were pulled in as dependencies when I emerged startkde, and all three were listed as New installs. How did my machine spend the past 5 days compiling 582 packages and miss those> And why is it that sometimes when I emerge I'll get a list of Digest authentication failures listing Changelog files (Always the Changelog- no variant in the filename besides the actual path to the changelog)? Is there something particular to the ARMV7 that I am doing wrong? I'll take any advice! Thanks!

[Leio]

For some sort of extra acceleration, there is xf86-video-fbturbo, which is a fork from xf86-video-fbdev that optimizes things for ARM NEON and some DMA things for Mali and I believe also for RPi VC4.
On top of that semi-proprietary graphics stack, there's also wayland acceleration on top of using dispmanx overlays in weston, which makes moving toplevel windows around really fast.


With the new incoming stack with KMS and everything, you'll be able to use modesetting driver instead, which is included with xorg-server and possibly get some XRENDER acceleration via glamor. That's the http://dri.freedesktop.org/wiki/VC4/ stuff that's cooking. It is not ready for general use, just if really into tinkering with things. Linux kernel 4.4 has basic 2D support for this and if all goes well 4.5 will have basic 3D support, with an upcoming mesa 11.1 or 11.2 having the userspace updates merged (there is an earlier version in already, but I hear the kernel interface changed before it gets merged mainline). More bits and pieces about this on http://anholt.livejournal.com/ - as said, not quite there yet for normal use, but something to look out for from 2016.

I don't know about your further issues desribed here beyond the original post. Sound like generic package management issues, not ARM specific.