[beagleboard] Re: Having to manually start Wifi

2015-04-02 Thread DeKay
This solution worked great for me on an image from a few months back. I highly suggest taking this route. http://madscientistlabs.blogspot.ca/2015/01/wifi-on-beaglebone-black-with-systemd.html On Thursday, 19 March 2015 10:06:22 UTC-6, Nathaniel Johnson wrote: I have been trying to get

Re: [beagleboard] Re: Having to manually start Wifi

2015-03-30 Thread Graham Haddock
Brian: Thanks for the pointers. I will go read up on it. Thanks, --- Graham == On Fri, Mar 27, 2015 at 7:06 PM, Brian Anderson b...@nwlink.com wrote: Since you are using Jessie images, have you tried using ConnMan to manage the WiFi connection rather than resorting to all of this systemd

Re: [beagleboard] Re: Having to manually start Wifi

2015-03-27 Thread Upol Ryskulova
Hello Graham, Thank you for your help. I re-implement systemd-timer service as you suggested. But service that timer expected to start after 30 sec , just starts after 4-5 sec after I start timer. So I just ended up to put sleep 30 in my script. Now (at least 3 times I tried) it has got its'

[beagleboard] Re: Having to manually start Wifi

2015-03-27 Thread Brian Anderson
Since you are using Jessie images, have you tried using ConnMan to manage the WiFi connection rather than resorting to all of this systemd and ifup/ifdown stuff? You can configure ConnMan using the connmanctl command line utility, or via the cmst GUI utility. to setup your link (ssid,

[beagleboard] Re: Having to manually start Wifi

2015-03-26 Thread Upol Ryskulova
Hello Graham, I have problem in getting stable wireless connection on BBB. I asked this quiestion

Re: [beagleboard] Re: Having to manually start Wifi

2015-03-26 Thread Graham Haddock
To get a reliable start of the WiFi service with jessie, I did the following: 1.) do NOT uncomment the wireless enable/start lines in /etc/network/interfaces. This would try to start up the WiFi before USB is up and running and stable. Apparently, once wpa_supplicant gets the error, it will not

Re: [beagleboard] Re: Having to manually start Wifi

2015-03-26 Thread Graham Haddock
I have not tried it. No time, yet. It seems like a much simpler solution than mine. What I intend to do is look in the .service file called by Frederik's solution, and see what that uses for dependencies they used for starting the service. Thanks, --- Graham == On Thu, Mar 26, 2015 at 11:56

Re: [beagleboard] Re: Having to manually start Wifi

2015-03-26 Thread Nathaniel Johnson
Graham, did you try Fredrik's solution? It works fine for me though left the auto wlan0 line in the interfaces file. -Nathaniel On Thu, Mar 26, 2015 at 11:54 AM, Graham Haddock gra...@flexradio.com wrote: To get a reliable start of the WiFi service with jessie, I did the following: 1.) do

[beagleboard] Re: Having to manually start Wifi

2015-03-24 Thread Nathaniel Johnson
UPDATE: Fredrik Olofsson's solution worked for me. I left in my auto statement as well. On Thursday, March 19, 2015 at 11:06:22 AM UTC-5, Nathaniel Johnson wrote: I have been trying to get wifi to work on the latest debian image. It does work but requires me to manually start it after

[beagleboard] Re: Having to manually start Wifi

2015-03-20 Thread Fredrik Olofsson
i found out that 'allow-hotplug' made wlan0 start at startup. here's how i setup my interfaces file... sudo pico /etc/network/interfaces #auto eth0 allow-hotplug eth0 #auto wlan0 allow-hotplug wlan0 iface wlan0 inet dhcp wpa-ssid ”name” wpa-psk ”pass” wireless-power off

[beagleboard] Re: Having to manually start Wifi

2015-03-20 Thread Nathaniel Johnson
Thanks for the reply. I will try Fredrik Olofsson's solution first but if that doesn't work I will use the systemd method. On Thursday, March 19, 2015 at 4:28:23 PM UTC-5, Graham wrote: It is a boot order problem. I reported it a month ago, or so. Debian is trying to start WiFi before the

[beagleboard] Re: Having to manually start Wifi

2015-03-19 Thread Graham
It is a boot order problem. I reported it a month ago, or so. Debian is trying to start WiFi before the USB interface is fully up, therefore it fails. If you wait until after the USB interface is fully up and running, you can manually start the WiFi. Or, write a systemd service to start it