Re: [!] 2.6.26 + vga=791
David Witbrodt wrote:
----- Forwarded Message ----
From: David Witbrodt <email@example.com>
To: Hugo Vanwoerkom <firstname.lastname@example.org>
Sent: Friday, August 1, 2008 10:34:51 PM
Subject: Re: [!] 2.6.26 + vga=791
But I did something interesting: I recompiled 2.6.26-1-686 but changed
to .config file to what I use with my homerolled kernel. And guess what:
The problem lies in the .config file that Debian uses and apparently my
hardware. Something that Maximilian Attems pointed out in
please enlighten us on the .config changes.
we are *not* carrying any fb specific patches.
So now I have to go item by item and investigate the diff in .config
files, which is vast because with my .config the kernel compiles in 12
minutes and with the Debian .config it takes 1 hour + 20 minutes!
That is good news. You may be getting close to a solution.
Might I suggestion the following incantation:
diff -y | less
I use that after I compile my new kernels from source and respond to the
questions presented by 'make oldconfig'. I keep personal documentation
on the kernel config settings that are relevant for my machines, and I
have found this diff trick to be the fastest way to incorporate changes
with new kernel versions.
The "-y" option gives you a side-by-side dump of both files -- no lines
omitted -- with indicators of lines that are different and lines that
are contained in only one file. Hopefully you have a fairly high
resolution monitor! ;) I like to run that diff in an xterm that I have
maximized using the F11 key.
Good clue! But I am no closer and consider giving up: it would only be
useful if I found a kernel parameter for the cmdline to avoid being
Any other "fix" entails recompiling the Debian Kernel, e.g. in order to
install uvesfb you have to do that.
The last Debian kernel that ran with vga=791 was 2.6.24. So I did a diff
-y beteen that and 2.6.25 that does *not* allow vga=791. That file is here: