[Eee Pad Transformer Android Development] jrohwer:
Looking by the above, you definitely do not have hw acceleration working, but software rasterisation by mesa (see the line GL_RENDERER above. When I run es2_info, I get:

EGL_VERSION = 1.4
EGL_VENDOR = NVIDIA
EGL_EXTENSIONS = EGL_NV_system_time EGL_KHR_config_attribs EGL_KHR_surfaceless_context EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_ANDROID_blob_cache EGL_KHR_vg_parent_image EGL_NV_perfmon EGL_KHR_lock_surface EGL_KHR_fence_sync EGL_NV_sync EGL_NV_depth_nonlinear EGL_NV_post_sub_buffer EGL_NV_post_convert_rounding EGL_NV_native_query EGL_KHR_stream EGL_KHR_stream_fifo EGL_KHR_stream_producer_eglsurface EGL_KHR_stream_consumer_gltexture EGL_KHR_stream_cross_process_fd EGL_EXT_create_context_robustness EGL_IMG_context_priority EGL_NV_3dvision_surface EGL_KHR_reusable_sync EGL_NV_stream_sync EGL_NV_coverage_sample EGL_NV_coverage_sample_resolve
EGL_CLIENT_APIS = OpenGL_ES2 OpenGL_ES OpenGL OpenVG
GL_VERSION: OpenGL ES 2.0 14.01002
GL_RENDERER: NVIDIA Tegra
GL_EXTENSIONS:
GL_OES_rgb8_rgba8, GL_OES_EGL_sync, GL_OES_surfaceless_context,
GL_OES_fbo_render_mipmap, GL_NV_depth_nonlinear, GL_NV_draw_path,
GL_NV_texture_npot_2D_mipmap, GL_OES_EGL_image, GL_OES_EGL_image_external,
GL_OES_vertex_half_float, GL_OES_mapbuffer, GL_NV_draw_buffers,
GL_NV_multiview_draw_buffers, GL_EXT_Cg_shader, GL_EXT_packed_float,
GL_OES_texture_half_float, GL_EXT_texture_array,
GL_OES_compressed_ETC1_RGB8_texture, GL_EXT_texture_compression_latc,
GL_NV_texture_compression_latc, GL_EXT_texture_compression_dxt1,
GL_EXT_texture_compression_s3tc, GL_NV_texture_compression_s3tc,
GL_EXT_texture_filter_anisotropic, GL_NV_get_tex_image, GL_NV_read_buffer,
GL_NV_shader_framebuffer_fetch, GL_NV_copy_image,
GL_NV_fbo_color_attachments, GL_EXT_bgra, GL_EXT_texture_format_BGRA8888,
GL_EXT_unpack_subimage, GL_NV_pack_subimage,
GL_NV_texture_compression_s3tc_update, GL_NV_read_depth,
GL_NV_read_stencil, GL_NV_uniform_buffer_object, GL_NV_map_buffer_range,
GL_EXT_robustness, GL_OES_standard_derivatives,
GL_NV_EGL_stream_consumer_external, GL_EXT_separate_shader_objects,
GL_NV_copy_buffer, GL_NV_3dvision_settings, GL_EXT_debug_marker,
GL_EXT_debug_label, GL_EXT_texture_storage, GL_NV_pixel_buffer_object,
GL_NV_framebuffer_blit, GL_NV_explicit_attrib_location,
GL_NV_coverage_sample

Note amongs others that GL_RENDERER is NVIDIA Tegra.

The issue is that both mesa and the NVIDIA Tegra drivers provide the libs libEGL.so, libGLESv1_CM.so, and libGLESv2.so. If you install both the mesa drivers and the Nvidia ones, then only one of these gets found, this depens on the how ld-config is set up.So in your case obviously the mesa lib gets found first and not the Nvidia ones.

Possible fixes (try individually or all)

Remove the mesa egl and gles drivers.

In /usr/lib, do (as root)

ln -s libEGL.so.1 libEGL.so
ln -s libGLESv1_CM.so.1 libGLESv1_CM.so
ln -s libGLESv2.so.1 libGLESv2.so
cd arm-linux-gnueabihf
ln -s ../libEGL.so
ln -s ../libGLESv1_CM.so
ln -s ../libGLESv2.so
ldconfig

Restart X.

Run es2_info again to confirm. (The fact that xorg.log shows the nvidia tegra driver loaded does not mean that the nvidia GLES libs are actually called).

You can test the performance with es2gears (also part of mesa-utils-extra). With the mesa driver, I get about 55 FPS, with the nvidia driver I get around 320 FPS :D

BTW Ubuntu has packaged the Nvidia drivers as nvidia-tegra (in Ubuntu raring this is only the tegra 16.2 driver but it works fine nevertheless. I use it as it sets up everything correctly, and figures out the gles and egl libs with update-alternatives, so the right libs get called. Dunno if Debian packages nvidia-tegra as well.

The segfault may well be due to the fact that you are calling the mesa libs, not the nvidia ones. For KDE, you can run kwin_gles as I explained in my reply on the rootbind thread.

Let us know your progress :)

---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------

I haven't tried but I use a bluetooth mouse without problems on my linux installation (Ubuntu raring). I see no reason why the bt keyboard should not work.