Ndiswrapper issues

[Shell_Eater]

(I'm really new to this. Working on getting a screenshot soon.)
I recently installed Ubutunu v10.10 on my desktop, and that went over reasonably well (other than a strange list of I/O errors after the install disk ejected, but I don't know that that is the problem).
I have a wireless router set up in my house, a Belkin n, and I don't have a driver that supports my wireless card. Did some looking, found Ndiswrapper-1.56, tried to install it. No discernable problems up until I execute "make"; then, there's a stream of errors.

'struct net_device' has no member named 'mc_count'
...repeats...
dereferencing pointer to incomplete type
...repeats...
make[3]: *** [/home/username/ndis/ndiswrapper-1.56/driver/wrapndis.o] Error 1
make[2]: *** [_module_/home/username/ndis/ndiswrapper-1.56/driver] Error 2
make[2]: Leaving directory `/usr/src/linux-headers-2.6.35-22-generic'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/derek/ndis/ndiswrapper-1.56/driver'
make: *** [all] Error 2

And of course "make install" and what not doesn't work after that either. Those struct net_device and pointer errors had some directories associated, all of them under /home/username/ndis/ndiswrapper-1.56/driver/wrapndis.c_some number_: . I've tried everything I know, looked around some, checked to make sure install went okay, nothing was corrupted...doesn't look that way, but I'm very open to suggestions here.

Thanks,
Shell_Eater

[Nagarjuna]

Hey, Shell_Eater. Welcome to the forums.

Apparently, kernel 2.6.35 includes some API changes that can break the ndiswrapper-1.56 build. Luckily, there is a patch that should fix this problem.

You can download it here: http://ndiswrapper.svn.sourceforge.n...9&pathrev=2729

Just throw that file in the ndiswrapper-1.56/driver directory and try to compile it.

Also just to clarify, you know you can install ndiswrapper from Ubuntu's package manager? Try:

sudo apt-get install ndiswrapper

This way, you won't need to manually compile it. Just let the package manager take care of that!

And if either method doesn't work, may I ask what wireless device your using? If for whatever reason your unsure, you can run the following commands. If it's USB, try:

lsusb

And if it's PCI, try:

lspci

You should find the device with it's make and model listed. Let us know if you need any help.

[Shell_Eater]

Hi, Nagarjuna. I have tried using the wrapndis.c file
(fatal error: linux/inetdevice.h: no such file or directory compliation terminated...also tried putting it under driver directory and compiling ndiswrapper through the command line, same error messages)

the synaptic package manager (ndiswrapper didn't show up there)

and apt-get (it said it couldn't locate ndiswrapper...I get the sense this is user error).

I'm having a whole lot of problems; I ran lscpi, and while I can physically verify the wireless card is there, connected and undamaged, I don't see it in the list. But I can worry about that after ndiswrapper is installed.

I have trouble believing that this isn't my fault, because the machine was not having hardware issues before I installed ubuntu. No clue where to go from here.

[Nagarjuna]

Hey, bud. I'm afraid I gave you some out-of-date information about the ndiswrapper package in Ubuntu. Sorry about that, it's been awhile since I've used it! Here is a very easy and straight-forward guide for installing ndiswrapper onto your Ubuntu system.

https://help.ubuntu.com/community/Wi...er/Ndiswrapper

Again, sorry for the incorrect info. Let us know if you run into any problems.

[Shell_Eater]

Thanks for working with me, Nagarjuna. I checked that link. I went there at the beginning, and didn't stop to think - I am not running one of the long-term support versions! Big mistake on my part, I just assumed that there wouldn't be any issues at all with the most recent release. (That's what you get for using computers other people maintain for you your whole life.) Will install 10.04, go through the motions outlined by the link, and tell you whether or not it worked in a few hours.

(I just hope it isn't a hardware or user issue. I'm a newbie of limited means...)

Thanks again,
Shell_Eater.