At boot up the picture is shifted approxximately 10% to the left, when I enter x-mode the picture fits perfect. I can switch with ctrl-alt-f1 to the console and adjust it with the auto adjust button on my lcd screen. But when I switch back to x-mode ctrl-alt-f7 the x-screen is now shifted to the right. Without the console framebuffer the shifting doesn't occur! For console-framebuffer i use vesa-tng! I don't know the version of gensplash, but now i use gentoo-sources-2.6.16-gentoo-12, but this did not work with previous versions. Unfortunately i didn't know the exakt kernel-version where this things begin to happen, but i think it was before gentoo-sources-2.6.14
Please provide: 1) the output of `fbset -i` 2) the contents of /proc/fb0/modes 3) the contents of /proc/cmdline 4) the output of `dmesg | grep vesa`
(In reply to comment #1) > Please provide: > 1) the output of `fbset -i` > 2) the contents of /proc/fb0/modes > 3) the contents of /proc/cmdline > 4) the output of `dmesg | grep vesa` > ok here is the information you have requested fbset -i mode "1280x1024-75" # D: 139.237 MHz, H: 80.252 kHz, V: 75.072 Hz geometry 1280 1024 1280 3000 16 timings 7182 228 89 41 1 138 3 vsync high rgba 5/11,6/5,5/0,0/0 endmode Frame buffer device information: Name : VESA VGA Address : 0xd8000000 Size : 7680000 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 0 YPanStep : 1 YWrapStep : 1 LineLength : 2560 Accelerator : No cat /proc/fb0/modes 640x400-8 640x480-8 800x600-8 1024x768-8 1280x1024-8 320x200-16 320x200-32 640x480-16 640x480-32 800x600-16 800x600-32 1024x768-16 1024x768-32 1280x1024-16 320x200-8 320x400-8 320x400-16 320x400-32 320x240-8 320x240-16 320x240-32 640x400-16 640x400-32 1600x1200-8 1600x1200-16 cat /proc/cmdline root=/dev/hda8 video=vesafb:ywrap,mtrr:3,1280x1024-32@75 splash=verbose,kdgraphics,fadein,theme:emergence quiet console=tty1 BOOT_MSG="Welcome to Gentoo Linux" dmesg | grep vesa Kernel command line: root=/dev/hda8 video=vesafb:ywrap,mtrr:3,1280x1024-32@75 splash=verbose,kdgraphics,fadein,theme:emergence quiet console=tty1 BOOT_MSG="Welcome to Gentoo Linux" vesafb: NVidia Corporation, NV20 Board, Chip Rev A3 (OEM: NVidia) vesafb: VBE version: 3.0 vesafb: protected mode interface info at c000:b8a0 vesafb: pmi: set display start = c00cb8e5, set palette = c00cb96a vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da vesafb: VBIOS/hardware supports DDC2 transfers vesafb: monitor limits: vf = 75 Hz, hf = 83 kHz, clk = 140 MHz vesafb: scrolling: ywrap using protected mode interface, yres_virtual=3000 vesafb: framebuffer at 0xd8000000, mapped to 0xe0880000, using 7500k, total 65536k
It seems that my bug is aduplicate of Bug 130207. When i remove the "@75" from 1280x1024-32@75 everything works fine again! What could be the reason for this?
Here is the output with the now working settings! fbset -i mode "1280x1024-75" # D: 135.007 MHz, H: 79.981 kHz, V: 75.029 Hz geometry 1280 1024 1280 3000 16 timings 7407 248 16 38 1 144 3 hsync high vsync high rgba 5/11,6/5,5/0,0/0 endmode Frame buffer device information: Name : VESA VGA Address : 0xd8000000 Size : 7680000 Type : PACKED PIXELS Visual : TRUECOLOR XPanStep : 0 YPanStep : 1 YWrapStep : 1 LineLength : 2560 Accelerator : No cat /proc/fb0/modes 640x400-8 640x480-8 800x600-8 1024x768-8 1280x1024-8 320x200-16 320x200-32 640x480-16 640x480-32 800x600-16 800x600-32 1024x768-16 1024x768-32 1280x1024-16 320x200-8 320x400-8 320x400-16 320x400-32 320x240-8 320x240-16 320x240-32 640x400-16 640x400-32 1600x1200-8 1600x1200-16 cat /proc/cmdline root=/dev/hda8 video=vesafb:ywrap,mtrr:3,1280x1024-32 splash=verbose,kdgraphics,fadein,theme:emergence console=tty1 BOOT_MSG="Welcome to Gentoo Linux" dmesg | grep vesa Kernel command line: root=/dev/hda8 video=vesafb:ywrap,mtrr:3,1280x1024-32 splash=verbose,kdgraphics,fadein,theme:emergence console=tty1 BOOT_MSG="Welcome to Gentoo Linux" vesafb: NVidia Corporation, NV20 Board, Chip Rev A3 (OEM: NVidia) vesafb: VBE version: 3.0 vesafb: protected mode interface info at c000:b8a0 vesafb: pmi: set display start = c00cb8e5, set palette = c00cb96a vesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da vesafb: VBIOS/hardware supports DDC2 transfers vesafb: monitor limits: vf = 75 Hz, hf = 83 kHz, clk = 140 MHz vesafb: scrolling: ywrap using protected mode interface, yres_virtual=3000 vesafb: framebuffer at 0xd8000000, mapped to 0xe0880000, using 7500k, total 65536k
(In reply to comment #3) > It seems that my bug is aduplicate of Bug 130207. When i remove the "@75" from > 1280x1024-32@75 everything works fine again! What could be the reason for this? > What is the status of this and Bug 130207. Removing the frequency "@75" seems to solve the problem. I can not test if this gets solved anytime as my hardware has changed and this problem did not occur anymore.
The status is that I'm waiting for uvesafb to be included in gentoo-sources. Once that happens (2.6.23), all vesafb-tng bugs will be closed. Hopefully uvesafb won't suffer from any of these issues. If it does, they will be investigated and fixed.
(In reply to comment #6) > The status is that I'm waiting for uvesafb to be included in gentoo-sources. > Once that happens (2.6.23), all vesafb-tng bugs will be closed. Hopefully > uvesafb won't suffer from any of these issues. If it does, they will be > investigated and fixed. > Thanks for your fast reply, i was just wondering why this bugs are still open! So let us see what uvesafb brings.
I'm closing this bug as WONTFIX, since we're dropping support for vesafb-tng. vesafb-tng has been replaced by uvesafb in gentoo-sources-2.6.23. uvesafb provides the same functionality, but is completely redesigned and hopefully will prove to be free of any bugs that might have been present in vesafb-tng. If you encounter a similar problem with uvesafb, please open a new bug.
