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.
Ok guys, this is driving me nuts... I have used linux for about 4 years now, and i have never ran into something that has confused me as much as this. I recetly picked up a machine for free. PII 400mmx, 384Mb RAM, 30Gig, blah, blah... anyways, no matter what distro i install, i can't boot it unless i use a boot disk or boot from the CD. I've tried logging in and running lilo and it still won't put the loader in the MBR. (MBR bootloader install won't work, this is the problem) Tried with Grub as well, and the best i got was a grub boot error. I'm thinking this has to be a bios thing because i've had this same hard drive in another machine and it ran and booted great. I made sure in the BIOS that my drive is LBA and that the virus protection crap is off, and i still can't figure this out. If anyone has any ideas, i'm all ears. Oh and just for some more background this has failed with the following distro's:
"PII 400mmx, 384Mb RAM, 30Gig, blah, blah... anyways, no matter what distro i install, i can't boot it unless i use a boot disk or boot from the CD. I've tried logging in and running lilo and it still won't put the loader in the MBR. (MBR bootloader install won't work, this is the problem) "
As a wild guess the distributions you tried may be using a CPU instruction that does not exist on a PII. Try using a distribution that was compiled for i386 to do the MBR installation. If that solves the problem you might consider using an i386 distribution for the entire installation.
If the i386 thing was a problem i would think that there would be more problems than just the bootloader. I mean, we're talking a completely functional install that won't boot because nothing ever gets put in the mbr. Boot disks and Cd bootables are the only things that get me into the system. I have win2k on a seperate hard drive in there, and it boots fine. Tried it both with and without a windows OS and got the same result. And no it's not an older compaq, the computer is actually an older Tangent. Here's the specs motherboard wise...
System Model: MICRO-STAR INTERNATIONAL CO., LTD MS-6119 1.X
Board: MICRO-STAR INTERNATIONAL CO., LTD MS-6119 (i440BX) 1.X
Bus Clock: 100 megahertz
BIOS: Award Software International, Inc. 4.51 PG 06/16/98
400 megahertz Intel Pentium II
32 kilobyte primary memory cache
512 kilobyte secondary memory cache
Originally posted by vectordrake There you go! For the record (basically the google searches...) P-II would run fine on an i686 kernel, so the previous argument is a bit weak.
i've had slack 10 on a celeron 333mhz machine before, so i know what you mean. I figured the BIOS was to blame since i pretty much ruled out HD problems. Just took me a bit of research to figure out what my system board was (thanks to Belarc advisor and a win2k pro drive) and find the BIOS flash update. I'm actually posting from it now, and i'm glad to have my slack back, can't wait till 10.1 when i get to play even more. Thanks for the input guys.
Yep, a lot of times, things like hard disk controllers will make an install go haywire. I have a VIA KTA133 chipset and it won't work properly when loading the generic ATA controller module - lotsa I/O errors. But, with the proper module loaded for my controller, the machine works great We still have to do it for ourselfs much of the time with Linux. That will change as time goes on.