 |
 |
On Mon, 14 Jul 2008, Malcolm J. Currie wrote: >> That says that the 3D driver support isn't working, so your rendering will >> be done by software. Try: >> >> glxinfo >> glxgears >> >> I'd expect glxgears to report an FPS of thousands, if the hardware >> acceleration is working (mine say 3900 & 5300). > > phaethon> glxinfo > name of display: :0.0 > Xlib: extension "GLX" missing on display ":0.0". > Xlib: extension "GLX" missing on display ":0.0". > Xlib: extension "GLX" missing on display ":0.0". > Error: couldn't find RGB GLX visual > > visual x bf lv rg d st colorbuffer ax dp st accumbuffer ms cav > id dep cl sp sz l ci b ro r g b a bf th cl r g b a ns b eat > > ---------------------------------------------------------------------- > Xlib: extension "GLX" missing on display ":0.0". > Xlib: extension "GLX" missing on display ":0.0". > 0x21 16 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None > Xlib: extension "GLX" missing on display ":0.0". > Xlib: extension "GLX" missing on display ":0.0". > 0x22 16 dc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None > > phaethon> glxgears > Xlib: extension "GLX" missing on display ":0.0". > glxgears: Error: couldn't get an RGB, Double-buffered visual. OK, that's comprehensively stuffed. I expect you've built the software support version of mesa3d (part of the repository for just these occasions). What sort of graphics card does the seat (i.e. screen you're looking at) have? An "lspci" should list it. Peter.