Page 5 of 5 FirstFirst ... 345
Results 41 to 43 of 43

Thread: rt3572: Can't get WPA_supplicant to work

  1. #41
    Join Date
    Feb 2010
    Location
    Montréal
    Beans
    108
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: rt3572: Can't get WPA_supplicant to work

    Quote Originally Posted by praseodym View Post
    Remove both lines containing "wlan0", remove your wireless profile and reboot. Then set-up a new wireless profile. Check:

    Code:
    cat /etc/network/interfaces
    route -n
    cat /etc/resolv.conf
    lsmod
    iwconfig
    dmesg | grep rt2
    rfkill list
    sudo iwlist scan
    If you are using Wicd, try with those 2 lines.
    How do I delete my wireless profile?

  2. #42
    Join Date
    Aug 2011
    Location
    Berlin, Germany
    Beans
    7,970
    Distro
    Ubuntu Mate 20.04 Focal Fossa

    Re: rt3572: Can't get WPA_supplicant to work

    In NetworkManager: Right-click->Edit, choose your profile and "remove". In Wicd (I dont use it) its similar after starting the applet.

  3. #43
    Join Date
    Feb 2010
    Location
    Montréal
    Beans
    108
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: rt3572: Can't get WPA_supplicant to work

    I was going to try your changes, but I ended up trying the rt2800usb driver first and it is working! I've learned from this saga not to celebrate too early, but I am once again writing from my Cisco AM10 Valet Connector.

    For some reason it uses wlan0 rather than ra0, but I am prepared to live with that. So I haven't configured interfaces at all. I'm going to mark this as solved. Solution: use rt2800usb. We'll see if the good news keeps rolling.

    Thank you SO MUCH for all your help. I've learned a ton about how linux wireless networking works from all this. I was rereading old posts from when I started and just amazed that I didn't know any of the things I know now back then. Thank you.

    And I think the supplicant was working at the end. But I think overall it wasn't associating with the driver very well, perhaps because I wasn't using the right driver. Anyway, this hopefully seems to be solved.

    Like, oh my SQL!!
    Last edited by ohmysql; November 2nd, 2011 at 05:08 PM.

Page 5 of 5 FirstFirst ... 345

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •