From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 13170] Macbook 5,2 only boots with acpi=off, or nosmp, or maxcpus=1
Date: Wed, 29 Jun 2016 14:55:33 +0000 [thread overview]
Message-ID: <bug-13170-2300-Y0vrwRLGBl@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-13170-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=13170
--- Comment #72 from morten vermund <mortenvermund@gmail.com> ---
(In reply to Francisco from comment #63)
> Hi, I've been following this bug for a while since I've a macbook 5,2. I've
> been able to use linux (ubuntu) with refit+grub-efi+nvidia driver for a
> while. Last week I reinstalled everything, Snow Leopard, Win7 and Ubuntu
> natty, everything works PERFECT using the same approach.
>
> Today, I've upgraded the RAM, from 2 to 4 Gigs (removed 2x1Gb and put
> 2x2Gb). Linux doesn't boot anymore with refit+grub-efi, only using maxcpus=1
> or acpi=off (still with Nvidia). The ram is OK, passes memtest86+, and win
> and snow leopard work without any problem. If I remove ANY one of the memory
> chips (1x2Gb 800Mhz) linux can boot again with grub-efi.
>
> I guess this is probably a problem of grub-efi, but as it is related I
> wanted to post it here, sorry if it's the wrong place.
>
> Here you can see the boot error from grub-efi when booting with 4Gb.
> http://www.billigalaan.se
>
> Please let me know if you want me to test anything in particular.
> I have Natty with Nvidia 270.41.06, with uname -r: 2.6.38-10-generic
>
> Sadly now I have to give up one CORE for 2gb of extra RAM :(
>
> Thanks!
> Francisco
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-06-29 14:55 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
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 [this message]
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=bug-13170-2300-Y0vrwRLGBl@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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