I finally got around to applying early printk, and I found out that the
system does indeed get to startup_32(). As it turns out this was simply
related to a CONFIG problem. I built-in INPUT (instead of using it as a
module), and the virtual console CONFIG was then made available. (NOTE:
I didn't think to check the input subsystem config, because the last
time I mistakenly disabled input -- because I simply used "make
oldconfig" which didn't enable CONFIG_INPUT -- the only thing it
disabled was the keyboard and mouse). Why does CONFIG_INPUT affect the
console?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/