Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hey, It took me a week and a half to figure out how to get this thing going. Here's the idiots version of installing it. Download the .zip file for your version of Redhat . If you dont know your version go to the Terminal and type uname -r Next you'll have to unzip the file and then type rpm -i <driverloader file name>.rpm This will install the driver. When its done, open your web browswer and type http://localhost:18020 and enter root for user name and your root password. You have to select your windows driver files that you put on your linux machine. its *.inf and *.sys file. Once you do this, get a license key from linuxant.com and then you're set.
Let me know if you have questions.
Yup - some 54Mb cards seem to be moving to the TI chip, which presently has no linux driver. Some manufacturers are making the switch with only a minor change to the card's name (check the tiny v2 on the Netgear box).
There is a driver project in early stages at http://acx100.sourceforge.net . In the meantime maybe the linuxant driverloader discussed here might work.
(sorry to be going off-topic but original poster seems to have got a good answer).
The WPC54G card works with the ndiswrapper module, available from ndiswrapper.sourceforge.net. I've got it working with the windows drivers on the Linksys website. I had to edit files in /etc/sysconfig/network-scripts by hand (horrors!) to get dhcp working and the file /etc/pcmcia/config to get the module to load automatically when the card does. But it's now working like a charm.
I'm no expert with these things, but that sounds as if you're missing some library or other. Have you installed the right driver for the WPC54? If so, did you compile ndiswrapper yourself? Those sorts of runtime errors usually turn up as compile-time errors if you do, and you can then figure out what you're missing. Email me directly if this is no help.
I have the WPC54G but it is version 4. I just bought it a few days ago. The only driver I think works is the one I got off of the CD. The reason I think it is the only one that works is because it is the only driver that displayed the present word next to it when I did the ndiswrapper -l.
I compile the ndiswrapper myself by doing make install. I do not receive any errors... it puts the command in my /etc/sbin folder. I then add the driver to the list with ndiswrapper -e <driver name> and it displays the present keyword. I then type modprobe ndiswrapper, like the install readme, and I receive the above error. Is there a place to start to troubleshoot this, I could use some options on where to start or what to look for. Thanks!
I'll have a look at my installation later today. It's not on this machine. But you certainly could post a message to the ndiswrapper mailing list. Someone there may have seen the problem before. If you google NdisMAllocateSharedMemoryAsync, you'll get references to some of the Microsoft documentation on NDIS. That may give you a somewhat better sense of what the problem is. Somehow, though, that function isn't being found when everything is dynamically linked. You might check the ndiswrapper source and see where, and if, it is defined. But I'd guess the mailing list is your best bet.
O.k. I have figured out that the NdisMAllocateSharedMemoryAsync is a function contained within the ndis.h header. My question is, how can I load the proper libraries and where could I find the library containing the ndis.h file. I'm hoping that once that library is in place I won't receive any error and the card should work fine. Thanks for your help! Rod