cant daul boot PopOS and Windows on desktop (seperate drives): Updated

[Iamgeese]

My PC is a an HP Z1 Entry Level tower from 2019, Intel I9

Drives I am using are M.2 SSDs (the long thin ones)

I got both PopOs and Windows working on my fairly cheap Asus Laptop earlier this year but cannot for the life of me get my much more expensive desktop to do the same thing. I installed a blank disk with pop OS flashed to a memory stick and I get a big fat nothing, I dont even get the HP screen to show up, the Bios wont show up. Safe boot wa s disabled at least as far as I know.

After many hours of farting around and no bios screen I got annoyed and gave up. Put the Windows drive back in (along side the blank one). Still no HP start screen and although I can see the other blank drive I cant really load anything on there. Each time I press any of the buttons to boot into the bios I get hear a beep sound like its just swearing at me.

Now I thought if I put a blank drive in then the computer would see it and try and do something with it but it does nothing and wont aknowlage the memory stick. Take the computer apart each time was horrible because dispite the fact they charge you over £1000 the build quality/engineering is dogshit and i worry about damaging something.


Update: I have fixed the no Bios problem by swapping out a cable and changing the socket but no I am stuck with an annying stick problem and it looks like this when I try and boot off the stick. The stick was flashed with BalenaEtcher.

One other issue is the everytime i verify the Hash checksum for PopOs it is never ever the same as the one on the site, its always differnt so I have given up checking, i wonder if they just havent updated it.

 

[Smilax]

My PC is a an HP Z1 Entry Level tower from 2019, Intel I9

Drives I am using are M.2 SSDs (the long thin ones)

I got both PopOs and Windows working on my fairly cheap Asus Laptop earlier this year but cannot for the life of me get my much more expensive desktop to do the same thing. I installed a blank disk with pop OS flashed to a memory stick and I get a big fat nothing, I dont even get the HP screen to show up, the Bios wont show up. Safe boot wa s disabled at least as far as I know.

After many hours of farting around and no bios screen I got annoyed and gave up. Put the Windows drive back in (along side the blank one). Still no HP start screen and although I can see the other blank drive I cant really load anything on there. Each time I press any of the buttons to boot into the bios I get hear a beep sound like its just swearing at me.

Now I thought if I put a blank drive in then the computer would see it and try and do something with it but it does nothing and wont aknowlage the memory stick. Take the computer apart each time was horrible because dispite the fact they charge you over £1000 the build quality/engineering is dogshit and i worry about damaging something.

Please disregard my question in the other thread, I just saw this.

edit: Have you seen any of these screens? https://h10032.www1.hp.com/ctg/Manual/c06524599.pdf

 

[Brickwizard]

Have you changed the settings in the UEFI to recognise it [I had to on my 2015 HP desktop]
don't forget whilst in there to disable windows quick start/fast boot and do a full power re boot, not a restart from windows.
Thirdly have you made sure you have the correct M2 keyed SSD for your slot [there are 3 types one is NVMe only, one is SATA SSD only, and the third is both]
addendum
oh and remember to make sure boot from USB is enabled

 

[Iamgeese]

Have you changed the settings in the UEFI to recognise it [I had to on my 2015 HP desktop]
don't forget whilst in there to disable windows quick start/fast boot and do a full power re boot, not a restart from windows.
Thirdly have you made sure you have the correct M2 keyed SSD for your slot [there are 3 types one is NVMe only, one is SATA SSD only, and the third is both]
addendum
oh and remember to make sure boot from USB is enabled

I fixed the problem by changing the cable and putting it into a differnt input. So now the bios does show up but now I am appear to either be stuckj with a dodgy boot stick or something else

I get this message trying to boot off the stick

 

[Brickwizard]

Sounds like it is either not set for boot from USB or t may be a dodgy pen-drive

 

[Trml]

I get this message trying to boot off the stick

This is a secure boot policy. If there is no other OS on the PC, you should be able to follow the answer at (PopOS should provide the mentioned mokutil too): https://askubuntu.com/questions/1523438/verifying-shim-sbat-data-failed-security-policy-violation

 

[Iamgeese]

Please disregard my question in the other thread, I just saw this.

edit: Have you seen any of these screens? https://h10032.www1.hp.com/ctg/Manual/c06524599.pdf

I am having to look at why I keep getting different checksums to the ones on the website. I do not know if this may also be the problem.

 

[Alexzee]

I am having to look at why I keep getting different checksums to the ones on the website. I do not know if this may also be the problem.

Absolutely:-

If the check sums don't match from where you downloaded the Linux .iso it's likely corrupt.
Any time the signatures don't match it shouldn't be trusted.

Pop OS was designed by the System 76 manufacturer.

Linux Computers with Linux Preinstalled | System76 Open Source PCs

Shop Linux computers with Linux preinstalled. Explore open source computers, Pop!_OS systems, and handcrafted PCs built in the USA.

system76.com

Could be another reason why you are having difficulty.
Is the thumb drive set in the BIOS as the first device to be booted?

Like @Brickwizard said the thumb drive may be dodgy.

 

[Iamgeese]

Absolutely:-

If the check sums don't match from where you downloaded the Linux .iso it's likely corrupt.
Any time the signatures don't match it shouldn't be trusted.

Pop OS was designed by the System 76 manufacturer.

Linux Computers with Linux Preinstalled | System76 Open Source PCs

Shop Linux computers with Linux preinstalled. Explore open source computers, Pop!_OS systems, and handcrafted PCs built in the USA.

system76.com

Could be another reason why you are having difficulty.
Is the thumb drive set in the BIOS as the first device to be booted?

Like @Brickwizard said the thumb drive may be dodgy.

I download the file and its buggered right from the start before any stick burning takes place. I dont know how these keeps happening or how I can mitigate this. Its all the, could it be my ISP just doesnt like Linux?

 

[Brickwizard]

try using a torrent download

 

[Iamgeese]

try using a torrent download

will defo look at that.

 

[KGIII]

I actually have enough bandwidth to help!

Which PopOS exactly are you downloading?

I assume you're downloding it from here:

Download Pop!_OS by System76

system76.com

If that's not the source of your download, what is the source?

 

[Iamgeese]

I actually have enough bandwidth to help!

Which PopOS exactly are you downloading?

I assume you're downloding it from here:

Download Pop!_OS by System76

system76.com

If that's not the source of your download, what is the source?

yes I have not downloaded it from anywhere else and its still screwed, no matter how many times I download it and I dont know why or even how.

The version I use is Nvidia.

Since I am stuck using windows at the moment this is what I am doing to verify the checksum:

Get-FileHash C:\Users\geese\Downloads\Insertlinuxnamehere -Algorithm SHA384 | Format-List

am I even do this right?

 

[Iamgeese]

will defo look at that.

okay apparently

try using a torrent download

okay apparently PosOs doesnt have torrents. I have only ever downloaded off their site and nowhere else.

 

[KGIII]

am I even do this right?

It looks like you are doing that properly. I haven't used Windows in a while. Hmm... Yeah, it has been a long time since I last used Windows.

Well, you might not be doing it quite right.

Get-FileHash C:\Users\geese\Downloads\[B]Insertlinuxnamehere[/B] -Algorithm SHA384 | Format-List

You need to use the actual name of the .iso file. Something like this:

Get-FileHash C:\Users\geese\Downloads\pop-os_22.04_amd64_nvidia_58.iso -Algorithm SHA384

From what I've found online, you don't need the extra stuff at the end. From the command you wrote, that won't actually work -- as it needs to point to the correct file. (If you've already done that, disregard this.)

That said, I downloaded the .iso and checked it on Linux. The checksum was a match.

 

[Trml]

I get this message trying to boot off the stick

Not to distract from verifying check-sums, important task, but have you also checked your initial error is not secure-boot related? AFAIK PopOS is not bootable with it enabled.

 

[Iamgeese]

Not to distract from verifying check-sums, important task, but have you also checked your initial error is not secure-boot related? AFAIK PopOS is not bootable with it enabled.

the secure boot should not be on. Unless latest windows "update" screwed it.

 

[Alexzee]

the secure boot should not be on. Unless latest windows "update" screwed it.

I've learned from some of our members here that the Windows boot manager can sometimes be difficult to deal with. From what I understand the Windows boot manager is going to do what it always does and that is take control.

I'd check on what @Trml said in post #16.

Last thought:
The fact the our administrator KGIII was able to check the integrity of the .iso w/o any issue's (getting a match) tells me that there is something indeed specific to your HP desktop's BIOS or as I mentioned above the Windows boot mgr is going to do what it always does.

There may be ways to get around this.
Perphaps @wizardfromoz may have something in his wand to enlighten you.

 

[Alexzee]

Have you tried other distributions other than Pop OS and still get the same result?

 

[Alexzee]

Looking more into the error message:

Verifying shim SBAT data failed Security Policy Violaiton

It's linked to Windows finding an insecure version of the bootloader due to a security update that Windows performed.
Maybe with Linux command-line remove the SBAT policy.....that is if you can boot into Linux.

Try blocking the SBAT feature in Windows. LAST RESORT! ***

Verifying shim SBAT data failed: Security Policy Violation

It seems that with the recent Windows Update, for systems that have dual-boot is not letting grub start, showing the message: Verifying shim SBAT data failed: Security Policy Violation. Does anyone...

askubuntu.com

• 1. Boot into Windows.

• 2. Open the Command Prompt as an administrator.

• 3. Run the following command and press Enter: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\SBAT /v OptOut /d 1 /t REG_DWORD

• 4. Close the Command Prompt and restart your computer.

Helpful video on the issue: