10de:0647 [MacBookPro5,2] Fails to boot into 12.04 desktop

Movie with nomodeset + console output http://hanfi.net/ubuntu/mbp.mov

Exact same issue with same MacBookPro Type. Haveing a 500GB SATA HD + 8GB RAM using Lucid Beta 1 64Bit. Another Linux e.g http://www.sysresccd.org/ CD boots just fine on this macine. OSX works fine, just as Windows 7 64 Bit. Using rEFIt 0.14 (http://refit.sourceforge.net/) but even the LiveCD option does not boot.

Disabled videodrive nomodeset, hangs at Wireless driver PHY.

Will investigate other options, boot parameters or what else I think might lead to success in the meantime...

Note that I've installed Linux, OSX , Windows, FreeBSD etc on MANY systems, so the issue is likely not my fault.

In Ubuntu 9.10 the "ERROR: FOUND UNSUPPORTED PHY" was the same message but it managed to boot the Live CD which is not the case in 10.04.
It seems also to have some problems with a "usb device on port 2" of course I had NO usb devices plugged in at this time.

The only way to get Lucid working at the moment is to install karmic koala(9.10) and then do the "update-manager -d" command. This will update the system to Lucid but sound will not work because it didn't work in Karmic either.
( https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/462098 )
Also if you try to install the proprietary Nvidia driver with the "Hardware Driver" section in the menu of Ubuntu, it will fail to install. So if you upgrade from Karmic to Lucid you have a) No sound and b) no 3D proprietary Nvidia driver.

I really hope this problem gets fixed, so that the MacBook Pro will be able to boot into the Lucid desktop.

If you upgrade from Karmic to Lucid you need to use the Super Grub Disc to boot into Lucid by the way.
rEFIt will not work.

Thanks will remember when needed, BTW this bug is not about not an upgrade, no feedback since there is no 10.04 release as of this moment, but about a fresh install Beta1, yup a real BETA with severe bugs ;). FYI just tried a fresh install of Ubuntu 9.10 64Bit Karmic Koala, could start the installation in graphical mode without problems, it just worked.

Thanks for you time CV. You wrote in post #5

> Lucid but sound will not work because it didn't work in Karmic either.
That is not the case see the thread you mentioned yourselves ;)
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/462098

Get sound working by installing the newest (not yet in the repos) linux kernel 2.6.32 following these instructions:
http://www.ramoonus.nl/2009/12/03/linux-kernel-2-6-32-installation-guide-for-ubuntu-linux/

Hpe it helps you.

Also, no doubt NVidea will work sooon, will try later today, but first the Karmic Koala + Upgrade and see where we can go from there...

CV wrote in # "rEFIt will not work." has to be seen in the contects of his post, to get GRUB-EFI to work in 64Bit take bootx64.efi and some tweaking I bet. "Beta " the best time of your life >:-). Any sensible helpfull results will be posted here, however the original issue remains, at least till beta 2.

BTW a lot about EFI n GRUB here
http://ubuntuforums.org/showthread.php?t=995704

Thanks,
maybe someone could change the status to "confirmed" and the importance to "high" if not even "critical" ?

I have the same issue as well (macbook pro 5,2, 17")

I think that the 2nd issue (after disabling nouveau and continue to boot) might be a FOSS wireless driver for the mac's broadcom NIC, which fails to load. These issues are similar for both i386 and amd64 variants.

My workaround was, as already described, to install Karmic and upgrade from there, installing the restricted drivers for the nvidia and broadcom cards; to make it boot I had to install grub2 into the partition my Lucid was on, in my case /dev/sda4.

And I agree with "cv" - this issue should be raised to 'high' or 'critical' as this is a complete show-stopper for those macbook users curious to try Lucid. And, considering how *nice* Lucid really is, that would be a real shame. :)

Here is the same video as in my post #3 in ogg/.ogv format: http://hanfi.net/ubuntu/mbp.ogv (this video can be played on Ubuntu without any additional codecs)

I have great news regarding the "no sound issue".

This is how it currently works:

1. Installing Ubuntu 9.10
2. "update-manager -d" in console
3. Updating the fresh Lucid beta with all the new updates
4. Having 2.6.32.17 kernel installed automatically through the updates
5. Booting up the latest "Super Grub Disc" version 1.30(latest version) and choosing "Load grub.cfg even if mbr is broken" from the menu
6. Done! Sound works for the first time and everything else seems ok!

(this bug is about the Live-CD wish still fails) ;-)

I'm happy to add that the proprietary Nvidia driver (current, from the Hardware Driver menu) installed with no problems and now Nvidia driver AND sound both work. Amazing.

Let's hope Live CD gets fixed too.

I know the below writen information is not 100% related to the orignal bug but still very relevant

..to give people hope on enjoying Ubuntu 10.04 on their MacBookPro (5,2)

I write this in the case the final 10.04 release CD would still not work.
Then there still would be a path to 10.04 via upgrading a fully working 9.10

On Karmic 9.10, I'm a happy camper now since,

* Wifi via restricted STA drivers works well
* Videocard Nvidia Driver 185.x works well, albeit restricted *<:o)
* Magic Mouse Basic works, needs tweaking, had no time yet. See
http://github.com/entrope/linux-magicmouse
* Bluetooth thus also works... ;)
* Sound works well, I've adjusted the Ubuntu wiki instructions
* iSight camera, a quick test showed picture, for testing I instaled
  cheese (sudo apt-get install cheese)

The related page for all of this Karmic goodness is
https://help.ubuntu.com/community/MacBookPro5-1_5-2/Karmic

BTW this helpful guy with great SEO links for EFI boot issues
http://www.rickycampbell.com/booting-windows-linux-and-osx-on-your-mac-without-using-grublilo-to-boot-windows/

Now I will see if we can upgrade to Lucid Lynx 10.04 Beta 1, a bold move...

So far, the original bug remains...well... bugging us. Cannot install Ubuntu Lucid Lynx 10.04 Beta 1 direct booted from CD on latest Modern MAC Powerbook Pro 5,2 :-( IMHO indeed critical.

As of Saturday night 11pm "update-manager -d" in a fresh Karmic Koala install (9.10) will NO LONGER result into a working 10.04 system. The 10.04 system will not boot anymore, not even with the super grub disc.

Also I tried the "Daily-Live" CD on Saturday afternoon which still fails to boot into the 10.04 Desktop.

If you have a working 10.04 Install right now then don't update or your system will not boot anymore since there is a serious bug right now which turns the system unbootable.

I got a MacBookPro5,5
Boot ROM Version: MBP55.00AC.B03

And the same problem seems to be here.. I can't boot from a usb disk, or cdrom..

Ohh same problem on 5,5? This is getting worse.

Hi, I have a macbook Pro 5,1 and I also have the same problem, which is strange since I was able to boot the Live CD in karmic.
I've tried the LiveCD and also a live USB in conjunction with rEFIt....but no luck

Hi, I have the same problem on a macbook pro 5,3 :-(

Anyone of the true heroes should finally
just raise the importance to critical since all 5,x MacBook Pro's seem to have this problem. Ubuntu will loose 1000's of users if this is bit fixed in beta 2.

bit=not (I'm typing on a iPhone) ;-)

has anyone tried using the alternate-install cd?? does it work or does it hang like the live cd?

I tried it, it doesn't wotrk. Nothing does work at the moment, NOTHING...

The installation using the alternative CD works but it hangs on the boot. I also tried the current live CD daily and daily-live. Both bot working. I also tried the DVD, not working too.
"update-manager -d" in Karmic not working too but I will try this tonight again...

so how do we get someone to pay attention to this bug? it's affecting all recent macbook pro users, and because of the similarities with the macbook I bet it is affecting that too, so I think there's a lot of people affected with this bug so we should try to get it noticed

Spam the mailing lists is my first idea what comes to mind. But I`m not going to do that, somebody else has to ruin his name ,-)

Trying to stop the driver from loading would be a first step to unravel the mistery, however adding the following bootline (F6)

noload=b43,b43-pci-bridge,ssb,b43legacy,b44 debug

Did not help :(. It could be that I'm using the wrong module name (b43 etc.) but since we cannot boot we must find the modulename via goin through kernal source ... sigh

NOTE the original bug still should be solved ofcourse. This info is soly ment to help solving the bug in the first place.

I can happily add that updating a fresh Karmic Koala install using the "update-manager -d" command results in a working Lucid Lynx again. (describted in post #13), so this is the only way to get a Lucid Lynx working at the moment.

Hi I have just found this thread that might give us a workaround to install Lucid using the LiveCD http://ubuntuforums.org/showthread.php?t=1442133&highlight=install+lucid+lynx+on+macbook+pro

Thanks, I'll try that.

Thanks Cor Driehuis for updating the description, I didn't know everybody can do that ;-)

Following the forum in post #30 it seems that nouveau is the actual problem which would make sence since nouveau was NOT included in Karmic Koala 9.10

I can confirm that adding "nouveau.noaccel=1 blacklist=vga16fb" (without the ") after the quite splash in the Live CD works.
It will boot and installation works.
After that you have to install the nvidia driver and then you have to reboot.
 NOTE, IMPORTANT: the second time you report after you installed the nvidia driver, the boot will fail, you need to add this time "nouveau.noaccel=0" (NOT 1) and after that you dont have to add anything else and it will always work.
If you have any questions about this or if you would like to have this in a movie, feel free to ask me.

BIG thanks for Christopher V. for the tips that at least made progress possible and for Chris Halse Rogers for the Undecided → High change. Now lets find some other Beta bug and report as best as we can!

It looks like there might be a couple of problems here - one vga16fb related, which *might* be fixed by a change we've made in a more recent daily LiveCD, one related to nouveau's acceleration.

It would be helpful if someone could describe the behaviour of a recent livecd with “blacklist=vga16fb” and *without* “quiet splash”. Does the livecd boot? If it doesn't, how far does it get? Do you get graphical corruption?

If it boots all the way with corruption, or you can get to a VT (with blacklist=vga16fb), could *one* person please run “apport-collect 546393”

Post #36 the: "recent livecd" meaning a daily build CD of after 20100402 ?

I will try the daily-live CD tomorrow and tell you if it works without "quite splash" and with "blacklist=vga16fb", I will also post a movie online to show the bug in a better way if it boots at all.
I don't understand how this "apport-collect 546393" thing works or where to type this so this could maybe someone else please do.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Ok apport-collect command done (as seen above). I'll try current the Daily-Live CD now (3rd of april, night)

I like to add that the above apport-collect was done on a successful boot with 3D Nvidia graphics working afterwards. (sometimes the Nvidia driver can't load and I need to select "Run Ubuntu in low-graphics mode", this happends around 30% of all boots)

I also tried the Daily Live CD from 3rd of April 2010 and adding "blacklist=vga16fb" and nothing else results into a nouveau pramin flush and the boot is NOT successful.

Here is the video from a few minutes ago:

http://hanfi.net/ubuntu/daily-live-3rd-april.ogv

I just booted latest kubuntu daily lucid_desktop_amd64.iso from the hard disk (using a custom entry for grub2) with the extra option "blacklist=vga16fb" and... heck, it boot so fast(er) :-) And the .iso is so much faster than my kubuntu 9.10 box.

* Sound works, volume up/down and display brightness up/down function keys as well.
* Ethernet (I am writing from within kubuntu lucid right now). I guess installing mactel-support will roll the rest.
* Bluetooth detects devices, pairing works -and it works FAST, the way it should (did not test further than this) :D

I don't more time to spend on this. But I though I'll let you know...

Regards

( Sorry for the typos above... )

off-topic: is there a way, in case everything (or most things) work(s) well, to just adopt the .iso with any configurations made on it, and install/use it (something like a dist-upgrade from karmic)?

It c/w-ould be then a "recommended" way for macbook(pro) owners before upgrading to lucid.

+ installed pommed and the keyboard backlight works (and it works so fast... the same for display brightness/ volume --- I can't believe it).

OK, I know that I probably do not add new informatio to developers but I can't hide my enthousiasm. This is the BEST experience using (k)ubuntu on the MBP (5,1).

I attached the external display and was (mentally) prepaired to fight a bit to get it working without restarting X. And what happens? A dialog popped-up and informed me about... a new connection or display (or whatever, doesn't matter). External display hotplugging works!

Excellent! Congratulations and Thank you for your efforts.

1. Nobody is using kubuntu
2. None of this is about the bug

Mea Culpa - Sorry Christopher. I thought it's the same thing when talking about "booting" at least.

I don't mind, let's talk about ice cream ;-)

( I admit that I have found the wrong place to post this stuff. But I would like to add that "1. Nobody is using kubuntu" is just not true. )

My (mis-)understanding was that 10.04 fails to boot MBP5,1 = fails to boot the kernel. I used the option "nouveau.noaccel=1 blacklist=vga16fb" to boot latest Kubuntu and it worked. I thought it would be useful to let others know so I added this here (+ a lot more due to my excitement about the upcoming release).

Anyway, IIUC, the bottom line is (besides the "blacklist=vga16fb" issue):
"nouveau" provides no _stable_ 3D acceleration in its current state [*] and it wont be ready when Lucid comes out". The solution would be to load "nouveau" with the option "nouveau.noaccel=1" for the machines that wear the respective graphic card(s).

Right?

---
[*] "Any 3-D functionality that might exist is still unsupported. Do not ask for instructions to try it." from <http://nouveau.freedesktop.org/wiki/>

yes I wrote that in post #34. nouveau is the problem

See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/553471
Easter monday, so a little spare time left to spend on investigation the defect, sigh...

Did not see any codechange yet in e.g.
http://tomoyo.sourceforge.jp/cgi-bin/lxr/source/drivers/gpu/drm/nouveau/nv50_instmem.c

Hi, I reported bug 553471 that Cor linked above.

By specifying "nomodeset xforcevesa" on the kernel command line I am able to get to a basic, non-accelerated desktop. I've been doing this with the AMD64 daily livecd.

Ok so "nouveau.noaccel=1 blacklist=vga16fb" and "nomodeset xforcevesa" both works...

...I wonder if they both give the same result...

They don't give the same result. One will be using the nouveau drivers, just without acceleration, the other will be using VESA.

@Νίκος Αλεξανδρής: Can you boot with *only* “blacklist=vga16fb”, or do you also need to add “nouveau.noaccel=1” before it works correctly?

From discussion in #nouveau it seems we may need to get efifb to properly initialise the cards before nouveau loads:

10:38 <marcheu> yeah try the efifb + handoff
10:39 <marcheu> there are EFI issues
10:39 <marcheu> right now you probably want to make apple use efifb
10:40 <RAOF> Instead of nouveau?
10:40 <marcheu> use efifb+ handoff
10:40 <marcheu> to nouveau

@Chris HR:

Please accept my apologies for _not_ being accurate in post #58. Of course I have to use the "nouveau.noaccel=1" as well. I thought that I (sort of) corrected this in post #65 where I mention that I use "nouveau.noaccel=1 blacklist=vga16fb".

Kindest regards, Nikos

---
PS Thank you for all of your efforts Chris

@Chris Halse Rogers: For "blacklist=vga16fb" *only* check post #57

Finally installed Lucid Lynx Beta 1 on MacBookPro. More details in the post on the forum most relevant thread
http://ubuntuforums.org/showthread.php?p=9083630

...after all this is a bugtracker, not a forum ;)

I'm a little bit confused. Didn't I mention in post #34 already that the installation works if these 2 options are added? ;-)

The original bug still exists kind of since the boot CD still isnt loading without this knownledge

What I don't understand, if I understand correctly what I read in nouveau's wiki [*], is why are we trying to look for something that does not exist yet. There is no support for 3D yet.

Hence, this is not a bug. We have to: (a) wait till some dev writes the code or (b) code it ourselfes.

Since I am no real programmer and can be of little help in coding this, I just can test whenever a 3D-code will be available. Correct me if I am wrong.

---
[*] from <http://nouveau.freedesktop.org/wiki/>:
"Any 3-D functionality that might exist is still unsupported. Do not ask for instructions to try it. But you can read GalliumHowto in case you are brave enough."

WE DON'T LOOK FOR 3D SUPPORT.

This bug is about the Lucid Beta1 not booting.

Just read the description, this bug was filled because all 5.x MacBook Pro Models are unable to boot into the desktop.

Now we know how it works using "nouveau.noaccel=1 blacklist=vga16fb" but we didn't know this before.

You write that you (plural) don't look for 3D support while this is the *real* problem (and you test various things to see if you can get accelerated graphics [posts # .. .. .. ] ) since the nouveau driver is just not ready yet. If "we" just want to "boot" then switch back to the old way (like in Karmic) where driver X ( I don't know which exactly) is used. It seems simple enough till the nouveau driver works fine.

Are there other reasons to stick with the nouveau driver?

---
( You can avoid CAPITAL LETTERS Christopher. They appear offensive... but if they make you feel GREAT ans SMART then go ahead. )

Νίκος Αλεξανδρής, the nouveau driver works fine on most nvidia hardware I have thrown at it, just not the mbp5,x series. I consider it ready for use (at the very least, ready to replace "nv"). This is a bug with that driver with this particular adapter. Furthermore, nvidia has officially discontinued the old "nv" driver. New nvidia cards will *not* be supported by it, and it is effectively dead as nobody outside nvidia supports it as far as anybody i've spoken to can tell. Shipping with nv on a LTS is somewhat short problematic, I assume.

Also, while we are talking about accelerated graphics, we are not talking about 3D graphics. The graphics driver can accelerate lots of non-3D drawing functions all without needing OpenGL/mesa/gallium. The nouveau driver as shipped with Lucid does not have any 3D capability, but does support other handy acceleration methods (eg. xrender)

The problem in this bug is the Lucid hangs during boot with a particular piece of hardware (said graphics adapters in macbookpro5,X units). Ideally the nouveau could be patched to work with it. Failing that, blacklisting these cards so they can fall back to either nv (or vesa, depending on support) would suffice. The Hanging during boot makes a very non-optimal out-of-the-box experience.

"The Hanging during boot makes a very non-optimal out-of-the-box experience" <- that's the bug.

I don't mind if I use nouveau or not.

Thank you for your time and the detailed explanations Chris Ir.

Nikos

The bug "unable to boot into the Ubuntu 10.04 beta1 Live-CD". Therefore also unable to install the OS is ofcourse still existing regardless everyones tips to get someting of the boot to work. At least could now send various other defects of Luxid Beta1 running on the acbook Pro

Thanks to everyone confirming the bug on various MacBook's.

I could not agree more with what others already mentioned: The Hanging during boot makes a very non-optimal out-of-the-box experience.

Any developer with possibility to fix this, I beg you to do so before the Final release of Lucid Lynx 10.04

If I could fix it alone I would, but even then I cannot release a fixed "official" CD of Lucid Lynx therefore I only can add help on the forum.

http://ubuntuforums.org/showthread.php?p=9083630

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

Upstream thinks that this should be fixable by loading efifb first, to set things up for nouveau.

Could you please try booting *without* “nouveau.noaccel=1” or “quiet splash” and *with* “video=efifb”? So, replacing “quiet splash” with “video=efifb”? This should cause efifb to be loaded, which might initialise things enough that nouveau will work.

You shouldn't need to add “blacklist=vga16fb”, but if it doesn't work the first time please try adding the blacklist.

If this doesn't work, we'll resolve it by disabling acceleration in nouveau for your systems.

Chris. I tried booting the current daily livecd. "video=efifb" does not work with or without "blacklist=vga16fb". Note that, at least in my case, I am not booting from EFI mode. I am using grub-pc via the bios compat mode.

"video=efifb" does not work for me either.

(note: I too use grub-pc and not efi mode)

Hm. Is anyone who is experiencing this bug running in EFI mode? There are some reports of recent macbook pros running nouveau successfully; maybe EFI mode works.

Chris Halse Rogers: That may be, but the Live CD does not support EFI, nor does a default install. Post-install, one would have to manually install grub-efi-${efi-arch}. I have briefly attempted this, but only have only managed to create an unbootable system.

Starting with Option key pressed, so one can boot from CD with replacing “quiet splash” with “video=efifb”
halted the install with the same "[drm] nouveau 0000:02:00.0 PRAMIN flush timeout" message.

Note that above I can see nouveau_channel_alloc: initialized FIFO 1. My impression is that Nouveau is well on it's way being finished and the develi is in the details.

Anyhow I love to give more sensible info since I did manage via a looooong road to get Lucid on my system, I thefore can make all kinds of dumps, for hardware info and what not. Chris Halse Rogers of post #89, what commands 'n scripts would you like me to run that would be helpful for the team to fix the bug?

Can get into EFI shell and do e.g. a devtree, dmpstore or drvdiag of anyhelp?

Just to chime in: I tried to boot from the daily live built 20100406 and it still is a complete show stopper for me on MBP 5,2. "nomodset" and "vga=efifb" don't really help here either, as the whole boot process eventually hangs solid.

I use beta 2 right now (installed it a few minutes ago).

1. video=efifb does notresult into a working desktop (pramin flush) <- this has been said before.

2. blacklist=vga16fb does not need to be added

3. adding nouveau.noaccel=1 is enough and will result into a working system

4. installing the nvidia driver with the "hardware driver" program will result into an "error" but actually it installed the driver successfully and the "error" doesn't exist.

5. nvidia driver will boot successful next boot and the nouveau.noaccel=1 option does NOT need to be added.

6. everything else works. ;-)

There's a test-kernel building in the nouveau ppa ( https://edge.launchpad.net/~xorg-edgers/+archive/nouveau/ ) which should quirk off acceleration for affected MacBook Pros. Once it has built could you please test that this kernel successfully boots *without* the nouveau.noaccel=1 kernel option?

I installed beta 2, on a MBP 5,3. I was able to start the LiveCD with "nouveau.noaccel=1 blacklist=vga16fb".
But after the installation I always get the PRAMIN flush timeout error, even if i add "nouveau.noaccel=1".

I'm also unable to boot my system anymore with or without noveau.noaccel=1 thanks to the new xorg updates which I installed earlier. Therefor I'm not able to test the new kernel. I simply can't boot the system at all.

I installed a fresh beta2 just a few minutes ago and I'm totally unable to boot it. No idea why it worked yesterday...(where I also installed a fresh beta2)

That means that I install beta 1 now again.

I'm also unable to boot form beta 1, no idea, my MacBook Pro seems to be broken for ever...

Please somebody else try the kernel from post #95 and tell Chris Halse Rogers if this works without the nouveau.noaccel=1 option or not.

I got lucid lynx beta using "nosplash nouveau.noaccel=1 vga=711" (...using Kubuntu though :-). I've installed but have some issues:

  - X wont autostart (need to "startx")
  - automount does not work (might be an KDE bug !?)
  - random crashes of various apps

(More in the Kubuntu-forum: <http://kubuntuforums.net/forums/index.php?topic=3110960.msg224899#msg224899>)

@Chris Halse R (+ note to self): not sure if I have the time to spend to try-out the "nouveau" stuff. Well, maybe yes... tomorrow!?

ohh... those typos: I ve installed Beta2 and _not_ Beta1.

Cheers!

"nosplash nouveau.noaccel=1 vga=711" did not do the trick on my Ubuntu beta 2.

@Seeed:

I am sorry to read that. I really did not have to do anything else than that. What do you see? Text flowing upwads I guess for some seconds... or not? Does the boot process just hang?

(...did you verify the integrity of your Live 10.04 CD Beta2?)

@Seeed: there is also the parameter "quiet". Could you retry booting using all of the above parameters I've described _and_ removing "quiet" and see at which point it hangs?

@Νίκος Αλεξανδρής:
What I see is the same error I get, with all the other parameters I tried:

"b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 8, Type 4, Revision4)"
"[drm] nouveau 0000:02:00.0 PRAMIN flush timeout"

I also removed the "quiet" parameter and everything seems to be working normal until I get the error above.
Checked the integrity of my disk and it seems to be fine.

@Seeed: can't help you out - sorry.

Lucid has still blocker bugs. I can't mount devices for example. Anyhow, I'll try out the latest nouveau stuff given above and then I'll get back to Karmic since I lost lot of time. Need to continue my work.

@ seeed good band
@seed 2nd time: you need to add the nouveau.noaccel=1 in the same line where quite splash is written.
Sounds unbelievable that you got a pramin flush timeout with nouveau.noaccel=1 because then this option fails for you which is even worse than the bug discussed here

@Chris Halse Rogers: After using the alternative i386 beta2 CD I was able to get a working system again.

Your special nouveau kernel Chris Halse Rogers, was not working for me and failed to boot with no options. I also tried nouveau.noaccel=1 which failed too(second screenshot).

@Chris HR: It didn't work for me also. I am now back in Karmic since I have no more free time currently.

@Seeed: Did you check the options for "safe graphics" or similar in the Live CD (pre-)Boot dialog? There must be an entry about this "vga=...".

Hmmm... now that I see I used "vga=771" and not "vga=711". But this might be of minor importance.

@Christopher "cv": You were right. When i put the parameter in the same line with quite splash i can boot and login in text mode. "startx" gets me to the desktop, but many apps crash and networkmanager does not seem to work either.

I can't help with testing the kernel, but I had the problem in this bug report when I upgraded from a daily alternate image a few days after Beta 1.

I fixed my system by booting the recovery mode with "nomodeset" appended to the grub boot command, and then ran the manual nvidia install shown in the known issues for http://www.ubuntu.com/testing/lucid/alpha2 - the bit about Jockey not supporting the Nvidia alternates system. I then rebooted and the nvidia kernel module failed to load, but the vesa fallback worked. I then reinstalled nvidia-common and it worked, fixing the nvidia driver.

Hope that helps as a workaround, I don't know if it will still work at this point.

Thanks, I got a working 2.6.32.19 kernel atm but this seems to be a nice trick if it really works.

Chris Halse Rogers in post #95 I'm willing to get masochistic and test the kernel 2.6.32-20.29~nouveauquirk. As I understand there is already n newer kernel https://edge.launchpad.net/ubuntu/lucid/+source/linux/2.6.32-20.30

1) Does this mean this also has this fix? and no need to thest the above OR
2) For short, if I understand correctly, I need to:
    - Add your PPA via: sudo add-apt-repository ppa:xorg-edgers/nouveau
    - Install the kernel via e.g. Synaptic (I'm on 64Bit hope it is there also)
    - disable my blacklist.conf line I've added "Blacklist nouveau"
    - Un-install my NVidea 1.9x restricted driver
    - Reboot and choose the correct new kernel in the grep menu
    - cross my fingers and hope it boot up without any additional boot parameters
    - Report my finding here...

 Correct?

@Cor: 1) Νίκος Αλεξανδρής and me tried this already and it's not working. He deleted the kernel from his ppa. The 2.6.32.20 in the official Lucid repositories has nothing to do with this.
2) correct

@Cor: The nouveauquirk package is still in the PPA. Yes, you'll need to manually install the kernel, because the new 2.6.32-20 kernel has superseded it.

This will also be in an upcoming kernel upload if you don't want to manually install the kernel.

Your steps in (2) seem correct.

To the others:
I'm not sure where using “vga=...” is coming from. It's my understanding that the kernel no longer recognises those settings; instead, it's video= and kms drivers. Perhaps a dmesg from when you're booting like that would be helpful? I'd like to work out why disabling acceleration is no longer working for you.

Confirming that for my MacBook Pro 5,1 I can only successfully boot the beta 2 livecd with the options nouveau.noaccel=1 blacklist-vga16fb otherwise the boot hangs. Trying with nomodeset also doesn't work for me.

Ok, I've pulled in a bunch of Chris' patches to disable acceleration out of the box for these cards. Could those of you affected please test the kernel at the URL below and report back here. The kernels are at the URL below. Thanks:

    http://people.canonical.com/~apw/raof-nv-accel-lucid/

This bug was fixed in the package linux - 2.6.32-21.31

---------------
linux (2.6.32-21.31) lucid; urgency=low

  [ Andy Whitcroft ]

  * allow modules.builtin to be optional
  * d-i: add mpt2sas to the message-modules udeb
    - LP: #530361

  [ Christopher James Halse Rogers ]

  * SAUCE: Nouveau: Add quirk framework to disable acceleration
    - LP: #544088, #546393
  * SAUCE: Nouveau: Disable acceleration on MacBook Pros
    - LP: #546393
  * SAUCE: Nouveau: Disable acceleration on GeForce3 cards
    - LP: #544088
  * SAUCE: Nouveau: Disable acceleration on 6100 cards
    - LP: #542950

  [ Stefan Bader ]

  * SAUCE: dma-mapping: Remove WARN_ON in dma_free_coherent
    - LP: #458201

  [ Surbhi Palande ]

  * SAUCE: sync before umount to reduce time taken by ext4 umount
    - LP: #543617

  [ Upstream Kernel Changes ]

  * tipc: Fix oops on send prior to entering networked mode (v3)
    - CVE-2010-1187
  * KVM: x86 emulator: Add Virtual-8086 mode of emulation
    - LP: #561425
  * KVM: x86 emulator: fix memory access during x86 emulation
    - LP: #561425
  * KVM: x86 emulator: Check IOPL level during io instruction emulation
    - LP: #561425
  * KVM: x86 emulator: Fix popf emulation
    - LP: #561425
  * KVM: Fix segment descriptor loading
    - LP: #561425
  * KVM: VMX: Update instruction length on intercepted BP
    - LP: #561425
  * KVM: VMX: Use macros instead of hex value on cr0 initialization
    - LP: #561425
  * KVM: SVM: Reset cr0 properly on vcpu reset
    - LP: #561425
  * KVM: VMX: Disable unrestricted guest when EPT disabled
    - LP: #561425
  * KVM: x86: disable paravirt mmu reporting
    - LP: #561425
  * AppArmor: Fix put of unassigned ns if aa_unpack fails
  * AppArmor: Fix refcount bug when exec fails
    - LP: #562063
  * AppArmor: Take refcount on cxt->profile to ensure it remains a valid
    reference
    - LP: #367499
  * AppArmor: fix typo in scrubbing environment variable warning
    - LP: #562060
  * AppArmor: fix regression by setting default to mediate deleted files
    - LP: #562056
  * AppArmor: fix refcount order bug that can trigger during replacement
    - LP: #367499
  * AppArmor: Make sure to unmap aliases for vmalloced dfas before they are
    live
    - LP: #529288
  * AppArmor: address performance regression of replaced profile
    - LP: #549428
  * AppArmor: make the global side the correct type
    - LP: #562047
  * AppArmor: use the kernel shared workqueue to free vmalloc'ed dfas
  * sky2: add register definitions for new chips
    - LP: #537168
  * sky2: 88E8059 support
    - LP: #537168
  * net: Fix Yukon-2 Optima TCP offload setup
    - LP: #537168
  * net: Add missing TST_CFG_WRITE bits around sky2_pci_write
    - LP: #537168
  * sky2: print Optima chip name
    - LP: #537168
  * (Upstream) dell-laptop: defer dell_rfkill_update to worker thread
    - LP: #555261
  * drm/nv40: add LVDS table quirk for Dell Latitude D620
    - LP: #539730
 -- Andy Whitcroft <email address hidden> Tue, 13 Apr 2010 18:50:58 +0100

OMG, this is the most beautiful day of my life.

I'm looking forward to the 2.6.31 kernel and will come back to this place in anger if it isn't working ;-)

*2.6.32.-21.31

@Andy Whitcroft I booted your kernel from post #118 with no problems! Works for me!

I did normal quite splash with no additional options. Great.

Just wanted to start testing the ppa:xorg-edgers/nouveau but decided to read the status of bug first. Now a new question arose.

Q: Does this mean the daily build of the CD image of 20100414 will contain the patch and we should be be able to normally boot from this CD now?

YES! I've tested the new kernel Linux 2.6.32-21-generic #31~raofnvaccel201004131332 SMP Tue Apr 13 13:06:14 UTC 2010 x86_64 GNU/Linux. from http://people.canonical.com/~apw/raof-nv-accel-lucid/

Note that I removed the blacklist.conf entry for nouveau and also removed the restricted Nvidia video drivers beforehand

GREAT, indeed I could boot normally, see below for a part of the log. THANKS to eveyone to help to let Apple macbookpro owners the option to "Switch Again" ;) to Linux. Now I can continue to perform more beta testing on Lucid Lynx 10.04.

I used the normal boot line, NO additional parameters added, happy happy!

...
[ 16.490396] nouveau 0000:02:00.0: power state changed by ACPI to D0
[ 16.490412] nouveau 0000:02:00.0: PCI INT A -> Link[Z003] -> GSI 23 (level, low) -> IRQ 23
[ 16.490423] nouveau 0000:02:00.0: setting latency timer to 64
[ 16.492570] [drm] nouveau 0000:02:00.0: Detected an NV50 generation card (0x096380c1)
[ 16.493554] [drm] nouveau 0000:02:00.0: Detected MacBook Pro 9600GT chip. Disabling acceleration
[ 16.493561] [drm] nouveau 0000:02:00.0: Attempting to load BIOS image from PRAMIN
[ 16.570987] [drm] nouveau 0000:02:00.0: ... appears to be valid
[ 16.570989] [drm] nouveau 0000:02:00.0: BIT BIOS found
[ 16.570991] [drm] nouveau 0000:02:00.0: Bios version 62.94.78.00
[ 16.570993] [drm] nouveau 0000:02:00.0: TMDS table revision 2.0 not currently supported
[ 16.570995] [drm] nouveau 0000:02:00.0: Found Display Configuration Block version 4.0
[ 16.570998] [drm] nouveau 0000:02:00.0: DCB connector table: VHER 0x40 5 16 4
...

BTW Can not install NVidia restricted drivers anymore via Administration -> Hardware drivers
Not in 2.6.32-21-generic and also not in 2.6.32-20-generic anymore. Also STA wifi drivers install does not work anymore...

Reinstalling the headers via the DEB here from http://people.canonical.com/~apw/raof-nv-accel-lucid/ solved my issue. Could now re-install NVidia restricted video drivers and also the STA restricted for Wifi.

For short, if this nouveau fix goes into the Lucid Lynx RC1 installing straight from CD will be possible again on a Macbookpro.

Ofcourse there will be lots of other issues no doubt, but we can then help solving these in the future and help improving the relevant MacBookPro Lucid Wiki pages.

THX to all of you giving input in this bug and anyone giving their energy to Linux opensource development!

Attempting to install 10.10 Desktop Beta 1 to a MBP5,1 led to the symptoms shown in this bug for lucid: attempting to install or boot to the live CD yielded a black screen with blinking cursor.

Using the work-around (nouveau.noaccel=1 blacklist=vga16fb) allowed the live CD to boot. I then switched to the nVidia driver and the system boots fine.

@Brad -- would you be able to boot test the kernels below (without the nvidia binary driver) if this works we can try and get these patches into the final release CDs. Kernels are at the URL below:

    http://people.canonical.com/~apw/lp546393-maverick/

Please report back here. Thanks.

@Brad -- any chance of some testing of those kernels. We have a very small window to get this fix into the final kernel else it will miss the release.

@Andy, I installed:

linux-headers-2.6.35-22-generic_2.6.35-22.32lp546393v201009161446_i386.deb
linux-image-2.6.35-22-generic_2.6.35-22.32lp546393v201009161446_i386.deb

And then disabled the nVidia driver and rebooted. It booted with the nouveau driver just fine.

Thanks!

Thank you Andy and Brad, you are heroes!

This bug was fixed in the package linux - 2.6.35-22.33

---------------
linux (2.6.35-22.33) maverick; urgency=low

  [ Andy Whitcroft ]

  * Revert "SAUCE: Add support for Intellimouse Mode in ALPS touchpad on
    Dell E2 series Laptops"
    - LP: #641320

  [ Brian Rogers ]

  * SAUCE: ir-core: Fix null dereferences in the protocols sysfs interface
    - LP: #624701

  [ Christopher James Halse Rogers ]

  * SAUCE: Nouveau: Add quirk framework to disable acceleration
    - LP: #544088, #546393
  * SAUCE: Nouveau: Disable acceleration on MacBook Pros
    - LP: #546393

  [ John Johansen ]

  * Revert "SAUCE: AppArmor: allow newer tools to load policy on older
    kernels"
  * SAUCE: AppArmor: allow newer tools to load policy on older kernels
    - LP: #639758

  [ Mathieu J. Poirier ]

  * SAUCE: Adding vdd_sdi regulator supply to OMAP3EVM

  [ Upstream Kernel Changes ]

  * ALSA: HDA: Enable internal speaker on Dell M101z
    - LP: #640254
 -- Leann Ogasawara <email address hidden> Fri, 17 Sep 2010 13:21:28 -0700

Sadly the bug still exists again, after it was fixed in Lucid, it came back in Natty.

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

Yep I can confirm that the only way to succesfully boot Natty with Nouveau on my MBP5,1 is to add nouveau.noaccel=1 to the kernel command line.

Im surprised to see MBP5.1 users having problems with booting into Ubuntu.
ive run ubuntu successfully for the last three releases when using the proprietary nvidia driver

What usually messed things up for me was what card was selected in OSX as the active card.
toggling this might be what gets you booted (my macbook has the 9600 and the 9400 nvidia card) into the installation.

Also , i run my macbook in efi mode nowdays, all works fine except that one needs to add a more up to date backlight module

adding this to grub console will disable your 9600 card before booting into your os and hence save battery.

outb 0x728 2
outb 0x710 2
outb 0x740 2
outb 0x750 0

@Tomodachi - if you note, the bug refers to the nouveau driver, not the binary one - with the nouveau driver it fails to successfully boot UNLESS acceleration is disabled - ie. it only boot successfully if you add:

nouveau.noaccel=1

to the kernel command line

The second issue is then that Xorg may pick to use the wrong card (ie the one which the display is not connected to - but this can be controlled by either disabling say the 9600 card as you do, or by specifying which card to use via its PCI device id in the device section of xorg.conf with something like:

BusID "PCI:3:0:0" # this selects the 9400M

How exactly can I find out if my MBP 5,2 has two video cards? I was not aware of this...

If it definitely is a MacBook Pro (emphasis on the Pro) then it does (a lower powered 9400M and a higher powered 9600M GT - you should be able to see both under OSX which boot via native EFI) - however by default Ubuntu will boot via BIOS emulation in which case the 9400M is automatically disabled by the Apple EFI firmware or some such - BUT if you boot Ubuntu via EFI then it should see both cards.

I´ve just managed to get the 12.04 LiveCD to boot into a GUI on my MacBook Pro 5,2

/sys/class/dmi/id/bios_vendor:Apple Inc.
/sys/class/dmi/id/bios_version: MBP52.88Z.008E.B05.0905042202
/sys/class/dmi/id/bios_date:05/04/09
/sys/class/dmi/id/sys_vendor:Apple Inc.
/sys/class/dmi/id/product_name:MacBookPro5,2
/sys/class/dmi/id/product_version:1.0
/sys/class/dmi/id/board_vendor:Apple Inc.
/sys/class/dmi/id/board_name:Mac-F2268EC8
/sys/class/dmi/id/board_asset_tag:Base Board Asset Tag#
/sys/class/dmi/id/chassis_vendor:Apple Inc.
/sys/class/dmi/id/chassis_type:8
/sys/class/dmi/id/chassis_version:Mac-F2268EC8

I had to add the following to the grub menu entry prior to booting:

 outb 0x728 1
 outb 0x710 2
 outb 0x740 2
 outb 0x750 0
 set gfxpayload=keep
 linux /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash nouveau.noaccel=1 --

I also made sure that the Power Saving settings in OS X were set to ¨Performance¨.

The screen initially goes black before eventually flickering and then showing the gui desktop. Adding blacklist=vga16fb or nomodeset, either together or individually on the kernel line resulted in X not starting and being dropped to a console.

FWIW this is being posted from the LiveCD (USB) during installation after installing the Broadcom restricted drivers and connecting to a WiFi network (802.11n WPA2 encrypted).

I´ll let you know how things go after the reboot...

System rebooted OK, had to add same options to grub to get GUI to display. Once up and running installed the restricted NVidia drivers and rebooted.

Booted to GUI with no additional options added to grub, NVidia splash screen displayed briefly then default desktop.

Now to get rEFIt back as the boot loader so I can boot into OS X again .... :(

Christopher "cv", this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

The bug is still present and nothing has changed. I can not install any current ubuntu but I tried the daily live cd as you suggested. The current kernel i tried in the live cd is

ubuntu@ubuntu:~$ uname -a
Linux ubuntu 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:39:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I repeat: the bug is exactly the same as it was 3 years ago.

If I type in "acpi=off" AND "nomodeset" in the command promnt on boot up of the live CD it will boot up, otherwise it will fail. Excatly the same behaviour as 3 years ago.

Christopher "vc", thank you for testing Trusty. Could you please answer the following questions:
1) Given that you may boot into the Trusty live environment via a WORKAROUND, are you able to install it?
2) If you cannot install it, could you please provide the information necessary to debug the problem via https://wiki.ubuntu.com/DebuggingUbiquity ?

I can install it. I have Ubuntu running right now on the Mac Book Pro. It's the Noveau driver. After the first boot, I can install the official NVIDIA driver and no more problems.

Christopher "cv", thank you for your response. Could you please attach Trusty logs for the failure boot without WORKAROUNDs via https://wiki.ubuntu.com/DebuggingUbiquity ?