search for: hashtool

Internet reports that I'm 1-of-many victims, failing to run linux on new/cheap laptops. Eg. quad-Atom; connex L1470. What is syslinux's recomended method to overcome <WinTel's UEFI lockout> using a USBbootStik ? Are wifi drivers: RTL8723BS for linux available yet ? ==TIA.

Hello everyone, I am trying to prepare a UEFI bootable thumb drive using syslinux and Linux foundations PreLoader.efi. I started the same as as it works with gummiboot-42: * Copy PRELOADER.EFI to EFI/BOOT/BOOTX64.EFI * Copy HASHTOOL.EFI to EFI/BOOT/BOOTX64.EFI * Copy gummibootx64.efi to EFI/BOOT/LOADER.EFI With just those files PreLoader asks to enroll gummiboot's hash. I do so and end up in gummiboot's menu. Copying the EFI64 syslinux.efi (from the 6.03-pre1 tarball) to EFI/BOOT/LOADER.EFI results in PreLoader c...

...g a USBbootStik ? Syslinux should work fine with UEFI (it does for me), and if for some reason you can't disable secure boot, download the Linux Foundation UEFI pre-loader (to use it, rename syslinux' bootx64.efi to loader.efi, rename Foundation's preloader.efi to bootx64.efi and place hashtool.efi in the same directory as bootx64.efi and loader.efi; the first time you boot, HashTool will be started, select Enroll hash and then loader.efi, then Exit, and Syslinux will start). -- < Jernej Simon?i? ><><><><>< https://eternallybored.org/ > Where there...

...gt; Syslinux should work fine with UEFI (it does for me), and if for some > reason you can't disable secure boot, download the Linux Foundation UEFI > pre-loader (to use it, rename syslinux' bootx64.efi to loader.efi, > rename Foundation's preloader.efi to bootx64.efi and place hashtool.efi > in the same directory as bootx64.efi and loader.efi; the first time you > boot, HashTool will be started, select Enroll hash and then loader.efi, > then Exit, and Syslinux will start). My guess is that we are talking about UEFI IA32, not UEFI X64. I would suggest trying with 6.0...

I have not looked into it all that much. But seems that UEFI basically allows booting without a bootloader. Here is some gentoo wiki info in it: http://wiki.gentoo.org/wiki/EFI_stub_kernel And Greg Kroah-Hartman talking about it a bit: http://kroah.com/log/blog/2013/09/02/booting-a-self-signed-linux-kernel/ I am looking forward to making a little HOWTO, for this subject and also for using

Am 22.01.2014 15:25, schrieb Dean Graff: > I have not looked into it all that much. But seems that UEFI basically > allows booting without a bootloader. It does. In fact I usually use preloader.efi (with keytool.efi and hashtool.efi for secure boot) and gummiboot.x64.efi to boot EFI stub kernels on x86_64. But until short time a go I had no idea someone would try to sell 32 bit UEFI on computers with 64 bit processors. > I am looking forward to making a little HOWTO, for this subject and also > for using `mkdiskim...

...34 AM, Mattias Schlenker wrote: > Hello everyone, > > I am trying to prepare a UEFI bootable thumb drive using syslinux and > Linux foundations PreLoader.efi. I started the same as as it works with > gummiboot-42: > > * Copy PRELOADER.EFI to EFI/BOOT/BOOTX64.EFI > * Copy HASHTOOL.EFI to EFI/BOOT/BOOTX64.EFI > * Copy gummibootx64.efi to EFI/BOOT/LOADER.EFI > > With just those files PreLoader asks to enroll gummiboot's hash. I do so > and end up in gummiboot's menu. > > Copying the EFI64 syslinux.efi (from the 6.03-pre1 tarball) to > EFI/BOOT/L...

...ootable media I currently use preloader+gummiboot while on BIOS media I use isolinux/extlinux. Since maintaining two configurations is some kind of extra work, I plan switching to syslinux in the next weeks or months. Creating an UEFI boot partition or El-Torito image seems easy: Use preloader, hashtool and the syslinux efi file, copy them to the FAT image and be happy. However I got two questions: 1. Do the 32 bit and 64 bit UEFI syslinux' both search for the same config or is there the possibility to use different config files? I might fiddle around with ifcpu64 but cannot yet, si...

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave