May 31, 2007 · Networking · Email This Post

Sponsored Link
Feisty has a terrible boot time on laptops compared to server (roughly 3x as long) even though it is a faster computer. You can speedup your boot time from over a minute to roughly 30 seconds by doing the following

Edit the /etc/network/interfaces file using the following command

sudo vi /etc/network/interfaces

Now you need to comment out the wireless card (in this case eth1)

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

#auto eth1
#iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp

Save and exit the file.Now you should see the your feisty boot time should have been faster than before

Incoming search terms:

Related posts

22 Comments to “How to Fix Slow Fesity Boot For Laptops”

  1. Adyton says:

    Thanks a million dude… My Dell Precision M65 now boots 4-5 times faster (no kidding!!)

    Adyton

    [Reply]

  2. Ralph says:

    why should I comment out my wireless card on my laptop? that’s how I connect normally. Do you connect manually now?

    [Reply]

  3. admin says:

    i did this for my laptop and after rebooting wireless was connected normally

    [Reply]

  4. Libu says:

    /etc/network/interfaces configuration file is not used by network manager (which is used by default in fiesty). From the networkmanager doc:
    Network Manager has been installed on your system, however it will not immediately be able to manage your network interfaces. To avoid problems with important configuration being ignored, or strange behaviours, the Ubuntu version will not manage any network interface configured in the /etc/network/interfaces file.

    [Reply]

  5. egan says:

    Before : 1 minute and 15 seconds (Bios+Grub+GDM)

    After : 1 minute and 14 seconds (Bios+Grub+GDM)

    Conclusion : there is no improvement (the one second delta is in the error bar).

    [Reply]

  6. Bjarte says:

    I did not notice any speed up, and I couldn’t connect to my wireless network anymore (untill I undid the change).

    Running Xubuntu, if that matters.

    [Reply]

  7. Björn says:

    Wow! Works lika a charm! The boot time has bortherd me for weeks now.

    [Reply]

  8. jaywee says:

    I edit the file, but I don’t notice speedup. perhaps just a little second (

    [Reply]

  9. Jordan_U says:

    If you are running Feisty you really shouldn’t have your wireless card in your /etc/networking/interfaces in the first place, it should be non existent or commented out by default because otherwise network-manager will ignore your wireless interface and therefore not “work”. What is probably happening is that your wireless SSID is not set in your /etc/networking/interfaces so when it tries to connect it hangs waiting ( without any chance of getting ) for a reply for it’s DHCP request, after a certain amount of time it times out and gives up and continues booting.

    “I did not notice any speed up, and I couldn’t connect to my wireless network anymore (untill I undid the change).

    Running Xubuntu, if that matters. ”

    Yes it does matter in fact, Xubuntu, unlike (k)Ubuntu does not use network-manager because network-manager does not yet work with XFCE’s pannel, so since you are not connecting using network-manager you need to have your /etc/networking/interfaces configured.

    [Reply]

  10. Julius says:

    When will Xubuntu be affected by this?

    [Reply]

  11. Julius says:

    whenn will it not be* sigh

    [Reply]

  12. hammedhaaret says:

    Hi… ive also had a problem with slow boot time and use another guide that did a bit different approach.

    main thing is, that this will only work for laptops with long boot-time problems.
    its something with a bug that makes ubuntu look for too many network cards, thus the long boot.

    [Reply]

  13. Matthew says:

    This worked wonders for me. My boot up time is now 70s

    [Reply]

  14. Roy says:

    Hello i am having trouble finding the network interfaces file can anyone help and what exactly do i do when iget there

    HELP

    [Reply]

  15. Kevin Archibald says:

    OK explain this as you would to a complete newbie.

    When i run this in the console it tells me:

    E325: ATTENTION
    Found a swap file by the name “/etc/network/.interfaces.swp”
    owned by: root dated: Wed Jun 13 17:09:59 2007
    file name: /etc/network/interfaces
    modified: YES
    user name: root host name: kevin-laptop
    process ID: 5444
    While opening file “/etc/network/interfaces”
    dated: Sat Jun 2 17:42:38 2007

    then if i say replace or restore or any option, once i get into the file, every keypress brings up a strange character, not the one I push. Trying to navigate to this file in GNOME and editing it from there brings up rights issues. ANyone want to save my wall from another forehead mark?

    [Reply]

  16. Pedro says:

    Hi I am really a newby in the linux world. I was trying to edit the ‘/etc/network/interfaces’, using the command ‘vi /etc/network/interfaces’. I can make the changes but unfortunately I do not know how to save and exit from the file afterwards. Any Help?

    Thanks

    [Reply]

  17. admin says:

    press
    Esc button

    type

    :wq!

    this will save your changes

    [Reply]

  18. Thomas says:

    Works wonders! I may put this on Launchpad as a bug, because it’s as if NetworkManager just got dropped into the system, if you know what I mean.

    [Reply]

  19. Tony says:

    That was it. Comment out the wireless card and it boots in 30 secs.

    Thanks

    [Reply]

  20. IMQ says:

    IMHO, the real lesson here is that all the network cards (wired and wireless) not in used should be commented out.

    In the example from the article, all network cards are set to “dhcp”. This means that the system will try to obtain an IP address for ALL the cards listed until timed out, causing a long delay when booting.

    Sometime ago, I discovered this when I was observing the boot process in the console mode and noticed a long delay when the system was trying to obtain an IP address for the 2nd Ethernet port on the motherboard, which is not connected to an Ethernet cable. I went in and commented out (basically disabled the port) and rebooted. Voila! The system skipped the 2nd Ethernet port and before I knew it, I was at the logon screen.

    [Reply]

  21. Darwin says:

    @admin, pedro: Never use :wq! to exit a vi(m) session. If you’ve opened the file read-only by accident (e.g. forgot to type sudo or something), or if there’s an error saving your changes, you’ll never know, because appending the ! makes vi quit no matter what. Instead, use just :wq or type ZZ. Neither of these options will exit if there’s a problem, so you won’t lose all your work.

    [Reply]

  22. donashish says:

    This worked wonders for me. earlier the boot process took about 80 sec. now its down to 35 sec!

    [Reply]

Leave a Reply