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 responded to a suggestion that I install security updates - did so and ended up with a copy of fedora that goes into a loop.
I suspect the prob is the driver to my video adapter.
To run, I need to interrupt grub with an escape.
It then shows me two choices
the bad one
and the old good one
It defaults to the bad one, I change it to the good one and tell it ot proceed.
this is inconvenient
I see that in /boot/grub/grub.conf the 2 systems are described
I beleive that if I merely edit that file, taking out the refernece to the bad one, I will be ok
That will leave the bad one on the disk but at least I wont have to go thru the ritual of interrupting grub.
Is there any reason I should not do this?
If I want to delete the bad one - after I've taken care of the grub.conf file, what do I do?
Ostrich tactics are no good. Instead boot the "bad one" into runlevel 1 and look at 'dmesg', /var/log/messages and /var/log/Xorg.0.log to see if there's clues. Also please try to be factual and complete when presenting information: "I suspect the prob is the driver to my video adapter" doesn't ring a bell (and my ESP isn't that good) but saying you run proprietary drivers for card X of Brand Y via DKMS might ring a bell for some.
I have not added an NVIDIA driver - something supplied with the system is talking to my NVIDIA card. The driver in the good version is compatible with it. The driver in the bad version is not. I did not supply either of these drivers.
Maybe from the version numbers I supplied you can tell what driver I got the first time and what driver I got the second time. I suspect you will find they are not the same.
For what it is worth - the good version apparently talks to the card in a simple protocol that does not try to take advantage of its features. I get low resolution, big character, al la video cards of old. Windows talks to the same card in a more spphisticated p[rotocal giving me very high resolution.
I dont have any idea how to find a link to the bug report that I posted a few months ago. Someome here directed me to a bug reporting site. Maybe you can track my prior messages and see where someone sent me. That is where I went.
I would try to do that but I dont understand the mechanics of this forum well enough to do so.
In any case, I've repeated the information in a post I sent a miute or so ago.
If I understand your problem, you did an update and got a kernel update and booting the new kernel "doesn't work". If the old kernel works, use it. Was there something imperative for you to get a new kernel? You can simply put hash marks (#) to the left of the entry for the new kernel so it is not on the menu (grub.conf). Maybe I'm not understanding your problem?
1. for the moment, after you have got into the system ok, you can set the 'default' value in /boot/grub/grub.conf to point to the kernel you want booted. Entries are numbered from zero, so the first 'title' entry in grub.conf is 'default=0', next 'title' entry would be 'default=1' and so on.
2. you could use yum remove <kernel> to completely remove the entry in a controlled manner.
Yancek - I started by saying that I intended to do what you said - except that I intended to delete the lines from the grub control file - same difference. I merely asked whether there would be any unintended consequence in doing this. Apparently not.
Unspawn suggested that this was putting my head in the sand and that I should help determine the cause. To me the cause is clear - somewhere between the first and second version the authors made a change in the terminal handler which results in this bug.
Chris.. I tried your command and it says that the good copy of the kernnel came from rawhide and the bad came from update.
I have no need for a better copy of the kernel - I work at gedit and at the command line developing software. The kernel announces that it crashes regularly, but the handlers restore it and it makes no neverminds to me.