Hello Robert and Everyone.
I'm a newbie with beaglebones black running debian...
I'm having a problem with connman and the interfaces file.
The problem arises with a beaglebone black rev c and the
image BBB-eMMC-flasher-debian-8.3-iot-armhf-2016-03-13-4gb.img, but also
happened with BBB-eMMC-f
Now everything make sense :-) I will take this into consideration for other
devices then. It is OK the minimalism for the console release. Thanks for
your work! regards.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Go
On Mon, Apr 27, 2015 at 11:23 AM, Jaime Fernández-Caro Belmonte
wrote:
> I solved the issue and just in case someone has it also this is what I did:
> debian@beaglebone:~$ lsusb
> Bus 001 Device 004: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070
> Wireless Adapter
> debian@beaglebone:~$ sudo
I solved the issue and just in case someone has it also this is what I did:
debian@beaglebone:~$ lsusb
Bus 001 Device 004: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070
Wireless Adapter
debian@beaglebone:~$ sudo dmesg -c > /dev/null
debian@beaglebone:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: N
root@beaglebone:~# sudo systemctl start wpa_supplicant
root@beaglebone:~# systemctl status wpa_supplicant
● wpa_supplicant.service - WPA supplicant
Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; disabled)
Active: active (running) since Sun 2015-04-26 20:47:58 CEST; 11s ago
Main
On Sun, Apr 26, 2015 at 1:41 PM, Jaime Fernández-Caro Belmonte
wrote:
> Hell man you are fast, thanks!
>
> Connman is not installed by default on that Release you made! So nop...
> Connman is not a trouble at this time... something else is interfering I
> think.
>
> Thanks!
How about, lets see wh
Hell man you are fast, thanks!
Connman is not installed by default on that Release you made! So nop...
Connman is not a trouble at this time... something else is interfering I
think.
Thanks!
El domingo, 26 de abril de 2015, 20:36:15 (UTC+2), RobertCNelson escribió:
>
> On Sun, Apr 26, 2015 at
On Sun, Apr 26, 2015 at 1:32 PM, Jaime Fernández-Caro Belmonte
wrote:
> Hello, I have upgraded my Debian distribution to latest one:
> https://rcn-ee.com/rootfs/bb.org/testing/2015-04-19/console/BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-19-2gb.img.xz
>
> I am facing issues with WiFi. Th
Hello, I have upgraded my Debian distribution to latest one:
https://rcn-ee.com/rootfs/bb.org/testing/2015-04-19/console/BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-19-2gb.img.xz
I am facing issues with WiFi. This is what I did:
sudo apt-get install wireless-tools wpasupplicant
sudo wpa
On Fri, Apr 17, 2015 at 12:54 PM, Jaime Fernández-Caro Belmonte
wrote:
> Hello,
>
> I´m testing connmanctl (debian-jessie-console-armhf-2015-04-09) and seems
> that I need to wrote complete path to it in order to interact with it
> "/usr/sbin/connmanctl"
>
> I think it should be included on system
Hello,
I´m testing connmanctl (debian-jessie-console-armhf-2015-04-09) and seems
that I need to wrote complete path to it in order to interact with it
"/usr/sbin/connmanctl"
I think it should be included on system or at least i´ve seen on forums is
being used just with 'connmanctl'. Any idea
Crystal clear. Thanks mate!
El miércoles, 15 de abril de 2015, 20:08:35 (UTC+2), RobertCNelson escribió:
> On Wed, Apr 15, 2015 at 1:00 PM, Jaime Fernández-Caro Belmonte
> wrote:
> > Thanks for your tries!
> >
> > When you say:
> > """
> > For bb.org, i've been using these tools to bring up eth
On Wed, Apr 15, 2015 at 1:00 PM, Jaime Fernández-Caro Belmonte
wrote:
> Thanks for your tries!
>
> When you say:
> """
> For bb.org, i've been using these tools to bring up eth0 over
> (/etc/network/interfaces)
> wheezy: wicd
> jessie: connman
> """
> This is not strictly true right? because on je
Thanks for your tries!
When you say:
"""
For bb.org, i've been using these tools to bring up eth0 over
(/etc/network/interfaces)
wheezy: wicd
jessie: connman
"""
This is not strictly true right? because on jessie with connman the
information on this path "/etc/network/interfaces" is nor really
On Tue, Apr 14, 2015 at 4:40 PM, Robert Nelson wrote:
> On Tue, Apr 14, 2015 at 4:32 PM, William Hermans wrote:
>> @Robert
>>
>> Any idea what is causing this ? I've yet to experience this myself, but I
>> always use ethernet + static IP. Did I mention that I dislike connman with a
>> passion ?
>
On Tue, Apr 14, 2015 at 5:06 PM, Jaime Fernández-Caro Belmonte
wrote:
> Thanks for your answer again Robert.
>
> Is this issue Kernel relevant? I mean, could be caused because Debian Jessie
> is supposed to be 3.16 by default and
> BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-09-2gb.img ha
Thanks for your answer again Robert.
Is this issue Kernel relevant? I mean, could be caused because Debian
Jessie is supposed to be 3.16 by default
and BBB-eMMC-flasher-debian-jessie-console-armhf-2015-04-09-2gb.img has
3.14 on it for BBB?
BRegards.
--
For more options, visit http://beaglebo
On Tue, Apr 14, 2015 at 4:32 PM, William Hermans wrote:
> @Robert
>
> Any idea what is causing this ? I've yet to experience this myself, but I
> always use ethernet + static IP. Did I mention that I dislike connman with a
> passion ?
In Jessie, I've been playing around with, [ifplugd] this after
@Robert
Any idea what is causing this ? I've yet to experience this myself, but I
always use ethernet + static IP. Did I mention that I dislike connman with
a passion ?
On Tue, Apr 14, 2015 at 11:46 AM, Robert Nelson
wrote:
> On Tue, Apr 14, 2015 at 1:35 PM, Jaime Fernández-Caro Belmonte
> wro
On Tue, Apr 14, 2015 at 1:35 PM, Jaime Fernández-Caro Belmonte
wrote:
> By the way the 2 minute delay on boot is also solved replacing this: auto
> eth0 By this: allow-hotplug eth0
Unless eth0 is plugged in at boot..
Then it doesn't always get an ip address.
Regards,
--
Robert Nelson
https://
By the way the 2 minute delay on boot is also solved replacing this: auto
eth0 By this: allow-hotplug eth0
Best regards!
El martes, 14 de abril de 2015, 20:21:21 (UTC+2), Jaime Fernández-Caro
Belmonte escribió:
>
> Now I understand why I could not configure WiFi...!!!
> I solved ETH0 issue co
Now I understand why I could not configure WiFi...!!!
I solved ETH0 issue commenting it.
Do you think is that a bug (to be solved) on jessie?
Thnks for your answer!
El martes, 14 de abril de 2015, 19:50:24 (UTC+2), RobertCNelson escribió:
>
> On Tue, Apr 14, 2015 at 12:43 PM, Jaime Fernández-Ca
On Tue, Apr 14, 2015 at 12:43 PM, Jaime Fernández-Caro Belmonte
wrote:
> Hello Robert,
>
> Is this connman also killing Jessie Console configuration (ETH-WifI)? Since
> a Month or Two I´m having problems with WiFi configuration and also with Eth
> under /etc/network/interfaces.
> It is installed b
Hello Robert,
Is this connman also killing Jessie Console configuration (ETH-WifI)? Since
a Month or Two I´m having problems with WiFi configuration and also with
Eth under /etc/network/interfaces.
It is installed by default for some reason now?
Thanks!
El lunes, 16 de marzo de 2015, 1:38:04 (
On Sun, Mar 15, 2015 at 7:34 PM, Ray Madigan wrote:
> I have an installation of Jessie lxqt running and am having difficulty
> getting it to use a static ip address.
>
> in /etc/network/interfaces I have
>
> auto eth0
> iface eth0 inet static
> address 192.168.1.113
> netmask 255.255.255.0
I have an installation of Jessie lxqt running and am having difficulty
getting it to use a static ip address.
in /etc/network/interfaces I have
auto eth0
iface eth0 inet static
address 192.168.1.113
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192
26 matches
Mail list logo
