WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: can CorePure64-13.1.iso support boot from UEFI ?  (Read 3152 times)

Offline lovelypp

  • Jr. Member
  • **
  • Posts: 51
can CorePure64-13.1.iso support boot from UEFI ?
« on: November 29, 2022, 05:37:54 AM »
I wrote rufus to udisk but can boot from it. I just don't why ? Can CorePure64-13.1.iso support boot from UEFI ?

thanks!

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 15240
Re: can CorePure64-13.1.iso support boot from UEFI ?
« Reply #1 on: November 29, 2022, 06:08:42 AM »
It does on my laptop, but perhaps more recent versions of uefi are different?

Offline gadget42

  • Hero Member
  • *****
  • Posts: 928
Re: can CorePure64-13.1.iso support boot from UEFI ?
« Reply #2 on: November 29, 2022, 10:42:40 AM »
secure boot?
** WARNING: connection is not using a post-quantum kex exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html

Offline lovelypp

  • Jr. Member
  • **
  • Posts: 51
Re: can CorePure64-13.1.iso support boot from UEFI ?
« Reply #3 on: November 29, 2022, 07:52:47 PM »
I have turned off safe boot. The cpuis J6412,  It can only support UEFI boot mode.
I tried many times but failed.

Offline lovelypp

  • Jr. Member
  • **
  • Posts: 51
Re: can CorePure64-13.1.iso support boot from UEFI ?
« Reply #4 on: November 29, 2022, 08:10:24 PM »
I tried another cpu (which cpu is J1900) and failed too.

Offline gadget42

  • Hero Member
  • *****
  • Posts: 928
Re: can CorePure64-13.1.iso support boot from UEFI ?
« Reply #5 on: November 29, 2022, 11:28:10 PM »
found this webpage interesting:
https://www.intel.com/content/www/us/en/products/sku/214758/intel-celeron-processor-j6412-1-5m-cache-up-to-2-60-ghz/specifications.html#specs-1-0-9

have no idea what these mean:
(without additional investigation/research/etc)
Intel AES New Instructions
Secure Key
Intel OS Guard
Intel Boot Guard
** WARNING: connection is not using a post-quantum kex exchange algorithm.
** This session may be vulnerable to "store now, decrypt later" attacks.
** The server may need to be upgraded. See https://openssh.com/pq.html