"...entirely obvious... Secure Boot [was not] involved in any way at all."
It is not obvious to me. Please elucidate. Tony never booted from USB, but he was trying to boot from a Linux usbkey and/or cdrw. The guy who did get it working, using the normal shift-restart trick, but was not booting Linux -- he was booting the win7 installer (not sure if from dvd or usb).
Isn't the list of available boot-devices you see in option#2 dynamically generated? With secureBoot enabled in the firmware, wouldn't it reject any non-msft-digisig'd media as 'non-bootable'?
The folks that *did* manage to install Linux used the old-school approach (go into the bios and mess with settings... including disabling SecureBoot amongst others).
Re: SecureBoot setting, versus SecureBoot philosophy
It is not obvious to me. Please elucidate. Tony never booted from USB, but he was trying to boot from a Linux usbkey and/or cdrw. The guy who did get it working, using the normal shift-restart trick, but was not booting Linux -- he was booting the win7 installer (not sure if from dvd or usb).
Isn't the list of available boot-devices you see in option#2 dynamically generated? With secureBoot enabled in the firmware, wouldn't it reject any non-msft-digisig'd media as 'non-bootable'?
The folks that *did* manage to install Linux used the old-school approach (go into the bios and mess with settings... including disabling SecureBoot amongst others).