[ltp] xorg dual-head with R50e

[Paul Kaplan]

Try the XF86Config file I posted 2x in the past week.
I'll bet it can be easily modified by comparing the entries with those in your 
default file.
Paul
On Thursday 08 September 2005 06:08 pm, Mo wrote:
> Hi there,
>
> I am trying to get a Xorg xinerama setup to work with my R50e, but even
> after searching google for days and trying many many different
> configurations I can't get it to work. The graphics card is a Intel 855GM.
> I'm running Debian Unstable, Xorg 6.8.2 (debian package) with a custom
> 2.6.13 kernel.
>
> This seems to be that bit that is failing:
> (II) Loading sub module "int10"
> (II) LoadModule: "int10"
> (II) Reloading /usr/X11R6/lib/modules/linux/libint10.a
> (II) I810(0): initializing int10
> (WW) I810(0): Bad V_BIOS checksum
> (II) I810(0): Primary V_BIOS segment is: 0xc000
> (EE) I810(0): vm86() syscall generated signal 4.
> (II) I810(0): EAX=0xc0000fdc, EBX=0x00000000, ECX=0x0000007d,
> EDX=0x0000ff00 (II) I810(0): ESP=0x00000fb2, EBP=0x00000fdc,
> ESI=0x00000000, EDI=0x0000200e (II) I810(0): CS=0xc000, SS=0x0100,
> DS=0x0000, ES=0x0000, FS=0x0000, GS=0x0000 (II) I810(0): EIP=0x0000303d,
> EFLAGS=0x00033282
> (II) I810(0): code at 0x000c303d:
>  c6 08 f6 c3 10 75 f2 80 fb 40 72 ea eb 1a bf 33
>  06 be 13 06 57 56 e8 be 00 5e 5f e8 b9 00 f6 c3
> (II) stack at 0x00001fb2:
>  84 52 a5 0c 00 00 00 00 0e 20 22 69 00 00 00 00
>  74 68 d6 69 7d 00 00 00 00 20 67 69 d7 1e 00 00
>  45 80 40 00 04 00 08 00 00 11 40 00 00 00 00 00
>  00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>  00 00 00 00 00 4f 00 00 00 06 00 00 00 32
> (II) I810(0): VESA BIOS not detected
>
>    *** If unresolved symbols were reported above, they might not
>    *** be the reason for the server aborting.
>
> Fatal server error:
> Caught signal 11.  Server aborting
>
>
>
> If it is of any help I put my configurations online:
> http://www.mopage.de/linux/Xorg.0.log
> http://www.mopage.de/linux/xorg.conf
> http://www.mopage.de/linux/kernel-config
>
> I played around with every combination of VBERestore, but I get the same
> error message.
>
> Thanks for any help,
> Mo