dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 24 Jan 2013 17:11:13 +0000	[thread overview]
Message-ID: <bug-59431-502-aQ3MzX1vMe@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-59431-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1873 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=59431

--- Comment #39 from Seth Forshee <seth.forshee@canonical.com> ---
(In reply to comment #37)
> I have no graphics setup or at least not that i am aware off.
> I get a ncurses based menu where i can choose the different kernels i have
> installed.

By "graphics" I just mean that grub can display something on the screen, which
seems to be the case. Typically on a Mac grub will use GOP for this, which is
the interface supported by efifb.

> Right now i cannot seem to get a console even with or without the
> gfxpayload=keep option on the 32bit kernel. When starting the same usb stick
> on a macbook air it works with both the 32bit kernel and the 64bit kernel.

There's only one graphics card in the airs. Part of your current problems seems
to be confusion over which card should be used.

> We don't use the default ubuntu grub install because we setup a small
> efiboot environment  using grub-mkimage.
> grub-mkimage -O x86_64-efi -o bootx64.efi  search_fs_uuid fat ext2 normal
> boot configfile linux

What I'm trying to figure out here is whether or not the patch I wrote is
actually needed. If it's a problem with how the kernel is being booted then
patching efifb probably isn't appropriate.

Please try booting a standard 64-bit Ubuntu image (either 12.10 or the 13.04
daily builds) and see if you experience any of the same problems. If not then
you've got a problem with your boot environment. I'm no grub expert, but your
list of modules is rather small. In particular I notice that there's a efi_gop
module that isn't included.

There's still obviously a problem with the graphics when you boot a 32-bit
kernel, but getting the kernel to identify the correct graphics device to use
is a prerequisite to fixing the other problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2820 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

  parent reply	other threads:[~2013-01-24 17:11 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
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 [this message]
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-aQ3MzX1vMe@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