From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HuslU-0006HI-RA for garchives@archives.gentoo.org; Sun, 03 Jun 2007 16:17:13 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l53GG0bY001267; Sun, 3 Jun 2007 16:16:00 GMT Received: from spore.ath.cx (c-24-245-14-14.hsd1.mn.comcast.net [24.245.14.14]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l53GBSs2028551 for ; Sun, 3 Jun 2007 16:11:28 GMT Received: from pascal.spore.ath.cx (pascal.spore.ath.cx [192.168.1.100]) by spore.ath.cx (Postfix) with ESMTP id 1DCD52B3CB for ; Sun, 3 Jun 2007 11:11:28 -0500 (CDT) Date: Sun, 3 Jun 2007 11:11:28 -0500 From: Dan Farrell To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] framebuffer questions Message-ID: <20070603111128.61b51886@pascal.spore.ath.cx> In-Reply-To: <777855.78690.qm@web31713.mail.mud.yahoo.com> References: <20070602204229.6c3d433a@pascal.spore.ath.cx> <777855.78690.qm@web31713.mail.mud.yahoo.com> Organization: Spore, Ltd. X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.6; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 390d70f6-12b3-41d6-943d-85acd92b48a0 X-Archives-Hash: f0dec32753404e1c2519a91d7b5534ac On Sat, 2 Jun 2007 20:19:12 -0700 (PDT) maxim wexler 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,1024x768-32@85 | 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. -- gentoo-user@gentoo.org mailing list