<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How to Fix Slow Fesity Boot For Laptops</title>
	<atom:link href="http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html</link>
	<description>Ubuntu Linux Tutorials,Howtos,Tips &#38; News &#124; Oneiric,Natty,Maverick</description>
	<lastBuildDate>Mon, 06 Feb 2012 15:40:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: donashish</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-5869</link>
		<dc:creator>donashish</dc:creator>
		<pubDate>Fri, 06 Feb 2009 18:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-5869</guid>
		<description>This worked wonders for me. earlier the boot process took about 80 sec. now its down to 35 sec!</description>
		<content:encoded><![CDATA[<p>This worked wonders for me. earlier the boot process took about 80 sec. now its down to 35 sec!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darwin</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1812</link>
		<dc:creator>Darwin</dc:creator>
		<pubDate>Tue, 01 Apr 2008 20:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1812</guid>
		<description>@admin, pedro: Never use :wq! to exit a vi(m) session.  If you&#039;ve opened the file read-only by accident (e.g. forgot to type sudo or something), or if there&#039;s an error saving your changes, you&#039;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&#039;s a problem, so you won&#039;t lose all your work.</description>
		<content:encoded><![CDATA[<p>@admin, pedro: Never use :wq! to exit a vi(m) session.  If you&#8217;ve opened the file read-only by accident (e.g. forgot to type sudo or something), or if there&#8217;s an error saving your changes, you&#8217;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&#8217;s a problem, so you won&#8217;t lose all your work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IMQ</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1811</link>
		<dc:creator>IMQ</dc:creator>
		<pubDate>Sun, 16 Sep 2007 19:51:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1811</guid>
		<description>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 &quot;dhcp&quot;. 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.</description>
		<content:encoded><![CDATA[<p>IMHO, the real lesson here is that all the network cards (wired and wireless) not in used should be commented out.</p>
<p>In the example from the article, all network cards are set to &#8220;dhcp&#8221;. 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.</p>
<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1810</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Wed, 12 Sep 2007 13:20:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1810</guid>
		<description>That was it. Comment out the wireless card and it boots in 30 secs.

Thanks</description>
		<content:encoded><![CDATA[<p>That was it. Comment out the wireless card and it boots in 30 secs.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1809</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Tue, 14 Aug 2007 20:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1809</guid>
		<description>Works wonders! I may put this on Launchpad as a bug, because it&#039;s as if NetworkManager just got dropped into the system, if you know what I mean.</description>
		<content:encoded><![CDATA[<p>Works wonders! I may put this on Launchpad as a bug, because it&#8217;s as if NetworkManager just got dropped into the system, if you know what I mean.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1808</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 14 Aug 2007 09:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1808</guid>
		<description>press
Esc button

type

:wq!

this will save your changes</description>
		<content:encoded><![CDATA[<p>press<br />
Esc button</p>
<p>type</p>
<p>:wq!</p>
<p>this will save your changes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pedro</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1807</link>
		<dc:creator>Pedro</dc:creator>
		<pubDate>Tue, 14 Aug 2007 07:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1807</guid>
		<description>Hi I am really a newby in the linux world. I was trying to edit the &#039;/etc/network/interfaces&#039;, using the command &#039;vi /etc/network/interfaces&#039;. I can make the changes but unfortunately I do not know how to save and exit from the file afterwards. Any Help?

Thanks</description>
		<content:encoded><![CDATA[<p>Hi I am really a newby in the linux world. I was trying to edit the &#8216;/etc/network/interfaces&#8217;, using the command &#8216;vi /etc/network/interfaces&#8217;. I can make the changes but unfortunately I do not know how to save and exit from the file afterwards. Any Help?</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Archibald</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1806</link>
		<dc:creator>Kevin Archibald</dc:creator>
		<pubDate>Tue, 14 Aug 2007 03:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1806</guid>
		<description>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 &quot;/etc/network/.interfaces.swp&quot;
          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 &quot;/etc/network/interfaces&quot;
             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?</description>
		<content:encoded><![CDATA[<p>OK explain this as you would to a complete newbie.</p>
<p>When i run this in the console it tells me:</p>
<p>E325: ATTENTION<br />
Found a swap file by the name &#8220;/etc/network/.interfaces.swp&#8221;<br />
          owned by: root   dated: Wed Jun 13 17:09:59 2007<br />
         file name: /etc/network/interfaces<br />
          modified: YES<br />
         user name: root   host name: kevin-laptop<br />
        process ID: 5444<br />
While opening file &#8220;/etc/network/interfaces&#8221;<br />
             dated: Sat Jun  2 17:42:38 2007</p>
<p>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?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1805</link>
		<dc:creator>Roy</dc:creator>
		<pubDate>Sat, 14 Jul 2007 10:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1805</guid>
		<description>Hello i am having trouble finding the network interfaces file can anyone help and what exactly do i do when iget there

HELP</description>
		<content:encoded><![CDATA[<p>Hello i am having trouble finding the network interfaces file can anyone help and what exactly do i do when iget there</p>
<p>HELP</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1804</link>
		<dc:creator>Matthew</dc:creator>
		<pubDate>Mon, 25 Jun 2007 15:34:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1804</guid>
		<description>This worked wonders for me.  My boot up time is now 70s</description>
		<content:encoded><![CDATA[<p>This worked wonders for me.  My boot up time is now 70s</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hammedhaaret</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1803</link>
		<dc:creator>hammedhaaret</dc:creator>
		<pubDate>Wed, 06 Jun 2007 00:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1803</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Hi&#8230; ive also had a problem with slow boot time and use another guide that did a bit different approach.</p>
<p>main thing is, that this will only work for laptops with long boot-time problems.<br />
its something with a bug that makes ubuntu look for too many network cards, thus the long boot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julius</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1802</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Tue, 05 Jun 2007 08:54:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1802</guid>
		<description>whenn will it not be* sigh</description>
		<content:encoded><![CDATA[<p>whenn will it not be* sigh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julius</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1801</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Tue, 05 Jun 2007 08:50:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1801</guid>
		<description>When will Xubuntu be affected by this?</description>
		<content:encoded><![CDATA[<p>When will Xubuntu be affected by this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan_U</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1800</link>
		<dc:creator>Jordan_U</dc:creator>
		<pubDate>Sun, 03 Jun 2007 22:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1800</guid>
		<description>If you are running Feisty you really shouldn&#039;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 &quot;work&quot;. 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&#039;s DHCP request, after a certain amount of time it times out and gives up and continues booting.



&quot;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. &quot;

Yes it does matter in fact, Xubuntu, unlike (k)Ubuntu does not use network-manager because network-manager does not yet work with XFCE&#039;s pannel, so since you are not connecting using network-manager you need to have your /etc/networking/interfaces configured.</description>
		<content:encoded><![CDATA[<p>If you are running Feisty you really shouldn&#8217;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 &#8220;work&#8221;. 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&#8217;s DHCP request, after a certain amount of time it times out and gives up and continues booting.</p>
<p>&#8220;I did not notice any speed up, and I couldn’t connect to my wireless network anymore (untill I undid the change).</p>
<p>Running Xubuntu, if that matters. &#8221;</p>
<p>Yes it does matter in fact, Xubuntu, unlike (k)Ubuntu does not use network-manager because network-manager does not yet work with XFCE&#8217;s pannel, so since you are not connecting using network-manager you need to have your /etc/networking/interfaces configured.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jaywee</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1799</link>
		<dc:creator>jaywee</dc:creator>
		<pubDate>Sun, 03 Jun 2007 18:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1799</guid>
		<description>I edit the file, but I don&#039;t notice speedup. perhaps just a little second (</description>
		<content:encoded><![CDATA[<p>I edit the file, but I don&#8217;t notice speedup. perhaps just a little second (</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Björn</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1798</link>
		<dc:creator>Björn</dc:creator>
		<pubDate>Sat, 02 Jun 2007 14:56:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1798</guid>
		<description>Wow! Works lika a charm! The boot time has bortherd me for weeks now.</description>
		<content:encoded><![CDATA[<p>Wow! Works lika a charm! The boot time has bortherd me for weeks now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bjarte</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1797</link>
		<dc:creator>Bjarte</dc:creator>
		<pubDate>Fri, 01 Jun 2007 18:03:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1797</guid>
		<description>I did not notice any speed up, and I couldn&#039;t connect to my wireless network anymore (untill I undid the change).

Running Xubuntu, if that matters.</description>
		<content:encoded><![CDATA[<p>I did not notice any speed up, and I couldn&#8217;t connect to my wireless network anymore (untill I undid the change).</p>
<p>Running Xubuntu, if that matters.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: egan</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1796</link>
		<dc:creator>egan</dc:creator>
		<pubDate>Thu, 31 May 2007 19:53:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1796</guid>
		<description>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).</description>
		<content:encoded><![CDATA[<p>Before : 1 minute and 15 seconds (Bios+Grub+GDM)</p>
<p>After : 1 minute and 14 seconds (Bios+Grub+GDM)</p>
<p>Conclusion : there is no improvement (the one second delta is in the error bar).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Libu</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1795</link>
		<dc:creator>Libu</dc:creator>
		<pubDate>Thu, 31 May 2007 17:03:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1795</guid>
		<description>/etc/network/interfaces configuration file is not used by network manager (which is used by default in fiesty). From the networkmanager doc:
&lt;i&gt;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.&lt;i&gt;</description>
		<content:encoded><![CDATA[<p>/etc/network/interfaces configuration file is not used by network manager (which is used by default in fiesty). From the networkmanager doc:<br />
<i>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.</i><i></i></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html/comment-page-1#comment-1794</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 31 May 2007 16:19:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.ubuntugeek.com/how-to-fix-slow-fesity-boot-for-laptops.html#comment-1794</guid>
		<description>i did this for my laptop and after rebooting wireless was connected normally</description>
		<content:encoded><![CDATA[<p>i did this for my laptop and after rebooting wireless was connected normally</p>
]]></content:encoded>
	</item>
</channel>
</rss>

