Find the answer to your Linux question:
Page 1 of 3 1 2 3 LastLast
Results 1 to 10 of 27
I have installed ndiswrapper. i attempt to setup my card, wlan0, and: root@kim:~# iwconfig lo no wireless extensions. eth0 no wireless extensions. sit0 no wireless extensions. wlan0 IEEE 802.11g ESSID:off/any ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Dec 2006
    Location
    Austin, Texas
    Posts
    26

    not working: ndiswrapper


    I have installed ndiswrapper. i attempt to setup my card, wlan0, and:
    root@kim:~# iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    sit0 no wireless extensions.

    wlan0 IEEE 802.11g ESSID:off/any
    Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
    Bit Rate:54 Mb/s Tx-Power:25 dBm
    RTS thr:2347 B Fragment thr:2346 B
    Encryption key:off
    Power Management:off
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    root@kim:~# iwconfig wlan0 essid Wireless
    root@kim:~# iwconfig
    lo no wireless extensions.

    eth0 no wireless extensions.

    sit0 no wireless extensions.

    wlan0 IEEE 802.11g ESSID:off/any
    Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
    Bit Rate:54 Mb/s Tx-Power:25 dBm
    RTS thr:2347 B Fragment thr:2346 B
    Encryption key:off
    Power Management:off
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    root@kim:~# iwlist wlan0 scan
    wlan0 No scan results
    root@kim:~#
    The folks over at ndiswrapper's site dont seem very helpful with this...

  2. #2
    Just Joined! Metaljaz's Avatar
    Join Date
    Jul 2006
    Posts
    53
    Assuming you are using Ubuntu since you did not say what distro you are using.
    To check if driver is loaded type this command from the terminal:

    sudo lsmod | grep <device driver>

    if the driver that is loading is not the driver that you want you will
    have to blacklist drivers that you do not wish to use.

  3. #3
    Just Joined!
    Join Date
    Dec 2006
    Location
    Austin, Texas
    Posts
    26
    Fedora 5. Anyway, I didn't think of that

    Will try soon.

  4. #4
    Just Joined!
    Join Date
    Dec 2006
    Location
    Austin, Texas
    Posts
    26
    I see only ndiswrapper; no other thing that looks like it even begins to have anything to do with wireless drivers or anything that would interfere. Also, the only ndiswrapper-related thing i see is ndiswrapper itself.

  5. #5
    Just Joined! Metaljaz's Avatar
    Join Date
    Jul 2006
    Posts
    53
    post more information about your wireless card so someone more familiar with fedora can assist you.

  6. #6
    Just Joined!
    Join Date
    Dec 2006
    Location
    Austin, Texas
    Posts
    26
    I don't know, exactly... it's whatever came in my laptop...

    lspci:
    ...
    05:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
    ...

  7. #7
    Just Joined! Metaljaz's Avatar
    Join Date
    Jul 2006
    Posts
    53
    Ok..based on the output of lspci you are using the bcm43xx chipset.
    Follow the link below and you should be up and running:

    http://fedoranews.org/mediawiki/inde...ng_Ndiswrapper

    here is another link. Do the initial part and then click on the ndiswrapper setup link.

    http://fedoramobile.org/fc-wireless/...8-ndiswrapper/

    Try the one that seems the easiest to you

  8. #8
    Just Joined!
    Join Date
    Mar 2005
    Location
    Washington State, US
    Posts
    6
    I'm running slack myself but I also have the bcm43xx chipset. A couple of sites that helped me are here:

    http://ndiswrapper.sourceforge.net/m...index.php/List

    and here:

    http://ndiswrapper.sourceforge.net/m...p/Installation

  9. #9
    Just Joined!
    Join Date
    Jun 2006
    Location
    The next brick house on the right.
    Posts
    63
    dime --

    You have downloaded, and presumably installed, ndiswrapper. Please run:

    Code:
    sudo ndiswrapper -l
    and that would be "-l" as in lower case L, not i or the number 1. Just to be sure !!

    The ndiswrapper executable provides the means for a Windows driver to be used within the Linux environment. This means that you need to bring in the Windows driver (both the .inf and the .sys files) to Linux and have ndiswrapper install them. The .inf and the .sys files will normally come from the driver CD that comes with the Broadcom-chipped card. At times (I know it's true for FC 6 and maybe FC 5 also) it is necessary to "blacklist" the driver that the kernel loads (i.e., "bcm43xx") so that the "true" driver can do its thing. That was definitely the case with my Kubuntu install and my Buffalo Broadcom 4318 card. Anyway, double-check at the ndiswrapper wiki site for the special instructions that apply to Fedora Core, as in some cases there is a problem with the size of the driver file and the Fedora Core stack size.

    Unfortunately, you are in for a little more research.

  10. #10
    Just Joined!
    Join Date
    Dec 2006
    Location
    Austin, Texas
    Posts
    26
    Quote Originally Posted by jglen490
    dime --

    You have downloaded, and presumably installed, ndiswrapper. Please run:

    Code:
    sudo ndiswrapper -l
    and that would be "-l" as in lower case L, not i or the number 1. Just to be sure !!

    The ndiswrapper executable provides the means for a Windows driver to be used within the Linux environment. This means that you need to bring in the Windows driver (both the .inf and the .sys files) to Linux and have ndiswrapper install them. The .inf and the .sys files will normally come from the driver CD that comes with the Broadcom-chipped card. At times (I know it's true for FC 6 and maybe FC 5 also) it is necessary to "blacklist" the driver that the kernel loads (i.e., "bcm43xx") so that the "true" driver can do its thing. That was definitely the case with my Kubuntu install and my Buffalo Broadcom 4318 card. Anyway, double-check at the ndiswrapper wiki site for the special instructions that apply to Fedora Core, as in some cases there is a problem with the size of the driver file and the Fedora Core stack size.

    Unfortunately, you are in for a little more research.
    Meh, I've looked all over the ndiswrapper site.

    Also:
    ndiswrapper -l shows my driver.

Page 1 of 3 1 2 3 LastLast

Posting Permissions

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