![[info]](http://l-stat.livejournal.com/img/userinfo.gif){kind=small}
I upgraded to Ubuntu Intrepid Ibex last night and now I can't connect to any WPA2 Enterprise networks. Unencrypted works fine, but the school's WPA2 APs seem to be more pervasive.
This issue seems to be happening to a lot of people so I'm hoping someone is working on it. That's the best thing about open source -- if something bothers you about the software you can change it yourself. Unfortunately this problem isn't in my area of expertise and I have plenty of programming to do for a project of my own.
I should have waited at least a month after the release to upgrade instead of jumping right in. New builds always have some serious problems that have to be worked out. I hear on message boards that new vehicle models and redesigns of old ones are prone to all kinds of quirks during the first model year. It's best to wait until the second year to buy one so all the issues can be worked out. The same seems to go with electronics -- the first iPhone had no GPS and a terrible 2G data connection, while the second version fixed these issues. And, of course, this quirkiness happens with software. Windows XP was a mess when it first came out and Vista was worse when it came to drivers and stability. XP is stable today (arguably), but Vista still has its problems.
Early adopters pay a high premium to get a product with limited functionality along with some unwanted side effects. As I sometimes forget, it's best to wait until the problems have been worked out and the price comes down (if it's not free software). Usually new and improved features get added in as the bugs get worked out.
So now I'm not even sure if I can drag my laptop around campus until this issue gets worked out. Serves me right for just following the appeal of something new, but not necessarily better.
This issue seems to be happening to a lot of people so I'm hoping someone is working on it. That's the best thing about open source -- if something bothers you about the software you can change it yourself. Unfortunately this problem isn't in my area of expertise and I have plenty of programming to do for a project of my own.
I should have waited at least a month after the release to upgrade instead of jumping right in. New builds always have some serious problems that have to be worked out. I hear on message boards that new vehicle models and redesigns of old ones are prone to all kinds of quirks during the first model year. It's best to wait until the second year to buy one so all the issues can be worked out. The same seems to go with electronics -- the first iPhone had no GPS and a terrible 2G data connection, while the second version fixed these issues. And, of course, this quirkiness happens with software. Windows XP was a mess when it first came out and Vista was worse when it came to drivers and stability. XP is stable today (arguably), but Vista still has its problems.
Early adopters pay a high premium to get a product with limited functionality along with some unwanted side effects. As I sometimes forget, it's best to wait until the problems have been worked out and the price comes down (if it's not free software). Usually new and improved features get added in as the bugs get worked out.
So now I'm not even sure if I can drag my laptop around campus until this issue gets worked out. Serves me right for just following the appeal of something new, but not necessarily better.