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 posted this message in another related thread, but thought that I might want to start a new one for discussion ...
I am also attempting to utilize the MA111 wireless adapter w/ a newly installed version of Redhat 9 (2.4 kernel). I have read many forum discussions, manuals & guides, to no avail. I need some very basic instructions on how to accomplish this as I am pretty much a complete idiot on this OS at this point.
I see that usb-uhci shows up as (unused). I was able to locate a file (./usr/share/terminfo/p/prism2), but I am not quite sure what that means at this point. Does that mean that the driver is pre-compiled? If so, where to go from here?
The next step is to read the README file on how to actually use the thing.
Down the bottom you'll see:
FOR USB USERS:
A) Make sure your kernel usb support is running
B) Plug in the Prism2.x USB device
C) Run 'modprobe prism2_usb prism2_doreset=1' to load the driver into memory.
D) Run 'wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable' to initialize the
E) Run 'wlanctl-ng wlan0 lnxreq_autojoin ssid=<your ssid> authtype=opensystem'
to enable the MAC in Infrastructure Station mode.
F) Run 'ifconfig wlan0 <your IP address>'
Follow those instructions. The wlanctl-ng command is a read bitch to use directly (iwconfig is *way* easier, however it only works on cards that use the linux wireless extensions thing. I think the prism driver was written before these came out or something, anyway).
Well, no errors but a ton of warnings. One (at least cause there's several identical erros just for different identifiers,) is enough to stop even modprobe from executing. I tried recompiling everything with the original options from config.in (usb=n, pcmcia=y) and received even more of the same types (and other) warnings.
The unknown symbol warnings are apparently coming from the kernel version comparisons in src/include/wlan/wlan_compat.h. It's comparing the kernel version to 2.6.0 and defining symbols based on that. I'm running 2.6.5-1.358 and therefore ending up with a host of unknown symbols (e.g. usb_kill_urb, register_wlandev, etc....)
I'm going to try upping the kernel version numbers in that header to 2.6.5 and recompiling and see what happens then................
To get dhcp to work you'll need to install either dhcpcd (dhcp client daemon), or dhclient. Then run one of them after bringing the interface up (doing the wlanctl stuff and "ifconfig wlan0 up") so basically:
ifconfig wlan0 up
You may also need to run:
nohup dhcpcd wlan0 &
to put in in the background (nohup makes the program ignore SIGHUP which is a unix signal that's sent to all programs running in a terminal when the terminal is closed, the & puts it in the background).