And step 3 onwards isnt working. It's very frustrating because i can connect, but cant "save the configuraton". Hi all, Is it possible to revert to the "standard" package after doing: rpm -Uvh wireless-tools I need some help here people. I've followed the tutorial, tried many packages, but I just get "command not found" each time I'm trying to do something.
I am a Linux newbie, so that may be the problem. Would anyone please tell me what I'm doing wrong????? I've tried the --force thingi ang get the message with Preparing Is this correct?? Using YDL 6. I still cant get this working. Im using the latest build of YDL6. Anyone else still having problems? I just did the install on YDL 6. The two things that caught me out The guide is awsome, theres just a few gotchas that tripped me as stated above. This is a great site. Thank you for your information.
However I am unable to edit the system files to enable on reboot. I yhink it has something to do with being read only files. Can anybody help me to edit them. I am using ydl 6. I'm having a bit of trouble.
There seems to be a lot of people having trouble getting this to work on reboot. Is there something we are all missing. Everything works find up to the last ifup eth0. If anyone could help there would be a lot of happy people on this site, including me. I've also had problems with the reboot.
So I've just put a temporary startup script together until the real fix comes along. This guide is too confusing. Proberbly tried it 10 times today and still no succes. Always get to the 'dhclient eth0' and then it claims that everything fails. Puts me understress for no reason. I can't seem to get this to work. I have to repeat the steps in the guide to get any connection. All attempts to get it to work on boot up fail. Please help. Tried this after MANY attempts to get 6. Now, it works!!
Thanks for the guide pal!! Very helpful for a complete bozo like me! Without out this guide I would be bald by now!! Cheers, Beeblebrox PSN name.
Success on PS3. Everything you need is in the guide and the forums. I used the original wireless tools package and these worked just fine. Only took about 10 minutes once I got all the commands down and replaced some batteries Linux is very picky about file directories. If you place the wireless package on your desktop you need to specify that file location for the rpm cpmmand to find the file i.
Also note that the directories are case sensitive. A lower case "D" on desktop will not work. Then run the rpm command from the correct directory. From here continue with the guide. Make sure you place. Take some time, print the whole thing out and follow the directions exactly. I used nano for editing the files for the reboot to work. When done hit ctrl x, then y then enter to save the changes. Remember the ssid is case sensitive and to type the commands exactly as you see them.
Also, if yo uare using a wireless keyboard, make sure the batteries are fresh. Seems trivial, but for speedy typers this can be a big pain when half your carachters are not registering lol. Hope this helps some more of you out. Thanks alot for this guide and all of the great forum posts people.
This thread was a life saver! I'm a complete newbie at this Yellowdog thing and this was really straight forward. All the extra comments about what folders to go to and having to be in the root, etc Thank you and keep up the great work! I am one of those who has upgraded to 2. Has anyone had any success with a scenario like mine. I will try with the latest wireless tools rpm package: wireless-tools I wonder why hypervisor prevents you from using both at the same time.
I have the new 2. I try this guide but is it impossible to go with this steps guide instructions I can't put any router cable feet!!! Thanx Thanx Thanx. Thomas, have you downloaded or transfered "wireless-tools Make sure that you are the user "root". Thanks to daChaac for the thorough writeup as well as the other folks for adding their invaluable comments, otherwise I wouldn't have gotten this to work, but I did.
Some advice that took me about 4 days of trying to compile And on the reboot setup, I used the network-scripts directory and then created the files from scratch-then it worked for me. Go to the terminal on your shelf in Linux and double click on it. Change your directory to the Desktop with- cd Desktop then type in the rpm -Uvh wireless-tools I had to look up some linux commands to be able to create some files, because the ifcfg-eth0 file wasn't there, as well as the keys-eth0 file.
When you are finished with that, hold down ctrl D again. Hi, just installed yellow dog 6. Im loged in as root and still says access denied. It does the same when i try to access the scripts also. Im stuck and im doing everthing i can but will not let me access the files???? Please any help would be great.. To confirm that you are running as root at the terminal, use the "id" command.
Hi Calvin Since this guide is over a year old, and it is based on a version of YDL from a while ago v5. So that's why I felt the need to put up my notes on how I got things working with the current version of Yellowdog. It is certainly not the only way, but it seems to at least get things working for now until someone can help find a more efficient and effective method.
Some quick pointers: - YDL 6. So you can ignore daChaac's tips on getting the packages downloaded and installed. The current version has all the right software to get things working, it is just odd that for some reason the easy way of doing things doesn't seem to work well, it doesn't work for some of us at least. Hence the need to break out a bash shell and start typing stuff at the command line unfortunately!
So that is why you get nothing when you try to get iwconfig to probe that device. So that is why iwconfig DOES give you details when you tell it to probe that device. You should therefore be able to get basic unencrypted wifi networking, or even WEP encrypted wifi networking going quite easily although I didn't try this, as I use WPA now for my network.. I know it looks quite scarily advanced it is not really that scary nor advanced , but one of the main reasons I put in so much detail was to hopefully help anyone who is a bit unsure to see what the output of the commands should look like, instead of just talking about typing something without you seeing an example of what I mean.
If you follow the steps on my blog page from where I have "-- 1. Created the startup link in runlevel 3". You should be able to follow each step from there - the prompt should look the same or quite similar ending in the ' ' sign and you type the commands in from there as I typed them in. You should see the same or similar out put.
For each command you are not sure of what it is or means, try google for the manual page info e. Good luck in your Linux crash-course! Post a Comment. I looked around and found some free webspace for prebuilt binaries and for modified source RPMs.
Please note that you will need your YDL root account in order to complete steps below. This guide was last updated on: 4. You should be able to follow each step from there - the prompt should look the same or quite similar ending in the ' ' sign and you type the commands in from there as I typed them in.
You should see the same or similar out put. For each command you are not sure of what it is or means, try google for the manual page info e. Good luck in your Linux crash-course! Hi Adhir Lalla Thank you for the feedback. I've changed the font and template for my blog, so hopefully it will be easier to distinguish between a zero and the letter "O" now.
Hi Stephen, I'm back on this now after a bit of a break using the ps3 to play games! I never get an ip address. Everything looks exactly as it should on the wireless setup, iwconfig shows the SSID i'm connected to and the correct chanel etc. However after a short period of time when its tried to get the IP and i restart networking, it drops all the iwconfig details. I know i'm close to getting it working, could it possibly be the wpa supplicant?
My router is a netgear DGGT. I'm going to have another stab at it tonight. Sorry to ask, it might seem like a bit of a stupid question. Also are you required to put 0x by the encryption key. Last, for some of the txts you have "" for the network name, yet in come areas you do not. Are the "" signs needed. I just followed the guide almost to the dot and it did not work, im reinstalling the os today and will try again when I come back from work. It's wierd because in some instances my router detects the os yet in others it does not.
I was able to connect in 6. I did get it working, i line up altering the same exact files in a different area after completely reinstalling. I also figured out what was incorrect i guess about the key, i wasnt including the "" marks, althought i did not believe those needed to be entered.
But Hurra, i got it working, in great great part thanks to this amazing guide. I think key is to just not give up, although i did spend close to 12 hours with the uninstalls before i finally got it working. Hi Tom Yes, as you eventually found out, in some places, like those configuration files, the quotation marks are required. I know it is a pain and very frustrating that it doesn't work as expected straight away.
It is really something that the YDL authors should put out a fix for. Hi Calvin Yes, you are also encountering an issue which I think is due to one of the many! The " my username " part you quoted, is actually the name of the current folder that you are in. One part of the process of opening a shell prompt is for bash to put the user into his home directory by default per the contents of the HOME environment variable Using su to switch user to root does NOT cause your bash shell to absorb all the setting of the root user - instead it keeps the settings of the user you were before issuing "su".
While using "su -" and that is the short hand way, the full way would be "su - root" causes the bash shell to a switch to user root, and b execute certain profile and bash setting files for the root user - the end result is that you get placed in root's home folder and also get things like your PATH environment variable updated properly. I'm not on the PS3 right now, so I can't record exact examples. But try the following: 1.
Open a terminal window. Check out the HOME variable as above. Type "exit" to exit out of the switch user shell you are now in i. Now switch to root, including getting root's full environment variables, with: su - 8. Another thing you could try which might help clarify the difference between executable files and configuration text files is to ask the shell to tell you something about the types of files by using the "file" program, e.
So yes, Linux can be quite picky and unforgiving if you don't type in things exactly as it is expecting you to, but once you get the hang of it, you will start to appreciate how the strict rules like this help to make it such a versatile environment to work in. By the way, to get the shell to print out all your environment variables, in either Linux or at a Windows cmd.
With it, the command runs and stays running in the background and you get returned back to the shell prompt to execute other commands.
Without it, the command will run and you will not be returned to the shell prompt until it finishes or until it is "killed".. To push a job to the background, which you are currently running at a shell prompt i. To see what jobs you are currently running type "jobs". To bring the most recently launched job from the background to the foreground, type "fg". I think that may be more to do with how little RAM there is on the box. But hey.. Well i've tried everything you can imagine now, i just cannot get the damn thing to give me an ip address at all, when i first start up and run iwconfig it looks fine seems to be associated ok but just never gets an ip, as soon as i restart networking or wpa-supplicant it drops all wireless settings and won't associate to the router again.
Final thing i will try is a re-install and run through this again before touching anything else. Just cannt connect my YDL to my network at all. Did everything but still failed. Is there any thing you can help me fix this? I don't know why. I reinstalled 3 times already and spent more than 20hours on fixing it.
This blog is very interesting Thanks for share awesome blog.
0コメント