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've just recently installed Mandrakelinux 10.0 on a dual booted, dual processor machine. To get the installation to even run, I had to add in noapic nolapic behind the linux install option. It worked just fine, but now when I run Linux I get the APIC error: 04(04) message scrolling over and over.
Thanks for responding, but I'm not sure what you mean.. I'm really new to all this. SMP means a multi-processor mobo, right? Yes, I have a multi-processor board, but only one processor installed. The second processor died on my some time ago. Does this make a difference?
And do I have to reinstall everything and then input just the nolapic instead of both, or is there a way for me to input a boot up command before I run Linux? The only time I input the noapic nolapic stuff was before I installed the OS.
Originally posted by Vlad-A Try to boot with APIC enabled nut Local APIC disabled. So just noloapic (local APIC disabled)
The only way I can input anything at boot up seems to be if I choose Floppy as the startup option instead of Linux, or Windows, or whatever else is listed on the boot screen. Of course, since I don't have a floppy disk in my computer it fails, but I can type in linux nolapic there at least. Unfortunately, it doesn't do anything.. neither does typing linux noapic nolapic or linux noapic.
Is there a different way to input code on a boot that I don't know about?
I believe I'm using Lilo as a Bootloader since it was the default option on the install. And I'm using the Discovery Edition of Mandrakelinux 10.0.
As for the CPU settings in my BIOS, no, I don't believe I'm overclocking since the CPU speed is set to 1600 and I have dual 1.8 Ghz Athlon MPs. My mobo does still reads as a dual processor board even though I have only one processor in it right now. Would that be a problem?
My system has always run Windows just fine, it's just when I try installing or running Linux that I get the APIC errors.. I've never had Linux work appropriately on my machine.
For instance, when I was installing Linux for the first time, all of the options I tried running (linux, vgalo, expert, text) either black-screened my monitor, or threw an APIC error: 04(04). To get around that, I input the noapic nolapic specifications after linux, and the install worked. Now, however, I get APIC errors whenever I try booting into Linux.. I never even get to the login screen.
I also haven't changed anything in the BIOS, and it's been about a year my computer's had only one processor.
I'm still confused about inputing boot commands... where exactly would I input this apic=off command? Was I correct trying to input stuff under the Floppy boot option, or is there another way to do it?
1-1 If you have configured your system with the LILO Graphical Boot menu then do following:
As soon as the LILO menu screen is displayed press the TAB Key to stop the count-down
Press then the Escape [ESC] Key to enter the text mode
A list of available kernel images will be presented.
Enter the kernel image you would like to boot (if there is a non SMP Image, then use this) and
after the image name enter acpi=off nolapic (it's not a typo. Boot with ACPI=off. ACPI=Advanced Config and Power Interface.)
1-2 If you have LILO text menu, the press the tab key after menu is displayed to stop count-down.
Select with the arrow keys the kernel you would like to boot and enter the option
Then presss the ENTER Key to boot. You shall use acpi=off nolapic as boot options.
I hope for you that you have an US keyboard, since LILO expects a keyboard with
an US Key mapping. Typing with a non US key mapped keyboard (I have german mapping)
can be a really funny stuff :-))) Guessing what key could be what (e.g. a ")"-Key on a DE Keyboard
is a "(" on a US Keyboard)
2-1 As alraedy said an APIC Error 04 is a hardware error. Operating systems shall handle this.
It's maybe that the kernel version Mandrake 10 provides can't handle this with your motherboard.
However: The fact that an operating system can handle an APIC Error does *not* mean
that there isn't a HW problem.
2-2 If nothing helps: Update your BIOS. There are some SMP Motherboards where Linux installation
is almost impossible. In many cases an BIOS update helped.
2-3 Consider also if nothing helps to chang ethe MP setting in your BIOS from 1.1 to 1.4 or vice versa.
Also disabling IDE DMA Mode can help. Turning off "Legacy USB support" in BIOS can also be helpfull.
After you have succeed to boot into linux I suggest you choose/recompile a more recent kernel.
I *think* Mandrake provides with the Installation Media the 2.6.5 kernel.
I've got some good news! Your 1-1 and 1-2 suggestions worked, but only when I used the boot option linux-i686-up-4GB. I typed the acpi=off nolapic code after the boot option, like you said, and it loaded fine...
Now, am I going to have to boot up this way all the time? I don't think it's a BIOS or HW problem. You mentioned changing the kernel in linux.. How would I do that?
I checked out the Linux interface last night and was impressed! I'm starting to get the hang of this. Thanks for the help so far!
Ok, I found etc/lilo.conf and attempted to modify its contents like you instructed, but everytime I try saving the changes, I get a permissions error, specifically saying:
The document could not be saved, as it was not possilbe to write to file:/etc/lilo.conf
Check that you have write access to this file or that enough disc space is available.
I'm logged in under the admin account I created and I can save the changed file in a different location without any problems. Also, although the permissions options are grayed out, the file properties say: Owner: Can View & Modify Content
Why won't it let me update the file? Is the fact that I'm editting this in KWrite have anything to do with it?
I do not know what you mean by "Administrator Account".
/etc/lilo.conf can only be modified by the root user.
The error messages you see, indicates that you are
editing lilo.conf as a "normal" user, so not as root.
I do not know if you have modified the Log-In Manager so you can log-in into KDE as root,
but by default Mandrake and MdkKDE do not give you that option.
You need to start kwrite as root.
I think that it might be a good idea to replace the MdkKDE Login screen (very restrictive) with the
default KDE log-in screen. Sometimes it's really necessary to log-in as root into KDE.
- 1.0 Log in as normal user
- 1.1 Click the KDE Application button (The button with a yellow star in a blue rectangle in the lower
left corner of the display).
- 1.2 A fly-out menu will be displayed. Select now: System->Configuration->Configure your computer
-1.3 You will be prompted for the root password. Enter the root password, (you have been asked
to enter a root password during the Mandrake installation. I hope you still remember it.)
- 1.4 Now Drakeconfig will be displayed.
- 1.5 Click on the "System Icon" => System Menu is displayed
- 1.6 Click on the "Display Manager" Icon
-1.7 It's very likely that the MdkKDM (Mandrake Display Manger) is selected
Select "KDE" and press the OK Button.
- 1.8 A dialog will be displayed telling you that changes are done and asking you
if you would like to retart the display manager (dm) service
Klick teh YES Button.
- 1.9 KDE will be terminated and restarted and you now shall see the standard KDE login-screen
If KDE is not started for whatever reasons and you are still in the text screen, then simply type
at the command line and press enter. (kdm=KDE Display Manager)
- 1.10 enter under "username" root and ander password your root password in the "standard" KDE log-in dialog
You shall now be loged in as root into KDE.
I *suggest* that you perform followning modification, since the KDE desktop screen has some restrictions in Mandrake for the
root user (e.g. Mandrake disables per default the root user to add Icons to it's KDE-Desktop)
When loged in as root in the KDE:
2.1 Click the KDE Application button (The button with a yellow star in a blue rectangle in the lower
left corner of the display).
2.2 Select System->Configuration->Configure your Desktop
2.3 Select the "LookNFeel" Item from the list in the left windows half.
The "LookNFeel" suboptions list will be expanded.
2.4 Select "Behaviour" from the suboption list. => A dialog in the right window half willl be displayed.
2.5 Check the "Show Icons on Desktop" Option in the dialog in the right window half *and*
take a look on the "Mouse Button Action" Section.
Select there for "Right Button" from the drop-down list for this Button: "Desktop Menu"
2.6 Click on the "Apply" Button and close the KDM Desktop Manager
Now you can start kwrite as root
E.G: Start a console from the KDE Application list
Click the KDE Application Button and select from the fly-out menu:
type into the console window:
CAUTION: The root can access everything, which means he can also destroy everything (in 99.99% of the cases
not by intention but by accident) Therefore log in as root only when absolutely necessary.
Just so you know, I did successfully log into root and altered my boot proceedure like you showed. Linux boots up by default in the non-SMP mode and has included the acpi=off nolapic code you taught me. I can now officially use Linux on my machine, something I wouldn't have done without having fixed this APIC issue I can assure you.
I have just one last question regarding dual processors.. If I ever got both processors going again, would I have to change the way I boot into Linux then, or would it work irregardless?
With a second processor you shall use the smp kernel.
What I would do in this case is:
Boot the system with a second processor inserted. Select from the LILO boot menu the SMP kernel
If there are problems, then use as boot options for the second kernel acpi=off and if this also fails
then acpi=off nolapic.
Once boot is successfull, change your lilo.conf making the smp kernel the default option in the boot menu.
If needed add also the boot options (like acpi=off, etc.) for the smp kernel in lilo.conf.
Now you know how to do this.
Do not forget to run /sbin/lilo after changing lilo.conf.
Also check from time to time with
the Errors (ERR) counter (at the end of the displayed list)