PuppyThis forum is for the discussion of Puppy 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.
I know that there are many posts about this. I've tried both the "hybrid" driver and the one supplied by Tempestuous. For the latter one, the .pet file gets installed "successfully" but when I want to load the module in network manager I get the message "can't find the file" or something like that. For the hybrid one the command
returns an error saying the module is not the right format.
What am I doing wrong? Something weired which might be related to this is that when I write to my home folder I realize that it goes to
/mnt/home/home/ I thought one didn't have to mount their own home folder.
I have had insmod not work for me too with same error message.
Try depmod from the command line and then modprobe wl.ko
Maybe you can get lucky.
You might also be able to use the windows drivers for it using ndiswrapper to load them.
I used the windows drivers with ndiswrapper for a linksys USB wireless device and it worked.
Have you tried downloading the Windows driver for it and using ndiswrapper and then selecting the inf file for it?
I know that sometimes getting wireless devices to work is a real pain.
But the driver should have an inf file if you downloaded the one for windows. You select it instead of the sys file.
I downloaded the hybrid driver from Broadcom. The windows driver does not have the right extension(!) The extension was ".sys" I think.
Huh? Download the Linux driver on the broadcom site. You have to compile it tho, so you will need to have more then what puppy comes with by default. If you want I can email you a good wl.ko that should work if you are using a recent kernel. If not then you may need to grab gcc and the kernel sources to be able to compile it.