[Bug 78037] Re: rt2500 in feisty: problem solution
Filed upstream. Sorry, LP fooled me with deluge. ** Bug watch added: GNOME Bug Tracker #429419 http://bugzilla.gnome.org/show_bug.cgi?id=429419 ** Also affects: deluge (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=429419 Importance: Unknown Status: Unknown ** Also affects: network-manager (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=429419 Importance: Unknown Status: Unknown ** Changed in: deluge (upstream) Importance: Unknown = Undecided Bugwatch: GNOME Bug Tracker #429419 = None Status: Unknown = Unconfirmed ** Changed in: deluge (upstream) Status: Unconfirmed = Rejected ** Summary changed: - rt2500 in feisty: problem solution + many cards need to be downed for changing essid -- many cards need to be downed for changing essid https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
This looks like the same as bug 104414 And no kiwimanager also does not work until after the wifi interface is either manually reset or reset via wlassistant. PS I like the kiwimanager interface more than knetworkmanager, but the results are the same. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Patrick: What do you use to configure your wireless card now? Please include a KDE alternative, since I'm a Kubuntu fan ;) -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
After completely uninstalling network-manager, all problems solved, the card works nicelly. By the way, network manager isn't part of the ubuntu-desktop metapackage anymore -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
It's possible to get the rt2500 working with NetworkManager via ndiswrapper. You just need to find a copy of rt2500.sys and rt2500.inf and use ndiswrapper to install them. A gigantic hack, but good if you're desperate to get NetworkManager working. Of course NetworkManager and ndiswrapper have their own set of issues (bug # 85468). -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
My WUSB54G v4 from ebay uses the rt2500 chipset and driver and doesn't connect to WPA in Feisty; I get a pop-up saying requires security capabilities unsupported by your hardware. The more recent (still in stores) WUSB54GC also uses rt2500. It's so unfortunate. rt2500 is completely free software and highly recommended for Linux (both from the FSF, ubuntu wiki, and Ralink's home page: http://www.ralinktech.com/ralink/Home/Support/Linux.html ) and there's still this monumental problem with it and network-manager-gnome. I can even get the Intel wireless cards and their firmware to work out of the box in Feisty easily but not rt2500. Maybe Im just seeing a problem where it doesn't exist but I wonder why so much time was spent with making binary blobs easy to use in Feisty and yet free hardware isn't supported. Of course I'm under no illusions it can be fixed easily, as Feisty will be frozen in a few days, but just a comment. As another workaround, I've heard on the Ubuntu forums that some other wireless managers in Synaptic can deal with it, but still network- manager-gnome is the default and supposed to be the big draw in Feisty...there's a whole thread devoted to this issue in the Feisty Fawn Discussion forum as well, with people who's wireless worked pre-Feisty and now doesn't due to network-manager/the driver not supporting the extensions talked about in the link norberto posted. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I can also confrim this bug. This card worked out of the box in edgy and dapper. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Yes, rt2500 is very free software friendly, but that does not automatically unfortunately mean that the drivers would be top-notch. The current problem is, that only the so called Legacy BETA drivers work reliably, but they don't support features needed by network-manager. On the other hand, the rt2x00 driver, which should replace all the current rt2400/rt2500/rt2570/rt61/rt73 drivers, is not yet stable. So basically the whole WLAN situation on Linux is a bit unfortunate, with some chipsets not working at all, most requiring non-free firmware blobs to be included in the distribution, and even the few potentially fully free solutions do not have good enough drivers. Plus the fact that kernel side things are a bit fluctuating. But as always, things are improving - with the DeviceScape WLAN framework in kernel finally approaching, and many drivers finally maturing (like rt2x00, broadcom, zd1211rw), I'd finally see Ubuntu 7.10 to have chances to have relatively nice support out of the box for also other cards besides Intel's, albeit it requires those firmware files still for most cards other than rt2x00. In Ubuntu 7.04, I have my ZD1211-based card now finally working with the default zd1211rw driver rewritten from scratch by the community. Also some of the Broadcom users are reporting they can now use the GPL driver instead of ndiswrapper hack. Granted both of those need the firmware files, but still requiring firmwares is a lesser harm than something non-free running on the computer CPU itself. That said, Ubuntu really should use the 1.1.0-b4 + patches driver (ie. latest legacy driver for rt2500) that Debian also uses, from http://packages.qa.debian.org/r/rt2500.html . It works reliably, but just needs that network manager is not used (AFAIK). Probably no-one in the Ubuntu core team has devoted enough though to this matter, and the fact that network manager was decided to enable by default complicates things. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Note that I'm not completely certain about whether rt2x00 could actually work for rt2500 cards, including network-manager / WPA2 support. Debian has some version of also rt2x00 (CVS 20070219 + patches), and apparently some people are having success with it http://packages.qa.debian.org/r/rt2x00.html. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) = Tollef Fog Heen Target: None = ubuntu-7.04 -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Confirming this bug with RT2500 using a Belkin F5D7000 wireless card (worked on Edgy). Can't set ESSID while interface is up. Workaround described above works for me but I have to restart networking. sudo ifconfig ra0 down sudo iwconfig ra0 essid xyz key 12345 sudo ifconfig ra0 up sudo /etc/init.d/networking restart then I put everything in rc.local -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I agree with davegod75. This should be upgraded in priority. Once all of the people who only run stable versions upgrade to Feity final, they'll be very upset when their wireless cards stop working. Please don't go final with this huge bug still lingering. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Bug #99597 NetworkManager detects networks but does not connect (RaLink 2500) seems to be a dublicate of this bug. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I have been bitten by the Atheros wireless problems that appeared with Dapper. Three computers of mine crashed constantly. After many months passed by and the bug was still not fixed, I bought three new Ralink cards because of the Free drivers. And now with the upcoming Feisty, the wireless problems seem to resurface for me. I am really tired of this situtation. -- rt2500 in feisty: problem solution https://bugs.launchpad.net/bugs/78037 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I can confirm this bug as well. I have dlink DWL-G122 ver.B1. rt2500usb. It can see the network but it shows 0% strength and I cannot connect. Developers any word on a fix for this?? Will it make it before the final? Also, i think the importance of this should be upped to high since it affects so many people. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I have the same problems described in the description with my rt2500, I use an unsecured network and network-manager sees my ESSID but can't connect. To get my wireless working I had to sudo ifdown ra0 sudo nano /etc/network/interfaces -type in my network info on ra0 sudo ifup ra0 No everytime I reboot I just need to do a simple sudo ifdown ra0 and sudo ifupra0, my wireless then works but network-manager is still unusable. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Same here. Mobo the dreaded K8 Combo - Z. Feisty Beta. Workaround by hand seems to do the trick. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Same problem here, using a wireless nic Asus WL-107g. I bought this nic cause it was recommended by the Free Software Foundation as there is a fully free driver (no binary blob required). http://www.fsf.org/resources/hw/net/wireless/cards.html It would be really pity if this bug cannot be resolved in the final Feisty. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Same here. My Conceptronic C54..?... PCI card based on the RT2500 chipset from RaLink worked out of the box on ubuntu edgy. I just had to type my WEP-Key into the network-admin - what a feeling... On the Feisty Beta Live CD the device is recognised as ra0 like on edgy before and network manager find all wlan networks in the envoirnment, but I was not able to get a working WEP or nonkey connection with the old school network-admin or iwconfig etc. nor by deleting all devices from /etc/network/interfaces (expect lo) and using the new network manager. networking manager asked me for wep-key, I type it then the network manager animation goes with the tooltip waiting for wepkey... waiting... waiting... no connection. it seems to me that there is a connection but no it doesn't get an IP over DHCP. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
That's bad news norberto. No way Feisty can go final with this huge hardware problem! -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Bad news guys. I have new information and I'm updating my last post. It's not a bug. As you can see at: http://live.gnome.org/NetworkManagerHardware rt2500 drivers supports unencrypted and WEP networks when used with NetworkManager. While the driver supports WPA, it does not use Linux Wireless Extensions for WPA support, which is required for NetworkManager. I make some test and the drivers work fine in old fashion way without NetworkManager. Good luck next time... -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I have the same problem in Festy beta. Try to boot without X and the rt2500 work fine. Workaround also works for me. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
This also happens to me. Kubuntu herd 5, all updates, this laptop: http://www.msicomputer.com/NB/product_spec.asp?model=MS-1039 -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Confirming this bug with RT2500. Can't set ESSID while interface is up. Workaround described above also works for me. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I can confirm my RT2500 card is not working on Herd 5. The workaround fixes it, but of course this is a sub-optimal solution! -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Same here confirmed, affects a lot of people. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
The rt2500pci card worked with Feisty herd 4 (kernel 2.6.20-9). The update to 2.6.20-10 broke it. The update to 2.6.20-11 didn't mend it. The workaround above works in 2.6.20-10, but not 2.6.20-11, possibly because it appears as two devices, ra0 and wmaster0 there. Output of lspci, lsmod, ifconfig and iwconfig for all three versions available. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I also have a problem with a RT2500 based card, after upgranding to feisty(from edgy) the interface is no lönger calles ra0 but wlan0. This in itself is not a problem, but i am unable to connnect to any network the scannign output is always empty, though i can set essid an key via iwconfig. As soon as I run for example dhclient i get the message wmaster0 unknown hardware type 801 and nothing else happens, except for not finding any networks, so this is seriously borken!! (I am typing this bug report on a windows machine :-( ). The old edgy driver worked completely flawless. So i would be happy if this can be fixed. Keep up the good work!! -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
** Changed in: network-manager (Ubuntu) Importance: Undecided = Medium Status: Unconfirmed = Confirmed -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I have same problem with rt2500 card in Feisty herd 4. I cannot set essid without downing the card even with no encryption. Let me know if you need any output. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Not a bug in the kernel, but one in network-managers backend. ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Unconfirmed = Rejected -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I have the same problem only I can configure the network manually without deactivating the device first. The network I'm connecting to is not encrypted, though. The relevant error message from daemon.log seems to be: Feb 18 18:53:15 benw-desktop NetworkManager: information^IActivation (ra0/wireless): association took too long (60s), failing activation. I'm attaching a snippet of my daemon.log. ** Attachment added: network manager messages from daemon.log http://librarian.launchpad.net/6466298/daemon.log -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Hello, I have a similar problem with the hostap driver in Feisty. I'm not sure if it's related, but I'm seeing similar behavior with NetworkManager -- no association, but I can manually bring the interface up with iwconfig, or with wireless-* lines in /etc/network/interfaces. I'm running Feisty with kernel 2.6.20-8-lowlatency and N-M 0.6.4-6ubuntu2. The card is a PCMCIA Linksys WPC11 with a Prism III inside. The primary firmware is at 1.1.0 and the secondary firmware at 1.8.2. hostap_cs is the driver being used. The ESSID is hidden and the network in encrypted with a shared WEP key. A few days ago, I decided to let N-M manage this connection. So, I removed the lines from /etc/network/interfaces that specified wlan0. Now, on boot, the connection does not come up. If I tell N-M to Connect to Other Wireless Network, it prompts me for the ESSID, security, and key. After entering these details, N-M fails to associate with the AP. However, I know the card can work, since if I go to the terminal and enter: ifconfig [interface] down iwconfig [interface] essid [ESSID] key restricted [key] ifconfig [interface] up dhclient3 [interface] Then the network works. For the sake of diagnosis, I have attached the output of N-M when invoked in non-daemon mode. ** Attachment added: Output of sudo NetworkManager --no-daemon 2 NetworkManager.log.0 http://librarian.launchpad.net/6468121/NetworkManager.log.0 -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I haven't tried network-manager with rt2500, but I know that it's working on three boxes where I have this card. I suspect the switch to network-manager in feisty is revealing that it needs a backend to operate rt2500 properly. ** Changed in: linux-source-2.6.20 (Ubuntu) Sourcepackagename: linux-source-2.6.20 = network-manager Importance: High = Undecided Status: Confirmed = Unconfirmed -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 78037] Re: rt2500 in feisty: problem solution
Ben, in Dapper I could set the essid without downing the card on my rt2500 laptop. On my other laptop (ipw2200), with Feisty I can also set the essid without downing the card (sometimes NM does not work and I have to configure the card manually). -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
What happens when you try setting the essid when the card is up? -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
Note: the same solution works for prism54: sudo ifconfig [interface] down sudo iwconfig [interface] essid [essid] key [key] sudo ifconfig [interface] up sudo dhclient3 [interface] This implies the problem is not at driver level at all, but higher up. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 78037] Re: rt2500 in feisty: problem solution
When I try to set the essid while the card is up nothing happens. No error. Simply the essid is not set, according to iwconfig. After a few weeks using the laptop with feisty, I also noticed that sometimes the essid cannot be set even if the card is down. As I usually notice that only when I up the card after setting essid, I don't know what iwconfig would report between the moment I try to set essid and the moment I up the card. Anyway, when that happens I just repeat the down/set essid/up process and it works. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
I have a rt2500 based card myself, and it doesn't play too well with NetworkManager yet. Have you tried connecting to a network without encryption? You should also be able to set the ssid without deactivating the ra0 interface. So does the card itself work, or is this just a problem with NetworkManager? -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 78037] Re: rt2500 in feisty: problem solution
Yes, the card itself works, but I have to ifconfig ra0 down before I can set the essid. Note that the card worked out of the box in dapper (but without NetworkManager). -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
By the way, by out of the box I meant using NetworkManager. I entered my essid/key in knetworkmanager, but the network failed to start. Then I tried manual configuration with iwconfig as mentioned above, and it did not work until I figured out that the interface must be down prior to setting the essid. -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
** Changed in: Ubuntu Sourcepackagename: None = linux-source-2.6.20 -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 78037] Re: rt2500 in feisty: problem solution
** Changed in: linux-source-2.6.20 (Ubuntu) Importance: Undecided = High Status: Unconfirmed = Confirmed ** Tags added: regression -- rt2500 in feisty: problem solution https://launchpad.net/bugs/78037 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
