Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
I have tried about 15 different linux distros and have to always come back to Mepis Linux because it is the only linux that works with wireless(Broadcom) right from the start. Can't get my wireless to work with any of the "major" versions of Linux. I can't understand why I can only find one that works....I know there are driver issues with some cards, but how can mepis get it to work, and no one else can? what are they doing?
mepis does not have the greatest documentation, and my sound does not work correctly, but my wireless does, so I keep installing various versions of linux, and just keep re-installing mepis......
Apparently mepis comes with the appropriate wireless driver already installed. If you figure out which driver it is using, you should be able to install the same driver in any other distribution and have functioning wireless adapter.
I suggest that you get a ralink rtX based card. They work out of the box with most distros and there are also opensource drivers available at seamonkey. I suspect Mepis is including the firmware for the broadcom chipset in its distro when other distros are not.
Apparently mepis comes with the appropriate wireless driver already installed. If you figure out which driver it is using, you should be able to install the same driver in any other distribution and have functioning wireless adapter.
I have tried using the correct driver, but still no luck.
On my HP laptop, the front of the laptop has a light which indicates the wireless is active. It turns blue when active. When winxp is booting, you can see the light turn blue, meaning the driver has been activated. I can't get that to happen with Linux, except mepis linux.
When I searched for a driver that works in windows, all I could find was the .sys file and not a real driver. any suggestions for a good reference for getting wireless to work? I would really like to use another distro, other than mepis.
For what it's worth, my laptop also has a light that should brighten when my wireless is active. I have never had the light function while in linux, and yet here I am
I'd be interested to know what ifconfig and iwconfig said about your wireless card in both your current distro and others.
I had my regular NIC device go out on my laptop and had to get wireless working on it. It didn't take too long. I used the bcm43xx driver in SuSE 10.3. If you have a regular wired NIC connection, there is even an "install_bcm43xx_firmware" that will download the needed firmware on the net. Then it is a simple matter of modprobing the bcm43xx driver and running YaST2 to configure wireless networking including the WPA-PSK encryption. If you do it manually, you need to read the bcm43xx_fwcutter's README file to learn that the *.fw files need to be copied to /usr/firmware.
Lately I've had problems getting ndiswrapper working. Previously the bcm43xx driver was limited to 10 mb/s and didn't support wpa but that is no longer the case, so it is usable now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.