• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Going from Windows to Linux

Page 4 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Alright after poking around in the source for module-init-tools and my kernel the "Invalid parameters" message is printed when module_init returns EINVAL and every EINVAL I see in the kernel's module.c is accompanied by a printk so something should be in your logs indicating why ndiswrapper failed to load.
 
Originally posted by: Nothinman
Alright after poking around in the source for module-init-tools and my kernel the "Invalid parameters" message is printed when module_init returns EINVAL and every EINVAL I see in the kernel's module.c is accompanied by a printk so something should be in your logs indicating why ndiswrapper failed to load.
Click to expand...

Hmmm.

I'll check into.

Been googling all day but gonna to call it quits in a few mins for the day.

Thank you for all your help.

:beer:
 
This is another reason why free drivers are so important, whoever makes your card would just release the specs on how to talk to it there would be a driver in the kernel and it would have just worked out of the box.
 
Originally posted by: Nothinman
This is another reason why free drivers are so important, whoever makes your card would just release the specs on how to talk to it there would be a driver in the kernel and it would have just worked out of the box.
Click to expand...

Well I might have to end up buying a new NIC for my fiancee's laptop so if I do I'll make sure to just get one that's on the compatible list and then give her my NIC 😛.

 
I got the -1 invalid error the other day and I never really knew why. I think it would happen with insmod but not modprobe, or something. Then I came across some undefined symbols (in the dmesg I believe) and just said screw it. (I installed some other sound driver than alsa and it disabled alsa and I couldn't figure out how to get it back.) So I just compiled alsa from scratch again and had no problems (I put the drivers in /etc/modules).

Maybe you should just remove every last remnant of ndiswrapper on there (and properly uninstall any ndiswrapper packages you may have gotten from your distro) and then try compiling the latest version from scratch again?

I'd be interested as to what this would report:
sudo -H -s
strace insmod /lib/modules/2.6.16.21-0.13-smp/updates/ndiswrapper.ko

Then we may be able to tell what went wrong. It'll be tons of output though so you may want to upload it as a file. If you don't feel like it that's fine too, I'm just curious.

sudo modprobe -v ndiswrapper

What does that report again?
 
I got the -1 invalid error the other day and I never really knew why.
Click to expand...

The -1 is just what insmod returns, what it prints after that is the important part and is the real clue as to why module_init in the kernel failed.

I think it would happen with insmod but not modprobe, or something.
Click to expand...

That's unlikely unless the module required some extra parameters that modprobe was feeding it but I don't know of any except some ISA modules. Which is similar to what I'm thinking is happening here only the opposite, that modprobe has some options configured for ndiswrapper that it doesn't like.

strace insmod /lib/modules/2.6.16.21-0.13-smp/updates/ndiswrapper.ko

Then we may be able to tell what went wrong. It'll be tons of output though so you may want to upload it as a file. If you don't feel like it that's fine too, I'm just curious.
Click to expand...

All it'll do is print whatever syscall does module_init and then you'll see it return EINVAL.
 
So I got tired of messing aruond with SUSE and decided to give Ubuntu 6.06 a try, good news is I got the NIC to come up bad news is I can't get an IP and when I do a dmesg | grep ndis I get the following.

root@compaq:~# dmesg | grep ndis
[17179604.104000] ndiswrapper version 1.8 loaded (preempt=yes,smp=no)
[17179604.244000] ndiswrapper: driver linksys (Cisco-Linksys, LLC.,01/05/2004,1.22.01.2004) loaded
[17179604.280000] ndiswrapper: using irq 11
[17179605.284000] wlan0: ndiswrapper ethernet device 00:0f:66:2e:0f:11 using driver linksys, 17FE:2220:1737:0029.5.conf
[17179605.492000] ndiswrapper (set_essid:61): setting essid failed (00010003)


Any ideas?

I can see my wireless network and the neighbors and set it to connect to mine but still don't get an IP, I even tried a static IP with no luck either (couldn't ping anything). I currently have my wireless wide open just to try and get this thing working but still nothing.

Also if it helps my wired internal NIC works fine.
 
OMG I got it working!!!!!!!!!


My essid was the issue!

It was two words with a space and had a "!" at the end so I just for the hell of it changed it to one word with no punctuation and tried again it worked!

But nows the next issue, can't get it working with WEP even seems that it will only work with an open wireless network which I don't like, any tips on how to configure wifi and security in Ubuntu 6.06 would be appreciated.
 
Anyone?

Still can't find a fix to get my WEP working which I need to use over WPA since thats all some other devices I have support.

 
wiconfig (I think) should be able to setup wep. Read the man page, ask us questions if you don't understand something.
 
I think it's iwconfig. There is a package called wpa2supplicant that should be able to use WPA too. For now I have also just left my wireless open for testing. I'll enable WEP on it one of these days and try to get Ubuntu to work with it.
 
iwconfig $device key <key>
iwconfig $device key on

or when you're inputting the key instead of <hash> I believe you can do, "s:<key in ascii>" to input ascii (the passphrase) instead of the actual key.
 
Originally posted by: SleepWalkerX
iwconfig $device key <key>
iwconfig $device key on

or when you're inputting the key instead of <hash> I believe you can do, "s:<key in ascii>" to input ascii (the passphrase) instead of the actual key.
Click to expand...

Well I gave this a shot but got error msg.

bash: syntax error near unexpected token 'newline'
 
Also should note that after looking on ubuntu forums, this seems to be a well established issue but I've yet to come across a solution so far.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top