Duffy Moon: the /etc/fstab uses different format, check the example on http://bbb.ieero.com/
That's the one I tried. It didn't work. It also takes hours to refresh the mpd database.
maybe they are mounted at time when the network connection is not yet established...
but you should have only one line per target directory. so either cifs or nfs, but not both
also it should work to call following from command line:
# umount can fail
umount /data/remote
# this should succeed
mount /data/remote
if mount does not succeed then check last lines of dmesg command
but you should have only one line per target directory. so either cifs or nfs, but not both
also it should work to call following from command line:
# umount can fail
umount /data/remote
# this should succeed
mount /data/remote
if mount does not succeed then check last lines of dmesg command
maybe they are mounted at time when the network connection is not yet established...
but you should have only one line per target directory. so either cifs or nfs, but not both
Ahh. I didn't realise. Well the cifs command worked manually so I'll just have that one in /etc/fstab and see how it goes.
I suppose that when it does work as it's supposed to, it stores the database in the remote directory, so that one only needs to refresh it when new music is added?
Also, I'm trying (and failing) to get mpdroid to work. Do I have to edit the /etc/mpd.conf file - i.e. comment out the local host line like this:
?#bind_to_address "localhost"
Last edited:
JTag & cape
Probably doesn't make any difference as the debugging if needed, would be done without the cape. The Hermes cape covers the jTag (J1) output header.
Probably doesn't make any difference as the debugging if needed, would be done without the cape. The Hermes cape covers the jTag (J1) output header.
J1 header is UART (serial)Probably doesn't make any difference as the debugging if needed, would be done without the cape. The Hermes cape covers the jTag (J1) output header.
Because of it's location - it is covered by almost every cape. 🙂
It can be useful to use it during boot with any cape just to be sure things are OK.
Great. It's working!bern: It should be enough to write line with "mt7601u" into /etc/modules
After rebooting SSIDs (wifi networks) are visable in the wicd-curses panel.
I can select my SSID and connect to my network even with 1A PSU.
Thank you very much miero
Last edited:
Miero to establish wifi connection with UWN200 WiFi dongle I installed wicd-curses package which is bulky (~30MB) and consumes some CPU power
(two processes: /usr/share/wicd/daemon/wicd-daemon.py and /usr/bin/python -O /usr/share/wicd/daemon/monitor.py consume about 3% of CPU)
Is there any other (more light) software for the same task? (eg. wifi network management). What do you recommend for Botic?
(two processes: /usr/share/wicd/daemon/wicd-daemon.py and /usr/bin/python -O /usr/share/wicd/daemon/monitor.py consume about 3% of CPU)
Is there any other (more light) software for the same task? (eg. wifi network management). What do you recommend for Botic?
Hi,
Is it necessary to disconnect Hermes from BBB before loading Volumio and trying to Boticize it?
Or can it be safely done with everything connected without the possibility of bricking the BBB?
Is it necessary to disconnect Hermes from BBB before loading Volumio and trying to Boticize it?
Or can it be safely done with everything connected without the possibility of bricking the BBB?
bern: I do not use wicd. It is enough to just write something like this into /etc/network/interfaces
Code:
auto wlan0
iface wlan0 inet dhcp
wpa-ssid YOUR-ESSID-HERE
wpa-psk YOYR-PASSWORD-HERE
This morning I powered up the BBB and got solid on led2 (activity indicator)
tried booting with botic v3 on ssd, various Debians would not flash or boot.
Tried booting with Angstrom_flash --- .img
BBB-eMMC-flasher-2013.09.12.img
and got
...Partition 1 not valid on dev 0
...spl : fat register err - - 1Running uname_boot ...
loading /boot/vmlinuz-4.0.0-botic5 ...
6223664 bytes read in 364 ms (16.3 MiB/s)
loading /boot/dtbs/4.0.0-botic5/am335x-boneblack.dtb ...
32313 bytes read in 44 ms (716.8 KiB/s)
loading /boot/initrd.img-4.0.0-botic5 ...
...### ERROR ### Please RESET the board ###
I did a reset button press and got ...
Running uname_boot ...
loading /boot/vmlinuz-4.0.0-botic5 ...
6223664 bytes read in 364 ms (16.3 MiB/s)
loading /boot/dtbs/4.0.0-botic5/am335x-boneblack.dtb ...
32313 bytes read in 44 ms (716.8 KiB/s)
loading /boot/initrd.img-4.0.0-botic5 ...
Strange thing in the 2nd example it shows loading /boot/dtbs/4.0.0-botic5
I've attached two examples from the Serial console output results .....
Just cannot get the BBB back to a normal boot after trying flashes of Debian, which don't take off on boot with the Cylon led display like flashing before.
tried booting with botic v3 on ssd, various Debians would not flash or boot.
Tried booting with Angstrom_flash --- .img
BBB-eMMC-flasher-2013.09.12.img
and got
...Partition 1 not valid on dev 0
...spl : fat register err - - 1Running uname_boot ...
loading /boot/vmlinuz-4.0.0-botic5 ...
6223664 bytes read in 364 ms (16.3 MiB/s)
loading /boot/dtbs/4.0.0-botic5/am335x-boneblack.dtb ...
32313 bytes read in 44 ms (716.8 KiB/s)
loading /boot/initrd.img-4.0.0-botic5 ...
...### ERROR ### Please RESET the board ###
I did a reset button press and got ...
Running uname_boot ...
loading /boot/vmlinuz-4.0.0-botic5 ...
6223664 bytes read in 364 ms (16.3 MiB/s)
loading /boot/dtbs/4.0.0-botic5/am335x-boneblack.dtb ...
32313 bytes read in 44 ms (716.8 KiB/s)
loading /boot/initrd.img-4.0.0-botic5 ...
Strange thing in the 2nd example it shows loading /boot/dtbs/4.0.0-botic5
I've attached two examples from the Serial console output results .....
Just cannot get the BBB back to a normal boot after trying flashes of Debian, which don't take off on boot with the Cylon led display like flashing before.
Attachments
Last edited:
bern: I do not use wicd. It is enough to just write something like this into /etc/network/interfaces
Code:auto wlan0 iface wlan0 inet dhcp wpa-ssid YOUR-ESSID-HERE wpa-psk YOYR-PASSWORD-HERE
You're right, less resource consuming way. I've removed wicd-curse.
Another two cases:
I found out that booting time of BBB with lan disconnected and only with wifi dongle plugged in is extremely long. I connected to BBB using serial-USB cable and it turned out that system waits about 100 second for lan connection.
Code:
[ 8.062422] libphy: PHY 4a101000.mdio:01 not found
[ 8.087078] net eth0: phy 4a101000.mdio:01 not found on slave 1
Second isuee: Using serial connection I see errors:
Code:
Debian GNU/Linux 7 botic ttyO0
Boticized BeagleBoard.org Debian Image 2015-02-15
default username:password is [root:botic] and [debian:botic]
The IP Address for wlan0 is: 192.168.1.15
botic login: [ 112.264303] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 117.273102] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 122.283971] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 127.925343] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 132.990782] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 138.663475] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 143.721929] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 148.752117] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 153.767088] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 158.784278] asoc-botic-card botic: ASoC: machine hw_params failed: -22
[ 163.797783] asoc-botic-card botic: ASoC: machine hw_params failed: -22
1) to speed up booting without Ethernet connection use "allow-hotplug eth0" instead of "auto eth0" in the /etc/network/interfaces
2) this is reported when invalid parameters for audio playback is reported ... you can ignore this if audio is played correctly.
I assume your audio player (which one are you using?) tries to set unsupported parameters and then falls back to supported one.
2) this is reported when invalid parameters for audio playback is reported ... you can ignore this if audio is played correctly.
I assume your audio player (which one are you using?) tries to set unsupported parameters and then falls back to supported one.
ichiban:
I assume old Angstrom images are not compatible with newer bootloaders, so you should try to use recent BeagleBoardDebian to fix your BBB...
1) download, extract and flash following image to SD card
https://rcn-ee.com/rootfs/2015-04-0...an-jessie-console-armhf-2015-04-09-2gb.img.xz
2) have serial console connected to BBB
3) boot SD card on BBB using hold button during boot procedure
4) check output on the serial console ... it should reflash eMMC and also fix boot EEPROM if damaged
if this fails, please paste serial output here
I assume old Angstrom images are not compatible with newer bootloaders, so you should try to use recent BeagleBoardDebian to fix your BBB...
1) download, extract and flash following image to SD card
https://rcn-ee.com/rootfs/2015-04-0...an-jessie-console-armhf-2015-04-09-2gb.img.xz
2) have serial console connected to BBB
3) boot SD card on BBB using hold button during boot procedure
4) check output on the serial console ... it should reflash eMMC and also fix boot EEPROM if damaged
if this fails, please paste serial output here
1) to speed up booting without Ethernet connection use "allow-hotplug eth0" instead of "auto eth0" in the /etc/network/interfaces
2) this is reported when invalid parameters for audio playback is reported ... you can ignore this if audio is played correctly.
I assume your audio player (which one are you using?) tries to set unsupported parameters and then falls back to supported one.
Thanks miero.
A major improvement in booting time after changing lan parameters to:" allow-hotplug eth0".🙂
I cannot fully tested playing functionality since I'm still waiting for second batch of Cronus+Hermes. Currently I can only report things I see in the logs. 😉
As a player I use squeezelie.
The error/warning:
Code:
asoc-botic-card botic: ASoC: machine hw_params failed: -22
Trying to play squeezelie I see:
Code:
ALSA snd_pcm_hw_hw_params:327 SNDRV_PCM_IOCTL_HW_PARAMS failed (-22)
Glad to see wifi working 🙂 are you guys at the stage where you can explain a recipe to add it in to the Botic build now? I'd love to get it sorted on mine.
# this will try to install packages from Botic repository
/source/boticize/02-install.sh
at the end ........
Configuration file `/etc/upmpdcli.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** upmpdcli.conf (Y/I/N/O/D/Z) [default=N] ?
I think I asked about this before but not sure what need to be the answer?
/source/boticize/02-install.sh
at the end ........
Configuration file `/etc/upmpdcli.conf'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** upmpdcli.conf (Y/I/N/O/D/Z) [default=N] ?
I think I asked about this before but not sure what need to be the answer?
Last edited:
Ha, I know now ... the USB_STORAGE is missing in the botic kernel ... so this feature is not supported.
I'll fix this next week...
Try to use network storage (shared disk) for now, it will work better than USB.
any updates Miero?
- Home
- More Vendors...
- Twisted Pear
- Support for Botic Linux driver