Bug #8662
Network device is not detected on MacBook Pro with retina display 2014
0%
Description
It’s a MacBook Pro 11,1 (mid 2014) with retina display. I also tried running “sudo rfkill list” and nothing was detected except bluetooth.
Please see screenshot.
Files
Subtasks
Related issues
Related to Tails - |
Rejected | 2014-08-19 |
History
#1 Updated by intrigeri 2015-01-10 08:55:50
- Subject changed from TAILS does not detect network device on MacBook Pro with retina display 2014 to Network device is not detected on MacBook Pro with retina display 2014
- Category set to Hardware support
- Assignee set to bluewater
- QA Check set to Info Needed
- Type of work changed from Code to Research
- can you confirm this is the mid-2014 model listed on https://en.wikipedia.org/wiki/MacBook_Pro#Technical_specifications_3 ?
- 13 or 15"?
- can you reproduce that issue with our latest experimental Jessie ISOs? (http://nightly.tails.boum.org/build_Tails_ISO_feature-jessie/) It has the
wl
driver, that should be the one you need (I think).
#2 Updated by bluewater 2015-01-13 16:44:11
intrigeri wrote:
> * can you confirm this is the mid-2014 model listed on https://en.wikipedia.org/wiki/MacBook_Pro#Technical_specifications_3 ?
it is
> * 13 or 15“?
13
> * can you reproduce that issue with our latest experimental Jessie ISOs? (”$":http://nightly.tails.boum.org/build_Tails_ISO_feature-jessie/) It has the wl
driver, that should be the one you need (I think).
I’m on it. currently donwloading the iso, I’ll try it and report back ASAP.
#3 Updated by intrigeri 2015-01-15 11:13:32
- related to
Feature #7798: Support more Broadcom Wi-Fi chipsets added
#4 Updated by BitingBird 2015-04-10 17:04:57
bluewater, any news on that?
#5 Updated by BitingBird 2016-06-29 06:10:27
bluewater, is it still the case with current Tails?
If we don’t get an answer soonish, I’ll close the ticket because it doesn’t have enough info to do something with.
#6 Updated by BitingBird 2016-10-16 05:28:19
- Status changed from New to Rejected
No info provided -> closing.
Please reopen if that’s still the case and you can provide additional info :)