iB::Topic::Can't get ndiswrapper to load Windows driver

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » Can't get ndiswrapper to load Windows driver

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (2) </ 1 [2] >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: Can't get ndiswrapper to load Windows driver

< Next Oldest | Next Newest >

lesliek

Group: Members
Posts: 91
Joined: Feb. 2006

Posted: Mar. 27 2007,02:37

Hi again ^thehatsrule^.

I created a new entry in my menu.lst file that added to the end of the middle line of my default entry the three additional words you suggested.

I then booted up and used that testing option.

At the desktop, I went through the same steps I'd been following earlier.

Unfortunately, the result was identical.

For the sake of completeness, here's the entire output of dmesg | grep -i ndiswrapper:

<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)

If you have any other suggestions, I'd be happy to try them.

Thanks again,

Leslie

^thehatsrule^ Offline

Group: Members
Posts: 3275
Joined: July 2006

Posted: Mar. 27 2007,03:24

This http://damnsmalllinux.org/cgi-bin....;t=4515 suggests acpi=noirq though its for another card... might also want to try
pnpbios=off
pci=bios
noapic

Did you try the superlowram (as decribed in wiki)?
Are there any other problems in dmesg? (irq conflicts)?

Might want to check out http://ndiswrapper.sourceforge.net/mediawiki/index.php/List#N
Apparently theres a couple versions of v2, so I'd assume some .inf+.sys's don't seem to work with others.

lesliek

Group: Members
Posts: 91
Joined: Feb. 2006

Posted: Mar. 27 2007,21:54

Thanks very much for your latest reply, ^thehatsrule^.

I'm pleased to say that I've now been able to advance further than ever before.

I deleted from the computer the two Windows files (WG511v2.INF and WG511v2.sys) I'd copied to it from the CD that came with the card and started all over.

First, I copied to the computer ALL of the files in the relevant Windows XP folder on the CD that came with the card, not just the two I’d earlier copied. Whether that mattered, I can’t say, but I did it because I saw in my reading someone suggesting that that be done.

Next, I ran ndiswrapper –i WG511v2.INF, followed by ndiswrapper -l. The latter showed that the driver was installed and hardware was present.

Next, I added /etc/ndiswrapper (which now included files created by running ndiswrapper –i WG511v2.INF) to .filetool.lst, added sudo modprobe ndiswrapper to bootlocal.sh and rebooted. (I hadn't done those things before, but had tried simply to take all of the steps one after the other. Maybe rebooting part way through the steps helped.)

As I watched on the reboot, I saw a message saying “unable to locate module ndiswrapper”. However, when I got the desktop, I decided to try again. I opened the terminal, typed in sudo modprobe ndiswrapper (which gave me back the prompt, not a message about being unable to locate the module) and then dmesg | grep –i ndiswrapper.

This time, the entries in dmesg didn’t include anything about being unable to allocate shared memory; as well, the lights on the card were flashing for the first time ever.

Then, very disappointingly, I had to leave for work, from where I'm typing this.

I hope that when I get home and boot up, I'll again be able to get back to the point where the card shows signs of life.

Naturally, I'd prefer that the sudo modprobe ndiswrapper command could run from bootlocal.sh, rather than from the command line.

Are you able to give me any suggestion as to why the command wouldn't work when included in bootlocal.sh?

Thanks again,

Leslie

^thehatsrule^ Offline

Group: Members
Posts: 3275
Joined: July 2006

Posted: Mar. 27 2007,22:55

I think some commands require time for loading, etc. especially for ndiswrapper.

Placing sleep commands before the non-working ones probably help you out. (I think `sleep 10` was suggested as a good test)

lesliek

Group: Members
Posts: 91
Joined: Feb. 2006

Posted: Mar. 28 2007,00:53

As much as I hate to admit this, I feel I must.

A combination of small print and old eyes made me fail to notice that I'd asked for the module ndsiwrapper, not the module ndiswrapper. With that changed, all works as expected on boot-up and I'm on to the next stage, during which I will probably make similar errors!

Thanks again, ^thehatsrule^, and I'm sorry to have troubled you about the latest problem unnecessarily.

9 replies since Mar. 26 2007,09:59

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (2) </ 1 [2] >/

Damn Small Linux Board » Damn Small Linux » Networking » Can't get ndiswrapper to load Windows driver