1. Please describe the problem: >>> MacBookPro (2015) fails to boot after upgrading to latest kernel versions and leaves me with a black screen. If I hit ESC and choose the first (oldest) kernel version, which came along with the live image, it works. Choosing any newer kernel version, it shows a black screen without showing the typical loading animation. As I have a LUKS encrypted disk, I would expect a password field, but that is not shown when starting the latest kernel version. As a side note: I have been installing Linux Fedora on the same MacBookPro for 4 years and I've never had any issue related with booting. 2. What is the Version-Release number of the kernel: >>>> These ones don't work: 5.7.11 and 5.8.4. The one that still works is kernel-5.6.6-300.fc32.x86_64 (that came with live image) 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : >>>> 5.7.11 (this is the first kernel I got after performing DNF upgrade) 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: >>>>> Yes, by letting Grub2 automatically select 5.6.6 (this equals with the live image version downloaded from getfedora.org. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: >>>>> I did not do that. 6. Are you running any modules that not shipped with directly Fedora's kernel?: >>>> NO. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. >>>> There's none. I have only kernel-5.6.6 in my logs. Details MacBookPro: Intel Core i7-4770HQ CPU @ 2.20Ghz x 8 Sold in 2015
Hello, I'm experiencing the same issue with my MacBook Pro 15" 2015 on Fedora 32 and 33. # dmidecode --type 1 Handle 0x0007, DMI type 1, 27 bytes System Information Manufacturer: Apple Inc. Product Name: MacBookPro11,4 Version: 1.0 Serial Number: [REDACTED] UUID: 530f1bd6-28b1-5641-9b52-fc06ee68a348 Wake-up Type: Power Switch SKU Number: Family: MacBook Pro If I boot any of the provided 5.8.x kernels, the boot fails just after the console initialization. The last lines displayed are: fuse: init (AP version 7.31) i915 0000:00:02.0: [drm] Found 128MB of eDRAM fb0: switching to inteldrmfb from EFI VGA The computer is then completely frozzen. If I press enter, nothing moves on screen. I have to long press the power button to shut it down. If I boot the 5.6.6 kernel provided with my initial install of Fedora 32, it boots flawlessly. Given the problem seems related to the console initialization, I tried to add "nomodeset=0" to my boot command. As a result both kernels (5.6.6 and 5.8.x) boot flawlessly. But there is a consequence: my second screen connected to HDMI is not working anymore and the display is sluggish. Installed kernels: # sha1sum /boot/vmlinuz-* b1f5688bebce0ee7814114affdc12012deeaf1a2 /boot/vmlinuz-0-rescue-c1ccf6ffe84f41748d9698803c5a2f16 b1f5688bebce0ee7814114affdc12012deeaf1a2 /boot/vmlinuz-5.6.6-300.fc32.x86_64 2d4c144ee8a2e333e87ff0aed750a355c416ed39 /boot/vmlinuz-5.8.17-200.fc32.x86_64 0357fa8ad93d572409f0c244d5d2ffa03d9a8ae1 /boot/vmlinuz-5.8.17-300.fc33.x86_64 Any idea what could be the issue ? Regards, Nicolas
After some research, this could be related to: - https://bugzilla.kernel.org/show_bug.cgi?id=208737 - https://gitlab.freedesktop.org/drm/intel/-/issues/2381
I finally found a workaround, as documented here[1]. Adding "intel_iommu=on" to my boot command make the 5.8.x kernel boot flawlessly with dual screen and good performances. 1. Edit /etc/default/grub and change the GRUB_CMDLINE_LINUX variable to add intel_iommu=on. GRUB_CMDLINE_LINUX="[...] intel_iommu=on" 2. Run grub2-mkconfig # grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg Generating grub configuration file ... Found Mac OS X on /dev/sda3 done I will revert this workaround as soon as the proper fix is included in the kernel. [1] https://bbs.archlinux.org/viewtopic.php?id=256520&p=3
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 EOL if it remains open with a Fedora 'version' of '32'. 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 32 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 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.