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

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.


No idea where exactly but you'll likely find such options in /etc/sysconfig or /etc/system*/.


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.

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

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