<?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: HowTo: Uninstall software that makes Ubuntu&#8217;s boot process fail</title>
	<atom:link href="http://www.serenux.com/2009/02/howto-uninstall-software-that-makes-ubuntus-boot-process-fail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.serenux.com/2009/02/howto-uninstall-software-that-makes-ubuntus-boot-process-fail/</link>
	<description>Life, the Universe and Ubuntu.</description>
	<lastBuildDate>Wed, 18 Jan 2012 12:38:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: HyRax</title>
		<link>http://www.serenux.com/2009/02/howto-uninstall-software-that-makes-ubuntus-boot-process-fail/comment-page-1/#comment-71</link>
		<dc:creator>HyRax</dc:creator>
		<pubDate>Tue, 24 Feb 2009 04:45:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.serenux.com/?p=438#comment-71</guid>
		<description>No, the issue wasn&#039;t the hardware, it was the software itself. In this case, ndiswrapper didn&#039;t like the Windows driver and borked itself. Turning off the adapter would not have fixed the problem because ndiswrapper would have still loaded the driver, thus my aim was to prevent ndiswrapper from loading the driver. Since I wasn&#039;t using ndiswrapper for anything else, the easy solution was just to uninstall ndiswrapper.

I could have simply loaded up the LiveCD, gone into /etc/ndiswrapper on the lappy and deleted the Windows driver, thus causing ndiswrapper to do nothing more than error out and quit, but there was a good opportunity for a tutorial, so I did it the chroot way. :)</description>
		<content:encoded><![CDATA[<p>No, the issue wasn&#8217;t the hardware, it was the software itself. In this case, ndiswrapper didn&#8217;t like the Windows driver and borked itself. Turning off the adapter would not have fixed the problem because ndiswrapper would have still loaded the driver, thus my aim was to prevent ndiswrapper from loading the driver. Since I wasn&#8217;t using ndiswrapper for anything else, the easy solution was just to uninstall ndiswrapper.</p>
<p>I could have simply loaded up the LiveCD, gone into /etc/ndiswrapper on the lappy and deleted the Windows driver, thus causing ndiswrapper to do nothing more than error out and quit, but there was a good opportunity for a tutorial, so I did it the chroot way. <img src='http://www.serenux.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SyntaxTerror</title>
		<link>http://www.serenux.com/2009/02/howto-uninstall-software-that-makes-ubuntus-boot-process-fail/comment-page-1/#comment-70</link>
		<dc:creator>SyntaxTerror</dc:creator>
		<pubDate>Tue, 24 Feb 2009 04:36:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.serenux.com/?p=438#comment-70</guid>
		<description>Would turning off the WLAN adapter in the BIOS stop the driver from loading at startup?

Are there any ways you could pass the kernel an argument of what it should and shouldn&#039;t load?  I&#039;ve never really played around with passing arguments to the kernel, but I assume there would be something to achieve this.</description>
		<content:encoded><![CDATA[<p>Would turning off the WLAN adapter in the BIOS stop the driver from loading at startup?</p>
<p>Are there any ways you could pass the kernel an argument of what it should and shouldn&#8217;t load?  I&#8217;ve never really played around with passing arguments to the kernel, but I assume there would be something to achieve this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

