Re: F10 not connected at start up -

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2009-03-11 at 15:12 -0400, Bob Goodwin wrote:
> Craig White wrote:
> > On Wed, 2009-03-11 at 14:34 -0400, Bob Goodwin wrote:
> >   
> >> I have an F-10 box that does not connect at boot.  I believe network 
> >> manager is completely disabled.  It starts in text mode, I enter startx.
> >>
> >> Fortunately I usually only boot it once a day at the most but it is a 
> >> bother.  I start it as 'bobg' and it wants a password [more than a dozen 
> >> characters], Then since it's not connected 'firestarter' isn't running 
> >> and it too wants a password, but since it's not connected 'firestarter' 
> >> wont start until I bring up system-config-network to activate the 
> >> connection, but first it wants a password, once that is down I can go to 
> >> the firestarter menu and start it.
> >>
> >> This is beginning to bother me and I know it must be something I have 
> >> misconfigured but haven't found it yet.  It just asked for some security 
> >> updates and I told it ok, enter the password again.  That's four times 
> >> in a few minutes and I haven't asked the computer to do any work yet!
> >>
> >> Any suggestions?
> >>     
> > ----
> > the default is to have NetworkManager service on and 'network' service
> > off and also to boot runlevel 5 so clearly you have been changing things
> > since the original installation.
> >
> > You might want to ensure that 'network' service is set to automatically
> > start at your runlevel (you don't say which boot level you are
> > setting)...
> >
> > chkconfig --list network
> >
> > and I would presume if you are booting runlevel 3, which is supposed to
> > have networking turned on by default, the above should show 'on' for
> > runlevel 3.
> >
> > if not, execute either
> >
> > chkconfig --levels 2345 network on # very explicit
> > or
> > chkconfig network on # less explicit, uses /etc/init.d/network
> >                      # chkconfig statement to determine
> >
> > You might want to do similar for 'Firestarter' service to ensure it too
> > is automatically started at boot up.
> >
> > Craig
> >
> >
> >   
> 
> Both network and firestarter are on for 2345, off for the others.
----
I would expect that if this is the case and there were a problem with
them starting during bootup, that /var/log/messages would indicate the
problem.

Craig

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux