[SOLVED] Kernel 18.104.22.168 will boot all the way to loading services, then stop
I've been a Slackware/Redhat user for many years until v.6, then withdrawn for almost 10 years.
Now I am back and building 2 machines for my kids to use for school projects.
Installed Fedora 11, d/l latest stable kernel from .org, configured, compiled, installed and stalled at the point where kernel will boot all the way up to the point where it will start services. Instead of proceeding, it just sits there and I can type anything and it will appear on the screen. If at that point I would press CAD, it will say shutting down MD volumes and reboot.
What information should I provide for you to be able to help me troubleshoot this particular kernel?
I can boot into the kernel 22.214.171.124 that came with the latest update no problem and am writing it from that Fedora 11 machine.
Here's my Grub.conf with the kernel in question coming first:
# grub.conf generated by anaconda
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_lion-lv_root
# initrd /initrd-version.img
title Fedora (126.96.36.199.-LionP4.fc11.i686)
kernel /vmlinuz-188.8.131.52.LionP4.fc11.i686 ro root=/dev/mapper/vg_lion-lv_root rhgb vga=0x346 #quiet
title Fedora (184.108.40.206-96.fc11.i586)
kernel /vmlinuz-220.127.116.11-96.fc11.i586 ro root=/dev/mapper/vg_lion-lv_root rhgb quiet vga=0x346
title Fedora (18.104.22.168-96.fc11.i686.PAE)
kernel /vmlinuz-22.214.171.124-96.fc11.i686.PAE ro root=/dev/mapper/vg_lion-lv_root rhgb quiet vga=0x346
title Fedora (126.96.36.199-167.fc11.i686.PAE)
kernel /vmlinuz-188.8.131.52-167.fc11.i686.PAE ro root=/dev/mapper/vg_lion-lv_root rhgb quiet vga=0x346
No one was able to provide any ideas so far
After posting the same on several forums I got no meaningful response.
No one was able to advise what process was pending at the black screen.
Also I tried upgrading to F12 and that thoroughly messed up the system, which I ended up re-partitioning, re-formatting and installing from scratch. After I completely recover the environment, I will resume testing of the new kernel compilation.