1843 2011-12-19 00:18:07 +0000 Error screen when I input "clear" in the terminal 2012-04-25 04:01:02 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-configuration unspecified E-Menlow x86 RESOLVED FIXED Medium normal 1.3 1 ningx.ma tom.zanussi dvhart hongnax.xu jessica.zhang jiajun.xu sgw yilongx.y.sun yp.bsp.watcher yp.watcher --- --- --- oldest_to_newest 17718 0 ningx.ma 2011-12-19 00:18:07 +0000 Tree/Branch: Poky/1.2_M1 Commit: b806f726b1db2cb605869c1022ef727c1110255b Meta: Master Commit: b6d5d9a3b06caf578103a04dc5fcf5e476343205 with 20111213-4 images for emenlow, boot system successful and then launch the Terminal, error screen when I input "clear" in the Terminal The error log of these failure cases show: ###### it: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. Try adjusting the vblank_mode configuration parameter. GL_RENDERER = Mesa DRI Intel(R) GMA500 20081116 - 5.0.1.0046 x86/MMX/SSE2 GL_VERSION = 2.0 Mesa 7.4 GL_VENDOR = Tungsten Graphics, Inc ###### 18213 1 dvhart 2012-01-18 11:19:17 +0000 Is this reproducable on other platforms? 18231 2 yilongx.y.sun 2012-01-18 17:02:27 +0000 The command "clear" run well on other platforms. 20719 3 tom.zanussi 2012-04-19 14:02:27 +0000 With current master of both poky and meta-intel, I'm not seeing this problem - 'clear' clears the screen fine. poky: 1a03b7dfba464fde770ba69b618427d13e0a3b8b meta-intel: f75f9b6f68473eb0efac802409608f8389be0030 20831 4 ningx.ma 2012-04-24 02:47:38 +0000 This issue still exist in denzil testing(20120418-1 image). Tree/Branch: denzil Commit id:2c3d4f5beee8f57a74244495511b9294df1085ea Meta branch:master Commit id:f75f9b6f68473eb0efac802409608f8389be0030 20833 5 ningx.ma 2012-04-24 06:49:14 +0000 This issue still exist in denzil testing(20120418-1 image). Tree/Branch: denzil Commit id:2c3d4f5beee8f57a74244495511b9294df1085ea Meta branch:master Commit id:f75f9b6f68473eb0efac802409608f8389be0030 20120418-1 enemlow image URL: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120418-1 20857 6 tom.zanussi 2012-04-25 04:01:02 +0000 Apparently the problem is that mesa-demos builds and installs a demo program called 'clear' into /usr/bin on emenlow, which is what gets run instead of the system 'clear'. mesa-demos is included only when enabling tools-testapps. The reason it worked for me is that the build I tested didn't enable tools-testapps. The solution is to test with a build that doesn't include tools-testapps. The real fix probably would be to modify mesa-demos to not install into /usr/bin but rather into a separate demo apps directory.