You are not logged in.

#1 2018-07-10 01:34:10

uruz
Member
Registered: 2018-07-04
Posts: 9

DAC not detected (Schiit Modi)

I have installed Arch twice recently, with a similar result each time.  I use a Schiit Modi DAC, and it was not recognized on initial boot.  After rebooting, it was detected and functioned normally until:
- entering and leaving suspend mode
- shutting down and restarting
- rebooting

There is no crackling, and function is consistent until any of those events.  Then, it is a crapshoot:  more often than not, the DAC is not recognized (Modi does not appear in pavucontrol).  Other times, it is once again recognized, lasting until one of those events.

I don't think the DAC is malfunctioning.  It never had a problem with Windows 7 or 10, and it functioned pretty consistently with Linux Mint...being recognized a bit more frequently than with Arch.  I bought a new USB cable, but it didn't make a difference.

My tentative thought is that something happens (or doesn't happen) during one of those processes.

Is there a way to figure out what the problem is?  Is there any worthwhile system command to run and post to the forum?

Last edited by uruz (2018-07-10 02:37:43)

Offline

#2 2018-07-10 03:21:19

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

DAC is not recognized (Modi does not appear in pavucontrol)

That's not a reasonable way to determine the state of the device. For a start, check lsusb, dmesg and maybe "dmesg -w" (then re-plug it to see what's going on)
If there's nothing suspicious, get pulseaudio out of the equation and check the devices availability w/ only alsa (principally "aplay -l")

Usual suspects are USB autosuspend (esp. if you installed TLP or laptop-mode-tools or so) and pulseaudio.

Offline

#3 2018-07-11 03:56:17

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

I ran all those commands while the DAC wasn't working, then I re-ran them while the DAC was working.  I'll include the main differences below.

aplay -l with DAC working includes:

card 2: Device [USB Modi Device], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Because alsa also doesn't detect the device when it's not working, I assume the problem isn't pulseaudio.

lsusb with DAC working includes:

Bus 001 Device 009: ID 0d8c:1319 C-Media Electronics, Inc. 

dmesg with DAC working:

[    3.383501] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[    3.383670] snd_hda_intel 0000:01:00.1: Disabling MSI
[    3.383675] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[    3.850101] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[    3.850182] usb usb1-port10: attempt power cycle
[    4.084984] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input11
[    4.085181] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input12
[    4.085390] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input13
[    4.085558] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
[    4.517129] e1000e: enp0s31f6 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[    4.517136] e1000e 0000:00:1f.6 enp0s31f6: 10/100 speed: disabling TSO
[    4.517206] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
[    5.123435] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[    5.520075] usb 1-10: new high-speed USB device number 9 using xhci_hcd
[    5.544382] usb 1-10: New USB device found, idVendor=0d8c, idProduct=1319, bcdDevice= 1.05
[    5.544389] usb 1-10: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.544393] usb 1-10: Product: USB Modi Device
[    5.544397] usb 1-10: Manufacturer: Schiit Audio
[    5.550070] hid-generic 0003:0D8C:1319.0004: No inputs registered, leaving
[    5.550281] hid-generic 0003:0D8C:1319.0004: hidraw3: USB HID v1.00 Device [Schiit Audio USB Modi Device] on usb-0000:00:14.0-10/input2

dmesg with DAC not working:

[    2.736723] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[    2.810006] usb 1-5.3: new high-speed USB device number 6 using xhci_hcd
[    2.810176] IPv6: ADDRCONF(NETDEV_UP): enp0s31f6: link is not ready
[    2.901069] usb 1-5.3: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice= 9.01
[    2.901070] usb 1-5.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.901071] usb 1-5.3: Product: USB2.0 Hub
[    2.901911] hub 1-5.3:1.0: USB hub found
[    2.902172] hub 1-5.3:1.0: 4 ports detected
[    2.917244] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x200000, bo 0000000041502802
[    2.917337] fbcon: nouveaufb (fb0) is primary device
[    3.246607] Console: switching to colour frame buffer device 240x67
[    3.280808] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[    3.306823] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
[    3.306992] snd_hda_intel 0000:01:00.1: Disabling MSI
[    3.306997] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[    3.860093] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[    3.860176] usb usb1-port10: attempt power cycle
[    4.014973] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input11
[    4.015105] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input12
[    4.015225] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input13
[    4.015390] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
[    4.453799] e1000e: enp0s31f6 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
[    4.453806] e1000e 0000:00:1f.6 enp0s31f6: 10/100 speed: disabling TSO
[    4.453881] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
[    5.136770] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[    6.096763] usb usb1-port10: Cannot enable. Maybe the USB cable is bad?
[    6.096837] usb usb1-port10: unable to enumerate USB device

In both cases, there are lines about the USB cable and attempting power cycle.  Although I don't know for sure, I'll treat it as though autosuspend is the problem.  Based on another thread (https://bbs.archlinux.org/viewtopic.php … 7#p1175827), I edited /sys/bus/usb/devices/1-10/power/control/autosuspend to equal 0.  /sys/bus/usb/devices/usb1/power/autosuspend already equaled 0.

After one reboot, I once again have no sound.  And I no longer have that /sys/bus/usb/devices/1-10 directory, which I assume makes sense if the DAC wasn't enumerated..

If you think I'm wrong about autosuspend, or have any other recommendations, please let me know.

Offline

#4 2018-07-11 06:47:22

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

USB-autosuspend is a likely cause, https://bbs.archlinux.org/viewtopic.php?id=212593

However, edits to sysfs won't survive reboots.
1st off: Do you use some power management tools?
(Because then all attempts to disable usb autosuspend in the kernel are moot - they'll just re-enable it based on their internal config)

*Otherwise* see https://wiki.archlinux.org/index.php/Po … utosuspend ("usbcore.autosuspend=-1" will completely disable autosuspend).

Offline

#5 2018-07-12 04:12:12

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

Thanks for following up.

I don't use any power management tools.  I tried disabling autosuspend first by creating /etc/modprobe.d/usb-autosuspend.conf and adding

options usbcore autosuspend=-1

After rebooting, I saw no change other than that it takes noticeably longer to get to the Arch boot menu.

I then edited /etc/default/grub to include

GRUB_CMDLINE_LINUX_DEFAULT="quiet usbcore.autosuspend=-1"

Still no change.  I also still see an error about usb1-port10 at the login prompt.  It showed up before my recent changes, but I didn't mention it.

Now the question:  If this isn't related to a power management tool or to autosuspend, what should be the next test to run or step to try?

Offline

#6 2018-07-12 07:17:29

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

https://www.archlinux.org/packages/comm … odeswitch/

Did you btw. try (re-)plugging it after the system booted?

Offline

#7 2018-07-12 13:47:31

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

I didn't try replugging before, but I just did a few times.  Nothing changed initially, but after rebooting, the DAC was recognized and functioned.  This continued after suspend mode and after rebooting again, but stopped when I did a complete shutdown/boot.  Seemed promising at first.  I'll try more later to see if it's consistent.  Could autosuspend just be part of the problem?

I'll be away from this computer for a few days, but will also look into usb_modeswitch after this weekend and report back.

Offline

#8 2018-07-12 20:17:22

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

Sounds like a race condition between the booting device and the booting system.
The thory would be that when the port is initially scanned, the DAC is in an undefined state (or responds shit for other reasons).

When the device doesn't show up, try to re-bind the hub.
https://zedt.eu/tech/linux/restarting-u … em-centos/

*Warning*: unbinding the usb controller controlling your keyboard will leave you w/o input, so ensure to script the echos ahead,

echo -n "0000:00:xx.y" > unbind; sleep 5; echo -n "0000:00:xx.y" > bind

Offline

#9 2018-07-13 02:56:14

mr_dashi
Member
Registered: 2018-07-13
Posts: 1

Re: DAC not detected (Schiit Modi)

First post on the Arch forum. I hope I don't get banned.

It sounds like the DAC was kind of working in Mint but not 100%? What gen Modi is it? Have you tried another USB DAC to rule out possible USB issues in the Schiit vs your Arch build?

Anecdotally, I had a Schiit Gungnir with gen2 USB that worked perfectly in a decade-old W7 box. When I ditched Windows for Linux, it worked perfectly, for awhile, until it became flaky, exhibiting similar symptoms as you've described, until it stopped working all together with Linux. It still worked perfectly in Windows though. My dmesg output spat out "unable to enumerate" and "maybe the USB cable is bad?" as well. My trouble shooting ended after ruling out usb suspend.

I ended up sending the Gungnir back to Schiit and they verified that the USB board was in fact broken. I upgraded to a gen5 USB within warranty, and since have zero issues with playback, including my new Arch Xfce/i3 build with pulseaudio and MPD. 

If the resident Arch illuminati cannot help you solve your issue, I would send it back to Schiit.

Offline

#10 2018-07-16 04:02:05

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

seth,
Thanks again for your ongoing help.  I tried unbinding and rebinding the USB hub.  I don't have a /sys/bus/usb/drivers/ehci_hcd directory.  The closest I see in the parent directory is xhci_hcd, which I think is for USB 3, but maybe everything is put there.   In any case, I got errors of

bash: unbind: Permission denied
bash: bind: Permission denied

Adding sudo didn't make a difference.

In case I'm missing something, the full listing in /sys/bus/pci/drivers is:
8250_lpss
8250_mid
ahci
dw_dmac_pci
e1000e
i801_smbus
iosf_mbi_pci
mei_me
nouveau
nvme
pcieport
pci-stub
rtl8821ae
sdv_gpio
serial
shpchp
snd_hda_intel
xen-platform-pci
xhci_hcd

I'll look at usb_modeswitch tomorrow.

mr_dashi,
Interesting to see what you have to say.  Mine is a regular Modi, I assume 1st gen and out of warranty.  No, I don't have any other USB DACs to try, but trying a new one will be a backup plan.  The Gungnir is too pricey for me, so I'd try something more modest: Fulla or Modi2.  Bifrost is the first gen5 USB in my range.  It's an option, but I'll consider other things first.  Thanks your your input.

Last edited by uruz (2018-07-16 13:24:53)

Offline

#11 2018-07-16 06:51:31

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

"sudo echo foo > bar" doesn't work, because you leverage "echo", but the writing process is the shell (">")
The general sudo "trick" (ie. if you cannot run this from a root shell) is to invoke the T-Pipe "tee":

echo -n "0000:00:xx.y" | sudo tee unbind; sleep 5; echo -n "0000:00:xx.y"  | sudo tee bind

Offline

#12 2018-07-17 03:16:41

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

Okay, sudo is not just a way of saying "No, I really mean it.".

I ran the same command in the same directory again from root.  There was a pause and it went to a new prompt, then it produced:

hub 1-10:1.0: hub_ext_port_status failed (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: Cannot enable.  Maybe the USB cable is bad?
usb 1-10-port1: cannot disable (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: Cannot enable.  Maybe the USB cable is bad?
usb 1-10-port1: cannot disable (err = -71)
ses 6:0:0:1: Wrong diagnostic page; asked for 1 got 8
ses 6:0:0:1: Failed to get diagnostic page 0x1
ses 6:0:0:1: Failed to bind enclosure -19
sd 6:0:0:1: [sdc] No Caching mode page found
sd 6:0:0:1: [sdc] Assuming drive cache: write through
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: Cannot enable.  Maybe the USB cable is bad?
usb 1-10-port1: cannot disable (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: cannot reset (err = -71)
usb 1-10-port1: Cannot enable.  Maybe the USB cable is bad?
usb 1-10-port1: cannot disable (err = -71)
usb 1-10-port1: unable to enumerate USB device
usb 1-10-port1: cannot disable (err = -71)
hub 1-10:1.0: hub_ext_port_status failed (err = -71)
hub 1-10:1.0: hub_ext_port_status failed (err = -71)
hub 1-10:1.0: hub_ext_port_status failed (err = -71)
hub 1-10:1.0: hub_ext_port_status failed (err = -71)
hub 1-10:1.0: hub_ext_port_status failed (err = -71)
usb 1-10: Failed to suspend device, error = -71

If I understand it correctly, everything above is related to this command:

echo -n "0000:00:xx.y" > bind

I think usb 1-10  is the device in question.  If this really is about the USB cable, I'm not sure what to do about it.  I bought a new USB cable to see if it would help, because Schiit recommends a <2m non-audiophile cable.  The cables I see all have some extra selling point (ex: gold plated connectors, ferrite chokes), so I don't know if I'm avoiding audiophile cables or not.

I don't have much time tonight to get to usb_modeswitch, so I'll have to put it off another day.

Offline

#13 2018-07-18 03:11:42

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

I installed usb_modeswitch, enabled logging, rebooted, then unplugged and replugged the DAC.  It hasn't changed anything as far as I can tell, and there is no new log file in /var/log.  Frankly, I'm not sure if my DAC is a multimode device, but it was worth a shot.

If you (seth) or anyone can think of anything else to try, I'm all ears.  If not, I'll start looking to see if a different DAC is the answer.

Offline

#14 2018-07-18 11:33:56

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

Did you *literally* issue …xx.y… into the un/bind?
(That should not have worked, but I've actually never tried the reaction ;-)

Otherwise, what's /dev/sdc? Some external drive on the same port? Is the DAC maybe attached to an external HUB?

lsusb -t

(ideally w/ DAC working and failing)

Offline

#15 2018-07-18 13:59:25

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

Ha!  No, it was "0000:00:14:0".  Definite newbie here, but not that much.

/dev/sdc is an external hard drive on a different port.  I've alternated plugging the DAC directly vs. using an external powered HUB.  Here are the results of "lsusb -t".

Plugged directly:

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 10: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 10: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 480M
    |__ Port 10: Dev 7, If 2, Class=Human Interface Device, Driver=usbhid, 480M

Using an external HUB:

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
    |__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 10: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M

Also, I noticed that the boot sequence was much more rapid using the external HUB.  Recently, without using it, my computer has been stuck on the screen that gives the manufacturer name and options "F1 for boot menu, F2 for setup, etc" (boot menu screen?) for at least a minute before going on to a login screen and giving this warning:

usb usb1-port10: Cannot enable. Maybe the USB cable is bad?

I wish I could give you working vs. non-working.  If I get a lucky reboot, I'll share what I find.  But based on history, I expect it to become less frequent at this point.

Last edited by uruz (2018-07-18 14:01:44)

Offline

#16 2018-07-18 15:02:55

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

The DAC doesn't seem to show up in the "external HUB" tree (though it would have to be indented on the tail of that paste - did you just cut it off?)

The external drive seems on a a bus by itself while the DAC shares a bus w/ some input devices (mouse/keyboard, I assume?)

=> Try to flip that, ie. plug the DAC into the jack where the external drive currently is et vv. and in general, consequently skip the external hub (eleminating variables and additional points of failure)

Offline

#17 2018-07-19 03:05:37

uruz
Member
Registered: 2018-07-04
Posts: 9

Re: DAC not detected (Schiit Modi)

No, that was the whole output.  It just didn't appear at all.  Frankly, I was surprised it showed up in the first instance.

From what I understand, Bus 02 is for USB 3 devices.  Things show up there when they are USB 3 capable, plugged into a USB 3 port.

I tried several configurations, shutting down each time,  First, I swapped DAC with external HDD.  It worked.

DAC working, plugged into a USB 3 port (swapping with external hard drive):

Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 9: Dev 4, If 0, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 9: Dev 4, If 1, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 9: Dev 4, If 2, Class=Human Interface Device, Driver=usbhid, 480M
|__ Port 10: Dev 5, If 0, Class=Mass Storage, Driver=usb-storage, 480M

I rebooted, and it no longer worked.

DAC not working, plugged into a USB 3 port (swapping with external hard drive):

Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 10: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 480M

When I left everything as-is and tried plugging the DAC into ports in the front of the computer, they all looked like the above output.


Then I tried returning the External HDD to its regular USB 3 port, and swapped the DAC with the mouse.  It worked.

DAC working, plugged into another USB 2 port (swapping with mouse):

Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
|__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
|__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
|__ Port 2: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 480M
|__ Port 2: Dev 5, If 0, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 2: Dev 5, If 1, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 10: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M

Now, what I expect to happen after suspend or reboot, is for the DAC to stop working...just like it stopped working on the USB 3 port after reboot.  So, I'm keeping my computer on in case you have anything else you think I should run while everything seems to be working.

Last edited by uruz (2018-07-19 03:06:59)

Offline

#18 2018-07-19 21:17:28

seth
Member
Registered: 2012-09-03
Posts: 7,612

Re: DAC not detected (Schiit Modi)

Not really.

Does it make a difference whether you boot cold or warm?
Ie. did you eg. rather power off to swap the usb port and then launched a cold boot in contrast to warm (re)boots which loose the device?

Offline

Board footer

Powered by FluxBB