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.

Alright, done bragging, but if you just got finished building that Vegas Hoe you'd brag too. Now I need some advice!

I'm new to Slackware(1-2mths), not Linux (10+yrs). Me and OpenSUSE have been having problems for awhile now and her bags are packed along with KDE(10+yrs) for XFCE(1-2mths).

I don't have broadband where I live so I use T-mobile wifi as only connection to net. I need net to update with slackpkg(know how to do that), as well as to survive. I've been using wicd on my laptop w/Slackware and KDE. Is wpa-gui worth using or should I install wicd? Any suggestions on configuring wpa-gui?

You can't imagine how much of a noob I feel like, but any pointers in the right direction would be helpful as networking is not one of my strong points. I'm really missing Yast right about now.

Any other suggestions on configuring would be cool too as the tower is only a couple of hours old. And please excuse me, I'm not always such an annoying noob. I Promise.

Wicd works fine, but I like using wpa_supplicant more because it was a pain to figure out, and it's installed by default. I don't really use the wpa_gui, but if you need some quick tips on wpa_supplicant I'd be glad to get into that.

Hum. this ASUS board has the Wi-Fi GO card. From what I'm understanding this is broadcom but lspci shows the only network adapter being a Atheros Communication INC. AR9485 Wireless Network Adapter. Of which is not working with wicd. Am I looking this up right?

dxtrpn: yes I'd love to see your wpa_suppicant.conf. It would be a big help

NetworkManager is probably a more comprehensive tool for connectivity with the internet than Wicd is. You'll probably need the ModemManager tools as well to get your T-Mobile connection working. Both are available from SlackBuilds.org if you are running 13.37 but are going to be included by default with Slackware 14.0 in the final release.

I use wicd here with encryption (WPA2), so I see no reason why it shouldn't work. What make you think that wicd would not handle your card?

This is a card that comes with the asus p8z77-vpro board from asus called "wi-fi go!".

Installed wicd from my slack dvd with pkgtool. wicd is working but not showing *any* connections. lspci show my adapter as a atheros ar9485. So card is there. lsmob dosn't show any atheros modules loaded. gonna try that and see what happens.

There might be some firmware for that card (sometimes shipped with kernel-firmware, sometimes not). In addition to that, you're going to want to double check that it is using the drivers for that chip (I believe the module is called ath9k, but you can double check with "lspci -k" and look for the wireless card itself and the module being used).

Didier Spaier:
I'll get back to you with that ouput in a sec. As I'm using KVM switch to bounce back an forth between Towers. I do know that iwconfig only showed and lo and eth0 but no wlan0. Could there be something there?

Open wpa_supplicant.conf. Replace the line specifying the ESSID with the
corresponding line output from wpa_passphrase, and do the same for the PSK.
Remove or comment out what you appended to the document before opening it.

Open /etc/rc.d/rc.inet1.conf. Uncomment just a few lines- most importantly, the lines
use that specify you want to use wpa_supplicant and dhcpcd. You may also specify your hostname and essid.

/etc/rc.d/rc.inet1 start (or restart, whatever your case may be)

ping -c 3 www. A Web Site .com

Success!

If everything's properly configured, the scripts will run during as your box boots up.
I can't access the files on my computer right now, but they are simply the defaults modified
as I've described.