Fujitsu T937: Fails to boot live USB; Qubes 4.0.1

[0x...@tuta.io]

Hello,

Having downloaded the 64 bit Qubes 4.0.1 image (.iso) from the Qubes-os website, and thoroughly verifying its authenticity with SHA256sums and PGP keys, I decided to write it from an Arch linux system to a 64GB Samsung flash drive using the following command in an unprivileged terminal:

`sudo dd if=~/Downloads/Qubes-R4.0.1-86_64.iso of=/dev/sdb bs=1048576 status=progress && sync`

I also tried using a block size of 4M, on different occasions (but the same iso).

After writing, I have plugged the written flash drive into each of my two USB type A ports on this same laptop (both confirmed working properly). When attempting to boot the flash drive (in my case, repeatedly pressing f12, then selecting the drive in the boot menu), I get a black (but backlit) screen that does not change. No messages of any kind.

The following BIOS settings are current:

Secure boot: ENABLED

TPM(security chip): ENABLED

USB Ports: ENABLED

Legacy USB support: ENABLED

Multi-core: ENABLED

HT (hyper threading): ENABLED

Virtualization: ENABLED

VT-d: ENABLED

Trusted execution technology (TXT): DISABLED

Software guard extensions: software controlled

After changing the "Secure boot" setting to DISABLED, the live image appears to attempt startup. I see multiple lines of text scroll down the screen, no errors to be seen. They move quickly, but they appear the same as I've seen on my successful live boots in Virtualbox (on this same machine). After the text completes (in less than two seconds), the screen again changes to a 'bright black,' a step above no signal.

I know this system supports UEFI, as the current OS (Arch linux) is configured to make use of it (but, again, some security features are disabled because this laptop was shipped with Windows 10, which was happily removed in its entirety). What follows is some hardware information that I think is relevant:

Fujitsu Lifebook T937

BIOS version: 1.15 (02/20/18)

Intel i5-7360U @ 2.30 GHz [stock]

12288MB of DDR4 SDRAM (4GiB onboard) [stock]

This laptop is not fully supported in the HCL, however I have seen at least one post (that didn't solve my problem) by someone who has made this work. I cannot find the post at this time, but as I recall it was to the effect of "move a few files in the live image to unusual places and it worked for me," and I don't believe it was even the same problem as mine is.

I truly appreciate any help you're willing to provide. Thank you.

~0xor

[0x...@tuta.io]

This is the post I was referencing: https://groups.google.com/d/msg/qubes-users/X2AGqAJZ8Go/k5pruzBjBQAJ

Thanks!

Jun 30, 2019, 1:28 AM by 0x...@tuta.io:

[awokd]

0x...@tuta.io:
> This is the post I was referencing: https://groups.google.com/d/msg/qubes-users/X2AGqAJZ8Go/k5pruzBjBQAJ <https://groups.google.com/d/msg/qubes-users/X2AGqAJZ8Go/k5pruzBjBQAJ>

>
> Thanks!
>
> Jun 30, 2019, 1:28 AM by 0x...@tuta.io:
>

>> After changing the "Secure boot" setting to DISABLED, the live image appears to attempt startup. I see multiple lines of text scroll down the screen, no errors to be seen. They move quickly, but they appear the same as I've seen on my successful live boots in Virtualbox (on this same machine). After the text completes (in less than two seconds), the screen again changes to a 'bright black,' a step above no signal.

Yes, Secure boot needs to be Disabled. If you have an nvidia video card
and you can't disable it in UEFI config, you need to add
"nouveau.modeset=0" to your boot options per the ISO image procedure in
https://www.qubes-os.org/doc/uefi-troubleshooting/#change-installer-kernel-parameters-in-uefi.

[0x...@tuta.io]

Jul 1, 2019, 6:15 PM by qubes...@googlegroups.com:

--

Thank you for your response. I do not have an nvidia GPU in this laptop- it's integrated into the Intel CPU.

[awokd]

0x...@tuta.io:

You could also try
https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-getting-to-anaconda-qubes-40,
followed by the one after it. I would have expected that to be mentioned
in your referenced post, though.