Yes
No
Somewhat
| My old and mostly abandoned blog |
Linux user #413984 ; Ubuntu user #178
J'aime les fraises.
Nighty night me lovelies!
| Reinstalling Ubuntu ? Please check this bug first ! |
| Using a ppa ? Please install ppa-purge from universe, you may need it should you want to revert packages back |
| No support requests / username changes by PM, thanks. |[SIGPIC][/SIGPIC]
Recently upgraded from feisty to gutsy in the hope wireless would improve. I used to be able to get it to work in feisty by editing the interfaces file... but that doesn't work anymore.
I must admit I really don't know what compiling the latest 'ndiswrapper' involves...
Hi, I'm using a card with the rt2500 chipset on Feisty and I'll upgrade to Gutsy Gibbon as soon as the stable version comes out, but I have a question, why using ndiswrapper when these chipsets are supposed to be fully supported in Ubuntu? You mean they don't work very well in Gutsy? (Feisty's default driver is working like a charm here, in spite of the fact I'm using a smp kernel on a core 2 duo machine).
Yes, I edited my /etc/network/interfaces file to my like and my wireless connection is working like a charm here. Thanks for clarify this to me, I was getting scared about the idea of using ndiswrapper
I'm using feisty fawn and tried this tutorial, followed it step by step, and WICD still won't connect for me!
I'm using WEP if that makes any difference.
Maybe you should open a new topic since this one is related to Gutsy Gibbon? Anyway, if you're using WEP, then it's fairly easy to connect to your AP; simply go to 'System>Administration>Network', select the wireless interface and click on properties, enter your settings there, then click on accept, check the checkbox at the left of your wireless interface (on the main window) and it should work.
Bookmarks