Can't install Ubuntu 16.04.4 LTS from a flash drive [closed]
You can skip to the second paragraph of this post to see what my problem is, but I thought it could be useful to add some informations about my computer. I'm trying to do this on an Acer Aspire E5-771G-50JH with Windows 10 installed in one partition and about 230 gigs of unallocated disk space. I had already installed Fedora on this laptop, but then I formatted the hard drive and reinstalled Windows, and updated the BIOS to the latest version. I successfully installed Kali Linux (the latest version, yes I know it was a dumb decision, but I couldn't use my wireless adapter when running it on a virtual machine, and the live version on the USB stick wouldn't boot), but it always got stuck at boot. So I wiped the two partitions that were created when installing it (getting a total of 230 GB of unallocated space), and used the Windows 10 installation USB stick to restore the MBR, so that I wouldn't see GRUB when turning on my laptop. Even after doing this, for some reason Kali is listed in the boot options in my BIOS. Anyway, I downloaded the 64 bit version of Ubuntu 16.04.4 LTS, verified the SHA256 checksum of the .iso file, and created a bootable USB flash drive with Rufus.
When I boot from the USB drive, I can choose to try Ubuntu without installing or to install it. After choosing either one I get a black screen and I'm not able to do anything, but after about 14 seconds from the moment I pressed enter on the chosen option, I get this message on my screen for less than a second:
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata: please update microcode to version: 0x20 (or later)
After that nothing happens. I've tried using different flash drives and checking for errors but everything seems fine. In my BIOS boot mode is set to UEFI (instead of Legacy) and secure boot is disabled.
This is not a duplicate question of Ubuntu 17.10 LIVE USB Firmware Bug TSC_DEADLINE , as his error message is different from mine and I only see it for less than a second. I tried the solution described in the answer for that question and it didn't work.
EDIT: problem solved, I had to replace the kernel boot parameters quiet splash
with nomodeset
.
boot live-usb usb-drive microcode
closed as off-topic by Thomas Ward♦ Jan 23 at 17:18
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
You can skip to the second paragraph of this post to see what my problem is, but I thought it could be useful to add some informations about my computer. I'm trying to do this on an Acer Aspire E5-771G-50JH with Windows 10 installed in one partition and about 230 gigs of unallocated disk space. I had already installed Fedora on this laptop, but then I formatted the hard drive and reinstalled Windows, and updated the BIOS to the latest version. I successfully installed Kali Linux (the latest version, yes I know it was a dumb decision, but I couldn't use my wireless adapter when running it on a virtual machine, and the live version on the USB stick wouldn't boot), but it always got stuck at boot. So I wiped the two partitions that were created when installing it (getting a total of 230 GB of unallocated space), and used the Windows 10 installation USB stick to restore the MBR, so that I wouldn't see GRUB when turning on my laptop. Even after doing this, for some reason Kali is listed in the boot options in my BIOS. Anyway, I downloaded the 64 bit version of Ubuntu 16.04.4 LTS, verified the SHA256 checksum of the .iso file, and created a bootable USB flash drive with Rufus.
When I boot from the USB drive, I can choose to try Ubuntu without installing or to install it. After choosing either one I get a black screen and I'm not able to do anything, but after about 14 seconds from the moment I pressed enter on the chosen option, I get this message on my screen for less than a second:
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata: please update microcode to version: 0x20 (or later)
After that nothing happens. I've tried using different flash drives and checking for errors but everything seems fine. In my BIOS boot mode is set to UEFI (instead of Legacy) and secure boot is disabled.
This is not a duplicate question of Ubuntu 17.10 LIVE USB Firmware Bug TSC_DEADLINE , as his error message is different from mine and I only see it for less than a second. I tried the solution described in the answer for that question and it didn't work.
EDIT: problem solved, I had to replace the kernel boot parameters quiet splash
with nomodeset
.
boot live-usb usb-drive microcode
closed as off-topic by Thomas Ward♦ Jan 23 at 17:18
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Most Acer need UEFI update. Have you been consisent about always installing in UEFI boot mode? And all Acer require "trust" on grub/ubuntu .efi boot files. Acer Spin 5 Ubuntu 17.04 Needs Acer password & trust askubuntu.com/questions/908854/… & Acer Aspire E15 will not dual boot, many details Trust settings in step 35 askubuntu.com/questions/627416/…
– oldfred
May 4 '18 at 19:38
add a comment |
You can skip to the second paragraph of this post to see what my problem is, but I thought it could be useful to add some informations about my computer. I'm trying to do this on an Acer Aspire E5-771G-50JH with Windows 10 installed in one partition and about 230 gigs of unallocated disk space. I had already installed Fedora on this laptop, but then I formatted the hard drive and reinstalled Windows, and updated the BIOS to the latest version. I successfully installed Kali Linux (the latest version, yes I know it was a dumb decision, but I couldn't use my wireless adapter when running it on a virtual machine, and the live version on the USB stick wouldn't boot), but it always got stuck at boot. So I wiped the two partitions that were created when installing it (getting a total of 230 GB of unallocated space), and used the Windows 10 installation USB stick to restore the MBR, so that I wouldn't see GRUB when turning on my laptop. Even after doing this, for some reason Kali is listed in the boot options in my BIOS. Anyway, I downloaded the 64 bit version of Ubuntu 16.04.4 LTS, verified the SHA256 checksum of the .iso file, and created a bootable USB flash drive with Rufus.
When I boot from the USB drive, I can choose to try Ubuntu without installing or to install it. After choosing either one I get a black screen and I'm not able to do anything, but after about 14 seconds from the moment I pressed enter on the chosen option, I get this message on my screen for less than a second:
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata: please update microcode to version: 0x20 (or later)
After that nothing happens. I've tried using different flash drives and checking for errors but everything seems fine. In my BIOS boot mode is set to UEFI (instead of Legacy) and secure boot is disabled.
This is not a duplicate question of Ubuntu 17.10 LIVE USB Firmware Bug TSC_DEADLINE , as his error message is different from mine and I only see it for less than a second. I tried the solution described in the answer for that question and it didn't work.
EDIT: problem solved, I had to replace the kernel boot parameters quiet splash
with nomodeset
.
boot live-usb usb-drive microcode
You can skip to the second paragraph of this post to see what my problem is, but I thought it could be useful to add some informations about my computer. I'm trying to do this on an Acer Aspire E5-771G-50JH with Windows 10 installed in one partition and about 230 gigs of unallocated disk space. I had already installed Fedora on this laptop, but then I formatted the hard drive and reinstalled Windows, and updated the BIOS to the latest version. I successfully installed Kali Linux (the latest version, yes I know it was a dumb decision, but I couldn't use my wireless adapter when running it on a virtual machine, and the live version on the USB stick wouldn't boot), but it always got stuck at boot. So I wiped the two partitions that were created when installing it (getting a total of 230 GB of unallocated space), and used the Windows 10 installation USB stick to restore the MBR, so that I wouldn't see GRUB when turning on my laptop. Even after doing this, for some reason Kali is listed in the boot options in my BIOS. Anyway, I downloaded the 64 bit version of Ubuntu 16.04.4 LTS, verified the SHA256 checksum of the .iso file, and created a bootable USB flash drive with Rufus.
When I boot from the USB drive, I can choose to try Ubuntu without installing or to install it. After choosing either one I get a black screen and I'm not able to do anything, but after about 14 seconds from the moment I pressed enter on the chosen option, I get this message on my screen for less than a second:
[ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata: please update microcode to version: 0x20 (or later)
After that nothing happens. I've tried using different flash drives and checking for errors but everything seems fine. In my BIOS boot mode is set to UEFI (instead of Legacy) and secure boot is disabled.
This is not a duplicate question of Ubuntu 17.10 LIVE USB Firmware Bug TSC_DEADLINE , as his error message is different from mine and I only see it for less than a second. I tried the solution described in the answer for that question and it didn't work.
EDIT: problem solved, I had to replace the kernel boot parameters quiet splash
with nomodeset
.
boot live-usb usb-drive microcode
boot live-usb usb-drive microcode
edited Jan 22 at 14:10
ludoboii
asked Mar 14 '18 at 22:09
ludoboiiludoboii
64
64
closed as off-topic by Thomas Ward♦ Jan 23 at 17:18
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
If this question can be reworded to fit the rules in the help center, please edit the question.
closed as off-topic by Thomas Ward♦ Jan 23 at 17:18
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward
If this question can be reworded to fit the rules in the help center, please edit the question.
1
Most Acer need UEFI update. Have you been consisent about always installing in UEFI boot mode? And all Acer require "trust" on grub/ubuntu .efi boot files. Acer Spin 5 Ubuntu 17.04 Needs Acer password & trust askubuntu.com/questions/908854/… & Acer Aspire E15 will not dual boot, many details Trust settings in step 35 askubuntu.com/questions/627416/…
– oldfred
May 4 '18 at 19:38
add a comment |
1
Most Acer need UEFI update. Have you been consisent about always installing in UEFI boot mode? And all Acer require "trust" on grub/ubuntu .efi boot files. Acer Spin 5 Ubuntu 17.04 Needs Acer password & trust askubuntu.com/questions/908854/… & Acer Aspire E15 will not dual boot, many details Trust settings in step 35 askubuntu.com/questions/627416/…
– oldfred
May 4 '18 at 19:38
1
1
Most Acer need UEFI update. Have you been consisent about always installing in UEFI boot mode? And all Acer require "trust" on grub/ubuntu .efi boot files. Acer Spin 5 Ubuntu 17.04 Needs Acer password & trust askubuntu.com/questions/908854/… & Acer Aspire E15 will not dual boot, many details Trust settings in step 35 askubuntu.com/questions/627416/…
– oldfred
May 4 '18 at 19:38
Most Acer need UEFI update. Have you been consisent about always installing in UEFI boot mode? And all Acer require "trust" on grub/ubuntu .efi boot files. Acer Spin 5 Ubuntu 17.04 Needs Acer password & trust askubuntu.com/questions/908854/… & Acer Aspire E15 will not dual boot, many details Trust settings in step 35 askubuntu.com/questions/627416/…
– oldfred
May 4 '18 at 19:38
add a comment |
0
active
oldest
votes
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Most Acer need UEFI update. Have you been consisent about always installing in UEFI boot mode? And all Acer require "trust" on grub/ubuntu .efi boot files. Acer Spin 5 Ubuntu 17.04 Needs Acer password & trust askubuntu.com/questions/908854/… & Acer Aspire E15 will not dual boot, many details Trust settings in step 35 askubuntu.com/questions/627416/…
– oldfred
May 4 '18 at 19:38