https://zmatt.net/w/index.php?title=Dell_Venue_11_Pro_no_bootable_devices_found&feed=atom&action=historyDell Venue 11 Pro no bootable devices found - Revision history2024-03-29T06:16:07ZRevision history for this page on the wikiMediaWiki 1.31.7https://zmatt.net/w/index.php?title=Dell_Venue_11_Pro_no_bootable_devices_found&diff=39&oldid=prevMatt at 12:49, 26 May 20172017-05-26T12:49:02Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 12:49, 26 May 2017</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>After installing Ubuntu on my Dell Venue 11 Pro, it failed to boot with the message "no bootable devices found".  I tried several times, from both BIOS Setup and Linux efibootmgr, to add a boot entry to start grub (/EFI/ubuntu/shimx64.efi)... but every time I rebooted this was no longer shown as a boot option.</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>After installing Ubuntu on my Dell Venue 11 Pro <ins class="diffchange diffchange-inline">7140</ins>, it failed to boot with the message "no bootable devices found".  I tried several times, from both BIOS Setup and Linux efibootmgr, to add a boot entry to start grub (/EFI/ubuntu/shimx64.efi)... but every time I rebooted this was no longer shown as a boot option.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>It turns out that the BIOS specifically looks for a file /EFI/boot/bootx64.efi to determine if a hard drive is bootable.  To work around this, you can create a dummy file /EFI/boot/bootx64.efi on the EFI system partition of the drive.  The BIOS will then automatically create a boot option for the drive, which you should disable to prevent it trying to run the empty file.  After this the normal Linux boot entry should work.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>It turns out that the BIOS specifically looks for a file /EFI/boot/bootx64.efi to determine if a hard drive is bootable.  To work around this, you can create a dummy file /EFI/boot/bootx64.efi on the EFI system partition of the drive.  The BIOS will then automatically create a boot option for the drive, which you should disable to prevent it trying to run the empty file.  After this the normal Linux boot entry should work.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The full instructions can be found at [https://bugs.launchpad.net/dell-sputnik/+bug/1499323]; the process is the same as for Dell XPS 13.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>The full instructions can be found at [https://bugs.launchpad.net/dell-sputnik/+bug/1499323]; the process is the same as for Dell XPS 13.</div></td></tr>
</table>Matthttps://zmatt.net/w/index.php?title=Dell_Venue_11_Pro_no_bootable_devices_found&diff=38&oldid=prevMatt at 12:48, 26 May 20172017-05-26T12:48:28Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 12:48, 26 May 2017</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l3" >Line 3:</td>
<td colspan="2" class="diff-lineno">Line 3:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>It turns out that the BIOS specifically looks for a file /EFI/boot/bootx64.efi to determine if a hard drive is bootable.  To work around this, you can create a dummy file /EFI/boot/bootx64.efi on the EFI system partition of the drive.  The BIOS will then automatically create a boot option for the drive, which you should disable to prevent it trying to run the empty file.  After this the normal Linux boot entry should work.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>It turns out that the BIOS specifically looks for a file /EFI/boot/bootx64.efi to determine if a hard drive is bootable.  To work around this, you can create a dummy file /EFI/boot/bootx64.efi on the EFI system partition of the drive.  The BIOS will then automatically create a boot option for the drive, which you should disable to prevent it trying to run the empty file.  After this the normal Linux boot entry should work.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The full instructions can be found at <del class="diffchange diffchange-inline">[</del>[https://bugs.launchpad.net/dell-sputnik/+bug/1499323<del class="diffchange diffchange-inline">]</del>]; the process is the same as for Dell XPS 13.</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The full instructions can be found at [https://bugs.launchpad.net/dell-sputnik/+bug/1499323]; the process is the same as for Dell XPS 13.</div></td></tr>
</table>Matthttps://zmatt.net/w/index.php?title=Dell_Venue_11_Pro_no_bootable_devices_found&diff=37&oldid=prevMatt: Created page with "After installing Ubuntu on my Dell Venue 11 Pro, it failed to boot with the message "no bootable devices found". I tried several times, from both BIOS Setup and Linux efiboot..."2017-05-26T12:47:41Z<p>Created page with "After installing Ubuntu on my Dell Venue 11 Pro, it failed to boot with the message "no bootable devices found". I tried several times, from both BIOS Setup and Linux efiboot..."</p>
<p><b>New page</b></p><div>After installing Ubuntu on my Dell Venue 11 Pro, it failed to boot with the message "no bootable devices found". I tried several times, from both BIOS Setup and Linux efibootmgr, to add a boot entry to start grub (/EFI/ubuntu/shimx64.efi)... but every time I rebooted this was no longer shown as a boot option.<br />
<br />
It turns out that the BIOS specifically looks for a file /EFI/boot/bootx64.efi to determine if a hard drive is bootable. To work around this, you can create a dummy file /EFI/boot/bootx64.efi on the EFI system partition of the drive. The BIOS will then automatically create a boot option for the drive, which you should disable to prevent it trying to run the empty file. After this the normal Linux boot entry should work.<br />
<br />
The full instructions can be found at [[https://bugs.launchpad.net/dell-sputnik/+bug/1499323]]; the process is the same as for Dell XPS 13.</div>Matt