me too!!

aparently it might be a problem to do with dma or irqs, (http://ndiswrapper.sourceforge.net/p.../index.php/FAQ) where linux cant find one spare or something. but i dont believe this for one second. any ideas?

and ive tried acpi=off and that still donest work. the faq also tells me to try to find out what irq the kernel is trying to use and free it. how do i do that?

take a look at this guys post, im very confused why he says his wrapper works great on wusb45g. http://sourceforge.net/mailarchive/m...sg_id=10380414 is he being ironic? the ndiswrapper sit ealso says on the compatibility page wusb54g works perfectly of course

i may have been suckered through no fault of my own

how do i do this?

"If you get "probe of XXXX:YY.ZZ.A failed with error -22", you may have problems with IRQ assignment (the kernel couldn't assign IRQ for the wireless card). You can find out which IRQ ndiswrapper is trying to use and release that IRQ (find out which other device is using it with cat /proc/interrupts). You may want to use ACPI and configure BIOS to assign IRQs using ACPI. "

From the link you posted, this is really starting to sound like a funky hardware issue. I know exactly diddly about mobo's, but it might be worth a google on that mobo and ndiswrapper to see if anyone has had similar problems. By the way, what kind of computer is this?

To see what interrupts are in use, pop open a console and type cat /proc/interrupts and that should give you a list of what IRQ's have been assigned to what device. It might be informative to do this a few times, each time changing a different thing. So try it with the card out, then put the card in and look. Then try to load the ndiswrapper module and look again. I'd also try it with acpi on and off.

no luck

At this point, all I can suggest is mucking about with the BIOS as suggested by the ndiswrapper fax. This isn't really an issue with your wireless card, but rather how linux is working with your motherboard. If you haven't invested a lot in this set-up I suppose you might try either rolling your own kernel or a different distro. Mabye Debian or Slackware would work better than Suse.

**bursts into tears**



i bought suse professional for 40 quid so i could have the manuals and stuff to find out that by all accounts red hat and mandrake are better

anyway....

am dl'ing mandrake now. i might as well give it a go. theres no point in having suse without net access. i was scared by mndrake before when it was so buggy. iveheard its still buggy but apart from that better than suse. i shall see.

can any1 help me?

Could you explain where you are stuck? If it is the same problem as was started in this thread, I'm afraid I don't have any new ideas. However, if you've installed a new distro and are having a new problem, feel free to post away. By the way, the idea that mandrake is buggy is a load of hooey. It is no more or less buggy than any other distro.

I've have had this working under 3 diffenent distributions now Slackware 10, Fedora Core 3 and Mandrake 10.1, same kernel 2.6.7 (and 2.6.9 )

But have recently got the same error, the only change I made was to include High memory in the kernel config and recompile ( I have 1.5 GB, and with out this it only sees 1GB), take it back out , re-build and it works again.

Have no idea why, or what is going on.

Not sure if that will help, but its worth a look.

Cheers

Hello,

I have the same problem with the WUSB54G on my suse 9.2 at home-desktop. But!!! the same device is working fine on my work-laptop which has also suse 9.2.

how can I find ot which IQR the device is using / trying to use???

if i type in: more /proc/interrupts
i get:
I the dmesg gives:

usb 2-2: new full speed USB device using address 5
ndiswrapper (NdisWriteErrorLogEntry:196): log: C000138A, length: 3 (c0000001)

ndiswrapper (ndis_init_one_usb:1556): Windows driver couldn't initialize the device
wusb20xp.sys: probe of 2-2:1.0 failed with error -22

hopefully someone can help, please

If that is the case, I would look at the ndiswrapper version and windows drivers on your work laptop. Frequently with ndiswrapper you end up trying different versions of ndiswrapper and windows drivers in order to get it to work. Of course the kernel version will also matter so it would be a good idea to look at what kernel your work machine uses.

Hello, maybe that's really the problem. I was thinking I have identical installations at work and at home. Both kernels are the same (suses 2.6.8-24.10-default). I also copied the windows drivers form one machine to the other to be sure to have the same version of the windows driver. However, here at work it's ndiswrapper version 0.10 whereas at home it's 0.11.

I will try to install 0.10 at home and hopefully it will work. I will report

PS: