I had CONFIG_FB_VIRTUAL set to be a loadable module, not
compiled into the kernel. The output stopped long before the
root partition was mounted, so the vfb module could not possibly
have been loaded at that point.
I also tried rebuilding the kernel with CONFIG_FB_VIRTUAL=n,
and got the same results. The output stops immediately after
"uncompressing image..ok now booting kernel." The system comes up
without any output to the console whatsoever, and I can telnet it.
If I touch the console keyboard, the system crashes or freezes or at
least drops off the network. I cannot determine what happens exactly,
because there is no console output. All I know is that the system
disappears from the network.
I have all of the other framebuffer devices activated, so
I suspect that /dev/fb0 is being set to some other frame buffer
device. Is there some file in /proc that I could examine to see
what frame buffers the kernel thinks it has? (From a quick grep
of linux/Documentation/fb/* and linux/drivers/video/*.c, I guess
the answer is "no".)
Anyhow, thanks for the advice. I suspect the problem is
along the lines that you have described, but with some other
framebuffer device besides /dev/vfb being the culprit.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 205
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu