Created attachment 357816 [details] kmscon with mesa-9.1.6 ===== Background info ===== Mesa compiled with: +(classic egl gbm gles1 gles2 ntpl pax_kernel pic video_cards_i965 python_single_target_python2_7 python_targets_python2_7) sys-apps/kmscon compiled with: +(drm gles2 optimizations) GPU is Sandy Bridge HD300 Steps to trigger: launch kmscon with "kmscon --font-engine=8x16 --drm --hwaccel --verbose" mesa 9.1.6 and 9.2.0-rc2 works good, error introduced at 9.2.0. Note: problem goes away if kmscon is started without hwaccel. Attaching kmscon stderr output with various mesa versions.
kmscon with mesa-9.2.0 kmscon --font-engine=8x16 --drm --hwaccel --verbose [0000.000000] NOTICE: kmscon Revision kmscon-7 Sep 4 2013 05:36:36 [0000.000165] INFO: conf: reading config file /etc/kmscon/kmscon.conf [0000.014626] NOTICE: vt: using tty /dev/tty8 [0000.041158] INFO: drm_shared: new drm device via /dev/dri/card0 [0000.065973] INFO: video: new device 0x6854080eb0 [0000.067000] INFO: ignoring video device /dev/fb0 on seat seat0 as it is a DRM-fbdev device [0001.491054] INFO: video: new display 0x685408bd10 [0001.491204] INFO: drm_shared: display 0x685408bd10 DPMS is ON [0001.493011] INFO: uterm_drm3d_video: activating display 0x685408bd10 to 1366x768 [0001.518584] INFO: drm_shared: setting DPMS of display 0x685408bd10 to ON [0001.537870] WARNING: gl_shader: cannot compile shader: 0:34(15): error: no precision specified this scope for type `float' 0:35(15): error: no precision specified this scope for type `float' 0:37(14): error: no precision specified this scope for type `vec2' 0:38(14): error: no precision specified this scope for type `vec3' 0:39(14): error: no precision specified this scope for type `vec3' 0:43(7): error: no precision specified this scope for type `vec2' 0:44(8): error: no precision specified this scope for type `float' 0:45(7): error: no precision specified th [0001.537968] ERROR: terminal: cannot set text-renderer parameters [0003.151101] INFO: terminating due to caught signal 2 [0003.151342] INFO: video: free device 0x6854080eb0 [0003.151388] INFO: uterm_drm3d_video: deactivating display 0x685408bd10 [0003.151703] INFO: video: free display 0x685408bd10 [0003.151766] INFO: uterm_drm3d_video: free drm video device 0x6854080eb0 [0003.163441] INFO: exiting
Created attachment 357818 [details] mesa-9.2.0, kmscon without hwaccel
Corrections: -GPU is Sandy Bridge HD300 +GPU is Sandy Bridge HD3000 - media-libs/mesa-9.2.0 regression from mesa-9.2.0_rc2 on Intel, GLES2 related triggered by sys-apps/kmscon + media-libs/mesa-9.2.0 regression from mesa-9.2.0_rc1 on Intel, GLES2 related triggered by sys-apps/kmscon rc2 doesn't seem to work too, was under impression that it was OK, trying out rc1.
Created attachment 357820 [details] mesa-9.2.0-rc2 kmscon started with "kmscon --verbose --font-engine=8x16 --drm --hwaccel"
Created attachment 357822 [details] mesa-9.2.0-rc2 kmscon started with "kmscon --verbose --font-engine=8x16 --drm"
Created attachment 357824 [details] mesa-9.2.0_rc1 kmscon started with "kmscon --verbose --font-engine=8x16 --drm --hwaccel"
Summary: bug introduced somewhere between mesa-9.2.0_rc1 and mesa-9.2.0_rc2, will try to bisect exact commit.
"Regression" caused by mesa commit c9a7d6950b9f58171864cd066552e9496cc8220a Is the error caused by kmscon or mesa? commit in mesa says "This is required by the spec"
Can confirm that this happens with radeon hardware too. Tested with mesa-9.2.0
Fixed by kmscon-git
