Page 1 of 2 12 LastLast
Results 1 to 10 of 19

Thread: NDISwrapper Yes, lspci No, iwconfig No

  1. #1
    Join Date
    Apr 2007
    Beans
    Hidden!

    Arrow NDISwrapper Yes, lspci No, iwconfig No

    Hi all,

    I'm having a little bit of problems getting WiFi to work on my new ASUS M51VA-AS045G. I know it works, as it is fine with the Vista installation.

    Anyways, on to the troubleshooting.

    The ASUS WiFi driver was downloaded from here.

    I have installed NDISwrapper 1.53 from source
    ndiswrapper -v
    utils version: '1.9', utils version needed by module: '1.9'
    module details:
    filename: /lib/modules/2.6.24-19-generic/misc/ndiswrapper.ko
    version: 1.53
    vermagic: 2.6.24-19-generic SMP mod_unload 586
    The driver/device seems to be installed OK
    ndiswrapper -l
    netw5v32 : driver installed
    device (8086:4232) present
    I have created a script to disable modules SSB and B43
    cat /etc/init.d/wirelessfix.sh
    #!/bin/bash

    modprobe -r b44
    modprobe -r b43
    modprobe -r ssb
    modprobe -r ndiswrapper
    modprobe ndiswrapper
    modprobe b44
    Now for the bits that don't really make sense or line up with anybody else's experience.

    ndiswrapper -m seems to have written the following file
    cat /etc/modprobe.d/ndiswrapper
    alias wlan0 ndiswrapper
    iwconfig does not detect a wireless device
    iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.
    lspci does not list the wireless card correctly
    lspci
    06:00.0 Network controller: Intel Corporation Unknown device 4232
    Does anyone know why NDISwrapper thinks that the driver is installed and the device is present, yet lspci does not recognise the card and iwconfig does not recognise a wireless device?

    Any help is greatly appreciated!

    Cheers,
    Dave

  2. #2
    Join Date
    Jan 2007
    Location
    ~/PA/USA
    Beans
    1,983
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: NDISwrapper Yes, lspci No, iwconfig No

    I added these to my /etc/modprobe.d/blacklist file:

    # everything to do with wireless
    blacklist b44
    blacklist ipv6
    blacklist b43
    blacklist b43legacy
    blacklist ssb
    blacklist agpgart

    I tried to use the wirelessfix.sh script and found that even after a reboot I had to re run the script for it to work. Now, since I've added the modules to the blacklist, after a reboot my ndiswrapper works.

    This may not work for you but it's worth a try......

  3. #3
    Join Date
    Apr 2007
    Beans
    Hidden!

    Re: NDISwrapper Yes, lspci No, iwconfig No

    I tried those blacklistings and also stopped the wirelessfix.sh script from running.

    Even after modprobing the ndiswrapper, I still get the same problems

    davidw@Laphroaig:~$ lsmod | grep b4
    davidw@Laphroaig:~$ lsmod | grep ssb
    davidw@Laphroaig:~$ lsmod | grep ndiswrapper
    ndiswrapper 193436 0
    usbcore 146028 8 ndiswrapper,hci_usb,uvcvideo,usb_storage,libusual, ehci_hcd,uhci_hcd
    davidw@Laphroaig:~$ cat /etc/modprobe.d/ndiswrapper
    alias wlan0 ndiswrapper
    davidw@Laphroaig:~$ lspci | grep Network
    06:00.0 Network controller: Intel Corporation Unknown device 4232
    davidw@Laphroaig:~$ ndiswrapper -l
    netw5v32 : driver installed
    device (8086:4232) present
    davidw@Laphroaig:~$ iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.
    Thanks for the help anyway!
    Last edited by davedave; July 31st, 2008 at 04:59 AM.

  4. #4
    Join Date
    Jan 2007
    Beans
    5,549

    Re: NDISwrapper Yes, lspci No, iwconfig No

    i remember having a similar issue once.. ndiswrapper said it was present but it wasnt quite there.. but a reboot worked for me

  5. #5
    Join Date
    Apr 2007
    Beans
    Hidden!

    Re: NDISwrapper Yes, lspci No, iwconfig No

    Thanks, though I have already tried that windows approach

  6. #6
    Join Date
    Jan 2007
    Location
    ~/PA/USA
    Beans
    1,983
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: NDISwrapper Yes, lspci No, iwconfig No

    What do you get with the output of:
    lshw -C network

  7. #7
    Join Date
    Apr 2007
    Beans
    Hidden!

    Re: NDISwrapper Yes, lspci No, iwconfig No

    Quote Originally Posted by cdtech View Post
    What do you get with the output of:
    lshw -C network
    sudo lshw -C network
    *-network UNCLAIMED
    description: Network controller
    product: Intel Corporation
    vendor: Intel Corporation
    physical id: 0
    bus info: pci@0000:06:00.0
    version: 00
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress bus_master cap_list
    configuration: latency=0
    *-network
    description: Ethernet interface
    product: RTL8111/8168B PCI Express Gigabit Ethernet controller
    vendor: Realtek Semiconductor Co., Ltd.
    physical id: 0
    bus info: pci@0000:07:00.0
    logical name: eth0
    version: 02
    serial: 00:22:15:2a:b4:1b
    size: 100MB/s
    capacity: 1GB/s
    width: 64 bits
    clock: 33MHz
    capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
    configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.2LK duplex=full ip=10.5.1.44 latency=0 link=yes module=r8169 multicast=yes port=twisted pair speed=100MB/s

  8. #8
    Join Date
    Jan 2007
    Location
    ~/PA/USA
    Beans
    1,983
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: NDISwrapper Yes, lspci No, iwconfig No

    Your "logical name: eth0" is incorrect. I'm looking through my notes......

  9. #9
    Join Date
    Apr 2007
    Beans
    Hidden!

    Re: NDISwrapper Yes, lspci No, iwconfig No

    That's on the LAN NIC though

  10. #10
    Join Date
    Jan 2007
    Location
    ~/PA/USA
    Beans
    1,983
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: NDISwrapper Yes, lspci No, iwconfig No

    Ok, go to /etc/udev/rules.d and edit the file "70-persistent-net.rules":
    sudo gedit /etc/udev/rules.d/70-persistent-net.rules

    Look for the line:
    Code:
    # PCI device 0x14e4:0x4311 (ndiswrapper)
    SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1a:73:b5:7e:d1", ATTRS{type
    }=="1", NAME="wlan0"
    Yours will probably have the eth0 listed, just change that to wlan0

Page 1 of 2 12 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
  •