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