Re: Xvesa on FC2 and xcompmgr

On Wed, 31 Mar 2004, Douglas McMorris wrote:

> >> > 1: Xvesa -verbose returns this:
> >> > Mode requested 640x480x4
> >> >     0x0012: 640x480x4 Planer (4 planes) (no linear framebuffer)
> >> >     Static color bpp 4 depth 4
> >> > Previous modes: VBE 0x4148 BIOS 0x48
> >> > Enable BIOS mode 0x12
> >> > Segmentation fault
> >>
> >> I have the same problem.  It was fine until i updgraded to FC2-test2 (i
> >> was on test1 before).
> >>

Excellent. This is the same situation I get when trying to list available
modes using Slackware with a 2.6 kernel (though vm86_loop actually just
never exits). As I understand it, FC2-test2 adds a 2.6 kernel, no? Are you
both newly running 2.6? I'm going to investigate kernel differences first
if this is the issue, and see if there is some extra protection-level that
thwarts calling software interrupt 0x80 in 2.6 directly which vm86old()
does.

 - Brent

> (gdb) run
> Starting program: /opt/fdo/bin/Xvesa -mode 0x011B :1 -query localhost
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0804f39a in vm86old (vm=0x9f506a0) at vm86.c:684
> 684         asm volatile (
> (gdb) bt
> #0  0x0804f39a in vm86old (vm=0x9f506a0) at vm86.c:684
> #1  0x0804ef91 in vm86_loop (vi=0x9f50688) at vm86.c:514
> #2  0x0804eb4a in Vm86DoInterrupt (vi=0x9f50688, num=167052936) at vm86.c:235
> #3  0x0804e3ba in VgaSetMode (vi=0x9f506a0, mode=18) at vga.c:105
> #4  0x0804cad3 in vesaSetMode (pScreen=0x0, mode=0x9f51448) at vesa.c:1318
> #5  0x0804cb1a in vesaEnable (pScreen=0x9f515a8) at vesa.c:1338
> #6  0x0807fc67 in KdScreenInit (index=0, pScreen=0x9f515a8, argc=6,
>     argv=0xfee71fd4) at kdrive.c:1254
> #7  0x080500b0 in AddScreen (pfnInit=0x807f930 <KdScreenInit>, argc=6,
>     argv=0xfee71fd4) at main.c:748
> #8  0x08080031 in KdInitOutput (pScreenInfo=0x80f72a0, argc=6,
> argv=0xfee71fd4)
>     at kdrive.c:1446
> #9  0x0804f69c in main (argc=6, argv=0xfee71fd4, envp=0xfee71ff0) at
> main.c:356