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.
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.
Nevermind, now the network card is enabled,but the signal really sucks now.Even the router is behind me, I cannot open the website. Anyway,thank you,Dan, so now I got this problem to fix.
Now I have the last problem, my wireless network can't get the signal,it can search the network, but it shows on the wifi-manager that it's out of range. Here is the snapshot. What does that access point mean, I made the configuration according to the walkthrough Bob provided, but no luck for me to open the website through wifi.
Finally I got wireless up and running, but another problem arises, everytime I reboot, the configuration just goes away, which means I have to follow the steps Dan gave again and turns it back to normal. What's weird is I've added the line "/sbin/modprobe ndiswrapper" in rc.modules, which was supposed to keep the computer booting as you like, but now each time I reboot my laptop, it just fades away, anyone knows why this happens?
And now the even more weird thing is if I unplug the cable, I won't be able to logon after reboot with ethernet or with wireless,even after plugging the cable again. Sorry I made so many posts in this thread, but this wireless thing is really getting on my nerves these days.
Check if bcm43xx module is loaded at boot time.
If this is the case, you should add this module to the blacklist.
Then redo ALL the steps I've indicated previously.
Thanks again for everyone's help, now I got my wireless up and running well, but still I don't know why I have to plug in the cable before booting if I want to use the ethernet card, anyway,I'm so glad I've learnt so much from you guys.
You have to plug in the cable in order to get an IP from dhcp.
You may also do:
dhcpcd eth0
if the ethernet card is eth0 and you'll have the interface up and running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.