Re: Ndiswrapper on 64 bit Fedora 7 - Hardware

This is a discussion on Re: Ndiswrapper on 64 bit Fedora 7 - Hardware ; I had the same problem due to a new driver "ssb" that needs to be added to the blacklist so it doesn't conflict with ndiswrapper: With a reboot -- add to /etc/modprobe.d/blacklist then reboot Without a reboot -- add "blacklist ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Re: Ndiswrapper on 64 bit Fedora 7

  1. Re: Ndiswrapper on 64 bit Fedora 7

    I had the same problem due to a new driver "ssb" that needs to be
    added to the blacklist so it doesn't conflict with ndiswrapper:

    With a reboot -- add to /etc/modprobe.d/blacklist then reboot

    Without a reboot --
    add "blacklist ssb" to the bottom of /etc/modprobe.d/blacklist
    # modprobe -r ssb
    # modprobe -r ndiswrapper
    # modprobe ndiswrapper
    # iwconfig
    (you will see output for your wireless card interface-- probably
    wlan0)
    # iwlist wlan0 scan
    (should show wireless access points available)


  2. Re: Ndiswrapper on 64 bit Fedora 7

    On Mon, 01 Oct 2007 09:04:49 -0700, davejones70 wrote:

    > modprobe -r ssb


    I'll give that a try.

    Josh

  3. Re: Ndiswrapper on 64 bit Fedora 7

    On Mon, 01 Oct 2007 09:04:49 -0700, davejones70 wrote:

    > I had the same problem due to a new driver "ssb" that needs to be added
    > to the blacklist so it doesn't conflict with ndiswrapper:
    >
    > With a reboot -- add to /etc/modprobe.d/blacklist then reboot
    >
    > Without a reboot --
    > add "blacklist ssb" to the bottom of /etc/modprobe.d/blacklist #
    > modprobe -r ssb
    > # modprobe -r ndiswrapper
    > # modprobe ndiswrapper
    > # iwconfig
    > (you will see output for your wireless card interface-- probably wlan0)
    > # iwlist wlan0 scan
    > (should show wireless access points available)


    It's still not working, I've put the following in
    /etc/modprobe.d/blacklist
    blacklist ssb
    blacklist bcm43xx
    blacklist bcm43xx_mac80211

    I have the following in /etc/modprobe.conf
    alias wlan0 ndiswrapper

    ndiswrapper -l
    netbc564 : driver installed
    device (14E4:4320) present (alternate driver: ssb)

    dmseg | grep ndiswrapper
    ndiswrapper version 1.46 loaded (smp=yes)
    ndiswrapper (link_pe_images:577): fixing KI_USER_SHARED_DATA address in
    the driver
    ndiswrapper: driver netbc564 (,10/01/2002,3.70.17.5) loaded
    ndiswrapper: using IRQ 17
    usbcore: registered new interface driver ndiswrapper
    ndiswrapper (iw_set_bitrate:493): setting bit rate failed (C00000BB)

    iwlist scanning
    wlan0 No scan results

    iwconfig wlan0
    wlan0 IEEE 802.11g ESSIDff/any Nickname:"ranger.bjrosen.com"
    Mode:Auto Frequency:2.462 GHz Access Point: Not-Associated
    Bit Rate=54 Mb/s Tx-Power:25 dBm
    RTS thrff Fragment thrff
    Power Managementff
    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

    There are lots of access points nearby. If I do a site survey using one
    of my Dlink DCS G900 wireless cameras I get,

    TaskForce34 00 0F B5 28 20 40 11 WEP 93
    NETGEAR 00 90 4C 7E 00 64 11 No 35
    Cityplace 00 18 3F 5E A1 01 10 WEP 26
    quicken3 00 14 6C 14 81 EC 8 No 26
    florida 00 1A 70 4E 43 1D 11 WEP 20
    lenasplace 00 18 39 40 01 74 11 WEP 20

    What else do I need it to do?

  4. Re: Ndiswrapper on 64 bit Fedora 7

    On Oct 2, 12:21 am, General Schvantzkoph
    wrote:
    > On Mon, 01 Oct 2007 09:04:49 -0700, davejones70 wrote:
    > > I had the same problem due to a new driver "ssb" that needs to be added
    > > to the blacklist so it doesn't conflict with ndiswrapper:

    >
    > > With a reboot -- add to /etc/modprobe.d/blacklist then reboot

    >
    > > Without a reboot --
    > > add "blacklist ssb" to the bottom of /etc/modprobe.d/blacklist #
    > > modprobe -r ssb
    > > # modprobe -r ndiswrapper
    > > # modprobe ndiswrapper
    > > # iwconfig
    > > (you will see output for your wireless card interface-- probably wlan0)
    > > # iwlist wlan0 scan
    > > (should show wireless access points available)

    >
    > It's still not working, I've put the following in
    > /etc/modprobe.d/blacklist
    > blacklist ssb
    > blacklist bcm43xx
    > blacklist bcm43xx_mac80211
    >
    > I have the following in /etc/modprobe.conf
    > alias wlan0 ndiswrapper
    >
    > ndiswrapper -l
    > netbc564 : driver installed
    > device (14E4:4320) present (alternate driver: ssb)
    >
    > dmseg | grep ndiswrapper
    > ndiswrapper version 1.46 loaded (smp=yes)
    > ndiswrapper (link_pe_images:577): fixing KI_USER_SHARED_DATA address in
    > the driver
    > ndiswrapper: driver netbc564 (,10/01/2002,3.70.17.5) loaded
    > ndiswrapper: using IRQ 17
    > usbcore: registered new interface driver ndiswrapper
    > ndiswrapper (iw_set_bitrate:493): setting bit rate failed (C00000BB)
    >
    > iwlist scanning
    > wlan0 No scan results
    >
    > iwconfig wlan0
    > wlan0 IEEE 802.11g ESSIDff/any Nickname:"ranger.bjrosen.com"
    > Mode:Auto Frequency:2.462 GHz Access Point: Not-Associated
    > Bit Rate=54 Mb/s Tx-Power:25 dBm
    > RTS thrff Fragment thrff
    > Power Managementff
    > 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
    >
    > There are lots of access points nearby. If I do a site survey using one
    > of my Dlink DCS G900 wireless cameras I get,
    >
    > TaskForce34 00 0F B5 28 20 40 11 WEP 93
    > NETGEAR 00 90 4C 7E 00 64 11 No 35
    > Cityplace 00 18 3F 5E A1 01 10 WEP 26
    > quicken3 00 14 6C 14 81 EC 8 No 26
    > florida 00 1A 70 4E 43 1D 11 WEP 20
    > lenasplace 00 18 39 40 01 74 11 WEP 20
    >
    > What else do I need it to do?


    Were you getting this far before you blacklisted the ssb driver? Does
    the "lsmod | grep ndiswrapper" look better than before?

    Anyway, it might be a driver problem since you can talk to the card
    but all of the values are zero. If you can't find another 64-bit
    driver for your wireless card, then this might be one of those reasons
    making 64-bit difficult to run because of the lack of hardware drivers
    for some devices.


+ Reply to Thread