Results 1 to 3 of 3

Thread: Can't connect to WPA2 wifi- Bad password

  1. #1
    Just burned his ISO
    Join Date
    Jun 2011
    Posts
    1

    Default Can't connect to WPA2 wifi- Bad password

    Hi,
    I recently installed BackTrack5-GNOME-64bit to my HDD (First time user) and I can't connect to my WiFi. I am pretty new to linux.
    It scans fine and finds the networks but when I try to connect to my Wifi through Wicd it says
    Code:
    Disconnecting active connections...
    ESSID: Resetting IP address...
    ESSID: Putting interface up...
    ESSID: Validating authentication...
    ESSID: Connection Failed: Bad password
    My device is
    Code:
    lspci -vnn | grep 14e4
    0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
    I've read on wireless.kernel.org that there is a known issue with DMA (Don't know what that is) and LP-PHY devices with kernel 2.6.
    My kernel is 2.6.38 (uname -r).
    I have seen some people make the BCM4312 work but I have looked on alot of different methods (Before I reinstalled) and nothing have worked.
    Some output (I don't know what most of these report so some might be abundant):
    Code:
    dmesg | grep b43
    [    2.991479] b43-pci-bridge 0000:0c:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
    [    2.991496] b43-pci-bridge 0000:0c:00.0: setting latency timer to 64
    [   14.093446] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
    [   14.407154] Registered led device: b43-phy0::tx
    [   14.407175] Registered led device: b43-phy0::rx
    [   14.407193] Registered led device: b43-phy0::radio
    [   15.530255] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    [  140.800303] b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
    [  140.816319] b43-phy0 ERROR: This device does not support DMA on your system. It will now be switched to PIO.
    [  140.824970] b43-phy0: Controller RESET (DMA error) ...
    [  141.160292] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    [  154.941477] b43-phy0: Controller restarted
    [  797.660277] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    [ 1998.600299] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    [ 2013.070296] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    [ 2064.800294] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    [ 2401.340273] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    [ 2415.570290] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
    Code:
    [ 2429.690134] sky2 0000:09:00.0: eth0: disabling interface
    [ 2429.701206] sky2 0000:09:00.0: eth0: enabling interface
    [ 2429.702039] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 2429.760115] sky2 0000:09:00.0: eth0: disabling interface
    [ 2429.915902] sky2 0000:09:00.0: eth0: enabling interface
    [ 2429.916401] ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 2432.060230] sky2 0000:09:00.0: eth0: Link is up at 100 Mbps, full duplex, flow control both
    [ 2432.060969] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 2440.120081] wlan0: no IPv6 routers present
    [ 2442.330084] eth0: no IPv6 routers present
    Code:
    iwconfig
    lo        no wireless extensions.
    
    eth0      no wireless extensions.
    
    wlan0     IEEE 802.11bg  ESSID:"X"  
              Mode:Managed  Frequency:2.452 GHz  Access Point: 00:18:E7:F5:0C:B8   
              Bit Rate=1 Mb/s   Tx-Power=20 dBm   
              Retry  long limit:7   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:off
              Link Quality=70/70  Signal level=-11 dBm  
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:269   Missed beacon:0
    Code:
    ifconfig
    eth0      Link encap:Ethernet  HWaddr a4:ba:db:d3:82:c5  
              inet addr:192.168.0.184  Bcast:192.168.0.255  Mask:255.255.255.0
              inet6 addr: fe80::a6ba:dbff:fed3:82c5/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:3988 errors:0 dropped:0 overruns:0 frame:0
              TX packets:2305 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:2933190 (2.9 MB)  TX bytes:496710 (496.7 KB)
              Interrupt:18 
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:80 errors:0 dropped:0 overruns:0 frame:0
              TX packets:80 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:5585 (5.5 KB)  TX bytes:5585 (5.5 KB)
    
    wlan0     Link encap:Ethernet  HWaddr 70:f1:a1:c2:52:b5  
              inet6 addr: fe80::72f1:a1ff:fec2:52b5/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:0 (0.0 B)  TX bytes:5340 (5.3 KB)
    Code:
    lsmod | grep b43
    b43                   306304  0 
    mac80211              269729  1 b43
    cfg80211              165057  2 b43,mac80211
    ssb                    43017  1 b43
    Code:
    cat /etc/modprobe.d/blacklist.conf
    # This file lists those modules which we don't want to be loaded by
    # alias expansion, usually so some other driver will be loaded for the
    # device instead.
    
    # evbug is a debug tool that should be loaded explicitly
    blacklist evbug
    blacklist ar9170usb
    blacklist r8187
    blacklist ath_pci
    
    # these drivers are very simple, the HID drivers are usually preferred
    blacklist usbmouse
    blacklist usbkbd
    
    # replaced by e100
    blacklist eepro100
    
    # replaced by tulip
    blacklist de4x5
    
    # causes no end of confusion by creating unexpected network interfaces
    blacklist eth1394
    
    # snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
    # hardware on its own (Ubuntu bug #2011, #6810)
    blacklist snd_intel8x0m
    
    # Conflicts with dvb driver (which is better for handling this device)
    blacklist snd_aw2
    
    # causes failure to suspend on HP compaq nc6000 (Ubuntu: #10306)
    blacklist i2c_i801
    
    # replaced by p54pci
    blacklist prism54
    
    # replaced by b43 and ssb.
    blacklist bcm43xx
    
    # most apps now use garmin usb driver directly (Ubuntu: #114565)
    blacklist garmin_gps
    
    # replaced by asus-laptop (Ubuntu: #184721)
    blacklist asus_acpi
    
    # low-quality, just noise when being used for sound playback, causes
    # hangs at desktop session start (Ubuntu: #246969)
    blacklist snd_pcsp
    
    # ugly and loud noise, getting on everyone's nerves; this should be done by a
    # nice pulseaudio bing (Ubuntu: #77010)
    blacklist pcspkr
    
    # EDAC driver for amd76x clashes with the agp driver preventing the aperture
    # from being initialised (Ubuntu: #297750). Blacklist so that the driver
    # continues to build and is installable for the few cases where its
    # really needed.
    blacklist amd76x_edac
    All I have done since my fresh install is download the firmware-b43-lpphy-installer and installed it.
    My two b43 packages are:
    firmware-b43-lpphy-installer (version: 4.174.64.19-4)
    b43-fwcutter (version: 1:013-2)

    I either would like some insight on how I can fix this problem (if possible) or help with / link to documentation to upgrade the kernel to 3.0. I have searched how to do this but didn't find anything.
    If I would go the path of upgrading the kernel, is it a daunting task? Is it smart at all? - I mean is it reasonably stable or is it in early early development? (I don't know much about these matters).

    Thanks for any help or advice in advance,
    Chanpa.

  2. #2
    Just burned his ISO
    Join Date
    Apr 2011
    Posts
    6

    Default Re: Can't connect to WPA2 wifi- Bad password

    you have a field above the password field, then there you need to find something like wpa2 (passphrase) or wpa1/2 (passphrase) and then type the real password and you are gonna be connected

  3. #3
    Just burned his ISO
    Join Date
    Jun 2011
    Posts
    11

    Default Re: Can't connect to WPA2 wifi- Bad password

    Connect with Presharedkey. If that don't work, try to connect with a static IP adress. Any chance you running a BTHOMEHUB ? Coz they have problems...

Similar Threads

  1. Help getting out WPA2 password from GPO
    By Sparco in forum Beginners Forum
    Replies: 3
    Last Post: 03-04-2011, 02:22 PM
  2. how to connect to the WPA2 LEAP wireless network?
    By Icht00r in forum Beginners Forum
    Replies: 1
    Last Post: 08-09-2010, 10:55 AM
  3. cannot connect WPA2
    By avatar in forum Beginners Forum
    Replies: 3
    Last Post: 05-28-2010, 10:02 AM
  4. IPW5100 WPA2-PSK TKIP+AES won't connect
    By Coyotl in forum OLD BackTrack 4 General Support
    Replies: 0
    Last Post: 08-19-2009, 01:03 AM
  5. -=Xploitz=- TUTORIAL: E-Z Connect To WPA2 AES
    By -=Xploitz=- in forum OLD Tutorials and Guides
    Replies: 13
    Last Post: 11-03-2008, 05:31 PM

Posting Permissions

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