There seems to be an issue on the 2015 model to:-
https://bugzilla.kernel.org/show_bug.cgi?id=108331 (Macbook 12inch 2015)
** Bug watch added: Linux Kernel Bug Tracker #108331
http://bugzilla.kernel.org/show_bug.cgi?id=108331
--
You received this bug notification because you are a member of
** Changed in: ubuntu-release-notes
Status: Incomplete = Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
unable to boot after install on 2013 macbook air
To manage
I have trusty on a 2013 MBA 13 and ran into this exact problem...
I can at least confirm that Seth's comment #17 above seems to have been
the solution... installing grub-efi seems to have fixed things.
What I find interesting is that it booted fine when I first installed
and then after letting
I bountied this and also found this page :
https://help.ubuntu.com/community/MacBookAir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
unable to boot after install on 2013 macbook air
Nope, processor.nocst=1 does not help. It still hangs reading the CPU
info and that's it. The only way to boot the mac-type images in such
state is using nr_cpus=1 in the boot options, which is pretty far from
optional... I honestly don't remember how that happened but a few weeks
ago I was stuck
Hello!
I'm quite unfamiliar with programming, but I'm a PhD student who wants
to install Ubuntu on his Macbook Air6,2. I drink a lot of coffee and am
more than willing to help, although I will need very explicit
instructions.
I am experiencing this issue, and I tried to go in and set nr_cpus=1
My problem of comment #27 was solved by picking a 14.10 daily-live amd64
image (without mac suffix - 14.10 beta-2 happened to only have images
with the mac suffix).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1284085
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Fri, Oct 17, 2014 at 08:33:42AM -, wvengen wrote:
My problem of comment #27 was solved by picking a 14.10 daily-live amd64
image (without mac suffix - 14.10 beta-2 happened to only have images
with the mac suffix).
The mac images really aren't needed except for quite old hardware.
On my MacBookPro11,1 I installed 14.10 beta-2 and have the same problem.
Booting from usb works, booting from harddisk not (after installation),
booting from harddisk while passing nr_cpus=1 on kernel cmdline works
(but only works with 1 core, obviously).
--
You received this bug notification
In my MacBookAir (6,2) I just installed the last daily build of 14.10
and had the same problem. I can boot from the live CD but after install,
it won't boot. I tried to re-run refind, but that doesn't fix it.
Passing nr_cpus=1 does the trick, though.
--
You received this bug notification
** Changed in: ubuntu-release-notes
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
unable to boot after install on 2013 macbook air
To manage
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
unable to boot after install on 2013 macbook air
To manage
I have a MacBookPro11,1 (specific configuration is 2.6 i5/8GB/256-Flash)
and using the standard (not mac) 14.04 ubuntu img results in the exact
same behavior as above. I.e. I can boot from usb successfully but when
booting the installed system the sequence stops immediately after the
point where
Thank you for taking the time to file a bug report on this issue.
However, given the number of bugs that the Kernel Team receives during
any development cycle it is impossible for us to review them all.
Therefore, we occasionally resort to using automated bots to request
further testing. This is
I have a 13 MBP 11,1, I was running Ubuntu 14.04 which was working
great for a period of time.After my battery died, it hangs with the
same booting SMP configuration node #0 CPUs #1 as described above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
unable to boot after install on 2013 macbook air
To manage notifications about
It sounds like we are getting into this situation because people are
using the +mac image when they do not need to. Some new text might be
needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Fri, Apr 04, 2014 at 01:28:23AM -, Richard Harding wrote:
I was using the OSX daily image from http://cdimage.ubuntu.com/daily-
live/current/ which did not present the options for efi or legacy.
The default 64-bit desktop image works fine on relatively recent Macs.
Maybe some of the
If anyone still has the legacy bios install, I'd be interested to know
if passing processor.nocst in the kernel boot options has any affect on
the problem. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
From a little searching I turned up:
https://bugzilla.kernel.org/show_bug.cgi?id=60635
which indicates that this is a problem related to Apple's bios-
compatible boot support, so one workaround is to do a native EFI install
(which I think is a better option most of the time). I'd suggest using a
Adding a Release Notes task as this is very confusing and needs manual
work arounds to get out of.
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: grub.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284085/+attachment/4063504/+files/grub.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
** Attachment added: acpi-tables.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284085/+attachment/4063502/+files/acpi-tables.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284085/+attachment/4063503/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
Using nr_cpus=1 allowed 13.10 3.11.0-12 to boot
I've added the outputs from:
acpidump
dpkg -l | grep grub
dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
unable to boot after
So that's definitely a legacy bios installation, which really isn't
recommended anymore for most systems because EFI boot usually works fine
and exposes more functionality.
I'd at least like to confirm that booting in native EFI works without
nr_cpus=1. You should be able to just run 'sudo
Thanks a lot! Installing via EFI worked like a charm, I was choosing the
legacy os option every time. I'll add the acpi output from this install
as well as you requested.
Thanks again,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: acpi-tables.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284085/+attachment/4064295/+files/acpi-tables.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
I was using the OSX daily image from http://cdimage.ubuntu.com/daily-
live/current/ which did not present the options for efi or legacy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
Are you able to boot without the nr_cpus parameter with older kernels?
Was this not happening with prior Ubuntu releases? If you don't know,
can you test a prior kernel, maybe the 3.11[0] or 3.2[1] upstream
kernel:
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/
[1]
You could also create a live CD with one of the earlier Ubuntu releases.
LiveCD info:
https://help.ubuntu.com/community/LiveCD
Earlier Ubuntu releases:
http://releases.ubuntu.com/
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a
Thanks for the information!
On my late 2013 15 MBP I tried with the following versions:
14.04 3.13.0-17
14.04 3.13.0-20
3.10 3.11.0-12
None of which were able to boot past the stage in the image posted by the
original reporter after installing.
But all were able to be run via usb livecd.
I
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on
I'd like to add that this bug does not only effect Air's, I have the
identical issue on a late 2013 Pro 15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284085
Title:
unable to boot after install
Sorry for the delay. I had to wait to get an ethernet adapter so I could
get network connectivity as wifi doesn't work on it currently after you
leave the usb boot thumbdrive.
I've gotten network and verified that the latest kernel available in
trusty, 3.13.0-16, does not work and has the same
I tested out linux-
image-3.14.0-031400rc5-generic_3.14.0-031400rc5.201403022235_amd64.deb
I had the same boot issue. It would not boot, but if I set nr_cpus=1 it
would boot up fine. It hands at the same Booting SMP configuration
point as the older kernels.
** Tags added:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.13 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
38 matches
Mail list logo
