h1

Efforts

March 28, 2007

I am taking a slight break from the bug report posts and posting an idea that I’ve been find more and more true, but quite problematic.
So I installed Kubuntu Edgy, then upgraded to Feisty with the newest kernel (2.6.20-13-generic) and try to get the wireless device to work. It is the RT2500 802.11g device and I struggle with this for a few hours. I have the wireless looking at the right gateway and DNS server in system settings, but it won’t connect. Knetworkmanager fails at configuring ra0. Wlanassistant fails to connect. After a while I decide that its not worth the effort. As much as I want wireless to work on this laptop (very much) I realize in this case I am doing much more work. I can use a wired connection in the use the laptop will see. In some problems we are trying to solve in the science department we have to look at some things. One afternoon my fellow student and I were arguing about the best way to use arrays to display some information until we realized we were both arguing against the simple way which we needed to get the next part going.

The problem with this is that we want everything to work in Ubuntu. We want that out-of-the-box laptop support. I just felt that if I spend more time on this laptop, I could eventually get it to work, just seems like I have better work to look at when it hits 3.10 am.

Advertisements

6 comments

  1. I discovered this wireless configuration problem when I first tested feisty which used kernel 2.6.19. I don’t expect it is a kernel problem. I am only giving you the kernel release so that you have an idea when the problem first occurred.

    Don’t give up on configuring the wireless. You are not the only one having a problem. I suspect there is some breakage going from edgy to feisty. Users like me, assume feisty is still beta ware and are not pinging you guys too hard about inconveniences.

    If you don’t address this problem now, Ubuntu is going to find itself in the same situation it as what happened with the X upgrade to edgy.

    Releasing every 6 months is a great idea, expect the fact it kind of forces everybody to switch over to the new release all at once.


  2. Quick workaround to get wireless back is to uninstall the Network Manager crap, and use manual configuration.


  3. rt2500 is not fully supported by NM:
    http://live.gnome.org/NetworkManagerHardware


  4. Hi,

    I can add a ‘me too’ to the Network Manager comments. I’ve disabled it as per the section in https://help.ubuntu.com/community/WifiDocs/NetworkManager, and my manually-configured rt2500 is back to its fully-working finest. (Well, the driver ignores the button on my notebook to enable/disable 802.11 wireless…)

    Cheers,
    Ken.


  5. Yep, another ‘me too’ here. Since Feisty I have to do the
    sudo ifdown eth1, sudo ifup eth1 mantra because it will not connect automatically. Interesting point is that ifdown returns an error that it found an old pid. So it seems that old id’s are not cleared correct when shutting down the laptop.


  6. Hey, just wanted to add to all of this that I have the RT2500 as well and the day before Feisty was released, my NIC decided to crap out on me and was forced into using my wireless instead. Taking a step back for a second, I was finally able to have my brother bring over his wireless router that he doesn’t use anymore. Back to the story, having never used it before I was skeptical as to how I was going to go about the whole process. I came across some information that helped me set it up tho. I had to edit /etc/network/interfaces and came across these lines to put in that file that will help:

    #————————————————————————-
    iface ra0 inet dhcp
    pre-up ifconfig ra0 up
    pre-up ifconfig ra0 down
    pre-up ifconfig ra0 up
    pre-up ifconfig ra0 down
    pre-up iwconfig ra0 essid “myssid”
    pre-up iwconfig ra0 mode Managed
    pre-up iwpriv ra0 set AuthMode=WPAPSK
    pre-up iwpriv ra0 set EncrypType=TKIP
    pre-up iwpriv ra0 set WPAPSK=”A shared key”
    pre-up ifconfig ra0 up
    #————————————————————————-
    or try one of these:
    #————————————————————————-
    iface ra0 inet dhcp
    pre-up iwpriv ra0 auth 3
    pre-up iwpriv ra0 enc 3
    pre-up iwconfig ra0 essid myssid
    pre-up iwpriv ra0 wpapsk A shared key
    pre-up iwconfig ra0 essid myssid
    #————————————————————————-
    auto ra0
    iface ra0 inet dhcp
    pre-up iwconfig ra0 essid ” myssid ”
    pre-up iwconfig ra0 mode managed
    pre-up iwpriv ra0 set Channel=11
    pre-up iwpriv ra0 set AuthMode=WPAPSK
    pre-up iwpriv ra0 set EncrypType=TKIP
    pre-up iwpriv ra0 set WPAPSK=”A shared key”
    pre-up iwpriv ra0 set TxRate=0
    #————————————————————————-

    Make sure to comment out the information in that file for your card if any is in there before you add the lines in there. Hopefully this will help you out if you haven’t got it working already! 🙂

    P.S. These methods are for WPA…



Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: