dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 13170] Macbook 5,2 only boots with acpi=off, or nosmp, or maxcpus=1
Date: Sat, 19 Feb 2011 15:58:44 GMT	[thread overview]
Message-ID: <201102191558.p1JFwiPl013980@demeter2.kernel.org> (raw)
In-Reply-To: <bug-13170-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=13170


Gregory Bellier <dest@gatekeeper.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dest@gatekeeper.fr




--- Comment #60 from Gregory Bellier <dest@gatekeeper.fr>  2011-02-19 15:58:42 ---
I also have a MacBook 5,2 (early 2009) and I experience the same errors than
you do. This has been tested on Ubuntu 10.10

I managed to build a grub2 1.99rc1 x86_64-efi.
I had to do some tweaks to make some progress. I'm hacking directly in grub.cfg
but from now, I don't care, I just want to test. So here is my entry :
menuentry 'Ubuntu, with Linux 2.6.35-25-generic' --class ubuntu --class
gnu-linux --class gnu --class os {
        insmod part_gpt
        insmod ext2
        set debug=video
        insmod efi_gop
        set root='(hd0,gpt3)'
        search --no-floppy --fs-uuid --set=root
d5175c18-7da2-49a9-a3af-844bad27c91d
        linux   /boot/vmlinuz-2.6.35-25-generic
root=UUID=d5175c18-7da2-49a9-a3af-844bad27c91d ro
        initrd  /boot/initrd.img-2.6.35-25-generic
}

The options are pretty much the same than the ones from my working grub (with
maxcpus=1).

At my first boot, I got "error: no argument specified". From what I've seen on
the internet, it's because the syntax is different between Grub 1.98 and
1.99rc1. In 1.98 it's --set d5175c18... while --set=root is needed for 1.99rc1.
However, this error wasn't a real problem because we're asked to press a key
and then the boot continues.

It continues until the second error: "error: no suitable mode found". I've
resolved this error by putting "set debug=video" and  "insmod efi_gop" in my
grub entry.

>From this point, I can see that the kernel starts booting until the error I now
have which I haven't solved yet : "fb: conflicting fb hw usage nouveaufb vs EFI
VGA - removing generic driver".

I hope this post will help some of you to make some progress until the point
I've reached.

I also tried what comment #58 detailed but I have the very same error :
conflicting fb...

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
--

  parent reply	other threads:[~2011-02-19 15:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-13170-2300@https.bugzilla.kernel.org/>
2010-04-26 15:25 ` [Bug 13170] Macbook 5,2 only boots with acpi=off, or nosmp, or maxcpus=1 bugzilla-daemon
2010-05-10 22:06 ` bugzilla-daemon
2010-05-10 22:16 ` bugzilla-daemon
2010-05-11 16:44 ` bugzilla-daemon
2010-05-17 15:19 ` bugzilla-daemon
2010-07-22 15:43 ` bugzilla-daemon
2010-10-02 20:28 ` bugzilla-daemon
2010-10-28 14:29 ` bugzilla-daemon
2010-12-17 18:03 ` bugzilla-daemon
2011-01-16 22:35 ` bugzilla-daemon
2011-02-19 15:58 ` bugzilla-daemon [this message]
2011-03-09 17:08 ` bugzilla-daemon
2011-04-06 12:55 ` bugzilla-daemon
2011-08-17  0:52 ` bugzilla-daemon
2011-08-19 11:08 ` bugzilla-daemon
2011-08-19 22:16 ` bugzilla-daemon
2011-08-20 12:30 ` bugzilla-daemon
2012-03-04  6:37 ` bugzilla-daemon
2012-03-05  6:07 ` bugzilla-daemon
2012-03-24 14:46 ` bugzilla-daemon
2012-05-30 16:27 ` bugzilla-daemon
2012-05-30 16:27 ` bugzilla-daemon
2013-04-09  6:24 ` bugzilla-daemon
2016-06-28 10:17 ` bugzilla-daemon
2016-06-28 10:24 ` bugzilla-daemon
2016-06-29 14:55 ` bugzilla-daemon
2021-04-16 16:48 ` bugzilla-daemon
2021-04-16 16:50 ` bugzilla-daemon
2021-04-16 16:52 ` bugzilla-daemon
2021-04-16 16:54 ` bugzilla-daemon
     [not found] <bug-13170-2300@http.bugzilla.kernel.org/>
2010-02-23  7:34 ` bugzilla-daemon
2010-02-23  9:17 ` bugzilla-daemon
2010-02-23 11:18 ` bugzilla-daemon
2010-02-24  2:39 ` bugzilla-daemon
2010-02-24  8:01 ` 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=201102191558.p1JFwiPl013980@demeter2.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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