On Di, 2008-02-19 at 16:21 +0000, Andreas Winkelbauer wrote: > as far as I have seen the 'special' modes have a preprocessor constant defined > in vgabios/vbe.h which looks like > #define VBE_OWN_MODE_1152X864X8888 0x14c > > the numbers (0x14c in this case) correspond to those used in vbetables-gen.c. > I > don't know if and where these definitions are used Yes, I found that too, but I could any references to it. I added my mode anyways, which didn't change anything.
> in fact all the non-standard (widescreen) modes defined in vbetables-gen.c > work > for me _except_ 1680x1050. I've tested this with kvm-60, kvm-61 and the latest > snapshot (as of writing this). this really looks like a limitation somewhere, > but at the moment I have no clue who could be responsible for that limitation. This is very strange... For me only some of the additional modes work and are reported by the driver correctly, but I couldn't find the criteria which makes the difference. > well, the amount of memory (in bytes) needed (for the framebuffer) is: width x > heigth x (color depth in bit / 8). in you example: 1920 x 1200 x 4 = 9216000 > bytes which is greater than 8MB, so you might want to try using 16MB of video > memory. I did already. Increasing the value in the vbetables.h actually did change the amount of vram reported by the windows driver, but appart from that nothing changed. Regards, Arne ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
