<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - MacBook Pro 5,1 with nVidia 9400m and 9600m, scrambled screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=58556#c27">Comment # 27</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - MacBook Pro 5,1 with nVidia 9400m and 9600m, scrambled screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=58556">bug 58556</a> from <a class="email" href="mailto:krestfallen@arcor.de" title="krestfallen@arcor.de">krestfallen@arcor.de</a> <pre>(In reply to <a href="show_bug.cgi?id=58556#c25">comment #25</a>) > Booting with both adapters enabled (9600 is the boot adapter), EFI-stub and > EFIFB, loading nouveau without acceleration:leads to scrambled screen. The > resolution is native 1440x900. > > Booting with both adapters enabled (9600 is the boot adapter) EFI-stub and > EFIFB, loading nouveau with acceleration, screen/adapter is frozen. System > seems to "hang"/lag. doesn't efifb wants to pick the 9400M? efifb pics the framebuffer base at 0xC0010000 from efifb.c: [M_MBP_5_1] = { "mbp5,1", 0xc0010000, 2048 * 4, 1440, 900 } these are the values for each gpu: 9400M: 0xC0010000 9600M GT: 0xB0030000 i tried nouveau yesterday and couldn't even load the kernel. with the nvidia driver it's even possible to switch to the desired gpu on boot. but with the 9400m screening and logging out afterwards and back in (no reboot) the screen also gets scrambled, slow and unstable. perhaps it's something with the gmux values or memory allocation!?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>