I managed to track this bug down to udev, but I am no expert when it comes to it, so I might be wrong. I also thought it could be the kernel when I saw the dmesg output but first I had to be sure it was not a udev issue.
At this point, I suspect it might even be a hardware issue (device which could be not respecting USB standards). Anyway, if you think udev can be ruled out of the list of packages which could be the source of the problem, so be it. But I would gladly try to troubleshoot this issue, and since I'm now stuck on udev level, I welcome any suggestion on how to expose the problem. Best, JB ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, April 18, 2019 9:45 AM, Michael Biebl <[email protected]> wrote: > Am 18.04.19 um 01:43 schrieb Jul': > > > Sorry for the lack of details. > > > > 1. how udev assigns this name? > > > > Since I have no custom udev rule, AFAIK, udev assigns it with the standards > > rules (in "/lib/udev/rules.d/60-persistent-alsa.rules" since it is a sound > > device). > > This rules file just creates a few symlinks in /dev/snd/by-id/ and > /dev/snd/by-path/ > > I don't see how that could influence your card being detected under > different names. > > The dmesg output you posted looks like those messages come directly from > the kernel. Maybe this is a kernel issue? > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? _______________________________________________ Pkg-systemd-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
