Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 18 of 18
I have already blacklisted the driver and I've double checked that only one driver is running. So no problem there, about the password, since I can't find my WiFi there ...
  1. #11
    Just Joined!
    Join Date
    Feb 2010
    Posts
    9
    I have already blacklisted the driver and I've double checked that only one driver is running. So no problem there, about the password, since I can't find my WiFi there is yet no need for the password to be correct or not :P

    I installed Wicd just to try if I were able to find my network there, as I could't see it in NM. I've seen through all settnings in Wicd, and can't really find one asking about encryptions or anything... As WPA Supplicant I'm using something called wext, don't really know what that is, but it is what Wicd is recomending me to use.

    Thanks once again for all help and quick responses! Really want this to work [=

  2. #12
    Just Joined!
    Join Date
    Feb 2010
    Posts
    9
    News!! I ran the Linux Mint Live CD on my Laptop which has a built-in wireless card and I was able to see and connect to my wifi! So it has to be something fuzzy about the drivers Im using, even though I just updated them =\

  3. #13
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,577
    That is why I suggested trying both drivers, to see if one worked better than the other. I am not sure of the wext driver, as I haven't used wpa_supplicant in a while.
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  4. #14
    Just Joined!
    Join Date
    Feb 2010
    Posts
    9
    Well yeah Ive tried both of the drivers (with the other one blacklisted) but that disent solve it. But I'll try to reinstall Mint and start with driver-uppdate and se how that goes

  5. #15
    Just Joined!
    Join Date
    Feb 2010
    Posts
    9
    Okey, so I've reinstalled everything and uppdated the drivers; just as before :< Gonna try to backlist them one by one again then post an uppdate on how everything is going.

  6. #16
    Just Joined!
    Join Date
    Feb 2010
    Posts
    9
    Good and bad news!

    The good news;
    Thanks to waterhead I'm now able to see my network and somewhat connect to it! I just had to reinstall everything and blacklist the rt2800usb.

    The Bad news;
    I can't get all the way through connection to my network; with Wicd I get stuck at Obtaining Ip (using Wext as WPA supplicant), so basiclly I'm getting nowere! (Tired both WPA and WPA2)..

    DHCP is enabled, and my adapter and the driver should be able to handle WPA. I've tried a long method that involved "sudo wpa_supplicant -Dwext -ira0 -c/etc/wpa_supplicant.conf -dd" = Diden't really get me anyeare, it get stuck after "Group_Handshake -> Complete".. And I'm like Whoaaa

    Thanks for all the help so far!

  7. #17
    Linux Guru waterhead's Avatar
    Join Date
    Jul 2004
    Location
    Franklin, Wisconsin
    Posts
    4,577
    You normally would use wpa_supplicant, by itself, instead of Wicd or NetworkManager. When you use it this way, you have to have a configuration file set up with the connection information. That is what the -c/etc/wpa_supplicant.conf part is referring to. To see examples of a file, read the man pages.
    Code:
    man wpa_supplicant.conf
    It looks like the first example is something like you would use. There also may be more examples in the /usr/share/doc/wpasupplicant directory.

    When using Wicd, you shouldn't have to do anything with wpa_supplicant. It may use it for the connections, but it should do all of the configuring for you. The same goes for NetworkManager, although I don't know if it even uses wpa_supplicant.
    Paul

    Please do not send Private Messages to me with requests for help. I will not reply.

  8. #18
    Just Joined!
    Join Date
    Feb 2010
    Posts
    1
    Quote Originally Posted by Bjoernen View Post
    Good and bad news!
    The Bad news;
    I can't get all the way through connection to my network; with Wicd I get stuck at Obtaining Ip (using Wext as WPA supplicant), so basiclly I'm getting nowere! (Tired both WPA and WPA2)..

    DHCP is enabled, and my adapter and the driver should be able to handle WPA. I've tried a long method that involved "sudo wpa_supplicant -Dwext -ira0 -c/etc/wpa_supplicant.conf -dd" = Diden't really get me anyeare, it get stuck after "Group_Handshake -> Complete".. And I'm like Whoaaa
    Hi got similar problems with the group_handshake, and i made a workaround for this.
    It seems no driver problem but more handshaking problem between processes, and the workarround is based on to set wpa_suplicant to a lower process priority, so it handles all events slower and the upper process (Wicd or network manager) is missing less information.

    Workarround (no patch) for AntiX 8.2 with Wicd 1.6.2.2-3mlrepo1
    cd /usr/share/wicd/wicd
    cp winettools.py winettools.py.org
    vi winettools.py
    change the code at
    cmd = ['wpa_supplicant'
    in
    cmd = ['nice', '-n', '19', 'wpa_supplicant'
    After that move the compiled versions and reboot,
    mv winettools.pyc winettools.pyc.org
    This works fine for me since a month,

    Maybe other locations other syntax in your case.
    I am not allowed to refer to other urls but if you wish you can get it.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

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