From: Walt H <waltabbyh@comcast.net>
To: Bongani Hlope <bonganilinux@mweb.co.za>
Cc: thunder7@xs4all.nl, linux-kernel@vger.kernel.org
Subject: Re: vesafb problem
Date: Thu, 27 Mar 2003 14:30:21 -0800 [thread overview]
Message-ID: <3E837B7D.9010005@comcast.net> (raw)
In-Reply-To: <20030327233902.5963b0b1.bonganilinux@mweb.co.za>
Bongani Hlope wrote:
> Strange I'm having the same problem, but I only have 256MB of memory and my GeForce 2 only has 32MB. This is what's on my messages file:
>
>
> vesafb: framebuffer at 0xe0000000, mapped to 0xd0807000, size 32768k
> vesafb: mode is 800x600x16, linelength=1600, pages=3
> vesafb: protected mode interface info at c000:c060
> vesafb: scrolling: redraw
> vesafb: directcolor: size=0:5:6:5, shift=0:11:5:0
> Looking for splash picture.... found (800x600, 13683 bytes).
> Console: switching to colour frame buffer device 82x30
> fb0: VESA VGA frame buffer device
>
Hmmm. That's a different problem than I'm experiencing. Your system
appears to be correctly remapping the framebuffer and switching to it.
You don't get a graphical boot? Seems as if you should from the log
snippet you posted.
-Walt
next prev parent reply other threads:[~2003-03-27 22:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 16:41 vesafb problem Walt H
2003-03-27 19:02 ` Jurriaan
2003-03-27 19:34 ` Walt H
2003-03-27 21:39 ` Bongani Hlope
2003-03-27 22:30 ` Walt H [this message]
2003-03-28 3:55 ` Bongani Hlope
2003-03-27 22:27 ` Walt H
2003-03-27 23:11 ` Walt H
2003-03-28 20:59 ` vesafb problem with 1GB Ram and possible fix Walt H
2003-03-29 10:41 ` Antonino Daplas
2003-03-29 20:24 ` Walt H
2003-03-29 21:39 ` Antonino Daplas
2003-03-30 23:16 ` Walt H
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E837B7D.9010005@comcast.net \
--to=waltabbyh@comcast.net \
--cc=bonganilinux@mweb.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder7@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.