Noob poster here, so apologies if this has already been done to death, however I can't find it under the search engine or in the manuals.
I have a Lenovo W500 laptop (Kernel 2.6.38 + Radeon HD 3650) which sometimes boots into F15 and sometimes doesn't. The issue seems to lie in the graphics hardware chosen during the boot when prompting for the password for the LUKS partition. Sometimes I get a graphic screen (blue background, padlock and text box), sometimes I have to press escape and can then enter the password and sometimes it will ignore this and continue to a kernel oops. This is prior to the greeter startup - is systemd trying to find hardware/video at this point? Is it trying to use the frame buffer device? Apologies, but I don't know where to start finding logs for this, if it dies with a kernel oops, after a restart the boot.log shows no evidence of what happened as it records only the successful boot. I've tried adding some of the video drivers to the ramdisk image using dracut, but this has made no difference.
The laptop was upgraded from FC14 using preupgrade - which failed. I then had to use the F15 DVD to recover and complete the upgrade. rpm -Va shows a number of issues with dependencies that I suspect are due to the co-existence of both fc14 and fc15 packages. FC14 sometimes exhibits this behaviour, but does not kernel oops if the splashscreen graphics for the passphrase cannot be started - it continues to the greeter. FC14 was a clean installation using the LXDE spin and has been maintained through yum.
Full hardware profile is here:
I haven't installed the ATI drivers, and am running the standard Intel/radeon drivers as delivered in the FC15 DVD (full DVD, not live)
If anyone can point me in the direction of how to troubleshoot further and any tips/links with respect to this boot problem with the LUKS passphrase, I'd really appreciate it. Even if it's just pointers on what to search for...
Thanks in advance..
---------- Post added at 02:35 PM ---------- Previous post was at 11:51 AM ----------
Some more info. If I install the livna catalyst drivers (livna-config-display, xorg-x11-drv-catalyst*), it does get around the boot issue with the luks encrypted passphrase. However I now need to try and develop a working xorg.conf as the greeter does not start.
I'll try and post up the fatal errors in X startup when I get the chance later...