Page 61 of 121 FirstFirst ... 1151596061626371111 ... LastLast
Results 601 to 610 of 1210

Thread: Comprehensive ndiswrapper troubleshooting guide

  1. November 26th, 2009 #601
    vancousa
    vancousa is offline Spilled the Beans
    Join Date
    Nov 2009
    Beans
    14

    Re: Comprehensive ndiswrapper troubleshooting guide

    pytheas22:

    I have included the responses from the commands below. I can't thank you enough for your help I am feed up with Windows.

    sudo rmmod b43
    ERROR: Module b43 does not exist in /proc/modules

    sudo modprobe b43
    No information returned

    sudo ifconfig
    wlan0 up

    wlan0 up
    SIOCSIFFLAGS: No such file or directory


    sudo iwlist scan
    lo Interface doesn't support scanning.

    eth0 Interface doesn't support scanning.

    wmaster0 Interface doesn't support scanning.

    wlan0 Interface doesn't support scanning : Network is down




    dmesg | grep -e b43 -e wlan[/code]

    [ 2.409829] b43-pci-bridge 0000:00:0a.0: PCI INT A -> Link[LNKC] -> GSI 10 (level, low) -> IRQ 10
    [ 9.690891] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
    [ 26.792237] b43 ssb0:0: firmware: requesting b43/ucode5.fw
    [ 26.816305] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
    [ 26.852565] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
    [ 26.852581] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
    [ 26.852589] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
    [ 27.391995] b43 ssb0:0: firmware: requesting b43/ucode5.fw
    [ 27.421444] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
    [ 27.462584] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
    [ 27.462689] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
    [ 27.462781] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
    [ 231.733422] b43-phy1: Broadcom 4306 WLAN found (core revision 5)
    [ 231.918877] b43 ssb0:0: firmware: requesting b43/ucode5.fw
    [ 231.966936] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
    [ 232.015223] b43-phy1 ERROR: Firmware file "b43/ucode5.fw" not found
    [ 232.015239] b43-phy1 ERROR: Firmware file "b43-open/ucode5.fw" not found
    [ 232.015248] b43-phy1 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
    [ 232.030372] b43 ssb0:0: firmware: requesting b43/ucode5.fw
    [ 232.072658] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
    [ 232.155874] b43-phy1 ERROR: Firmware file "b43/ucode5.fw" not found
    [ 232.155893] b43-phy1 ERROR: Firmware file "b43-open/ucode5.fw" not found
    [ 232.155902] b43-phy1 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
    [ 309.033997] b43 ssb0:0: firmware: requesting b43/ucode5.fw
    [ 309.057842] b43 ssb0:0: firmware: requesting b43-open/ucode5.fw
    [ 309.100392] b43-phy1 ERROR: Firmware file "b43/ucode5.fw" not found
    [ 309.100409] b43-phy1 ERROR: Firmware file "b43-open/ucode5.fw" not found
    [ 309.100418] b43-phy1 ERROR: You must go to http://wireless.kernel.org/en/users/...devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.


    If the second-to-last command (the "iwlist" one) returns a list of networks, try connecting now.
    Advanced reply Adv Reply  
  2. November 26th, 2009 #602
    sharobim
    sharobim is offline Spilled the Beans
    Join Date
    Nov 2009
    Beans
    16

    Re: Comprehensive ndiswrapper troubleshooting guide

    Thank you so much for your prompt and lovely spirit to help. As you will notice I can see many network but unable to log to mine "Mike's"
    Here are the results.
    mike@mike-laptop:~$ lspci -nn
    00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03)
    00:01.0 PCI bridge [0604]: Intel Corporation 82855PM Processor to AGP Controller [8086:3341] (rev 03)
    00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01)
    00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01)
    00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01)
    00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01)
    00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev 81)
    00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge [8086:24cc] (rev 01)
    00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE Controller [8086:24ca] (rev 01)
    00:1f.5 Multimedia audio controller [0401]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5] (rev 01)
    00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01)
    01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] [1002:4c66] (rev 02)
    02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet [14e4:165d] (rev 01)
    02:01.0 CardBus bridge [0607]: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller [1217:7113] (rev 20)
    02:01.1 CardBus bridge [0607]: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller [1217:7113] (rev 20)
    02:03.0 Network controller [0280]: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller [14e4:4318] (rev 02)
    mike@mike-laptop:~$
    mike@mike-laptop:~$
    mike@mike-laptop:~$ lsusb
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 004: ID 046d:c016 Logitech, Inc. M-UV69a/HP M-UV96 Optical Wheel Mouse
    Bus 003 Device 003: ID 1058:0702 Western Digital Technologies, Inc. Passport External HDD
    Bus 003 Device 002: ID 058f:9254 Alcor Micro Corp. Hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    mike@mike-laptop:~$
    mike@mike-laptop:~$
    mike@mike-laptop:~$ dmesg | grep -ie wlan -ie radio
    [ 10.476887] wlan0: ethernet device 00:0e:9b:d5:85:27 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4318.5.conf
    [ 10.476932] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
    [ 19.438662] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 35.748280] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 46.736035] wlan0: no IPv6 routers present
    mike@mike-laptop:~$
    mike@mike-laptop:~$
    mike@mike-laptop:~$ uname -rm
    2.6.31-15-generic i686
    mike@mike-laptop:~$
    mike@mike-laptop:~$ sudo iwlist scan
    [sudo] password for mike:
    lo Interface doesn't support scanning.

    eth0 Interface doesn't support scanning.

    wlan0 Scan completed :
    Cell 01 - Address: 00:1E:E5:85:7F:21
    ESSID:"Hayastan"
    Protocol:IEEE 802.11g
    Mode:Managed
    Frequency:2.437 GHz (Channel 6)
    Quality:34/100 Signal level:-74 dBm Noise level:-96 dBm
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
    12 Mb/s; 48 Mb/s
    Extra:bcn_int=100
    Extra:atim=0
    Cell 02 - Address: 00:24:56:2E:EF:B9
    ESSID:"Mike's"
    Protocol:IEEE 802.11g
    Mode:Managed
    Frequency:2.437 GHz (Channel 6)
    Quality:100/100 Signal level:-28 dBm Noise level:-96 dBm
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
    11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
    48 Mb/s; 54 Mb/s
    Extra:bcn_int=100
    Extra:atim=0
    IE: WPA Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (1) : TKIP
    Authentication Suites (1) : PSK
    Cell 03 - Address: 00:40:F4:F9:FA:47
    ESSID:"DLLOWIFI"
    Protocol:IEEE 802.11g
    Mode:Managed
    Frequency:2.437 GHz (Channel 6)
    Quality:12/100 Signal level:-88 dBm Noise level:-96 dBm
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
    12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s
    48 Mb/s; 54 Mb/s
    Extra:bcn_int=100
    Extra:atim=0
    Cell 04 - Address: 00:13:46:F3:42:A8
    ESSID:"Opah"
    Protocol:IEEE 802.11g
    Mode:Managed
    Frequency:2.437 GHz (Channel 6)
    Quality:3/100 Signal level:-94 dBm Noise level:-96 dBm
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
    11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
    48 Mb/s; 54 Mb/s
    Extra:bcn_int=100
    Extra:atim=0
    IE: WPA Version 1
    Group Cipher : CCMP
    Pairwise Ciphers (1) : CCMP
    Authentication Suites (1) : PSK
    Cell 05 - Address: 00:1C:10:22:FB:FF
    ESSID:"benoit"
    Protocol:IEEE 802.11g
    Mode:Managed
    Frequency:2.462 GHz (Channel 11)
    Quality:50/100 Signal level:-64 dBm Noise level:-96 dBm
    Encryption keyn
    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s
    24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s
    12 Mb/s; 48 Mb/s
    Extra:bcn_int=100
    Extra:atim=0
    IE: IEEE 802.11i/WPA2 Version 1
    Group Cipher : TKIP
    Pairwise Ciphers (2) : CCMP TKIP
    Authentication Suites (1) : PSK
    Thanks again
    Advanced reply Adv Reply  
  3. November 27th, 2009 #603
    pytheas22's Avatar
    pytheas22
    pytheas22 is offline Staff Emeritus
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    vancousa: from your dmesg output, it looks like you just need to install the firmware for your wireless card. To do that, type these commands while plugged into the Internet:
    Code:
    sudo apt-get update
sudo apt-get install b43-fwcutter
    While the package is being installed, you will be prompted to download firmware automatically. Say yes. Then reboot and your wireless card should work. If not, please post the output of:
    Code:
    dmesg | grep -e b43 -e wlan
sudo iwlist scan
    (FYI, you can also install the firmware using the graphical utility at System>Administration>Hardware Drivers, in case you prefer not to use the command line.)

    sharobim: according to the b43 project page, your wireless card should be supported by the native Linux driver, so there should be no need to use ndiswrapper; also, the native driver may work better. So please run the following command to give the b43 driver a try:
    Code:
    sudo apt-get update
sudo apt-get install b43-fwcutter
    (When prompted to download firmware, say yes, then continue with:
    Code:
    sudo rmmod b43
sudo rmmod b44
sudo rmmod ssb
sudo rmmod ndiswrapper
sudo modprobe b43
    Now try connecting and hopefully it will work. If not, please post the output of all the commands above, as well as:
    Code:
    dmesg | grep -e b43 -e wlan

    Personal site     | Understanding Wireless Chipsets | Troubleshooting ndiswrapper | The VAR Guy
    Advanced reply Adv Reply  
  4. November 28th, 2009 #604
    sharobim
    sharobim is offline Spilled the Beans
    Join Date
    Nov 2009
    Beans
    16

    Re: Comprehensive ndiswrapper troubleshooting guide

    I feel so bad to bother you but I am sure you will forgive me for been so ignorant

    Yesterday, I moved to "Wicd" and got some strange results..!
    1) If I have the wired connection running and try the wireless it work like a charm.
    2) If I try the wireless with the Ethernet removed it can take up to 1/2 an hour to connect after many retries saying validating then complaining about "unable to get IP address"

    Today after following you recommendation I can no longer connect to the wireless even after 1 hour? not even after an ethernet connection was established.
    Sorry

    mike@mike-laptop:~$ sudo apt-get update
    [sudo] password for mike:
    Ign cdrom://Ubuntu 9.10 _Karmic Koala_ - Release i386 (20091028.5) karmic/main Translation-en_US
    Ign cdrom://Ubuntu 9.10 _Karmic Koala_ - Release i386 (20091028.5) karmic/restricted Translation-en_US
    Hit http://us.archive.ubuntu.com karmic Release.gpg
    Ign http://us.archive.ubuntu.com karmic/main Translation-en_US
    Hit http://archive.canonical.com karmic Release.gpg
    Ign http://archive.canonical.com karmic/partner Translation-en_US
    Hit http://security.ubuntu.com karmic-security Release.gpg
    Ign http://security.ubuntu.com karmic-security/main Translation-en_US
    Ign http://us.archive.ubuntu.com karmic/restricted Translation-en_US
    Ign http://us.archive.ubuntu.com karmic/universe Translation-en_US
    Ign http://us.archive.ubuntu.com karmic/multiverse Translation-en_US
    Get:1 http://us.archive.ubuntu.com karmic-updates Release.gpg [189B]
    Ign http://us.archive.ubuntu.com karmic-updates/main Translation-en_US
    Ign http://us.archive.ubuntu.com karmic-updates/restricted Translation-en_US
    Ign http://us.archive.ubuntu.com karmic-updates/universe Translation-en_US
    Ign http://us.archive.ubuntu.com karmic-updates/multiverse Translation-en_US
    Hit http://archive.canonical.com karmic Release
    Ign http://security.ubuntu.com karmic-security/restricted Translation-en_US
    Ign http://security.ubuntu.com karmic-security/universe Translation-en_US
    Ign http://security.ubuntu.com karmic-security/multiverse Translation-en_US
    Hit http://security.ubuntu.com karmic-security Release
    Hit http://us.archive.ubuntu.com karmic Release
    Get:2 http://us.archive.ubuntu.com karmic-updates Release [44.1kB]
    Hit http://archive.canonical.com karmic/partner Packages
    Hit http://security.ubuntu.com karmic-security/main Packages
    Hit http://security.ubuntu.com karmic-security/restricted Packages
    Hit http://security.ubuntu.com karmic-security/main Sources
    Hit http://security.ubuntu.com karmic-security/restricted Sources
    Hit http://security.ubuntu.com karmic-security/universe Packages
    Hit http://security.ubuntu.com karmic-security/universe Sources
    Hit http://security.ubuntu.com karmic-security/multiverse Packages
    Hit http://security.ubuntu.com karmic-security/multiverse Sources
    Hit http://us.archive.ubuntu.com karmic/main Packages
    Hit http://us.archive.ubuntu.com karmic/restricted Packages
    Hit http://us.archive.ubuntu.com karmic/main Sources
    Hit http://us.archive.ubuntu.com karmic/restricted Sources
    Hit http://us.archive.ubuntu.com karmic/universe Packages
    Hit http://us.archive.ubuntu.com karmic/universe Sources
    Hit http://us.archive.ubuntu.com karmic/multiverse Packages
    Hit http://us.archive.ubuntu.com karmic/multiverse Sources
    Get:3 http://us.archive.ubuntu.com karmic-updates/main Packages [88.5kB]
    Get:4 http://us.archive.ubuntu.com karmic-updates/restricted Packages [14B]
    Get:5 http://us.archive.ubuntu.com karmic-updates/main Sources [28.5kB]
    Get:6 http://us.archive.ubuntu.com karmic-updates/restricted Sources [14B]
    Get:7 http://us.archive.ubuntu.com karmic-updates/universe Packages [54.1kB]
    Get:8 http://us.archive.ubuntu.com karmic-updates/universe Sources [12.2kB]
    Get:9 http://us.archive.ubuntu.com karmic-updates/multiverse Packages [1,616B]
    Get:10 http://us.archive.ubuntu.com karmic-updates/multiverse Sources [1,223B]
    Fetched 230kB in 3s (74.4kB/s)
    Reading package lists... Done
    mike@mike-laptop:~$ sudo apt-get install b43-fwcutter
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    b43-fwcutter is already the newest version.
    The following packages were automatically installed and are no longer required:
    linux-backports-modules-2.6.31-14-generic kdegames-mahjongg-data
    Use 'apt-get autoremove' to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.
    mike@mike-laptop:~$ sudo rmmod b43
    ERROR: Module b43 does not exist in /proc/modules
    mike@mike-laptop:~$ sudo rmmod b44
    ERROR: Module b44 does not exist in /proc/modules
    mike@mike-laptop:~$ sudo rmmod ssb
    ERROR: Module ssb does not exist in /proc/modules
    mike@mike-laptop:~$ sudo rmmod ndiswrapper
    mike@mike-laptop:~$ sudo modprobe b43
    WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
    WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
    mike@mike-laptop:~$ dmesg | grep -e b43 -e wlan
    [ 8.512862] wlan0: ethernet device 00:0e:9b:d5:85:27 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4318.5.conf
    [ 8.512906] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
    [ 13.307470] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 21.260271] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 31.392030] wlan0: no IPv6 routers present
    [ 34.655562] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 36.304268] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 46.960031] wlan0: no IPv6 routers present
    [ 139.543024] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 140.152334] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 150.816045] wlan0: no IPv6 routers present
    [ 254.545253] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 255.148320] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 265.504035] wlan0: no IPv6 routers present
    [ 369.615608] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 370.216326] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 380.432037] wlan0: no IPv6 routers present
    [ 569.598191] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 570.200327] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 580.600043] wlan0: no IPv6 routers present
    [ 774.580850] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 775.192397] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 785.600041] wlan0: no IPv6 routers present
    [ 979.541720] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 980.152347] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 990.848042] wlan0: no IPv6 routers present
    [ 1233.251456] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1233.869197] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1244.788034] wlan0: no IPv6 routers present
    [ 1421.303853] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1421.920377] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1432.672045] wlan0: no IPv6 routers present
    [ 1801.536456] ndiswrapper: device wlan0 removed
    [ 1819.929826] b43-pci-bridge 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
    [ 1820.028365] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
    [ 1820.347136] Registered led device: b43-phy0::tx
    [ 1820.347195] Registered led device: b43-phy0::rx
    [ 1820.347245] Registered led device: b43-phy0::radio
    [ 1821.524069] b43 ssb0:0: firmware: requesting b43/ucode5.fw
    [ 1821.630350] b43 ssb0:0: firmware: requesting b43/pcm5.fw
    [ 1821.645936] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
    [ 1821.650900] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
    [ 1821.776064] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
    [ 1821.817736] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1824.684082] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
    [ 1824.725413] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1824.988086] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
    [ 1825.024777] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 1826.680331] wlan0: direct probe to AP 00:24:56:2e:ef:b9 (try 1)
    [ 1826.681989] wlan0: direct probe responded
    [ 1826.681999] wlan0: authenticate with AP 00:24:56:2e:ef:b9 (try 1)
    [ 1826.683745] wlan0: authenticated
    [ 1826.683780] wlan0: associate with AP 00:24:56:2e:ef:b9 (try 1)
    [ 1826.685679] wlan0: RX AssocResp from 00:24:56:2e:ef:b9 (capab=0x431 status=0 aid=1)
    [ 1826.685689] wlan0: associated
    [ 1826.687268] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 1837.508041] wlan0: no IPv6 routers present
    mike@mike-laptop:~$
    Advanced reply Adv Reply  
  5. November 28th, 2009 #605
    vancousa
    vancousa is offline Spilled the Beans
    Join Date
    Nov 2009
    Beans
    14

    Re: Comprehensive ndiswrapper troubleshooting guide

    When you refer to firmware I know that as code that is loaded onto the PCI Card. Do you mean the PCI Windows Drivers?

    Quote Originally Posted by pytheas22 View Post
    vancousa: from your dmesg output, it looks like you just need to install the firmware for your wireless card. To do that, type these commands while plugged into the Internet:
    Code:
    sudo apt-get update
sudo apt-get install b43-fwcutter
    While the package is being installed, you will be prompted to download firmware automatically. Say yes. Then reboot and your wireless card should work. If not, please post the output of:
    Code:
    dmesg | grep -e b43 -e wlan
sudo iwlist scan
    (FYI, you can also install the firmware using the graphical utility at System>Administration>Hardware Drivers, in case you prefer not to use the command line.)

    sharobim: according to the b43 project page, your wireless card should be supported by the native Linux driver, so there should be no need to use ndiswrapper; also, the native driver may work better. So please run the following command to give the b43 driver a try:
    Code:
    sudo apt-get update
sudo apt-get install b43-fwcutter
    (When prompted to download firmware, say yes, then continue with:
    Code:
    sudo rmmod b43
sudo rmmod b44
sudo rmmod ssb
sudo rmmod ndiswrapper
sudo modprobe b43
    Now try connecting and hopefully it will work. If not, please post the output of all the commands above, as well as:
    Code:
    dmesg | grep -e b43 -e wlan
    Advanced reply Adv Reply  
  6. November 28th, 2009 #606
    pytheas22's Avatar
    pytheas22
    pytheas22 is offline Staff Emeritus
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    sharobim: the behavior you describe sounds strange. Are you sure your wireless is really connecting when the ethernet is plugged in, and it's not just that the ethernet is already connected?

    In any case, if things are working worse now than they were originally, you can get back to the original situation (where wicd would connect you quickly when the ethernet cable was also plugged in) by blacklisting the b43 and ssb drivers with the commands:
    Code:
    echo b43 | sudo tee -a /etc/modprobe.d/blacklist.conf
echo ssb | sudo tee -a /etc/modprobe.d/blacklist.conf
echo ndiswrapper | sudo tee -a /etc/modules
    This will cause the system to switch back to ndiswrapper, which is what you were using before.

    As for figuring out why the wireless seems to work fine when ethernet is plugged in, it would be helpful if you connected under those conditions, then posted the output of:
    Code:
    ifconfig
iwconfig
grep -e ndis -e wlan /var/log/syslog
dmesg | grep -e ndis -e wlan
    vancousa: the firmware I'm referring to is proprietary firmware that the open-source b43 driver requires to work properly, which is different from the firmware on the device itself and also different from the Windows drivers (it's actually extracted from the Windows drivers, but you need only certain bits of the drivers, not the whole thing). Ubuntu doesn't come with the firmware installed by default because of legal issues (the company that owns the firmware has not granted Ubuntu the right to redistribute it), but you can install it using the commands from my last post. After that, your card should work.

    Personal site     | Understanding Wireless Chipsets | Troubleshooting ndiswrapper | The VAR Guy
    Advanced reply Adv Reply  
  7. November 28th, 2009 #607
    vancousa
    vancousa is offline Spilled the Beans
    Join Date
    Nov 2009
    Beans
    14

    Re: Comprehensive ndiswrapper troubleshooting guide

    I ran the commands from last post and recived the following messages. I will not that he last message states to enter a cd which I did but it would noy\t continue. It is like the application/script is not recognizing the CD. Now I will mention that the cd is not named Ubuntu 9.10 _Karmic Koala_ - Release i386 (20091028.5) but is named Ubuntu 9.10 i386. I also need to mention that I downloaded the ISO image and created an ISO cd. I do not know if that is why the script/app will not recognize that I have the correct cd. This ISO was created in a windows XP OS and not under Ubuntu 9.10 so I do not know if that is a factor and is stopping me from completing the last command sudo apt-get install b43-fwcutter.

    Again I can't thank you enough for your help.

    Below are the results of the two commands from your prvious post.

    ubuntu:~$ sudo apt-get update

    Ign cdrom://Ubuntu 9.10 _Karmic Koala_ - Release i386 (20091028.5) karmic/main Translation-en_US
    Ign cdrom://Ubuntu 9.10 _Karmic Koala_ - Release i386 (20091028.5) karmic/restricted Translation-en_US
    Hit http://security.ubuntu.com karmic-security Release.gpg
    Hit http://us.archive.ubuntu.com karmic Release.gpg
    Ign http://us.archive.ubuntu.com karmic/main Translation-en_US
    Ign http://us.archive.ubuntu.com karmic/restricted Translation-en_US
    Ign http://us.archive.ubuntu.com karmic/universe Translation-en_US
    Ign http://us.archive.ubuntu.com karmic/multiverse Translation-en_US
    Hit http://us.archive.ubuntu.com karmic-updates Release.gpg
    Ign http://us.archive.ubuntu.com karmic-updates/main Translation-en_US
    Ign http://us.archive.ubuntu.com karmic-updates/restricted Translation-en_US
    Ign http://us.archive.ubuntu.com karmic-updates/universe Translation-en_US
    Ign http://us.archive.ubuntu.com karmic-updates/multiverse Translation-en_US
    Hit http://us.archive.ubuntu.com karmic Release
    Hit http://us.archive.ubuntu.com karmic-updates Release
    Hit http://us.archive.ubuntu.com karmic/main Packages
    Hit http://us.archive.ubuntu.com karmic/restricted Packages
    Hit http://us.archive.ubuntu.com karmic/main Sources
    Hit http://us.archive.ubuntu.com karmic/restricted Sources
    Hit http://us.archive.ubuntu.com karmic/universe Packages
    Hit http://us.archive.ubuntu.com karmic/universe Sources
    Hit http://us.archive.ubuntu.com karmic/multiverse Packages
    Hit http://us.archive.ubuntu.com karmic/multiverse Sources
    Hit http://us.archive.ubuntu.com karmic-updates/main Packages
    Hit http://us.archive.ubuntu.com karmic-updates/restricted Packages
    Hit http://us.archive.ubuntu.com karmic-updates/main Sources
    Hit http://us.archive.ubuntu.com karmic-updates/restricted Sources
    Hit http://us.archive.ubuntu.com karmic-updates/universe Packages
    Hit http://us.archive.ubuntu.com karmic-updates/universe Sources
    Hit http://us.archive.ubuntu.com karmic-updates/multiverse Packages
    Ign http://security.ubuntu.com karmic-security/main Translation-en_US
    Ign http://security.ubuntu.com karmic-security/restricted Translation-en_US
    Hit http://us.archive.ubuntu.com karmic-updates/multiverse Sources
    Ign http://security.ubuntu.com karmic-security/universe Translation-en_US
    Ign http://security.ubuntu.com karmic-security/multiverse Translation-en_US
    Hit http://security.ubuntu.com karmic-security Release
    Hit http://security.ubuntu.com karmic-security/main Packages
    Hit http://security.ubuntu.com karmic-security/restricted Packages
    Hit http://security.ubuntu.com karmic-security/main Sources
    Hit http://security.ubuntu.com karmic-security/restricted Sources
    Hit http://security.ubuntu.com karmic-security/universe Packages
    Hit http://security.ubuntu.com karmic-security/universe Sources
    Hit http://security.ubuntu.com karmic-security/multiverse Packages
    Hit http://security.ubuntu.com karmic-security/multiverse Sources
    Reading package lists... Done

    ubuntu:~$ sudo apt-get install b43-fwcutter
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
    linux-headers-2.6.31-14 linux-headers-2.6.31-14-generic
    Use 'apt-get autoremove' to remove them.
    The following NEW packages will be installed:
    b43-fwcutter
    0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
    Need to get 0B/18.1kB of archives.
    After this operation, 115kB of additional disk space will be used.
    Media change: please insert the disc labeled
    'Ubuntu 9.10 _Karmic Koala_ - Release i386 (20091028.5)'
    in the drive '/cdrom/' and press enter

    Media change: please insert the disc labeled
    'Ubuntu 9.10 _Karmic Koala_ - Release i386 (20091028.5)'
    in the drive '/cdrom/' and press enter
    Advanced reply Adv Reply  
  8. November 28th, 2009 #608
    sharobim
    sharobim is offline Spilled the Beans
    Join Date
    Nov 2009
    Beans
    16

    Re: Comprehensive ndiswrapper troubleshooting guide

    Thanks,I reverted back to yesterday's configuration and got back a wireless connection OK
    To answer your query, yes if I connect right after having an Ethernet connection it work - in this case it took quite some time without Ethernet cable - but I got a wireless connect after many automatic retries (22 minutes).

    I feel sorry to give you trouble again - Thanks


    mike@mike-laptop:~$ ifconfig
    eth0 Link encap:Ethernet HWaddr 00:11:43:42:71:1a
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:11

    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:8 errors:0 dropped:0 overruns:0 frame:0
    TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:480 (480.0 B) TX bytes:480 (480.0 B)

    wlan0 Link encap:Ethernet HWaddr 00:0e:9b:d5:85:27
    inet addr:192.168.2.12 Bcast:192.168.2.255 Mask:255.255.255.0
    inet6 addr: fe80::20e:9bff:fed5:8527/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:3945 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1834 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:664615 (664.6 KB) TX bytes:229102 (229.1 KB)
    Interrupt:5 Memory:fafee000-faff0000

    mike@mike-laptop:~$ iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    wlan0 IEEE 802.11g ESSID:"Mike's"
    Mode:Managed Frequency:2.437 GHz Access Point: 00:24:56:2E:EF:B9
    Bit Rate=54 Mb/s Tx-Power:32 dBm
    RTS thr:2347 B Fragment thr:2346 B
    Power Managementff
    Link Quality:96/100 Signal level:-34 dBm Noise level:-96 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    mike@mike-laptop:~$



    Missing some data from x window here....


    ort 67 interval 9
    Nov 28 08:15:12 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    Nov 28 08:15:22 mike-laptop kernel: [ 59.510078] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:15:24 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
    Nov 28 08:15:28 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:15:28 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:15:28 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:15:29 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:15:29 mike-laptop kernel: [ 66.675568] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:15:29 mike-laptop kernel: [ 66.974340] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    Nov 28 08:15:29 mike-laptop kernel: [ 67.456252] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 08:15:31 mike-laptop avahi-daemon[1012]: Registering new address record for fe80::20e:9bff:fed5:8527 on wlan0.*.
    Nov 28 08:15:40 mike-laptop kernel: [ 77.916037] wlan0: no IPv6 routers present
    Nov 28 08:15:43 mike-laptop avahi-autoipd(wlan0)[2214]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 110).
    Nov 28 08:15:43 mike-laptop avahi-autoipd(wlan0)[2214]: Successfully called chroot().
    Nov 28 08:15:43 mike-laptop avahi-autoipd(wlan0)[2214]: Successfully dropped root privileges.
    Nov 28 08:15:43 mike-laptop avahi-autoipd(wlan0)[2214]: Starting with address 169.254.7.155
    Nov 28 08:15:48 mike-laptop avahi-autoipd(wlan0)[2214]: Callout BIND, address 169.254.7.155 on interface wlan0
    Nov 28 08:15:48 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:15:48 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:15:48 mike-laptop avahi-daemon[1012]: Registering new address record for 169.254.7.155 on wlan0.IPv4.
    Nov 28 08:15:52 mike-laptop avahi-autoipd(wlan0)[2214]: Successfully claimed IP address 169.254.7.155
    Nov 28 08:16:04 mike-laptop avahi-autoipd(wlan0)[2214]: Got SIGTERM, quitting.
    Nov 28 08:16:04 mike-laptop avahi-autoipd(wlan0)[2214]: Callout STOP, address 169.254.7.155 on interface wlan0
    Nov 28 08:16:04 mike-laptop avahi-daemon[1012]: Withdrawing address record for 169.254.7.155 on wlan0.
    Nov 28 08:16:04 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:16:04 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:16:05 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:16:05 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:16:09 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:16:17 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
    Nov 28 08:16:30 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
    Nov 28 08:16:50 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Nov 28 08:17:00 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Nov 28 08:17:00 mike-laptop dhclient: DHCPREQUEST of 192.168.2.12 on wlan0 to 255.255.255.255 port 67
    Nov 28 08:17:02 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.12.
    Nov 28 08:17:02 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:17:02 mike-laptop avahi-daemon[1012]: Registering new address record for 192.168.2.12 on wlan0.IPv4.
    Nov 28 08:17:20 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:17:20 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:17:20 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:17:20 mike-laptop avahi-daemon[1012]: Withdrawing address record for 192.168.2.12 on wlan0.
    Nov 28 08:17:20 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.12.
    Nov 28 08:17:20 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:17:20 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:17:20 mike-laptop avahi-daemon[1012]: Withdrawing address record for fe80::20e:9bff:fed5:8527 on wlan0.
    Nov 28 08:17:20 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:17:31 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:17:31 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:17:32 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:17:32 mike-laptop kernel: [ 189.570854] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:17:32 mike-laptop kernel: [ 189.765722] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    Nov 28 08:17:32 mike-laptop kernel: [ 190.244387] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 08:17:34 mike-laptop avahi-daemon[1012]: Registering new address record for fe80::20e:9bff:fed5:8527 on wlan0.*.
    Nov 28 08:17:43 mike-laptop kernel: [ 200.800039] wlan0: no IPv6 routers present
    Nov 28 08:18:08 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:18:08 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:18:12 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:18:20 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:18:28 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:18:36 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    Nov 28 08:18:48 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    Nov 28 08:18:52 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Nov 28 08:18:58 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Nov 28 08:19:00 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Nov 28 08:19:05 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
    Nov 28 08:19:10 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
    Nov 28 08:19:13 mike-laptop avahi-autoipd(wlan0)[2609]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 110).
    Nov 28 08:19:13 mike-laptop avahi-autoipd(wlan0)[2609]: Successfully called chroot().
    Nov 28 08:19:13 mike-laptop avahi-autoipd(wlan0)[2609]: Successfully dropped root privileges.
    Nov 28 08:19:13 mike-laptop avahi-autoipd(wlan0)[2609]: Starting with address 169.254.7.155
    Nov 28 08:19:18 mike-laptop avahi-autoipd(wlan0)[2609]: Callout BIND, address 169.254.7.155 on interface wlan0
    Nov 28 08:19:18 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:19:18 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:19:18 mike-laptop avahi-daemon[1012]: Registering new address record for 169.254.7.155 on wlan0.IPv4.
    Nov 28 08:19:22 mike-laptop avahi-autoipd(wlan0)[2609]: Successfully claimed IP address 169.254.7.155
    Nov 28 08:19:24 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Nov 28 08:19:35 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Nov 28 08:19:42 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Nov 28 08:19:57 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:19:57 mike-laptop avahi-autoipd(wlan0)[2609]: SIOCSIFFLAGS failed: Permission denied
    Nov 28 08:19:57 mike-laptop avahi-autoipd(wlan0)[2609]: Callout STOP, address 169.254.7.155 on interface wlan0
    Nov 28 08:19:57 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:19:57 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:19:57 mike-laptop avahi-daemon[1012]: Withdrawing address record for fe80::20e:9bff:fed5:8527 on wlan0.
    Nov 28 08:19:57 mike-laptop avahi-daemon[1012]: Withdrawing address record for 169.254.7.155 on wlan0.
    Nov 28 08:19:57 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:19:57 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:19:58 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:19:58 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:19:58 mike-laptop kernel: [ 335.632596] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:19:58 mike-laptop kernel: [ 335.784324] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    Nov 28 08:19:58 mike-laptop kernel: [ 336.236354] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 08:20:00 mike-laptop avahi-daemon[1012]: Registering new address record for fe80::20e:9bff:fed5:8527 on wlan0.*.
    Nov 28 08:20:09 mike-laptop kernel: [ 346.616044] wlan0: no IPv6 routers present
    Nov 28 08:20:34 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:20:34 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:20:38 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Nov 28 08:20:44 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Nov 28 08:20:50 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Nov 28 08:21:00 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
    Nov 28 08:21:17 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Nov 28 08:21:27 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:21:35 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
    Nov 28 08:21:39 mike-laptop avahi-autoipd(wlan0)[2825]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 110).
    Nov 28 08:21:39 mike-laptop avahi-autoipd(wlan0)[2825]: Successfully called chroot().
    Nov 28 08:21:39 mike-laptop avahi-autoipd(wlan0)[2825]: Successfully dropped root privileges.
    Nov 28 08:21:39 mike-laptop avahi-autoipd(wlan0)[2825]: Starting with address 169.254.7.155
    Nov 28 08:21:44 mike-laptop avahi-autoipd(wlan0)[2825]: Callout BIND, address 169.254.7.155 on interface wlan0
    Nov 28 08:21:44 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:21:44 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:21:44 mike-laptop avahi-daemon[1012]: Registering new address record for 169.254.7.155 on wlan0.IPv4.
    Nov 28 08:21:48 mike-laptop avahi-autoipd(wlan0)[2825]: Successfully claimed IP address 169.254.7.155
    Nov 28 08:21:52 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:21:52 mike-laptop avahi-autoipd(wlan0)[2825]: SIOCSIFFLAGS failed: Permission denied
    Nov 28 08:21:52 mike-laptop avahi-autoipd(wlan0)[2825]: Callout STOP, address 169.254.7.155 on interface wlan0
    Nov 28 08:21:52 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:21:52 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:21:52 mike-laptop avahi-daemon[1012]: Withdrawing address record for fe80::20e:9bff:fed5:8527 on wlan0.
    Nov 28 08:21:52 mike-laptop avahi-daemon[1012]: Withdrawing address record for 169.254.7.155 on wlan0.
    Nov 28 08:21:52 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:21:52 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:21:53 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:21:53 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:21:53 mike-laptop kernel: [ 450.568591] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:21:53 mike-laptop kernel: [ 450.720350] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    Nov 28 08:21:53 mike-laptop kernel: [ 451.176335] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 08:21:54 mike-laptop avahi-daemon[1012]: Registering new address record for fe80::20e:9bff:fed5:8527 on wlan0.*.
    Nov 28 08:22:03 mike-laptop kernel: [ 461.236037] wlan0: no IPv6 routers present
    Nov 28 08:22:29 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:22:29 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:22:30 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Nov 28 08:22:37 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:22:45 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    Nov 28 08:22:59 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
    Nov 28 08:23:15 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
    Nov 28 08:23:30 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 1
    Nov 28 08:23:31 mike-laptop avahi-autoipd(wlan0)[2991]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 110).
    Nov 28 08:23:31 mike-laptop avahi-autoipd(wlan0)[2991]: Successfully called chroot().
    Nov 28 08:23:31 mike-laptop avahi-autoipd(wlan0)[2991]: Successfully dropped root privileges.
    Nov 28 08:23:31 mike-laptop avahi-autoipd(wlan0)[2991]: Starting with address 169.254.7.155
    Nov 28 08:23:35 mike-laptop avahi-autoipd(wlan0)[2991]: Callout BIND, address 169.254.7.155 on interface wlan0
    Nov 28 08:23:35 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:23:35 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:23:35 mike-laptop avahi-daemon[1012]: Registering new address record for 169.254.7.155 on wlan0.IPv4.
    Nov 28 08:23:39 mike-laptop avahi-autoipd(wlan0)[2991]: Successfully claimed IP address 169.254.7.155
    Nov 28 08:23:47 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:23:47 mike-laptop avahi-autoipd(wlan0)[2991]: SIOCSIFFLAGS failed: Permission denied
    Nov 28 08:23:47 mike-laptop avahi-autoipd(wlan0)[2991]: Callout STOP, address 169.254.7.155 on interface wlan0
    Nov 28 08:23:47 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:23:47 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:23:47 mike-laptop avahi-daemon[1012]: Withdrawing address record for fe80::20e:9bff:fed5:8527 on wlan0.
    Nov 28 08:23:47 mike-laptop avahi-daemon[1012]: Withdrawing address record for 169.254.7.155 on wlan0.
    Nov 28 08:23:47 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:23:47 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:23:48 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:23:48 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:23:48 mike-laptop kernel: [ 565.587484] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:23:48 mike-laptop kernel: [ 565.739079] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    Nov 28 08:23:48 mike-laptop kernel: [ 566.188325] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 08:23:49 mike-laptop avahi-daemon[1012]: Registering new address record for fe80::20e:9bff:fed5:8527 on wlan0.*.
    Nov 28 08:23:50 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
    Nov 28 08:23:55 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Nov 28 08:23:58 mike-laptop kernel: [ 576.432037] wlan0: no IPv6 routers present
    Nov 28 08:24:01 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:24:09 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:24:17 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    Nov 28 08:24:24 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:24:24 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:24:26 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:24:31 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    Nov 28 08:24:34 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
    Nov 28 08:24:43 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Nov 28 08:24:45 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Nov 28 08:24:51 mike-laptop avahi-autoipd(wlan0)[3155]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 110).
    Nov 28 08:24:51 mike-laptop avahi-autoipd(wlan0)[3155]: Successfully called chroot().
    Nov 28 08:24:51 mike-laptop avahi-autoipd(wlan0)[3155]: Successfully dropped root privileges.
    Nov 28 08:24:51 mike-laptop avahi-autoipd(wlan0)[3155]: Starting with address 169.254.7.155
    Nov 28 08:24:53 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
    Nov 28 08:24:55 mike-laptop avahi-autoipd(wlan0)[3155]: Callout BIND, address 169.254.7.155 on interface wlan0
    Nov 28 08:24:55 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:24:55 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:24:55 mike-laptop avahi-daemon[1012]: Registering new address record for 169.254.7.155 on wlan0.IPv4.
    Nov 28 08:24:59 mike-laptop avahi-autoipd(wlan0)[3155]: Successfully claimed IP address 169.254.7.155
    Nov 28 08:25:12 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Nov 28 08:25:23 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
    Nov 28 08:25:32 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:25:32 mike-laptop avahi-autoipd(wlan0)[3155]: SIOCSIFFLAGS failed: Permission denied
    Nov 28 08:25:32 mike-laptop avahi-autoipd(wlan0)[3155]: Callout STOP, address 169.254.7.155 on interface wlan0
    Nov 28 08:25:32 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:25:32 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:25:32 mike-laptop avahi-daemon[1012]: Withdrawing address record for fe80::20e:9bff:fed5:8527 on wlan0.
    Nov 28 08:25:32 mike-laptop avahi-daemon[1012]: Withdrawing address record for 169.254.7.155 on wlan0.
    Nov 28 08:25:32 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:25:32 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:25:33 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:25:33 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:25:33 mike-laptop kernel: [ 670.561984] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:25:33 mike-laptop kernel: [ 670.713801] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    Nov 28 08:25:33 mike-laptop kernel: [ 671.164326] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 08:25:35 mike-laptop avahi-daemon[1012]: Registering new address record for fe80::20e:9bff:fed5:8527 on wlan0.*.
    Nov 28 08:25:44 mike-laptop kernel: [ 682.040039] wlan0: no IPv6 routers present
    Nov 28 08:26:09 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:26:09 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:26:11 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Nov 28 08:26:18 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:26:26 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    Nov 28 08:26:40 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:26:48 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Nov 28 08:26:58 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Nov 28 08:27:09 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
    Nov 28 08:27:12 mike-laptop avahi-autoipd(wlan0)[3352]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 110).
    Nov 28 08:27:12 mike-laptop avahi-autoipd(wlan0)[3352]: Successfully called chroot().
    Nov 28 08:27:12 mike-laptop avahi-autoipd(wlan0)[3352]: Successfully dropped root privileges.
    Nov 28 08:27:12 mike-laptop avahi-autoipd(wlan0)[3352]: Starting with address 169.254.7.155
    Nov 28 08:27:17 mike-laptop avahi-autoipd(wlan0)[3352]: Callout BIND, address 169.254.7.155 on interface wlan0
    Nov 28 08:27:17 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:27:17 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:27:17 mike-laptop avahi-daemon[1012]: Registering new address record for 169.254.7.155 on wlan0.IPv4.
    Nov 28 08:27:21 mike-laptop avahi-autoipd(wlan0)[3352]: Successfully claimed IP address 169.254.7.155
    Nov 28 08:27:38 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Nov 28 08:27:45 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    Nov 28 08:27:56 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    Nov 28 08:28:10 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
    Nov 28 08:28:23 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
    Nov 28 08:28:57 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:28:57 mike-laptop avahi-autoipd(wlan0)[3352]: SIOCSIFFLAGS failed: Permission denied
    Nov 28 08:28:57 mike-laptop avahi-autoipd(wlan0)[3352]: Callout STOP, address 169.254.7.155 on interface wlan0
    Nov 28 08:28:57 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:28:57 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:28:57 mike-laptop avahi-daemon[1012]: Withdrawing address record for fe80::20e:9bff:fed5:8527 on wlan0.
    Nov 28 08:28:57 mike-laptop avahi-daemon[1012]: Withdrawing address record for 169.254.7.155 on wlan0.
    Nov 28 08:28:57 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:28:57 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:28:58 mike-laptop dhclient: DHCPRELEASE on wlan0 to 192.168.2.1 port 67
    Nov 28 08:28:58 mike-laptop dhclient: receive_packet failed on wlan0: Network is down
    Nov 28 08:28:58 mike-laptop kernel: [ 875.595572] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    Nov 28 08:28:58 mike-laptop kernel: [ 875.747135] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    Nov 28 08:28:58 mike-laptop kernel: [ 876.200339] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    Nov 28 08:29:00 mike-laptop avahi-daemon[1012]: Registering new address record for fe80::20e:9bff:fed5:8527 on wlan0.*.
    Nov 28 08:29:09 mike-laptop kernel: [ 886.636040] wlan0: no IPv6 routers present
    Nov 28 08:29:34 mike-laptop dhclient: Listening on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:29:34 mike-laptop dhclient: Sending on LPF/wlan0/00:0e:9b:d5:85:27
    Nov 28 08:29:38 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
    Nov 28 08:29:41 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Nov 28 08:29:47 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    Nov 28 08:29:54 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    Nov 28 08:30:02 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    Nov 28 08:30:12 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
    Nov 28 08:30:21 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
    Nov 28 08:30:36 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
    Nov 28 08:30:39 mike-laptop avahi-autoipd(wlan0)[3586]: Found user 'avahi-autoipd' (UID 104) and group 'avahi-autoipd' (GID 110).
    Nov 28 08:30:39 mike-laptop avahi-autoipd(wlan0)[3586]: Successfully called chroot().
    Nov 28 08:30:39 mike-laptop avahi-autoipd(wlan0)[3586]: Successfully dropped root privileges.
    Nov 28 08:30:39 mike-laptop avahi-autoipd(wlan0)[3586]: Starting with address 169.254.7.155
    Nov 28 08:30:44 mike-laptop avahi-autoipd(wlan0)[3586]: Callout BIND, address 169.254.7.155 on interface wlan0
    Nov 28 08:30:44 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:30:44 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:30:44 mike-laptop avahi-daemon[1012]: Registering new address record for 169.254.7.155 on wlan0.IPv4.
    Nov 28 08:30:48 mike-laptop avahi-autoipd(wlan0)[3586]: Successfully claimed IP address 169.254.7.155
    Nov 28 08:31:39 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
    Nov 28 08:31:39 mike-laptop dhclient: DHCPREQUEST of 192.168.2.12 on wlan0 to 255.255.255.255 port 67
    Nov 28 08:31:40 mike-laptop avahi-autoipd(wlan0)[3586]: Got SIGTERM, quitting.
    Nov 28 08:31:40 mike-laptop avahi-autoipd(wlan0)[3586]: Callout STOP, address 169.254.7.155 on interface wlan0
    Nov 28 08:31:40 mike-laptop avahi-daemon[1012]: Withdrawing address record for 169.254.7.155 on wlan0.
    Nov 28 08:31:40 mike-laptop avahi-daemon[1012]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 169.254.7.155.
    Nov 28 08:31:40 mike-laptop avahi-daemon[1012]: Interface wlan0.IPv4 no longer relevant for mDNS.
    Nov 28 08:31:40 mike-laptop avahi-daemon[1012]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.2.12.
    Nov 28 08:31:40 mike-laptop avahi-daemon[1012]: New relevant interface wlan0.IPv4 for mDNS.
    Nov 28 08:31:40 mike-laptop avahi-daemon[1012]: Registering new address record for 192.168.2.12 on wlan0.IPv4.
    Nov 28 08:37:26 mike-laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
    Nov 28 08:37:26 mike-laptop dhclient: DHCPREQUEST of 192.168.2.12 on wlan0 to 255.255.255.255 port 67
    mike@mike-laptop:~$



    mike@mike-laptop:~$ dmesg | grep -e ndis -e wlan
    [ 6.704806] ndiswrapper version 1.55 loaded (smp=yes, preempt=no)
    [ 7.484114] ndiswrapper: driver bcmwl5 (Broadcom,10/12/2006, 4.100.15.5) loaded
    [ 7.484431] ndiswrapper 0000:02:03.0: PCI INT A -> Link[LNKB] -> GSI 5 (level, low) -> IRQ 5
    [ 7.492331] ndiswrapper: using IRQ 5
    [ 7.856870] wlan0: ethernet device 00:0e:9b:d5:85:27 using NDIS driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS Network Adapter', 14E4:4318.5.conf
    [ 7.856913] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
    [ 7.856994] usbcore: registered new interface driver ndiswrapper
    [ 11.915999] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 18.664981] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 19.132318] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 29.968031] wlan0: no IPv6 routers present
    [ 59.510078] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 66.675568] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 66.974340] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 67.456252] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 77.916037] wlan0: no IPv6 routers present
    [ 189.570854] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 189.765722] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 190.244387] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 200.800039] wlan0: no IPv6 routers present
    [ 335.632596] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 335.784324] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 336.236354] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 346.616044] wlan0: no IPv6 routers present
    [ 450.568591] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 450.720350] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 451.176335] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 461.236037] wlan0: no IPv6 routers present
    [ 565.587484] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 565.739079] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 566.188325] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 576.432037] wlan0: no IPv6 routers present
    [ 670.561984] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 670.713801] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 671.164326] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 682.040039] wlan0: no IPv6 routers present
    [ 875.595572] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 875.747135] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 876.200339] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 886.636040] wlan0: no IPv6 routers present
    mike@mike-laptop:~$
    Advanced reply Adv Reply  
  9. November 28th, 2009 #609
    bkratz
    bkratz is offline Ubuntu addict and loving it
    Join Date
    Apr 2009
    Beans
    2,601

    Re: Comprehensive ndiswrapper troubleshooting guide

    sharobim

    [ 189.570854] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 189.765722] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 190.244387] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 200.800039] wlan0: no IPv6 routers present
    [ 335.632596] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 335.784324] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 336.236354] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 346.616044] wlan0: no IPv6 routers present
    [ 450.568591] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 450.720350] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 451.176335] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 461.236037] wlan0: no IPv6 routers present
    [ 565.587484] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 565.739079] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 566.188325] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 576.432037] wlan0: no IPv6 routers present
    [ 670.561984] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 670.713801] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 671.164326] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 682.040039] wlan0: no IPv6 routers present
    [ 875.595572] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 875.747135] ndiswrapper (iw_set_auth:1602): invalid cmd 12
    [ 876.200339] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
    [ 886.636040] wlan0: no IPv6 routers present
    mike@mike-laptop:~$



    It looks like you may be seeing the same thing I have---

    https://bugs.launchpad.net/ubuntu/+s...er/+bug/459716
    Advanced reply Adv Reply  
  10. November 29th, 2009 #610
    pytheas22's Avatar
    pytheas22
    pytheas22 is offline Staff Emeritus
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    vancousa: I don't know what's going on with the package manager not liking your CD--that's probably a separate issue--but instead of fighting with that, please run these commands, which will install the firmware another way (without using the b43-fwcutter package):
    Code:
    wget http://burnthesorbonne.com/files/b43_firmware.tar.gz
tar -xzvf b43_firmware.tar.gz 
rm b43_firmware.tar.gz 
sudo mv b43* /lib/firmware
echo b43 | sudo tee -a /etc/modules
    Then reboot and hopefully things will finally work.

    sharobim: I'm on my way out now and need to do some more thinking/research on what to do for you, but will respond by tomorrow. Apologies for the delay.

    In the meantime you could try seeing if disabling encryption on your router makes any difference, which would tell us whether or not your issue could be the same as the one described in the bug report that bkratz linked to in the post above. But I kind of suspect that's not the problem.

    Personal site     | Understanding Wireless Chipsets | Troubleshooting ndiswrapper | The VAR Guy
    Advanced reply Adv Reply  
Page 61 of 121 FirstFirst ... 1151596061626371111 ... LastLast
« Previous Thread | Next Thread »

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
  •  

Ubuntu Forums Code of Conduct