Click to view our Accessibility Statement or contact us with accessibility-related questions
Showing 1 of 298 conversations about:
Mikhail.N
10
Dec 14, 2017
bookmark_border
@Michael_Grace I've received SDAC the last weekend and started using it with my Linux workstation. I've had an issue twice that after a long standby time I'm getting the following error showing up in the kernel log:
usb 1-1.3: 1:1: usb_set_interface failed (-32)
And there is no sound from SDAC anymore even after I replug it and restart PulseAudio. Only a full reboot helps, which isn't really great. I've never had this issue with ODAC rev. B on the same machine in the same OS configuration.
I'm using SDAC in 44 kHz / 24 bit stereo mode and my kernel is 4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Is it possible to investigate this problem somehow? I can provide any debugging info required.
Dec 14, 2017
datyeti
45
Dec 15, 2017
bookmark_border
Mikhail.NI just experienced a weird issue using win8.1. The dac sounded horrible compared to onboard. Tested all the cables and different amps. Had to reconnect the micro usb to the sdac and then it worked fine. I'm using 24 bit 48khz with windows properties since I don't have other playing software currently.
Dec 15, 2017
Michael_Grace
432
Grace Design
Dec 15, 2017
bookmark_border
Mikhail.NHi Mikhail, Sorry you are having trouble with the SDAC. Unfortunately it is pretty difficult for us to track down issues like this on Linux. While we have tested the SDAC on a Ubuntu 16 box here we have not seen this kind of behavior. However, our linux boxes here never go in to standby mode. As you know Linux distributions and hardware configurations can be very wide ranging. It sounds like your installation might have some kind of power management bug. The OS should always be able to re-set the usb device upon removing and reconnecting it. Ubuntu 14 is pretty old at this point, maybe try upgrading to 16 or 17? Good luck! Michael
Dec 15, 2017
Mikhail.N
10
Dec 16, 2017
bookmark_border
Michael_GraceThanks @Michael_Grace ! I understand, Linux is jungles. I've found some information that this problem may depend on whether USB 2.0 or 3.0 port on the host is being used, so I've switched to a USB 2.0 port for now to see if it helps.
As for upgrading—I can't do that easily, because it's a corporate environment where the entire company must use a particular distribution version for ease of maintenance.
Thanks for designing and releasing this DAC! (sorry I forgot to thank you at the very beginning :)
Dec 16, 2017
archiebunker
32
Dec 20, 2017
bookmark_border
Mikhail.NAny reason you haven't updated to 16.04? I have had no issues with my old Dragonfly v1.2 since switching to 16.04 but did have to do a little tweaking to get it working correctly. Perhaps updating to the latest LTS might solve the problem.
Dec 20, 2017
archiebunker
32
Dec 20, 2017
bookmark_border
archiebunkerOoops, didn't see your follow-up comment.
Dec 20, 2017
Mikhail.N
10
Dec 27, 2017
bookmark_border
Mikhail.NTo all who may encounter a similar problem—connecting SDAC via USB 2.0 powered hub seem to solve the problem. I had no issues for more than a week.
Dec 27, 2017
View Full Discussion
Related Products