I recently rebuilt my MythTV DVR from Fedora 6 to KnoppMyth, using the latest KnoppMyth version (R5F27).

All of the hardware works except for my USB wifi adapter (Edimax EW-7318USg).

I was able to build, without errors, the open-source rt73 driver from http://rt2x00.serialmonkey.com (this is the driver I'd used successfully under Fedora 6).

But running "ifup wlan0" fails; it cannot connect to any access point under dhcp (it keeps trying, but times out with "dhcp offers not found" errors).

The frustrating thing is, if I run "iwlist wlan0 scan", it *does* return a list of local access points.

So at some level, the driver is working, but it cannot make a connection (I've tried this for both access points which required WEP and those that were open).

I also tried two other drivers: Edimax's own Linux driver (http://www.edimax.com/images/Image/Driv ... _0_4_0.zip) and the Windows drivers under ndiswrapper.

Both installed without errors, but modprobe gave me "unknown device" errors, so none of the ifconfig/iwconfig commands worked at all.

Does anyone have any experience with this USB device under KnoppMyth, or have any suggestions?

I managed to get it to work, using the instructions posted here: http://wiki.archlinux.org/index.php/RT73_Wireless and some tweaks of my own.

Basically, it came down to three things:

(1) Do not use the open-source driver from the rt2x00 project; instead, use the native Ralink driver

(2) After compiling, do not run 'make install'; instead, copy the modules and firmware manually

(3) Do not use the rt73sta.dat file to control the adapter; instead, use the standard ifconfig/iwconfig commands

I also found adding those control commands ("ifconfig rausb0 up; iwconfig rausb0 essid access_point_id key wep_key") inside /etc/network/interfaces didn't work, as the adapter simply would not connect the the specified access point at boot.

Adding those same commands plus "dhclient rausb0" in a custom boot script (akin to rc.local, but using the debian/knoppix equivalent http://www.debian.org/doc/FAQ/ch-custom ... ootscripts), however, did work.