Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ls: cannot access '/dev/serial/by-path': No such file or directory and ls: cannot access '/dev/usb-serial/by-id/': No such file or directory even after PR25246 applied #29201

Open
m3cinc opened this issue Sep 17, 2023 · 9 comments
Open

ls: cannot access '/dev/serial/by-path': No such file or directory and ls: cannot access '/dev/usb-serial/by-id/': No such file or directory even after PR25246 applied #29201

m3cinc opened this issue Sep 17, 2023 · 9 comments
Labels
bug 🐛 Programming errors, that need preferential fixing needs-reporter-feedback ❓ There's an unanswered question, the reporter needs to answer udev

Comments

@m3cinc
Copy link

m3cinc commented Sep 17, 2023 •
edited by yuwata

systemd version the issue has been seen with

252.5-2ubuntu3.1

Used distribution

Ubuntu 23.04 and Debian Linux 6.1.21-v7l+ #1642 SMP Mon Apr 3 17:22:30 BST 2023 armv7l

Linux kernel version used

6.1.21-v7l and 6.2.0-1012-raspi aarch64

CPU architectures issue was seen on

arm

Component

systemd, systemd-udevd, udevadm, udev rule files

Expected behaviour you didn't see

ls /dev/usb-serial/by-id/ should return a list of all USB Serialized
similarly,

ls /dev/serial/by-path

Unexpected behaviour you saw

ls: cannot access '/dev/usb-serial/by-id/': No such file or directory
and
ls: cannot access '/dev/serial/by-path': No such file or directory

Steps to reproduce the problem

install fresh images of the referenced id.
issue the command ls /dev/serial/by-id/ or ls /dev/serial/by-path/
will generate the No such filke or directory, due to the absence of symlinks...

Apply patch (PR #25246) to substitute 60-serial.rules in /usr/lib/udev/rules.d as follows:

sudo mv /usr/lib/udev/rules.d/60-serial.rules /usr/lib/udev/rules.d/60-serial.rules.bak
cd /usr/lib/udev/rules.d/
sudo wget https://raw.githubusercontent.com/yuwata/systemd/5286da064c97d2ac934cb301066aaa8605a3c8f9/rules.d/60-serial.rules
--2023-09-17 11:22:22-- https://raw.githubusercontent.com/yuwata/systemd/5286da064c97d2ac934cb301066aaa8605a3c8f9/rules.d/60-serial.rules
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8001::154, 2606:50c0:8002::154, 2606:50c0:8003::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8001::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1136 (1.1K) [text/plain]
Saving to: ‘60-serial.rules’

60-serial.rules.1 100%[===========================================>] 1.11K --.-KB/s in 0s

2023-09-17 11:22:22 (8.76 MB/s) - ‘60-serial.rules’ saved [1136/1136]
sudo udevadm control --reload-rules && sudo udevadm trigger
ls /dev/serial/by-id
ls: cannot access '/dev/serial/by-id': No such file or directory
ls /dev/serial/by-id/
ls: cannot access '/dev/serial/by-id/': No such file or directory

Reboot does not improve situation... and errors persist as symlinks are not established.

content of 60-serial.rules follows:

# do not edit this file, it will be overwritten on update

ACTION=="remove", GOTO="serial_end"
SUBSYSTEM!="tty", GOTO="serial_end"

SUBSYSTEMS=="usb", IMPORT{builtin}="usb_id", IMPORT{builtin}="hwdb --subsystem=usb"
SUBSYSTEMS=="pci", ENV{ID_BUS}=="", ENV{ID_BUS}="pci", \
  ENV{ID_VENDOR_ID}="$attr{vendor}", ENV{ID_MODEL_ID}="$attr{device}", \
  IMPORT{builtin}="hwdb --subsystem=pci"

# /dev/serial/by-path/, /dev/serial/by-id/ for USB devices
KERNEL!="ttyUSB[0-9]*|ttyACM[0-9]*", GOTO="serial_end"

SUBSYSTEMS=="usb-serial", ENV{.ID_PORT}="$attr{port_number}"

IMPORT{builtin}="path_id"
ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="", SYMLINK+="serial/by-path/$env{ID_PATH}"
ENV{ID_PATH}=="?*", ENV{.ID_PORT}=="?*", SYMLINK+="serial/by-path/$env{ID_PATH}-port$env{.ID_PORT}"

ENV{ID_BUS}=="", GOTO="serial_end"
ENV{ID_SERIAL}=="", GOTO="serial_end"
ENV{ID_USB_INTERFACE_NUM}=="", GOTO="serial_end"
ENV{.ID_PORT}=="", SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_USB_INTERFACE_NUM}"
ENV{.ID_PORT}=="?*", SYMLINK+="serial/by-id/$env{ID_BUS}-$env{ID_SERIAL}-if$env{ID_USB_INTERFACE_NUM}-port$env{.>

LABEL="serial_end"

Additional program output to the terminal or log subsystem illustrating the issue

udevadm info /dev/serial*
P: /devices/platform/soc/fe201000.serial/tty/ttyAMA0
M: ttyAMA0
R: 0
U: tty
D: c 204:64
N: ttyAMA0
L: 0
S: serial0
E: DEVPATH=/devices/platform/soc/fe201000.serial/tty/ttyAMA0
E: DEVNAME=/dev/ttyAMA0
E: MAJOR=204
E: MINOR=64
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=2734926
E: ID_MM_CANDIDATE=1
E: DEVLINKS=/dev/serial0
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

P: /devices/platform/serial8250/tty/ttyS0
M: ttyS0
R: 0
U: tty
D: c 4:64
N: ttyS0
L: 0
S: serial1
E: DEVPATH=/devices/platform/serial8250/tty/ttyS0
E: DEVNAME=/dev/ttyS0
E: MAJOR=4
E: MINOR=64
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=2740488
E: ID_MM_CANDIDATE=1
E: DEVLINKS=/dev/serial1
E: TAGS=:systemd:
E: CURRENT_TAGS=:systemd:

udevadm test /dev/serial*
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.

Trying to open "/etc/systemd/hwdb/hwdb.bin"...
Trying to open "/etc/udev/hwdb.bin"...
Trying to open "/usr/lib/systemd/hwdb/hwdb.bin"...
Trying to open "/lib/systemd/hwdb/hwdb.bin"...
Trying to open "/lib/udev/hwdb.bin"...
=== trie on-disk ===
tool version:          252
file size:        12212228 bytes
header size             80 bytes
strings            2479260 bytes
nodes              9732888 bytes
Loading kernel module index.
Failed to read $container of PID 1, ignoring: Permission denied
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Found container virtualization none.
Using default interface naming scheme 'v252'.
Parsed configuration file "/usr/lib/systemd/network/99-default.link"
Parsed configuration file "/usr/lib/systemd/network/73-usb-net-by-mac.link"
Parsed configuration file "/usr/lib/systemd/network/10-raspi-eth0.link"
Created link configuration context.
Reading rules file: /usr/lib/udev/rules.d/10-local-rpi.rules
Reading rules file: /usr/lib/udev/rules.d/39-usbmuxd.rules
Configuration file /etc/udev/rules.d/40-libsane.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Reading rules file: /etc/udev/rules.d/40-libsane.rules
/etc/udev/rules.d/40-libsane.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring
/etc/udev/rules.d/40-libsane.rules:26: The line takes no effect any more, dropping
Reading rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
Reading rules file: /usr/lib/udev/rules.d/40-usb_modeswitch.rules
Reading rules file: /usr/lib/udev/rules.d/40-vm-hotadd.rules
Reading rules file: /usr/lib/udev/rules.d/50-apport.rules
Reading rules file: /usr/lib/udev/rules.d/50-firmware.rules
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
Reading rules file: /usr/lib/udev/rules.d/55-dm.rules
Reading rules file: /usr/lib/udev/rules.d/56-dm-parts.rules
Reading rules file: /usr/lib/udev/rules.d/56-hpmud.rules
Reading rules file: /usr/lib/udev/rules.d/60-autosuspend.rules
Reading rules file: /usr/lib/udev/rules.d/60-avrdude.rules
Reading rules file: /usr/lib/udev/rules.d/60-block.rules
Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /usr/lib/udev/rules.d/60-dfu-util.rules
Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules
Reading rules file: /usr/lib/udev/rules.d/60-fido-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-input-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-inputattach.rules
Reading rules file: /usr/lib/udev/rules.d/60-libgphoto2-6.rules
Reading rules file: /usr/lib/udev/rules.d/60-libopenni2-0.rules
Reading rules file: /usr/lib/udev/rules.d/60-libsane1.rules
Reading rules file: /usr/lib/udev/rules.d/60-pcmcia.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-dm.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
Reading rules file: /usr/lib/udev/rules.d/60-sensor.rules
Reading rules file: /usr/lib/udev/rules.d/60-serial.rules
Reading rules file: /usr/lib/udev/rules.d/60-tpm-udev.rules
Reading rules file: /usr/lib/udev/rules.d/61-mate-settings-daemon-rfkill.rules
Reading rules file: /usr/lib/udev/rules.d/61-persistent-storage-android.rules
Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
Reading rules file: /usr/lib/udev/rules.d/64-xorg-xkb.rules
Reading rules file: /usr/lib/udev/rules.d/65-libwacom.rules
Reading rules file: /usr/lib/udev/rules.d/66-snapd-autoimport.rules
Reading rules file: /usr/lib/udev/rules.d/68-del-part-nodes.rules
Reading rules file: /usr/lib/udev/rules.d/69-cd-sensors.rules
Reading rules file: /usr/lib/udev/rules.d/69-libmtp.rules
Reading rules file: /usr/lib/udev/rules.d/69-wacom.rules
Reading rules file: /usr/lib/udev/rules.d/70-camera.rules
Reading rules file: /usr/lib/udev/rules.d/70-joystick.rules
Reading rules file: /usr/lib/udev/rules.d/70-memory.rules
Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules
Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules
Reading rules file: /usr/lib/udev/rules.d/70-printers.rules
Reading rules file: /etc/udev/rules.d/70-snap.chromium.rules
Reading rules file: /etc/udev/rules.d/70-snap.cups.rules
Reading rules file: /etc/udev/rules.d/70-snap.firefox.rules
Reading rules file: /etc/udev/rules.d/70-snap.snapd-desktop-integration.rules
Reading rules file: /etc/udev/rules.d/70-snap.snapd.rules
Reading rules file: /usr/lib/udev/rules.d/70-spice-vdagentd.rules
Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules
Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules
Reading rules file: /usr/lib/udev/rules.d/71-ipp-usb.rules
Reading rules file: /usr/lib/udev/rules.d/71-power-switch-proliant.rules
Reading rules file: /usr/lib/udev/rules.d/71-seat.rules
Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules
Reading rules file: /usr/lib/udev/rules.d/73-special-net-names.rules
Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules
Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-broadmobi-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-cinterion-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-dell-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-dlink-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-fibocom-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-foxconn-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-gosuncn-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-haier-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-linktop-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-mtk-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-qcom-soc.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-qdl-device-blacklist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-quectel-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-sierra.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-telit-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-tplink-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-ublox-port-types.rules
Reading rules file: /etc/udev/rules.d/77-mm-usb-device-blacklist.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/78-graphics-card.rules
Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules
Reading rules file: /usr/lib/udev/rules.d/80-debian-compat.rules
Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/80-ifupdown.rules
Reading rules file: /usr/lib/udev/rules.d/80-iio-sensor-proxy.rules
Reading rules file: /usr/lib/udev/rules.d/80-libinput-device-groups.rules
Reading rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules
Reading rules file: /usr/lib/udev/rules.d/80-net-setup-link.rules
Reading rules file: /usr/lib/udev/rules.d/80-udisks2.rules
Reading rules file: /usr/lib/udev/rules.d/81-net-dhcp.rules
Reading rules file: /usr/lib/udev/rules.d/84-nm-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/85-hdparm.rules
Reading rules file: /usr/lib/udev/rules.d/85-hplj10xx.rules
Reading rules file: /usr/lib/udev/rules.d/85-nm-unmanaged.rules
Reading rules file: /usr/lib/udev/rules.d/90-alsa-restore.rules
Reading rules file: /usr/lib/udev/rules.d/90-bolt.rules
Reading rules file: /usr/lib/udev/rules.d/90-console-setup.rules
Reading rules file: /usr/lib/udev/rules.d/90-fwupd-devices.rules
Reading rules file: /usr/lib/udev/rules.d/90-libgpod.rules
Reading rules file: /usr/lib/udev/rules.d/90-libinput-fuzz-override.rules
Reading rules file: /usr/lib/udev/rules.d/90-nm-thunderbolt.rules
Reading rules file: /usr/lib/udev/rules.d/90-pipewire-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/90-pulseaudio.rules
Reading rules file: /usr/lib/udev/rules.d/95-cd-devices.rules
Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
Reading rules file: /usr/lib/udev/rules.d/95-kpartx.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
Reading rules file: /usr/lib/udev/rules.d/96-e2scrub.rules
Reading rules file: /usr/lib/udev/rules.d/97-dmraid.rules
Reading rules file: /usr/lib/udev/rules.d/97-hid2hci.rules
Reading rules file: /etc/udev/rules.d/99-com.rules
/etc/udev/rules.d/99-com.rules:15 Invalid key/value pair, ignoring.
/etc/udev/rules.d/99-com.rules:16 Invalid key/value pair, ignoring.
/etc/udev/rules.d/99-com.rules:19 Invalid key/value pair, ignoring.
Reading rules file: /usr/lib/udev/rules.d/99-gpio.rules
Reading rules file: /usr/lib/udev/rules.d/99-libsane1.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
Configuration file /etc/udev/rules.d/S99-2000S1.rules is marked executable. Please remove executable permission bits. Proceeding anyway.
Reading rules file: /etc/udev/rules.d/S99-2000S1.rules
/etc/udev/rules.d/S99-2000S1.rules:26: GOTO="libsane_rules_end" has no matching label, ignoring
/etc/udev/rules.d/S99-2000S1.rules:26: The line takes no effect any more, dropping
Reading rules file: /etc/udev/rules.d/raspberrypi.rules
ttyAMA0: /usr/lib/udev/rules.d/50-udev-default.rules:29 GROUP 20
ttyAMA0: /etc/udev/rules.d/99-com.rules:30 Running PROGRAM '/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi''
ttyAMA0: Starting '/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi''
Successfully forked off '(spawn)' as PID 5538.
Skipping PR_SET_MM, as we don't have privileges.
ttyAMA0: '/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi''(out) '0'
ttyAMA0: Process '/bin/sh -c 'ALIASES=/proc/device-tree/aliases; if cmp -s $ALIASES/uart0 $ALIASES/serial0; then echo 0;elif cmp -s $ALIASES/uart0 $ALIASES/serial1; then echo 1; else exit 1; fi'' succeeded.
ttyAMA0: /etc/udev/rules.d/99-com.rules:30 LINK 'serial0'
ttyAMA0: Preserve permissions of /dev/ttyAMA0, uid=0, gid=20, mode=0660
ttyAMA0: Failed to lock stack directory '/run/udev/links/serial0': Permission denied
ttyAMA0: Failed to create/update device symlink '/dev/serial0', ignoring: Permission denied
ttyAMA0: Failed to create symlink '/dev/char/204:64' to '/dev/ttyAMA0': Permission denied
ttyAMA0: Failed to create device symlink '/dev/char/204:64': Permission denied
DEVPATH=/devices/platform/soc/fe201000.serial/tty/ttyAMA0
DEVNAME=/dev/ttyAMA0
MAJOR=204
MINOR=64
SUBSYSTEM=tty
ACTION=add
TAGS=:systemd:
ID_MM_CANDIDATE=1
DEVLINKS=/dev/serial0
CURRENT_TAGS=:systemd:
Unload kernel module index.
Unloaded link configuration context.

lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 002 Device 002: ID 2109:0817 VIA Labs, Inc. USB3.0 Hub             
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1d50:606f OpenMoko, Inc. Geschwister Schneider CAN adapter
Bus 001 Device 007: ID 0c45:7403 Microdia Foot Switch
Bus 001 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 005: ID 3151:3020 YICHIP Wireless Device
Bus 001 Device 003: ID 2109:2817 VIA Labs, Inc. USB2.0 Hub             
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The CAN adapter needs serialized address in klipper... not possible because of this bug...
@m3cinc m3cinc added the bug 🐛 Programming errors, that need preferential fixing label Sep 17, 2023
@yuwata yuwata removed the pid1 label Sep 17, 2023
@yuwata
Copy link
Member

yuwata commented Sep 17, 2023

Both devices /dev/ttyAMA0 and /dev/ttyS0 are not under the USB bus. Currently, the rule only provides /dev/serial/by-path/ or by-id/ symlinks only when the serial device is under the USB bus.

lsusb
Bus 001 Device 004: ID 1d50:606f OpenMoko, Inc. Geschwister Schneider CAN adapter
The CAN adapter needs serialized address in klipper... not possible because of this bug...

I am not familiar with the CAN device, but the CAN device seems neither /dev/ttyAMA0 nor /dev/ttyS0, as the CAN device is under the USB bus, but these tty devices are not.

Please provide corresponding results of udevadm commands for the CAN device. I guess you can find a symlink for the device under /sys/bus/usb/devices/:

$ udevadm info /sys/bus/usb/devices/USB_DEVICE
$ udevadm test /sys/bus/usb/devices/USB_DEVICE

@yuwata yuwata added the needs-reporter-feedback ❓ There's an unanswered question, the reporter needs to answer label Sep 17, 2023
@m3cinc
Copy link
Author

m3cinc commented Sep 17, 2023 via email •
edited by yuwata

@yuwata
Copy link
Member

yuwata commented Sep 17, 2023

@m3cinc I edited your reply, as it contains too many unrelated devices, and their layouts are broken. Also, the result of udevadm test is dropped, as the command does not support multiple devices, so only the first device is processed, and the processed device in the reply is completely unrelated.

The device that you are interested in is under /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4.

Please provide the results of the following commands (please do not use * or so. Type the command as is.):

udevadm info --tree /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4

The result should be large and decorated. Please do not paste the result in the reply, but attach as a file. Or, use gist or a pastebin service. Otherwise, the layout of the result should be broken again.

@m3cinc
Copy link
Author

m3cinc commented Sep 17, 2023 via email

@yuwata
Copy link
Member

yuwata commented Sep 17, 2023

@m3cinc Hm, it seems that GitHub dropped the attachment in your reply. Please provide it through the Web UI (or gist or so).

@m3cinc
Copy link
Author

m3cinc commented Sep 18, 2023 via email

@yuwata
Copy link
Member

yuwata commented Sep 18, 2023

Thanks. I cannot find anything spurious in the output. What do you expect?
Note, CAN device is a network device, not a serial. If you expect a symlink under /dev/serial/by-id or by-path to the CAN device, then that is simply not supported, as network devices do not have device nodes under /dev.

@m3cinc
Copy link
Author

m3cinc commented Sep 18, 2023 via email

@yuwata
Copy link
Member

yuwata commented Sep 18, 2023

Which device (device here means syspath) should have the expected symlinks ? Is the device really detected by the kernel ? If so, you can find it under /sys/bus/serial/devices. Please provide its syspath and output of udevadm info for the device.

At least, under /sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4, there is no serial device. If a serial device should exist under the syspath, then that's not a udev issue.

I guess some drivers or modules required for the device is not installed, and the kernel does not detect the device. But not sure.

That used to work in prior versions of systemd udev and simply does not anymore.

If this is really a udev bug, then please provide the result of udevadm info for the device with the working systemd version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug 🐛 Programming errors, that need preferential fixing needs-reporter-feedback ❓ There's an unanswered question, the reporter needs to answer udev
Milestone
No milestone
Development

No branches or pull requests
2 participants
@m3cinc @yuwata