From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 58556] MacBook Pro 5, 1 with nVidia 9400m and 9600m, scrambled screen
Date: Wed, 24 Jul 2013 13:17:29 +0000 [thread overview]
Message-ID: <bug-58556-8800-dgaIDQJVEY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-58556-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2428 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=58556
--- Comment #7 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Hi Joanand
(In reply to comment #0)
> Resolution for kernels < 3.4.9: I made use of gpupwr to disable the discrete
> adapter and then loaded nouveau (without any parameters). The system was
> "programmed" to use 9400m as it starts. This worked quite fine over long
> time.
>
"Worked" with our without acceleration ?
> Temporary resolution for 3.7.1: Use MacOSX to change the default adapter to
> the one which is "not" desired. Reboot, load nouveau with noaccel=1 (now
> screen gets scrambled), switch to the other device (in my case "echo DIGD >
> /sys/kernel/debug/vgaswitcheroo/switch"). Voila you have a readable screen.
Did you had the chance to narrow down what caused the change (<3.4.9 vs 3.7.1)
? It may be due to nouveau, vgaswitcheroo and/or other kernel driver
(In reply to comment #6)
> (In reply to comment #5)
> > Great find Matyas
> >
> > If you're interested in cutting short the sequence you can forcepost the
> > card, thus it should have you the suspend/resume trick. Use
> > nouveau.config=NvForcePost=1
> >
> > Curious if the above will give you acceleration or only a working
> > output/monitor
> > (ie. try it with and without noaccel=1)
> >
> > Cheers
>
> Hi,
> On my MBP, if I do not use noaccel=1, then the whole system crashes.
>
> I have tried NvForcePost=1 with noaccel, the result was a switched off
> screen, but system seems to boot.
> With accel, screen switches off and crashes.
>
> Is there any config which would activate accel for 9400 but no accel for
> 9600? This would be very helpful for me.
>
> Thanks.
There has been a brief discussion what is the best way to handle this (passing
nouveau params to specific card, disabling certain card etc.) although
implementation may be far off ;(
Meanwhile add a hack for your card by checking the PCI and returning early
rather than initialising the card - not sure which location is better
nouveau_drm_probe or nouveau_drm_load. Keep in mind to keep is symmetric (ie.
handle the case in nouveau_drm_remove/nouveau_drm_unload)
Your code will look something similar to
if ((pdev->bus == xx) &&
(pdev->dev == xx) &&
(pdev->func == xx)) {
return 0; // you can also try return -E*
}
Cheers
Emil
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3607 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2013-07-24 13:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 7:23 [Bug 58556] New: MacBook Pro 5, 1 with nVidia 9400m and 9600m, scrambled screen bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-58556-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-02-01 18:31 ` [Bug 58556] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-17 21:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-23 21:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-23 22:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-23 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 11:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 13:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-07-24 13:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 17:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-24 22:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-25 17:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-06 13:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 4:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 13:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-22 19:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 17:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-23 21:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-13 14:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-03 22:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-18 20:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-12-09 11:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-05 13:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-07 8:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-07 23:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-08 21:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-08 23:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-09 10:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-09 20:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 10:14 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 10:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-17 10:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-24 6:53 ` 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-58556-8800-dgaIDQJVEY@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox