请问一下，谁的gentoo-source-2.6.15-r1编译支持framebuffer成功了？

shaaben

我用nvidiafb也很慢，大概是在挂根文件系统的时候才出来。

vulcan

我用的VESA-FB，不是nvidia-fb，我今天尝试把fbsplash编译到了内核中，但是还是要到挂载分区的时候，也就是内核被初始化之后才出现splash，这可能是initramfs的问题，但是找了一个小时，找不到可能原因，谁还有这方面的经验？提示一下。

shaaben

You may (and probably will) find that the background image is loaded with a certain few-seconds-delay even when using an initramfs image. During that time the standard black-and-white 640x480 resolution is used.

Such behaviour is normal. The only workaround (in order to get the background image as early as possible) would be using the vesafb frame buffer device (instead of vesafb-tng). Here's Spock's elaborate answer on that issue: "The initramfs is used to populate the root filesystem before the frame-buffer subsystem is initialized, so it's good enough - don't worry about it. As you might have noticed, your PC boots into the text mode, and not the graphics mode. The graphics mode is set up when the framebuffer sub-system is initialized. But before that can happen, other things must be initialized, things that take some time. That's why for a second or two you might be seeing the kernel messages. You might say that with vesafb you didn't have those. And you will be right. But vesafb is an exception, not a rule (it's initialized while the kernel is being loaded) . Every other fb driver, including vesafb-tng, rivafb, radeonfb,... is initialized with the fbdev subsystem".

Compiling the initramfs image directly into the kernel rather than loading it at boot should also greatly reduce the time it takes to display the bootsplash image as it can then load all the necessery files straight away rather than waiting untill filesystems have been mounted.

vulcan

看来是2.6.15-r1的问题，应该出在了initrd上，我换到更高的2.6.15-r7一切正常了，我以前的老内核也很好，大概1秒左右就进入到图形的控制台。

晨想

2.5.16?内核 还是？。。嘿嘿。。

vulcan

Post by 终极幻想
2.5.16?内核 还是？。。嘿嘿。。

不好意思，写错了，2.6.15,哈哈