On Sat, 2 Jun 2007 20:19:12 -0700 (PDT) maxim wexler <[EMAIL PROTECTED]> wrote:
> > also, gentoo has a doc: > > > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=10 > > That gives the best explanation. Now dmesg | grep -i > vesa concludes with: > <...> > vesafb: framebuffer at 0xf0000000, mapped to > 0xd1900000, using 10240k,total 16384k > fb1: VESA VGA frame buffer device. Thke vesafb driver is built into the kernel, right? You need it right away when booting. No sense in fiddling around with initrd's, just put it in the kernel. > But, the screen looks the same. I started out with > 1024x768 then changed to 1280x1024 but certain web > pages still do not fit the screen. For example, a > trip to the above handbook address using elinks is an > exercise in frustration. As you scroll down using the > down arrow the page jumps from side to side making it > very difficult to follow. That does sound frustrating. Let me provide some qotes: | |video=vesafb:mtrr:3,ywrap,[EMAIL PROTECTED] | I still think your boot line isn't quite right. May I see the updated version from /proc/cmdline ? > If I manually enter the kernel line at the prompt w/o > mentioning the framebuffer at all one is installed > anyway which is just like all the others :( Yes, that's why I think the boot command line isn't quite right. The kernel loads the driver eventually, if it's not specified the settings at boot, just like all other drivers get loaded, and if they find hardware to support, generally say something on the console. By the time vesafb loads on your system, it's already initialized the console and it's too late to give it the resolution you want. -- [EMAIL PROTECTED] mailing list
