Aug 09 2005

RealTek RTL8100S LAN on FreeBSD 5.4: no carrier

Tag: FreeBSD, Hardware, Techjs @ 10:00 pm

I just installed FreeBSD 5.4 on my Abit AA8-DuraMax, but I’ve run into some troubles with my networking. It seems that the on-board NIC doesn’t properly detect when a cable is plugged in. ifconfig shows it as “status: no carrier”

I know it’s not the router or the cable, because they both work fine on other machines. The 8100S chipset is listed as supported on the FreeBSD 5.4 Hardware compatibility list, as well as the man pages for the re driver.

Some other weirdness: If I plug the ethernet cable from the BSD machine to another machine’s NIC, it is properly detected. It only doesn’t detect when connected to my router. Also, if I manually set the card to 10baseT/UTP using ifconfig’s media parameter, it also works. It doesn’t work on autoselect, or any other media setting besides 10baseT/UTP.

Anyone have any ideas? Some info:

ifconfig:
————————————–
re0: flags=8843<up ,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=18<vlan_mtu ,VLAN_HWTAAGGING>
inet 192.168.1.31 netmask 0xffffff00 broadcast 192.168.1.255
inet6 …
ether 00:50:8d:eb:e5:be
media: Ethernet autoselect (none)
status: no carrier
lo0: flags=8049<up ,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0×4Relevant dmesg:
————————————–
re0: <realtek 8169S Single-chip Gigabit Ethernet> port 0xee00-0xeeff mem 0xfbfff000-0xfbfff0ff irc 16 at device 1.0 on pci1
miibus0: <mii bus> on re0
rgephy0: <rtl8169s /8110S media interface> on miibus0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
re0: Ethernet address: 00:50:8d:eb:e5:bepciconf -lv:
————————————–
re0@pci1:1:0: class=0×020000 card=0×1039147b chip=0×816910ec rev=0×10 hdr=0×00
vendor = ‘Realtek Semiconductor’
device = ‘RTL8169 Gigabit Ethernet Adapter’
class = network
subclass = ethernet

pciconf -r pci1:1:0 0:0xff
————————————–
816910ec 02b00007 02000010 00002008
0000ee01 fbfff000 00000000 00000000
00000000 00000000 00000000 1039147b
00000000 000000dc 00000000 40200110
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 f7c20001
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Apr 28 2005

iPod on Windows XP: Delayed Write Failed

Tag: Apple, Hardware, Tech, Windows, iPod/iTunesjs @ 11:00 am

Note: Be sure to read my Update to this post

When trying to update my shiny new iPod via iTunes on Windows XP, I kept getting the following error:

“Delayed Write Failed
Windows was unable to save all the data for the file x. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.”

The iPod would lockup and I’d have to reset it to get it to work again. After some research I found the cause: Write Caching was disabled on my hard disks. Because iTunes tries to push as much data as possible as quickly as possible, Windows was unable to keep up, resulting in the error.

To enable Write Caching on your hard disks:

Start > Control Panel > System > Device Manager > Disk Drives > Properties > Policies > Enable Disk Caching

Note that this option was unavailable to me (greyed out), and after some research I realized it was because I had the Intel Application Accelerator installed, which turns OFF write caching and prevents you from enabling it. So after a quick uninstall of Intel Application Accelerator and a quick reboot, I was able to enable Write Caching on my hard disks, and now the error is gone and my iPod is updating as expected.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Mar 02 2005

Nexus Memory Heatspreader Installation

Tag: Hardware, Techjs @ 4:24 pm

Nexus Memory Heatspreader
I’m in the process of “upgrading” my desktop, and part of that upgrade includes a cooling overhaul. My desktop is a loud bitch, and my goal was to cool it as best as possible… and more importantly, as silent as possible. As part of my plan to lower the case temperature and get rid of the front air intake fan (as recommended by AMD’s Cooling Guide), I decided to order some Nexus Memory Heatspreaders from EndPCNoise.com to cool my RAM.

Installing them seems easy enough, so easy in fact, that I ran into a few problems. :)

First, you must ensure that when sticking your RAM onto the adhesive tape, you line up the RAM exactly in the middle of the heatspreader casing. While this may seem blatantly obvious, even a slight millimeter deviation from center can cause problems when seating your RAM back into the motherboard socket. One of my RAM sticks was slightly off-center in the heatspreader, making it impossible to re-seat the stick. The overhanging edges of the heatspreader were preventing the RAM clip from properly locking into place and seating the RAM. I ended up having to use a pair of pliers to bend the overhanging part of the heatspreader to make it fit.

Second, do not seperate the two pieces of the heatspreader when sticking your RAM to it. The heatspreaders have a little hinge at the top, and in order to close the heatspreader over your RAM, there needs to be a slight bit of head room for the hinges to slide into place. I made the mistake of sticking one half of the heatspreader on my RAM first. I wrongly positioned the RAM flush up against the top of the heatspreader, but this prevented the other half of the heatspreader from clipping back on! Think of it as a 3-ring binder: if you put too many papers in the binder, the binder won’t fully close. I ended up having to attach only one hinge, and the other one (that wouldn’t slide into the other hinge) I had to bend up with a pair of pliers. The provided clips hold both sides of the heatspreader in place well, so I’m not too worried about it, but for a moment there I was worried that I’d have a RAM stick with only half of a heatspreader.

Finally, that adhesive tape is amazingly sticky. If you mess up placing it on your RAM, there’s no going back, so make sure you do it right the first time!

So let this be a lesson to you if you’re installing heatspreaders on your RAM - it may look like an easy no-brainer, but it actually requires quite a bit of attention.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

« Previous Page