Hi,
I have a very annoying issue that I unable to find any solution yet and I want to give it a try here to get a solution or workaround.
I have an USB DAC Serenade iDSD device which makes 2 very loud popping sound on booting every time.
After booting it plays audio fine.
Is it this device?
If so is powered up before the computer starts?
Yes, this is it.
Powered up with the PC.
Totally silent during Windows boot.
lsusb:
Bus 003 Device 004: ID 22e1:f008 TEMPOTEC TempoTec HD USB AUDIO
Could be that the Linux driver is to blame but not sure. Can you boot up the PC and the DAC/Amp without the cable connected, wait until the computer is booted and only then connect the USB cable? Does that also give those popping sounds?
If so a work-around could be to boot with the USB not powered up, not sure how easy that is.
Connecting after boot makes those 2 loud popping sound either.
If it’s already connected while booting it’s more delay between the 2 sound.
Tried it in usb2, usb3 ports, with different cables, but nothing changed.
I got those messages in dmesg as I connected its USB cable to PC several times:
[ 65.171321] [ T87] usb 3-3: new high-speed USB device number 4 using xhci_hcd
[ 65.311473] [ T87] usb 3-3: config 1 interface 0 altsetting 0 endpoint 0x83 has an invalid bInterval 40, changing to 9
[ 65.311592] [ T87] usb 3-3: config 2 has an invalid interface number: 2 but max is 1
[ 65.311599] [ T87] usb 3-3: config 2 has 3 interfaces, different from the descriptor's value: 2
[ 65.311681] [ T87] usb 3-3: config 3 interface 0 altsetting 0 endpoint 0x82 has an invalid bInterval 40, changing to 9
[ 65.311843] [ T87] usb 3-3: New USB device found, idVendor=22e1, idProduct=f008, bcdDevice= 0.00
[ 65.311851] [ T87] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 65.311858] [ T87] usb 3-3: Product: TempoTec HD USB AUDIO
[ 65.311863] [ T87] usb 3-3: Manufacturer: TEMPOTEC
[ 65.311868] [ T87] usb 3-3: SerialNumber: 0007
[ 65.369411] [ T87] input: TEMPOTEC TempoTec HD USB AUDIO as /devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-3/3-3:1.0/0003:22E1:F008.0006/input/input13
[ 65.424831] [ T87] hid-generic 0003:22E1:F008.0006: input,hidraw5: USB HID v2.01 Device [TEMPOTEC TempoTec HD USB AUDIO] on usb-0000:24:00.3-3/input0
[ 65.480254] [ T2671] mc: Linux media interface: v0.10
[ 65.784869] [ T2671] usb 3-3: 2:4 : unsupported format bits 0x100000000
[ 65.979274] [ T2671] usbcore: registered new interface driver snd-usb-audio
[ 88.146820] [ T87] usb 3-3: USB disconnect, device number 4
[ 94.507671] [ T87] usb 3-3: new high-speed USB device number 5 using xhci_hcd
[ 94.647819] [ T87] usb 3-3: config 1 interface 0 altsetting 0 endpoint 0x83 has an invalid bInterval 40, changing to 9
[ 94.647934] [ T87] usb 3-3: config 2 has an invalid interface number: 2 but max is 1
[ 94.647942] [ T87] usb 3-3: config 2 has 3 interfaces, different from the descriptor's value: 2
[ 94.648024] [ T87] usb 3-3: config 3 interface 0 altsetting 0 endpoint 0x82 has an invalid bInterval 40, changing to 9
[ 94.648185] [ T87] usb 3-3: New USB device found, idVendor=22e1, idProduct=f008, bcdDevice= 0.00
[ 94.648194] [ T87] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 94.648201] [ T87] usb 3-3: Product: TempoTec HD USB AUDIO
[ 94.648207] [ T87] usb 3-3: Manufacturer: TEMPOTEC
[ 94.648213] [ T87] usb 3-3: SerialNumber: 0007
[ 94.713580] [ T87] input: TEMPOTEC TempoTec HD USB AUDIO as /devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-3/3-3:1.0/0003:22E1:F008.0007/input/input14
[ 94.767888] [ T87] hid-generic 0003:22E1:F008.0007: input,hidraw5: USB HID v2.01 Device [TEMPOTEC TempoTec HD USB AUDIO] on usb-0000:24:00.3-3/input0
[ 95.000813] [ T87] usb 3-3: 2:4 : unsupported format bits 0x100000000
[ 88.089692] [ T585] usb 3-3: new high-speed USB device number 4 using xhci_hcd
[ 88.229859] [ T585] usb 3-3: config 1 interface 0 altsetting 0 endpoint 0x83 has an invalid bInterval 40, changing to 9
[ 88.229979] [ T585] usb 3-3: config 2 has an invalid interface number: 2 but max is 1
[ 88.229987] [ T585] usb 3-3: config 2 has 3 interfaces, different from the descriptor's value: 2
[ 88.230070] [ T585] usb 3-3: config 3 interface 0 altsetting 0 endpoint 0x82 has an invalid bInterval 40, changing to 9
[ 88.230231] [ T585] usb 3-3: New USB device found, idVendor=22e1, idProduct=f008, bcdDevice= 0.00
[ 88.230240] [ T585] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 88.230247] [ T585] usb 3-3: Product: TempoTec HD USB AUDIO
[ 88.230253] [ T585] usb 3-3: Manufacturer: TEMPOTEC
[ 88.230259] [ T585] usb 3-3: SerialNumber: 0007
[ 88.281928] [ T585] input: TEMPOTEC TempoTec HD USB AUDIO as /devices/pci0000:00/0000:00:07.1/0000:24:00.3/usb3/3-3/3-3:1.0/0003:22E1:F008.0006/input/input13
[ 88.336586] [ T585] hid-generic 0003:22E1:F008.0006: input,hidraw5: USB HID v2.01 Device [TEMPOTEC TempoTec HD USB AUDIO] on usb-0000:24:00.3-3/input0
[ 88.397340] [ T2685] mc: Linux media interface: v0.10
[ 88.633286] [ T2685] usb 3-3: 2:4 : unsupported format bits 0x100000000
[ 88.730793] [ T2685] usbcore: registered new interface driver snd-usb-audio
As a workaround I can turn down volume while booting on device itself, but sometimes I forgot it etc., it not so comfortable, but annoying. Dual booting Linux with Windows.
Pretty sure this is not a OpenSUSE specific problem but more a Linux specific problem.
Just searching for “popping sound linux boot” on the Internet gives multiple relevant links with some work-arounds that as far as I understand disable sound at boot or set the volume to zero and only enable it later. Not sure if that would work for your situation and these instructions are typically outdated as they are not for pipewire.
I have a similar issue, but that has been distribution independent (a variety of Debian-based systems). The loud pop is from an externally powered, aux connected speaker in my case. I’ve never really come to a solution as for why this occurs.
Although I noticed this behavior is not consistent, so it could be software/audio driver related.
Confirm that, all of distributions are affected. It’s not related to volume. Already tried to mute it before restart. Already tried to find a solution, but found nothing just more owners with this same issue. Maybe it would be worth to report that issue on more relevant site but don’t know where.
Yeah, all of distributions are affected.
I always get those 2 annoying loud pop sound on every boot if I forget to turn down volume on the device itself.
In an ideal world you would ask Tempotec to solve the problem.
What you could done is trace USB while the device is being plugged in on Windows, trace the same on Linux and compare things. Making these logs is relatively easy, comparing not and fixing the problem problem in linux/drivers/pipewire is even harder.
I’ve always assumed, that this has to do with the audio driver initialized during boot. I noticed that the issue, at least for me, is not persistent. Occasionally it won’t occur for a while after an update, but is reintroduced with a later update.
To be honest, I wasn’t bothered enough to trace the issue. I could just monitor what was updated after it appears/disappears. I now try to just switch off the speakers after shutdown and only power on after the OS is done booting.
In an ideal world PC device manufacturers provides Linux support for their products or some information at least.
I had no any knowledge to investigate the issue further or how to start an usb protocol analyzing without any usb protocol debugging knowledge. Despite that I found wireshark which can read usb capture .pcap data files. I successfully captured usb messages under Windows and Linux (usbmon), but on Linux they are very weird and has a lot of other messages related to USBHUB protocol communication with additional messy messages…
- It starts with some USBHUB protocol GET_STATUS requests from PORT1 to PORT10
- some DESCRIPTOR Request via USB protocol
- an URB_INTERRUPT message again.
- After that in 3.9 sec, there is nothing happens.
- Then it rescan all PORTS again, but it founds connection on PORT 6.
- it does SET_FEATURE - PORT_RESET on PORT 6
- it does CLEAR_FEATURE - PORT_RESET on PORT 6
- it does it 2 times
- etc. some additional garbage messages
Maybe those host initiated PORT_RESET messages occurring the loud popping sounds.
In Windows I don’t see any of those messages above and the whole initialization process is complete in 0.13 sec without any “USBHUB” protocol transaction…
2 Likes
I hear those loud popping sounds even if I turn on or reconnect the USB DAC and the volume didn’t already turned down on the device itself. Maybe your issue is different and not on low (usb protocol) level.
Oh, our issues appear unrelated then. Best of luck resolving this!