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.
TSCRYPTO - What a curious username? Not serving or ex forces by any chance ??? (ex-RN myself).
Anyway, as I understand it, the origins of "swap" were from when people only had a small amount of RAM, and the swap was used when the ram was upto it's limit. Then the system would use the swap as additional room and swap stuff between the ram and swap (that's basically as i understand it). It wasn't until I started installing other distro's alongside my mandrake (something to do with being curious about what lots of others "bang on about", and getting my hands on a 120gig western digital HDD).
Although I have 768 of physical ram, I decided to include a 1 gig swap partition (1 gig seemed like a nice round number, though in the past the recommendation was to use double the physical ram) and even though I had an uphill struggle getting proper debian working (some help from one of the blokes at my LUG had a lot to do with it), I never managed to get it looking as good as my mandrake install. Hence when I tried running knoppix from a cd (it's one of the "live" distro's), I also found the knoppix forums and read up about it and installed it over the top of the debian that I had, and I found it to be nearly as easy as mandrake to install, except it basically becomes a debian testing/unstable install (and no, that isn't quite like it sounds either).
As far as the sound thing is concerned, one of the first things to check is the volume control. Mostly, they are muted by default, at the install point. You should start by opening one of the mixers and making sure that it's turned up and not muted.
I notice you mentioned nautilus, so that means gnome (as opposed to the kde default under mandrake), so you will have to open whatever mixer you have (possibly aumix, or tkmix, or something like that) and change/check the settings.
I use kde, so from there I would open kde control centre and check the sound settings, if you have both kde and gnome installed, you would be able to tell if the sound is working by logging out and logging back in using kde, there's a start up jingle thingy and I don't know if gnome does the same. But you could just try playing the wav file again.
When you get to playing audio cd's, you will have to check what the system actually calls the cd player. By that, I mean that kscd (in kde), and grip (in kde and gnome, a disc ripper that also is a fully functional cd player) seem to default to /dev/cdrom. I imagine that with the correct settings, that might work, but I have always had to change that to point at the device that I want to play the disc with (I have a dvd player and a cdrw).
I should point out, I'm given to understand that windows takes the sound output from the ide cables, whereas with linux, you have to have the drive connected to the sound card/onboard sound device. for me that means that by default my system can only play cd's with the cdrw, as the dvd doesn't have a cable connection to sound card. to get the disc playing, I have to tell kscd or grip to point to /dev/scd0 - and no I don't have a scsi player, thats just because the system used scsi emulation for the cd burner and burning purposes (though I haven't bothered to learn how to do that yet!).
To check your sound device (card or whatever), go into the mandrake control centre and check the hardware section, it should show up on the list - you could then highlight it and run the config tool under the box on the right hand side (there's two tools, but if you click the wrong one, you get a dialogue box that needs some input that I don't know about, just cancel it and select the other option) - you could still experience minor snags, if like me there is more than one driver for your sound device e.g. I have a soundblaster live! 5.1 digital and mandrake seems to think that it could use one of two drivers, the Audigy() and emu10k1. If I re-install, it always seems to default to the wrong one i.e. the Audigy(), so I have to select the emu10k1 driver and I get sound straight away.
It's easy to just think "thick bastards" if one of use doesn't have an answer, but when you think about the hundreds of different sound cards/devices available in the UK alone, without internation variations, then it's quite remarkable that it only tends to be the mega mega new ones that don't have a driver, and that situation doesnt' last for long.
Post back when you have had time to try some of the variations/idea's that have been suggested.
p.s. f*****g typical, trying to think of a phrase, post a reply and then it pops into my head - swap space = virtual ram.
A lot of what you have suggested, I had already tried - unmuting the sound, running the config tool within the Mandrake contol centre, but to no avail. I then cam across this while searching here. I could not get the permissions correct as suggested in the big post, however, the editing of rc.modules file did the trick.
I have sound, but unfortunately it is crackly and tinny. Looks as if there might be a bit more tweaking needed.
Should XMMS be able to see audio cd's in the CDRW drive? At the moment for me, it cant... ie, I can only play .wavs from the dektop
originally quoted by TSCRYPTO
And yes, ex army here.
Thought so. Picked up on the username reference yesterday, only thought to ask today.
I do use xmms, though not for playing cd audio - When I was first learning how to do stuff like listening to cd's and the like, it took me forever to learn that with kscd and grip, all I had to do was to change the default device from /dev/cdrom to /dev/scd0 (the scd0 bit is to do with the scsi emulation used by cdrw's for burning cd's) I then just do hit and miss selection of the various freedb options until I get the track listing as well.
With xmms, I have to tell it to look at /dev/scsi/host0/bus0/target2/lun0 to make it play an audio cd, and for reasons that are beyond me, I couldn't make it save this as the default device - and as you can see, the path is far too long to try and remember.
The xmms usage I get is to listen to virgin radio (the fm signal won't make it through the hills north of Brighton), so i just listen to the "ogg broadband" stream. I just hit the download bit, it's only a small file, then open xmms, click on the "load playlist" radio button, the load playlist box opens, and then I hit the load playlist button there, the file manager type box opens asking me where the playlist is, the box has opened at my /home and I just select the downloaded file (which for virgin is called live.pls), this puts a couple of lines 1, 2, 3, in the xmms playlist, I just click the first one, and the xmms player goes through the "buffering" thing and bingo virginradio streaming.
Oh, and just as a little extra, if you have just started with mandrake (and linux in general), do a search for posts by me with plf in the text, follow the instructions to update your "urpmi" sources, and then the bit I've put about installing via "rpmdrake+", one of the ones I have answered tonight include the bit about uninstalling xmms (the mandrake packaged version) and re-installing the "texstar" packaged version. Which I understand is the very latest one, which apparently can pick up digital input's and a few other bits and bobs.
Don't ask me how, cos I haven't got that sussed yet, but I always prefer to keep up the latest versions, especially sound and graphics (sound for better drivers, or facilities, and graphics for eye-candy, as they like to say the other side of the pond!).
1. Are there any known probs with installing Mandrake 9.1 from iso's installed on a HDD? I ask because it seems that although 9.1 is working fine on my PC, the install was not complete. For instance I thought that X-CD-Roast would install but it didnt. I have had to find the rpm on cd2 iso and copy it over and install.
Is there any way within M 9.1 that I can check whhat HASNT been installed?
2. RAM usage. Last night I searched for some rpm files within the cd iso's. The search took a minute or so and I watched the amount of RAM being consumed rise quickly. At the end of the search the gnome process monitor showed that RAM usage was at about 600MB. To me this seems high. But the strange thing was was that once the search ended and Konqueror was closed, the RAM used remained at some 600MB. ie it didnt return to its pre-search level.
Is this right?
I looked in the process moitor and the processes running were NOT using a total of 600MB of RAM.
Is there a bug within the process monitor, or am I missing the point entirely...
Once the ISO's are downloaded, and then burned to disc, you normally follow the "usual" install route.
There is only the limited amount of packages that are installed by default. During the install routine, you would probably have seen the packages selection screen, with 2 columns (basically) of things that you can select to install.
When 9.1 had been out about a week or so, I read a review that "blew the mandrake trumpet", but at the same time said that from the "n00b" point of view, it recommended that unless you know exactly what packages you want, check all the stuff down the left column and ONLY kde and/or gnome in the right, as installing "the whole shooting match" could lead to confusion.
Which, I think is a fair comment. Because although I have been meddling with linux for nearly 2 years (8.2 was my first mandrake), I know what servers are, but haven't got the faintest what to do with them (not that I've got millions of pages to "serve" anyway ).
By following the review's suggestion, you would still end up with an install that has a whole bunch of app's/facilities, that you probably won't use, but you get the majority of stuff that a "user" would need.
The result being that if you then need something else, it SHOULD, be on one of the other disc's (I presume that you have got all 3 - though as far as I recall the 3rd disc is source code and a few app's that they couldn't fit onto discs 1/2).
Also, if you have modified your "urpmi sources" as per one of my previous posts, then you also get the option to download any variations that may be available from the plf or texstar (which are often more up to date than the mandrake packages. Also you'd have to remember to remove older versions of "whatever" e.g. last week, I helped out with a thread about conflicts in xmms, the person hadn't worked out that the conflict was between the older mandrake package and the newer texstar version, and I just checked it out by uninstalling mandrakes package and installing texstars one - which worked fine).
I'm also a little confused about what you say about " the gnome process monitor" and in the same paragraph mention "konqueror". I'm not sure what you mean by the "gnome process monitor". When I have bothered to have some sort of system monitor running, I have always installed "gkrellm" which can monitor all sorts of system "things" (not that I know what half of them are ) but it can be handy for watching the comings and goings of the system and/or network.
So, if the process monitor is a gnome thing, could there be a "compatibility snag" ? I know that most gnome things will work under kde, not so sure if it's the same in reverse. Does the system need or have you got "gtk" installed (I would presume so if you installed both kde and gnome).
Also, if you are looking into the iso's on the hard drive, could that cause the ram to be used at a high level ?? Not sure - though it would be worth searching LQ, as I'm pretty sure I've seen thread's about that sort of thing (and no it doesn't sound right - but it's not a problem that I've experienced - well I don't think so, but then again, I don't bother looking into stuff like that - or anything else for that matter - as long my system seems to be working ok, I leave it well alone).
You could also check out the mandrake site, as there are some forums there. as far as I know, you don't have to be a mandrakeclub member (I am, but I also use boxed set DVD power pack - cos I think that mandrake is good enough to be worth some of my "hard earned", and I'm pleased that I do, as there are a few commercial bits and bobs that you don't get on the download version - and it makes life so much easier).
Sorry, that's probably not much help, but it may give you a few things to look into.
Don't worry about RAM usage. Linux is much better at handling RAM allocation than windows. If there is any "free" RAM, linux tends to use it for buffers/cache to speed up disk access. You would have noticed this if for some reason you had re-searched one of those ISOs - it would have been faster, because most, if not all of the data would already be in RAM - that's why your RAM usage shot up. If a program requests more RAM, these buffers are flushed, and the program can (usually) get what it wants. If you are REALLY running out of RAM, then it will start using your swap space, and you'll notice a performance drop.
Just a quick note to say thanks for all the help and advice postd to this thread over the last week. Unfortunately I havent really had a great deal of time to spend here on Linuxquestions and furthermore, my Mandrake machine is a stand alone jobbie - ie its not connected to the net at the moment.
I plan to go back over whats been posted here and continue my learning - and fingers crossed, the Mandrake box will be connected to the net soon, once I get a shared connection sorted with the other (XP) machine in the house.