LiveCD 14.10 - WiFi does not work until I will launch "Install Ubuntu" and skip a few steps (Macbook Pro 8.2)

Bug #1406835 reported by Michael Bell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

My computer is Macbook Pro 8,2 (15" early 2011) , although this problem could probably be witnessed at some other models as well.

First of all (as I said in my first bug report) I could boot only with nomodeset option -- otherwise I will be stuck at "i8042: no controller found" message

After booting 14.10 LiveCD, WiFi is not working and wireless networks are not available. However, if I will launch "Install Ubuntu" and get to "Installation Type" step -- right after "preparing to install ubuntu" step -- those wireless networks will "magically" appear ... (and then I could Quit the setup, and WiFi will be still working) . I've double checked - and that is not a coincidence

Those WiFi drivers have to be initialized during the boot process - otherwise it harms user experience (and also plenty of those users, who don't want to install ubuntu right now, will not guess that they would need to launch setup & skip a few steps in order to get the WiFi working)

I have attached two files to this bug report:
1) Full dmesg log
2) Small part of dmesg log which appears instantly after I get to "Installation Type" step

P.S. Notice that there are many other errors & warning during the booting process as well. Probably because it is a first Ubuntu release which does not have a separate ISO for Macs like before

Revision history for this message
Michael Bell (gorilla1337) wrote :
Revision history for this message
Michael Bell (gorilla1337) wrote :

dmesg_addition

description: updated
description: updated
tags: added: livecd mac macbook mbp utopic
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1406835/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Michael Bell (gorilla1337) wrote :

I am sorry but I cant point out a specific package which causes a problem

affects: ubuntu → ubiquity (Ubuntu)
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. If you test it and it is still an issue, kindly upload the updated logs by running only once:
apport-collect 1406835

and any other logs that are relevant for this particular issue.

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
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.