I ran “ifconfig” and this is what I got:


root@overo:~# ifconfig

lo        Link encap:Local Loopback 

          inet addr:  Mask:

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:16 errors:0 dropped:0 overruns:0 frame:0

          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:1152 (1.1 KiB)  TX bytes:1152 (1.1 KiB)


root@overo:~# ifconfig hci0 up


hci0: unknown interface: no such device:





"People sleep peaceably in their beds at night only because rough men

stand ready to do violence on their behalf." - George Orwell


From: Geoffrey Atkinson [mailto:geoffrey.j.atkinson@gmail.com]
Sent: Wednesday, June 15, 2011 5:53 PM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] ifconfig problem


Perhaps related, I observe the following behavior:  (Overo FE w/ Tobi)

On initial boot running ifconfig (via console) results in no output.

Machine is unpingable.

Restarting the network daemon usually doesn't help - results in device not found

Reboot and everything is fine.

I see the above behavior on 3 out of 5 cold starts.

On Wed, Jun 15, 2011 at 5:39 PM, William Pretty Security Inc <bill.pretty@xplornet.com> wrote:

Hi All;

I remember seeing a post on here about a problem with ifconfig and the Tobi boards,

but I can’t remember what the solution was L There was some kind of a conflict in

system setting I think.


The problem is that the ”ifconfig eth0 up” command results in a device not found message …


Can anyone remember what the solution was ??






A prisoner of war is a man who tries to kill you and fails, and then asks you not to kill him.

Winston Churchill


EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
gumstix-users mailing list