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 pretty sure this belongs here, if it doesn't please let me know so I can delete it and/or move it.
I am a newbie in all means and manners but I have something I promised I would do and am having a lot of problems doing it.
I am supposed to setup a dual boot system running both windows and linux on a computer which was bought part by part and assembled just fine.
I can get just about any version of windows to install just fine, that isn't the problem.
Any time I try to get any version of linux to install, the same thing happens.
It will load the install menu for Fedora 5 and 7 plus the latest version of Ubuntu (I can't remember what it is called though)
When I choose an install option (any of them, live, graphic, txt, etc.) there is some loading dialog and the computer just stops responding.
There are no error messages and there is almost literally no response.
When I try to push the power button, nothing happens. Ctrl-alt-delete doesn't work either.
Even if I push numlock or capslock or anything, the keyboard's l.e.d. remains in the state it was just before the computer froze.
In fact, the only thing that does respond is the reset button (the power button not so much)
With Ubuntu the computer will turn to a blank screen and all of they keyboard l.e.d.s will turn off and neither of the Fedora startup dialog freezes at the same spot.
It is a AMD athlon 64x2 4400+ processor
seagate 120gb pata 3
LIT ON IT corp cdrw/dvd combo drive
240 pin ddr2 dimm corsair valueselect 1gb ram
Amd690gm-m2 ecs elitegroup motherboard
Thank you anyone for taking the time to just read this information because I have not found any solutions so far because any boot options I try also result in the same error
you should try to disable acpi at boot (from cd). at the CD boot prompt read the instructions.
Also, as Windows installs correctly, you could try a distro with proprietary drivers just to see if there is a problem with drivers (for instance mandriva one)
What I mean is that I cannot get the Linux install menu to run.
Neither Ubuntu or Fedora can get past the menu that asks for what kind of install I want to run (Ie: for graphical instillation press enter for...)
I'm really confused because I got windows 2k and xp working on it (just the plain old versions) so I know that the system otherwise works fine.
An interesting thing that just happened is that when I tried to get fedora core 6 to install it doesn't freeze the same way as the other installs.
The last thing to show up is "running /sbin/loader" but it does respond to num lock (the light on the keyboard lights up) which none of the others did.
Oh yeah, I forgot to mention that originally there was no OS or anything on the drive and I still had the same problem which leads me to believe that this isn't a dual boot issue.
Last edited by Attamagaushi; 08-28-2007 at 02:54 PM.
It's not a "dual boot issue", it's a hardware issue. In order to do a normal Linux installation, you've got to run Linux: that's what the install CDs are for. But to run Linux, the OS has got to be setup for your specific hardware rig which requires detection and probing of components and loading correct drivers for your components. One of the problems with Linux is that while the OS is constantly being improved, since no one in the design/manufacturing end of hardware is actually targetting a Linux customer base, the Linux developers don't have enough information to have software that's quite as cutting-edge as the available hardware. Your system (or parts of it) might just be "too new".
I suggest you try removing various components and get the system as simple as possible with less cutting-edge components and see what combination can get you to a command prompt. From there you will be able to dig deeper, like looking at boot logs and looking in the /proc directory and hopefully you will be able to identify what component or combination of components gives the problem. Note that in every install CD I've used, you can get a command prompt (after the system has boot through, of course) by pressing either "alt-2" or "ctrl-alt-2". Numbers other than 2 may be needed.
It's not a "dual boot issue", it's a hardware issue.
I reiterate: try PCLinuxOS. I had all kinds of hardware issues with Ubuntu and Mepis. PCLinuxOS has the best hardware detection and live setup that I've tried (and I've tried a lot of distros). When the menu comes up, select to load the Live distribution, not install. Install once it's done loading.
Be sure you're familiar with drive numbering and other nuances of Linux before you try to install any distro.
You also might check the motherboard (and other components) manufacturer's websites for bios updates and to see if they have any custom linux drivers.
I personally prefer running linux via vmware (vmware server is free and fairly easy to use), which also has the advantage of using the windows drivers for the hardware and thus avoids tons of compatibility issues if you just want to learn linux this might be easier than trying to do an install on a system with hardware issues.
VMs are tons easier to manage than dual boots, which I have come to dislike. Not that using vms doesn't have its own pitfalls
The AMD 690 chipset is quite new and there seem to be hiccups in graphics and sata chips from what I've been reading so far. I was thinking about buying a relatively similar board but refrained from that because I read so many "Why doesn't it boot" threads about it.
A recent kernel should work tho. You might for example try Slackware 12.0 which has quite a vanilla 126.96.36.199 kernel and see if it boots through. You might also want check for BIOS updates as miedward already proposed.
Last edited by General Failure; 08-30-2007 at 03:19 AM.