Linuxmusician01 wrote: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.Red Leader wrote:# modprobe -r snd-emu10k1-synth snd-emu10k1 ; modprobe snd-emu10k1
...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:Code: Select all
su root
And back to Dave with:Code: Select all
su dave
The "prompt" on the command line then changes from a dollar sign ($) to a pound sign (#). Looks something like this:Code: Select all
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:Code: Select all
sudo modprobe -r snd-emu10k1-synth snd-emu10k1
sudo modprobe snd-emu10k1
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!
