monitor goes to "no signal" during boot

[suplero]

I have just started working with Lucid alpha 3, and discovered that for some reason at boot the monitor goes to standby with "no signal" but then wakes up again when kde starts.

I think this has something to do with the new bootsplash stuff, but I don't know why or how it is doing what it is.

What is particularly irksome about the situation is that I did an encrypted install, but the splash screen doesn't appear to ask for the passphrases, so I can't actually boot into the newly installed system.

I was able to get into grub at boot by holding the shift key down, and removed the "quiet splash" from grub boot options, but the screen still went to standby with no signal.

The only way to actually "see" the booting process was to add the nomodeset option to grub, but then for some reason a) it took forever to boot, and b) kde never started due to xserver errors.

Not quite the outcome I was hoping for.

On a side note, I really, REALLY don't get the fascination with bootsplashes to begin with. Taking away information is good I actually prefer seeing the boot process happen, so I know what is going on. Up until 10.04, removing the quiet and splash options allowed turning off the graphical crap at the beginning, but now with Lucid, apparently that option is no longer even provided.

Second side note: Why is cryptsetup dependent on plymouth? Really you can't provide an encryption system without a graphical boot system

sometimes the direction developers choose to go totally baffles me.

[suplero]

Re: monitor goes to "no signal" during boot

A second install turned out differently - I went with the guided partitioning using encrypted LVM, and the install works better.

The bootup still sends the monitor to standby with a "no signal" message, but I can enter the one password and it will then boot to KDE, which turns the monitor back on.

Still not ideal, but workable.

The previous installs were with 2 or more encrypted partitions, which I set up manually. Maybe that is still a work in progress.

Also, my system info is AMD Athlon 64, using Nvidia graphics card.

While trying different things to get x started before, I ran into several errors about firmware and noveau and a bunch of nvXX directories. I'm not sure if that is important.