Description of problem: When I boot the F17 RC4 install medium on my MacBook Pro (3,1) with nVidia GeForce 8600M GT graphics using GRUB2 and EFI I get severe screen flicker. It appears as though the backlight is actually turning on and off several (about 20-30) times a second. Version-Release number of selected component (if applicable): How reproducible: I'd imagine it would be the same on any MacBook with similar nVidia graphics. Steps to Reproduce: 1. Boot off of Fedora 17 install medium via EFI.
Forgot to mention, this happens in both the framebuffer and X11.
Assigning to Matt. Matt, I'm not sure what data you need in these cases, can you advise? Thanks!
I can also confirm this on my MacBook Pro 3,1. Would be happy to supply any data required. (Fedora 17 full release + latest software updates.)
Two more things: 1. Looking at the screen, I don't really think it's the backlight causing it anymore, but rather the lcd itself flickering on and off. 2. I'm 90% sure this is a KMS issue. I can boot Ubuntu with efifb as long as nomodeset is on. If I try and boot with efifb and KMS enabled, I just get a blank screen. Obviously nouveaufb doesn't work with KMS disabled (At least thats the vibe I got from their wiki), and I get no video at all (rather, it stays frozen at the last GRUB screen) when I boot Fedora with nomodeset. Booting with efifb + nomodeset isn't a usable solution though because there's still no way to get an accelerated X server running (nVidia binary doesn't seem to like EFI, nouveau needs KMS.)
Also, one more thing: This doesn't affect external VGA monitors connected via a DVI to VGA adaptor. (I'm unable to try an external DVI-D monitor, perhaps someone else could?)
I can confirm there is no flicker on an external monitor with a DVI connection at both ends.
I can also recreate if useful. Similar setup.
I have the same issue, on the same machine as OP (MBP 3,1). As mentioned in comment #4, I can't boot with nVidia proprietary driver. I'd be glad to bring any info needed. Is someone has a temporary work around it would be greatly appreciated.
FWIW, it seems to disappear after a suspend/wake cycle.
My workaround was to go to Ubuntu booted via CSM. Although if sleep/wake fixes it I may go back to Fedora.
Wow, the suspend trick does seem to work for me as well. It doesn't totally eliminate the flicker, but it does remove about 95%+ of it.
Same bug, on MacbookPro 3,1. Followed these directions to install the nvidia drivers (using the akmod once, then tried kmod next time). Both stall after grub. http://www.if-not-true-then-false.com/2012/fedora-17-nvidia-guide/ I can supply any logfiles / conf files required.
I am using Fedora 17 for the first time. EFI boot on a Macbook Pro 3,1 with the same severe screen flickering. The suspend/resume workaround does work for me aswell. But I'd very much appreciate if some genius fixes this! :) I have also tried installing proprietary drivers, but I ended up with a buggy boot process, i.e. the boot stops at a text screen of something like "Loaded Display Manager".
I'm assuming no one really knows what causes this?
This bug is being closed because it has been set needinfo for more than 2 weeks without a response. If this is still an issue, please reopen and reply with the requested information.
Many people on this issue have shown a desire to provide information and have done so as much as possible. No one who might attempt to resolve this issue has asked for what specific information should be provided. The issue should not be closed.
Justin, the 'needinfo' was set on a member of the *development team*, not a reporter. The onus is on your side here. Re-opening. (the needinfo was on matt).
Sorry about that, it was a blind close on bugs that had been needinfo for a period of time.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Reporters, is this affecting F18 or F19?
I can confirm F18 (tested from KDE spin) and F19 (XFCE spin) are affected.
Updating, then. Thanks.
Hi all, Booting Fedora 19's with the additional kernel argument: nouveau.config=NvForcePost=1 fixes this issue on my MacBook Pro 3,1. No need to suspend/resume anymore!
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
This is still present in F19 3.11.1-200.fc19 and still fixed by: nouveau.config=NvForcePost=1 Although for some reason in F19 X11 is no longer capable of auto-configuring (Need to manually create a xorg.conf file) on my MBP either, but that's another bug for another time.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.