On Monday 14 November 2005 17:03, Jonas Smedegaard was heard to say: > No need for excuse: this is highly relevant info, as I suspect it > shows that the recent yaird inclusion of fbcon is what solves this. > > Could it be that even if you noticed the new fbcon line in > Default.cfg, your image is in fact from an older date so does not > include this? Yes indeed. This afternoon, after I let the fact that fbcon was in there sink in for a few minutes (the 2-year-old was asleep, amazing what a difference that makes in my attention span!), and realized I didn't remember it when I looked in Default.cfg the first time last week, I decided to do something suggested by the folks on debian-user and "reinstall" so yaird would generate a new initrd. I did that by "dpkg-reconfigure linux-image-2.6.14-1-686" and watched to make sure that yaird was mentioned in the output. It was, and that's when I tried putting "vga=791" back in to lilo.conf and it worked. > The reason I am interested in this is that with the newest kernel > release fbcon is builtin, so you are one of the last to help figure > out if fbcon is actually needed to be builtin. Well, it worked today when it didn't work when I first installed 2.6.14, so indeed something in the mean time changed for the better. Can you think of any additionall information I might be able to provide? I do not remember editing any files by hand other than lilo.conf. I just looked at Default.cfg, I didn't change anything. I hope that helps. > - Jonas Curt- -- September 11th, 2001 The proudest day for gun control and central planning advocates in American history
Attachment:
pgpE0XmqpZVpy.pgp
Description: PGP signature