HyperTask installation https://issues.hyperbola.info/ 2020-02-10T20:00:30Z FS#1506: Download Authenticity check, key has expired, key ID differs from instructions 2020-02-10T20:00:30Z 2020-02-07T17:44:51Z

After download of iso, following verify instructions, https://wiki.hyperbola.info/doku.php?id=en:guide:verify_live_images ,

What was done:
$ gpg –keyserver pgp.mit.edu –recv-key “C92B AA71 3B8D 53D3 CAE6 3FC9 E697 4752 F970 4456” $ gpg –verify hyperbola-milky-way-v0.3-dual.iso.sha512.sig

Expected response:
file signature is ‘good’ and that it was signed with the following key: F9704456.

Actual response:
gpg: assuming signed data in ‘hyperbola-milky-way-v0.3-dual.iso.sha512’ gpg: Signature made Mon 23 Sep 2019 12:51:43 PM EDT
gpg: using RSA key C92BAA713B8D53D3CAE63FC9E6974752F9704456
gpg: Good signature from “AndrĂ© Silva emulatorman@hyperbola.info” [expired]
gpg: aka “AndrĂ© Silva emulatorman@riseup.net” [expired]
gpg: aka “[jpeg image of size 24564]” [expired]
gpg: Note: This key has expired!
Primary key fingerprint: C92B AA71 3B8D 53D3 CAE6 3FC9 E697 4752 F970 4456

ithink314 https://issues.hyperbola.info/:1506
FS#1373: installation successful, but buggy 2019-09-22T14:07:26Z 2019-04-21T21:36:24Z


This was the guide I followed, but there was one small issue:

The issue is attached within a picture. You will notice that a bunch of unneeded shortcuts are on my desktop right? well... I wondered how I can remove them. multiple filesystem root(s) and home(s) and boot(s)

but yeah, its extremely weird and messed up. a bit funny but troublesome and annoying.

Should I email the user who made that guide or leave it here? That’s what I am wondering.

winter https://issues.hyperbola.info/:1373
FS#1366: [ISO][UEFI] Replace Syslinux with rEFInd 2019-03-15T21:39:02Z 2019-03-12T22:18:45Z

Actual v0.2 ISOs use Syslinux UEFI Boot Manager for supporting EFI systems. However, I wanted to request its replacement by rEFInd, which is much, much better.

Here is why Syslinux should not be used, at least for more advanced tasks than just booting the OS:

  • UEFI Syslinux application syslinux.efi cannot be signed by sbsign (from sbsigntools) for UEFI Secure Boot. Bug report: [3]
  • Using TAB to edit kernel parameters in UEFI Syslinux menu might lead to garbaged display (text on top of one another). Bug report: [4]
  • UEFI Syslinux does not support chainloading other EFI applications like UEFI Shell or Memtest86+. Enhancement request: [5]
  • In some cases, UEFI Syslinux might not boot in some Virtual Machines like QEMU/OVMF or VirtualBox or some VMware products/versions and in some UEFI emulation environments like DUET. A Syslinux contributor has confirmed no such issues present on VMware Workstation 10.0.2 and Syslinux-6.02 or later. Bug reports: [6], [7] and [8]
  • Memdisk is not available for UEFI. Enhancement request: [9]

The citations are from the ArchWiki, check it out for more info.

From all of those points, I have confirmed the 3rd and 4th ones. These are a PITA, because EFI Shell is super useful (Parabola and Arch has it in its ISOs) and not being able to test it in VMs make it harded for ISO testers since they’ve to take more time on writing the image to the USB... etc.

rEFInd doesn’t have these issues, plus, it can be easily testes with QEMU. Try this:

  1. install ovmf package
  2. run the following, and specify the latest Milky Way ISO:
/bin/qemu-system-x86_64 -soundhw ac97 \
      -k es -machine accel=kvm -m 1024 \
      -boot once=d,menu=off -net nic -net user -rtc base=localtime \
      -bios /usr/share/ovmf/x64/OVMF_CODE.fd -cdrom /path/to/file.iso

You will see errors in the CLI. Now, try with my customized ISO (dir with ISO file, sign [key: 6DB9C4B4F0D8C0DC432CF6E4227CA7C556B2BA78], and sha512 checksum), the same steps as above. You’ll see that it successfully boots, and has UEFI Shell apps.

Here is my hyperiso fork. Take a look at the refind/* branches. The refind/with-uefi-shell has EFI Shell from Tianocore EDK2 latest stable tag, and refind/without-uefi-shell, well, doesn’t have it. Note that the binary files from refind/with-uefi-shell are downloaded from upstream and they’re sha512 checksumed. If for any reason you cannot do that way, there’s the other branch as an alternative.

P.S.: I see that actual configs have configured syslinux.efi to show other boot menus rather than the “Boot Hyperbola” option, but I tested it in my PC with UEFI enabled and it just showed the mentioned option

David P. https://issues.hyperbola.info/:1366
FS#183: UEFI boot not working 2018-01-07T09:53:21Z 2017-12-30T18:27:59Z

Booting from UEFI with a USB gives the message:

No configuration file found

0.2 and 0.2.1

J. Doe https://issues.hyperbola.info/:183