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 just found some reference to a problem/bug that might be the cause for all you problems. You'll need to reboot and look at the bootup screen. At some point in the reboot you'll have a screen that shows you the kernels you can boot. Write them down and post that info here please.
I solved the problem.
After I had edited the grub menu.lst manually in the past, the new installed kernel was not loaded to the boot options (See Bug https://bugs.launchpad.net/ubuntu/+s...ls/+bug/392039 ).
I just removed the backuped menu.lst and did a grub-update to generate a new one.
After reboot karmic had the latest kernel. Also my grafic card problems solved this....
This will not make much sense to you probably but will be very useful to other users that are following this thread.
At a point in the boot up you'll see a screen with boot options, looks like a list with several options. The first option will be selected and is the one that's booted when you do nothing or press enter. Normally the screen stays like that for some seconds in order to give you the possibility to change booting.
Write down the options you see on that boot up screen and post them here.
That might well be the cause of all your troubles. You are booting in the wrong kernel. As mentioned in my previous post, the upgrade from 9.04 to 9.10 doesn't change the boot options like it should but keeps listing the 9.04 kernel. So you'll need to change the menu.lst and/or boot options.
I'm not sure how this should be done since I'm not that familiar with Ubuntu. But I believe the easiest way is to type in a terminal window:
I'm sure someone will correct me if I'm wrong. But you could try that.
I just went trough the entire thread looking for a post where someone (or me for that matter) told you to run
but haven't found one except for the one like tree posts ago. You might be confusing with the
sudo apt-get update
This one is different. This command (sudo grub-update) will look for available images on your harddisk, for the menu.lst file and if I'm not mistaking will correct the menu.lst so that when after the update, when you reboot the system, the correct kernel will be available and loaded.
you misunderstood me, probably because i don't speak english that well.
i just meant to say that i had already given the idea (post 6) that this might be a problem related to the fact that, when the computer starts, it says version 9.04 instead of 9.10. it was a joke.
on the other hand, i REALLY did the 2 commands that you said, a few minutes ago, and the result was that they both closed the command line window and nothing else happened.
hence my question : what should i do now? restart the computer?