<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sérgio's blog &#187; Hardware</title>
	<atom:link href="http://www.smachado.com/category/hardware/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.smachado.com</link>
	<description>About computers, software, gadgets, programming and more....</description>
	<lastBuildDate>Sun, 16 May 2010 20:40:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>No link light while connecting to network</title>
		<link>http://www.smachado.com/2009/09/no-link-light-while-connecting-to-network/</link>
		<comments>http://www.smachado.com/2009/09/no-link-light-while-connecting-to-network/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 21:57:31 +0000</pubDate>
		<dc:creator>smachado</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://www.smachado.com/?p=115</guid>
		<description><![CDATA[I got a new laptop to work with and noticed that if I plugged a network cable into it to connect to certain networks sometimes it worked sometimes it didn&#8217;t &#8211; I couldn&#8217;t even see a link light at the socket.
I thought this would be a driver issue of the laptop so I was ready [...]]]></description>
			<content:encoded><![CDATA[<p>I got a new laptop to work with and noticed that if I plugged a network cable into it to connect to certain networks sometimes it worked sometimes it didn&#8217;t &#8211; I couldn&#8217;t even see a link light at the socket.</p>
<p>I thought this would be a driver issue of the laptop so I was ready to find a new driver for this network card.</p>
<p>So I opened Control Panel and System Properties. Then I clicked the Hardware tab and opened Device Manager.</p>
<p>At Device Manager I expanded Network Adapters tab and selected the ethernet controller of my laptop. I right clicked it and opened the properties window. My initial purpose was to find the driver version but I started looking at the settings.</p>
<p>So I selected the Advanced tab and eventually Speed &amp; Duplex. Wait.. why is it set to 100 Mb Full? Hummm&#8230;. let me change that to Auto. Bingo&#8230; After applying the change I got a 1.0Gbs connection&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.smachado.com/2009/09/no-link-light-while-connecting-to-network/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>CentOS 4.2 and nforce drivers (forcedeth issue)</title>
		<link>http://www.smachado.com/2008/12/centos-42-and-nforce-drivers-forcedeth-issue/</link>
		<comments>http://www.smachado.com/2008/12/centos-42-and-nforce-drivers-forcedeth-issue/#comments</comments>
		<pubDate>Sat, 27 Dec 2008 13:23:11 +0000</pubDate>
		<dc:creator>Sergio</dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://www.smachado.com/?p=11</guid>
		<description><![CDATA[Today I had to install CentOS 64 bit on a desktop built on an ASUS P5N32-E SLI motherboard. This motherboard features a nForce 680i SLI chipset and other fancy stuff that are likely to cause trouble to Linux distributions, specially old versions.
I decided to go for CentOS 4.2 just because I had it available on [...]]]></description>
			<content:encoded><![CDATA[<p>Today I had to install CentOS 64 bit on a desktop built on an <a title="ASUS P5N32-E SLI motherboard" href="http://www.asus.com/products.aspx?modelmenu=1&amp;model=1459&amp;l1=3&amp;l2=11&amp;l3=397" target="_blank">ASUS P5N32-E SLI motherboard</a>. This motherboard features a nForce 680i SLI chipset and other fancy stuff that are likely to cause trouble to Linux distributions, specially old versions.</p>
<p>I decided to go for CentOS 4.2 just because I had it available on a DVD from a magazine, it was 64-bit and as an entreprise distribution it should be stable.</p>
<p>Installation was straightforward although I had to specify the drivers to use for hard disk (sata_nv) just before it started.</p>
<p>Upon login into my new installation I noticed I didn&#8217;t had any ethernet interfaces configured. This motherboard has two gigabit ethernet interfaces. They should use forcedeth driver from nvidia but they&#8217;re not working. Loading forcedeth manually didn&#8217;t do it . Also using options msi=0 msix=0 also didn&#8217;t do it.</p>
<p>So I decided to download the most recent kernel package for CentOS 4 which is kernel-smp-2.6.9-78.0.8.EL.x86_64.rpm. I downloaded from another computer to an usb stick and copied over to my CentOS 4 host. Then as root I executed the command: <em>rpm -i  kernel-smp-2.6.9-78.0.8.EL.x86_64.rpm</em> and rebooted.</p>
<p>After booting using the new kernel the system was able to find my ethernet devices. Aditionally it also found my onboard sound card.</p>
<p>After configuring them I was able to get network on my new system.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.smachado.com/2008/12/centos-42-and-nforce-drivers-forcedeth-issue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
