#Installing Klipper on Beaglebone

1 messages · Page 1 of 1 (latest)

gloomy hinge
#

Hello, I need a lot of help and I don't even know if this is the right place to ask this

Long story short, I am not literate when it comes to this stuff, I have an old printer that I am trying to update to using Klipper that uses a Beaglebone Black but have been running into issue after issue getting it to actually work

I have been trying to follow this guide. I have tried using the latest image Debian 10.3 2020-04-06 4GB SD IoT and using the exact same image Debian 9.9 2019-08-03 4GB SD IoT. Both times when I type the first command:

./klipper/scripts/install-beaglebone.sh```
I get the Error
```E: Sub-process /usr/bin/dpkg returned an error code (1)```

Because I was having so many issues and a lot of people suggested to use KIAUH, following [their setup guide](https://github.com/th33xitus/kiauh), I could install the helper, but when I tried to get it to install Klipper it threw the same error. (I want to mention that one time I did get it to install Klipper, the SD card just ran out of space trying to install Moonraker, I am now using a larger SD card, but the same actions now throw this error)

Is there anyone with any knowhow or experience with Beagleboards or getting Klipper installed on them?
bold thunderBOT
#
AI Help

I'm sorry to hear that you're facing difficulties with installing Klipper on your Beaglebone Black. While I can't provide direct support for specific hardware or software setups, I can offer some general troubleshooting tips that might help you with your issue:

  1. Double-check your internet connectivity: Ensure that your Beaglebone Black is connected to the internet and can access the necessary resources to clone the repository and install the dependencies. You can verify this by attempting to access websites or perform other network-related tasks.

  2. Update package manager: Before attempting to install Klipper, make sure that your package manager is up to date. You can do this by running the command:

    sudo apt-get update
    
  3. Resolve package dependency issues: The error you're encountering (E: Sub-process /usr/bin/dpkg returned an error code (1)) typically indicates a problem with package dependencies. Try running the following command to fix any broken dependenc...

gloomy hinge
#

sudo apt-get update
didn't help anything

wet kernel
gloomy hinge
#

32GB

wet kernel
#

formatted to the right size?

#

just to clarify the sd card in the beaglebone thing right?

gloomy hinge
#

I used the raspberrypi imager to empty it, I’m new to all this so I don’t fully understand what to do

wet kernel
#

whats the output of df -k

gloomy hinge
#

I did this earlier

Filesystem     1K-blocks    Used Available Use% Mounted on
udev              219204       0    219204   0% /dev
tmpfs              49504    1576     47928   4% /run
/dev/mmcblk0p1   3558936 1902164   1456276  57% /
tmpfs             247512       0    247512   0% /dev/shm
tmpfs               5120       4      5116   1% /run/lock
tmpfs             247512       0    247512   0% /sys/fs/cgroup```
#

someone else was helping me elsewhere so now i am back to before i sent the commands that gave me the error

wet kernel
#

try the sudo apt-get update again and see if that errors out

bold thunderBOT
#
This post has been closed due to inactivity.

This post has been inactive for over 1 hour and so has been closed. To reopen this post simply send another message.

gloomy hinge
#

.

#

ok so right now im on a completely fresh bone-debian-10.3-iot-armhf-2020-04-06-4gb image

I just ran sudo apt-get update, this was the result:


We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for debian:
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://repos.rcn-ee.com/debian buster InRelease [3,078 B]
Get:3 http://deb.debian.org/debian buster-updates InRelease [56.6 kB]
Get:4 http://deb.debian.org/debian-security buster/updates InRelease [34.8 kB]
Get:5 http://repos.rcn-ee.com/debian buster/main armhf Packages [2,352 kB]
Get:6 http://deb.debian.org/debian buster/contrib armhf Packages [40.1 kB]
Get:7 http://deb.debian.org/debian buster/main armhf Packages [7,706 kB]
Get:8 http://deb.debian.org/debian buster/non-free armhf Packages [62.1 kB]                                     
Get:9 http://deb.debian.org/debian buster-updates/main armhf Packages [8,784 B]                                 
Get:10 http://deb.debian.org/debian-security buster/updates/non-free armhf Packages [3,812 B]                   
Get:11 http://deb.debian.org/debian-security buster/updates/main armhf Packages [513 kB]                        
Fetched 10.9 MB in 1min 15s (145 kB/s)                                                                          
Reading package lists... Done
gloomy hinge
# wet kernel whats the output of `df -k`

also I just redid df -k and got this, it looks the same mostly:

Filesystem     1K-blocks    Used Available Use% Mounted on
udev              219204       0    219204   0% /dev
tmpfs              49504    1580     47924   4% /run
/dev/mmcblk0p1   3558936 1980736   1377704  59% /
tmpfs             247512       0    247512   0% /dev/shm
tmpfs               5120       4      5116   1% /run/lock
tmpfs             247512       0    247512   0% /sys/fs/cgroup```
wet kernel
#

the df -k shows disk usage, your at 59% used

#

try running the guide from the start now, should be able to pull things in

gloomy hinge
wet kernel
#

do df-H, makes it easer to read

#

had to go and find the command

gloomy hinge
#

its running git clone https://github.com/Klipper3d/klipper right now but i will after its done

gloomy hinge
# wet kernel do df-H, makes it easer to read
Filesystem      Size  Used Avail Use% Mounted on
udev            225M     0  225M   0% /dev
tmpfs            51M  1.7M   50M   4% /run
/dev/mmcblk0p1  3.7G  2.4G  1.1G  70% /
tmpfs           254M     0  254M   0% /dev/shm
tmpfs           5.3M  4.1k  5.3M   1% /run/lock
tmpfs           254M     0  254M   0% /sys/fs/cgroup```
#

ok so its only seeing 3.7GB i think

wet kernel
#

yeah, i would reformat using windows then reflash it

gloomy hinge
#

im on mac so idk if that changes anything

#

so i should empty it and reformat it to what

#

ExFAT or MS-DOS (FAT)

wet kernel
#

i dont know how macs format but there should be an option

#

no FAT32?

gloomy hinge
#

oh, the raspberypi imager has an "erase (format card as FAT32)"

wet kernel
#

do that one then

gloomy hinge
#

ok

#

then image it?

wet kernel
#

yeah

gloomy hinge
#

ok

#

this is what i have been doing earlier, but maybe something changed

#

ok, it flashed, the board is booting up now

wet kernel
#

verify the size with df -H first thing

gloomy hinge
#
Filesystem      Size  Used Avail Use% Mounted on
udev            225M     0  225M   0% /dev
tmpfs            51M  1.7M   50M   4% /run
/dev/mmcblk0p1  3.7G  2.0G  1.5G  57% /
tmpfs           254M     0  254M   0% /dev/shm
tmpfs           5.3M  4.1k  5.3M   1% /run/lock
tmpfs           254M     0  254M   0% /sys/fs/cgroup```
wet kernel
#

was there an option to change the size in the pi imager?

gloomy hinge
#

not that i saw

#

is there an imager that you are more familiar with? Ive just been using the Pi one because that was the only one i knew

wet kernel
#

the pi is fine for imaging, just didnt know it had a formatter, try formatting through mac

#

should be an option to see the size

#

use FAT32 if its there exFAT if its not

gloomy hinge
#

This is what it looks like after erasing it

wet kernel
#

now use the imager and retry

gloomy hinge
#

its booting up now

#
Filesystem      Size  Used Avail Use% Mounted on
udev            225M     0  225M   0% /dev
tmpfs            51M  1.7M   50M   4% /run
/dev/mmcblk0p1  3.7G  2.0G  1.5G  57% /
tmpfs           254M     0  254M   0% /dev/shm
tmpfs           5.3M  4.1k  5.3M   1% /run/lock
tmpfs           254M     0  254M   0% /sys/fs/cgroup```
wet kernel
#

output of lsblk

#

my best guess is you dont have the partition mounted currently

gloomy hinge
#
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0      179:0    0 28.8G  0 disk
└─mmcblk0p1  179:1    0  3.5G  0 part /
mmcblk1      179:8    0  1.8G  0 disk
├─mmcblk1p1  179:9    0 70.6M  0 part
└─mmcblk1p2  179:10   0  1.7G  0 part
mmcblk1boot0 179:16   0    1M  1 disk
mmcblk1boot1 179:24   0    1M  1 disk```
wet kernel
#

well im right, though i dont know the process to mount

gloomy hinge
#

oof, ok

#

at least i know the name for what im looking for though

#

everything i can find right now refers to a uEnv.txt file that I can't find anywhere so ill do more digging later, thanks for your help though

#

?solved