Comment 3 for bug 770232

Thanks for the suggested workaround described above Mark. I may try this myself when I have more time. I cannot help feeling that you and I shouldn't have to be doing this though: Your device USB ID is different from mine and presumably there will be further users with different hardware who are also affected by this bug back lack the ability to track it back to here. I do not feel that it is right that we should be having to hack around with local config files, which will then of course sit outside any Ubuntu led update process in future, when there are working drivers available which should be enabled. One of the core strengths of Ubuntu is meant to be ease of use and working out of the box. This driver deprecation clearly fails here. If we consider the case of trying to use a live cd to fix an issue on the only computer available at a site then you or I would be stuck because we would be unable to get network connectivity to find out how to apply the fix needed to get network connectivity in the first place.
To me a fix would involve either
1) Re-enabling the deprecated driver until the hardware handling system catches up and can use the new driver
2) Updating the udev rules or whatever CENTRALLY to apply the appropriate driver module
3) Somehow aliasing the new driver to the old one so that it is loaded either way
I do not even know if the rt3070sta module will work with my hardware as I write this.