On 3/27/07, Leslie Katz [EMAIL PROTECTED] wrote:
I'm trying to get this card going on an old laptop and am using Damn
Small Linux.
If you're using the Live version of DSL, ndiswrapper's memory
allocation problem may come from DSL's ramdisk. DSL allocates a fair
amount of RAM for a virtual hard
David P wrote:
On 3/27/07, Leslie Katz [EMAIL PROTECTED] wrote:
I'm trying to get this card going on an old laptop and am using Damn
Small Linux.
If you're using the Live version of DSL, ndiswrapper's memory
allocation problem may come from DSL's ramdisk. DSL allocates a fair
amount of RAM
On 3/27/07, Leslie Katz [EMAIL PROTECTED] wrote:
I have only the crudest understanding of these things, but coupling what
you say with something Peter Chubb said in an earlier post makes me
wonder whether that early high usage of RAM makes it impossible
afterwards for the needed memory to be
David P wrote:
I was thinking that maybe you could set the ndiswrapper module to load
automatically on startup, especially before that high usage of RAM
occurs. Maybe add ndiswrapper to /etc/modules?
Thank you very much for your suggestion, David. When I chopped the
process up into small chunks
I'm trying to get a PCMCIA wireless card going.
I know it requires the use of ndiswrapper. I'm trying to follow the
installation instructions that come from the ndiswrapper website.
All is fine until I do modprobe ndiswrapper. When I run that, I get the
prompt back with no output having
Leslie == Leslie Katz [EMAIL PROTECTED] writes:
Leslie I'm trying to get a PCMCIA wireless card going.
Leslie I know it requires the use of ndiswrapper. I'm trying to
Leslie follow the installation instructions that come from the
Leslie ndiswrapper website.
Leslie All is fine until I do
Peter Chubb wrote:
Hmmm. The device driver is trying to get 256k of memory in a single
chunk. If your machine has been up for any lenght of time, that's
going to be very difficult.
Try rebooting, and then modprobing ndiswrapper immediately after boot
--- you're more likely to have free memory
Leslie == Leslie Katz [EMAIL PROTECTED] writes:
Leslie Peter Chubb wrote:
Hmmm. The device driver is trying to get 256k of memory in a
single chunk. If your machine has been up for any lenght of time,
that's going to be very difficult.
Try rebooting, and then modprobing ndiswrapper
Peter Chubb wrote:
You only need to do this once. After that, the driver bits are
installed by the ndiswrapper command into a standard place.
I'm trying to get this card going on an old laptop and am using Damn
Small Linux. I didn't do what was necessary to ensure persistence of
that
