Thank you for your suggestion
Also, I'm sorry reply late.
So I am not native English, I takes time to write.
>Ubuntu I believe uses a different network manager
I am aware network maneger is used in GUI environment, and, should not be
used on the server without a GUI
Am I wrong?
>Try change auto wlan0 to allow-hotplug wlan0.
I changed
# auto wlan0
allow-hotplug wlan0
After that, I started wlan0
ifup wlan0
Message is displayed
RTNETLINK answers: File exists
Failed to bring up wlan0
wlan0 had started.
ifconfig
wlan0 Link encap: Ethernet HWaddr dc: fb: 02:59:1 d: 4e
inet addr: 192.168.12.101 Bcast: 192.168.12.255 Mask:
255.255.255.0
inet6 addr: fe80 :: defb: 2ff: fe59: 1d4e/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
RX packets: 1115 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 33 errors: 0 dropped: 0 overruns: 0 carrier: 0
collisions: 0 txqueuelen: 1000
RX bytes: 163039 (163.0 KB) TX bytes: 6373 (6.3 KB)
However, like the previous, wifi unable to communicate. ping unreachable
2014-06-07 21:44 GMT+09:00 Aspect-ex <aspect...@gmail.com>:
> Thank you for your suggestion
> Also, I'm sorry reply late.
> So I am not native English, I takes time to write.
>
>
>
> >Ubuntu I believe uses a different network manager
> I am aware network maneger is used in GUI environment, and, should not be
> used on the server without a GUI
> Am I wrong?
>
>
>
> >Try change auto wlan0 to allow-hotplug wlan0.
> I changed
> # auto wlan0
> allow-hotplug wlan0
>
> After that, I started wlan0
> ifup wlan0
>
> Message is displayed
> RTNETLINK answers: File exists
> Failed to bring up wlan0
>
> wlan0 had started.
> ifconfig
> wlan0 Link encap: Ethernet HWaddr dc: fb: 02:59:1 d: 4e
> inet addr: 192.168.12.101 Bcast: 192.168.12.255 Mask:
> 255.255.255.0
> inet6 addr: fe80 :: defb: 2ff: fe59: 1d4e/64 Scope: Link
> UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric: 1
> RX packets: 1115 errors: 0 dropped: 0 overruns: 0 frame: 0
> TX packets: 33 errors: 0 dropped: 0 overruns: 0 carrier: 0
> collisions: 0 txqueuelen: 1000
> RX bytes: 163039 (163.0 KB) TX bytes: 6373 (6.3 KB)
>
> However, like the previous, wifi unable to communicate. ping unreachable
>
>
>
> _/_/_/_/_/_/_/_/_/_/_/_/_Aspect
> アスペクト
> 斉藤 和之
> Tel : 090-3638-9234
> E-mail : aspect.ex@gmail,com
>
>
> 2014-06-07 4:48 GMT+09:00 <konrad.tomal...@gmail.com>:
>
> I have similar problems with Debian console image.For me if eth0 is down,
>>> wlan0 can't initialize correctly. Try change auto wlan0 to allow-hotplug
>>> wlan0.
>>>
>>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/yvPd-nmUVbk/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
