F5F Stay Refreshed Software Operating Systems Dell Inspiron 3000 line: Linux installation doesn't support EMCM boot mode

Dell Inspiron 3000 line: Linux installation doesn't support EMCM boot mode

Dell Inspiron 3000 line: Linux installation doesn't support EMCM boot mode

G
gdog557
Member
218
05-23-2016, 04:54 AM
#1
I own a Dell Inspiron laptop purchased a year ago specifically for C++ development on a Linux system. I prefer not to use Windows tools for this purpose. Initially, I managed to install and run Linux Mint after setting it up. Recently, I had it sent back to Dell for USB ports and keyboard replacement due to hardware issues. Upon return, it came back with a fresh Windows 10 installation. When attempting to reinstall Linux Mint, the process works until I try to boot into Linux normally, at which point I see a message indicating no bootable drives are available. I've tried several Linux distributions—Ubuntu, xUbuntu, lUbuntu, Arch, and various Mint versions—but none have worked. I'm curious if Dell made any changes during the repair that might be preventing Linux from installing properly. My situation seems to mirror a similar issue described in an older post without a clear resolution.
G
gdog557
05-23-2016, 04:54 AM #1

I own a Dell Inspiron laptop purchased a year ago specifically for C++ development on a Linux system. I prefer not to use Windows tools for this purpose. Initially, I managed to install and run Linux Mint after setting it up. Recently, I had it sent back to Dell for USB ports and keyboard replacement due to hardware issues. Upon return, it came back with a fresh Windows 10 installation. When attempting to reinstall Linux Mint, the process works until I try to boot into Linux normally, at which point I see a message indicating no bootable drives are available. I've tried several Linux distributions—Ubuntu, xUbuntu, lUbuntu, Arch, and various Mint versions—but none have worked. I'm curious if Dell made any changes during the repair that might be preventing Linux from installing properly. My situation seems to mirror a similar issue described in an older post without a clear resolution.

X
54
05-23-2016, 07:22 AM
#2
Check the fix here: https://askubuntu.com/questions/879986/e...ity/883179