DSL 3.1 NDISWRAPPER Problem


Forum: Networking
Topic: DSL 3.1 NDISWRAPPER Problem
started by: rmccarri

Posted by rmccarri on Dec. 23 2006,00:23
Hi,
I am trying to get the new 3.1 DSL distribution up and running on an eMachines laptop with a Broadcom 4320 wireless adapter.

I had a previous distribution working perfectly with NDISWRAPPER using the all too familiar bcmwl5 driver.  However, with this new version, I am not able to connect to my access point.  Has anyone else had this problem?

Thanks in advance for any advice.

Posted by deadyoda on Dec. 23 2006,16:33
You should write here the error msg you have with "dmesg"

It could help (?)

And give the working version of dsl :)

Posted by Casandro on Jan. 07 2007,20:19
Quote (deadyoda @ Dec. 23 2006,11:33)
You should write here the error msg you have with "dmesg"

It could help (?)

And give the working version of dsl :)

Well I've seen the message. Although I don't really have the details here, offhand. I can tell you that I had the same problem on Ubuntu. The only thing that helped was updating ndiswrapper. So it's most likely an ndiswrapper problem. Please include a newer version, if possible. Thanks.
Posted by Casandro on Jan. 08 2007,17:44
Quote (deadyoda @ Dec. 23 2006,11:33)
And give the working version of dsl :)

The error in ndsl (the newest version) is like this:
ndiswrapper version 1.14 loaded (preemt=yes,smp=yes)
ndiswrapper: driver gplus (D-Link, 04/09/2004,6.0.0.18) loaded
loadndisdriver: page allocation failure. order:7, mode:0xd0
Then there's something which looks like a stack trace or something.
ndiswrapper (NdisMAllocateSharedMemory:926): couldn't allocate 409600 bytes of un-cached DMA memory.
ndiswrapper (miniport_init:273): coudn't initialize device: X0000001
ndiswrapper (pnp_start_device:497): Windows drier coudln't initialize the device (C000000001)
ndiswrapper: probe of 0000:00:0a.0 failed with error -22

I'm sorry for any typoes. essentially it fails the same on DSL 3.1 and ndsl. It also failed on Ubuntu. There compiling the ndiswrapper module solved the problem.

Powered by Ikonboard 3.1.2a
Ikonboard © 2001 Jarvis Entertainment Group, Inc.