Mytek Stereo192 Not Connecting

[bigmo]

Hello!

Recent install of Snakeoil OS.  Pretty excited to have a Linux-based solution so I can get my old laptop off of the windows train.  However, my Mytek Stereo192 is not playing along.  Here are the details.

Mytek Stereo192 DAC, latest firmware that was available. 
Snakeoil 1.2.1
Ubuntu 20.04.3 LTS
Core2 Duo CPU, 4GB RAM (old school laptop)

I installed firmware from this thread: https://www.snakeoil-os.net/forums/Threa...ight=Mytek
Also tried the troubleshooting steps posted there as well, unfortunately to no avail.  

The Music Player page shows only the following two ALSA output devices:
STAC9228 ANALOG (HW:0,0)
STAC9228 DIGITAL(HW:0,1)

So the Mytek DAC is not showing up.  

Two things I am also seeing:
When I first added the Mytek tar and mytekusb2-generic.fw files nothing happened, so I logged directly into the machine and instantly got this message:
Checking for ALSA Mytek device
Inserting module
Failed to insert module snd_usb_mytek

I rebooted the machine (from the webapp) with the dac being turned off.  Once the app started I turned on the DAC and got these messages:
usb 6-1: device desriptor read/64, error -71
usb 6-1: device desriptor read/64, error -71
usb 6-1: device desriptor read/64, error -71
usb 6-1: device desriptor read/64, error -71
usb 6-1: device not accepting address 4, error -71
usb 6-1: device not accepting address 5, error -71
usb usb6-port1: unable to enumerate USB device

I've tried changing the Native DSD to DOP (as troubleshooting) with no change.  I'm guessing the snd_usb_mytek module is probably the root of the problem, but am unsure how to make it right.  I'm willing to poke around in Ubuntu if necessary.  I've also tried rebooting the app with the DAC powered up and that doesn't seem to change anything.  

Let me know if a diagnostics file is necessary.  Would be happy to send to agent_kith.  

Many thanks!

Big Mo

[agent_kith]

Hmm. It's been a while since I last looked at Mytec. The mytek firmware files might need updating.

You might need to extract the latest firmware from a Windows driver, and upload them to your Linux system. See here for details: https://github.com/lintweaker/mytekusb2/...r/FIRMWARE

I'll try and see if I can do this over the weekend if you have trouble with the above..

[bigmo]

Thanks for the quick reply.  I appreciate it.  I look forward to your findings.  

In the meantime I'll try the lintweaker suggestion and report back.  I didn't have a lot of luck with their solution over the weekend but was testing against an older version of Ubuntu and that was disaster.  

Thanks!

EDIT:  The latest Mytek drivers from their site are versioned 1.35.22 for USB Windows driver, and 4.3.147542 for the FW driver.

[bigmo]

OK, no luck.  I extracted the three files from the Windows USB driver zip copied them to the /lib/firmware/mytek directory.  I still see on the webapp that it shows IN USE: STAC9228 DIGITAL (HW:0,1) and does not show the Mytek at all.  Tried a few restarts and things look the same.  I do see a new zombie process is showing up in the messages at boot time...might be related?  

Will check in here regularly.  Let me know if there is data I can provide or if you need the diagnostics.  

Thank you!

[agent_kith]

OK, no luck.  I extracted the three files from the Windows USB driver zip copied them to the /lib/firmware/mytek directory.  I still see on the webapp that it shows IN USE: STAC9228 DIGITAL (HW:0,1) and does not show the Mytek at all.  Tried a few restarts and things look the same.  I do see a new zombie process is showing up in the messages at boot time...might be related?  

Will check in here regularly.  Let me know if there is data I can provide or if you need the diagnostics.  

Thank you!

With the latest firmware loaded. Generate a diagnostics file and send it over. Hopefully i can find something useful to troubleshoot.

Mytec192 is a pretty old DAC now, maybe worth considering to upgrade to a modern XMOS based DAC? I'm not too familiar with the SQ of the Mytec, if it's a high quality DAC. ALternatively, maybe it's worth it to try and get it going. You should be able to get Mytec up and running if you install the old Snakeoil 1.0.x, and follow the mytec thread to get things going.

[bigmo]

Will generate and send the file shortly.  

I agree that this DAC is getting old, but I have it as part of a very minimal system and am using it also as a preamp.  I personally think it is worth the effort to get it up and going 

Thanks for the homework assignment(s).  I'll generate diagnostics, uninstall current Snakeoil and attempt older version(s).  I'll never know until I try it.  Something is up and I plan on finding it.  

More soon.  Thanks!

[bigmo]

Quick question: as I rebuild my installation do I need to keep the files in /firmware/mytek as per the lintweaker setup?  I'm thinking I do not.  Thanks!

[bigmo]

So close.  

First tried 1.0.x and 1.1.x but was unable to get to the web interface when using either one.  The IP changed, of course, but even after retrieving the correct value from my router I still could not see the server.  Weird.  So I headed back to try 1.2.0.  I did not use the upgrade to 1.2.1 so as to eliminate any variables there.  At this point the server showed the previous usb errors, but the snakeoil logs showed something far better:

[Fri Nov  5 22:34:56 2021] usb 6-1: new full-speed USB device number 2 using uhci_hcd
[Fri Nov  5 22:34:56 2021] usb 6-1: device descriptor read/64, error -71
[Fri Nov  5 22:34:57 2021] usb 6-1: device descriptor read/64, error -71
[Fri Nov  5 22:34:57 2021] usb 6-1: new full-speed USB device number 3 using uhci_hcd
[Fri Nov  5 22:34:57 2021] usb 6-1: device descriptor read/64, error -71
[Fri Nov  5 22:34:57 2021] usb 6-1: device descriptor read/64, error -71
[Fri Nov  5 22:34:57 2021] usb usb6-port1: attempt power cycle
[Fri Nov  5 22:34:57 2021] usb usb6-port1: failed to disable port power
[Fri Nov  5 22:34:58 2021] usb 6-1: new full-speed USB device number 4 using uhci_hcd
[Fri Nov  5 22:34:58 2021] usb 6-1: device not accepting address 4, error -71
[Fri Nov  5 22:34:58 2021] usb 6-1: new full-speed USB device number 5 using uhci_hcd
[Fri Nov  5 22:34:59 2021] usb 6-1: device not accepting address 5, error -71
[Fri Nov  5 22:34:59 2021] usb usb6-port1: unable to enumerate USB device
[Fri Nov  5 22:35:02 2021] usb 2-3: new high-speed USB device number 3 using ehci-pci
[Fri Nov  5 22:35:02 2021] usb 2-3: New USB device found, idVendor=25ce, idProduct=000e, bcdDevice= 1.00
[Fri Nov  5 22:35:02 2021] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Fri Nov  5 22:35:02 2021] usb 2-3: Product: STEREO192-DSD DAC
[Fri Nov  5 22:35:02 2021] usb 2-3: Manufacturer: Mytek Digital
[Fri Nov  5 22:35:02 2021] usb 2-3: SerialNumber: 00000000000E0868

This is positive.

A few issues still persist:

• The DAC still displays 'no lock' status.  
  
• Mytek does not appear as an ALSA Output Device (should it???  I'm guessing yes)
  
• myMPD displays MPD disconnected for some reason (I'll look into this next)
  

I'll also try the mytekusb2loader-generic.fw just in case.

EDIT: Ran the loader:
./mytekusb2-firmware-loader.sh
Checking for ALSA Mytek device
aplay: device_list:274: no soundcards found...
Inserting module
Failed to insert module snd_usb_mytek

I'd be willing to drop this file in the right place myself, but imagine there might be some enumeration that goes along with it.  Almost feels like a permissions thing.  Will keep hacking.

[agent_kith]

Failed to insert module snd_usb_mytek[/font]

I'd be willing to drop this file in the right place myself, but imagine there might be some enumeration that goes along with it.  Almost feels like a permissions thing.  Will keep hacking.

Now that rings a bell!

You'll also need a special kernel. Go to this thread here, and download the kernel for mytek. Instructions for applying the kernel update is explained here. Before you do that, wait for my email.

[bigmo]

Power outage in my neighborhood yesterday, so no progress for me.  

Email received.  Thanks much, agent_kith!

Got the new kernel uploaded with no incident, but cannot get it to stay as the boot kernel for my system.  I know, I know: why on earth does this guy have so much trouble...

The Boot Kernel section does show two items in the dropdown: 5.4.0-89-generic or 4.4.9-rt17-amd64-ng-mytek.  I select mytek, of course, click Save and reboot but the 5.4.0-89-generic just keeps coming back.  I saw a segmentation fault after one reboot, but just once and have not had it again.  

I did notice that when I change the Boot Kernel and click save, the boot kernel changes back immediately before I can even reboot the OS.  Might be related.  

I am using version 1.2.0.  I suppose I could update to 1.2.1 but was just trying to keep my problems isolated before upgrading.  

As always, I'll keep chipping away at it.