still struggling with ndiswrapper

Jeff Vian jvian10 at charter.net
Wed Nov 2 22:21:32 UTC 2005


On Wed, 2005-11-02 at 15:10 -0500, James Pifer wrote:
> > It may be related to the 4k stack problem.  I had that on my laptop and
> > used the kernel with 16k stack from
> > http://www.linuxant.com/driverloader/wlan/full/downloads-fc4-i686.php
> > to solve it.
> > 
> > > Thanks,
> > > James
> > > 
> > > 
> > 
> 
> Okay, now I'm running a kernel with 16k stacks. I also loaded
> ndiswrapper 1.5. 
> 
> I can load everything like this:
> 
> ndiswrapper -i /install/ndiswrapper/broadcom/bcmwl5.inf
> /sbin/modprobe ndiswrapper
> /sbin/iwconfig wlan0 mode Managed
> /sbin/iwconfig wlan0 key my_key_goes_here
> /sbin/iwconfig wlan0 essid my_ssid_goes_here
> /sbin/ifconfig wlan0 192.168.1.25 netmask 255.255.255.0 up
> 
> In /var/log/messages I get this:
> Nov  2 15:03:54 laptop kernel: ndiswrapper version 1.5 loaded
> (preempt=no,smp=yes)
> Nov  2 15:03:54 laptop kernel: ndiswrapper: driver bcmwl5
> (Broadcom,10/20/2004, 3.70.22.0) loaded
> Nov  2 15:03:54 laptop kernel: ACPI: PCI Interrupt 0000:02:02.0[A] ->
> GSI 18 (level, low) -> IRQ 193
> Nov  2 15:03:54 laptop kernel: eth%d: ndiswrapper ethernet device
> 00:90:4b:5f:be:d2
> Nov  2 15:03:54 laptop kernel: ndiswrapper: using irq 193
> Nov  2 15:03:55 laptop kernel: wlan0: vendor: ''
> Nov  2 15:03:55 laptop kernel: wlan0: ndiswrapper ethernet device
> 00:90:4b:5f:be:d2 using driver bcmwl5, 14E4:4320.5.conf
> Nov  2 15:03:55 laptop kernel: wlan0: encryption modes supported: WEP;
> TKIP with WPA; AES/CCMP with WPA
> 
> Here's the big problem at the moment. I don't see this device connecting
> to my wireless router. If I look at the connections on my wireless
> router this mac address does not connect. I've also tried it with
> encryption turned off on the router, and not using a WEP key, but it
> still doesn't connect. 
> 
> Anyone have any suggestions now?
> 
As I recall, you previously had the system locking up when you did the
modprobe step.  This seems to be some progress.

Use ndiswrapper -l to see the interface drivers and device are present.

Have you tried using iwlist to see if the adapter finds any local access
points? It should see the access point even if it does not connect, and
should tell you about it.

Other things that might interfere are mode, channel (I think 1-12, but 6
is usually the default for the AP), and maybe others.
I usually try to get the connection without encryption, then enable
encryption later.

My ifcfg-wlan0 is:

IPV6INIT=no
ONBOOT=no
USERCTL=no
PEERDNS=yes
GATEWAY=
TYPE=Wireless
DEVICE=wlan0
HWADDR=
BOOTPROTO=dhcp
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
ESSID='my_essid'
CHANNEL=6
MODE=Managed
RATE=Auto

That worked first time with dhcp, although I have done the same with
static IP addresses as well.  The only things I change for a static IP
is IPADDR, GATEWAY, NETMASK, and BOOTPROTO

If I am using WEP the entry is made in keys-wlan0

> Thanks,
> James
> 
> 




More information about the users mailing list