LinuxQuestions.org
Latest LQ Deal: Linux Power User Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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!

Notices


Reply
  Search this Thread
Old 07-08-2010, 04:56 PM   #1
rmknox
Member
 
Registered: May 2010
Posts: 354

Rep: Reputation: 34
Defective version of fedora boots


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
2.6.32.12-115.fc12.i686
and the old good one
2.6.31.5.- 127.fc12.i686
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?

Thanks in advance
Dick
 
Old 07-08-2010, 06:06 PM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,331
Blog Entries: 55

Rep: Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529
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.
 
Old 07-08-2010, 06:37 PM   #3
rmknox
Member
 
Registered: May 2010
Posts: 354

Original Poster
Rep: Reputation: 34
Unspawn

I previously submitted a very complete description of the problem and my configuration.

If it is approariate to do so here agin, I will pull the material together again and do so.

I do not have proprietary anything.
 
Old 07-08-2010, 06:53 PM   #4
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,331
Blog Entries: 55

Rep: Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529Reputation: 3529
Quote:
Originally Posted by rmknox View Post
I previously submitted a very complete description of the problem and my configuration.
Just add the link here.


Quote:
Originally Posted by rmknox View Post
I do not have proprietary anything.
Sure? No Nvidia drivers?
 
Old 07-08-2010, 06:54 PM   #5
rmknox
Member
 
Registered: May 2010
Posts: 354

Original Poster
Rep: Reputation: 34
Symptom
When the bad copy boots, I get a pattern on the screen similar to a TV test pattern, and the system is in a loop - with one of my l e d s continuously flashing

Configuration
1.25 ghz AMD athlon
NVIDIA RIVA TNT display adapter
ECS K7S5a board / chipset
AMD BIOS 07.00T
512 mb main mem
128 kb primary cache
256 2ndary cache
66 mhz bus clock

History
When this happened I cam here and described the problem and asked how to report the problem. Somone here directed me to another location that takes bug reports.

ADD ONS
I have added nothing to the system - it is exactly as delivered.

Last edited by rmknox; 07-08-2010 at 06:56 PM.
 
Old 07-08-2010, 07:05 PM   #6
rmknox
Member
 
Registered: May 2010
Posts: 354

Original Poster
Rep: Reputation: 34
Apparently we are talking at the same time.

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.
 
Old 07-08-2010, 07:10 PM   #7
rmknox
Member
 
Registered: May 2010
Posts: 354

Original Poster
Rep: Reputation: 34
You asked for a link to the bug report.

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.
 
Old 07-08-2010, 07:20 PM   #8
rmknox
Member
 
Registered: May 2010
Posts: 354

Original Poster
Rep: Reputation: 34
Unspawn
I'm an old hacker but a total novice at UNIX - did one unix job abt 20 years ago and remember almost nothing

you suggest I boot into level something of the bad version

how do I do that?

Imagine I've interrupted grub and am looking at its menu

how do I get to where you suggest

if I merely let grub launch the bad one I end up in a loop

Dick
 
Old 07-08-2010, 09:27 PM   #9
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: PCLinux, Slackware
Posts: 6,870

Rep: Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248Reputation: 1248
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?
 
Old 07-08-2010, 09:41 PM   #10
chrism01
LQ Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Centos 6.8, Centos 5.10
Posts: 17,240

Rep: Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324Reputation: 2324
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.
Try

yum list installed | grep kernel

to get the correct name https://access.redhat.com/kb/docs/DOC-2531
 
Old 07-08-2010, 11:01 PM   #11
rmknox
Member
 
Registered: May 2010
Posts: 354

Original Poster
Rep: Reputation: 34
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.

Thanks to all of you for your attention and help.

Dick
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Defective by Design is Defective LXer Syndicated Linux News 0 01-30-2010 01:00 AM
Fedora 9 boots (long delay) as single core if I go to GRUB menu, otherwise boots fine saravkrish Fedora 1 05-27-2008 08:59 AM
error when compiling 2.4 version of kernel from 2.6 version in fedora core mshenbagaraj Linux - Kernel 1 04-30-2007 04:31 PM
installed fedora and it boots! BUT still has a few more problems =( colinexl Linux - Newbie 4 01-13-2005 01:19 PM
redhat fedora gcc version (compiled for 2.4.20) doesn't match kernel version 2.4.22 start1000 Linux - Software 0 03-16-2004 09:17 PM


All times are GMT -5. The time now is 04:43 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration