Red Leader wrote:[...] Try it with sudo apt get. 'get' not a command. Try 'sudo apt get install'....'E: Unable to locate package update'. What am I doing wrong?
Understandable mistake. You were almost there! The command is "apt-get" (it's one word with a with a dash in it) instead of "apt get". I still make this mistake too sometimes.
...and it said their was a fatal error because snd-emu10k1 is already in use!
The Debian page to which I redirected you might be a little cryptic. Let me explain something first (took me a long time to figure this out in the beginning too). In Linux in the old days one has to execute certain "dangerous" commands as root. Root is the boss (or super user) of your computer: you are not. One switches user with the command su like so:
dave@frank:~$ su root
<<type in root's password>>
root@frank:/home/frank/#
Some Linuxers presume that everybody on earth knows that. So when they post an example from a command with a dollar sign ($) in front of it they assume that you know that you are supposed to execute said command as a regular user. When they post a command with a pound sign (#) in front of it they assume that you know that you are supposed to execute that command as root. If one simply types in "su" - without a username after it - then Linux assumes that you want to be the super user (i.e. root).
Debian still works this way but distro's like Ubuntu and Mint don't. They think that it is unsafe that you can become root. Therefore root does not have a password and you must execute commands as root with the command sudo (super user do). You then type in your own password.
Now why didn't your modprobe command work? If you look closely then you might notice that there is a pound sign in front of said commands: they must be executed as root. So I'd do:
The frist command removes the old diver (kernel module) the second inserts it again. That second command loads the driver for your sound card with the needed firmware that you've just compiled from source. I hope...
I forgot how one can check if the sound card actually works properly then. Probably by trying to play an MP3 or something...
Good luck! You're almost there.
@linuxmusician01,
Thanks for sticking with me on this one. I should either pay you to come over here or I can ship the box to you
I'll read through your post a few times and then get down there and give it a go again. The strange thing is that I did the command that the one Bill1959 posted but its like my computer just doesn't see the card.
Just for fun, here is my small/humble studio (with the offending hardware in the bottom center of the image!):
For what it's worth, I've already tracked one album from my band and I'm 95% of the way through the guitars on our second album when my AF4 kicked the bucket, which makes this a little more frustrating, since we're trying to wrap up the project.
I'll give things a go tonight and report back! Thank you again, you especially, and everyone else in this thread. Thank you for your patience for a 10+ year linux newbie!
Is it something you just have to explore around with? I don't want to break anything, but here is what happened when I tried to do the command with the new information for this code:
dave@frank:~$ sudo apt-get install build-essential
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
dpkg-dev fakeroot g++ g++-7 gcc gcc-7 libalgorithm-diff-perl
libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan4 libatomic1
libc-dev-bin libc6-dev libcilkrts5 libfakeroot libgcc-7-dev libitm1 liblsan0
libmpx2 libquadmath0 libstdc++-7-dev libtsan0 libubsan0 linux-libc-dev
manpages-dev
Suggested packages:
debian-keyring g++-multilib g++-7-multilib gcc-7-doc libstdc++6-7-dbg
gcc-multilib autoconf automake libtool flex bison gcc-doc gcc-7-multilib
gcc-7-locales libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg
libasan4-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg
libmpx2-dbg libquadmath0-dbg glibc-doc libstdc++-7-doc
The following NEW packages will be installed:
build-essential dpkg-dev fakeroot g++ g++-7 gcc gcc-7 libalgorithm-diff-perl
libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan4 libatomic1
libc-dev-bin libc6-dev libcilkrts5 libfakeroot libgcc-7-dev libitm1 liblsan0
libmpx2 libquadmath0 libstdc++-7-dev libtsan0 libubsan0 linux-libc-dev
manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 30 not upgraded.
Need to get 26.6 MB of archives.
After this operation, 117 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
I said 'no' because I wasn't sure if it was the same thing. But if it is...what gives? Why would typing it differently and without the whole structure work correctly? Still a little new to all this...
Last edited by Red Leader on Tue Apr 02, 2019 3:33 am, edited 1 time in total.
Sorry, I haven't been able to follow this thread as closely as I'd like..
A search of Filesystem--->lib--->firmware--->emu should tell you if you have the firmware installed, there should should be 6 files, if you have some sort of 'alsa-firmware' package installed you shouldn't need to build any firmware from source. I believe the KXStudio repos provide that package.
You do not have the required permissions to view the files attached to this post.
dave@frank:~$ sudo apt-get install build-essential
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
dpkg-dev fakeroot g++ g++-7 gcc gcc-7 libalgorithm-diff-perl
libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan4 libatomic1
libc-dev-bin libc6-dev libcilkrts5 libfakeroot libgcc-7-dev libitm1 liblsan0
libmpx2 libquadmath0 libstdc++-7-dev libtsan0 libubsan0 linux-libc-dev
manpages-dev
Suggested packages:
debian-keyring g++-multilib g++-7-multilib gcc-7-doc libstdc++6-7-dbg
gcc-multilib autoconf automake libtool flex bison gcc-doc gcc-7-multilib
gcc-7-locales libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg
libasan4-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg
libmpx2-dbg libquadmath0-dbg glibc-doc libstdc++-7-doc
The following NEW packages will be installed:
build-essential dpkg-dev fakeroot g++ g++-7 gcc gcc-7 libalgorithm-diff-perl
libalgorithm-diff-xs-perl libalgorithm-merge-perl libasan4 libatomic1
libc-dev-bin libc6-dev libcilkrts5 libfakeroot libgcc-7-dev libitm1 liblsan0
libmpx2 libquadmath0 libstdc++-7-dev libtsan0 libubsan0 linux-libc-dev
manpages-dev
0 upgraded, 26 newly installed, 0 to remove and 30 not upgraded.
Need to get 26.6 MB of archives.
After this operation, 117 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
I said 'no' because I wasn't sure if it was the same thing. But if it is...what gives? Why would typing it differently and without the whole structure work correctly? Still a little new to all this...
You should have said Yes.
(the correct command to install software on Ubuntu based systems indeed is "sudo apt-get install <<insert_software_name_here>>")
Sorry, I haven't been able to follow this thread as closely as I'd like..
A search of Filesystem--->lib--->firmware--->emu should tell you if you have the firmware installed, there should should be 6 files, if you have some sort of 'alsa-firmware' package installed you shouldn't need to build any firmware from source. I believe the KXStudio repos provide that package.
I just checked, and I have those files. They are under Home/alsa firmware 1.0.28/Emu
Does that folder need to be in a different location for the system to recognize them?
Also, in Cadence, it has an exclamation point around the kernal (4.18.0) as 'generic', and also says 'User in audio group: - no'
Not sure if this matters.
In Cadence, my only option for 'hardware/interface' is 'hw:PCH,0 [ALC887-VD Analog]' ....which sounds like the onboard sound controller on the mb, but I'm not sure...
Ardour still won't open. Just says 'could not create session'.
Red Leader wrote:Looks really generic to me, so I'm sensing 'no' on ALSA recognizing it?
You're right. ALSA is not recognising the card. JACK relies on ALSA, so Cadence won't list the card until ALSA recognises it.
ALSAJACKPyramid.png
lspci checked the bottom layer of the pyramid. Now we have to sort the ALSA layer by installing alsa-firmware. You could try using Synaptic for this or add the KX repositories. There are instructions at this link: https://kx.studio/Repositories.
You're getting warnings on Cadence because you started with a standard Ubuntu. Installing kxstudio-default-settings from the KX repos may fix this.
EDIT: I suggested going back to AV Linux, then thought that was adding to the confusion, and suggested kx-default-settings instead.
You do not have the required permissions to view the files attached to this post.
Last edited by merlyn on Tue Apr 09, 2019 2:07 pm, edited 2 times in total.
To reiterate what merlyn said and what I posted before if you're on Ubuntu you need to get the alsa-firmware package from the KXStudio repositories. For the record AV Linux has always had alsa-firmware pre-installed so I'm a bit puzzled why your emu doesn't work there.
As far as networking stuff there is no customization or difference from vanilla Debian with any of those system functions in AV Linux, it is not uncommon for Ubuntu to have drivers and hardware support that Debian doesn't have or that requires extra steps with Debian.
@Red Leader Trying the new 2019 version of AV Linux is an option. If you have another device with internet access you could use that to post what the problem is with networking. It may be quicker to sort the networking on AV Linux than sort the audio on your current Ubuntu setup.
