3 issues, please help me

[deguz]

In lsmod bcm43xx isn't in. I've already blacklisted it.

On 04/12/2007, Derek Broughton <news at pointerstop.ca> wrote:
> deguz wrote:
>
> > wlan0     IEEE 802.11g  ESSID:off/any
> >           Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated
> >           Bit Rate:54 Mb/s   Tx-Power:32 dBm
> >           RTS thr:2347 B   Fragment thr:2346 B
> >           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
> > Output of iwlist wlan0 scan:
> > wlan0     No scan results
> > But it's not correct, there are wlan networks here.
>
> Not that it can see :-(
>
> > dmesg says:
> > dmesg |grep ndis
> > [   16.680000] ndiswrapper version 1.50 loaded (smp=yes, preempt=no)
> > [   16.772000] ndiswrapper: driver bcmwl5 (Broadcom,10/12/2006,
> > 4.100.15.5) loaded
> > [   16.780000] ndiswrapper: using IRQ 17
> > [   16.988000] usbcore: registered new interface driver ndiswrapper
> > dmesg |grep wlan0
> > [   16.984000] wlan0: ethernet device 00:1a:73:9b:84:8c using NDIS
> > driver: bcmwl5, version: 0x4640f05, NDIS version: 0x501, vendor: 'NDIS
> > Network Adapter', 14E4:4311.5.conf
> > [   16.984000] wlan0: encryption modes supported: WEP; TKIP with WPA,
> > WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
>
> That all looks good.
>
> > [   77.568000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> That probably implies that nothing has _tried_ to bring the link up, not
> that it is not available (at least mine says that right now, while I'm on a
> wired connection)
>
> > I think the problem is with the wlan button, it is blue (it works)
> > until GRUB loads, but when GRUB loads, it turns off, and i can't turn
> > it on. I really need to use wlan, please help me.
>
> No, I don't think so.  Until ndiswrapper loads the driver, the light
> shouldn't be blue.  I think your broadcom driver is still there and
> interfering.  Do "lsmod | grep bcm".  If it shows bcm43xx, rmmod it,  and
> add "blacklist bcm43xx" in a file in /etc/modprobe.d/, then you probably
> need to restart ndiswrapper (not sure what the procedure is there, because
> mine worked first try).
>
> --
> derek
>
>
> --
> kubuntu-users mailing list
> kubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
>