Linux hangs after having installed WMP54GX Linksys driver in NdisWrapper
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.
Well, I can now honestly say I'm stumped. Your installation procedure seems fine, and as long as make didn't throw any errors, ndiswrapper should be fine. I'm also assuming that when you loaded the Windows driver, you had a .inf and .sys file in the same location.
Which kind of leaves us with a nasty problem, namely that this card may not work with ndiswrapper. The only think I can think of would be to search the manufacturers web site and try any drivers they have for this thing, even old ones.
Sorry, but I'm not sure that helps. The problem is that this card and chipset are new, and as usual, the manufacturers offer absolutely zero linux support. I've done a bit of googling, and I'm not finding any success stories except the one I pointed out a couple of posts back.
The only suggestion I've got at this point it to give linuxant another go and see if it can handle the driver.
I still have some options, but meanwhile I am thinking about changing the card, if I won't have success during the next days.
The idea I have is to add option values to the /etc/modprobe.conf file additionally the the alias ("alias wlan0 ndiswrapper"). I found mem values (0xddee0000 and 0xdde00000) and the irq value (11) for this card, and I think I'll add an io value as well. Of cource this is only experimental...
The only suggestion I've got at this point it to give linuxant another go and see if it can handle the driver.
I tried it with Driverloader - and it also failed. Here is the extract of the kernel messages:
Code:
sbcore: registered new driver driverloader
driverloader: wnihdd51.sys: 0xe1353000..0xe1420200 entry = e141bc00 (pbase = 0x10000)
driverloader: /var/lib/driverloader/ntoskrnl.exe: unable to open (err=-2)
driverloader: wnihdd51.sys: export not found: InterlockedPushEntrySList (ntoskrnl.exe)
driverloader: /var/lib/driverloader/ntoskrnl.exe: unable to open (err=-2)
driverloader: wnihdd51.sys: export not found: strstr (ntoskrnl.exe)
driverloader: /var/lib/driverloader/ntoskrnl.exe: unable to open (err=-2)
driverloader: wnihdd51.sys: export not found: MmIsAddressValid (ntoskrnl.exe)
driverloader: /var/lib/driverloader/ntoskrnl.exe: unable to open (err=-2)
driverloader: wnihdd51.sys: export not found: InterlockedPopEntrySList (ntoskrnl.exe)
driverloader: /var/lib/driverloader/ndis.sys: unable to open (err=-2)
driverloader: wnihdd51.sys: export not found: NdisInitializeReadWriteLock (NDIS.SYS)
driverloader: unable to load "wnihdd51.sys" (-6)
I've changed the netani.inf file a little bit, e.g. I have deleted all lines with "wnihdd51.sys" (seems to be the XP driver), so that the other sys file (wnihdd50.sys, W2K driver?) should only be loaded. It is a bit curious for me that the kernel log messages mentioned above appear even after having deleted the lines with "wnihdd51.sys". Do you have any ideas for that behaviour?
It is a bit curious for me that the kernel log messages mentioned above appear even after having deleted the lines with "wnihdd51.sys". Do you have any ideas for that behaviour?
To be honest, not really. My understanding of Windows drivers is fairly limited, but it seems that this one might be linked to more than just a single .sys file. I may be 100% wrong about that, but if this driver doesn't comply with normal Windows rules, it would explain why ndiswrapper and linuxant can't use it.
Quote:
I found links to software from Airgo Networks Inc., die Producer of the used Chipset on the Linksys card, and from Belkin:
The stuff from Belkin is useless, at least for fixing your problem. It seems to be the software for one of their routers. I haven't been able to download the stuff from Airgo (their server is frighteningly slow) but again, if this isn't a driver for the cards, it probably isn't going to help your problem. At least not in the near term. It was something like this that allowed the Broadcom 43xx chipsets to be reverse-engineered, but that takes a LONG time to happen.
Quote:
I use the 32bit version from OpenSuse and the mentioned software.
Nuts. I was hoping I had just overlooked something simple.
I think if you want wireless you're going to need to use a different card under Linux. I'm just not seeing anything wrong that I have an idea of how to fix.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.