LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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


Closed Thread
  Search this Thread
Old 11-18-2012, 10:42 AM   #1
rmknox
Member
 
Registered: May 2010
Posts: 354

Rep: Reputation: 34
Need help from a Grubista or a Kernel Nut - fedora 16 problem


I need help from someone more knowledgeable and sophisticated than I.

1)My latest fedora 16 3.6.6-1.fc16-.i686 shows the grub banner but does not bring up the log on screen. I need to tell grub to load the prior version 3.4.11 which works fine.
I would like to see what is happening with 3.6.6 after the grub banner. I suspect there is a configuration file parameter that would let me do this. Maybe in the grub config file or where-ever. Can someone lead me there?

2)I see in /boot that the file intrafms-3.6.6-1.fc16.i686.img is dated 11/14 - the day before I first noticed this problem

per Nautilus
initramfs-3.6.6-1.fc16.i686.img
Wed 14 Nov 2012 08:34:44 PM PST

I don't recall taking any action that would change the system the day before I first noticed the problem. Perhaps I have a parameter set to automatically update the kernel ? I believe there is a parameter that allows automatic update; can someone point me to it since I think I'd be better off not having the system update automatically.

Any help would be appreciated

Dick
 
Old 11-18-2012, 01:51 PM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,331
Blog Entries: 55

Rep: Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530
Quote:
Originally Posted by rmknox View Post
My latest fedora 16 3.6.6-1.fc16-.i686 shows the grub banner but does not bring up the log on screen. I need to tell grub to load the prior version 3.4.11 which works fine.
If with "grub banner" you mean the menu from which you select the OS and kernel to boot then that is different from the "log on screen", which is the Display Manager (DM): GDM for GNOME, KDM for KDE, etc, etc. Depending on what bootloader you use, GRUB legacy or GRUB2, and how it was configured you may see (or not see) kernels versions displayed at the "grub banner". If you don't see any entries try pressing the "e" key (edit) or ESC on bootup after your BIOS diagnostics finished (if it shows at all). If you now can select an entry try picking the previous kernel. If only the 3.6.6 kernel line shows then select that, press "e", move the cursor to the kernel line, press "e" again, move the cursor to the end of the line, add a space and then (w/o quotes) "systemd.unit=rescue.target". Now press enter and then "b" to boot into single user level where you can log in on the command line. Best first check /var/log/messages and other log files in /var/log for clues.


Quote:
Originally Posted by rmknox View Post
I would like to see what is happening with 3.6.6 after the grub banner. I suspect there is a configuration file parameter that would let me do this. Maybe in the grub config file or where-ever.
No idea where exactly but you'll likely find such options in /etc/sysconfig or /etc/system*/.


Quote:
Originally Posted by rmknox View Post
I don't recall taking any action that would change the system the day before I first noticed the problem. Perhaps I have a parameter set to automatically update the kernel ? I believe there is a parameter that allows automatic update; can someone point me to it since I think I'd be better off not having the system update automatically.
It sure is an inconvenience to have a non-booting system but setting the option to "off" does not fix things.
IMHO it would be better to configure GRUB(2) to show you earlier kernels to boot so you can check lo files and run diagnostics to fix things the right way.
 
1 members found this post helpful.
Old 11-18-2012, 09:53 PM   #3
rmknox
Member
 
Registered: May 2010
Posts: 354

Original Poster
Rep: Reputation: 34
Quote:
Originally Posted by unSpawn View Post
If with "grub banner" you mean the menu from which you select the OS and kernel to boot then that is different from the "log on screen",
Hi unSpawn

Based on your comments I believe I've done a poor job of describing the problem. Thanks for those comments. I decided to post a better written version on the Fedora distributions forum.

Thanks

Dick
 
Old 11-19-2012, 03:49 AM   #4
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,331
Blog Entries: 55

Rep: Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530Reputation: 3530
FUP: http://www.linuxquestions.org/questi...up-4175437735/
 
  


Closed Thread


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
CyberPower CP1500C UPS and USB with NUT problem 81bones Linux - Hardware 4 09-23-2011 11:01 AM
NUT config problem: chdir sKaar Slackware 2 12-16-2006 02:23 AM
UPS NUT install problem tramni1980 Slackware 0 08-14-2006 07:05 AM
Problem getting my Debian box to use nut to talk to my Belkin UPS AlucardZero Linux - Software 0 05-21-2006 07:00 PM
Fedora Apache drive me nut hct224 Linux - Newbie 6 10-07-2004 02:22 AM


All times are GMT -5. The time now is 07:04 AM.

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