On Wed, Nov 12, 2025 at 10:50:49PM +0100, Alexandre Ratchov wrote: > On Wed, Nov 12, 2025 at 09:32:53PM +0000, Mikolaj Kucharski wrote: > > Hi. > > > > Long time ago, I had following flags for sndiod: > > > > rcctl set sndiod flags -f rsnd/0 -F rsnd/1 > > > > and from what I have in my notes I could use: > > > > sndioctl server.device=1 > > > > to switch between devices and also what I remember, I could just unplug > > USB-C head phones and audio would switch to built in audio device > > (azalia). > > > > I didn't use USB-C headphones for probably more than a year, maybe even > > two years. This week I wanted to use random USB headphones which I had > > at hand: > > > > uaudio0 at uhub1 port 5 configuration 1 interface 1 "Apple, Inc. EarPods" > > rev 2.01/26.81 addr 5 > > uaudio0: only one clock domain supported > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Basically, this device is not supported. Did it really work before?
Huh. You are right. I did not expect that, when device is attached to uadio(4) may still not be supported. I went over all my USB-C Apple EarPods, none of them work. I tested Google USB-C earbuds and they work: uaudio0 at uhub1 port 5 configuration 1 interface 1 "Google Pixel USB-C earbuds" rev 2.00/0.20 addr 5 uaudio0: class v1, full-speed, sync, channels: 2 play, 1 rec, 7 ctls audio1 at uaudio0 uhidev0 at uhub1 port 5 configuration 1 interface 3 "Google Pixel USB-C earbuds" rev 2.00/0.20 addr 5 uhidev0: iclass 3/0, 5 report ids ucc0 at uhidev0 reportid 1: 3 usages, 3 keys, enum wskbd1 at ucc0 mux 1 wskbd1: connecting to wsdisplay0 uhid0 at uhidev0 reportid 4: input=0, output=38, feature=0 uhid1 at uhidev0 reportid 5: input=34, output=0, feature=0 Comparing dmesg output between Google's and Apple's ear buds I missed that following line is missing in Apple's ear buds, right? audio1 at uaudio0 -- Regards, Mikolaj
