public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Kapshuk <alexander.kapshuk@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Failed to load driver: Nouveau
Date: Mon, 28 Aug 2017 19:41:27 +0300	[thread overview]
Message-ID: <CAJ1xhMXt=-QxKoG_hS_7ouxTKNj5C3cmQqnynC6e+RF40Nsd7w@mail.gmail.com> (raw)
In-Reply-To: <CALtB3Ddh1dBJT5umd9KFuGvtvzOZYKPdAYEHuM3QPcREH0BvLw@mail.gmail.com>

On Mon, Aug 28, 2017 at 6:30 PM, IceAmber <iceamber2015@gmail.com> 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


  reply	other threads:[~2017-08-28 16:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-27  8:23 [gentoo-user] Failed to load driver: Nouveau IceAmber
2017-08-27  9:52 ` Adam Carter
2017-08-27  9:57   ` IceAmber
2017-08-27 10:04     ` Adam Carter
2017-08-27 11:27       ` IceAmber
2017-08-27 14:45         ` Alexander Kapshuk
2017-08-27 14:49           ` Alexander Kapshuk
2017-08-27 16:54             ` Alexander Kapshuk
2017-08-27 17:24               ` IceAmber
2017-08-27 17:59                 ` Alexander Kapshuk
2017-08-28 11:41                   ` IceAmber
2017-08-28 11:48                     ` Alexander Kapshuk
2017-08-28 14:00                       ` IceAmber
2017-08-28 14:13                         ` Alexander Kapshuk
2017-08-28 14:17                         ` David Abbott
2017-08-28 14:36                           ` IceAmber
2017-08-28 14:38                             ` IceAmber
2017-08-28 14:57                               ` Alexander Kapshuk
2017-08-28 15:09                                 ` IceAmber
2017-08-28 15:11                                 ` Alexander Kapshuk
2017-08-28 15:30                                   ` IceAmber
2017-08-28 16:41                                     ` Alexander Kapshuk [this message]
2017-08-29  9:35                                       ` Alexander Kapshuk
2017-08-29 13:22                                         ` IceAmber
2017-08-29 13:58                                           ` J. Roeleveld
2017-08-29 14:28                                         ` Alexander Kapshuk
2017-08-29 14:58                                           ` IceAmber
2017-08-29 15:14                                             ` Alexander Kapshuk
2017-08-29 15:20                                               ` IceAmber
2017-09-06 22:46                           ` Marc Joliet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ1xhMXt=-QxKoG_hS_7ouxTKNj5C3cmQqnynC6e+RF40Nsd7w@mail.gmail.com' \
    --to=alexander.kapshuk@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox