Pop OS 20.04 black screen while install with UEFI on Windows10 pro

[wdrdres3qew5ts21]

Pop OS 20.04 black screen while install with UEFI

Distribution (run cat /etc/os-release): Lenovo Yoga C930 Intel UHD620 Windows 10Pro: Dual Boot Ram 16GB : Core-I7 8550 Gen 8 U Series

Issue/Bug Description: Pop OS 20.04 black screen while install with UEFI

Steps to reproduce (if you know):

1. flash POP OS with balenaEtcher
2. disable secure boot on Windows10
3. using UEFI Flash Drive to number 1 boot loader
4. POP OS display install menu.
5. Press enter / waiting for 10 seconds
6. Screen always stuck at black/ blank screen

Other Notes: I had try Kali Linux, Zorin OS and Elementary OS it works perfectly fine but I don't know why POP OS always had blank screen I can't do anythng I had try read many discussion on internet so I think this might be important bugs. https://www.reddit.com/r/pop_os/comments/bg602f/pop_os_boot_blank_screen/ https://www.reddit.com/r/pop_os/comments/h02mk8/it_keeps_crashing_to_a_black_screen/ https://www.reddit.com/r/pop_os/comments/gx12yk/black_screen_when_trying_to_install_pop_os_intel/

[WereDev]

I have a similar issue on an MSI Prestige 15. I see the install menu and then it goes to a black screen. I can't escape to a terminal, it seems the system locks up. What's curious is that I had 20.04 running on this machine so the install worked at one time, but wanting to reinstall after tinkering with Manjaro, now I get stuck at the black screen.

Thinking something might have change with the installer, I tried various versions of the ISO. pop-os_20.04_amd64_nvidia_3.iso installs just fine. I also tried version 4, 5, 7, and 11; all had the black screen issue. It seems whatever changed in the installer between 3 and 4 is likely the culprit.

[WereDev]

Might be related to #1058 ?

[ItaloCovas]

I'm having the same issue, just installed in another machine and worked but on mine it crashes after clicking "Try/Install Pop OS!"

[WereDev]

This is still a problem, even with 21.04. I gave up and am using Fedora now. Took some additional tweaking with TLP and NVidia drivers but is working well so far.

[ItaloCovas]

It just worked now with LTS version. Then I updated to 21.04 and got black screen after login, but I reinstalled nvidia drivers and worked again, 21.04 is amazing!

[LimpingNinja]

Same issue here.

[Am1nCmd]

is there any update solution?

I still have this error using NVidia also without NVidia iso

LTS version not tested

[ItaloCovas]

Try LTS version, worked for me.

[Am1nCmd]

Same issue using LTS with NVidia

Sent from my iPhone

On 26 Aug 2021, at 9.43 PM, Italo Covas @.***> wrote:



Try LTS version, worked for me.

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/pop-os/pop/issues/1112#issuecomment-906475355, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADVBANPDDD6PCDEVC33SG2LT6ZHIJANCNFSM4OKTDOBQ.

[LimpingNinja]

LTS did not work with me, neither was there a difference between NVIDIA and Normal ISO. Both failed, I was able to install Ubuntu fine (all releases) and Manjaro (Gnome) is currently installed with no problem as a poor man's replacement for Pop!_OS

[cpmalek]

Had the same issue with my Surface Pro 3. Get it running by disabling SMT (Simultaneous Multithreading). Perhaps this is useful for somebody...

[Am1nCmd]

Had the same issue with my Surface Pro 3. Get it running by disabling SMT (Simultaneous Multithreading). Perhaps this is useful for somebody...

how did you disable SMT?

[profblackjack]

Old thread, but wanted to let the internet know when they search: on my Yoga 920 I had to disable Intel SMT in the BIOS, and then the live usb would boot correctly

[Star-Bandit]

I was also having this problem with 21.04 and 20.04 LTS on my NUC. I had previously had 20.04 LTS on it, switched to KDE and when I came back the new boot installer wasn't working correctly. I have managed to fix how to do it on a NUC.

In BIOS settings > Security >

• Intel Platform Trust Technology > uncheck
• Intel Software Guard Extensions (SGX) > Disabled
• iSetupCfg Password Check > Bypass

These are the changes I made to my system. I am not sure if any of them individually or all the above are what fixed the problem but I was able to successfully boot and install the LTS and 21.04 after this. Hope this helps someone else.

[LimpingNinja]

• Intel Software Guard Extensions (SGX) > Disabled

I left the TPM on and disabled software guard extensions; this solves on an HP Envy 32 AIO. There is a second problem where black screen can still occur when you boot selectively to UEFI drive instead of just selecting UEFI boot order.

You can tell on the ENVY because of you select directly you get a high-res "Try/Install" logo screen; if you let it cycle to the USB by itself you get low-res try screen but install works.

[echokrist]

I had similiar issues with my MSI Prestige 15 trying to install the Pop OS 22.04 LTS with NVIDIA proprietary drivers. UEFI or UEFI with CSM BIOS setting would not work, those settings resulted in either a black screen, kernel not being able to load the NVIDIA drivers or an out of memory error.

The solution for my MSI Prestige 15 was to use the Legacy BIOS option, that made me able to install and use the Pop OS 22.04 LTS with NVIDIA drivers.

While when installing Pop OS 22.04 LTS with Intel drivers on my Lenovo Thinkpad X1 Carbon G7 worked just fine with UEFI BIOS setting enabled.

I would like to note that both laptops have Secure Boot disabled.

I am unaware as to why this is, but hopefully this information can help someone out there.

[bovinezro]

Another data point to help those who get here from a google search: I had the same experience as crnial, except with an MSI Prestige 14 A10SC-021. Attempting to install 22.04 LTS with NVIDIA drivers led to a black screen. Switching from UEFI to Legacy resolved the issue.

Interestingly, 21.10 installed fine on this machine with UEFI enabled but 22.04 LTS would immediately black screen and seemed to be completely unresponsive. Disabling UEFI and using the Legacy boot option worked, using the same installation media (I didn't suspect the media as it worked fined on another machine earlier in the day). Secure Boot was disabled during both attempts.

[oCtodur]

Same same on Prestige 15 A10SC, black screen with UEFI, but legacy works. However, after installing PopOS I get error on grub so it won't boot. To be more precise this is what happens:

[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "apt-get" "autoremove" "-y" "--purge"
[INFO distinst:crates/chroot/src/command.rs:99] Reading package lists...
[INFO distinst:crates/chroot/src/command.rs:99] Building dependency tree...
[INFO distinst:crates/chroot/src/command.rs:99] Reading state information...
[INFO distinst:crates/chroot/src/command.rs:99] The following packages will be REMOVED:
[INFO distinst:crates/chroot/src/command.rs:99]   efibootmgr*
[INFO distinst:crates/chroot/src/command.rs:99] 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
[INFO distinst:crates/chroot/src/command.rs:99] After this operation, 93.2 kB disk space will be freed.
[INFO distinst:crates/chroot/src/command.rs:99] (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 197695 files and directories currently installed.)
[INFO distinst:crates/chroot/src/command.rs:99] Removing efibootmgr (17-1ubuntu2) ...
[INFO distinst:crates/chroot/src/command.rs:99] Processing triggers for man-db (2.10.2-1) ...
[INFO distinst:src/installer/steps/configure/chroot_conf.rs:372] creating recovery partition
[WARN distinst:src/installer/steps/configure/chroot_conf.rs:381] recovery at /tmp/distinst.5v9VjAvHYBqC/recovery was not found, therefore no recovery partition will be created
[INFO distinst:src/installer/steps/configure/chroot_conf.rs:73] configuring bootloader
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "kernelstub" "--esp-path" "/boot/efi" "--add-options" "quiet loglevel=0 systemd.show_status=false splash" "--loader" "--manage-only" "--force-update" "--verbose"
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "update-grub"
[WARN distinst:crates/chroot/src/command.rs:99] Sourcing file `/etc/default/grub'
[WARN distinst:crates/chroot/src/command.rs:99] Sourcing file `/etc/default/grub.d/init-select.cfg'
[WARN distinst:crates/chroot/src/command.rs:99] Generating grub configuration file ...
[WARN distinst:crates/chroot/src/command.rs:99] Found linux image: /boot/vmlinuz-5.17.5-76051705-generic
[WARN distinst:crates/chroot/src/command.rs:99] Found initrd image: /boot/initrd.img-5.17.5-76051705-generic
[INFO distinst:src/installer/steps/configure/chroot_conf.rs:291] configuring keyboard layout
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "localectl" "set-x11-keymap" "se" "" ""
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "/usr/bin/env" "-i" "SYSTEMCTL_SKIP_REDIRECT=_" "openvt" "--" "sh" "/etc/init.d/console-setup.sh" "reload"
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "ln" "-s" "/etc/console-setup/cached_UTF-8_del.kmap.gz" "/etc/console-setup/cached.kmap.gz"
[INFO distinst:src/installer/steps/configure/chroot_conf.rs:279] re-enabling update-initramfs
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "sh" "-c" "rm /usr/sbin/update-initramfs"
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "sh" "-c" "mv /usr/sbin/update-initramfs.bak /usr/sbin/update-initramfs"
[INFO distinst:src/installer/state.rs:33] starting configuring bootloader step
[INFO distinst:src/installer/steps/bootloader.rs:35] /dev/nvme0n1: installing bootloader for Bios
[INFO distinst:crates/chroot/src/command.rs:109] running "chroot" "/tmp/distinst.5v9VjAvHYBqC" "grub-install" "--recheck" "--target=i386-pc" "/dev/nvme0n1"
[WARN distinst:crates/chroot/src/command.rs:99] Installing for i386-pc platform.
[ERROR distinst:src/installer/state.rs:37] configuring bootloader error: command failed with exit status: exit status: 1
[ERROR distinst:src/installer/mod.rs:300] errored while installing system: command failed with exit status: exit status: 1
[INFO distinst:ffi/src/installer.rs:190] Install error: command failed with exit status: exit status: 1

I'm thinking legacy mode is not the way to go here if you're dual booting, but I might be wrong. All other Zorin, Ubuntu, Fedora etc boots fine with the same mode. I'm not sure why the devs are not putting any effort in this seeing as its been going on for well over 2 years now. Tried everything on my end, ended up upgrading my bios, patched some intel firmware stuff in windows and yet, nothing works with Pop except legacy, which in the end doesn't really work to complete the installation.

Devs, this is something you need to fix. We're not 1 or 2 users in here, we're plenty!

[oCtodur]

After 4 days of trying to fix this with various boot options and OSes, I finally managed to boot into Pop OS and typing from there. For me the resolution was to download 21.10 instead and boot that one and then just upgrade the system. I did have problem with 5gHz wifi and had to connect to 2.4, that was the only issue.

I got the 21.10 .iso file from here https://linuxtracker.org/index.php?page=torrent-details&id=c89f45877e574e2deab9cc91d9eb27a021c6ef9b&hit=1

Here is how my partitions look like:

Hope this helps other peps in here who are still struggling with this. Cheers!

[LimpingNinja]

Hello everyone, just wanted to point out that the solution I used on the Envy has worked on multiple devices. I disabled the Software Guard Extensions and Secure Boot in the Bios; I disabled TPM but I have had no problem on either install with it on.

A big thing I did was go into the boot order and put the USB UEFI boot device first. LET IT BOOT itself, the resolution will be lower, but the install works. Even with all the above steps, if you request a boot menu with a keypress and select the USB UEFI device it will fail, but letting it pass through itself with the items mentioned disabled has worked on multiple systems. With the last few versions.

There is clearly something different in the pathway the systems take when you manually select UEFI vs auto-selection.

[helgatheviking]

I tried disabling secure boot and then changing the boot order and one you click on try/install i get a black screen too. Guess i won't be using this OS.

[laneparton]

I had to disable the Hybrid Graphics option (which has a note about being problematic on Linux) in BIOS on a newer Dell laptop.

[sphfaar]

Same issue on Razer blade stealth 13 (2019)

[Ejhfast]

Same issue. The trick putting the USB UEFI boot device first in the boot order didn't work for me

[dicksondickson]

I ran into this problem on the NUC 11 Pro. I was able to resolve this by turning on "virtual display emulation". This feature is built into the NUC to emulate a 1280x1024 screen when the HDMI ports are unplugged. This leads me to believe that this might a display / EDID issue. I recommend those not using the NUC try to installing popos with an old non-4K monitor.

[JmyL]

You should disable TPM 2.0 setting also! I've tried with my xps 13. After I disabled secure boot and TPM, Pop OS installation was smooth like butter :-)

[jstdk]

I have been unable to install PopOS on my Asus Vivobook (3k screen) for a long time. I normally create USB from Balena Etcher on a Mac. I tried it again today and it failed. Then I did the exact same thing from Balena on Ubuntu, now I can boot PopOS. Very strange, but happy that it works without any config changes.