# After update i cant connect

**URL:** <https://klipper.discourse.group/t/after-update-i-cant-connect/8957>\
**Category:** General Discussion\
**Created:** [June 13, 2023, 11:39am UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957 "2023-06-13T11:39:02Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\
**Post date:** [June 13, 2023, 11:39am UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/1 "2023-06-13T11:39:02Z")

</div>

### Basic Information:

Printer Model: vcore 3.1  
 MCU / Printerboardoctopus pro + Ebb42  
 `klippy.log`  
[klippy.log (6).txt](https://klipper.discourse.group/uploads/short-url/ex5JrHRd9cDLHafbzhGEMzyx057.txt) (5.4 MB)

_Fill out above information and_ **_in all cases attach your_ `klippy.log` _file_**. _Pasting your_ `printer.cfg` _is **not** needed_  
_**Be sure to check our [Knowledge Base](https://klipper.discourse.group/t/about-the-knowledge-base-category-table-of-contents/6228) and in particular [this](https://klipper.discourse.group/t/how-to-trouble-shoot/6326) and [this](https://klipper.discourse.group/t/how-to-ask-for-help/6327) post**_

### Describe your issue:

Hi,

This morning I made a short impression… And at the end I have updated, everything except the Octopus Pro, because it is the 429 and the Ebb42.

Well, after rebooting have come lis problems … Fluidd does not connect to the printer… I guess it will have to do with the update

I can read these error

> mcu ‘mcu’: Unable to connect  
> Once the underlying issue is corrected, use the  
> “FIRMWARE\_RESTART” command to reset the firmware, reload the  
> config, and restart the host software.  
> Error configuring printe

…

---

<div class="post-metadata">

**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\
**Post date:** [June 13, 2023, 11:56am UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/2 "2023-06-13T11:56:37Z")

</div>

There is a method for revert update?

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [June 13, 2023, 12:15pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/3 "2023-06-13T12:15:18Z")

</div>

> [@Peurif](#):
>
> everything

What is _everything_?

Have you checked that the serial is still valid:

```auto
[mcu]
baud = 250000
serial = /dev/serial/by-id/usb-Klipper_stm32f429xx_3A0039000D50304738313820-if00

```

Have you checked the USB connection?

---

<div class="post-metadata">

**Author:** ![Piezo](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/piezo/32/1110_2.png) [@Piezo](https://klipper.discourse.group/u/Piezo)\
**Post date:** [June 13, 2023, 12:25pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/4 "2023-06-13T12:25:39Z")

</div>

If your Pi OS is Debian Bullseye, you’re like affected by [this bug](https://klipper.discourse.group/t/debian-bullseye-bug-causing-klipper-to-no-longer-find-the-printer-board/8231/5).  
Follows the instruction on that topic and klipper should be able to connect after a reboot.

---

<div class="post-metadata">

**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\
**Post date:** [June 13, 2023, 12:55pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/5 "2023-06-13T12:55:12Z")

</div>

No… The lottery won’t touch me… but this.

I read few days ago and believed that it could be produced by updating klipper, and I have not updated klipper, if the rest…

When I get home I’ll try

---

<div class="post-metadata">

**Author:** ![bill\_w](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/bill_w/32/1427_2.png) [@bill\_w](https://klipper.discourse.group/u/bill_w)\
**Post date:** [June 13, 2023, 1:50pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/6 "2023-06-13T13:50:07Z")

</div>

Same thing happened to me yesterday. There were two problems. As someone else mentioned herein, the USB connection changed. The "serial = " statement had changed. The second problem probably affects only a few users. I have a BME280 hooked up to the PI on I2C 1. The RPI mcu would no longer load. I had to reload the RPI firmware with the make command and reflash.

Afterward, all was well.

---

<div class="post-metadata">

**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\
**Post date:** [June 13, 2023, 2:05pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/7 "2023-06-13T14:05:15Z")

</div>

i have checked, and that i am affected

the response of:

> pi@fluiddpi:~ $ apt-cache policy udev

is:

> pi@fluiddpi:~ $ apt-cache policy udev  
> udev:  
> Installed: 247.3-7+rpi1+deb11u2  
> Candidate: 247.3-7+rpi1+deb11u2  
> Version table:  
> 252.5-2~bpo11+1 100  
> 100 [Index of /debian](http://ftp.debian.org/debian) bullseye-backports/main armhf Packages  
> \*\*\* 247.3-7+rpi1+deb11u2 500  
> 500 [Index of /raspbian](http://raspbian.raspberrypi.org/raspbian) bullseye/main armhf Packages  
> 100 /var/lib/dpkg/status

---

<div class="post-metadata">

**Author:** ![Piezo](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/piezo/32/1110_2.png) [@Piezo](https://klipper.discourse.group/u/Piezo)\
**Post date:** [June 13, 2023, 2:10pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/8 "2023-06-13T14:10:52Z")

</div>

> [@Peurif](#):
>
> I read few days ago and believed that it could be produced by updating klipper, and I have not updated klipper, if the rest…

It’s the opposite actually: the bug comes with OS system package updates.

Mainsail crew made a onliner fix:

```auto
curl -sSL https://raw.githubusercontent.com/mainsail-crew/MainsailOS/develop/patches/udev-fix.sh | bash

```

---

<div class="post-metadata">

**Author:** ![Peurif](https://avatars.discourse-cdn.com/v4/letter/p/c57346/32.png) [@Peurif](https://klipper.discourse.group/u/Peurif)\
**Post date:** [June 13, 2023, 2:24pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/9 "2023-06-13T14:24:01Z")

</div>

> [@Piezo](#):
>
> `curl -sSL https://raw.githubusercontent.com/mainsail-crew/MainsailOS/develop/patches/udev-fix.sh | bash`

WORKS…

thanks… to all

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [May 5, 2024, 9:40pm UTC](https://klipper.discourse.group/t/after-update-i-cant-connect/8957/10 "2024-05-05T21:40:17Z")

</div>


