Networking :: Another Wireless Crash.

I believe I've isolated the complete lockup problem I posted in the "Other" thread. This lockup is both keyboard and mouse. It occurs when The wirless card is activated through ndiswrapper and usually was far enough off to add uncertainty but today it locks within a minute or so, and most of the time immediately.
It a Motorola card with the a broadcom chip. Driver is bcmwl5.inf.
Athlon K-6 350 with 196mb ram.
I cannot get the thing activated running live cd though I input all addressing options to the file.

[/QUOTE]

I am having the same problems with my Buffalo card. (Uses the same ndiswrapper driver: bcmwl5.inf) I have had this same problem with SLAX and ndiswrapper, but SLAX 5.0.5 works great, and wanted to go back to DSL.

Does anyone have any ideas.

Try boot with:

dsl acpi=off

and see if it helps.

I tried dsl acpi=off, and I thought that did the trick...

Here's what I did:

Booted DSL, and typed dsl acpi=off at the boot prompt

open'd a terminal window and installed the wireless driver

sudo ndiswrapper -i bcmwl5.inf
sudo ndiswrapper -l
sudo modprobe ndiswrapper

everything was going great, then i tried to get an IP through dhcp and typed:

pump -i wlan0

then the system locked (i thought it might be using all the resources so I let it sit for about 15min and it was still locked.)

I then reboot'd entered the same boot command, and loaded the ndiswrapper module the same, but this time used the control panel and tried netcardconfig. I selected DHCP, and it stated that wlan0 connected DHCP "OK" and then locked up.

I then reboot'd entered the same boot command, and loaded the ndiswrapper module the same, but this time tried firefox. and after the window opened, the second light on the card came on and then the system locked up.

tonight I will try another card, just to make sure it is the Buffalo Airstation card and/or driver that is causing the problems.

Slax works with the same driver, and Slax uses DHCPCD... it there a DHCPCD version for DSL?

If the machine locked after firefox opened, then the problem must be with your card's ndiswrapper driver or the pcmcia card services and it is not due to your DHCP program (pump vs. dhcpcd).

You might be able to get it to work with a different driver file. Are you using the one recommended by the ndiswrapper folks?

http://ndiswrapper.sourceforge.net/mediawiki/index.php/List

Next Page...
original here.