Actually that is probably a mistake on my side. I had the impression
that it was much longer but didn't take into account that the old
behaviour allowed the VGA console to work until viafb was completly
loaded and fbcon took over while the new one immediately destroys the
screen and shows random things until it is completely loaded. However
the time between hitting enter for the module load command and getting a
working fbcon really is at least nearly the same.
Well as for the behaviour change described above I think the problem
might be in the load path. At least when I faked an exit as when memory
size detection or ioremapping fails (which is a very common issue that
really needs a workaround) I get the same unusable VGA console. This
needs to be fixed.
This whole I2C stuff seems incredibly unstable I even have indicators
that the current code might be to blame for freezing the machine on some
configurations with P4M900 IGP. I just try to prevent it to get even
worse...
Thanks,
Florian Tobias Schandinat
--