All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 26193] New: nouveau falls back to NoAccel on 9400M
Date: Sun, 24 Jan 2010 06:10:12 -0800 (PST)	[thread overview]
Message-ID: <bug-26193-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=26193

           Summary: nouveau falls back to NoAccel on 9400M
           Product: xorg
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: bjt23-HmMyXyqgL2CVc3sceRu5cw@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=32792)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=32792)
Xorg.0.log

I'm seeing this in my xorg log:

(EE) NOUVEAU(0): Error creating GPU channel: -16
(EE) NOUVEAU(0): Error initialising acceleration.  Falling back to NoAccel

I assume this means no EXA and no 2D accel, which is sad :( .

I'm on a MacBook Pro 13" with GeForce 9400M (NVac).  Using nouveau-drm from the
kernel tree with git rev eeec3a1ecd703d3a32fe223274d2a77686030d78 (built out of
tree for kernel 2.6.32-gentoo-r2), and xf86-video-nouveau git rev
2630a1553d560ce2c7391bc103d4a543f7d3d0da.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2010-01-24 14:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24 14:10 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-26193-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-01-24 14:10   ` [Bug 26193] nouveau falls back to NoAccel on 9400M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-24 14:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-24 14:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-24 14:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-24 14:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-24 23:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-25  0:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-25  8:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-25  8:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-25  8:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-25  9:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-26  8:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-26 16:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-26 17:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-27  8:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-27  8:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-27 11:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-29 17:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-01-29 18:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-22  5:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-02-22 12:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-26193-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.