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!
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'm using SuSE 9.2, and i cant seem to get my wireless internet to work on it
i used the YaST wireless card set up to get it to (i hoped) connect
it's a 2wire router, and from digging about in my windows partition and wireless settings, i found out that it's an o[en network
and ad-hoc something (i wrote it down, but i didnt take very good notes, i guess)
there's a 10 digit code that the router needs to let me connect, i'm not sure what sort of password it is, (ascii, hex, or passcode)
wow, this is not that clear at all. ask questions, i'm sure i'll be able to answer them (at least, about my stuff(theoretically, at least))
thanks in advance
The model number would be a good start, and the chipset would be great to have. Sadly, the chipsets often change on cards without notice, and without model number change, so figuring out your chipset could be hard.
Im assuming your on the same PC right now using windows to post here.
If so, go to your network card properties (right click the 'wireless' icon beside the clock, click Configure, then right click the connection you see, and Properties. You shuld see "Connect using [your network card]" and beside it a Configure button. click that. There it will give you a little information about your network card.
For my rubbish Belkin Wireless, it says Manufacturer: Broadcom.
That helps alot when needing to get the proper drivers. Try and see what manufacturer you got.
but i have no way of transfering the text from linux to my windows partition :\
if you could tell me what i was looking for? maybe that could help
lspci listed both my wireless card and my ethernet card, but i dont see how recognizing both could be a problem, especially if the ethernet card doesnt have any internet connection
the rest looked like it was just stuff off of my motherboard, b/c it was all VIA stuff, and i have an ASUS motherboard that has VIA chips
lspci -n gave me a bunch of stuff that i couldnt understand, the first 3 things on the list was
0000:00:00.0 class 0060 1106:3099
0000:00:01.0 class 0604 1106:b099
0000:00:09.0 class 0003 1106:3038 (rev 50)
this is hexadecimal, right?
i supposed i could have writen more of this stuff down, but i'm on my way to class. i'll try the iwconfig (do i have to be root?)
if you could tell me what i have to look for in lspci, it would be a lot easier, as well as teach me more
To be honest, I'm not much help at this point. My knowlege on if a wireless card is working or not goes as far as 'is the light on after issueing xxxx command'. However, I do know of am old DOS trick (probably a UNIX trick that DOS stole ) that could help you with posting output of commands when you have to go back and forth between partitions. Type the command as usual, then after the command.... type a space, a greater than sign (carrot), another space, and then the name of a file of your choosing. This will save the output of the command to a text file instead of outputing it to the screen. Here is an example of that with the 'ls' command.
ls > ls_log.txt
or you can use a absolute path name
ls > /home/user/text_output/ls_log.txt
Using this, you can save the outputs to a floppy or memory key and simply bring them up when you reboot into Windows.
Just because Yast detects the card and knows what it is, does not mean that it will work without more work. I had the same issue with my card, Yast detected it fine, but I had to use ndiswrapper to get my card working.
Ndiswrapper is an very ingenious program that uses the Windows drivers to run and control wireless cards that have no Linux drivers written for them. However, in my experience, it is also a major headache to setup (never have been completely successful with it).
iwconfig is part of wireless tools, which you may or may not have. If you need to download wireless tools, its at sorceforge. There is a link along with some information about wireless tools for linux here: