How can you get any version of Linux to see the 2018 MacBook Pro SSD?
Clash Royale CLAN TAG#URR8PPP
up vote
17
down vote
favorite
I have tried
nvme_load=yes
in place of
quiet ---
with Ubuntu 18.04.1 and Xubuntu 18.04.df -h
results in only the system generated mounts and the installation media.
The weekly live including firmware image of Debian also fails to discover the ssd.
I have located more information on the SSD. I found this information in the system profiler on OS X High Sierra.
Apple SSD Controller:
APPLE SSD AP1024M:
Capacity: 1 TB (1,000,555,581,440 bytes)
TRIM Support: Yes
Model: APPLE SSD AP1024M
Revision: 177.77.7
Serial Number: C02829600M9JPD216
Link Width: x4
Link Speed: 8.0 GT/s
Detachable Drive: No
BSD Name: disk0
Partition Map Type: GPT (GUID Partition Table) .
Removable Media: No
S.M.A.R.T. status: Verified
lsblk
from a xubuntu 18.04.1 live installer does not show any pcie or nvme devices.
Note: the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
linux macintosh ssd
add a comment |
up vote
17
down vote
favorite
I have tried
nvme_load=yes
in place of
quiet ---
with Ubuntu 18.04.1 and Xubuntu 18.04.df -h
results in only the system generated mounts and the installation media.
The weekly live including firmware image of Debian also fails to discover the ssd.
I have located more information on the SSD. I found this information in the system profiler on OS X High Sierra.
Apple SSD Controller:
APPLE SSD AP1024M:
Capacity: 1 TB (1,000,555,581,440 bytes)
TRIM Support: Yes
Model: APPLE SSD AP1024M
Revision: 177.77.7
Serial Number: C02829600M9JPD216
Link Width: x4
Link Speed: 8.0 GT/s
Detachable Drive: No
BSD Name: disk0
Partition Map Type: GPT (GUID Partition Table) .
Removable Media: No
S.M.A.R.T. status: Verified
lsblk
from a xubuntu 18.04.1 live installer does not show any pcie or nvme devices.
Note: the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
linux macintosh ssd
Do the fail to discover it, or do they just fail to mount it?
– RalfFriedl
Aug 18 at 21:48
Well, the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
– Cheatcode
Aug 18 at 22:22
It is fairly know the latest Mac models are not compatible yet.
– Rui F Ribeiro
Aug 19 at 13:52
This question is in a French newspaper: nextinpact.com/brief/…
– Cœur
Nov 7 at 2:22
add a comment |
up vote
17
down vote
favorite
up vote
17
down vote
favorite
I have tried
nvme_load=yes
in place of
quiet ---
with Ubuntu 18.04.1 and Xubuntu 18.04.df -h
results in only the system generated mounts and the installation media.
The weekly live including firmware image of Debian also fails to discover the ssd.
I have located more information on the SSD. I found this information in the system profiler on OS X High Sierra.
Apple SSD Controller:
APPLE SSD AP1024M:
Capacity: 1 TB (1,000,555,581,440 bytes)
TRIM Support: Yes
Model: APPLE SSD AP1024M
Revision: 177.77.7
Serial Number: C02829600M9JPD216
Link Width: x4
Link Speed: 8.0 GT/s
Detachable Drive: No
BSD Name: disk0
Partition Map Type: GPT (GUID Partition Table) .
Removable Media: No
S.M.A.R.T. status: Verified
lsblk
from a xubuntu 18.04.1 live installer does not show any pcie or nvme devices.
Note: the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
linux macintosh ssd
I have tried
nvme_load=yes
in place of
quiet ---
with Ubuntu 18.04.1 and Xubuntu 18.04.df -h
results in only the system generated mounts and the installation media.
The weekly live including firmware image of Debian also fails to discover the ssd.
I have located more information on the SSD. I found this information in the system profiler on OS X High Sierra.
Apple SSD Controller:
APPLE SSD AP1024M:
Capacity: 1 TB (1,000,555,581,440 bytes)
TRIM Support: Yes
Model: APPLE SSD AP1024M
Revision: 177.77.7
Serial Number: C02829600M9JPD216
Link Width: x4
Link Speed: 8.0 GT/s
Detachable Drive: No
BSD Name: disk0
Partition Map Type: GPT (GUID Partition Table) .
Removable Media: No
S.M.A.R.T. status: Verified
lsblk
from a xubuntu 18.04.1 live installer does not show any pcie or nvme devices.
Note: the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
linux macintosh ssd
linux macintosh ssd
edited Nov 20 at 6:31
muru
35.1k581154
35.1k581154
asked Aug 18 at 21:43
Cheatcode
8914
8914
Do the fail to discover it, or do they just fail to mount it?
– RalfFriedl
Aug 18 at 21:48
Well, the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
– Cheatcode
Aug 18 at 22:22
It is fairly know the latest Mac models are not compatible yet.
– Rui F Ribeiro
Aug 19 at 13:52
This question is in a French newspaper: nextinpact.com/brief/…
– Cœur
Nov 7 at 2:22
add a comment |
Do the fail to discover it, or do they just fail to mount it?
– RalfFriedl
Aug 18 at 21:48
Well, the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
– Cheatcode
Aug 18 at 22:22
It is fairly know the latest Mac models are not compatible yet.
– Rui F Ribeiro
Aug 19 at 13:52
This question is in a French newspaper: nextinpact.com/brief/…
– Cœur
Nov 7 at 2:22
Do the fail to discover it, or do they just fail to mount it?
– RalfFriedl
Aug 18 at 21:48
Do the fail to discover it, or do they just fail to mount it?
– RalfFriedl
Aug 18 at 21:48
Well, the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
– Cheatcode
Aug 18 at 22:22
Well, the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
– Cheatcode
Aug 18 at 22:22
It is fairly know the latest Mac models are not compatible yet.
– Rui F Ribeiro
Aug 19 at 13:52
It is fairly know the latest Mac models are not compatible yet.
– Rui F Ribeiro
Aug 19 at 13:52
This question is in a French newspaper: nextinpact.com/brief/…
– Cœur
Nov 7 at 2:22
This question is in a French newspaper: nextinpact.com/brief/…
– Cœur
Nov 7 at 2:22
add a comment |
2 Answers
2
active
oldest
votes
up vote
14
down vote
It's currently not possible to install anything except Windows 10 on Apple computers equipped with T2 chip. This security chip makes it impossible to see the internal drive, Apple generously did an exception only for Windows 10 (but only if you install it via Boot Camp).
A possible option could be Linux installed on a USB/Thunderbolt external drive, unfortunately I tried this only for Windows but it worked (though the internal drive was not visible).
Update: changing the Secure Boot option makes no difference.
Source
2
Wow. Why the heck does turning off secure boot not fix the problem?! Apple says on their own site: "The 'No Security' setting doesn't enforce any of the above security requirements for your startup disk." Wat?!
– Wowfunhappy
Nov 6 at 14:50
I don't know, but it's sadly true.
– GeekUser
Nov 9 at 22:07
add a comment |
up vote
11
down vote
I have a MacBook Pro Mid 2018 and managed to get the SSD working for like 10 seconds.
When you live boot Linux Mint or Ubuntu and do:
modprobe nvme
Then check for the hardware ID of the Apple Storage controller by doing:
lspci -nn | grep NVMe
Then put that ID in the new_id file under nvme:
echo 106b 2005 > /sys/bus/pci/drivers/nvme/new_id
When you did that it shows up under lsblk
but only for like 10~30 seconds before the machine randomly turns off after 1second of full cooler spin 100%. I am not sure why this happens, but it does seem to detect it correctly as for me it showed a 500GB NVMe ssd under lsblk
. I didn't manage to get gparted
opened as it took longer than the time before it shuts off.
7
I'd be careful assuming this actually defeated the lock. Depending on how the T2 works it could be waiting for access then detecting an unauthorized access attempt and shutting down the system for protection.
– madscientist159
Nov 5 at 21:23
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
14
down vote
It's currently not possible to install anything except Windows 10 on Apple computers equipped with T2 chip. This security chip makes it impossible to see the internal drive, Apple generously did an exception only for Windows 10 (but only if you install it via Boot Camp).
A possible option could be Linux installed on a USB/Thunderbolt external drive, unfortunately I tried this only for Windows but it worked (though the internal drive was not visible).
Update: changing the Secure Boot option makes no difference.
Source
2
Wow. Why the heck does turning off secure boot not fix the problem?! Apple says on their own site: "The 'No Security' setting doesn't enforce any of the above security requirements for your startup disk." Wat?!
– Wowfunhappy
Nov 6 at 14:50
I don't know, but it's sadly true.
– GeekUser
Nov 9 at 22:07
add a comment |
up vote
14
down vote
It's currently not possible to install anything except Windows 10 on Apple computers equipped with T2 chip. This security chip makes it impossible to see the internal drive, Apple generously did an exception only for Windows 10 (but only if you install it via Boot Camp).
A possible option could be Linux installed on a USB/Thunderbolt external drive, unfortunately I tried this only for Windows but it worked (though the internal drive was not visible).
Update: changing the Secure Boot option makes no difference.
Source
2
Wow. Why the heck does turning off secure boot not fix the problem?! Apple says on their own site: "The 'No Security' setting doesn't enforce any of the above security requirements for your startup disk." Wat?!
– Wowfunhappy
Nov 6 at 14:50
I don't know, but it's sadly true.
– GeekUser
Nov 9 at 22:07
add a comment |
up vote
14
down vote
up vote
14
down vote
It's currently not possible to install anything except Windows 10 on Apple computers equipped with T2 chip. This security chip makes it impossible to see the internal drive, Apple generously did an exception only for Windows 10 (but only if you install it via Boot Camp).
A possible option could be Linux installed on a USB/Thunderbolt external drive, unfortunately I tried this only for Windows but it worked (though the internal drive was not visible).
Update: changing the Secure Boot option makes no difference.
Source
It's currently not possible to install anything except Windows 10 on Apple computers equipped with T2 chip. This security chip makes it impossible to see the internal drive, Apple generously did an exception only for Windows 10 (but only if you install it via Boot Camp).
A possible option could be Linux installed on a USB/Thunderbolt external drive, unfortunately I tried this only for Windows but it worked (though the internal drive was not visible).
Update: changing the Secure Boot option makes no difference.
Source
edited Sep 24 at 17:41
answered Sep 24 at 16:22
GeekUser
2417
2417
2
Wow. Why the heck does turning off secure boot not fix the problem?! Apple says on their own site: "The 'No Security' setting doesn't enforce any of the above security requirements for your startup disk." Wat?!
– Wowfunhappy
Nov 6 at 14:50
I don't know, but it's sadly true.
– GeekUser
Nov 9 at 22:07
add a comment |
2
Wow. Why the heck does turning off secure boot not fix the problem?! Apple says on their own site: "The 'No Security' setting doesn't enforce any of the above security requirements for your startup disk." Wat?!
– Wowfunhappy
Nov 6 at 14:50
I don't know, but it's sadly true.
– GeekUser
Nov 9 at 22:07
2
2
Wow. Why the heck does turning off secure boot not fix the problem?! Apple says on their own site: "The 'No Security' setting doesn't enforce any of the above security requirements for your startup disk." Wat?!
– Wowfunhappy
Nov 6 at 14:50
Wow. Why the heck does turning off secure boot not fix the problem?! Apple says on their own site: "The 'No Security' setting doesn't enforce any of the above security requirements for your startup disk." Wat?!
– Wowfunhappy
Nov 6 at 14:50
I don't know, but it's sadly true.
– GeekUser
Nov 9 at 22:07
I don't know, but it's sadly true.
– GeekUser
Nov 9 at 22:07
add a comment |
up vote
11
down vote
I have a MacBook Pro Mid 2018 and managed to get the SSD working for like 10 seconds.
When you live boot Linux Mint or Ubuntu and do:
modprobe nvme
Then check for the hardware ID of the Apple Storage controller by doing:
lspci -nn | grep NVMe
Then put that ID in the new_id file under nvme:
echo 106b 2005 > /sys/bus/pci/drivers/nvme/new_id
When you did that it shows up under lsblk
but only for like 10~30 seconds before the machine randomly turns off after 1second of full cooler spin 100%. I am not sure why this happens, but it does seem to detect it correctly as for me it showed a 500GB NVMe ssd under lsblk
. I didn't manage to get gparted
opened as it took longer than the time before it shuts off.
7
I'd be careful assuming this actually defeated the lock. Depending on how the T2 works it could be waiting for access then detecting an unauthorized access attempt and shutting down the system for protection.
– madscientist159
Nov 5 at 21:23
add a comment |
up vote
11
down vote
I have a MacBook Pro Mid 2018 and managed to get the SSD working for like 10 seconds.
When you live boot Linux Mint or Ubuntu and do:
modprobe nvme
Then check for the hardware ID of the Apple Storage controller by doing:
lspci -nn | grep NVMe
Then put that ID in the new_id file under nvme:
echo 106b 2005 > /sys/bus/pci/drivers/nvme/new_id
When you did that it shows up under lsblk
but only for like 10~30 seconds before the machine randomly turns off after 1second of full cooler spin 100%. I am not sure why this happens, but it does seem to detect it correctly as for me it showed a 500GB NVMe ssd under lsblk
. I didn't manage to get gparted
opened as it took longer than the time before it shuts off.
7
I'd be careful assuming this actually defeated the lock. Depending on how the T2 works it could be waiting for access then detecting an unauthorized access attempt and shutting down the system for protection.
– madscientist159
Nov 5 at 21:23
add a comment |
up vote
11
down vote
up vote
11
down vote
I have a MacBook Pro Mid 2018 and managed to get the SSD working for like 10 seconds.
When you live boot Linux Mint or Ubuntu and do:
modprobe nvme
Then check for the hardware ID of the Apple Storage controller by doing:
lspci -nn | grep NVMe
Then put that ID in the new_id file under nvme:
echo 106b 2005 > /sys/bus/pci/drivers/nvme/new_id
When you did that it shows up under lsblk
but only for like 10~30 seconds before the machine randomly turns off after 1second of full cooler spin 100%. I am not sure why this happens, but it does seem to detect it correctly as for me it showed a 500GB NVMe ssd under lsblk
. I didn't manage to get gparted
opened as it took longer than the time before it shuts off.
I have a MacBook Pro Mid 2018 and managed to get the SSD working for like 10 seconds.
When you live boot Linux Mint or Ubuntu and do:
modprobe nvme
Then check for the hardware ID of the Apple Storage controller by doing:
lspci -nn | grep NVMe
Then put that ID in the new_id file under nvme:
echo 106b 2005 > /sys/bus/pci/drivers/nvme/new_id
When you did that it shows up under lsblk
but only for like 10~30 seconds before the machine randomly turns off after 1second of full cooler spin 100%. I am not sure why this happens, but it does seem to detect it correctly as for me it showed a 500GB NVMe ssd under lsblk
. I didn't manage to get gparted
opened as it took longer than the time before it shuts off.
edited Nov 11 at 16:43
Jeff Schaller
36.4k952120
36.4k952120
answered Nov 3 at 9:37
Menno van leeuwen
11113
11113
7
I'd be careful assuming this actually defeated the lock. Depending on how the T2 works it could be waiting for access then detecting an unauthorized access attempt and shutting down the system for protection.
– madscientist159
Nov 5 at 21:23
add a comment |
7
I'd be careful assuming this actually defeated the lock. Depending on how the T2 works it could be waiting for access then detecting an unauthorized access attempt and shutting down the system for protection.
– madscientist159
Nov 5 at 21:23
7
7
I'd be careful assuming this actually defeated the lock. Depending on how the T2 works it could be waiting for access then detecting an unauthorized access attempt and shutting down the system for protection.
– madscientist159
Nov 5 at 21:23
I'd be careful assuming this actually defeated the lock. Depending on how the T2 works it could be waiting for access then detecting an unauthorized access attempt and shutting down the system for protection.
– madscientist159
Nov 5 at 21:23
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f463422%2fhow-can-you-get-any-version-of-linux-to-see-the-2018-macbook-pro-ssd%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do the fail to discover it, or do they just fail to mount it?
– RalfFriedl
Aug 18 at 21:48
Well, the installer and Gparted fail to list it. Typically these both require an unmounted drive to work with. So, it simply does not see the SSD. I read that this system uses a PCIE SSD , though im not sure how to send a kernel module to allow use of it.
– Cheatcode
Aug 18 at 22:22
It is fairly know the latest Mac models are not compatible yet.
– Rui F Ribeiro
Aug 19 at 13:52
This question is in a French newspaper: nextinpact.com/brief/…
– Cœur
Nov 7 at 2:22