Go Back   Home > Forums > > >
Home Forums Rules Articles diyAudio Store Blogs Gallery Wiki Register Donations FAQ Calendar Search Today's Posts Mark Forums Read

Twisted Pear Superior quality electronic kits

Reply
 
Thread Tools Search this Thread
Old 23rd August 2019, 01:21 PM   #2871
wealas is offline wealas
diyAudio Member
 
Join Date: Apr 2017
Not the kbuild package, the linux-kbuild package: Debian -- Details of package linux-kbuild-4.19 in buster - obviously this version won't work.
  Reply With Quote
Old 24th August 2019, 10:19 AM   #2872
amigo1 is offline amigo1
diyAudio Member
 
amigo1's Avatar
 
Join Date: Jan 2019
Default MPD 0.20.23 оr 0.21.13 to Beaglebone Black, Debian 10

Quote:
Originally Posted by wealas View Post
MPD
Please explain, which MPD 0.20.23 оr 0.21.13 you prefer install to Beaglebone Black?
  Reply With Quote
Old 25th August 2019, 05:55 PM   #2873
wealas is offline wealas
diyAudio Member
 
Join Date: Apr 2017
Neither, I was only using mpd for testing, I moved away from the BBB altogether.
  Reply With Quote
Old 26th August 2019, 06:56 AM   #2874
amigo1 is offline amigo1
diyAudio Member
 
amigo1's Avatar
 
Join Date: Jan 2019
Default Debian 10 for BBB

Quote:
Originally Posted by wealas View Post
Neither, I was only using mpd for testing, I moved away from the BBB altogether.
Why you have moved away from the BBB?
  Reply With Quote
Old 27th August 2019, 09:03 AM   #2875
Oystein is offline Oystein  Netherlands
diyAudio Member
 
Join Date: Jun 2009
Location: Zierikzee
Quote:
Originally Posted by twluke View Post
.
Thank you again for your support here (August, 9th) to get your image working.

I had multiple issues and after some testing I relaised what went wrong.

First of all my drive mount (mount -a) was not maintained after reboot.
I managed to fix this.

Due to my very limited Linux knowledge it took me some time to realise that the command "mpc play" only gives a result if MPD is playing a song which I could nog manage in the beginning.

The only final persistent problem is that I have troubles getting MPD to work after reboot.

Many times I have to run the following commands again to get it running:
systemctl stop mpd.service
systemctl daemon-reload
systemctl start mpd.service

I already edited /lib/systemd/system/mpd.service (replaced $MPDCONF with /etc/mpd.conf)

Then I test MPD by "systemctl status mpd.service" to see if it gives no errors, then the system works as expected.

Are there some debugging commands I can try when I get errors at "systemctl status mpd.service" ?
  Reply With Quote
Old 27th August 2019, 10:08 AM   #2876
twluke is offline twluke  Japan
diyAudio Member
 
Join Date: Nov 2012
Location: Tokyo
Support for Botic Linux driver
Quote:
Originally Posted by Oystein View Post
First of all my drive mount (mount -a) was not maintained after reboot.
I managed to fix this.
If mount -a after each reboot is somewhat annoying, you can automatically launch this command using /etc/rc.local. As the recent debian system including my image does not originally support this function, you have to make it enable. The method is well written in this URL.

Quote:
-snip-
Then I test MPD by "systemctl status mpd.service" to see if it gives no errors, then the system works as expected.
Your approach is correct. The MPD does not automatically start after booting. If the original contents in the /root directory are mostly remaining, you can find "on", "off" and "stat" scripts there, which are executable. If you want to start MPD, just send ./on and then ./stat for checking status. Then you can start mpc play. If you want to stop MPD, just send ./off.

Quote:
Are there some debugging commands I can try when I get errors at "systemctl status mpd.service" ?
I don't know such commands but the bottom lines in systemctl status mpd.service will always give you such hints.

Regards,
  Reply With Quote
Old 27th August 2019, 10:52 AM   #2877
mr_whocares is offline mr_whocares  Germany
diyAudio Member
 
Join Date: Mar 2005
Location: germany
Quote:
Originally Posted by Oystein View Post
Thank you again for your support here (August, 9th) to get your image working.

I had multiple issues and after some testing I relaised what went wrong.

First of all my drive mount (mount -a) was not maintained after reboot.
I managed to fix this.

Due to my very limited Linux knowledge it took me some time to realise that the command "mpc play" only gives a result if MPD is playing a song which I could nog manage in the beginning.

The only final persistent problem is that I have troubles getting MPD to work after reboot.

Many times I have to run the following commands again to get it running:
systemctl stop mpd.service
systemctl daemon-reload
systemctl start mpd.service

I already edited /lib/systemd/system/mpd.service (replaced $MPDCONF with /etc/mpd.conf)

Then I test MPD by "systemctl status mpd.service" to see if it gives no errors, then the system works as expected.

Are there some debugging commands I can try when I get errors at "systemctl status mpd.service" ?
i had the same issue with running mpd. and the mdp database could not get updated properly as well. the solution was to re-install mpd. after that everything is working fine!

just do:
apt-get remove mpd
apt-get install mpd

my only issue is that the wlan connection is unstable and getting interrupted regularly . but this seems to be a known issue with debian in general.

thanks a lot again to twluke for the image!
  Reply With Quote
Old 27th August 2019, 01:08 PM   #2878
bern is offline bern  Poland
diyAudio Member
 
Join Date: Jul 2010
Quote:
Originally Posted by coroner21 View Post
Found the cause of the major problem with buffer underruns in case more serializers were enabled: Apparently a code change in mcasp caused unused serializers not to be explicitly de-activated anymore which does not really work for our purposes.

Reversing this and applying another minor patch based on miero's initial patch set for the botic driver I am now able to get also DSD working and sample rates up to 384khz.

The updated driver based on linux-4.19 should work with the following (only stereo playback tested on my side though):
  • Standard I2S playback (up to 384khz on 8 channels)
  • DSD playback (up to 4 channels tested only with DSD64 so far (I do not have any other DSD files))
  • I2C control of an ES9018 DAC using sabre32 codec (use the botic codec for generic I2S DAC)

Since I do not need or use it I did not care to maintain the code for the record / SPDIF configuration: This updated driver only works in I2S / DSD mode and the serconfig parameter is not parsed anymore. In addition, my clocks are 45158400 and 49152000 so this is how the driver is configured per default (the usual module parameters can be used to overwrite this).

I have created a github repository and instructions are provided there if anyone wants to try this: GitHub - coroner21/linux-am33xbot: Arch Linux ARM Kernel with botic patches
I installed Arch Linux on my BBB and would like to build patched Botic kernel.
After cloning the repository when I start with:
Code:
makepkg -A
I receive an error:
Code:
/bin/sh: arm-linux-gnueabihf-gcc: command not found
Do I really need recompiller on armv7l (BBB) machine?
It would be nice to have a new fresh image of Arch with Botic patched kernel.

Last edited by bern; 27th August 2019 at 01:14 PM.
  Reply With Quote
Old 28th August 2019, 10:07 PM   #2879
amigo1 is offline amigo1
diyAudio Member
 
amigo1's Avatar
 
Join Date: Jan 2019
Default New Volumio img for beaglebone black

Quote:
Originally Posted by twluke View Post
Regards,
Please specify, why your last Volumio img file for beaglebone black is so big?
Mayby it is time to re-release it ?
  Reply With Quote
Old 29th August 2019, 10:11 AM   #2880
mr_whocares is offline mr_whocares  Germany
diyAudio Member
 
Join Date: Mar 2005
Location: germany
Default /source/boticize/01-addrepos.sh , /source/boticize/02-install.sh

hi miero,

i have been trying to re-install my volumio1.5BBB again. during the boticizing according to your old instructions, which always worked very fine for me in the past, i am getting now messages that many links can not be found anymore during executing the boticize scripts :-(
(please see the scripts
/source/boticize/01-addrepos.sh
/source/boticize/02-install.sh
/source/boticize/03-enablepm.sh )

any chance to update the scripts or any suggestions please? thanks a lot for you support !

best regards
  Reply With Quote

Reply


Support for Botic Linux driverHide this!Advertise here!
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Open baffle with fullrange driver and bass support Godzilla Full Range 5 22nd July 2011 01:32 PM
Low end support for single driver monitors strider75 Multi-Way 97 30th September 2009 03:02 PM
ASIO support (driver) for Labview Aoxomox Digital Line Level 0 3rd May 2009 05:29 PM
Linux/BruteFIR support coming in LspCAD tcpip Multi-Way 18 18th October 2005 03:08 AM
linux badgers Introductions 3 3rd April 2005 03:27 PM


New To Site? Need Help?

All times are GMT. The time now is 03:27 PM.


Search Engine Optimisation provided by DragonByte SEO (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 14.29%
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2019 DragonByte Technologies Ltd.
Copyright ©1999-2019 diyAudio
Wiki