-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Firmware 2128 not working with 2i2 4G #23
Comments
How strange! When it's in the not-working state, could you provide the output of |
sudo dmesg | grep -A 5 -B 5 -i scarlett [ 1.919549] usb 1-3.1: New USB device found, idVendor=05ac, idProduct=820a, bcdDevice= 1.00
|
state.Gen { |
I do have an /var/lib/alsa/asound.state. I tried moving it as you suggested - no change. |
Okay, that config you've got there will make things not work. I'm guessing that config is also in your This procedure should fix your issues: after making sure the FYI, this is the routing config you've got there, as shown by alsa-scarlett-gui: It should be looking more like this: (note DSP Inputs 1/2 and PCM Inputs 1/2 connected wrong in yours compared to what it should be) |
Thanks for the help. I reset the config and re-updated the firmware and it all works. The alsa gui is now also working and I have unplugged and replugged the 2i2 with nothing breaking. The /var/lib/alsa/asound.state file did not reappear. I also tested it on a different linux machine without changing anything on that machine, and it now works. I wish I could explain with certainty how I messed this up in the first place so others could be warned, but I am not sure. I had first attempted to update the firmware using the debian package, then later installed the scarlett2 utility. I would imagine I somehow messed it up in the debian attempt. The play-by-play on the eventual fix:
|
That's great news, thanks for reporting back! Watch out for that asound.state being created again if you shut your system down while the device is plugged in; whatever config is on the device then will again be restored every time you connect your interface. Masking the systemd alsa-state service should prevent this from happening. |
I upgraded a new fourth generation 2i2 to Firmware version 2128 using "scarlett2 update". Scarlett2 did not report any errors. The 2i2 unit lost the light-up volume indicator on input 1, and audacity showed no signal coming from either channel. I downgraded using "scarlett2 erase-firmware" and the unit regained functionality. The issue is repeatable: I can upgrade and lose functionality, then downgrade to restore functionality. I am running Ubuntu 24.04.1 LTS, kernel 6.8.0-45-generic. The upgraded 2i2 is also non-functional with Ubuntu 22.04.5 LTS. The problem seems to be with the firmware and not with the installer, because updating the firmware on the 2i2 using an Apple computer then returning the 2i2 to the linux computer results in the same behavior.
The text was updated successfully, but these errors were encountered: