2008/8/27, Julien Cristau <jcristau@debian.org>:
> Yeah, seems it's the same error in x86emu, and the same SiS chip, so
> probably the same bug.
I have tried to use the vesa driver (by replacing 'sis' by 'vesa' in xorg.conf). It doesn't work: the xserver is not loaded and an error is displayed (it talks about a failure occured when X starts so X is disabled and gdm has to be restarted when X will be configured).
xserver-xorg-video-vesa is installed.
The file joined to this e-mail comes from :
/usr/share/bug/xserver-xorg/script 3>output_script_vesa
The error the signal 11 still exists but the two errors about the 'suspect byte access to port 4' are not there.
> We'll need more debugging information from
> x86emu to understand what's going on,
>
In the source package xorg-server, in hw/xfree86/x86emu/
there is debug.c (which includes hw/xfree86/x86emu/x86emu/x86emui.h and x86emui.h includes debug.h).
The code uses a preprocessor directive
#ifdef DEBUG
There is the same directive in several files in hw/xfree86/int10/ but no specific debug.{c|h} file. INT10.HOWTO talks about vm86_GP_fault() for debugging purpose (PIO instructions can be logged).
Do you think the log will be more verbose if I install xserver-xorg-core-dbg?
--
Stéphane.
Attachment:
output_script_vesa
Description: Binary data