Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Raspberry Pi & vc4 (opengl) glxgears fps
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM
View previous topic :: View next topic  
Author Message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Wed Aug 24, 2016 3:10 pm    Post subject: Raspberry Pi & vc4 (opengl) glxgears fps Reply with quote

Today I tested mesa-9999 with vc4 enabled on my Raspberry Pi 2 and to my astonishment I found a nice new
long awaited eselect opengl option:
[quote]
rp pi # eselect opengl list
Available OpenGL implementations:
[1] raspberrypi *
[2] xorg-x11

8) 8) 8)

I immediately emerged mesa-progs and run "vblank_mode=0 glxgears". Anyone else tried this? I get approx. 88 fps.
Back to top
View user's profile Send private message
Yamakuzure
Advocate
Advocate


Joined: 21 Jun 2006
Posts: 2280
Location: Adendorf, Germany

PostPosted: Thu Aug 25, 2016 7:47 am    Post subject: Reply with quote

If you have "raspberrypi" in the eselect list of opengl, it is using the driver from media-libs/raspberrypi-userland.

The vc4 driver from mesa is a Gallium driver and would not show up there.

I am using mesa-11.2.2 on a Raspberry Pi 3, the current mesa-12.0.1 is broken for me.

glxinfo would then show, in the "Extended renderer info" section:
Code:
    Vendor: Broadcom (0x14e4)
    Device: VC4 (0xffffffff)
    Version: 11.2.2
(...)
OpenGL renderer string: Gallium 0.4 on VC4
btw: I had to uninstall raspberrypi-userland, because X always hung with their driver.

Another note:
With the Gallium driver, glxgears shows ~726 FPS on my machine (Although RPi 3 and not 2). I think you are using swrast, the software rasterizer, and not VC4, because until I got VC4 working, I had ~88FPS, too.

You could try "vblank_mode=0 glxgears -info" and look what renderer it uses.
_________________
Important German:
  1. "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
  2. "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
Back to top
View user's profile Send private message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Sat Aug 27, 2016 12:53 pm    Post subject: Reply with quote

Quote:

The vc4 driver from mesa is a Gallium driver and would not show up there.

So I should switch back to "xorg-x11"
:(

wth is that llvm stuff ?

Quote:

Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0xffffffff)
Device: llvmpipe (LLVM 3.7, 128 bits) (0xffffffff)
Version: 12.1.0
Accelerated: no
Video memory: 860MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.0

OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.7, 128 bits)


Do you have any special setup? I dont know how to enable the gallium or disable sw-raster
Back to top
View user's profile Send private message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Sat Aug 27, 2016 1:16 pm    Post subject: Reply with quote

I use the raspberry pi 7" Touchscreen, maybe thats the reason for the software rendering?

/var/log/Xorg.0.log
Quote:

(II) AIGLX: Screen 0 is not DRI2 capable
[ 113.233] (EE) AIGLX: reverting to software rendering
[ 114.186] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 114.189] (II) AIGLX: Loaded and initialized swrast
[ 114.189] (II) GLX: Initialized DRISWRAST GL provider for screen 0

Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


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

PostPosted: Sat Aug 27, 2016 4:05 pm    Post subject: Reply with quote

Yamakuzure,

I guess that's a 32 bit install on a Pi3 ?
_________________
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
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Sat Aug 27, 2016 5:37 pm    Post subject: Reply with quote

@Yamakuzure, what kernel do you use?
Back to top
View user's profile Send private message
Yamakuzure
Advocate
Advocate


Joined: 21 Jun 2006
Posts: 2280
Location: Adendorf, Germany

PostPosted: Tue Aug 30, 2016 10:09 am    Post subject: Reply with quote

@Neddy: Yes, it is a 32bit install. There are too many issues on 64bit (and it is *impossible* to get the VC4 to work on 64bit, because the driver parts, both kernel and mesa, simply do not work in 64bit mode), so I gave up on my 64bit Gentoo project and am running 32bit.
( The nearest I got was this )

@dasPaul : sys-kernel/raspberrypi-sources-4.4.9999 with slight adaptations to the defconfig

And for the ''7 TouchScreen, I do not thinks so. There might be a different issue:

media-libs/mesa-12.0.1 is broken for VC4!

It is a dev release, so I masked in on my RPi3 and am using 11.2.2 now, which works fine. Until I realized this, I had the same "Screen 0 is not DRI2 capable" which you have. However, the live ebuild works, so the issue should be resolved in the next mesa-12.x release. But while Building Mesa for VC4 wiki enables the shader cache, the mesa ebuild forcefully disables it. I am currently building a variation of mesa-11.2.2 with swrast disabled and the shader cache enabled.

Edith remembered: "llvmpipe" is the software rasterizer aka "swrast". ;-)
_________________
Important German:
  1. "Aha" - German reaction to pretend that you are really interested while giving no f*ck.
  2. "Tja" - German reaction to the apocalypse, nuclear war, an alien invasion or no bread in the house.
Back to top
View user's profile Send private message
Mouski
n00b
n00b


Joined: 25 Jun 2016
Posts: 21

PostPosted: Mon Sep 05, 2016 4:42 pm    Post subject: Reply with quote

Mesa 12.0.2 is out > http://www.phoronix.com/scan.php?page=news_item&px=Mesa-12.0.2-Released
Back to top
View user's profile Send private message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Thu Sep 08, 2016 5:43 pm    Post subject: Reply with quote

I emerged mesa-12.0.2, uninstalled userland, but I still have sw renderer and ~80 fps. My kernel is 4.6.3-v7. Dont know if this is important but I loaded
the vc4 module manualy and added "avoid_warnings=2" to config.txt.

Maybe I should downgrade the kernel to sys-kernel/raspberrypi-sources-4.4.9999. :?
Back to top
View user's profile Send private message
Mouski
n00b
n00b


Joined: 25 Jun 2016
Posts: 21

PostPosted: Thu Sep 08, 2016 7:00 pm    Post subject: Reply with quote

If all it's installed correctly, you don't need to load manually any module. Try lsmod to see if vc4 is loaded without any configuration.
Back to top
View user's profile Send private message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Thu Sep 08, 2016 7:15 pm    Post subject: Reply with quote

Do you have anything else special in your config.txt regarding vc4?
Back to top
View user's profile Send private message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Fri Sep 09, 2016 9:21 am    Post subject: Reply with quote

I just emerged raspberrypi-sources-4.4.9999
and compiled with this script:

Code:
#!/bin/bash

function make_kern {
KERNEL=kernel7
if [ ! -f .config ]; then make bcm2709_defconfig;fi && \
make CC="distcc armv7a-hardfloat-linux-gnueabi-gcc" -j12 -l3 zImage && \
make CC="distcc armv7a-hardfloat-linux-gnueabi-gcc" -j12 -l3 modules && \
make CC="distcc armv7a-hardfloat-linux-gnueabi-gcc" -j12 -l3 dtbs && \
sudo make CC="distcc armv7a-hardfloat-linux-gnueabi-gcc" -j12 -l3 modules_install && \
sudo cp -v arch/arm/boot/dts/*.dtb /boot/ && \
sudo cp -v  arch/arm/boot/dts/overlays/*.dtb* /boot/overlays/ && \
sudo cp -v  arch/arm/boot/dts/overlays/README /boot/overlays/ && \
sudo scripts/mkknlimg arch/arm/boot/zImage /boot/$KERNEL.img && \
echo "...done!" || echo "ERROR"
}

time make_kern


I also added "dtoverlay=vc4-kms-v3d,cma-128" to config.txt.
Then after reboot I saw the rainbow-square, then nothing for a while, then the touchscreen came back but it stucked in the boot process after starting the network interfaces and froze completely. I will try to connect a HDMI display and see if I can grab any debug informations before it freezes.
Back to top
View user's profile Send private message
Mouski
n00b
n00b


Joined: 25 Jun 2016
Posts: 21

PostPosted: Fri Sep 09, 2016 1:24 pm    Post subject: Reply with quote

I just added the overlay in my config.txt, nothing else. Maybe try updating firmware.
Back to top
View user's profile Send private message
KAMIKAZE_
Guru
Guru


Joined: 09 Oct 2003
Posts: 309
Location: Riga, Latvia

PostPosted: Fri Sep 09, 2016 2:24 pm    Post subject: Reply with quote

someone, please share OS image for PRi 3 :)
_________________
-=[powered by Gentoo]=-
Back to top
View user's profile Send private message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Fri Sep 09, 2016 3:48 pm    Post subject: Reply with quote

What I also don't understant is if I've built my kernel and files have been copied into a clean /boot directory
the following files are in there (cmdline.txt & config.txt I wrote myself):

Code:
ls -l /boot
insgesamt 4276
-rwxr-xr-x 1 root root   14494  9. Sep 17:29 bcm2709-rpi-2-b.dtb
-rwxr-xr-x 1 root root   15164  9. Sep 17:29 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root     142 20. Jul 11:28 cmdline.txt
-rwxr-xr-x 1 root root    1722  9. Sep 13:09 config.txt
-rwxr-xr-x 1 root root 4331948  9. Sep 17:30 kernel7.img
drwxr-xr-x 2 root root    8192  9. Sep 17:30 overlays


for the firmware I just git-cloned the latest. When I look into firmware/boot there are those files:

Code:
ls -lah
insgesamt 20M
drwxr-xr-x 3 pi   users 4.0K  9. Sep 15:05 .
drwxr-xr-x 8 pi   users 4.0K  9. Sep 15:05 ..
-rw-r--r-- 1 root root   14K  9. Sep 15:05 bcm2708-rpi-b.dtb
-rw-r--r-- 1 root root   14K  9. Sep 15:05 bcm2708-rpi-b-plus.dtb
-rw-r--r-- 1 root root   14K  9. Sep 15:05 bcm2708-rpi-cm.dtb
-rw-r--r-- 1 root root   15K  9. Sep 15:05 bcm2709-rpi-2-b.dtb
-rw-r--r-- 1 root root   16K  9. Sep 15:05 bcm2710-rpi-3-b.dtb
-rw-r--r-- 1 root root   15K  9. Sep 15:05 bcm2710-rpi-cm3.dtb
-rw-r--r-- 1 pi   users  18K  9. Jul 13:53 bootcode.bin
-rw-r--r-- 1 pi   users  19K  9. Jul 13:53 COPYING.linux
-rw-r--r-- 1 root root  2.5K  9. Sep 15:05 fixup_cd.dat
-rw-r--r-- 1 root root  6.4K  9. Sep 15:05 fixup.dat
-rw-r--r-- 1 root root  9.5K  9. Sep 15:05 fixup_db.dat
-rw-r--r-- 1 root root  9.5K  9. Sep 15:05 fixup_x.dat
-rw-r--r-- 1 root root  4.1M  9. Sep 15:05 kernel7.img
-rw-r--r-- 1 root root  4.0M  9. Sep 15:05 kernel.img
-rw-r--r-- 1 pi   users 1.5K  9. Jul 13:53 LICENCE.broadcom
drwxr-xr-x 2 pi   users 4.0K  9. Sep 15:05 overlays
-rw-r--r-- 1 root root  607K  9. Sep 15:05 start_cd.elf
-rw-r--r-- 1 root root  4.8M  9. Sep 15:05 start_db.elf
-rw-r--r-- 1 root root  2.7M  9. Sep 15:05 start.elf
-rw-r--r-- 1 root root  3.8M  9. Sep 15:05 start_x.elf


What files do I need to copy from the firmware folder into boot? All files that do not already exist in /boot? Because overwriting the kernel and overlays from the firmware folder would not make much sense to me.
Back to top
View user's profile Send private message
dasPaul
Apprentice
Apprentice


Joined: 14 Feb 2012
Posts: 243
Location: Dresden

PostPosted: Sun Sep 11, 2016 7:20 am    Post subject: Reply with quote

I managed to get kernel 4.4.9999 working. Still no vc4 but more questions:

Did you use mesa-11.2.2 from portage or did you compile by yourself and what use flags/configuration options do you have enabled?
Do you somewhere have opengl flag enabled?
Do I need egl,gles1,gles2?

Kernel 4.4.9999 gets now loaded but screen does strange things during boot.
vc4 module also gets automaticaly loaded:

lsmod:
Code:
Module                  Size  Used by
binfmt_misc             6388  1
usbip_host             13307  0
usbip_core              5257  1 usbip_host
8192cu                560049  0
cfg80211              427855  1 8192cu
rfkill                 16037  2 cfg80211
i2c_dev                 5859  0
mt7650u_sta           903837  1
panel_raspberrypi_touchscreen     2978  0
vc4                   100447  0
drm_kms_helper        101028  2 vc4
drm_mipi_dsi            8702  2 vc4,panel_raspberrypi_touchscreen
evdev                  11396  0
snd_soc_bcm2835_i2s     6354  0
drm                   262436  4 vc4,drm_kms_helper,panel_raspberrypi_touchscreen
joydev                  9024  0
snd_soc_core          125885  1 snd_soc_bcm2835_i2s
syscopyarea             2945  1 drm_kms_helper
snd_pcm_dmaengine       3391  1 snd_soc_core
sysfillrect             3443  1 drm_kms_helper
sysimgblt               2069  1 drm_kms_helper
snd_pcm                75762  2 snd_soc_core,snd_pcm_dmaengine
fb_sys_fops             1309  1 drm_kms_helper
snd_timer              19224  1 snd_pcm
snd                    51908  3 snd_soc_core,snd_timer,snd_pcm
i2c_bcm2708             4834  0
bcm2835_gpiomem         3040  0
spi_bcm2835             6678  0
bcm2835_wdt             3225  0
rpi_ft5406              2898  0
uio_pdrv_genirq         3164  0
uio                     8000  1 uio_pdrv_genirq
rpi_backlight           2064  0
ipv6                  347530  26


firmware is
Code:
Sep  7 2016 14:47:38
Copyright (c) 2012 Broadcom
version 1f1070f16206004c8f2172144ec8f167db6c742f (clean) (release)


dmesg | grep drm
Code:
[    6.230249] [drm] Initialized drm 1.1.0 20060810
[    6.393344] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4])
[    6.394231] vc4-drm soc:gpu: bound 3f700000.dsi (ops vc4_dsi_ops [vc4])
[    6.394309] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4])
[    6.394469] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.394596] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.394743] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops vc4_crtc_ops [vc4])
[    6.394838] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4])
[    6.396261] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    6.396276] [drm] Driver supports precise vblank timestamp query.
[    6.396345] vc4-drm soc:gpu: No connectors reported connected with modes
[    6.396363] [drm] Cannot find any crtc or sizes - going 1024x768
[    6.411680] vc4-drm soc:gpu: fb0:  frame buffer device


boot/cmdline.txt
Code:
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 rootfstype=ext4 smsc95xx.turbo_mode=N elevator=deadline rootwait

boot/config.txt
Code:

lcd_rotate=2
dtoverlay=vc4-kms-v3d,cma-128
gpu_mem=128
dtparam=i2c_arm=on
dtparam=i2s=on
dtparam=spi=on
dtparam=i2c1=on
gpu_mem=16
max_usb_current=1

arm_freq=1000
core_freq=500
sdram_freq=500
over_voltage=2
force_turbo=1


Xorg.0.log:
Code:
X.Org X Server 1.18.3
Release Date: 2016-04-04
[    53.063] X Protocol Version 11, Revision 0
[    53.063] Build Operating System: Linux 4.4.20-raspberrypi-v7+ armv7l Gentoo
[    53.063] Current Operating System: Linux rp 4.4.20-raspberrypi-v7+ #2 SMP Sat Sep 10 09:07:58 CEST 2016 armv7l
[    53.064] Kernel command line: cma=128M@128M dma.dmachans=0x7f35 bcm2708_fb.fbwidth=800 bcm2708_fb.fbheight=480 bcm2709.boardrev=0x2a21041 bcm2709.serial=0xe841dacb smsc95xx.macaddr=B8:27:EB:41:DA:CB bcm2708$
[    53.065] Build Date: 10 September 2016  06:27:05PM
[    53.065]
[    53.065] Current version of pixman: 0.34.0
[    53.065]    Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
[    53.066] Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    53.068] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Sep 10 19:43:57 2016
[    53.071] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    53.072] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    53.075] (==) No Layout section.  Using the first Screen section.
[    53.075] (==) No screen section available. Using defaults.
[    53.075] (**) |-->Screen "Default Screen Section" (0)
[    53.075] (**) |   |-->Monitor "<default monitor>"
[    53.081] (==) No monitor specified for screen "Default Screen Section".
        Using a default monitor configuration.
[    53.081] (==) Automatically adding devices
[    53.081] (==) Automatically enabling devices
[    53.081] (==) Automatically adding GPU devices
[    53.081] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    53.091] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[    53.091]    Entry deleted from font path.
[    53.091] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[    53.091]    Entry deleted from font path.
[    53.091] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[    53.091]    Entry deleted from font path.
[    53.092] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[    53.092]    Entry deleted from font path.
[    53.092]    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[    53.093] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[    53.093]    Entry deleted from font path.
[    53.093]    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[    53.093] (==) FontPath set to:
        /usr/share/fonts/misc/
[    53.093] (==) ModulePath set to "/usr/lib/xorg/modules"
[    53.093] (II) The server relies on udev to provide the list of input devices.
        If no devices become available, reconfigure udev or disable AutoAddDevices.
[    53.094] (II) Loader magic: 0x1e8e18
[    53.094] (II) Module ABI versions:
[    53.094]    X.Org ANSI C Emulation: 0.4
[    53.094]    X.Org Video Driver: 20.0
[    53.094]    X.Org XInput driver : 22.1
[    53.094]    X.Org Server Extension : 9.0
[    53.096] (II) xfree86: Adding drm device (/dev/dri/card0)
[    53.097] (II) no primary bus or device found
[    53.098]    falling back to /sys/devices/platform/soc/soc:gpu/drm/card0
[    53.098] (II) LoadModule: "glx"
[    53.102] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    53.181] (II) Module glx: vendor="X.Org Foundation"
[    53.181]    compiled for 1.18.3, module version = 1.0.0
[    53.181]    ABI class: X.Org Server Extension, version 9.0
[    53.181] (==) AIGLX enabled
[    53.181] (==) Matched modesetting as autoconfigured driver 0
[    53.181] (==) Matched fbdev as autoconfigured driver 1
[    53.181] (==) Assigned the driver to the xf86ConfigLayout
[    53.182] (II) LoadModule: "modesetting"
[    53.182] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[    53.186] (II) Module modesetting: vendor="X.Org Foundation"
[    53.186]    compiled for 1.18.3, module version = 1.18.3
[    53.186]    Module class: X.Org Video Driver
[    53.186]    ABI class: X.Org Video Driver, version 20.0
[    53.186] (II) LoadModule: "fbdev"
[    53.187] (WW) Warning, couldn't open module fbdev
[    53.187] (II) UnloadModule: "fbdev"
[    53.187] (II) Unloading fbdev
[    53.187] (EE) Failed to load module "fbdev" (module does not exist, 0)
[    53.187] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    53.187] (--) using VT number 7

[    53.198] (II) modeset(0): using drv /dev/dri/card0
[    53.198] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    53.199] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[    53.199] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    53.199] (==) modeset(0): RGB weight 888
[    53.199] (==) modeset(0): Default visual is TrueColor
[    53.199] (II) modeset(0): No glamor support in the X Server
[    53.199] (II) modeset(0): ShadowFB: preferred NO, enabled NO
[    53.199] (II) modeset(0): Output HDMI-1 has no monitor section
[    53.200] (II) modeset(0): Output DSI-1 has no monitor section
[    53.200] (II) modeset(0): EDID for output HDMI-1
[    53.200] (II) modeset(0): EDID for output DSI-1
[    53.200] (II) modeset(0): Printing probed modes for output DSI-1
[    53.200] (II) modeset(0): Modeline "800x480"x180.2   83.33  800 861 863 907  480 487 489 510 (91.9 kHz eP)
[    53.200] (II) modeset(0): Output HDMI-1 disconnected
[    53.201] (II) modeset(0): Output DSI-1 connected
[    53.201] (II) modeset(0): Using exact sizes for initial modes
[    53.201] (II) modeset(0): Output DSI-1 using initial mode 800x480 +0+0
[    53.201] (II) modeset(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[    53.201] (==) modeset(0): DPI set to (96, 96)
[    53.201] (II) Loading sub module "fb"
[    53.201] (II) LoadModule: "fb"
[    53.201] (II) Loading /usr/lib/xorg/modules/libfb.so
[    53.209] (II) Module fb: vendor="X.Org Foundation"
[    53.209]    compiled for 1.18.3, module version = 1.0.0
[    53.209]    ABI class: X.Org ANSI C Emulation, version 0.4
[    53.209] (==) Depth 24 pixmap format is 32 bpp
[    53.230] (==) modeset(0): Backing store enabled
[    53.230] (==) modeset(0): Silken mouse enabled
[    53.234] (II) modeset(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[    53.238] (==) modeset(0): DPMS enabled
[    53.245] (--) RandR disabled
[    53.251] (II) AIGLX: Screen 0 is not DRI2 capable
[    53.251] (EE) AIGLX: reverting to software rendering
[    54.221] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[    54.225] (II) AIGLX: Loaded and initialized swrast
[    54.225] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    54.226] (II) modeset(0): Setting screen physical size to 211 x 127
[    54.530] (II) config/udev: Adding input device FT5406 memory based driver (/dev/input/event0)
[    54.530] (**) FT5406 memory based driver: Applying InputClass "evdev touchscreen catchall"
[    54.530] (II) LoadModule: "evdev"
[    54.530] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[    54.543] (II) Module evdev: vendor="X.Org Foundation"
[    54.543]    compiled for 1.18.3, module version = 2.10.3
[    54.543]    Module class: X.Org XInput Driver
[    54.543]    ABI class: X.Org XInput driver, version 22.1
[    54.543] (II) Using input driver 'evdev' for 'FT5406 memory based driver'
[    54.543] (**) FT5406 memory based driver: always reports core events
[    54.543] (**) evdev: FT5406 memory based driver: Device: "/dev/input/event0"
[    54.544] (--) evdev: FT5406 memory based driver: Vendor 0 Product 0
[    54.544] (--) evdev: FT5406 memory based driver: Found absolute axes
[    54.544] (--) evdev: FT5406 memory based driver: Found absolute multitouch axes
[    54.544] (II) evdev: FT5406 memory based driver: No buttons found, faking one.
[    54.544] (--) evdev: FT5406 memory based driver: Found x and y absolute axes
[    54.544] (--) evdev: FT5406 memory based driver: Found absolute touchscreen
[    54.544] (II) evdev: FT5406 memory based driver: Configuring as touchscreen
[    54.544] (**) evdev: FT5406 memory based driver: YAxisMapping: buttons 4 and 5
[    54.544] (**) evdev: FT5406 memory based driver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[    54.544] (**) Option "config_info" "udev:/sys/devices/virtual/input/input0/event0"
[    54.544] (II) XINPUT: Adding extended input device "FT5406 memory based driver" (type: TOUCHSCREEN, id 6)
[    54.545] (II) evdev: FT5406 memory based driver: initialized for absolute axes.
[    54.545] (**) FT5406 memory based driver: (accel) keeping acceleration scheme 1
[    54.545] (**) FT5406 memory based driver: (accel) acceleration profile 0
[    54.545] (**) FT5406 memory based driver: (accel) acceleration factor: 2.000
[    54.545] (**) FT5406 memory based driver: (accel) acceleration threshold: 4
[    54.547] (II) config/udev: Adding input device FT5406 memory based driver (/dev/input/mouse0)
[    54.547] (II) No input driver specified, ignoring this device.
[    54.547] (II) This device may have been added with another device file.
[   132.352] (II) evdev: FT5406 memory based driver: Close
[   132.352] (II) UnloadModule: "evdev"
[   132.401] (II) Server terminated successfully (0). Closing log file.

eselect mesa list:
Code:
i915 (Intel 915, 945)
i965 (Intel GMA 965, G/Q3x, G/Q4x, HD)
r300 (Radeon R300-R500)
r600 (Radeon R600-R700, Evergreen, Northern Islands)
sw (Software renderer)
  [1]   classic
  [2]   gallium *


glxinfo
Code:
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: VMware, Inc. (0xffffffff)
    Device: llvmpipe (LLVM 3.7, 128 bits) (0xffffffff)
    Version: 11.2.2
    Accelerated: no
    Video memory: 861MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 3.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0


I am out of ideas.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on ARM All times are GMT
Page 1 of 1

 
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