From: grfgguvf.29601511@bloglines.com
To: adaplas@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weird framebuffer bug?
Date: 4 May 2006 23:42:07 -0000 [thread overview]
Message-ID: <1146786127.1525598216.32201.sendItem@bloglines.com> (raw)
--- Antonino A. Daplas <adaplas@gmail.com> wrote:
> Does the same thing happens
with different color depths?
>
> Can you try using the "vesa" driver with
X? If the same thing happens, it might
> be a problem with the BIOS.
>
I will check these later.
>
> BTW, what does dmesg and fbset -i say?
>
% dmesg | egrep -i 'frame|fb|vesa|nv'
BIOS-e820: 0000000007fff000
- 0000000008000000 (ACPI NVS)
Security Framework v1.0.0 initialized
vesafb:
framebuffer at 0xf0000000, mapped to 0xb8880000, using 6144k, total 32768k
vesafb: mode is 1024x768x32, linelength=4096, pages=1
vesafb: protected
mode interface info at c000:c060
vesafb: scrolling: redraw
vesafb: Truecolor:
size=8:8:8:8, shift=24:16:8:0
Console: switching to colour frame buffer device
128x48
fb0: VESA VGA frame buffer device
# fbset -i
mode "1024x768-76"
# D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
geometry 1024 768 1024
768 32
timings 12714 128 32 16 4 128 4
rgba 8/16,8/8,8/0,8/24
endmode
Frame buffer device information:
Name : VESA VGA
Address
: 0xf0000000
Size : 6291456
Type : PACKED PIXELS
Visual : TRUECOLOR
XPanStep : 0
YPanStep : 0
YWrapStep : 0
LineLength : 4096
Accelerator : No
> Tony
>
> PS: I'll be traveling in a few hours, so I may not be able to answer
back.
>
Well thank you for answering so far then.
This is not urgent
you can answer tomorrow or at any later time.
next reply other threads:[~2006-05-04 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 23:42 grfgguvf.29601511 [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-05 1:33 grfgguvf.29601511
2006-05-04 22:01 grfgguvf.29601511
2006-05-04 23:07 ` Antonino A. Daplas
2006-05-04 21:34 grfgguvf.29601511
2006-05-04 21:24 grfgguvf.29601511
2006-05-04 21:29 ` Valdis.Kletnieks
2006-05-04 21:44 ` Antonino A. Daplas
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=1146786127.1525598216.32201.sendItem@bloglines.com \
--to=grfgguvf.29601511@bloglines.com \
--cc=adaplas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®