Tinkering with Asus Tinker Board 2S

Manavendra you explained the situation that I was reading in bits and pieces on the net clearly.

At work now . once back home and ran the errands for the day, i will run the command you sent and post the result.

New to SBCs and learnt that it's not like Win and in a hard way.

TB (S) of 2017 has Debian 10 V3 while TB 2 (S) of 2020 has Deb 10 V2 !!!. Developed perhaps depending on demand. TB 2 seems to be made for industry while TB for hobbyists. TB 2 S 4GB was cheaper by $30 than TB S R2.0 2GB or so from a local vendor and just jumped at it 😭😭
Don't worry too much about the version now. The day you get familiar and comfortable with linux, we can update tinker board2 to run Deb 11 but on the current kernel on the TB. Once you do that you will stop getting dependency issue for software like logitech media server, etc
 
To avoid dependency problem the first thing that is needed is to know is that where is your linux distribution being pulled from. You need to run two commands as below on the terminal and paste the output for us to see.

cat /etc/os-release
cat /etc/apt/sources.list
linaro@linaro-alip:~$ sudo cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
linaro@linaro-alip:~$ sudo cat /etc/apt/sources.list
deb http://http.debian.net/debian/ buster main contrib non-free
deb-src http://http.debian.net/debian/ buster main contrib non-free
deb http://security.debian.org/ buster/updates main contrib non-free
deb-src http://security.debian.org/ buster/updates main contrib non-free
deb http://http.debian.net/debian/ buster-updates main contrib non-free
deb-src http://http.debian.net/debian/ buster-updates main contrib non-free
linaro@linaro-alip:~$

I ran the two commands and the results are above. It is Buster and it has busted me 😤😤
 
linaro@linaro-alip:~$ sudo cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
linaro@linaro-alip:~$ sudo cat /etc/apt/sources.list
deb http://http.debian.net/debian/ buster main contrib non-free
deb-src http://http.debian.net/debian/ buster main contrib non-free
deb http://security.debian.org/ buster/updates main contrib non-free
deb-src http://security.debian.org/ buster/updates main contrib non-free
deb http://http.debian.net/debian/ buster-updates main contrib non-free
deb-src http://http.debian.net/debian/ buster-updates main contrib non-free
linaro@linaro-alip:~$

I ran the two commands and the results are above. It is Buster and it has busted me 😤😤
How is the boot happening. From the internal card or the external card. From whatever I have read, tinker can boot from the internal card or external micro sd card.
 
TB 2 S has 16GB eMMC. It can boot from micro SD also if a jumper is moved to Maskrom position.

All TBs with S (TB S, TB S R2.0 and TB 2 S plus Edge R and T have eMMC

It is very fast to boot up
 
TB 2 S has 16GB eMMC. It can boot from micro SD also if a jumper is moved to Maskrom position.

All TBs with S (TB S, TB S R2.0 and TB 2 S plus Edge R and T have eMMC

It is very fast to boot up
Booting from micro sd has the advantage of having multiple sd cards and trying out different settings. Once you have finalized one can do the same thing with the eMMC. But that's Ok if you are using eMMC. Let us proceed further.

What is the IP address of your NAS drive? Is it NTFS or FAT32 formatted?
 
Booting from micro sd has the advantage of having multiple sd cards and trying out different settings. Once you have finalized one can do the same thing with the eMMC. But that's Ok if you are using eMMC. Let us proceed further.

What is the IP address of your NAS drive? Is it NTFS or FAT32 formatted?
I have to check these.

but now taking cue from your earlier reply on the version of Deb and dependency issues, I used an earlier version of LMS (7.9.2) and it went on to install LMS.

executed

sudo systemctl enable logitechmediaserver

that finally coughed out

Synchronizing state of logitechmediaserver.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable logitechmediaserver
insserv: warning: script 'mountboot.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `mountboot.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `mountboot.sh'
insserv: warning: script 'rkisp_3A.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `rkisp_3A.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `rkisp_3A.sh'
insserv: warning: script 'mountboot.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `mountboot.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `mountboot.sh'
insserv: warning: script 'rkisp_3A.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `rkisp_3A.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `rkisp_3A.sh'
Failed to enable unit: Unit file /etc/systemd/system/logitechmediaserver.service is masked.

What could be the issue?

Still I proceeded with the script from Bobby

linaro@linaro-alip:~$ sudo addgroup lms
addgroup: The group `lms' already exists.
linaro@linaro-alip:~$ sudo usermod -aG lms squeezeboxserver
linaro@linaro-alip:~$ usermod -aG audio linaro
bash: usermod: command not found
linaro@linaro-alip:~$ sudo usermod -aG audio linaro
linaro@linaro-alip:~$ sudo usermod -aG audio squeezeboxserver
linaro@linaro-alip:~$ sudo mkdir /mnt/NAS
mkdir: cannot create directory ‘/mnt/NAS’: File exists
linaro@linaro-alip:~$ sudo chown linaro:lms /media/NAS
chown: cannot access '/media/NAS': No such file or directory

What is this chown command doing?
 
I have to check these.

but now taking cue from your earlier reply on the version of Deb and dependency issues, I used an earlier version of LMS (7.9.2) and it went on to install LMS.

executed

sudo systemctl enable logitechmediaserver

that finally coughed out

Synchronizing state of logitechmediaserver.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable logitechmediaserver
insserv: warning: script 'mountboot.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `mountboot.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `mountboot.sh'
insserv: warning: script 'rkisp_3A.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `rkisp_3A.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `rkisp_3A.sh'
insserv: warning: script 'mountboot.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `mountboot.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `mountboot.sh'
insserv: warning: script 'rkisp_3A.sh' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `rkisp_3A.sh'
insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `rkisp_3A.sh'
Failed to enable unit: Unit file /etc/systemd/system/logitechmediaserver.service is masked.

What could be the issue?
systemctl unmask logitechmediaserver.service
systemctl enable logitechmediaserver.service

The above will fix the error that the service is masked

Still I proceeded with the script from Bobby

linaro@linaro-alip:~$ sudo addgroup lms
addgroup: The group `lms' already exists.
linaro@linaro-alip:~$ sudo usermod -aG lms squeezeboxserver
linaro@linaro-alip:~$ usermod -aG audio linaro
bash: usermod: command not found
linaro@linaro-alip:~$ sudo usermod -aG audio linaro
linaro@linaro-alip:~$ sudo usermod -aG audio squeezeboxserver
linaro@linaro-alip:~$ sudo mkdir /mnt/NAS
mkdir: cannot create directory ‘/mnt/NAS’: File exists
linaro@linaro-alip:~$ sudo chown linaro:lms /media/NAS
chown: cannot access '/media/NAS': No such file or directory

What is this chown command doing?

do
sudo mkdir /media/NAS
sudo chown linaro:lms /media/NAS

the chown commands allows the linaro user to access the /media/NAS directory.

Next step will be to mount your external NAS device on /media/NAS directory.
 
systemctl unmask logitechmediaserver.service
systemctl enable logitechmediaserver.service

The above will fix the error that the service is masked



do
sudo mkdir /media/NAS
sudo chown linaro:lms /media/NAS

the chown commands allows the linaro user to access the /media/NAS directory.

Next step will be to mount your external NAS device on /media/NAS directory.
That worked I believe. thank you.....................
 
Let us now mount your external NAS drive on /media/NAS. For that we need the filesystem type and the IP address of the NAS server. If it is a ntfs share, then the username and password for the share will also be required
 
It says ext4 for File System
How did you find that out? If that were the case how did you mount the NAS drive on your macmini. Mac OS cannot mount ext4. Probably you are telling me the filesystem for unmounted /media/NAS
 
It is from the Synology App on my mobile.
View attachment 75463
Lovely. It means that synology is a linux device. Since your mac mini was able to mount it, it also means that your synology has samba installed. Do the following. Replace 192.168.1.100 with the IP address of your synology device

sudo mount -t nfs4 -o proto=tcp,port=2049 192.168.1.100:/media/NAS

If there is a problem you might have to install nfs-common and repeat the above mount command

sudo apt install nfs-common

After that run the command on your TB. It should show your mounted drive.


Then the command

ls -l /media/NAS

should list the files on your synology
 
linaro@linaro-alip:~$ sudo mount -t nfs4 -o proto=tcp,port=2049 192.168.0.115:/media/NAS
mount: 192.168.0.115:/media/NAS: can't find in /etc/fstab.

with later commands cannot see synology
 
Sorry. For synology I think the share is /volume1/share. The share name should be somewhere in the synology settings. Run the following command

sudo mount -t nfs4 -o proto=tcp,port=2049 192.168.1.100:/volume1/share /media/NAS
 
see this post. You need to tell me what is the share name configured in synology

 
linaro@linaro-alip:/media/NAS$ sudo mount -t nfs 192.168.0.115:/volume1/music
mount: 192.168.0.115:/volume1/music: can't find in /etc/fstab.
 
linaro@linaro-alip:/media/NAS$ sudo mount -t nfs 192.168.0.115:/volume1/music
mount: 192.168.0.115:/volume1/music: can't find in /etc/fstab.

It is
sudo mount -t nfs4 -o proto=tcp,port=2049 192.168.1.100:/volume1/music /media/NAS

you are missing out /media/NAS
 
Last edited:
Get the Award Winning Diamond 12.3 Floorstanding Speakers on Special Offer
Back
Top