Hey,

I just received my APi but sadly it is not spitting out an HDMI signal. Serial says:

Version 2.18.1263. Copyright (C) 2018 American Megatrends, Inc.
Press <DEL> or <ESC> to enter setup.error: no suitable video mode found.
error: no suitable video mode found.
Booting in blind mode
[    2.406394] Couldn't get size: 0x800000000000000e
[    2.411678] MODSIGN: Couldn't get UEFI db list
[    2.416788] Couldn't get size: 0x800000000000000e
[    2.422189] Couldn't get size: 0x800000000000000e
[    2.874524] usb 1-3: string descriptor 0 read error: -22
[  OK  ] Started Show Plymouth Boot Screen.
plymouth-start.service
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Started AppArmor initialization.
apparmor.service
         Starting Raise network interfaces...
[  OK  ] Started Flush Journal to Persistent Storage.
systemd-journal-flush.service
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
systemd-tmpfiles-setup.service
         Starting Update UTMP about System Boot/Shutdown...
         Starting Network Time Synchronization...
         Starting Network Name Resolution...
         Starting RPC bind portmap service...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
systemd-update-utmp.service
[  OK  ] Started RPC bind portmap service.
rpcbind.service
[  OK  ] Reached target RPC Port Mapper.
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
systemd-resolved.service
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Initialization.
systemd-timesyncd.service
[  OK  ] Started ACPI Events Check.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
         Starting Docker Socket for the API.
[  OK  ] Listening on ACPID Listen Socket.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Started resolvconf-pull-resolved.path.
[  OK  ] Listening on CUPS Scheduler.
[FAILED] Failed to start Message of the Day.
See 'systemctl status motd-news.timer' for details.
         Starting Socket activation for snappy daemon.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Reached target Paths.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started Discard unused blocks once a week.
[  OK  ] Started Trigger anacron every hour.
networking.service
[  OK  ] Reached target Timers.
[  OK  ] Started Raise network interfaces.
[  OK  ] Listening on Docker Socket for the API.
[  OK  ] Listening on Socket activation for snappy daemon.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
[  OK  ] Started D-Bus System Message Bus.
dbus.service
         Starting Detect the available GPUs and deal with any system changes...
         Starting Accounts Service...
[  OK  ] Started Atomic Pi XMOS audio chip microphone select line holder.
atomicpi-hold-mic.service
[  OK  ] Started Set the CPU Frequency Scaling governor.
ondemand.service
         Starting System Logging Service...
         Starting WPA supplicant...
         Starting Configure EFI to boot the same device on next boot...
         Starting SPI GPIO-based custom bus configuration service...
         Starting Automatic root filesystem resizer...
         Starting Restore /etc/resolv.conf i…fore the ppp link was shut down...
         Starting LSB: IPv4 DHCP client with IPv4LL support...
[  OK  ] Started ACPI event daemon.
         Starting LSB: Start busybox udhcpd at boot time...
[acpid.service
  OK  ] Started CUPS Scheduler.
cups.service
         Starting Login Service...
         Starting Dispatcher daemon for systemd-networkd...
         Starting LSB: Bluetooth monitoring daemon...
[  OK  ] Started Regular background program processing daemon.
cron.service
         Starting resolvconf-pull-resolved.service...
         Starting LSB: automatic crash report generation...
         Starting Initialize hardware monitoring sensors...
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Modem Manager...
         Starting Network Manager...
[  OK  ] Started Atomic Pi XMOS audio chip reset line holder[    5.822296] intel_sst_acpi 808622A8:00: No matching machine driver found
.
atomicpi-hold-xmos.service
         Starting LSB: Record successful boot for GRUB...
         Starting Disk Manager...
         Starting I2C GPIO-based custom bus configuration service...
         Starting Snappy daemon...
[  OK  ] Started Run anacron jobs.
anacron.service
         Starting Save/Restore Sound Card State...
[  OK  ] Started System Logging Service.
rsyslog.service
[  OK  ] Started SPI GPIO-based custom bus configuration service.
spi-gpio-custom.service
[  OK  ] Started Restore /etc/resolv.conf if…before the ppp link was shut down.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Started resolvconf-pull-resolved.service.
[  OK  ] Started Configure EFI to boot the same device on next boot.
efi-keep-current-boot.service
[  OK  ] Started Detect the available GPUs and deal with any system changes.
[  OK  ] Started LSB: Start busybox udhcpd at boot time.
udhcpd.service
[  OK  ] Started LSB: Bluetooth monitoring daemon.
bluemon.service
[  OK  ] Started WPA supplicant.
wpa_supplicant.service
[  OK  ] Started Login Service.
systemd-logind.service
[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[  OK  ] Started LSB: automatic crash report generation.
apport.service
[  OK  ] Started Initialize hardware monitoring sensors.
lm-sensors.service
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
avahi-daemon.service
[  OK  ] Started Make remote CUPS printers available locally.
cups-browsed.service
i2c-gpio-custom.service
[  OK  ] Started I2C GPIO-based custom bus configuration service.
[  OK  ] Reached target Sound Card.
         Starting Authorization Manager...
[  OK  ] Started LSB: Record successful boot for GRUB.
grub-common.service
[  OK  ] Started LSB: IPv4 DHCP client with IPv4LL support.
dhcpcd.service
[  OK  ] Started Save/Restore Sound Card State.
alsa-restore.service
         Starting Load/Save RF Kill Switch Status...
[  OK  ] Started Automatic root filesystem resizer.
growroot.service
[  OK  ] Started Authorization Manager.
polkit.service
[  OK  ] Started Accounts Service.
accounts-daemon.service
[  OK  ] Started Modem Manager.
ModemManager.service
         Starting Hostname Service...
         Starting Bluetooth service...
[  OK  ] Started Load/Save RF Kill Switch Status.
systemd-rfkill.service
[  OK  ] Started Bluetooth service.
bluetooth.service
[  OK  ] Reached target Bluetooth.
[  OK  ] Started Disk Manager.
udisks2.service
[  OK  ] Started Hostname Service.
systemd-hostnamed.service
tmp-sanity\x2dmountpoint\x2d694792998.mount
NetworkManager.service
[  OK  ] Started Network Manager.
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
         Starting Permit User Sessions...
         Starting OpenBSD Secure Shell server...
         Starting containerd container runtime...
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Permit User Sessions.
systemd-user-sessions.service
         Starting Light Display Manager...
         Starting Hold until boot process finishes up...
[  OK  ] Started Snappy daemon.
snapd.service
containerd.service
[  OK  ] Started containerd container runtime.
         Starting Wait until snapd is fully seeded...
[  OK  ] Started Wait until snapd is fully seeded.
snapd.seeded.service
[  OK  ] Started Network Manager Script Dispatcher Service.
NetworkManager-dispatcher.service
[  OK  ] Started OpenBSD Secure Shell server.
ssh.service

Ubuntu 18.04.1 LTS localhost ttyS0


localhost login:

Is there hope for a solution?

EDIT: https://dlidirect.com/community/champ/forums/1778-atomic-pi-user-forum/topics/7797-system-not-booting-to-hdmi-monitor seems like the same problem.

EDIT2: Tried other monitor works with this one fine. Seems to be an incompatability between the equipment. See: https://dlidirect.com/community/champ/forums/1778-atomic-pi-user-forum/topics/7797-system-not-booting-to-hdmi-monitor