Here's the stats on my situation:  I am at the intermediate tails install
portion, operating off of the first usb drive I've made.  I cannot get tails
to boot on either of 2 laptops.  Thank you for your help! J

 

Details

 

.         Tails version:  tails-i386-2.6

.         Verified by Firefox plugin

.         PC #1:  Brand/Model:  HP, Envy dv6 Notebook, AMD A10 Processor

.         When I try to start with Tails, it boots from the system.  When I
change the BIOS to boot from others, I see these two options:  EFI (usb2:)
or the System boot.  When I choose EFI, it gives me a list of options (file
structure on USB drive).  Most of the files are empty.  When I navigate and
find the submenu BOOT, and choose either the bootia32.efi or bootia64.efi
file, it says "no configuration file found" .  

.         I'm using a 16GB USB stick to install it from.

.         I used Universal USB installer to install it on the USB

.         I've never successfully installed it before (or attempted before).

.         When I enabled legacy mode, I saw this error when I chose the
bootia32.efi or bootia64.efi files.  A gray window popped up with  a DOS
prompt:  

 

WARNING:  No configuration file found

Boot: 

 

.         PC #2:  On a different laptop (ASUS), I set it up with EFI as
primary, and disabled fast boot.  I get this message:  

 

----------------------Secure Boot Violation------------------------

Invalid signature detected.  Check Secure Boot Policy in Setup.

 

I am wondering if the i386 file rendered/output everything correctly to the
USB?  

 

Is there a way for me to specifically point the boot process to the config
file?  Here's the tree for the usb:

 



 

I can show details of each folder if that's helpful.  I did find a
syslinux.cfg file in the uui folder.  Is that the config it's looking for?

 

Thank you very much.

 

DJ

_______________________________________________
tails-support mailing list
[email protected]
https://mailman.boum.org/listinfo/tails-support
To unsubscribe from this list, send an empty email to 
[email protected].

Reply via email to