ndiswrapper and bcm4311 in feisty

Bug #99054 reported by Ülo Parri
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Brian Murray

Bug Description

I have hp pavilion dv2007ea laptop. Wireless worked well before, but now i can't connect anymore.
I have had same problem with edgy and gentoo.
When i started using feisty all was well no problems, but now all seems to be fine, but no wireless connection can be made.
bcm43xx module gives really slow connection, so it's not an alternative.
Could be kernel or ndiswrapper problem.

Updates also brought suspend and sound bug. So to me feisty herd 5 was good and it's gone downhill since.

Have tried both 64 and 32 bit versions.

Revision history for this message
Ülo Parri (ylts-parri) wrote :
Revision history for this message
Ülo Parri (ylts-parri) wrote :
Revision history for this message
Mike Dahlgren (dahlgren) wrote :

Thanks for your bug report, I believe this may be a duplicate of Bug #98856

Revision history for this message
Gert Kulyk (gkulyk) wrote :

Did you try to blacklist bcm43xx before trying to set-up ndiswrapper? If not, ndiswrapper will fail. In general I would recommend at least trying bcm43xx again, ndiswrapper caused a lot of troubles (at least for me).

Since kernel 2.6.20 the bcm43xx module is much more stable than it was in earlier releases. OK, at the moment still not a lot more than 11Mbit/s, but at least you'll get a stable connection.

Revision history for this message
Ülo Parri (ylts-parri) wrote :

can't get connected with bcm43xx
with bcm43xx iwconfig shows:

wlan0 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4311"
          Mode:Managed Frequency=2.484 GHz Access Point: Invalid
          Bit Rate=1 Mb/s Tx-Power=18 dBm
          RTS thr:off Fragment thr:off
          Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

and with ndiswrapper:
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

indicator on my router blinks for a while and then stops.

Revision history for this message
Ülo Parri (ylts-parri) wrote :

and it worked perfectly first when i installed kubuntu herd 5. Later something changed

Revision history for this message
Brian Murray (brian-murray) wrote :

Do you have the bcm43xx-fwcutter package installed when trying to use the bcm43xx module? Additionally I noticed the following in your dmesg log:

[ 57.063159] ndiswrapper (load_sys_files:216): couldn't prepare driver 'bcmwl5'
[ 57.063575] ndiswrapper (load_wrap_driver:118): couldn't load driver bcmwl5; check system log for messages from 'loadndisdriver'

It seems something was misconfigured when you were trying to use ndiswrapper.

Revision history for this message
Ülo Parri (ylts-parri) wrote :

I had some problems with 64 and 32 bit, while i was trying to find solution. I tried both 64 and 32 bit versions of kubuntu and got 64-bit driver in 32-bit kubuntu. I noticed it myself and fixed.
But problem remains...
With both ndiswrapper and with bcm43xx AND bcm43xx-fwcutter everything seems to work, but i can't get connection.
And 4311 with bcm43xx is declared unstable and not supported by developers.

Revision history for this message
Brian Murray (brian-murray) wrote :

Could you the log files again now that your system has the right driver?

Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.