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.
What's up? Checked everything and found it working again as it should? I hope so.
What happened, in short and simple words, is that your upgrade didn't change the boot manager configuration correctly. As a result of this you were booting with the kernel of Jaunty instead of the one that comes with Karmic.
Apparently a lot of things changed in Karmic, resulting in the fact that various things didn't work anymore after your upgrade. This just because packages and modules and such were upgraded correctly but since you booted into the 'old' kernel were not compatible or recognized by that one.
What you have done yesterday is install the correct version of Grub, the boot manager, then do an upgrade from legacy to change from using menu.lst to grub.cfg. Then you checked what devices could be found by Grub and install the boot manager correctly.
So after doing all that, when you rebooted the correct kernel was loaded, and with that you got all modules, packages, drivers and such recognized and working again.
thanks for answering.
there are some words i'm not familiar with :
jaunty, karmic, legacy.
so basically, was it my fault, or was it because of the new ubuntu version, or because of another reason?
also, there's something that i don't understand. The window where you can choose which os you want to use seems to be grub, if i understood correctly, which is part of the linux world. it sounds to me like linux is loaded even before i can choose to boot on linux or not. quite contradictory.
shouldn't it be part of the mother board instead?
And what's the link between grub and the things called bios and master boot record?
Jaunty Jackalope is the 'code name' for version 9.04 of Ubuntu, Karmic Koala the one for version 9.10. When referring to legacy in this issue it means that we're upgrading from a 'older', but still in use, system.
It was not your fault as far as I know, it was just the upgrade gone sideways. There have been a lot of errors and issues with this version of Ubuntu. Hence the postings on several forums in regards with problems after an upgrade to Ubuntu 9.10.
The Grub you install is a boot manager. It's just a process that starts before you start into any operating system that you might have on your harddisk(s) in order to give you the choice of which one you want to boot. If you do nothing and wait the first in the list is booted.
The motherboard does nothing in regards to choosing and/or booting an operating system. In the bios you can set which device should be used to boot from (boot order), but that's all you do in that regard. If you set it to harddisk, then the bios connects the harddisk prior to for example the CD drive to look for a bootable system. If a bootable system is encountered the control is passed on. If there's no bootable system on the harddisk then it moves on to the next in line.
You cannot instruct the motherboard nor the bios which operating system to boot, as far as I know.
The master boot record (MBR) is a dedicated space on any harddisk where information in regards to bootable systems is saved. If the bios looks for a bootable device that MBR is read in order to check if there is a bootable operating system located on the harddisk.
The choice you get offered by the grub boot manager happens when you already passed the bios, you're already 'on' the harddrive running the grub process.
Probably someone else can explain it in a lot more accurate and technological terms, but I tried to explain to the best of my knowledge.