Nathan's Journal Help

Blogs » Nathan's Journal » Fixing Spiffy
Mon 09 of June, 2008 23:00 PDT

Fixing Spiffy

Tags:  geekiness

I finally got spiffy fixed up this weekend, mainly to get it out from under my desk and off my todo list (spiffy being our media PC that suffered a total hard disk failure nearly 2 years ago, and has never really recovered properly). The main difficulty has been getting it onto the wireless network - unfortunately linux support for wireless devices (other than orinoco and intel, which seem to be fairly stable) can still be a bit dicey.

Lessons learned:

  • There are multiple versions of the Linksys WUSB54G, which have wildly different chipsets, none of which are guaranteed to work out of the box under linux. Frankly, I'd still avoid USB wireless devices as much as possible.
  • Firmware updates sometimes actually include new features. In this case, the 1.2.x updates to the Netgear WG602v3 added what they call Client Bridge mode (ie, it bridges an ethernet segment to the primary AP, and doesn't accept wireless clients of its own). Oddly enough, this is largely why I originally bought the second one nearly two years ago. About darn time...
  • ATI no longer supports the Radeon 9200 in the fglrx driver. Fortunately the x.org ati driver now actually supports TV output quite well, and we don't need ATI's one any more.
  • The XC-Cube is old enough now that things like LIRC actually support its remote control out-of-the-box, without only a moderate amount of messing around with obscure configuration files.

On a completely unrelated point, does anyone want a nearly-new WUSB54Gv4? cool

And yes, I do still need to post some comments on Japan, sometime soon I promise...

About me

Nathan is a full-time software engineer and part-time maintainer of several pieces of open-source software that noone has even heard of (most notably lxdream and elr). His interests include programming language design, distributed systems, emulation, Japanese, and go.