# /dev/serial/by-id/': No such file or directory **URL:** \ **Category:** General Discussion\ **Created:** [January 15, 2025, 4:28am UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397 "2025-01-15T04:28:00Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [January 15, 2025, 4:28am UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/1 "2025-01-15T04:28:00Z")
### Basic Information: Printer Model: ender 5+ MCU / Printerboard: BTT SKR 3 EZ Host / SBC : Pi 4b+ klippy.log [klippy.log](https://klipper.discourse.group/uploads/short-url/4YJRSYzza1fvOp1RIF8DbL1AWVj.log) (64.3 KB) ![help1](https://global.discourse-cdn.com/free1/uploads/klipper/original/3X/f/4/f416a518f9372959d96ebeaa80958cae981590f7.jpeg) _Fill out above information and_ **_in all cases attach your_ `klippy.log` _file_** (use zip to compress it, if too big). _Pasting your_ `printer.cfg` _is **not** needed_ _ **Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there** _ ### Describe your issue: … ---
**Author:** ![flowerysong](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/flowerysong/32/10214_2.png) [@flowerysong](https://klipper.discourse.group/u/flowerysong)\ **Post date:** [January 15, 2025, 4:42am UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/2 "2025-01-15T04:42:26Z")
Neither command you’ve tried is what the documentation says to do. The first one is missing a space, the second one is missing `ls`. ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [January 15, 2025, 5:14am UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/3 "2025-01-15T05:14:46Z")
Curse you dyslexia! This is why I’m not a programmer X\_X I’ll give that a shot and see if it solves my problems edit - i tried > ls /dev/serial/by-id/\* from the klipper FAQ. still get the > ls /dev/serial/by-id/\* > ls: cannot access ‘/dev/serial/by-id/\*’: No such file or directory ---
**Author:** ![3dcoded](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/3dcoded/32/20297_2.png) [@3dcoded](https://klipper.discourse.group/u/3dcoded)\ **Post date:** [January 15, 2025, 12:32pm UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/4 "2025-01-15T12:32:09Z")
You might want to check out this potential fix: > [@Debian 11 (Bullseye) udev bug - No board or serial found](https://klipper.discourse.group/t/debian-11-bullseye-udev-bug-no-board-or-serial-found/10711): > > Background In recent updates, Debian Bullseye (Debian 11) introduced a [bug in udev](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035094) that causes the command ls /dev/serial/by-id/\* to fail, because the bug prevents the creation of this device path. As of writing this, the bug remains unfixed in the regular Debian repositories, but it is already fixed in optional Debian repositories. How to Diagnose To check if the OS is affected by the bug, run: sudo apt -y update && sudo apt -y upgrade apt-cache policy udev If the command’s output display… ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [January 15, 2025, 3:09pm UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/5 "2025-01-15T15:09:44Z")
The console messages and` ls /dev/serial/by-id/*` output is usually due to the board being not correctly recognized by the host process on the Pi 4b+. The typical reasons and solutions are listed here: [Issues flashing the printer board](https://klipper.discourse.group/t/issues-flashing-the-printer-board/14015) ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [January 16, 2025, 5:58am UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/6 "2025-01-16T05:58:50Z")
guys…i dont know if this matters, but i totally derped on the host. Its a Pi 3B+, not a 4b+… does that matter? I will try hooking up a different usb device and see if i can get that to recognize on that command. im assuming that if i get the same error, it might be my pi? ive reflashed the MCU a few times using the provided firmware, as well as my own compiled firmware. I can see on the SD card that it took the fimware.bin and its now fimware.cur, but neither seemed to do anything different. edit - i got my ADXL to connect to the pi! so it is indeed my firmware that must be bad on the MCU. I’ll try compiling a new one and report back. ---
**Author:** ![obsidianwraith](https://avatars.discourse-cdn.com/v4/letter/o/d78d45/32.png) [@obsidianwraith](https://klipper.discourse.group/u/obsidianwraith)\ **Post date:** [January 16, 2025, 6:54am UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/7 "2025-01-16T06:54:21Z")
guys, i figured it out! the PDF user manual the BTT provides tell you to configure for the WRONG PROCESSOR!!! BTT says to compile for the “STM32H743” but the board is actually “STM32H723” after compiling for the correct processor, it works!!! ---
**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\ **Post date:** [February 15, 2025, 4:55pm UTC](https://klipper.discourse.group/t/dev-serial-by-id-no-such-file-or-directory/21397/8 "2025-02-15T16:55:15Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.