MCU _problem_ cannot access '/dev/by-id/'

General Discussion
1

Basic Information:

inter Model: Flying Bear 3D Printer Reborn 2

Screenshot (10)
Screenshot (10)1920Ă—1080 276 KB

Tried everything possible but the problem still exists

2

Screenshot (11)
Screenshot (11)1920Ă—1080 111 KB

Screenshot (12)
Screenshot (12)1920Ă—1080 132 KB

Screenshot (14)
Screenshot (14)1920Ă—1080 138 KB

3

Have you tried this?

BTW: Uploading text copies of outputs are way more better the screen copies :wink:

1 Like
4

In my case it’s Armbian.
Thank’s anyway :heart::heart:
​

1 Like
5

Armbian is either Ubuntu based or Debian based, depending on what you downloaded.

The dmesg output indicates that the board is not correctly recognized by the Linux operating system. While @EddyMI3D’s input can still be valid, this currently seems not the root cause.

Likely the board is not properly flashed.

  • Either wrong settings (I do not know which board is in this printer, since you did not provide any information)
  • Flash process went wrong
  • (Board is dead)
1 Like
6

In printer is Makerbase Nano6 v3.2 board

7

Not sure, MKS does not list this board, but it is likely based on a Nano v3.
Try

189987697-b000b8da-88fb-4ac4-a033-98176f45a511
189987697-b000b8da-88fb-4ac4-a033-98176f45a511961Ă—202 11.7 KB

and name the resulting bin file Robin_nano_6.bin flash via SD

8

That’s exactly what I did, but it didn’t change anything.

9

Sorry, no further idea.
The kernel of your Linux system is producing a hardware related error. It could also be some issues with your host:

  • Maybe try a different Armbian version
  • Try a different USB port on the host
  • Remove all other USB devices, if any
  • Different USB cable

On my Armbian, this error would mean:

klipper@bananapim5:~/klipper$ grep '62' /usr/include/asm-generic/errno.h
#define ETIME           62      /* Timer expired */
klipper@bananapim5:~/klipper$

Which has scientific value only as I have no idea what it means.

10

I tried 5 other USB cables
And 1 other OS issues

But the problem still exists

11

Here is a command that I found on the discord channel that fixes that problem. I’ve used it 3 times on 3 different printers and it works.

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

2 Likes
12

@Davtyan
Did that solve your problem?

1 Like
13

@hcet14 :

You have read that?

1 Like
14

I deleted and reinstalled everything but can’t seem to find the mcu: serial at this point.
There is no file or directory.
I have tried almost all possible options, I have read and familiarized myself with the contents of all the klipper files, but the problem was not solved.

15

I just asked Davtyan a question and I didn’t get an answer yet. Funny, that you asked me another one concerning my question.

Unsure, if I understand your question right!

“udev-fix.sh”? Yes.

Old, first thing I thought.

What’s this doing?

# Patch Funcs

patch_udev(){
    local udev_pkg_version
    udev_pkg_version="$(dpkg-query -s udev | grep "Version" | sed 's/Version\: //')"

    if [[ -n "${udev_pkg_version}" ]] && [[ "${udev_pkg_version}" =~ "deb11u2" ]]; then
        echo_red "'udev' version: ${udev_pkg_version}, is affected by bug ..."
        echo_green "Install patched udev rule from systemd git repository ..."
        curl -sSL "${UDEV_FIX_RAW_RULE_FILE}" > "${UDEV_FIX_TMP_FILE}"
        sudo cp "${UDEV_FIX_TMP_FILE}" "${UDEV_FIX_OUTPUT_FILE}"
        rm -f "${UDEV_FIX_TMP_FILE}"
    else
        echo_green "'udev' version: ${udev_pkg_version}, is NOT affected by bug ... [SKIPPED]"
    fi
16

Sorry, overseen that @ line

1 Like
17

Yes, I read it, but unfortunately only when I deleted everything and tried again.

18

Is that your printer mainboard?

https://it.aliexpress.com/item/1005005534811484.html?src=google&aff_fcid=e31eb792b8fc42fc87172475a59d239b-1692736516156-05696-UneMJZVf&aff_fsk=UneMJZVf&aff_platform=aaf&sk=UneMJZVf&aff_trace_key=e31eb792b8fc42fc87172475a59d239b-1692736516156-05696-UneMJZVf&terminal_id=f968300ba8744547ba223fb80126025c&afSmartRedirect=y&gatewayAdapt=glo2ita

19

No , mine is Makerbase Nano6 v3.2

It seems to me that I have stressed a lot about this issue and am already getting confused.
I’m sorry if I’m formulating my answers incorrectly, I think I’ll reformulate and present the question more clearly a little later. Anyway, thank you all for your help.

20

You’re welcome. Good idea, starting over. Make sure you provide good information about your setup (printer mainboard, printer, host (sbc, or something else).

Good luck, hcet1

1 Like