From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 59431] [snb efi gmux] imac 12,1 blank screen upon booting
Date: Wed, 23 Jan 2013 22:01:35 +0000 [thread overview]
Message-ID: <bug-59431-502-EoMjKGK17c@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59431-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 908 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=59431
--- Comment #24 from Seth Forshee <seth.forshee@canonical.com> ---
Created attachment 73542
--> https://bugs.freedesktop.org/attachment.cgi?id=73542&action=edit
Add quirk to efifb for iMac 12,1
Here's a patch to try. But after some more poking around I'm wondering why this
is needed. The kernel seems to get the information about the GOP framebuffer
for most recent Macs without quirking, so it makes me wonder why it doesn't
work on this machine.
Just to check one obvious point, are you either running with the stock Ubuntu
kernels or else with CONFIG_FB_EFI=y? An easy way to verify this is to boot the
machine and run 'grep CONFIG_FB_EFI /boot/config-$(uname -r)'. This should
output 'CONFIG_FB_EFI=y' if your kernel is configured to include the EFI
framebuffer support.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1930 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-01-23 22:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-59431-502@http.bugs.freedesktop.org/>
2013-01-16 11:46 ` [Bug 59431] [snb efi gmux] imac 12,1 blank screen upon booting bugzilla-daemon
2013-01-23 15:52 ` bugzilla-daemon
2013-01-23 17:30 ` bugzilla-daemon
2013-01-23 18:22 ` bugzilla-daemon
2013-01-23 18:37 ` bugzilla-daemon
2013-01-23 19:39 ` bugzilla-daemon
2013-01-23 20:56 ` bugzilla-daemon
2013-01-23 22:01 ` bugzilla-daemon [this message]
2013-01-24 9:53 ` bugzilla-daemon
2013-01-24 12:07 ` bugzilla-daemon
2013-01-24 12:08 ` bugzilla-daemon
2013-01-24 12:13 ` bugzilla-daemon
2013-01-24 12:20 ` bugzilla-daemon
2013-01-24 13:37 ` bugzilla-daemon
2013-01-24 13:40 ` bugzilla-daemon
2013-01-24 14:30 ` bugzilla-daemon
2013-01-24 14:52 ` bugzilla-daemon
2013-01-24 14:57 ` bugzilla-daemon
2013-01-24 15:00 ` bugzilla-daemon
2013-01-24 15:12 ` bugzilla-daemon
2013-01-24 15:40 ` bugzilla-daemon
2013-01-24 16:47 ` bugzilla-daemon
2013-01-24 16:48 ` bugzilla-daemon
2013-01-24 17:11 ` bugzilla-daemon
2013-01-25 16:24 ` bugzilla-daemon
2013-01-25 19:46 ` bugzilla-daemon
2013-01-25 20:51 ` bugzilla-daemon
2013-01-25 23:56 ` bugzilla-daemon
2013-01-26 7:29 ` bugzilla-daemon
2013-01-28 9:06 ` bugzilla-daemon
2013-01-31 10:59 ` bugzilla-daemon
2019-11-19 8:32 ` bugzilla-daemon
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-59431-502-EoMjKGK17c@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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