My bad, I thought it was the case but I mixed up the numbers. Please find enclosed the details you've asked for.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, April 19, 2019 1:47 AM, Felipe Sateler <fsate...@debian.org> wrote: > On Thu, Apr 18, 2019 at 5:32 PM Michael Biebl <bi...@debian.org> wrote: > >> Am 18.04.19 um 19:35 schrieb JB: >>> If it can help, it happened to other people, e.g. here with Arch : >>> https://bbs.archlinux.org/viewtopic.php?id=222301 >>> >> >> Felipe, with your PA hat on, can you take a look at this? > > PA simply reads information udev relays to it (ID_MODEL, ID_VENDOR, etc). > > Julien, can you post the output of: > > udevadm info -p /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.1/sound/card2 > > in both cases? > > From the pacmd output I see that the product id is not the same: 10e0 in the > correct case vs 9023 in the wrong case. These are picked from the ID_MODEL_ID > udev property. > >> To me this looks like a kernel/driver issue, but would welcome your >> input on this. > > IIUC, ID_MODEL_ID is originated in the kernel rather than udev, which would > make this a kernel bug. > > -- > > Saludos, > Felipe Sateler
udevadm_info_good_state
Description: Binary data
udevadm_info_bad_state
Description: Binary data
