lkml.org 
[lkml]   [2006]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Weird framebuffer bug?
--- 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-05-05 01:44    [W:0.024 / U:0.596 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site