To let the list know, I don't know if I follow this, but, it turns out
if I build vgabios 0.6a locally I can get this to work. I have to use
the "fbdev" device driver in XFree86, but it works.
Also, when I build the new vgabios.bin, it turns out I have to specify
the "-L" command line option for
On 3/26/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
I tried using the newer video appendage and it didn't seem to work. I
had to use the older vga=. I believe you are talking about the kernel
boot param, yes?
yes. normally the vesafb-tng is supposed to address missing functions
or resolutions of
no obvious problem in the xf86config file.
when all fails, use the framebuffer :) and Xfbdev (fbdev driver instead
of vesa)
The framebuffer seems to miss every other vertical scan line. I'm not
sure if I make sense, but the video wraps around the screen onto
itself vertically. Thus rendering hal
On 3/26/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
It does work in cirrus mode for 1024x768. I was under the impression
that it was all the cirrus driver would support. However, the std-vga
mode supports vga 799 and 798 in the console. (1600x1200:24bpp and
1600x1200:16bpp respectively)
The X dri
It does work in cirrus mode for 1024x768. I was under the impression
that it was all the cirrus driver would support. However, the std-vga
mode supports vga 799 and 798 in the console. (1600x1200:24bpp and
1600x1200:16bpp respectively)
Here is the output from dmesg showing the console working:
On 3/25/07, Christian MICHON <[EMAIL PROTECTED]> wrote:
On 3/26/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
> Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
> having 1600x1200 working in the virtual machine, so I looked at using
> the -std-vga option with the "vesa" X driver.
>
On 3/26/07, Kyle Hubert <[EMAIL PROTECTED]> wrote:
Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
having 1600x1200 working in the virtual machine, so I looked at using
the -std-vga option with the "vesa" X driver.
While initializing X, I get the following:
(...)
could you
Anthony Liguori <[EMAIL PROTECTED]> wrote:
> Kyle Hubert wrote:
> > Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
> > having 1600x1200 working in the virtual machine, so I looked at using
> > the -std-vga option with the "vesa" X driver.
>
> You probably have to increas
Kyle Hubert wrote:
Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
having 1600x1200 working in the virtual machine, so I looked at using
the -std-vga option with the "vesa" X driver.
You probably have to increase your hsync and vrefresh ranges.
Regards,
Anthony Liguori
Wh
Hi, I'm working with QEMU on an XFree86 machine. I was desirous of
having 1600x1200 working in the virtual machine, so I looked at using
the -std-vga option with the "vesa" X driver.
While initializing X, I get the following:
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIO
10 matches
Mail list logo
