Am 13.05.14 21:48, schrieb Bernhard Walle:
> However, I took the step to update the x86emu code from X.org. That
> seems to work! At least with my test VM that is based on Arch Linux.
> I'll try the original Gentoo-based VM tomorrow.
That worked, too. :)
I sent a pull request via https://github.c
Am 13.05.14 17:41, schrieb Kevin O'Connor:
>
> So, my advice would be to either avoid x86emu (eg, maybe by trying the
> vm86 mode of v86d, or maybe by not using uvesafb), try compiling v86d
> with a newer version of x86emu, or stick with the "lgpl VGA BIOS".
Unfortunately I cannot use vm86 mode b
On Tue, May 13, 2014 at 08:08:41PM +0200, Gerhard Wiesinger wrote:
> On 13.05.2014 17:41, Kevin O'Connor wrote:
> > The x86emu code does not properly emulate "leal" (as near as I can tell
> >it treats it as a "leaw" instead), which leads to all sorts of bizarre
> >behavior when it tries to interpre
On 13.05.2014 17:41, Kevin O'Connor wrote:
The x86emu code does not properly emulate "leal" (as near as I can
tell it treats it as a "leaw" instead), which leads to all sorts of
bizarre behavior when it tries to interpret the code. This type of
issue has occurred for a bunch of instructions (o
On Tue, May 13, 2014 at 11:20:11AM +0200, Bernhard Walle wrote:
> Am 2014-05-13 07:52, schrieb Bernhard Walle:
> >* Kevin O'Connor [2014-05-12 22:07]:
> >>On Mon, May 12, 2014 at 08:53:53PM +0200, Bernhard Walle wrote:
> >>> Am 2014-05-12 07:29, schrieb Kevin O'Connor:
> >>> >
> >>> >It does look
Am 2014-05-13 07:52, schrieb Bernhard Walle:
Hi,
* Kevin O'Connor [2014-05-12 22:07]:
On Mon, May 12, 2014 at 08:53:53PM +0200, Bernhard Walle wrote:
> Am 2014-05-12 07:29, schrieb Kevin O'Connor:
> >
> >It does look like the x86emu issue. You can try applying the
> >SeaVGABIOS patch below to
Hi,
* Kevin O'Connor [2014-05-12 22:07]:
> On Mon, May 12, 2014 at 08:53:53PM +0200, Bernhard Walle wrote:
> > Am 2014-05-12 07:29, schrieb Kevin O'Connor:
> > >
> > >It does look like the x86emu issue. You can try applying the
> > >SeaVGABIOS patch below to confirm it.
> >
> > The output doesn
On Mon, May 12, 2014 at 08:53:53PM +0200, Bernhard Walle wrote:
> Am 2014-05-12 07:29, schrieb Kevin O'Connor:
> >
> >It does look like the x86emu issue. You can try applying the
> >SeaVGABIOS patch below to confirm it.
>
> The output doesn't appear. But I'm sure that I copied the correct files
>
Am 2014-05-12 07:29, schrieb Kevin O'Connor:
It does look like the x86emu issue. You can try applying the
SeaVGABIOS patch below to confirm it.
The output doesn't appear. But I'm sure that I copied the correct files
because modifications of other strings worked.
Regards,
Bernhard
-Kevin
On Sun, May 11, 2014 at 04:19:55PM +0200, Bernhard Walle wrote:
> Am 2014-05-11 14:37, schrieb Kevin O'Connor:
> >On Sun, May 11, 2014 at 01:42:57PM +0200, Bernhard Walle wrote:
> >>Am 10.05.14 17:07, schrieb Kevin O'Connor:
> >>> Also, it looks like uvesafb can call x86emu. Older versions of x86e
Am 2014-05-11 14:37, schrieb Kevin O'Connor:
On Sun, May 11, 2014 at 01:42:57PM +0200, Bernhard Walle wrote:
Am 10.05.14 17:07, schrieb Kevin O'Connor:
> Also, it looks like uvesafb can call x86emu. Older versions of x86emu
> are known to not emulate some instructions properly, and it has cause
On Sun, May 11, 2014 at 01:42:57PM +0200, Bernhard Walle wrote:
> Am 10.05.14 17:07, schrieb Kevin O'Connor:
> > Also, it looks like uvesafb can call x86emu. Older versions of x86emu
> > are known to not emulate some instructions properly, and it has caused
> > problems for SeaVGABIOS. The most r
Am 10.05.14 17:07, schrieb Kevin O'Connor:
>
> Can you run the original SeaVGABIOS image and provide the output with
> the following added to the qemu command line:
>
> -chardev stdio,id=seabios -device isa-debugcon,iobase=0x402,chardev=seabios
Since it's quite much debugging info, I uploaded it
On Fri, May 09, 2014 at 05:06:21PM +0200, Bernhard Walle wrote:
> Hello,
>
> I'm using QEmu 2.0.0 on a Linux host (x86-64) with a quite special
> target system that uses uvesafb ('video=uvesafb:1024x768-32'). I get
> following errors in the target system:
>
> uvesafb: Getting mode info block
Hello,
I'm using QEmu 2.0.0 on a Linux host (x86-64) with a quite special
target system that uses uvesafb ('video=uvesafb:1024x768-32'). I get
following errors in the target system:
uvesafb: Getting mode info block for mode 0x2 failed (eax=0x4f01, err=1)
uvesafb: Getting mode info block f
15 matches
Mail list logo