SCIENTIFIC-LINUX-USERS Archives

April 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Reply To:
Date:
Mon, 29 Apr 2013 13:01:05 +0900
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
On 04/29/2013 11:59 AM, W K Daniel PUN wrote:
> Hi all,
>
> I got the following FAILED messages during the system booting and only
> understand the last FAILED message.  But the first two FAILED message
> still come up even the device is present.  Any possibilities to fix them?
>
> Bringing up loopback interface:  OK
> Bringing up interface Auto_CQURoam:  Device does not seem to be present,
> delaying initialization.   FAILED
> Bringing up interface Auto_cherub7:  Device does not seem to be present,
> delaying initialization.   FAILED
> Bringing up interface em1:
> Determining IP information for em1... failed; no link present.  Check
> cable?   FAILED

Your system thinks it has no network hardware connected (which may be 
the case). The Auto_* stuff is about wireless networks you have 
registered (the school's wifi at CQURoam and another one you've used 
called cherub7). The wireless ones might be trying to auto-connect in 
sequence and, if out of range, state they fail being not present -- 
someone else will have to confirm that behavior, but it seems likely.

Are you having a network problem, like you can't connect after booting 
up, or you're just seeing ugly-looking messages about network devices 
that aren't connected and wifi points that are out of range?

ATOM RSS1 RSS2