Linux - Wireless NetworkingThis forum is for the discussion of wireless networking in Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Finally figured out how to get ndiswrapper going. And to my surprise my computer actually liked it. I followed the instructions step by step but get an error that is not covered in the install manual. This is after I run ndiswrapper -l and it tells me the driver is present and the hardware is present.
#depmod -a
*got no error it just would hang for a bit then go back to the prompt*
#modprobe ndiswrapper
Fatal: Error inserting ndiswrapper (/lib/modules/2.6.13-15-defualt/extra/ndiswrapper.ko): operation not permitted
???
It should be due to the linking thing they talked about earlier in the manual because my make install when off without a hitch. Any ideas?
I feel I am so close to finally getting my card up and running!!!!And it will be nice
Last edited by samuelLjackson; 10-18-2005 at 06:03 PM.
Lol I guess I just realized I didnt post any of my specs. Got a dlink 510 (should be 2nd revision and am using the drivers on the cd like the guide said). Running suse 10.0. Any ideas fellas I really want to get my wireless up and stop using window$
Can you load any other modules or is this error limited to ndiswrapper? The reason I'm asking is that there are two possible explanations that come to mind:
- Your kernel was compiled to NOT allow modules. It would be weird, but you can compile a kernel this way.
-The user you're using to load the module doesn't have sufficient permission to load kernel modules. This would be most likely if you used su to become root.
By the way, I don't think you need to run depmod. However, it also shouldn't hurt to have done so.
Thanks for the reply. I am a linux newbie so I don't know how to find out if my kernel doesn't allow modules or how to load other ones. I just did the regular install of the new SuSe 10.0. So I would think I could add modules. And I did run this as su. How do I add another module to see if that is the problem?
Hi,
I installed ndiswrapoper today in SuSE 10.0 OSS today.
I got the same problem, but I did try a few times, uninstalling and rebuilding the program, and a few tryings, I got it! I don't know if I was lucky or did something differently, but it worked.
Maybe my answer is not too helpful, but I'm just telling you: don't worry, it will work!
Originally posted by samuelLjackson Thanks for the reply. I am a linux newbie so I don't know how to find out if my kernel doesn't allow modules or how to load other ones. I just did the regular install of the new SuSe 10.0. So I would think I could add modules. And I did run this as su. How do I add another module to see if that is the problem?
Yeah, if it is a stock Suse kernel, it should have the ability to load modules. The easiest way to tell is to run lsmod in a console. If it lists modules, then your kernel can use them.
I'm guessing that using su is the problem. Did you use su or did you use su -. Note the - after the su. If you didn't use su -, I would try doing that. Using su - causes su to create an envirnoment more like you had directly logged in as root, and sometimes it makes a difference.
Ok Tried the su - thing. Didn't work. Tried logging in as root and running it. Didn't work. lsmod did indeed bring up a garbage load of modules. So it should'nt be that. I guess I am going to delete and retry everything logged in as root. Maybe that will do it. Only problem is how do I delete ndiswrapper? lol I know how to make and make install but not delete. THanks for your help guys.
I think that starting around ndiswrapper 1.1, they included a make unistall command, so if your version is later than that, jump into the directory you used to compile and type make uninstall. If that doesn't work, there are good uninstall instructions on the ndiswrapper wiki. See my sig for the link.
Quote:
I guess I am going to delete and retry everything logged in as root.
I guess I'm a little confused by this. Were you not root when you ran make install?
My guess is that either you kernel-source link isn't present, or you have two versions of ndiswrapper installed at the same time. Is your kernel-source file installed and did you create a symbolic link to it as instructed in the first step of the ndiswrapper installation instructions? You'll know you've created a good link if it tells you "link exists." Also, ensure you don't have two versions of ndiswrapper installed together, but I bet the link is your problem.
I would first remove your driver with the "ndiswrapper -e driver" command (where driver is the name of the driver you've installed), run "ndiswrapper -l" to ensure it was removed, and run "make uninstall" from the ndiswrapper directory. It doesn't even hurt to run it twice as it explains! Then, make sure you've done the "Prerequisites" paragraph found here http://ndiswrapper.sourceforge.net/m...p/Installation Next, reinstall ndiswrapper and your driver and see if you still get the error. MAKE SURE you are logged in as root for the make install command!
Last edited by Agentvenom; 10-22-2005 at 06:45 PM.
NOTE: Windows driver configuration file format has changed since 1.5. You must re-install Windows drivers if they were installed before.
make[1]: Leaving directory `/usr/src/ndiswrapper-1.10/utils'
mkdir -p -m 0755 /usr/man/man8
install -m 644 ndiswrapper.8 /usr/man/man8
root@darkstar:/usr/src/ndiswrapper-1.10#
root@darkstar:~# uname
Linux
root@darkstar:~# kernelversion
2.4
root@darkstar:~#
then i modprobe list :
root@darkstar:/mnt/wind/linux tuto/anyeng# modprobe ndiswrapper
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_read_config_byte_Rsmp_3ccefab4
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol free_irq_Rsmp_f20dabd8
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol strstr_Rsmp_1e6d26a8
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_unregister_driver_Rsmp_e8061e13
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol usb_deregister_Rsmp_f866a128
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol usb_register_Rsmp_3c7dbaf5
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_free_consistent_Rsmp_1bfc1908
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol _ctype_Rsmp_8d3894f2
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol sscanf_Rsmp_859204af
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol unregister_netdev_Rsmp_d23a054e
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_disable_device_Rsmp_95846005
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol simple_strtol_Rsmp_0b742fd7
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol netif_rx_Rsmp_a023a113
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol vsnprintf_Rsmp_6989a769
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol add_timer_Rsmp_a19eacf8
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol del_timer_Rsmp_fc62f16d
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol misc_deregister_Rsmp_f683d127
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol mod_timer_Rsmp_1f13d309
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol __tasklet_schedule_Rsmp_ed5c73bf
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol eth_type_trans_Rsmp_e18b86cb
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol tasklet_kill_Rsmp_79ad224b
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol complete_and_exit_Rsmp_3caea255
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol __out_of_line_bug_Rsmp_8b0fd3c5
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol schedule_task_Rsmp_2d6c3d04
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol usb_ifnum_to_if_Rsmp_391684f1
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_set_master_Rsmp_99cc7ae2
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol iounmap_Rsmp_5fb196d4
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_alloc_consistent_Rsmp_ca1c24c8
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol __kfree_skb_Rsmp_63a98146
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_set_power_state_Rsmp_11eecaa6
/lib/modules/2.4.31/misc/ndiswrapper.o: /lib/modules/2.4.31/misc/ndiswrapper.o: unresolved symbol pci_request_regions_Rsmp_01186146
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.