#Help with fresh install

161 messages · Page 1 of 1 (latest)

neon anvil
#

I just did a fresh re-install, and after installing Klipper, Moonraker, Fluid, and various add-ons (Beacon), I'm getting an error with numpy on restarting Klipper.

"Internal error during connect: cannot import name 'RankWarning' from 'numpy.exceptions' (/home/pi/klippy-env/lib/python3.9/site-packages/numpy/exceptions.py)"

Any ideas on how to fix this?

safe blaze
#

I'm not sure whether or not it's an answer ( it might be), but your fresh install...isn't. Python 3.9 is ancient

#

What on earth did you install?

neon anvil
neon anvil
neon anvil
safe blaze
#

install an UP TO DATE piOS, then use kiauh

#

there's no reason to hamstring yourself by starting from bullseye

neon anvil
safe blaze
#

( I guess I should say, that's assuming you're running an actual Pi. if its something else, then an appropriate OS for that. but go with the current version, regardless)

neon anvil
#

I'm installing bookworm now

safe blaze
#

I'm just reviewing the docs

#

the actual instruction (if its where I think you are) just says "Then select Raspberry Pi OS Lite (32bit)"

#

it doesn't actually specify a version

#

the screenshot does show a version, but that's just...the reality of being a screenshot, not that they're actually saying "use this version"

neon anvil
#

Read down toward the bottom

#

📋 Please see the Changelog for possible important changes!

Mainly tested on Raspberry Pi OS Lite (Debian 10 Buster / Debian 11 Bullseye)
Other Debian based distributions (like Ubuntu 20 to 22) likely work too
Reported to work on Armbian as well but not tested in detail

safe blaze
#

huh

#

you're right

#

well

neon anvil
#

No worries. I'll try the newer OS

safe blaze
#

I'm gonna go out on a limb and say they just haven't updated that 😛

#

I don't think they mean it

neon anvil
#

I was on buster prior to this, so...

#

boxturtle didn't like my old software

toxic tulip
neon anvil
neon anvil
safe blaze
neon anvil
#

oops

#

klipper.service - Klipper 3D Printer Firmware SV1
Loaded: loaded (/etc/systemd/system/klipper.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-07-06 07:59:06 BST; 8h ago
Docs: https://www.klipper3d.org/
Main PID: 620 (python)
Tasks: 2 (limit: 3916)
CPU: 8.731s
CGroup: /system.slice/klipper.service
└─620 /home/pi/klippy-env/bin/python /home/pi/klipper/klippy/klippy.py /home/pi/printer_data/config>

Jul 06 07:59:06 fluiddpi systemd[1]: Started klipper.service - Klipper 3D Printer Firmware SV1.

safe blaze
#

Hmm, doesn't quite have what I was looking for... my bad

#

Side bar, this is the modern install, just you named it fluiddpi, right?

#

How about journalctl -u klipper -r

neon anvil
#

what do you mean by modern versus fluiddpi?

#

@safe blaze

neon anvil
safe blaze
#

Well fluiddpi is an old mainsailos-like disk image that the fluidd folk used to make

#

Its long depreciated, and shouldn't be what you are using, in any way, shape, or form

#

Yet I see its name turn up here...

neon anvil
#

I see. That's what I chose 2 years ago and have stuck with it.

#

@safe blaze I'll switch once these errors are sorted out

safe blaze
#

No, you wont

neon anvil
#

@safe blaze Ah

safe blaze
#

Your issues are because you're using it

#

You need to do a fresh install of something actually fresh

neon anvil
#

Ok. I did what the message you quoted says to do. I used KIAUH to install Fluidd

safe blaze
#

But what disk image did you start from?

neon anvil
#

Hmm.

safe blaze
#

You cannot use an old fluiddpi image as your starting point (which is what it sounds like you did, but maybe I'm misunderstanding)

neon anvil
#

@safe blaze I started with the raspberry pi imager

safe blaze
#

Thats a piece of software (for writing disk images)

#

What image did you write with it

neon anvil
#

Once I had that image on the sdcard, I ran Kiauh and installed Klipper, Moonraker, and Fluidd from the Kiauh menu.

#

I essentially followed the instructions that EricZimmerman posted above

#

The only difference is his instruction say Mainsail while I chose Fluidd

#

And I chose 32 bit OS versus 64 bit

safe blaze
#

What os did you actually choose though

neon anvil
#

Raspberry Pi OS Lite (32-bit)

#

Bookworm

safe blaze
#

Then why is it called "fluiddpi"

#

Just because you typed that in as the host name?

neon anvil
#

Where did you see it?

safe blaze
neon anvil
#

oh, that's what my host used to be named, and so I specified that in the config when specifying the advanced config at the rpi os

safe blaze
neon anvil
#

Its just a name

safe blaze
neon anvil
#

Instead of voron24, I put in fluiddpi. got it

safe blaze
#

So moving on. Did you ever run that journalctl command?

neon anvil
#

journalctl -u klipper -r
Jul 06 07:59:06 fluiddpi systemd[1]: Started klipper.service - Klipper 3D Printer Firmware SV1.

#

One moment. In my klippy log, its showing an error on a beacon file

#

Unhandled exception during connect
Traceback (most recent call last):
File "/home/pi/klipper/klippy/klippy.py", line 130, in _connect
self._read_config()
File "/home/pi/klipper/klippy/klippy.py", line 123, in _read_config
self.load_object(config, section_config.get_name(), None)
File "/home/pi/klipper/klippy/klippy.py", line 103, in load_object
mod = importlib.import_module('extras.' + module_name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.11/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "<frozen importlib._bootstrap>", line 1206, in _gcd_import
File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 940, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "/home/pi/klipper/klippy/extras/beacon.py", line 21, in <module>
import numpy as np
ModuleNotFoundError: No module named 'numpy'

#

that's the source

safe blaze
#

That's...weird. like, numpy definitely should have been installed somewhere in the proceedings

neon anvil
#

I found this link on a klipper group page:
https://klipper.discourse.group/t/error-importing-numpy-after-beacon-install/21897

Klipper
Error importing Numpy after Beacon install

Basic Information: Printer Model: Voron 2.4 MCU / Printerboard: Octopus Host / SBC Rpi3 klippy.log klippy.zip (21.9 KB) Describe your issue: I am installing my first Beacon using the Quick Start guide on the website and everything seemed to install and update fine but when I when I restarted I get this Klipper error. I know nothing abou...

safe blaze
#

I guess do

sudo apt update
sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-dev
neon anvil
#

I followed that yesterday, and it started to throw the message I originally posted about yesterday. I can try it again.

safe blaze
#

Well yes, because you weren't on a modern platform yesterday

neon anvil
#

Here goes nothing. 🙂

#

@safe blaze That finished. I rebooted and there is no change. Puzzling

safe blaze
#

Output of the commands. Fresh logs...

neon anvil
#

From the beginning?

safe blaze
#

?

neon anvil
#

Do you mean show the log?

safe blaze
#

I mean do two things

#
  1. Show the output of when you ran those commands we just did
neon anvil
#

I see

safe blaze
#
  1. Post a newly downloaded klippy.log
neon anvil
#

That command generated a lot of log activity. I'll post here

safe blaze
#

Wtf. You're sure that was downloaded after running the other thing, and then rebooting?

neon anvil
#

sudo apt install python3-numpy python3-matplotlib libatlas-base-dev libopenblas-dev

#

yeah. it went nuts

safe blaze
#

Right, but then you rebooted the pi

#

And then you downloaded the klippy.log?

neon anvil
#

Oh, the klippy log has activity in there from the beginning of my install before I started to add my printer.cfg and other modules back.

#

How can I clear it?

safe blaze
#

That's not the question

#

I know how to read the the log

#

I'm asking you when it was downloaded

#

Aka, when the most recent info in it originates

neon anvil
#

I copied the file immediately before pasting it here

#

So I rebooted, saw the same error message, you asked for the log. I opened the klippy.log in my web admin, and copied/pasted to here.

safe blaze
#

Strange

neon anvil
#

The timestamp of the file shows it was from 17 minutes ago now

#

What's strange?

safe blaze
#

Could try ~/klippy-env/bin/pip3 install numpy I guess

neon anvil
#

pip3 isn't in that directory

#

I don't have a klipp-env directory

#

ah crap

#

one sec. my terminal got disconnected

#

🙂

#

pi@fluiddpi:~ $ ~/klippy-env/bin/pip3 install numpy
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting numpy
Using cached numpy-2.3.1-cp311-cp311-linux_armv7l.whl
Installing collected packages: numpy
Successfully installed numpy-2.3.1

#

Something is happening

#

@safe blaze No more numpy error. Now it can't find the mcu

#

should my usb device uuid's change after a reinstall?

safe blaze
#
  1. No
  2. What uuids? I don't see any canbus devices in your log?
#

Which device isn't it seeing?

neon anvil
#

I have a nitehawk36

#

I may have not installed a module for that

safe blaze
#

Nitehawk is usb though, not canbus

neon anvil
#

true

safe blaze
#

(So doesn't really need anything installed)

neon anvil
#

I mean usb device names

safe blaze
#

So once again, what exactly is the error?

neon anvil
safe blaze
#

mcu 'rpi': Unable to open port: [Errno 2] No such file or directory: '/tmp/klipper_host_mcu'

#

So yes, you missed installing something, but it's nothing to do with your nitehawk

#

Although, hold that thought

#

Just looking through your config

#

I don't see anything actually using that

#

Gimme a sec

#

Ya, you have the host mcu in your config, but it's just kinda
..there... its not being used

#

So I'd just comment out

[mcu rpi]
serial = /tmp/klipper_host_mcu
#

And call it good

neon anvil
#

Yeah, I only have 3 usb devices plugged into my pi

safe blaze
#

It's a software mcu

#

It has nothing to do with how many usb devices you have

toxic tulip
safe blaze
toxic tulip
#

Well used for the adxl back in the day. Not adxl per se.

#

Like shifting said comment it out

neon anvil
#

That did the trick

#

no errors

#

thanks guys!

#

That adxl may have been for a dedicated sensor I had a couple years ago

#

Never had an issue with it reporting an error before this upgrade though

safe blaze
#

Well you had the software installed before

neon anvil
safe blaze
#

You could have reinstalled it (my first solution) and it would have stopped complaining too

#

But then I noticed that there was a simpler way in your case

neon anvil
#

Anything I need to be aware of before changing the hostname?