Support for Botic Linux driver

mikelangeloz · 2017-01-13 4:09 pm

miero said:
mikelangeloz: standard alsa in debian stable does not support DSD or high sample rates

I prepared a patched ALSA library, that must be installed before MPD is built:
- Index of /botic/pool/main/a/alsa-lib

In case you want to rebuild also this ALSA library, a updated kernel header /usr/include/sound/asound.h is also needed, that defines DSD formats.

Do you know where I can find the updated /usr/include/sound/asound.h ?
I'm trying to compile it on x86 as well...
PS: What about boticizing also Volumio's x86 kernel? What do you think?

miero · 2017-01-13 9:27 pm

you can find patched /usr/include/sound/pcm.h in the following .deb: http://repo.ieero.com/pool/main/l/linux-upstream/linux-libc-dev_1cross_armhf.deb

The x86 kernel could be extended to allow high sample rates (>192kHz), here is the patch: https://github.com/miero/linux-dev/...support-for-sampling-rates-up-to-768kHz.patch

However I'm not sure if there is a support for high sampling rates in other drivers, e.g. USB.

Other changes in Botic kernel are related only to BBB, so there is no need to port them.

ichiban · 2017-01-14 2:40 am

twluke said:
Well, apart from the IP connection to the Media Server, your system appears well back to the previous state. If you would like to try again the new botic7, please read carefully the instruction of old botic7 installation by miero. Probably you appears to have missed sync command at the final stage of installation on the last time.

Regards,

Not really back to the previous state, but a bare bones original botic 5.

I believe the reason that the Logitech Media Server running on a PC does not find a player, is because the version 5 Botic on the microSSD card I have from my original load of it to BBB last May of 2015 does not have the Squeezelite Player. So, I tried loading S-lite as per instructions at
"Botic HOWTOs for driver & tools"

https://docs.google.com/document/d/...OSF2fu3Sz4zzmaURM/edit#heading=h.xxqem0p4lig6

..and there were allsorts of errors.

So, before I try the instructions at

http://www.diyaudio.com/forums/twisted-pear/258254-support-botic-linux-driver-10.html#post4182051

...I have to ask, does the Botic version 7 include the Squeezelite player???
Then I would continue to try installing Botic v7, IF it has Squeezelite.

twluke · 2017-01-14 3:07 am

ichiban said:
...I have to ask, does the Botic version 7 include the Squeezelite player???
Then I would continue to try installing Botic v7, IF it has Squeezelite.

The botic7 deb file does not include squeezelite but you can download a linux package from this site beow:

https://sourceforge.net/projects/lmsclients/files/squeezelite/linux/

You might want to try to install the latest squeezelite-1.8.6-825-armv6hf.tar.gz there, though I'm not a user of squeezelite.

Regards,

twluke · 2017-01-14 6:36 am

twluke said:
The botic7 deb file does not include squeezelite but you can download a linux package from this site beow:

https://sourceforge.net/projects/lmsclients/files/squeezelite/linux/

You might want to try to install the latest squeezelite-1.8.6-825-armv6hf.tar.gz there, though I'm not a user of squeezelite.

Regards,

Well, the squeezelite above appears working on the botic7-rc3 system, at least on the console view (I don't have a physical device). Ichiban, you can go forward.

Code:

root@botic:/usr/src# cat /etc/dogtag
BeagleBoard.org Debian Image 2015-02-15
root@botic:~# uname -r
4.8.13-botic7-rc3
root@botic:/usr/src# tar -zxvf squeezelite-1.8.6-825-armv6hf.tar.gz
root@botic:/usr/src# ls -ld *
-rw-r--r-- 1 root root     2433 Feb  6  2015 LICENSE.txt
-rw-r--r-- 1 root root 13557072 Dec 10 01:03 linux-image-4.8.13-botic7-rc3_1_armhf.deb
-rwxr-xr-x 1 root root  1118040 Dec  7 18:42 squeezelite
-rw-r--r-- 1 root root  7672040 Dec 11 13:50 squeezelite-1.8.6-825-armv6hf.tar.gz
-rwxr-xr-x 1 root root 13673972 Dec  7 18:45 squeezelite-ffmpeg
root@botic:/usr/src# ./squeezelite -?
Squeezelite v1.8.6-825, Copyright 2012-2015 Adrian Smith, 2015-2016 Ralph Irving
root@botic:/usr/src# ./squeezelite
root@botic:~# top

 PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND           
 1305 root      20   0  9744 9548 3236 S   1.0  1.9   0:00.47 squeezelite       
 1315 root      20   0  2648 1652 1328 R   0.7  0.3   0:00.05 top               
  157 root      20   0     0    0    0 S   0.3  0.0   0:00.25 kworker/0:3       
 1310 root      20   0  8060 3772 3260 S   0.3  0.7   0:00.19 sshd              
    1 root      20   0  4684 3500 2392 S   0.0  0.7   0:01.08 systemd

Regards,

ichiban · 2017-01-14 4:10 pm

twluke said:

Well, the squeezelite above appears working on the botic7-rc3 system, at least on the console view (I don't have a physical device). Ichiban, you can go forward.

Code:

root@botic:/usr/src# cat /etc/dogtag
BeagleBoard.org Debian Image 2015-02-15
root@botic:~# uname -r
4.8.13-botic7-rc3
root@botic:/usr/src# tar -zxvf squeezelite-1.8.6-825-armv6hf.tar.gz
root@botic:/usr/src# ls -ld *
-rw-r--r-- 1 root root     2433 Feb  6  2015 LICENSE.txt
-rw-r--r-- 1 root root 13557072 Dec 10 01:03 linux-image-4.8.13-botic7-rc3_1_armhf.deb
-rwxr-xr-x 1 root root  1118040 Dec  7 18:42 squeezelite
-rw-r--r-- 1 root root  7672040 Dec 11 13:50 squeezelite-1.8.6-825-armv6hf.tar.gz
-rwxr-xr-x 1 root root 13673972 Dec  7 18:45 squeezelite-ffmpeg
root@botic:/usr/src# ./squeezelite -?
Squeezelite v1.8.6-825, Copyright 2012-2015 Adrian Smith, 2015-2016 Ralph Irving
root@botic:/usr/src# ./squeezelite
root@botic:~# top

 PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND           
 1305 root      20   0  9744 9548 3236 S   1.0  1.9   0:00.47 squeezelite       
 1315 root      20   0  2648 1652 1328 R   0.7  0.3   0:00.05 top               
  157 root      20   0     0    0    0 S   0.3  0.0   0:00.25 kworker/0:3       
 1310 root      20   0  8060 3772 3260 S   0.3  0.7   0:00.19 sshd              
    1 root      20   0  4684 3500 2392 S   0.0  0.7   0:01.08 systemd

Regards,

I will now try installing botic v7, thank you for your persistence. You, ARE ICHIBAN.

ichiban · 2017-01-14 8:36 pm

twluke said:
Please have a look at #1611 post by miero. It is the "instruction".
Regards,

So, I followed the instructions in post #1611 and got thesame result as before.
After reboot IP scanner doesn't find the BBB.

I know the results don't show the "sync" "reboot" because I captured the screen output before the "sync" command

and not after the "sync".

=================== Results ====================
root@botic:/etc/dpkg# chmod 755 /etc/dpkg/linux-image-4.8.13-botic7-rc3_1_armhf.deb
root@botic:/etc/dpkg# ls -la
total 13260
drwxr-xr-x 4 root root 4096 Jan 29 12:04 .
drwxr-xr-x 73 root root 4096 Feb 16 2015 ..
-rw-r--r-- 1 root root 446 Jun 13 2013 dpkg.cfg
drwxr-xr-x 2 root root 4096 Feb 16 2015 dpkg.cfg.d
-rwxr-xr-x 1 root root 13557072 Jan 29 12:04 linux-image-4.8.13-botic7-rc3_1_armhf.deb
drwxr-xr-x 2 root root 4096 Feb 15 2015 origins
=========================================
root@botic:/etc/dpkg# dpkg -i /etc/dpkg/linux-image-4.8.13-botic7-rc3_1_armhf.deb
Selecting previously unselected package linux-image-4.8.13-botic7-rc3.
(Reading database ... 23252 files and directories currently installed.)
Unpacking linux-image-4.8.13-botic7-rc3 (from .../linux-image-4.8.13-botic7-rc3_1_armhf.deb) ...
Setting up linux-image-4.8.13-botic7-rc3 (1) ...
update-initramfs: Generating /boot/initrd.img-4.8.13-botic7-rc3
zz-uenv_txt: Updating /boot/uEnv.txt [uname_r=4.8.13-botic7-rc3]
root@botic:/etc/dpkg#
=========================== END RESULTS ==============

miero · 2017-01-14 10:59 pm

ichiban, serial console output?

twluke · 2017-01-14 11:13 pm

ichiban said:
So, I followed the instructions in post #1611 and got thesame result as before.
After reboot IP scanner doesn't find the BBB.

That's a pity.

Again I cannot find anything wrong with the installation log. Perhaps your micro SD card containing new botic 7 system may have a corrupted filesystem, that may be preventing normal boot-up. If that so, usually the fsck command may solve this problem. If you can boot up the BBB from eMMC, you might want to try this command to examine your SD card.

Regards,

ichiban · 2017-01-15 1:07 am

twluke said:
That's a pity.

Again I cannot find anything wrong with the installation log. Perhaps your micro SD card containing new botic 7 system may have a corrupted filesystem, that may be preventing normal boot-up. If that so, usually the fsck command may solve this problem. If you can boot up the BBB from eMMC, you might want to try this command to examine your SD card.

Regards,

Did not have file on SD card.
File was downloaded to PC then TTY'd to the BBB into folder /etc/dpkg and the rights chmod'd to -rwxr-xr-x .

Is this the file I should use? linux-image-4.8.13-botic7-rc3_1_armhf.deb ???
I see there are also firmware, headers, image, and upstream files??

ichiban · 2017-01-15 1:15 am

miero said:
ichiban, serial console output?

I'm sorry to say, but it's been a year and a half or more since I last did a 'serial console output' when I had problems getting BBB/Botic loaded when the Cronus/Hermes PCBs were released.

I'll have to search back in this thread to see how you last gave me help/instructions to do that.

Also, at what point do you need output? Right now the BBB will only start up with a SD card with botic v5 on it.

Cheers

miero · 2017-01-15 1:18 am

Try also searching on Web, for example: Beagleboard:BeagleBone Black Serial - eLinux.org

Couple of last lines after restart (before halting/stopping) should hint us, where is the problem.

twluke · 2017-01-15 1:24 am

ichiban said:
Did not have file on SD card.
File was downloaded to PC then TTY'd to the BBB into folder /etc/dpkg and the rights chmod'd to -rwxr-xr-x .

So you are booting up the botic-BBB from eMMC? If so, the file system in the eMMC may be corrupted.

Do you have a bootable SD card? If you have it, can you boot the BBB from it? If you can, boot the BBB via SD card and check the filesystem in eMMC (something like /dev/mmcblk.) by fsck.

BTW, the easiest way to solve your problem would be to have a dedicated linux system on a PC. Ubuntu, e.g., is qute easy to set up.

Regards,

ichiban · 2017-01-15 1:40 am

miero said:
Try also searching on Web, for example: Beagleboard:BeagleBone Black Serial - eLinux.org

Couple of last lines after restart (before halting/stopping) should hint us, where is the problem.

Just to be clear, the condition of the BBB is after the attempted v5 update to v7.

The BBB will not boot up as it is now.

In order to boot it up, I must use a SD card with botic v5 on it.

So, do you want those 'lines after restart' with the BBB started with the 'botic v5 SD card'?

ichiban · 2017-01-15 2:07 am

twluke said:
So you are booting up the botic-BBB from eMMC? If so, the file system in the eMMC may be corrupted.

Do you have a bootable SD card? If you have it, can you boot the BBB from it? If you can, boot the BBB via SD card and check the filesystem in eMMC (something like /dev/mmcblk.) by fsck.

BTW, the easiest way to solve your problem would be to have a dedicated linux system on a PC. Ubuntu, e.g., is qute easy to set up.

Regards,

No experience with fsck, but here is what I have so far ......
====================================================
login as: root
Debian GNU/Linux 7 \n \l

Boticized BeagleBoard.org Debian Image 2015-02-15

default username

assword is [root:botic] and [debian:botic]

root@192.168.1.2's password:
Last login: Sat Jan 14 21:07:01 2017 from msipc.home
root@botic:~#
root@botic:/dev# fsck -v mmcblk
fsck from util-linux 2.20.1
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
[-I inode_buffer_blocks] [-P process_inode_size]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume "yes" to all questions
-c Check for bad blocks and add them to the badblock list
-f Force checking even if filesystem is marked clean
-v Be verbose
-b superblock Use alternative superblock
-B blocksize Force blocksize when looking for superblock
-j external_journal Set location of the external journal
-l bad_blocks_file Add to badblocks list
-L bad_blocks_file Set badblocks list

root@botic:/dev# fsck.ext4 -v mmcblk
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext4: No such file or directory while trying to open mmcblk
Possibly non-existent device?

root@botic:/dev# fsck.ext4 -v /dev/mmcblk
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext4: No such file or directory while trying to open /dev/mmcblk
Possibly non-existent device?

root@botic:/dev# cd ..
root@botic:/# pwd
/

root@botic:/# fsck.ext4 -v /dev/mmcblk
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext4: No such file or directory while trying to open /dev/mmcblk
Possibly non-existent device?

root@botic:/# fsck.ext4 -v /dev/mmcblk0
e2fsck 1.42.5 (29-Jul-2012)
/dev/mmcblk0 is in use.
e2fsck: Cannot continue, aborting.

root@botic:/#

twluke · 2017-01-15 6:45 am

ichiban said:
No experience with fsck, but here is what I have so far ......
-snip-
root@botic:~#
root@botic:/dev# fsck -v mmcblk

Well, I assume that the record above is deriving from the botic5 system running on your SD card. Firstly, you have to find the device name of eMMC in which you probably installed botic7 deb file. To do this, try this command "fdisk -l".

The command will show the devices pertinent to the booted system and probably you'll find the devices like below:

Code:

Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk1p1   *        2048       26623       12288    e  W95 FAT16 (LBA)
/dev/mmcblk1p2           26624     1433599      703488   83  Linux

Then, issue this command "fsck /dev/mmcblk1p2".

If there is any problems with the device, the command will ask you for repair. Answer "yes' to all questions and the process will be done. If there is no problems with the device, the command will show no asking.

"fsck /dev/mmcblk1p1" will be also worth trying.

Usually /dev/mmcblk0p1 and/or /dev/mmcblk0p2 are the devices now booting up the BBB (your SD card in this case) and can not be modified.

If eMMC devices are supposed to be shown as /dev/mmcblk0xx, then fsck them.

Regards,

kencmh · 2017-01-17 5:31 am

miero said:
kencmh, I suspect that MPD from volumio does not support "dsd_native yes" option.

But this is already the latest version downloaded from this link http://updates.volumio.org/bbb/volumio/2.041/volumio-2.041-2016-12-11-bbb.img.zip

Is there any update version?

ichiban · 2017-01-20 1:20 am

fdisk -l results

twluke said:
Well, I assume that the record above is deriving from the botic5 system running on your SD card. Firstly, you have to find the device name of eMMC in which you probably installed botic7 deb file. To do this, try this command "fdisk -l".

The command will show the devices pertinent to the booted system and probably you'll find the devices like below:

Code:

Device Boot Start End Blocks Id System /dev/mmcblk1p1 * 2048 26623 12288 e W95 FAT16 (LBA) /dev/mmcblk1p2 26624 1433599 703488 83 Linux

Then, issue this command "fsck /dev/mmcblk1p2".

If there is any problems with the device, the command will ask you for repair. Answer "yes' to all questions and the process will be done. If there is no problems with the device, the command will show no asking.

"fsck /dev/mmcblk1p1" will be also worth trying.

Usually /dev/mmcblk0p1 and/or /dev/mmcblk0p2 are the devices now booting up the BBB (your SD card in this case) and can not be modified.

If eMMC devices are supposed to be shown as /dev/mmcblk0xx, then fsck them.

Regards,

Here are the results.

root@botic:/var/log# fdisk -l

Disk /dev/mmcblk0: 3867 MB, 3867148288 bytes
4 heads, 16 sectors/track, 118016 cylinders, total 7553024 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 2048 26623 12288 e W95 FAT16 (LBA)
/dev/mmcblk0p2 26624 7553023 3763200 83 Linux

Disk /dev/mmcblk0boot1: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders, total 4096 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mmcblk0boot1 doesn't contain a valid partition table

Disk /dev/mmcblk0boot0: 2 MB, 2097152 bytes
4 heads, 16 sectors/track, 64 cylinders, total 4096 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mmcblk0boot0 doesn't contain a valid partition table
root@botic:/var/log#
root@botic:/var/log#
root@botic:/var/log#
root@botic:/var/log# fsck /dev/mmcblk1p2
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk1p2
Possibly non-existent device?
root@botic:/var/log#
root@botic:/var/log# fsck /dev/mmcblk1p1
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk1p1
Possibly non-existent device?
root@botic:/var/log#
root@botic:/var/log#
root@botic:/var/log# fsck /dev/mmcblk0
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
/dev/mmcblk0 is in use.
e2fsck: Cannot continue, aborting.

twluke · 2017-01-20 3:09 am

ichiban said:
Here are the results.

root@botic:/var/log# fdisk -l

Disk /dev/mmcblk0: 3867 MB, 3867148288 bytes
4 heads, 16 sectors/track, 118016 cylinders, total 7553024 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/mmcblk0p1 * 2048 26623 12288 e W95 FAT16 (LBA)
/dev/mmcblk0p2 26624 7553023 3763200 83 Linux

Assuming that you are booting up the BBB via the SD card, this /dev/mmcblk0 is corresponding to it.

While, the fdisk message below

root@botic:/var/log# fsck /dev/mmcblk1p2
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk1p2
Possibly non-existent device?
root@botic:/var/log#
root@botic:/var/log# fsck /dev/mmcblk1p1
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk1p1
Possibly non-existent device?

will suggest you have no valid botic5 system in the eMMC. You need to flash eMMC by botic5 and confirm it can boot up the BBB. Then try to install botic7. If this fails to boot up after installation, then try to fsck the eMMC device.

Regards,

ichiban · 2017-01-20 3:23 am

twluke said:
Assuming that you are booting up the BBB via the SD card, this /dev/mmcblk0 is corresponding to it.

While, the fdisk message below
will suggest you have no valid botic5 system in the eMMC. You need to flash eMMC by botic5 and confirm it can boot up the BBB. Then try to install botic7. If this fails to boot up after installation, then try to fsck the eMMC device.

Regards,

No, this is a boot without SDcard. I will give another try installing botic7.

If it does not boot after botic7 install, how do I do an fsck when I can't reach the BBB with puTTY?
and how do I fsck the eMMC?
Thanks

Support for Botic Linux driver

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member