Debian 9.8 on Zotac PI-223

[Alburon]

Hey All,

I have a little experience with Linux, mostly Raspberry Pis, but this issue is unfortunately way over my head. I'm hoping to use this as a network probe / bandwidth monitor but it seems that some hardware on the device is preventing Debian from booting. It seems to hang right after it initializes the USB xHCI Controller so I've been focusing on that and have tried the following:

• - Removing all USB Devices
  - Disabling USB 3 in BIOS
  - Making it run as USB 2 with "lspci -nn | grep USB" & "setpci -H1 -d 8086:XXXX d0.l=0"
  - Turning off ahci in grub.cfg

System Information:

• - Zotac PI-223 https://www.zotac.com/us/product/mini_pcs/pi223
  • - Intel Atom x5-Z8350
    - 2GB DDR3L-RS1600 onboard memory
    - 32GB eMMC onboard storage
  - Debian 9.8 (debian-9.8.0-amd64-netinst.iso with 32-bit EFI)
  - Installed with just SSH and System Utils

Here is a picture of the boot screen, as I don't know where to grab boot logs from yet.
https://imagebin.ca/v/4as4zYzo0oKx

Greatly appreciate any help provided,
David

[Head_on_a_Stick]

The processor is 64-bit but it comes with a 32-bit Windows version, does the 32-bit Debian version boot on that device?

Debian stretch should support mixed-bitness UEFI systems but perhaps it just doesn't work with this device.

[Alburon]

I will try the 32-bit version again, it seemed to have the same issue, but I'll confirm.

[Alburon]

Tried i386 net install, but it does have the same issue booting.

[Bloom]

Does the UEFI setup menu have a 'Secure Boot' setting? If so, you must set this to 'disabled' or Debian will never be able to boot. Debian supports UEFI, but not Secure Boot (since that requires a digital signed key from... Microsoft!).

[Head_on_a_Stick]

Does the UEFI setup menu have a 'Secure Boot' setting?

The OP's photograph shows that systemd has started so that isn't the problem here.

Debian supports UEFI, but not Secure Boot

Debian 10 should support Secure Boot, they bought some keys from Microsoft

[Alburon]

Sorry thought I came back and posted the resolution to this but it looks like I didn't. Seems that installing the iwlwifi drivers corrected this issue.