Ndiswrapper Information

Nicely done andrewd18 ^_^

can i add it to my guides on my signatures?

Thanks again ^_^
[/b]

Yes you may; just remember that we have a limit on the number of lines one can have in one's signatures.

many thanks i'll try to keep that in mind ^_^

Andrew,
Thank you for the informative instructions on getting ndiswrapper working with Suse 10.1 32 bit. It always worked with Suse 9.x but it seems to be a bit coy with 10.1. The following is just for your interest. If I use YAST and the new Newtworking tools I can get my Belkin card working OK. The only problem is that every time I try to connect to my AP then I have to supply the pass phrase for the WEP. It does not seem to remember even though it is contained in the configuration file. If I use the old tools in YAST then nothing operates after boot. I tried your script file and that does not work either. I should note that I am using ndiswrapper that came with the CD rather than downloading the latest version. Do you think that this will make such a difference ?

Regards

John

A lot was changed in 10.x, which really hurts the use of the old tools. I recommend you stick to entering the passphrase all the time, as it's the least trouble out of all the things you mentioned.

Second... it's not *my* script file, it's someone else's. I can't write code (excepting HTML) worth a darn, especially an init script.

If you can get your card working with the ndiswrapper on the CD, great. Go for it. The only reason I recommend that people use the latest version is for the numerous bugfixes (which your card apparently does not need).

~~ Andrew D.

A lot was changed in 10.x, which really hurts the use of the old tools. I recommend you stick to entering the passphrase all the time, as it's the least trouble out of all the things you mentioned.

Well just for the fun, I stripped out the CD version of ndiswrapper, downloaded version 1.23 and re-installed everything. It still works in the same way which, as you say, is the least of the problems.

Second... it's not *my* script file, it's someone else's. I can't write code (excepting HTML) worth a darn, especially an init script.

Sorry for the "your script" I know you didn't write it but it was a recommendation on your info page and I thought it might help others to know that it does not necessarily work.



Regards

John

I'm going to try and get this revised sometime over the next few weeks. People have been having problems connecting after setting it up with YaST, and I've been rather buggered with the current formatting. It just seems clunky to me. Hopefully, I can also get around to that 9.x revision I've been meaning to do since May. (all the 10.x changes have kept me busy enough!) <_<[/b]

I didn't change the 9.x edition, but the 10.x is now at version 3.1. I'm thinkin' I won't update the 9.x how-to until I get some complaints on it, because 9.x is being deprecated with the 10.2 release, and that's due in a few months.

Anyway, it's done.

If you have any tips, tricks, or other things you'd like to see added to it, please send me a Personal Message or an E-mail and I'll try to get it in the next revision for you. [/b]

This still stands. Send 'em in, if you have 'em.

Sorry for the "your script" I know you didn't write it but it was a recommendation on your info page and I thought it might help others to know that it does not necessarily work.
Regards

John
[/b]

By the way... I did do some research into init scripts for SUSE, and I've modified the script in 3.1. Hopefully it will help with some of the issues I've been hearing about lately. (although I doubt it'll solve yours just yet).

~~ Andrew D.

Hej Andrew

Thank for your NDISwrapper Setup information!
I got through following it, and my equipment was:
SuSE 10.1, HP Pavilion zv5140EA with Broadcom BCM4301.
Found the Windows drivers on window partion with files:
bcmwl5.inf
bcmwl5.PNF
bcmwl5.sys

I download ndiswrapper-1.25 and followed your instructions.

The only place I went wrong and not reading carefully the text, was after: make install (which went okay), but I tried to make a symbolic link like: ln -s /usr/src...../build.

Yours
Jan Holm

(2006-12-03)
Release 3.2
* Adjusted the tutorial into 2nd-person. Should be easier to read now.
* Made the 64-bit driver warnings more obvious.
* Fixed some of the images slightly.
* Tried to explain that getting no output from modprobe ndiswrapper is normal.
* Fixed a really, really stupid typo in the <Path to Windows XP Driver> section.

Im new with Suse - so I don't know is there a reason why You prefer to buid ndiswrapper Yourself . As I understand there are ready packages present - is there something wrong with them ?

Originally posted by FAQ
# Why do you tell people to use the newest ndiswrapper instead of the one that comes with SuSE? That seems really stupid and sadistic.

To be short - the SuSE-included version (on 10.1, not sure about 10.2) is old and doesn't contain some important bugfixes. On top of that, there are no maintainers for a ndiswrapper package (as far as I know), so using the source is the only way to go for that new version.

If people can get their cards to work with 0.12, that's great for them. I just think it's worth it, particularly considering how much ndiswrapper has changed since 0.12, to use the latest and greatest.