On Tue, Aug 29, 2017 at 12:35 PM, Alexander Kapshuk <[email protected]> wrote: > On Mon, Aug 28, 2017 at 7:41 PM, Alexander Kapshuk > <[email protected]> wrote: >> On Mon, Aug 28, 2017 at 6:30 PM, IceAmber <[email protected]> wrote: >>> here is the result >>> >>> iceamber@localhost:~ $ lsmod | grep nouveau >>> nouveau 1507328 2 >>> i2c_algo_bit 16384 1 nouveau >>> drm_kms_helper 118784 1 nouveau >>> ttm 77824 1 nouveau >>> drm 282624 5 nouveau,ttm,drm_kms_helper >>> agpgart 32768 3 nouveau,ttm,drm >>> led_class 16384 3 input_leds,hid_sony,nouveau >>> >>> >> >> Your nouveau kernel driver seems to be OK. That's good news. >> The bad news is we're back to square one. >> >> It was glxinfo, which is a part of x11-apps/mesa-progs, that generated >> the original error message. >> So, perhaps, it is a mesa problem. >> >> Can you please try this command line and see what it outputs: >> LIBGL_DEBUG=verbose glxgears > > This reference may help better debug your problem: > https://nouveau.freedesktop.org/wiki/MesaDrivers/
The Mesa drivers wiki page above says: nv50 and nvc0 Make sure you are using at least Mesa 7.11, but please consider using latest stable release. You have to use at least the 2.6.38 kernel or you will encounter memory corruptions. For nvc0 hardware it's recommended to use at least kernel 3.1. Bug reports for nv50 and nvc0 can be submitted by following the general reporting guidelines. Please, also follow the About bugs and problems section above. What version is your media-libs/mesa? Is this the first time you've run into this trouble using the nouveau driver? What driver did you use before with this piece of hardware proprietary nvidia one, or nouveau?
