LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   ndiswrapper broadcom bcmwl6 (https://www.linuxquestions.org/questions/linux-wireless-networking-41/ndiswrapper-broadcom-bcmwl6-534767/)

bychan 03-05-2007 10:46 AM

ndiswrapper broadcom bcmwl6
 
Hi,
last week I bought a HP Pavilion dv6203ea (DV6200).
It installed very well under SuSE10.2. Everything works except the wlan.
The system was sold with a preinstalled Windows Vista.
I found the driver under Windows in c:/SwSet/WLAN, i.e.
a bcmwl6.inf.
I did the following commands:
ndiswrapper -i bcmwl6.inf
depmod -a
modprobe ndiswrapper
ndiswrapper -mi
ndiswrapper -ma
depmod -a modprobe ndiswrapper

a call
ndiswrapper -l gives me the following results:
installed drivers:
bcmwl6 driver installed, hardware (14E4:4328) present (alternate driver: ndiswrapper)
Which looks fine, I think, but the result of
iwconfig
just gives the following results:
lo no wireless extensions.
eth0 no wireless extensions.
sit0 no wireless extensions
eth0 is my working LAN connection anyway. I would have expected a working eth1 or wlan0 wireless extension.

I fiddled around with the problem the whole weekend, so I will be more than haoppy with some help.

Thanks,
Bernard

bychan 03-05-2007 10:56 AM

boot messages
 
I just checked the boot messages concerning my driver problem and found the following error messages:
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisAllocateMdl'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisFreeMdl'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMRegisterMiniportDriver'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMSetMiniportAttributes'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMGetBusData'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMRegisterScatterGatherDma'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisFreeNetBufferList'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMRegisterInterruptEx'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMOidRequestComplete'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisAllocateIoWorkItem'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisQueueIoWorkItem'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisAllocateMemoryWithTagPriority'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMSetBusData'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferAndNetBufferList'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisAllocateNetBufferListPool'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMDeregisterInterruptEx'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMDeregisterMiniportDriver'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMDeregisterScatterGatherDma'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisFreeNetBufferListPool'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisOpenConfigurationEx'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisFreeIoWorkItem'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMSendNetBufferListsComplete'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMSynchronizeWithInterruptEx'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMIndicateStatusEx'
<3>ndiswrapper (import:245): unknown symbol: NDIS.SYS:'NdisMIndicateReceiveNetBufferLists'
<3>ndiswrapper (load_sys_files:215): couldn't prepare driver 'bcmwl6'

Maybe it will be of any help to somebody?

Hangdog42 03-05-2007 11:22 AM

Quote:

The system was sold with a preinstalled Windows Vista.
I found the driver under Windows in c:/SwSet/WLAN, i.e.
I honestly don't know if ndiswrapper will work with Vista drivers. I'm going to guess not, but that is only a guess. However, I do know that ndiswrapper will work with XP drivers, and I would think you could get those from the HP website. Otherwise, look up your card on the ndiswrapper wiki and use the driver they suggest.

Also, depending on what chipset you've got in there, bcm43xx, the native linux driver, might be an option. It is a touch buggy and limited to 11b speeds, so it isn't an automatic choice.

bychan 03-05-2007 02:13 PM

The idea with the XP-drivers sound very good.
I downloaded one from HP called sp34510.exe
"cabetract sp34510.exe"
produced a directory with a "Setup.exe" included.
Starting it with wine leads to a crash of Wine :-(
I tried to find such a driver at Broadcom.com as well, but they haven't any driver with the name.
Any idea?

Hangdog42 03-05-2007 02:40 PM

What is the chipset on that card? You might have luck finding a driver at the ndiswrapper wiki if you know the chipset.
Quote:

"cabetract sp34510.exe"
Try unzip sp34510.exe in Linux. Usually these things are self extracting zip files, which Linux can deal with.

bychan 03-05-2007 03:13 PM

Quote:

Originally Posted by Hangdog42
What is the chipset on that card? You might have luck finding a driver at the ndiswrapper wiki if you know the chipset.
lspci | grep Broad
02:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01)


Try unzip sp34510.exe in Linux. Usually these things are self extracting zip files, which Linux can deal with.

unzip doesn't unfortunately work.

bychan 03-05-2007 03:28 PM

I've just downloaded and installed a driver from ndiswrapper wiki, i.e. R140747.EXE.
Everything installed fine, except that wlan is still not working.
Before I installed it, I just removed the old driver in /etc/ndiswrapper. Is that enough or do I have to do something else. Restart some process etc.

For installation I did again:
ndiswrapper -i bcmwl5.inf
depmod -a
modprobe ndiswrapper
ndiswrapper -mi
ndiswrapper -ma
depmod -a modprobe ndiswrapper

The command "ndiswrapper -l" gives me:
installed drivers:
bcmwl5 driver installed, hardware (14E4:4328) present (alternate driver: ndiswrapper)

This looks as if everything is working fine, doesn't it?

Hangdog42 03-05-2007 03:41 PM

Is ndiswrapper in the output of lsmod? Also, as long as your looking at lsmod, is bcm43xx there? Finally, if ndiswrapper is loaded, what is the output of iwconfig?

bychan 03-05-2007 03:44 PM

Great!!!!!!!

I've just rebooted and iwconfig shows now:

lo no wireless extensions.

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
Encryption key:off
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


So this means I just have to configure it?

Thank you very very much! I appreciate your help!!!

Hangdog42 03-05-2007 03:49 PM

Yup, you just have to configure it:

iwconfig wlan0 essid YourSSID

and if you're using WEP, you would also do:

iwconfig wlan0 key YourWEPKeyInHex

Check out the iwconfig man page for other things you can do with iwconfig.

Once you've got the card configured, you'll need to request an IP from the DHCP server. I'm not sure what Suse uses as a DHCP client, but one of the following will hopefully work:

ifup wlan0
dhcpcd wlan0
dhclient wlan0

bychan 03-05-2007 04:03 PM

I've done, what you have suggested and wlan0 appears in ifconfig now as well, but I haven't received any IP-Adress from my DHCP server which is a FRITZBOX.

Hangdog42 03-06-2007 11:42 AM

Please post the outputs of iwconfig and ifconfig. Also have a look at your log files after running your DHCP client (/var/log/syslog, /var/log/messages and the dmesg output). The DHCP client should be leaving clues about what is happening. Also, what DHCP command are you using?

bychan 03-06-2007 03:40 PM

output of ifconfig:
eth0 Protokoll:Ethernet Hardware Adresse 00:16:36:F0:48:3A
inet Adresse:192.168.178.32 Bcast:192.168.178.255 Maske:255.255.255.0
inet6 Adresse: fe80::216:36ff:fef0:483a/64 Gültigkeitsbereich:Verbindung
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3355 errors:0 dropped:0 overruns:0 frame:0
TX packets:2099 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:4399544 (4.1 Mb) TX bytes:165941 (162.0 Kb)

lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:30 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:0
RX bytes:1956 (1.9 Kb) TX bytes:1956 (1.9 Kb)


output pf iwconfig:
lo no wireless extensions.

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
Encryption key:5C5C-633E-6672-8F74-6864-6E24-12 Security mode:restricted
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

eth0 no wireless extensions.

sit0 no wireless extensions.

in /var/log/messages I get the message:
Mar 5 23:51:58 Io ifup: No configuration found for wlan0

in boot.msg is the same message:
No configuration found for wlan0

I think the reason is, that my commands from command line are not saved,i.e.

iwconfig wlan0 essid FRITZBOX
iwconfig wlan0 mode managed
iwconfig wlan0 key XXXX-XXXX-XXXX-XXXX-XXXX-XXXX-XX
iwconfig wlan0 commit

I am using
DHCP Client Daemon v.1.3.22-pl4

Thank you very much!

jschiwal 03-06-2007 04:45 PM

In SuSE, you can configure your wireless from YaST.

Select Network Devices, then select the wireless device and click on the Edit button.

On the bottom of the page, there is a drop down list for advanced features. In the hardware part, make sure that the kernel module listed is ndiswrapper. Also click the routing button. If you aren't using dhcp, you will need to enter your default gateway.

After returning to the main page, and clicking Next, you will get to the page where you set up encryption. Select Managed and if you are using WPA, select WPA_PSK from the drop down box. You will need to enter the same key that the router uses.

Most of these configurations are saved in the config file /etc/sysconfig/network/ifcfg-wlan0.
This file is executed, setting environment variables that subsequent scripts use.

The values for wpa_supplicant.conf are created from these variables. The /etc/wpa_supplicant.conf file is not used. A config file is created in /var/run/ instead on the fly.

FYI. You were lucky that SuSE didn't try to use the bcm43xx driver instead.

bychan 03-07-2007 01:55 AM

Quote:

Originally Posted by jschiwal
In SuSE, you can configure your wireless from YaST.

It worked fine, thanks to your description

After starting "ifup wlan0" the wireless shows up in ifconfig, but only if I have an "ifdown eth0" before. But still there's no IP-Address for wlan0:

wlan0 Protokoll:Ethernet Hardware Adresse 00:1A:73:24:A3:8D
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:177 Speicher:d6000000-d6004000



> Most of these configurations are saved in the config file
> /etc/sysconfig/network/ifcfg-wlan0.
ifcfg-wlan0 looks like this:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='10'
IPADDR=''
MTU=''
NAME=''
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='ifplugd'
USERCONTROL='no'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='FRITZBOX'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0='XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='static-0'



Quote:

Originally Posted by jschiwal
FYI. You were lucky that SuSE didn't try to use the bcm43xx driver instead.

Just to be curious: What would have happened?


All times are GMT -5. The time now is 03:07 AM.