Page 20 of 121 FirstFirst ... 1018192021223070120 ... LastLast
Results 191 to 200 of 1210

Thread: Comprehensive ndiswrapper troubleshooting guide

  1. #191
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    My question is what do I have to do to get this wireless driver activated and in use as part of the boot up process. I switched between Ubuntu and WinXP many times during the day. It gets pretty annoying to have to go to the terminal to type in the code every time.
    Try running this command once:
    Code:
    echo wl | sudo tee -a /etc/modules
    Then reboot and see if your card is automatically up. If not, do this:

    1. type:

    Code:
    sudo gedit /etc/init.d/wifi-fix.sh
    A blank file will pop open. Put this into it:
    Code:
    #!/bin/bash
    
    #this script loads the 'wl' driver at boot; see http://ubuntuforums.org/showthread.php?t=885847&page=19 for more information
    
    modprobe -r b44 b43 ssb ndiswrapper wl
    modprobe wl
    2. now run these commands:
    Code:
    cd /etc/init.d
    sudo chmod +x wifi-fix.sh
    sudo update-rc.d wifi-fix.sh defaults
    This should take care of it if the first solution doesn't (try the first solution first because it's cleaner).

    As for the ethernet being unclaimed: have you applied all Ubuntu updates? From what Google told me, this should solve that issue, hopefully. If the updates don't help, please try booting into an older kernel and let me know if that makes a difference.
    Last edited by pytheas22; December 27th, 2008 at 07:31 PM.

  2. #192
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    Whoa. You say ndiswrapper will not validate encrypted connections? I was advised to disable fwcutter and use just the ndiswrapper. I did that and I can only connect wirelessly to an unencrypted access point. I have bcmwl5 drivers installed. Dale.
    Dale: no, I didn't mean that ndiswrapper can't connect to encrypted networks. In the case above, with that particular wireless card, there seem to be problems with WEP and WPA when using ndiswrapper as a driver. But in general, ndiswrapper is perfectly capable of connecting to networks that use WEP, WPA, WPA-enterprise, etc.

    Since you have a Broadcom-based wireless card, you should really not need to use ndiswrapper, as Broadcom cards have very good native Linux drivers. If you could please post the output of these commands, I'll try to help you get set up with a better driver:
    Code:
    lshw -C Network
    lspci -nn | grep -i broadcom
    uname -mr
    Also, if you use wicd (see post #178 for installation instructions), you *might* be able to connect to a protected network under your current configuration, depending on where exactly the problem lies. It might be worth a shot before we go and switch out your drivers completely.

  3. #193
    Join Date
    Aug 2006
    Beans
    17

    Re: Comprehensive ndiswrapper troubleshooting guide

    I've been banging my head against the wall trying to get ndiswrapper working with my msi wind( 8187SE wireless), tried using no encryption, wep and wpa, it can see the network every time, just not connect to it. No errors that I can find anywhere or anything.

    ndiswrapper -l shows it as installed and present,


    *-network
    description: Wireless interface
    product: Realtek Semiconductor Co., Ltd.
    vendor: Realtek Semiconductor Co., Ltd.
    physical id: 0
    bus info: pci@0000:02:00.0
    logical name: wlan0
    version: 22
    serial: 00:1d:92:cb:fe:29
    width: 32 bits
    clock: 33MHz
    capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
    configuration: broadcast=yes driver=ndiswrapper+net8187se driverversion=1.52+Realtek,08/22/2008,5.9071.0 latency=0 link=no module=ndiswrapper multicast=yes wireless=IEEE 802.11g


    [ 33.353471] ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
    [ 33.619794] ndiswrapper: driver net8187se (Realtek,09/17/2008,5.9073.0917.2008) loaded
    [ 33.781275] ndiswrapper: using IRQ 17
    [ 34.587976] wlan0: ethernet device 00:1d:92:cb:fe:29 using NDIS driver: net8187se, version: 0x500a5, NDIS version: 0x500, vendor: 'Realtek RTL8185 Wireless LAN (Mini-)PCI NIC ', 10EC:8199.5.conf
    [ 34.588022] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
    [ 34.588130] usbcore: registered new interface driver ndiswrapper
    [ 56.175820] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 105.826432] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 106.804198] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 191.847657] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 273.700518] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 300.675885] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 359.037601] ndiswrapper: device wlan0 removed
    [ 359.037957] usbcore: deregistering interface driver ndiswrapper
    [ 359.096085] ndiswrapper version 1.52 loaded (smp=yes, preempt=no)
    [ 359.120388] ndiswrapper: driver net8187se (Realtek,08/22/2008,5.9071.0822.2008) loaded
    [ 359.194916] ndiswrapper: using IRQ 17
    [ 359.363975] wlan0: ethernet device 00:1d:92:cb:fe:29 using NDIS driver: net8187se, version: 0x500a5, NDIS version: 0x500, vendor: 'Realtek RTL8185 Wireless LAN (Mini-)PCI NIC ', 10EC:8199.5.conf
    [ 359.366248] wlan0: encryption modes supported: WEP; TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
    [ 359.367831] usbcore: registered new interface driver ndiswrapper
    [ 362.893742] wlan0: no IPv6 routers present
    [ 371.717247] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 372.830659] ADDRCONF(NETDEV_UP): wlan0: link is not ready
    [ 465.667119] ADDRCONF(NETDEV_UP): wlan0: link is not ready


    I seem to be getting a lot of wlan0 link not readies...but I don't know if thats a problem or not?

  4. #194
    Join Date
    Dec 2008
    Beans
    24

    Re: Comprehensive ndiswrapper troubleshooting guide

    Hiya - thanks again for all your hard work - i did manage to disable security on my router, and yes - i got connected! obviously not a permanent solution though... so now am doing fresh re-install of 8.10 as didn't seem to be able to get back to the original linux driver...

  5. #195
    Join Date
    Dec 2008
    Beans
    24

    Re: Comprehensive ndiswrapper troubleshooting guide

    Dear Pytheus - I reinstalled ubuntu, and reloaded wicd - no joy in connecting - same thing happens - ie. it tries to connect for ages, but doesn't manage it. I have left wicd in operation - here is output of code: (have only included the parts relevant to the wireless network)

    lisa@lisa-Ubuntu-desktop:~$ lshw -C Network
    *-network:0
    description: Wireless interface
    physical id: 1
    logical name: wlan0
    serial: 00:18:4d:62:5a:51
    capabilities: ethernet physical wireless
    configuration: broadcast=yes multicast=yes wireless=IEEE 802.11bg


    lisa@lisa-Ubuntu-desktop:~$ dmesg | grep -e rtl -e wlan -e ndis
    [ 21.082541] phy0: hwaddr 00:18:4d:62:5a:51, RTL8187vB (default) V1 + rtl8225z2
    [ 21.082583] usbcore: registered new interface driver rtl8187
    [ 138.144984] wlan0: authenticate with AP 00:1d:68:0c:80:e7
    [ 138.344032] wlan0: authenticate with AP 00:1d:68:0c:80:e7
    [ 138.544026] wlan0: authenticate with AP 00:1d:68:0c:80:e7
    [ 138.744033] wlan0: authentication with AP 00:1d:68:0c:80:e7 timed out
    [ 153.170640] wlan0: authenticate with AP 00:1d:68:0c:80:e7
    [ 153.368032] wlan0: authenticate with AP 00:1d:68:0c:80:e7

    .. and the above repeated a number of times with the same output but different numbers in square brackets..

    lisa@lisa-Ubuntu-desktop:~$ wget google.com
    --2008-12-27 12:49:55-- http://google.com/
    Resolving google.com... failed: Name or service not known.
    wget: unable to resolve host address `google.com'

    lisa@lisa-Ubuntu-desktop:~$ host google.com
    cat /etc/rs;; connection timed out; no servers could be reached

    lisa@lisa-Ubuntu-desktop:~$ cat /etc/resolv.conf
    domain lan
    search lan
    nameserver 192.168.1.254

    lisa@lisa-Ubuntu-desktop:~$ wget 209.85.171.100
    --2008-12-27 12:50:28-- http://209.85.171.100/
    Connecting to 209.85.171.100:80... failed: Network is unreachable.
    lisa@lisa-Ubuntu-desktop:~$

    If I reload the network manager I have to reboot, and thereafter I have lost the original connection I had before re-installing wicd. Repeated the above commands and get identical output.

    Maybe I should get another wireless adaptor? Do you know of one which is more likely to work???

  6. #196
    Join Date
    Dec 2008
    Location
    Connecticut
    Beans
    22
    Distro
    Xubuntu 8.10 Intrepid Ibex

    Re: Comprehensive ndiswrapper troubleshooting guide

    Hi pytheas22,

    Thank you again for the details instructions.

    1. Method 1 is definitely cleaner but it did not work.

    2. Method 2 shows that the STA driver is activated and currently in use vs activated and not in use. However same as 1, there is not wireless connection and the icon does not move like it's trying to connect, just static.

    3. However, when I type in the
    sudo modprobe -r b44 b43 ssb ndiswrapper wl
    sudo modprobe wl

    Then again it works.

    This sounds really strange but I was extremely careful typing the codes for 1 and 2 and follow the directions to a t.

    I did something since yesterday. Blacklisted ndiswrapper, b44 b43 ssb. Still had to do the typing of code above.

    So that's my sorry story.


  7. #197
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    *I'm going to reply to three different people in this one post, so if you're one of those people, please make sure to scroll down and find the section relevant to you.

    taliosfalcon: like others, you may want to see if you have better luck connecting under wicd (see post #178 for instructions on installing it). This may do the trick, especially if you're trying to connect to a secured network. The way that Network Manager (the program that Ubuntu uses by default to connect) does WPA negotiation is sort of weird, and sometimes wicd does it more successfully.

    Another possible solution for you is to install native drivers for your card instead of ndiswrapper. I helped a friend get the wireless working on her Wind--same wireless card as yours--and the native driver, r8187b, works quite well. To install those drivers, run these commands (make sure you are online via ethernet first):
    Code:
    sudo apt-get install build-essential
    wget http://julienpecqueur.com/ftp/rtl8187se_linux_26.1023.0928.2008.tar.gz
    tar -xzvf rtl8187se_linux_26.1023.0928.2008.tar.gz
    cd rtl8187se*
    ./makedrv
    sudo modprobe -r ndiswrapper
    sudo ./wlan0up
    At this point, provided you haven't received any error messages, your card should be up and running until the next reboot. If this works, we can make the installation permanent so that the wireless will come up automatically.


    [note: if the process above fails, you can try an alternate installation method using Debian packages by running these commands:
    Code:
    wget http://boskastrona.ovh.org/download/linux-rtl8187se-modules-1023@2.6.27.7.11.deb
    sudo dpkg -i linux-rtl8187se-*.deb
    This should work for Ubuntu 8.10.]

    etherealethel: I'm afraid I don't have anything definite to tell you, but I found this post, which says that running this command solves the problem of the WG111v2 not connecting:
    Code:
    sudo iwconfig wlan0 rate 5.5M
    Does it help? If not, please post the output of this command:
    Code:
    lspci -nn
    husky55: try running these commands. I made a typo previously which probably screwed things up (I'll edit the original post to fix it), and the script that you created is probably not really running at boot. But running this once should fix that:
    Code:
    cd /etc/init.d
    sudo chmod +x wifi-fix.sh
    sudo update-rc.d wifi-fix.sh defaults
    The 'defaults' part is what I forgot before.

  8. #198
    Join Date
    Dec 2008
    Location
    Connecticut
    Beans
    22
    Distro
    Xubuntu 8.10 Intrepid Ibex

    Re: Comprehensive ndiswrapper troubleshooting guide

    Hey everybody, it's the holidays!!!

    Why are we doing this? Surely it's not because our jobs are at stake!!!

    I swore to my wife that I would not be fooling with computers today and during the holidays. But she had to do some errands. So here I am again.

    First, my thanks and best wishes to pytheas22 for a Happy New Year and I hope that the economy will get better in 2009 for all of us. It has been a dreadful year for a lot of people. But only in America do we swing from the right to the left in every few years. Yes we can.

    Frankly, as pointed out earlier, a reinstall of Ubuntu would solve some or most of my problems (since I don't know any better), but I want to learn this thing, this Ubuntu wireless business. Like the tale of the scorpion and the turtle crossing the river, the scorpion had promised the turtle not to kill the turtle in return for a free ride. but then the scorpion reneged and stung the turtle. When the turtle asked why did he did it, he said "it's in my nature." And so they both drowned.

    Anyway, I just want to wish everybody a Happy New Year and many thanks again to pytheas22 who has the grace and generosity to send me the correct code.

    The correct code works perfectly. How about that for an encore? Yes we can!!!

  9. #199
    Join Date
    Dec 2008
    Beans
    24

    Re: Comprehensive ndiswrapper troubleshooting guide

    Hi pytheus - I did come accross that thread too - but it didn't work - I have now tried plugging in a friend's d-link adaptor - DWL-G122 - and that seems to work just fine - even without using ndiswrapper - so fingers x'd and I'll see if it still works when i move the computer back upstairs!!!

    Incidentally I did come across another thread re. the netgear card that might mean something to you - i just don't have the competence to follow the instructions - something about disabling the IEEE80211 framework????

    http://linux-wless.passys.nl/languag...ws.english.php

    Anyway, thanks again for all your help on this - glad to see you're putting your PhD to good use!!!!!
    Hopefully I won't be posting any more desperate pleas for help....

  10. #200
    Join Date
    Aug 2007
    Location
    Paris
    Beans
    5,538
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Comprehensive ndiswrapper troubleshooting guide

    etherealethel: unfortunately, the information on that page that you linked to seems a bit outdated and I don't think is relevant any longer. Modern Linux kernels don't use the IEEE80211 framework at all anymore (it's been replaced by mac80211), and the Realtek driver referred to on that page has been replaced by a newer one that doesn't have these module-compatibility issues.

    However, that brings up one last thing which you might try, which is compiling the latest Linux wireless drivers. This will give you an updated version of the driver for your card, which may, if you're lucky, work better than the default one. To compile the latest wireless stack, first download the source code and save it to your desktop. Then run these commands:
    Code:
    sudo apt-get install build-essential
    cd ~/Desktop
    tar xjvf compat-wireless-2.6.tar.bz2 
    cd compat-wireless*
    make
    sudo make unload
    sudo make load
    At this point, see if you have any better luck connecting to your router. If so, we can make the changes permanent. Otherwise, rebooting your machine will make it default back to the stock Ubuntu wireless drivers.

    If not, the DWL-G122 is a good option for plug-and-play wireless--I have one myself (rev. C) and it works great with its Ralink chipset.

Page 20 of 121 FirstFirst ... 1018192021223070120 ... LastLast

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
  •