LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   broadcom chip wireless problems (https://www.linuxquestions.org/questions/linux-wireless-networking-41/broadcom-chip-wireless-problems-307357/)

mikede 03-29-2005 08:16 AM

broadcom chip wireless problems
 
I have done a few searches and have found similar problems but nothing quite what I have. I am using the MN-720 wireless controller from microsoft. I have ndiswrapper installed and it says driver is installed and hardware is present. when I do a cardctl ident i get socket 0: no product info available and same for socket 1. The cards leds are on but very dimly.

network settings says the connection is active but no traffic is going over it.
(also the wlan0 does not show up in connection properties, though it does in the settings panel.)

ifconfig shows the device as present as does iwconfig.

I am still fairly a newb with linux and would really appreciate any help you could give me. Thank you for your time.

darkleaf 03-29-2005 08:48 AM

Can you ping to your router/internet (try both). Use "ping -c 4 ipaddress"

mikede 03-29-2005 09:19 AM

I cannot ping with wireless to either router or to internet. Although i can with my cat5 cable and with other wireless connections (alas with windows on other wireless connections.)

darkleaf 03-29-2005 09:35 AM

Conclusion it doesn't work. One last thing you did modprobe ndiswrapper did you?

If so then it looks like the card isn't recognized. Do you have the newest version of ndiswrapper?

I only had one result in a google and the guy who got it to work didn't tell why so I asked if he could tell it. Hope he does. Some other things I found:

Quote:

ndiswrapper:

Driver-and-Installation

*

Option 1: Use Dell's TrueMobile?? 1300 driver. I'm hosting it for your convenience at http://ankhcraft.com/drivers/bcmwl5.zip

Please note that the pciids are not the same for this card, so, following driver installation into ndiswrapper, you'll need to create some symlinks, like so (as root): ln -s 14e4:4320:1028:0002.conf /etc/ndiswrapper/14e4:4325:1414:0003.conf ln -s 14e4:4325:1414:0003.conf /etc/ndiswrapper/14e4:4325.conf

*

Option 2: Use a homegrown driver INF file that I have created, along with the same SYS file from above.

It has the benefit that you will not have to create any symlinks. I'm hosting it for your convenience at http://ankhcraft.com/drivers/mn720-ankh.zip Please note that I do not provide any warranty for this INF file that I have created, express or implied. All I can say is that it works for me, and I use this card heavily (with this driver).

*

Option 3: Use MicroSuck?'s Driver from the cd (or optionally from http://www.network-drivers.com/drivers/141/141400.htm)

Please be warned that this driver does not play nice with Linux hosted NDIS emulation wrappers in general. In order to get this driver work with ndiswrapper specifically, you must make sure you do NOT have the card plugged into the cardbus slot when you insert the ndiswrapper module. You'll get a kernel panic if you do, and then you're toast. Plug the card in afterward. After this, it works wonderfully. Also, it is worth mentioning that the MicroSuck? driver is known to be unstable when used with LinuxAnt's driverloader. You may experience random system lockups, even though you may avoid the kernel panic mentioned above. I would suggest that you stay away from this driver, period, under Linux.


Which are you using. If it's the last you might try another one or you might try any other except for the ms driver itself which doesn't seem to much fun ;). Hope this helps a bit.

mikede 03-30-2005 06:58 AM

Thank you for your help. I switched to the home grown driver but without any change in status. I once had it working with FC1 but never with FC3 or Debian as I am now using. I guess I will just have to go buy a new Wireless card. One that works well with linux. Thank you again for your aid.

darkleaf 03-30-2005 07:33 AM

I think if you got it to work once you should be able to do it again. Even though it's a ms card. Have you tried a search here on lq with your model name in it. Maybe the hardware compatibility list here on LQ has some info too

darkleaf 03-30-2005 07:41 AM

OK people get it to work with ndiswrapper. It might be worth the try? Did you install the card yourself? If the lights are on only dimly is it properly in the socket? What does "lspci" say?

Which version of ndiswrapper are you using?

Also there's a howto here which says to just use ms drivers.
http://www.linuxquestions.org/hcl/sh...cat=146&page=1

If you feel comfortable trying it out you can do. If not I think you could still try the other dirvers listed there before you buy another card. Someone said just follow the ndiswrapper instructions on the site.

mikede 03-31-2005 06:20 AM

I have followed that guide before. The card is in the socket properly, yes. I am using the latest version of ndiswrapper. It says the hardware is there even and sets up wlan0. The problem is that when i try to have linux say what card is there it only identfys it as an unknown card. The MS drivers were the ones I was using before with no difference in results. The problem may lie not in the device driver? but in how linux recognizes the PCMCIA card? Honestly I do not know. I even tried adding the MN-720 to the /etc/pcmcia/config. Doing a cardctl status gives me :
Socket 0:
3.3V CardBus card
function 0: [ready]
Socket 1:
no card.

and cardctl ident gives me-
Socket0:
product info: "Broadcom", "802.11b cardbus", 8.0"
manfid: id is here
function: 6 (network


Maybe the card is not recieving the power that it needs for some reason? Any Ideas on what i would edit to be sure that it recieves the proper voltage (after i check the manufacturer's specs to be sure i do not give it too much?)

darkleaf 03-31-2005 07:30 AM

Well doesn't it recognize it then cause you now have those cardctl stuff? Also I don't know but maybe "lspci" should recognize it too if it's a PCI card.

Also your wlan0 doesn't get setup completely. You still have to set some things statically or with dhcp.

ankhcraft 04-19-2005 02:09 AM

Well, maybe I can help here. I'm the one that contributed the homegrown .INF file along with the broadcom drivers. I've currently got this card up and running right now, and in fact I'm posting this reply over that link. So, it does, in fact, work. I'm running Gentoo Linux.

Originally, back in August, I was using it with ndiswrapper 0.10, but now I'm using ndiswrapper 1.1.

By the way, the childish "Microsuck" comment didn't come from me, someone else edited my entry in the ndiswrapper Wiki and gratituitously made that "improvement" for me. ;-)

So, what is the status of this issue now? Are you still having this problem?

loderunner 06-13-2005 03:43 PM

Sounds familiar...
 
This may not be helpful, but I am currently having the EXACT same problem. Same card, same info returned by ifconfig, iwconfig and cardctl, and yes, both my lights are on--but only very, very dimly.

Wish I could be more helpful, but I'm still a rather useless newbie (just converted to Linux a week ago.) Whatever the problem is, it's definitely reproduceable.

I'm running Ubuntu Hoary Hedgehog default install with all availible updates. So far, I've only tried ankhcraft's driver. System is a Compaq Presario 2100 with onboard ethernet (but obviously, no onboard wifi.)


All times are GMT -5. The time now is 06:15 PM.