Unable to print after upgrade to v0.1.6 with no error message

[sneme1234]

dmesg.txt
klippy.log
serialqueue.c.txt

Printer: Neptune 4 pro
OpenNept4une: v0.1.6

I am able to completely control the printer through the Fluidd/Orca - I can move the toolhead/bed, heat toolhead/bed, load filament. Uploading a file to print causes the console to show the following:

09:50:13
$ SDCARD_PRINT_FILE FILENAME="small square_0.2mm_PLA_Elegoo Neptune 4 Pro_1m24s.gcode"
09:50:13
File opened:small square_0.2mm_PLA_Elegoo Neptune 4 Pro_1m24s.gcode Size:32837
09:50:13
File selected

I have let this sit for at least 20 minutes with no change. Eventually the console clears itself. No errors appear in the console or on the device tab. The only way to exit is restarting the Klipper service since the print has 'started'.

Unsure if this is related to issue #352 as I am unable to print anything post v0.1.6 upgrade.
Looking through Klipper issues, since I cannot print at all, seems like it might be related to this issue: MCU Comm Problem Klipper Infinite Start Up I pulled the serialqueue.c file from my printer and it looks like it has the problematic commits in it preventing me from getting to the issue detailed in #352. I am still new to rummaging around in this stuff so I apologize if this is nonsense.

I am planning to reflash the eMMC back to v0.1.5 to get back to printing now that I have saved all of the log files.

[halfmanbear]

I've recompiled the kernel and have posted another pre-release v0.1.7

https://github.com/OpenNeptune3D/OpenNept4une/releases/tag/v0.1.7

[jimmycr]

the same/similar problem - even with latest OpenNept4une update (v0.1.7-1).

Neptune 4 Plus with Cartographer, immediatelly after bed_mesh printer crashes :(

moonraker.log
klippy.log

[ringnutz]

Same here, going back to 1.5, luckily I backed up everything

[jimmycr]

Had to do the same, printer was "out-of-order" for 2 days, have no time :( . So I flashed my 0.1.5 backup, updated everything except OpenNept4une, deleted OpenNept4une section from moonraker.conf to be safe in Fluidd, made backup of whole home/mks folder.

My working setup (2. November 2025) :

[Atlas1O8]

@jimmycr Installing everything from scratch. Then flashing the eMMC and following the wiki step by step. Should you explain which steps to skip or omit and what to change to achieve your result?
Did you solve the layer shifting too?
I start cursing when I installed OpenNept4une!
I'm desperate since I updated from version 0.1.5 (more than 1 month) I can no longer print.😭

[sneme1234]

@Atlas1O8 @jimmycr i haven’t been able to print since I made this post. I have downgraded to 1.5 multiple times by freshly installing the v1.5 image and not updating opennept4une or klipper from v12 which was my last working config and still nothing. I can do everything in fluidd, control the printer/toolhead, scan with my eddy probe, everything but print. I also tried a fresh install of 1.7 and that didn’t work either. I am at a loss.

[jimmycr]

What printer, mate?

[Atlas1O8]

Neptune 4 MAX for me

[jimmycr]

ahh, sorry, have image for N4+ with nonstock steppers, cartographer, ..., so you should change a lot of things... :(

[Atlas1O8]

ahh, sorry, have image for N4+ with nonstock steppers, cartographer, ..., so you should change a lot of things... :(

Ok thanks, but the OpenNept4une image is not important.
The OpenNept4une 0.1.5 image is available online so no problem for that.
If you want to help us, just explain the procedure you followed. I'm interested in the Installation steps .

Example
Following the Wiki during installation sometimes asks to update everything, should you answer No?
1 What not to follow on the wiki to maintain version 0.1.5
2 In the file moonraker.conf Which line should I change?

Thanks, in case it works There is a paid coffee for you 😁

[jimmycr]

It's easy, I had working backup from November 2nd...so now I just ignore all updates for "Opennept4une" and "Display connector" in Fluidd... I can update anything else, but these two....

[halfmanbear]

Closing due to issue being caused by a klipper bug that was patched in December.