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 27501] MacBook Pro 5, x unable to boot [NV96 + NVAC]
Date: Sun, 17 Aug 2014 10:02:53 +0000	[thread overview]
Message-ID: <bug-27501-8800-nb68d5NG9E@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-27501-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 730 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=27501

--- Comment #28 from Pierre Moreau <pierre.morrow-GANU6spQydw@public.gmane.org> ---
I've made some progress on this bug, enabling Nouveau to be loaded with
acceleration enabled. However, X is **absolutely not** usable: complete garbage
screen, lots of Nouveau errors, only action available is power down the
computer (or reboot). But for using Nouveau with acceleration in console mode,
it works fine.

There are (at least) two main problems:

*   9400M acceleration is broken (resulting in Nouveau locking up on boot);
*   it seems there is a lockup when starting a working X with both cards
enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1476 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-08-17 10:02 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 22:43 [Bug 27501] New: nVidia 9600M GT (Macbook Pro current model) is unable to boot bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-27501-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-04-06 22:44   ` [Bug 27501] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-07  4:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-08 10:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-10  9:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-15  9:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-05 23:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-03-11  2:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-03 13:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-18 14:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-06 13:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-08  0:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-08  0:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-07-08 12:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-23 20:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-29  5:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-11-14 10:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-06 18:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-17 11:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-17 15:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-02-19 10:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-03-20  5:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-03-20 17:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-25  1:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-25  4:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-07-26  1:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-17 22:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 13:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21  4:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21  4:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21  4:21   ` [Bug 27501] MacBook Pro 5, x unable to boot [NV96 + NVAC] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 10:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-09-14  9:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-15 11:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-15 11:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-16 11:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-23 17:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-24 17:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-24 17:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-24 17:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-25 11:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-25 11:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-28  1:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-28  1:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-28  9:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-03 14:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-03 20:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-03 20:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-03 21:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-03 23:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-04  8:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-10 17:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-12 13:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-08 20:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-20 17:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-21 17:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-21 18:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-21 21:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-21 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-24 21:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-24 21:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02  8:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 14:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 21:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-16  0:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-12 12:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-05 22:42   ` 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-27501-8800-nb68d5NG9E@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.