# Ls /dev/serial/by-id/\* Is not being properly generated

**URL:** <https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383>\
**Category:** General Discussion\
**Created:** [July 27, 2025, 9:07pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383 "2025-07-27T21:07:05Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 27, 2025, 9:07pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/1 "2025-07-27T21:07:05Z")

</div>

### Basic Information:

Printer Model: Creality Ender 3  
 MCU / Printerboard: BTT Skr Mini E3 V3  
 Host / SBC: Raspberry pi 4 Model B  
 [klippy.log](https://klipper.discourse.group/uploads/short-url/7Zd7IPEprmDF6dSOukkW0Kg2NMd.log) (290.6 KB)

### Describe your issue:

I cannot seem to get the expected result from the following command to use in my printer.cfg file

```auto
jarchiepacheco@mainsailos:~/klipper $ ls /dev/serial/by-id/*
ls: cannot access '/dev/serial/by-id/*': No such file or directory
jarchiepacheco@mainsailos:~/klipper $

```

I am feeling reasonably confident that I have followed the instructions carefully but here are my settings in case there is something I am missing:

First this is the config I used for my firmware.

```auto
[*] Enable extra low-level configuration options
    Micro-controller Architecture (STMicroelectronics STM32) --->
    Processor model (STM32G0B1) --->
    Bootloader offset (8KiB bootloader) --->
    Clock Reference (8 MHz crystal) --->
    Communication interface (USB (on PA11/PA12)) --->
    USB ids --->
[] Optimize stepper code for 'step on both edges'
() GPIO pins to set at micro-controller startup

```

It seems to match the settings listed in the [BTT github](https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/tree/master/firmware/V3.0/Klipper).

Just to double check, I also took a look at my board and took a photo. It seems to match the information above. I can provide the photo if asked but I am unable to attach it to this post as a new user.

The other supporting evidence I have is the outputs lsusb and sudo dmesg  
which provides

```auto
jarchiepacheco@mainsailos:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
jarchiepacheco@mainsailos:~ $

```

and (pulling the information I think is relevant out)

```auto
[1.127933] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[1.266677] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[1.266713] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[1.266724] usb 1-1: Product: USB2.0 Hub
[1.268158] hub 1-1:1.0: USB hub found
[1.268456] hub 1-1:1.0: 4 ports detected
[1.523754] EXT4-fs (mmcblk0p2): mounted filesystem d4cc7d63-da78-48ad-9bdd-64ffbba449a8 ro with ordered data mode. Quota mode: none.
[1.556473] usb 1-1.2: new full-speed USB device number 3 using xhci_hcd
[1.653411] usb 1-1.2: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[1.653443] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1.653453] usb 1-1.2: Product: stm32g0b1xx
[1.653461] usb 1-1.2: Manufacturer: Klipper
[1.653468] usb 1-1.2: SerialNumber: 33002B0008504B5735313920
[1.945154] systemd[1]: System time before build time, advancing clock.
[2.039075] NET: Registered PF_INET6 protocol family
[2.039831] Segment Routing with IPv6

```

If this is not enough information, I have a full .txt file I can provide. I just couldn’t link it in this post as a new user.

At this point in time, I have reflashed the firmware to the board multiple times, even using the one provided by BTT with the same results. I know the error means that there is an issue with the USB connection or the firmware on the board but I don’t know where to proceed from here. I’ve tried following the help from multiple posts on this forum regarding this but I haven’t had any luck.

Any help would be greatly appreciated and if any more information is needed then I will provide that as soon as I can.

Thanks,

---

<div class="post-metadata">

**Author:** ![Polyneutron](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@Polyneutron](https://klipper.discourse.group/u/Polyneutron)\
**Post date:** [July 27, 2025, 9:32pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/2 "2025-07-27T21:32:50Z")

</div>

Okay from the lsusb: the address is: 1d50:614e. Now make menuconfig for you main board. once complete hit “q” to exit and then type make clean. While in dafu mode type make flash FLASH\_DEVICE=1d50:614e and press enter. Now once complete reset the main board or re-start the system and they open klipper and type: ls/dev/serial/by-id/\* and you will see your ID file.

---

<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:** [July 28, 2025, 5:47am UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/3 "2025-07-28T05:47:43Z")

</div>

> [@Polyneutron](#):
>
> ls/dev/serial/by-id/\*

There is no space after `ls`.

Note: For better readability, please always use `Preformatted Text` for code.

---

<div class="post-metadata">

**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:** [July 28, 2025, 6:10am UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/4 "2025-07-28T06:10:08Z")

</div>

The config and your `dmesg` snippet look good. According to it, your connection path should be:

```auto
/dev/serial/by-id/usb-Klipper_stm32g0b1xx_33002B0008504B5735313920-if00

```

It is surely strange that `ls /dev/serial/by-id/*` returns nothing. Please attach the full `dmesg` output.

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 28, 2025, 7:16pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/6 "2025-07-28T19:16:32Z")

</div>

[make flash output.txt](https://klipper.discourse.group/uploads/short-url/s5fFVSftfFDJjWz7iNoYjjK0Lfj.txt) (3.1 KB)

This is the output I get from those instructions. I may be incorrect because I don’t fully understand what your commands are having me do (I know it’s dumb to run commands without understanding what they do) but I think you’re trying to flash the control board over usb and I believe the BTT e3 can’t be flashed over usb. It needs to be flashed on an sd card.

If this is incorrect then I apologize but I gave it a try and the linked file is the output from it.

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 28, 2025, 7:25pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/7 "2025-07-28T19:25:44Z")

</div>

Here is that full log.

[dmesg.txt](https://klipper.discourse.group/uploads/short-url/utGMhGGivuruq9No5zIow1jSITT.txt) (35.2 KB)

---

<div class="post-metadata">

**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\
**Post date:** [July 28, 2025, 7:53pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/8 "2025-07-28T19:53:41Z")

</div>

Welcome jarchiepacheco,

> [@jarchiepacheco](#):
>
> I may be incorrect because I don’t fully understand what your commands are having me do (I know it’s dumb to run commands without understanding what they do) but I think you’re trying to flash the control board over usb

no.

Try

`[mcu]`  
`serial = /dev/serial/by-id/usb-Klipper_stm32g0b1xx_33002B0008504B5735313920-if00`

in your printer.cfg file.

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 28, 2025, 8:10pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/9 "2025-07-28T20:10:04Z")

</div>

I gave that a try and had no luck.

If it helps, I am attaching a copy of my printer.cfg file.

[printer.cfg](https://klipper.discourse.group/uploads/short-url/vqZYYcjDKKiWVMhdzt3DcetsYh8.cfg) (3.4 KB)

---

<div class="post-metadata">

**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:** [July 28, 2025, 8:42pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/10 "2025-07-28T20:42:02Z")

</div>

> [@jarchiepacheco](#):
>
> Here is that full log.

According to the `dmesg`, the board seems correctly flashed and registered. There are some messages that may indicate the `modemmanager` could be interfering.

Try the approach detailed here, but for `modemmanager` or use the automatic script solution: [BRLtty / ModemManager - Services Interfering with Klipper](https://klipper.discourse.group/t/brltty-modemmanager-services-interfering-with-klipper/10611)

- How did you install Klipper?
- If the above approach does not work, check the `dmesg` command to see which tty, e.g.

```auto

```

dc\_acm 1-1.3:1.0: ttyACM0: USB ACM device

````auto
the device registers and use this as an intermediate troubleshooting step, e.g.
```kcfg
[mcu]
serial = /dev/ttyACM0

````

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 28, 2025, 8:59pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/11 "2025-07-28T20:59:27Z")

</div>

This is the result of running the automatic script:

```auto
jarchiepacheco@mainsailos:~ $ curl -sf -L https://raw.githubusercontent.com/Sineos/useful_bits/main/Linux/disable_unwanted_services.sh | sudo bash
[sudo] password for jarchiepacheco:
Checking for root rights
                             [OK]
Checking if brltty is installed
                             [No brltty service(s) found.]
Checking if modemmanager is installed
                             [No modemmanager service(s) found.]

```

Unfortunately I forgot to take note of the first time I ran the command but it did tell me it masked the modemmanager stuff.

I am still receiving the same result from the ls /dev/… command. I also don’t fully understand what the rest of your reply is telling me to do but I installed klipper via the raspberry pi imager and selected the mainsailOS option. I haven’t had to do any manual installation of anything at this point beyond the firmware for the control board and configurations.

---

<div class="post-metadata">

**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\
**Post date:** [July 28, 2025, 9:02pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/12 "2025-07-28T21:02:16Z")

</div>

> [@jarchiepacheco](#):
>
> I gave that a try and had no luck.

> [@hcet14](#):
>
> Try
> 
> `[mcu]`  
> `serial = /dev/serial/by-id/usb-Klipper_stm32g0b1xx_33002B0008504B5735313920-if00`
> 
> in your printer.cfg file.

Sorry, I do that fault always (klippy.log vs printer.cfg) 😒

Please try

`serial: /dev/serial/by-id/usb-Klipper_stm32g0b1xx_33002B0008504B5735313920-if00`

---

<div class="post-metadata">

**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:** [July 28, 2025, 9:06pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/13 "2025-07-28T21:06:08Z")

</div>

- What Linux distribution?
- How was Klipper installed?
- provide the output `ps -axu` or `ps -axu > ps.txt`

> [@hcet14](#):
>
> Sorry, I do that fault always (klippy.log vs printer.cfg) 😒

You might profit from reading [Klipper’s printer.cfg - Syntax and Parsing Rules](https://klipper.discourse.group/t/klipper-s-printer-cfg-syntax-and-parsing-rules/23425)

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 28, 2025, 9:06pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/14 "2025-07-28T21:06:18Z")

</div>

Still no luck.

Here is the associated lines of my printer.cfg

```auto
[mcu]
serial: /dev/serial/by-id/usb-Klipper_stm32g0b1xx_33002B0008504B5735313920-if00
# serial: /dev/ttyAMA0
# restart_method: command

```

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 28, 2025, 9:09pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/15 "2025-07-28T21:09:59Z")

</div>

Here is that output:

[ps -axu output.txt](https://klipper.discourse.group/uploads/short-url/cQOWtIa5L9ah7ctsGZxQdmRh4W3.txt) (14.3 KB)

As far as I know, Klipper was installed as part of the mainsailOS package on the raspberry pi imager.

I think my linux distro is Debian.

Here is the output from a hostnamectl command

```auto
jarchiepacheco@mainsailos:~ $ hostnamectl
 Static hostname: mainsailos
       Icon name: computer
      Machine ID: 56cfa5597b4b4c5eb7872d35bbfc7582
         Boot ID: 746681bb77724c78b6f93333eff2bd94
Operating System: Debian GNU/Linux 12 (bookworm)
          Kernel: Linux 6.12.34+rpt-rpi-v8
    Architecture: arm64

```

---

<div class="post-metadata">

**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:** [July 29, 2025, 9:21am UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/16 "2025-07-29T09:21:07Z")

</div>

I can see nothing strikingly amiss.  
I’d propose to flash a new SD card with Raspberry Pi OS Lite and install your environment with KIAUH and try again.  
I’m not sure, but somehow have the feeling that it might be an issue on the Linux OS level.

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 29, 2025, 3:51pm UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/17 "2025-07-29T15:51:46Z")

</div>

Okay, that sounds good. I will give that a go later today after work and I will report back my results. I appreciate the help!

---

<div class="post-metadata">

**Author:** ![jarchiepacheco](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/jarchiepacheco/32/19960_2.png) [@jarchiepacheco](https://klipper.discourse.group/u/jarchiepacheco)\
**Post date:** [July 30, 2025, 2:57am UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/18 "2025-07-30T02:57:31Z")

</div>

Following your advice, everything went off without any issue. Thank you for the help, shame we couldn’t figure out the exact problem and solution. Anyways, thank you and happy printing!

---

<div class="post-metadata">

**Author:** ![Polyneutron](https://avatars.discourse-cdn.com/v4/letter/p/47e85d/32.png) [@Polyneutron](https://klipper.discourse.group/u/Polyneutron)\
**Post date:** [August 5, 2025, 12:23am UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/19 "2025-08-05T00:23:23Z")

</div>

Flashing through klipper will work. It doesn’t have to be written as a bin file and onto a micro sd… I have the Manta m8p and successfully flashed to obtain the serial ID. Although now I use can and uuid.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [September 4, 2025, 10:23am UTC](https://klipper.discourse.group/t/ls-dev-serial-by-id-is-not-being-properly-generated/24383/20 "2025-09-04T10:23:48Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.