Bug 1829174 - MacBookPro13,3 Built-in display doesn't work for linux >= 5.6 kernels
Summary: MacBookPro13,3 Built-in display doesn't work for linux >= 5.6 kernels
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-04-29 06:07 UTC by Dick Marinus
Modified: 2020-08-14 18:49 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-08-14 18:49:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg.txt (116.17 KB, text/plain)
2020-04-29 06:07 UTC, Dick Marinus
no flags Details

Description Dick Marinus 2020-04-29 06:07:57 UTC
Created attachment 1682696 [details]
dmesg.txt

1. Please describe the problem:
On my MacBookPro13,3 the built-in display doesn't work anymore since I've updated the kernel to 5.6

2. What is the Version-Release number of the kernel:
5.6.6-200


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.6.6-200

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Boot the kernel, I'm using refind as bootloader.


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've tried 5.6.7-200.fc31 (updates-testing), same problem.


6. Are you running any modules that not shipped with directly Fedora's kernel?:

Yes, kmod-macbook12-spi-driver to use the built-in keyboard (sigh...)


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.

Done.


Note You need to log in before you can comment on or make changes to this bug.