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 then.
Thanks very much for your reply, Peter.
Here's absolutely everything I did as a result:
- powered off
- booted up
- opened a terminal
- used ndiswrapper with the -i option and the Windows .INF file; while
the command was executing, I got repeated twice "Forcing parameter
AdhocGModel1 to AdhocGModel0"
- used ndiswrapper with the -l option; I got the following:
Installed drivers:
wg511v2 driver installed, hardware present
- used depmod with the -a option
- used modprobe ndiswrapper; I got the prompt back with no intervening
screen output
- used dmesg | grep -i ndiswrapper; I got the following:
<6> ndiswrapper version 1.14 loaded (preempt=no,smp=yes)
<6> ndiswrapper: driver wg511v2 (NETGEAR,02/22/2005,3.1.1.7) loaded
<6> ndiswrapper: using IRQ 11
<3> ndiswrapper (NdisMAllocateSharedMemory: 926): couldn't allocate
261376 bytes of un-cached DMA memory
<4> ndiswrapper (miniport_init:273): couldn't initialize device: C0000001
<4> ndiswrapper (pnp_start_device:497): Windows driver couldn't
initialize the device (C0000001)
It seems as though doing the modprobe just as soon as is possible when
following the installation instructions doesn't make a difference.
If you have any other suggestions, I'd be happy to try them.
Thanks again,
Leslie
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
