Skip to contentSkip to conversation

Weird framebuffer bug?

DISCUSSION [email protected] 2 participants 2 messages May 4, 2006

lore
Share & tools
lore
#0 lore raw
Quoted 1 line · --- Antonino A. Daplas

And if you can't specify

the actual resolution with vesafb, try nvidiafb.

I have specified the actual
resolution. Text mode with vesafb fills the whole screen (and the on-screen menu says 1024x768 which is the native resolution of the monitor). The screenshot I took when using X via fbdev (set to 1024x768 too) while the displaying was erroneous is 1024x768 as well. It somehow just doesn't reach the monitor in that form.

#1 lore raw
Quoted 7 lines · [email protected] wrote:
Quoted 1 line · --- Antonino A. Daplas

And if you can't specify

the actual resolution with vesafb, try nvidiafb.

Quoted 7 lines

I have specified the actual
resolution. Text mode with vesafb fills the whole screen (and the on-screen menu says 1024x768 which is the native resolution of the monitor). The screenshot I took when using X via fbdev (set to 1024x768 too) while the displaying was erroneous is 1024x768 as well. It somehow just doesn't reach the monitor in that form.

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.

BTW, what does dmesg and fbset -i say?

Tony

PS: I'll be traveling in a few hours, so I may not be able to answer back.