Re: wireless network question



N'kaem-ael wrote:
Hey All,

I have a DELL Inspiron 1721 (WLAN 1390). I am running 64 bit
Fedora 8 and have downloaded a 64 bit windows driver for ndiswrapper
(1.50). When I run "ndiswrapper -l" I get a response:

bcmwl5 : driver installed
device (14E4:4311) present (alternative driver: ssb)


when I run iwlist wlan0 scan, I receive:

wlan0 Interface doesn't support scanning : Network is down

Does anyone have any ideas on where I should go from here? Any help
is much appreciated. Thanks.

I this a new setup on the router side also? Sounds like password or
key or something doesn't match. Maybe reset everything and start with
a primitive setup.
.

Relevant Pages

  • Re: bcm43xx regression in 2.6.24 (with patch)
    ... >> Isn't the fundamental problem here that the ssb driver claims the same ... >> PCI IDs as the bcm43xx driver? ... >> between bcm43xx and the ssb driver. ...
    (Linux-Kernel)
  • Re: bcm43xx regression in 2.6.24 (with patch)
    ... >> Isn't the fundamental problem here that the ssb driver claims the same ... >> PCI IDs as the bcm43xx driver? ... >> between bcm43xx and the ssb driver. ...
    (Linux-Kernel)
  • [PATCH] Fix the bcm43xx driver breakage in 2.6.24/25.
    ... The bcm43xx Wifi driver won't work any more, ... The first patch separates the ssb b43 pci bridge and the ssb pci ... Don't build the bcm43xx driver if SSB is static and the b43 PCI-SSB bridge code is enabled. ...
    (Linux-Kernel)
  • Re: [PATCH] prevent SSB compilation on s390 part 2
    ... prevent SSB from being selected. ... So add an explicit depends on HAS_IOMEM to the Broadcom driver to ... prevent selection on s390. ... B44 does not depend on PCI. ...
    (Linux-Kernel)
  • Re: bcm43xx regression in 2.6.24 (with patch)
    ... The bcm43xx driver used to work with 2.6.23 without requiring ... Isn't the fundamental problem here that the ssb driver claims the same ... PCI IDs as the bcm43xx driver? ...
    (Linux-Kernel)