How does solid state hardware just die?
Dec. 5th, 2008 11:20 pm
After dinner I drove out to Frys and in an hour had a new 802.11g Linksys WAP54G up and running. I even reprogrammed it to use DHCPC so I won't have to scan the entire network looking for the damn thing next time, and told my DHCPC server to preserve its MAC-to-IP address across reboots. It has better security now. Yamaraashi-chan was having a nastier case of Internet withdrawl than either Omaha or I.
But how does this happen? Linksys WAPs are solid state. It's sat in our pantry for the past eight years (the last time I downloaded drivers for it, the most common version of Windows was 98!), quietly ticking away, doing its job. It has no fan, no hard drive, no moving parts at all. I've only updated the flash four or five times in its life. Why would it suddenly just keel over and die in the middle of a transaction like that?
no subject
Date: 2008-12-06 08:32 am (UTC)no subject
Date: 2008-12-06 08:38 am (UTC)no subject
Date: 2008-12-06 10:59 am (UTC)no subject
Date: 2008-12-06 03:53 pm (UTC)Like all good software geeks, just tell yourself "It's a hardware problem."
no subject
Date: 2008-12-07 12:29 am (UTC)no subject
Date: 2008-12-07 02:10 pm (UTC)Don't forget the interconnects!
Date: 2008-12-06 05:21 pm (UTC)http://nepp.nasa.gov/WHISKER/
http://www.electronicsproductionworld.com/articleView~idArticle~71680_173413417372008.html
no subject
Date: 2008-12-07 07:09 am (UTC)Fortunately you've only been breathing flux fumes
Date: 2008-12-07 07:37 am (UTC). png
no subject
Date: 2008-12-08 10:07 am (UTC)no subject
Date: 2008-12-09 01:56 am (UTC)no subject
Date: 2008-12-09 03:03 pm (UTC)no subject
Date: 2008-12-10 12:58 am (UTC)oh - use aluminum foil on top of the newspaper, or else squirt a bit of water on it. that will help keep down the static so you don't fry the electronics.
no subject
Date: 2008-12-10 09:25 am (UTC)Re: Fortunately you've only been breathing flux fumes
Date: 2008-12-09 01:46 am (UTC)Small form factors suck!
Date: 2008-12-09 02:02 am (UTC)As if that wasn't bad enough, the designers just specified some surface-mount capacitors that are only 0.002" x 0.001"! I can't even SEE those without magnification!
Re: Small form factors suck!
Date: 2008-12-09 03:13 pm (UTC)Re: Small form factors suck!
Date: 2008-12-10 12:51 am (UTC)Tip 2: get a soldering iron with temperature controls, and check the tip temperature before use with a calibrated three-wire thermometer. You can also get a Metcal station - they self-calibrate from line voltage. Never let it get above 700 F, even for huge components. A good soldering iron is expensive, but will pay for itself in reduced scrap. (note - I'm not following my own advice; my home soldering iron is a Radio Shack cheapie)
Re: Small form factors suck!
Date: 2008-12-10 09:29 am (UTC)DIE COSMIC RAYS! I HATES YOU!
Date: 2008-12-09 01:49 am (UTC)oooh! i HATE debugging those! especially when it isn't strong enough to actually cause permanent damage, and is just enough to cause a bit to change state.
Re: DIE COSMIC RAYS! I HATES YOU!
Date: 2008-12-09 03:17 pm (UTC)Re: DIE COSMIC RAYS! I HATES YOU!
Date: 2008-12-10 12:55 am (UTC)Re: DIE COSMIC RAYS! I HATES YOU!
Date: 2008-12-10 09:36 am (UTC)no subject
Date: 2008-12-06 11:11 am (UTC)no subject
Date: 2008-12-06 12:23 pm (UTC)--
* Or if the government censorbug finally had enough wit'cha.
no subject
Date: 2008-12-06 08:08 pm (UTC)no subject
Date: 2008-12-06 10:03 pm (UTC)Whenever I look at gear that "just died", the first thing I always look for is a bulging electrolytic capacitor. Those things just go pop. I even recall buying a motherboard where one of the marketing points on the box was that it used all-solid capacitors instead of electrolytic types.
In a a way it's all speculation - certainly the other commenters' posts are equally valid.
If you take the black box that is a wireless router and break it down into the major functional groups, you usually have a 5-port switch, with one port internally wired to the actual "router" portion, which in turn has another port to the wireless hardware. The software running on the router performs bridging between the wireless and wired LANS, provides services like DHCP and DNS relaying to the LAN side, and performs NAT between the router's LAN and WAN ports.
The WAP54G is similar in that it has a LAN port and a wireless port, and a cpu bridging the two. It seems pretty clear that something is preventing the CPU from finishing its initialisation of the lan port, or from doing anything to the WAN port. There's a strong chance that the LAN light is the hardware's power-on default, and the thing is completely brain-dead.
no subject
Date: 2008-12-07 05:31 am (UTC)Except you *know* that their eyes will glaze over the moment you give them any kind of technical explanation like those listed here.
Here's a better explanation: because your bridge cost $79.95, not $495. It has cheap components in it that will likely fail sooner than later. Your bridge lasted 8 years, and that's far beyond its useful lifetime. As you've noted, it's long past obsolete.
More than likely, one of those cheap components was a capacitor, as previously noted. It's also worth noting that to find and replace that component would cost more in labour than it would to replace the whole thing. Electronics are like that.
no subject
Date: 2008-12-07 09:28 am (UTC)I'm currently running a medium-priced NetGear WG302v2 WAP. So far it's been okay, although
trinsf insists it still drops connections to her laptop. I've never managed to work out how to diagnose the local WiFi neighborhood.
Parenthetically, I'm finding it harder and harder to find a WAP qua WAP. They all seem to be WAP plus router/firewall/DHCP server/cable modem/print server/espresso machine.