Fedora Linux Support Community & Resources Center
  #1  
Old 2nd March 2012, 10:54 PM
dom107 Offline
Registered User
 
Join Date: Feb 2012
Location: France
Posts: 6
windows_7firefox
F16 Boot time OK... unless when network not connected

Hello,

Fedora 16 is installed on a netbook.

The boot time is OK unless the network is not connected.
It takes an additional minute when the network is not connected.

Using manual IP address doesn't change this.

Thanks in advance for ideas on this.
Reply With Quote
  #2  
Old 3rd March 2012, 12:30 PM
lightman47 Online
Registered User
 
Join Date: Apr 2009
Location: central NY, USA
Posts: 592
linuxfirefox
Re: F16 Boot time OK... unless when network not connected

I experience this when fstab tries to mount {not connetced} network drives. Once they time-out, boot proceeds normally. For me the delay is acceptable because it's fairly rare when I am not connected to my network. Not sure if your case is the same.
Reply With Quote
  #3  
Old 3rd March 2012, 02:18 PM
marko Online
Registered User
 
Join Date: Jun 2004
Location: Laurel, MD USA
Posts: 6,050
linuxfirefox
Re: F16 Boot time OK... unless when network not connected

Try running:
Quote:
systemd-analyze blame
to show the list of times per service, see which one is the long one in the listing at the top. Remember that the times don't necessarily occur in serial order, some of the times 'hide' other times:
Code:
------- service 1
     ------ service 2
              --------service 3
                 ----- service 4
and so on, so the boot time isn't as large as the total of all the listed times
Reply With Quote
  #4  
Old 3rd March 2012, 03:35 PM
dom107 Offline
Registered User
 
Join Date: Feb 2012
Location: France
Posts: 6
linuxfirefox
Re: F16 Boot time OK... unless when network not connected

systemd-analyze blame doesn't show much difference w/ or without network... So it must be in a step before...
Code:
With network                                                    Without network
10409ms        var-lib-nfs-rpc_pipefs.mount                          9542ms         var-lib-nfs-rpc_pipefs.mount
9733ms         fedora-loadmodules.service                            9521ms         media.mount
8772ms         systemd-vconsole-setup.service                        9451ms         dev-mqueue.mount
6318ms         media.mount                                           9439ms         sys-kernel-debug.mount
6282ms         dev-mqueue.mount                                      9436ms         dev-hugepages.mount
6267ms         sys-kernel-debug.mount                                9396ms         sys-kernel-security.mount
6250ms         dev-hugepages.mount                                   9229ms         fedora-loadmodules.service
6241ms         udev-settle.service                                   8525ms         remount-rootfs.service
6234ms         sys-kernel-security.mount                             6211ms         systemd-vconsole-setup.service
6096ms         udev-trigger.service                                  6180ms         udev-settle.service
5913ms         remount-rootfs.service                                5698ms         sys-kernel-config.mount
3883ms         fedora-readonly.service                               5661ms         udev-trigger.service
3460ms         sys-kernel-config.mount                               4091ms         systemd-sysctl.service
2903ms         mdmonitor-takeover.service                            3822ms         mdmonitor-takeover.service
2692ms         udev.service                                          3287ms         udev.service
2067ms         systemd-remount-api-vfs.service                       2757ms         systemd-remount-api-vfs.service
1969ms         iscsi.service                                         2157ms         plymouth-start.service
1934ms         sendmail.service                                      1404ms         iscsid.service
1672ms         iscsid.service                                        1400ms         fedora-storage-init.service
1270ms         systemd-sysctl.service                                1167ms         NetworkManager.service
1228ms         NetworkManager.service                                1055ms         nfs-lock.service
1005ms         fedora-storage-init.service                           998ms          systemd-readahead-collect.service
917ms          netfs.service                                         977ms          systemd-readahead-replay.service
800ms          nfs-lock.service                                      935ms          netfs.service
680ms          ip6tables.service                                     810ms          fedora-readonly.service
631ms          console-kit-log-system-start.service                  684ms          ip6tables.service
629ms          avahi-daemon.service                                  660ms          fedora-storage-init-late.service
595ms          iptables.service                                      646ms          sendmail.service
556ms          systemd-readahead-collect.service                     587ms          iptables.service
553ms          rsyslog.service                                       579ms          sm-client.service
544ms          fedora-storage-init-late.service                      575ms          boot.mount
542ms          systemd-logind.service                                571ms          console-kit-log-system-start.service
538ms          systemd-readahead-replay.service                      530ms          avahi-daemon.service
533ms          sshd-keygen.service                                   510ms          livesys.service
523ms          livesys.service                                       504ms          rsyslog.service
453ms          abrt-ccpp.service                                     488ms          systemd-logind.service
446ms          mcelog.service                                        440ms          sshd-keygen.service
436ms          auditd.service                                        432ms          mcelog.service
429ms          irqbalance.service                                    421ms          auditd.service
415ms          rtkit-daemon.service                                  420ms          fcoe.service
372ms          sm-client.service                                     417ms          irqbalance.service
366ms          acpid.service                                         360ms          nfs-idmap.service
353ms          fcoe.service                                          350ms          acpid.service
283ms          systemd-tmpfiles-setup.service                        339ms          abrt-ccpp.service
262ms          sandbox.service                                       309ms          systemd-tmpfiles-setup.service
246ms          nfs-idmap.service                                     246ms          sandbox.service
239ms          lvm2-monitor.service                                  217ms          abrt-vmcore.service
230ms          home.mount                                            214ms          lvm2-monitor.service
215ms          abrt-vmcore.service                                   196ms          home.mount
166ms          dbus.service                                          186ms          dbus.service
115ms          fedora-wait-storage.service                           118ms          fedora-wait-storage.service
109ms          boot.mount                                            110ms          rpcbind.service
90ms           rpcbind.service                                       80ms           rtkit-daemon.service
68ms           livesys-late.service                                  58ms           livesys-late.service
59ms           console-kit-daemon.service                            56ms           console-kit-daemon.service
14ms           systemd-user-sessions.service                         19ms           systemd-user-sessions.service
Reply With Quote
  #5  
Old 8th March 2012, 08:14 PM
japafi Offline
Registered User
 
Join Date: Mar 2010
Posts: 87
linuxfirefox
Re: F16 Boot time OK... unless when network not connected

Do you have network service enabled? It may cause delay and not needed as NetworkManager is handling the connectivity.
Reply With Quote
  #6  
Old 9th March 2012, 07:11 AM
IonIvan Offline
Registered User
 
Join Date: Oct 2011
Posts: 8
linuxfirefox
Re: F16 Boot time OK... unless when network not connected

I've got the same problem.
BTW, NetworkManager is disabled and I use network.service because NM will never work as I want him to.
Reply With Quote
  #7  
Old 9th March 2012, 09:35 AM
dom107 Offline
Registered User
 
Join Date: Feb 2012
Location: France
Posts: 6
windows_7firefox
Re: F16 Boot time OK... unless when network not connected

Quote:
Originally Posted by japafi View Post
Do you have network service enabled? It may cause delay and not needed as NetworkManager is handling the connectivity.
Hello,
From the above output of "systemd-analyze blame", I see that NetworkManager.service is enabled but I don't see any "network.service".
Reply With Quote
  #8  
Old 12th April 2012, 08:23 AM
safulop Offline
Registered User
 
Join Date: Jun 2008
Posts: 83
windows_7firefox
Re: F16 Boot time OK... unless when network not connected

Yes this is most definitely a F16 problem. My laptop has this delay even in wifi range; the last boot step reports wlan not connected, but it doesn't even try. It picks up the connection just fine when it finally boots. When plugged into ethernet the problem goes away because the eth0 connection is noticed.

I regard this as a bug.
Reply With Quote
Reply

Tags
boot, connected, f16, network, time

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
I'm connected and using the network but NM thinks I'm not... renichms Servers & Networking 2 25th September 2008 03:13 PM
Connected to wireless network (none) in F9 rose0500 Servers & Networking 10 21st May 2008 12:18 AM
How to disable network searching at boot time adarsh Servers & Networking 2 12th September 2007 03:50 AM
How can I get my PCMCIA network card to work at boot time on Fedora C2? lothario Hardware & Laptops 11 4th April 2007 02:58 AM
Network connected, no internet microslave Servers & Networking 13 6th September 2006 05:20 AM


Current GMT-time: 23:39 (Wednesday, 17-09-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat