Forum Post Draft — SPI‑XI Board Will Not Boot on First Power‑On

Sovol SV08 MAX
,
1

I’m a Kickstarter Backer, and I just unboxed my printer today. On first boot, the SPI‑XI board failed to start correctly and the printer has never completed a successful boot.

Symptoms

• Moonraker fails during startup
• KlipperScreen shows “Unable to get printer info”
• Immediate MCU connection errors
• NetworkManager auto‑creates a WiFi profile named ZYIPTest at every boot
• ZYIPTest always activates first, fails, then switches to my correct SSID (AURA_2G)
• By the time AURA_2G connects, the boot process has already failed

Important Hardware Detail

The CB1 compute module is integrated into the MCU board, so it cannot be removed or replaced separately.
I only removed the eMMC module to reflash the firmware.

Troubleshooting Already Done

• Full firmware reinstall using the official eMMC flashing adapter
• Verified the SPI‑XI OS image flashed correctly
• Split my router SSID into separate 2.4 GHz and 5 GHz networks
• Assigned the printer to the dedicated 2.4 GHz SSID
• Deleted all .nmconnection files (including ZYIPTest) multiple times
• Recreated AURA_2G as the only WiFi profile
• Cleared NetworkManager cache, state, and autoconnect history
• Checked /etc/rc.local and /boot/scripts/btt_init.sh (no WiFi provisioning logic)
• Verified fallback AP mode is not active
• Rebooted after each change
• ZYIPTest still reappears at boot even when no file exists for it

Specific Issue

The printer repeatedly recreates a WiFi profile named ZYIPTest at boot.
This profile does not exist on disk, but NetworkManager still generates it and tries it first.
This appears to cause Moonraker to fail before the correct WiFi connects.

What I’m Asking

  1. How do I get the SPI‑XI board to boot correctly?
  2. How do I stop ZYIPTest from being recreated at boot?
  3. If the board cannot be recovered, I need a replacement SPI‑XI board, since the CB1 is integrated and cannot be swapped independently.
2

@cardoc

So, you’ve had this printer for about a year & never set it up..??

3

You have a display attached to HDMI?

Moonraker should happily talk to KlipperScreen on 127.0.0.0 with no other network needed.

The “Unable to get printer info” message indicates the MCU isn’t communicating with the host (cm1)

Connect with SSH, launch KIAUH and see if it can locate your MCU.

This isn’t a official support channel. You need to email info@sovol3d.com. Include your order number and a picture of the serial number sticker.

4

The machine does not need a wifi network to boot, or print. Plug into the ethernet port, its always live, and configured as long as Linux booted..

The error message is likely due to not connecting to klipper firmware on something, not powered or not plugged in. It is very likely that Linux actually boots, the small factory screen at the bottom has its uses but is far from the best way to see what’s going on.

(strongly suggest a 5" or 7" HMDI touchscreen, ordered mine same time I ordered my MAX, both arrived same day, I have the BTT 7")

SSH in as sovol/sovol (user and password) might provide more info/tools.

What version of image do you have loaded? The current 2.09 image installs, then on first boot immediately prompts you to update to 2.19 OTA.