I tried flash/wrire the all version shared on this thread as: Volumio, GentooPlayer, RuneAudio, Arch Linux...into my BBGW (them are images of BBB or BBW). But the all can't using wifi or Internet Over USB on my BBGW. So, I can't find my BBGW on Network Audio too.
This is as complete as I could make it without support.
If somebody has additional notes please tell me so I can make it even better
Thank you! Very usefull manual! Can you create new Volumio image?
Last edited:
Sorry ... see the last paragraph of my instructions ... I am not a Linux specialist and have no clue how to do Volumio
I have been fine-tuning my instructions anyway on my own experiences.
Somehow I have less trouble getting Debian 8 running O.K. compared to Debian 9. I don't know why.
I enclosed the latest version with even more information.
If you really follow all the steps you should be very close to a nice working Botic system.
-
Last edited:
Do you have any image / kernel (not necessarily including botic) that is able to support the wifi of the BBGW? We'll have to make an effort to upgrade the kernel of that one...
I can see Wifi on any images from last-image of beagleboard site if it support for BBGW. I run as below list:
1. Debian 9.9 2019-08-03 4GB SD IoT: https://debian.beagleboard.org/images/bone-debian-9.9-iot-armhf-2019-08-03-4gb.img.xz
2. Debian 9.9 2019-08-03 4GB SD LXQT: https://debian.beagleboard.org/images/bone-debian-9.9-lxqt-armhf-2019-08-03-4gb.img.xz
3. Debian 9.1 2017-09-21 4GB SD IoT: https://debian.beagleboard.org/images/bone-debian-9.1-iot-armhf-2017-09-21-4gb.img.xz
4. Debian 9.1 2017-08-31 4GB SD LXQT: http://debian.beagleboard.org/images/bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img.xz
5. Debian 8.7 2017-03-19 4GB SD LXQT: https://debian.beagleboard.org/images/bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img.xz
6. Debian 8.7 2017-03-19 4GB SD IoT: https://debian.beagleboard.org/images/bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz
I can acess to BBGW via Internet over USB with Putty SSH or Cloud IDE too.
Last edited:
Tks you for manual guide details . I will try the build later.Sorry ... see the last paragraph of my instructions ... I am not a Linux specialist and have no clue how to do Volumio
I have been fine-tuning my instructions anyway on my own experiences.
Somehow I have less trouble getting Debian 8 running O.K. compared to Debian 9. I don't know why.
I enclosed the latest version with even more information.
If you really follow all the steps you should be very close to a nice working Botic system.
-
Here is a small update, nothing new in content but corrected a typo and some other small corrections.
I still have a problem getting "mount -a" stick after reboot with Debian 9 but no problem with Debian 8.
Don't know why but for now I prefer Debian 8 ( 8.7 IoT )
Could be my NAS is playing me
I leave the BBB on all the time but in the event of a power-cycle I have to mount again with Debian 9 which is a small inconvenience but prefer to not bother at all
-
I still have a problem getting "mount -a" stick after reboot with Debian 9 but no problem with Debian 8.
Don't know why but for now I prefer Debian 8 ( 8.7 IoT )
Could be my NAS is playing me
I leave the BBB on all the time but in the event of a power-cycle I have to mount again with Debian 9 which is a small inconvenience but prefer to not bother at all
-
@chientechnical, did you verify that debian buster image also works? You can try the debian buster image I uploaded at one point. I have just re-uploaded it to the file service:
File upload and sharing. Large file transfers. Free online cloud storage.
The sha256 sum of the file you download should be:
You can also directly use the buster image as provided on the bb.org site and follow the instructions on GitHub - coroner21/linux-am33xbot at debian-buster to upgrade and install a kernel including botic patches.
File upload and sharing. Large file transfers. Free online cloud storage.
The sha256 sum of the file you download should be:
Code:
874c184cba06716bf64d79ab567eb3767a8ee1bb3dcc8c2e1b6c356c78c5656eHere is a small update, nothing new in content but corrected a typo and some other small corrections.
I still have a problem getting "mount -a" stick after reboot with Debian 9 but no problem with Debian 8.
Don't know why but for now I prefer Debian 8 ( 8.7 IoT )
Could be my NAS is playing me
I leave the BBB on all the time but in the event of a power-cycle I have to mount again with Debian 9 which is a small inconvenience but prefer to not bother at all
-
I have problem when used the codes (apt-get update, apt-get upgrade, sudo apt autoremove, apt-get install mc) as images attack below:
My ethernet are good, and I connect to my BBGW via USB: 192.168.7.2
Please hepl me
Attachments
I tried the following versions. It good performance - I see BeagleBone wifi are hotspot.
1. Debian 9.9 2019/08/03 4GB SD IOT
2. Debian 9.9 2019/08/03 4GB SD LXQT
3. Debian 9,5 2018/10/07 4GB SD IOT
4. Debian 9,5 2018/10/07 4GB SD LXQT
Then I performance as your guide but wrong as images attacked before.
I will the try on Debian 8 later.
My PC Windows are alway connected to Internet with wifi wireless 192.168.1.5
I only connect to my BBGW via Putty SSH via USB (Internet Over USB) with 192.168.7.2
So, BBGW are not connect to Internet, right?
Last edited:
It looks like your BBB is not connected to internet.
Your PC is on another subnet than BBB
PC = xxx.xxx.1.xxx
BBB = xxx.xxx.7.xxx
Normally when BBB starts it should get an IP addres from your router (DHCP server) and then your BBB also should have an IP address wit “1” in the 3rd block.
But this is standard TCP/IP / network technology not related to Botic.
Did you connect the USB/LAN converter to your router direct or do you have direct cable between BBB and PC ?
P.S. in Windows PC you can bridge you LAN connection (to BBGW) to your wireless connection.
Then the BBGW is also connected to the internet.
On internet is enough info how to do this: Google for “Windows LAN brigde to wireless”
Your PC is on another subnet than BBB
PC = xxx.xxx.1.xxx
BBB = xxx.xxx.7.xxx
Normally when BBB starts it should get an IP addres from your router (DHCP server) and then your BBB also should have an IP address wit “1” in the 3rd block.
But this is standard TCP/IP / network technology not related to Botic.
Did you connect the USB/LAN converter to your router direct or do you have direct cable between BBB and PC ?
P.S. in Windows PC you can bridge you LAN connection (to BBGW) to your wireless connection.
Then the BBGW is also connected to the internet.
On internet is enough info how to do this: Google for “Windows LAN brigde to wireless”
Last edited:
Another possibility is to connect your BBGW to the internet is to take it to your Wifi router (I guess it will also have some LAN ports; or use a port on the nearby switch) and put the LAN cable in an available LAN port.
Your BBGW will still be accessible from your PC ( make sure you do an IP scan to find the new IP address of the BBGW ) and continue from there.
Your BBGW will still be accessible from your PC ( make sure you do an IP scan to find the new IP address of the BBGW ) and continue from there.
Sorry, can you try again with this link: debian-botic | Files.fm.
This used to work some time ago at least...
Thank the support for anyone.
I having problem. Before, from my smart phone or my pc connect to Beaglebone hotspost, it's popup an web access for me enter the name and password of My Lan. But popup are miss now. So I will can't connect the BBGW to my LAN.
I tried all the version, but popup acess are miss all. I need repair this problem first.
Tks all ��
As I am trying to create a solid instruction how to install Debian + Botic I have tried several combinations.
Debian 8 + MPD 019 seems to be most stable and works fine for me.
Debian 9 / 10 with MPD 021 less so.
All with the latest Botic 4.8.13.
The problems with Debian 9 / 10 is that the system says "no soundcard" when "aplay -l" or "cat /proc/asound/cards" with identical settings as with Debian 8.
As Botic is also relatively old could this be an issue where Botic is not 100% compatible anymore with the newer Debian versions ?
Anybody similar impressions ?
P.S. for Debian 8 I downloaded 8.7 IoT and due to "apt-get upgrade" finally got 8.11.
Debian 8 + MPD 019 seems to be most stable and works fine for me.
Debian 9 / 10 with MPD 021 less so.
All with the latest Botic 4.8.13.
The problems with Debian 9 / 10 is that the system says "no soundcard" when "aplay -l" or "cat /proc/asound/cards" with identical settings as with Debian 8.
As Botic is also relatively old could this be an issue where Botic is not 100% compatible anymore with the newer Debian versions ?
Anybody similar impressions ?
P.S. for Debian 8 I downloaded 8.7 IoT and due to "apt-get upgrade" finally got 8.11.
Are ALSA utilities and libasound updated? It might be worth a try... 'sudo apt-get install libasound2 alsa-utils'
I have been using an older Debian 8 with absolutely no problem on BBB/Hermes/Cronus/Teleporter/B3Pro. As we have 'advanced' from the original Debian on which Botic ran till the most recent, there really has been no benefit in the main object of the system - clock rate adjustment. If there are other reasons to update, fine, but these instability findings will weigh against any advantage of newer versions.
Edit: does this help at all? ->. Debian User Forums • View topic - [Solved] Debian 10 - No sound card available to Pulseaudio
Last edited:
I am using teleporters for MCK in sync mode and it works very well. In my setup, these two caveats apply: 1) the connections to/from the teleporters are about 3 cm in length or less and soldered, and 2) I'm using the version of Cronus with the buffer for MCK. If I recall correctly, teleporters are good up to 150MHz.
Frank