Dual monitor problems on Acer Travelmate

[ollo]

Hi
after spending al lot of time reading and testing out most of the articles here..
I still got problems get xinerama working on my acer laptop.

my Config-File:

Section "ServerLayout"
Identifier "XFree86 Configured"
Screen "Screen 0"
Screen "Screen 1" LeftOf "Screen 0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
# FontPath "unix/:7100"
EndSection

Section "Module"
Load "extmod"
Load "xie"
Load "pex5"
Load "dri"
Load "dbe"
Load "record"
Load "xtrap"
Load "glx"
Load "speedo"
Load "type1"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "de"
Option "XkbVariant" "nodeadkeys"
EndSection

Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
# Option "Protocol" "Microsoft"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
# Option "Device" "/dev/ttyS0"
Option "Device" "/dev/input/mice"
EndSection

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 31.5 - 57.0
VertRefresh 50.0 - 90.0
EndSection

Section "Monitor"
Identifier "Monitor1"
VendorName "Siemens"
ModelName "MCM 171"
HorizSync 30.0 - 70.0
VertRefresh 50.0 - 150.0
EndSection

Section "Device"
Identifier "Card0"
Driver "fbdev"
VendorName "Trident"
BoardName "CyberBlade/DSTN/Ai1"
BusID "PCI:1:0:0"
EndSection

Section "Screen"
Identifier "Screen 0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Depth 16
EndSubSection
EndSection

Section "Screen"
Identifier "Screen 1"
Device "Card0"
Monitor "Monitor1"
SubSection "Display"
Depth 16
EndSubSection
EndSection

my log:

(II) LoadModule: "fb"
(II) Loading /usr/X11R6/lib/modules/libfb.a
(II) Module fb: vendor="The XFree86 Project"
compiled for 4.3.0, module version = 1.0.0
ABI class: XFree86 ANSI C Emulation, version 0.2
(**) FBDEV(0): Using "Shadow Framebuffer"
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"
(II) Loading /usr/X11R6/lib/modules/libshadow.a
(II) Module shadow: vendor="The XFree86 Project"
compiled for 4.3.0, module version = 1.0.0
ABI class: XFree86 ANSI C Emulation, version 0.2
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] 0 0 0x81000000 - 0x817fffff (0x800000) MX[B]
[1] 0 0 0x80100000 - 0x8011ffff (0x20000) MX[B]
[2] 0 0 0x80800000 - 0x80ffffff (0x800000) MX[B]
[3] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[4] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0x81c00000 - 0x81c00fff (0x1000) MX[B]
[9] -1 0 0x81a00000 - 0x81a00fff (0x1000) MX[B]
[10] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O
[11] -1 0 0x80120000 - 0x8012ffff (0x10000) MX[B](B)
[12] -1 0 0x81000000 - 0x817fffff (0x800000) MX[B](B)
[13] -1 0 0x80100000 - 0x8011ffff (0x20000) MX[B](B)
[14] -1 0 0x80800000 - 0x80ffffff (0x800000) MX[B](B)
[15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[20] -1 0 0x00007050 - 0x0000705f (0x10) IX[B]
[21] -1 0 0x00008000 - 0x000080ff (0x100) IX[B]
[22] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[23] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument
(==) FBDEV(0): Backing store disabled
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument
(EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument
(**) Option "Protocol" "IMPS/2"
(**) Mouse0: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse0: Core Pointer
(**) Option "Device" "/dev/input/mice"
(**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Mouse0: ZAxisMapping: buttons 4 and 5
(**) Mouse0: Buttons: 5
(II) Keyboard "Keyboard0" handled by legacy driver
(II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE)
(II) Mouse0: ps2EnableDataReporting: succeeded
GetModeLine - scrn: 0 clock: 78653
GetModeLine - hdsp: 1024 hbeg: 1056 hend: 1184 httl: 1312
vdsp: 768 vbeg: 772 vend: 776 vttl: 792 flags: 266


It still displays the same screen on both displays

any ideas?
_________________
----
error in operator: add beer

[scootersmk]

Not sure if this is still needed in the more current versions, but try adding this to your config:

[ollo]

Thank U

I tried it but xinerama still dosen't work.

I'm not sure but i've seen
"Xinerama" "On"
also in the forum.
What shall be used?

Anyway I tried this too with the same effect like the one above.

ollo

---
error in operator : add beer
_________________
----
error in operator: add beer

[brlewis]

"true" and "On" will basically mean the same thing. I always use "true", for what it is worth.

For your dual-head setup, I believe you need a second "device" section. Then your second screen needs to be setup with the second device. Here is my example:

http://www.brandonlewis.net/documents/ati/XF86Config

Have fun, dual-head can be a pain.
_________________
Let us vote to dunk the witch in the river Styx and photograph the lye.

[kurifu]

This might seem a little simple, but sometimes it is easily over looked by laptop users.

Most laptops will repeat the same information from the primary head on the adapter to the secondary head, or in other words show the same screen on both heads, much like you described.

Usually there is a function key, or BIOS setting, or something that allows you to force each head to act independantly of one another, it would be a good idea to check and make sure that is happening. You can also dmesg | less for possible clues as to what is going on, look for your framebuffer information if you have any. Some actually report information about connected devices, and how the heads should behave.