You're all good, man! Trying to get a feel on what you're doing, I think @Aravisian has the idea 
Make sure you're in the same directory as install.sh - in the terminal.
You can always open the containing directory, then right click blank space, Open in Terminal, and it'll open a terminal to the directory you're in through the file explorer! I use that one all the time, heh 
This thing is, what is being relayed in the terminal is the usage line in the script. 
usage()
{
cat <<EOF
Usage example:
sudo $0 [[v1.8.x/]v1.8]
EOF
exit 1
}
So, the script is running... and immediately exits at that point.
@LandscapingTrav
cd into the directory and please run:
bash -x ./install.sh arg1
and relay the output here...
liz@liz-Babytiger:~/Downloads/sof-bin-v2.2.6$ bash -x ./install.sh arg1
Try
sudo ./install.sh v2.2.6/v2.2
having a check through the install.sh in text editor it says this "# The "real" installation process belongs to sof/installer/ in the
is this what its referring to
liz@liz-Babytiger:~/Downloads/sof-bin-v2.2.6$ sudo ./install.sh v2.2.6/v2.2
./install.sh ERROR: v2.2.6/sof-v2.2 not found
Yes, it is.
You were on the right track above on this. When you matched the format.
But this script is written strangely.
Over-all it follows the logic and structure of the file tree. But the "usage Example" that we are getting hung up on is exactly its weakest point.
Because it is written to reject the rest of the process if you do not give it the exact arguments that it wants: But is unclear about what arguments that it wants.
So, this is not you being a poor learner.
Let's try the following, instead (the ln -s command creates a Symbolic link shortcut. THe following commands are what the Script is supposed to execute):
cd ~/Downloads/sof-bin-v2.2.6
rsync -a sof*v2.2 /lib/firmware/intel/
ln -s sof-v2.2 /lib/firmware/intel/sof
ln -s sof-tplg-v2.2 /lib/firmware/intel/sof-tplg
rsync tools-v2.2/* /usr/local/bin
liz@liz-Babytiger:~/Downloads/sof-bin-v2.2.6$ rsync -a sofv2.2 /lib/firmware/intel/
rsync: link_stat "/home/liz/Downloads/sof-bin-v2.2.6/sofv2.2" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1205) [sender=3.1.3]
Who would have thought getting sound would be so tedious.
Yeah, this is annoying...
Can you check if you have an Intel Directory in /lib/firmware? You should... but the output says something is missing...
i just checked the lib/firmware/interl to see if it actually existed and found it appears to already contain certain versions of the Sof-firmware
ill carry on from here and see how we go. Download fixed topology file:
run curl -LO https://mrchromebox.tech/files/misc/sof-apl-da7219.tplg.gz
Unzip topology file:
run gunzip sof-apl-da7219.tplg.gz
Copy topology file to required location:
run sudo cp sof-apl-da7219.tplg /lib/firmware/intel/sof-tplg/
Create driver config options file:
run sudo nano /etc/modprobe.d/inteldsp.conf
copy/paste in the following lines (right-click and select paste)
options snd-intel-dspcfg dsp_driver=3
options snd-sof-pci fw_path="intel/sof"
save and exit via CTRL+O, Enter, CTRL+X
reboot
It is worth trying. Not having the "latest" is actually often a boon. The "latest" packages are usually unstable.
ill give it a shot and perhaps we will get lucky!
Holy dooley we have sound! if you set it to say 2 out of 10 its far too loud but you can micro adjust the sound which im happy with, 100% just a first world problem but sound is sound! now i wont be getting grilled by the mother in law for her youtube not playing sound. Thank you for your time and help!
Im keen to keep learning about this system, as daunting as it seems i feel it still gives a whole load more freedom than windows or the chromeOS her chromebook came with. Just had a look at this permissions of the lib folder and youll see in the privileges to it it says im not the owner, im guessing that is what the sudo is for in terminal, essentially telling the computer you are the owner ive put in the password now let me change things?
I wonder if you can now adjust the sound levels to your needs using alsamixer
i.e. type alsamixer in terminal.
You can see that the file structure in GnuLinux is very much an organized tree - unlike Windows OS which is scattered and completely illogical.
We start with Root, which is the base level and the one directory that contains all directories.
When you are within this directory, you will always need Root Permissions or to be 'elevated to root privileges'.
SuperUserDO is sudo. Superuser means elevated privileges. DO means "do this."
Moving along all the branches of root, we see /opt, or /etc, or /lib but there is one Special Branch on the tree: /home
In that directory, lives the User Account. Opening /home will show folders that are named for each user. Often, there is just one user but there can be more if you set up multiple users.
Once you enter that username folder you are now under the permissions of That User and Their Ownership.
And when you enter your own /home/$USER directory, it is under your ownership.
Root Directory also has a home of its own since Root has ownership and that owner is the administrator (Whoever it is that has the root password). This directory in the root folder is simply called /root.
When in any Users Directory - Yours - Another Users - or Roots, you must use the password associated with that Users Privileges and ownership in order to make changes.
System-wide Settings and Software will be in Root - under /etc, /opt, or /usr
(e.g. /usr/share/applications)
User specific settings and software will be in their Home Directory, usually in /.local
(e.g. /.local/share/applications)as well as in /.config.
Whew, apologies - family blew through, fun times.. Got kinda busy entertaining and such.
Reading through all of it now, glad you got it going! That installer was, weird though.. mine came with a .deb to install. And couldn't find the dagg'on link to the V1.7.1 that I used.. it's just called 'custom-kernel-main' but has topology and ucm2 stuff. Also had to run some commands to 'activate' the sound; I guess? 
it worked though..
+1 @zabadabadoo - have to boost my 'Headphone' channel in alsamixer to get speaker levels up enough to hear something, for some reason - that affected the speaker volume. But, loud and clear now!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
