SlackwareThis Forum is for the discussion of Slackware 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 found this by using the "Search forum" button on the "Threads in forum" title bar of the main forum page. It's a good place to look for info on what your trying to do.
It is going to be far easier for you if you can connect to the net from Slackware with a cable first and then try and setup your Slackware wireless. You may need to be downloading drivers and tools to fix your problem and downloading them to windows and then getting them into Slackware can be a pain.
Wireless can be a bit of a nightmare at first anyway, especially if you have WAP setup. I have found it easier to first get a wired connection, second get a none encrypted wireless connection and then setup WPA or WEP. You may well have to do quite a bit of reading/searching to get your answers (unless someone gives you a set by step detailed way of doing this) but this will teach you a lot.
Not wishing to sound cruel or try and put you off here but if you want your wifi to "just work" instantly then maybe Slackware is not for you. I found that PCLinuxOS was the only distro (and I have played with a lot) that would "just work" with my wireless WPA setup. I don't use PCLinuxOS much as I love Slackware and have got my wireless working but it took a lot of research (I feel it was worth it ) but I am quoting this as an example.
I think this is a bug, similar to the Ubuntu bug reported last week with Radio Kill switch:
I have every loaded and reloaded many times, I still cannot get my eth1 to be deteced as a wireless device:
modprobe -r ipw3945
outputs the following in dmesg:
Jul 12 12:33:14 xps-m1710 kernel: ipw3945: Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.1d
Jul 12 12:33:14 xps-m1710 kernel: ipw3945: Copyright(c) 2003-2006 Intel Corporation
Jul 12 12:33:14 xps-m1710 kernel: ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Jul 12 12:33:14 xps-m1710 kernel: ipw3945: Detected Intel PRO/Wireless 3945ABG Network Connection
Jul 12 12:33:15 xps-m1710 kernel: ipw3945: Radio Frequency Kill Switch is On:
Jul 12 12:33:15 xps-m1710 kernel: Kill switch must be turned off for wireless networking to work.
I haven't found or googled and adedquate solution as I am juggling this while trying to work LOL but I feel your pain since I went nuts all day reloaded and recompiling crap...I can't figure out why this suddenly happend, but it seems to be ACPI related, I may end up trying a kernel boot parameter to turn it off