SlackwareThis Forum is for the discussion of Slackware 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.
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 have installed Slack 12 on my laptop and am attempting to get the wireless card working. Mods, please either lock or close the other thread I started as I am unable to delete it myself.
Anyway, I installed the windows driver for the card, which is a Belkin N1 WiFi PCMCIA card model F5D8013, using ndiswrapper, then built the module using
Code:
ndiswrapper -m
then installed the module using
Code:
modprobe ndiswrapper
which seemed to work as the light came on the card.
Bear with me as I am not on my machine ATM, but I can get the exact outputs later. lspci shows it as an ethernet controller made by the Marvell Technology Group, inc, but says it's an "unknown device". I've followed the steps in the slack book, but unfortunately netconfig doesn't do anything with wireless, and after editing in the information for the wireless network in rc.wireless.conf and then running rc.inetd1 or rc.inet1, one of those as I cannot remember right now, the card is still not functioning. iwconfig shows wlan0, but I am unable to use
Code:
#iwconfig wlan0 essid spiderweb
#iwconfig wlan0 mode auto
#iwconfig wlan0 key ""
#iwconfig wlan0 AP spiderweb
to change any of the settings. It acts like it changes, but when I run iwconfig again it shows that nothing has changed. Can anyone give me some ideas? I know the card works as I am able to use it in windows, so that is not an issue. Thanks!
Anyway, I installed the windows driver for the card, which is a Belkin N1 WiFi PCMCIA card model F5D8013, using ndiswrapper, then built the module using
Code:
ndiswrapper -m
then installed the module using
Code:
modprobe ndiswrapper
which seemed to work as the light came on the card.
Bear with me as I am not on my machine ATM, but I can get the exact outputs later. lspci shows it as an ethernet controller made by the Marvell Technology Group, inc, but says it's an "unknown device". I've followed the steps in the slack book, but unfortunately netconfig doesn't do anything with wireless, and after editing in the information for the wireless network in rc.wireless.conf and then running rc.inetd1 or rc.inet1, one of those as I cannot remember right now, the card is still not functioning. iwconfig shows wlan0, but I am unable to use
Code:
#iwconfig wlan0 essid spiderweb
#iwconfig wlan0 mode auto
#iwconfig wlan0 key ""
#iwconfig wlan0 AP spiderweb
to change any of the settings. It acts like it changes, but when I run iwconfig again it shows that nothing has changed. Can anyone give me some ideas? I know the card works as I am able to use it in windows, so that is not an issue. Thanks!
Is the LED you speak of the link?
You can modify the '/etc/rc.d/rc.inet1.conf' file to setup the device. If you modify the configuration then just do a; '/etc/rc.d/rc.inet1 restart' to use your modified configuration.
Post the output of the following as root from the cli;
Code:
~#ifconfig -a #kernel at boot see what?
~#route -n #what is the route table?
~#lspci -vv #what devices are seen? Marvel makes
#several.
~#lsmod #what modules installed?
The above information should help diagnose the problem.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
First thing to do is disable any security on the router. No wep, wpa, wpa2, mac or ip filtering. Setup dhcp if not already. You want to make the connection as simply as possible. You may have the key right but the interface is not working. Just make it as simply as possible. Once you can make this connection reenable security you want and configure for that.
You can modify the '/etc/rc.d/rc.inet1.conf' file to setup the device. If you modify the configuration then just do a; '/etc/rc.d/rc.inet1 restart' to use your modified configuration.
Post the output of the following as root from the cli;
Code:
~#ifconfig -a #kernel at boot see what?
~#route -n #what is the route table?
~#lspci -vv #what devices are seen? Marvel makes
#several.
~#lsmod #what modules installed?
The above information should help diagnose the problem.
Dude, you are the man! Editing rc.inet1.conf with the pertinent information got it up and running right away! Thanks a million. Likely that was my problem with the initial Kubuntu install as well, but I like Slackware better anyway, so it's going to stay.
Edit: It's a bit slow, but I'm sure that's just more configuration that needs to be done, at least it's connecting now, and that's what's important.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.