Intrepid MacBook Pro 3,1 "Santa Rosa" LiveCD Disaster

Bug #327849 reported by Alex
2
Affects Status Importance Assigned to Milestone
Linux
Fix Released
High
Mactel Support
Invalid
Undecided
Unassigned
Ubuntu
Invalid
Undecided
Ricky Campbell

Bug Description

Please amend the wiki; this release is absolutely inappropriate for installation from LiveCD on a Macbook Pro 3,1 Santa Rosa.

Loved Hardy for some months. Upgrade from Hardy seemed reasonably stable. Formatted hard drive and decided to go dual-boot with Mac OS 10.5.x (previously single-booting Hardy) and encountered innumerable errors during install. Crashed upon reboot. Hundreds of lines of errors scrolled by.

Previously attempted this over a month ago and tried again today with a freshly downloaded and burned LiveCD -- same effect.

Please, PLEASE amend the wiki or otherwise warn owners of this particular MacBook Pro model against attempting install off LiveCD. I have found it all terribly misleading.

Revision history for this message
Brad Crittenden (bac) wrote :

Thanks for your bug report. The wiki at https://help.ubuntu.com/community/MacBookPro3-1/Intrepid indicates others have had success installing Intrepid so I'm unsure why your installation went so wrong.

Do you think you've hit the MBR bug documented on the wiki at at bug 222126?

Revision history for this message
Ricky Campbell (cyberdork33) wrote :

Could you post what some of the errors are maybe? What do you mean by "crash"? What did it do?

Revision history for this message
Alex (alexanderlane) wrote :

@Brad: At this point, we must assume the good people at Ubuntu are so deeply committed to the public relations side of their distribution that they end up falsely presenting it to be without compatibility problems -- even in cases where the problems are severe. My attempt to amend that wiki to warn others of potential madness was thwarted by an overzealous administrator (he meant well, I'm sure).
Here's what happens: http://bugzilla.kernel.org/show_bug.cgi?id=11811

And then we, of course, press the power button. Upon the next boot, Ubuntu forces disk check (presumably following the hard shutdown). Forced disk check inevitably fails, and we're sent along the Möbius strip of failed forced checks with no apparent way out.

This, in my estimation, would be enough to make most Linux newcomers abandon ship.

As I said, Hardy is a fantastic alternative to Intrepid for this particular hardware. I'm currently running Debian 5 ("Lenny") on this machine. After dealing with minimal workarounds (none of which prevented me from using it out of the box), it's running wonderfully.

I'm still baffled at the complete absence of documentation of these major problems within the Ubuntu MacBookPro Wiki.

Revision history for this message
Ricky Campbell (cyberdork33) wrote :

Alex, I believe we talked via email.

Your bug is valid, and should be reported here, and even mentioned in the wiki, but You make the consequences seem far more serious than they really are. Let's work to find a fix for the problem rather than telling everyone not to use a specific distribution. There are several people with your hardware using Intrepid, and thus, I think this may only effect a specific subset of all MacBookPro3,1 users.

I have added the bug against linux here.

Changed in mactel-support:
importance: Undecided → Medium
Changed in linux:
status: Unknown → Fix Released
Revision history for this message
Ricky Campbell (cyberdork33) wrote :

OK, the Linux bug was apparently fixed fixed in 2.6.27-8 or so. The current kernel in use by Intrepid is 2.6.27-11, so this should be a non-issue.

unfortunately, You are the only on that seems to be complaining of he issues you are having, and the likelihood that this issue has simply been "ignored" by other MacBookPro3,1 users is quite low. If you can present some technical information from you experience that might indicate where the issue lies, or reference some other bug that resembles your own, this cannot be fixed.

I am sorry that you had such a terrible experience with Intrepid, hopefully this issue can be resolved for future releases. For now, I am marking it as invalid against Ubuntu since the bug you referenced has already been addressed.

Changed in mactel-support:
importance: Medium → Undecided
Revision history for this message
Alex (alexanderlane) wrote :

Mr. Ricky Campbell continues to inexplicably deny the validity of this problem despite reports that the distribution in question is highly unstable on certain hardware. This is indeed a valid claim against Ubuntu Intrepid and should be assigned as such.

Revision history for this message
Alex Karpenko (alexkarpenko) wrote :

Hello Alex,

The bug you have referred us to has been fixed. It seems to me that the issue is specific to your setup. If you would like your bug to be resolved, please provide additional information so that the problem can be identified. It would be useful to know at which point the installation fails, what errors (if any) are printed, how you partition your drive, which boot manager you use (and anything else that you deem would *actually* be useful to fixing your problem).

Please understand that it is unreasonable to expect the wiki to be amended with: "this release is absolutely inappropriate for installation from LiveCD on a Macbook Pro 3,1 Santa Rosa.", when you in fact seem to be the only one who has made this claim so far.

Regards,
Alex K.

Revision history for this message
Ricky Campbell (cyberdork33) wrote :

You want to assign the bug to me? Fine.

1. I am removing the confirmed status since, nobody has confirmed anything.

2. Your issue about the community documentation wiki is not valid for the Ubuntu project. It is not official Ubuntu documentation, and thus cannot be attributed to the Ubuntu project.

3.You did provide a link to an existing bug in Linux, and they have reported back that it was fixed. If that bug was truly your problem, then this bug can be closed because the problem is fixed (and has been fixed). Obviously, you still feel that there is a problem, so I am guessing that bug had nothing to do with your problem.

4. Unless you provide any supporting information about this bug and what software it might even effect, this bug is invalid. So far you have not given anything that can enable anyone to fix anything. Until you do so, I am marking the bug as invalid. When you have supporting data to contribute, you can reopen the bug.

I hope that you can provide some information that will help us fix the issue you are having.

Revision history for this message
Ricky Campbell (cyberdork33) wrote :

No package assigned. No data provided that can indicate a problem.

Revision history for this message
Ricky Campbell (cyberdork33) wrote :

With no information on what to fix after a month, this is being marked invalid.

Changed in mactel-support:
status: New → Invalid
Changed in ubuntu:
status: Incomplete → Invalid
Changed in linux:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.