Bug 6565 - genericx86: Xorg log error "AIGLX: reverting to software rendering"
Summary: genericx86: Xorg log error "AIGLX: reverting to software rendering"
Status: RESOLVED WONTFIX
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-runtime (show other bugs)
Version: 1.7
Hardware: Other x86
: Medium normal
Target Milestone: 1.7 M3
Assignee: Stoicescu Cornel
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-07-22 11:53 UTC by Stoicescu Cornel
Modified: 2014-07-23 16:30 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
Xorg.0.log (18.86 KB, text/plain)
2014-07-22 11:53 UTC, Stoicescu Cornel
no flags Details
Xorg conf files (5.16 KB, text/plain)
2014-07-23 07:56 UTC, Stoicescu Cornel
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stoicescu Cornel 2014-07-22 11:53:10 UTC
Created attachment 2048 [details]
Xorg.0.log

STATUS: FAILED
BUILD: master:1dcdd877c7946be4c0b1203deb14e2f842f9d0c2
ENVIRONMENT: generic-x86 on Atom N2600
STEPS TO REPRODUCE: 
  
 target must have x11-base in image features
run command " cat /var/log/Xorg.0.log | grep -v "(EE) error," | grep -v "PreInit" | grep -v "evdev:" | grep -v "glx" | grep "(EE)" "



EXPECTED OUTCOME: 
  
 Exit status must be 1

Actual outcome:

(EE) AIGLX: reverting to software rendering
Comment 1 Bruce Ashfield 2014-07-22 12:54:14 UTC
I sent this to Nitin, since I don't have the h/w in question
Comment 2 Darren Hart 2014-07-22 16:23:41 UTC
Which board is this? Just the CPU isn't sufficient.

A few lines of context is helpful:

[3618483.074] (II) modesetting(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[3618483.075] (==) modesetting(0): DPMS enabled
[3618483.573] (--) RandR disabled
[3618483.599] (II) AIGLX: Screen 0 is not DRI2 capable
[3618483.599] (EE) AIGLX: reverting to software rendering

From what I could tell, the only drivers attempted were modesetting, fb, and vesa. Intel was not attempted. Does intel_drv exist on the disk image?

If handy, can you also post the contents of /etc/X11/xorg.conf if it exists?
Comment 3 Stoicescu Cornel 2014-07-23 07:54:59 UTC
 - The specifications for the board can be found here:
http://www.jetway.com.tw/jw/ipcboard_view.asp?productid=945&proname=NF36-2800%20/%20NF36-2600/NF36-2550

This board is used because it's a 32 bit only machine.

 - Regarding Xorg.conf, I cannot find it. Here is a quick search of the file system:
root@genericx86:~# find / | grep -i "xorg.*conf"
/usr/share/X11/xorg.conf.d
/usr/share/X11/xorg.conf.d/10-evdev.conf
/usr/share/X11/xorg.conf.d/50-synaptics.conf
/usr/share/X11/xorg.conf.d/10-quirks.conf

I will attach the contents of these files.

 - Here is the output from lsmod:
root@genericx86:~# lsmod
Module                  Size  Used by
snd_hda_codec_hdmi     34238  1
snd_hda_codec_realtek    46238  1
snd_hda_codec_generic    47767  1 snd_hda_codec_realtek
snd_hda_intel          30825  0
r8169                  54478  0
snd_hda_codec          91276  4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
snd_pcm                75123  3 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel
snd_timer              16706  1 snd_pcm
uvesafb                22887  1

Also, I searched the file system for intel_drv:

/usr/lib/xorg/modules/drivers/intel_drv.so
/usr/src/kernel/drivers/gpu/drm/i915/intel_drv.h
/usr/src/kernel/drivers/gpu/drm/gma500/psb_intel_drv.h
Comment 4 Stoicescu Cornel 2014-07-23 07:56:06 UTC
Created attachment 2052 [details]
Xorg conf files
Comment 5 Darren Hart 2014-07-23 16:30:48 UTC
The N2600 is a Cedar Trail Atom CPU using PVR graphics (closed binary driver). Closing bug. People wanting accelerated graphics on this board will need to use the official cedartrail BSP from IOTG. (meta-cedartrail in meta-intel)