After new Zorin 17 install VERY long blank screen before login

After a successful Zorin 17 install, I had to run the boot repair utility from a USB boot, because it would not boot after an initial successful boot and login. My intentions were to be dual boot with an existing Win10 install (Legacy), but that didn't work as it won't boot to Win10 (not worried about it as my data is still accessible via Zorin). The boot repair didn't do anything, still get a blank screen. To share what others here may have gone through, I did see and accepted the Zorin OS updates after I was logged in. After a reboot at some point after, that's when I got the blank screen. Oddly enough, a couple of times it took about 5-10 minutes and suddenly the login screen did popup and allow me in, but for the most part it's broken. I suspect the update may have hosed it. Can someone please provide me the steps to roll back or perhaps fix this oddity? Thanks

Zorin OS 17.2 Pro
Linux 6.8.0-40-generic
Motherboard MSI MAG B550 TOMAHAWK with integrated Radeon graphic chip.

1 Like

Welcome to the Forum!

Are Secure Boot and Fast Boot in the BIOS disabled?
Is Fast Start-Up in Windows disabled?
Waht Tool did You used to create the bootable USB Stick?

Does that ''Legacy'' mean that Your BIOS is in Legacy Mode?

  • Secure Boot in BIOS is disabled
  • For Windows Fast Start-up, I'm not sure as I am unable to boot to Win10 after the Zorin install. Win10 does show up on the Grub menu, but it only produces a sort of "can't boot from disk" message.
  • I used balenaEtcher to create the USB boot stick
  • Yes, Legacy+UEFI, I think. I need to reboot to BIOS, which I hate doing as I never know the temperament of the boot process and if I'll get a login screen.

You could come over the BIOS in Windows ... But when you have even Problem to come to that ... You could try the Following:

Turn Your Machine off, no Stand-By or Sleep Mode. Completely down. Then press the Power button on Your Machine and immediately spam-pressing the Key for Your BIOS. It feels a bit stupid to do it that Way, I know. I had to do this in the Past this Way. So, I know that. Maybe You need some Tryings but hopefully it brings You in the BIOS.

There You could look if Fast Boot in the BIOS is turned off and then start into Windows to check for Fast Start-Up. then I would suggest to take a different Tool that BalenaEtcher. Because You are on Windows, I can recommend from personal Experience Rufus.

What you should check, too is the checksum of Your ISO. For Instructions look here:

Another Thing: When You installed Zorin, what Option did You choose? There should be 3:

  • Install Zorin alongside Windows
  • Erase Disk
  • Something else

I chose Something Else, after reading a forum article on this and manually created a new / root partition from free space on the boot SSD and leaving everything else to defaults.

I may just start over from another machine and use Rufus to create the USB boot stick.

Another theory on my current issue, since it seems to hang after the Grub menu and either get a blank screen (no cursor) or after 5-10 minutes I get a login prompt. Would there be some sort of disk check taking it's sweet time to complete and not showing the login screen? Just an idea.
EDIT: I do have a secondary 1TB HDD for data only.

Update: I used the QuickHash utility to check the integrity of the ISO hash. It matches.

@Ponce-De-Leon I believe I figured it out. When I said Secure Boot was disabled, I missed something. I'm not too familiar with TPM or TPM State. It was still enabled. Once I disabled it, any power up or restart brings up Grub and Zorin login screen comes up in about 10 seconds. I restarted 3 times and powered up for a cold boot. It always works as intended now. Thank you for hearing me out! :slight_smile:

Next is to fix the Win10 boot record w/o messing up Zorin. But...it might just be a complete redo from scratch.

4 Likes

If this works for You, You should mark Your Post as Solution. That could help other People who have the same or similar Issue.

1 Like

TPM also fixed this. I can log into Win10 again, so there was no damage done to the Windows boot record. :nerd_face: :+1:t3:

1 Like