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: Fri, 17 Dec 2010 18:03:47 GMT [thread overview]
Message-ID: <201012171803.oBHI3lwv006152@demeter2.kernel.org> (raw)
In-Reply-To: <bug-13170-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=13170
--- Comment #58 from David <dstansby@gmail.com> 2010-12-17 18:03:45 ---
New comment downstream saying:
"I've got Ubuntu 10.10 (2.6.35-23-generic #41-Ubuntu SMP) booting using
my old grub 1.97 (that was booting Ubuntu 9.04) compiled as so:
./configure --with-platform=efi --target=x86_64
make
./grub-mkimage -d . -o grub.efi acpi boot chain configfile ext2 fat hfsplus
normal part_gpt sh
Then my grub.cfg has
menuentry "linux latest" {
root=(hd0,3)
fakebios
linux /vmlinuz root=/dev/sda3 video=efifb agp=off acpi=force
initrd /initrd.img
}
I've got 2 CPUs, ACPI (sleep, reboot, poweroff, battery/power) - my next
step will be to try a newer version of grub2."
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-12-17 18:03 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 [this message]
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
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=201012171803.oBHI3lwv006152@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