Re: Dual head howto?
Thanks very much, this really helped. You had some things that were not
in shown in the example in my XF86Config-4 file.
Best effort so far: My main monitor runs X, the cursor goes off the
screen to the left where I said the other monitor was, but the secondary
monitor shows blank/garbage. The good news is that it changes when I
change its config in XF86Config (named XF86Config-4 on debian). See the
end of this post for key sections of my config file, feedback welcome.
(The 2nd monitor apparently hates console mode, looks horrible even with
the framebuffer disabled.)
My config file is below, comments very welcome.
BTW: Regarding X and fb: As Hans Ekbrand said in a parallel thread, I
DON'T use fb and X at the same time; the matrox doc in
kernel-sources.../Documentation/fb makes it very clear that while X
might be able to use the framebuffer it certainly won't be accelerated
and hints at dire incompatibilities. I was never tempted. As shown
below, I use the "mga" driver for X windows. When I run X, no problems.
When I switch to a non-X console I get a nice looking smooth font that
has a much better resolution than 24x80.
TIA, Paul
#XF86Config-4, Monitor, Device, Screen & Layout section, comments
#omitted. Note that I usually run my Art Media (Trinitron clone) 17"
#monitor at 1152x864 with depth 24, I've stepped this back while trying
#to get the second monitor going as well. My Matrox G400 has 16 MB.
Section "Monitor"
Identifier "Monitor_0"
VendorName "Art Media"
ModelName "A-1701T"
HorizSync 30-70
VertRefresh 50-120
EndSection
Section "Monitor"
Identifier "Monitor_1"
VendorName "MicroScan"
ModelName "4 GP"
HorizSync 30-64
VertRefresh 50-100
EndSection
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Driver "vga"
EndSection
Section "Device"
Identifier "Matrox_0"
Driver "mga"
BusID "PCI:1:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Matrox_1"
Driver "mga"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Screen"
Identifier "Screen_0"
Device "Matrox_0"
Monitor "Monitor_0"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "640x480" "1152x864" "1024x768" "800x600"
ViewPort 0 0
EndSubsection
EndSection
Section "Screen"
Identifier "Screen 1"
Device "Matrox_1"
Monitor "Monitor_1"
DefaultDepth 16
Subsection "Display"
Depth 16
Modes "640x480" "800x600" "1024x768"
ViewPort 0 0
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Dual Layout"
Screen "Screen_0"
Screen "Screen_1" LeftOf "Screen_0"
InputDevice "Mouse_0" "CorePointer"
InputDevice "Keyboard_0" "CoreKeyboard"
EndSection
TIA,
Paul
--
Paul Mackinney
paul@mackinney.net
Simon Hepburn declaimed:
> Here are the important bits. *do not * use this, modify it. The bus id for
> your card may well be different. Remember you cannot use Xinerama and 3d
> accel together, choose one or the other.
>
> # XF86Config-4
>
> #Uncomment for Xinerama
> #Section "ServerFlags"
> # Option "Xinerama" "yes"
> #EndSection
>
> Section "InputDevice"
> Identifier "Keyboard_0"
> Driver "keyboard"
> Option "CoreKeyboard"
> Option "XkbRules" "xfree86"
> Option "XkbModel" "pc102"
> Option "XkbLayout" "gb"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse_0"
> Driver "mouse"
> Option "CorePointer"
> Option "Device" "/dev/psaux"
> Option "Protocol" "IMPS/2"
> Option "ZAxisMapping" "4 5"
> EndSection
>
>
> Section "Device"
> Identifier "Card_0"
> Driver "mga"
> VendorName "Matrox"
> BoardName "MGA G400 AGP"
> BusID "PCI:1:5:0"
> Screen 0
> EndSection
>
>
> Section "Device"
> Identifier "Card_1"
> Driver "mga"
> VendorName "Matrox"
> BoardName "MGA G400 AGP"
> BusID "PCI:1:5:0"
> Screen 1
> EndSection
>
> Section "Monitor"
> Identifier "Monitor_0"
> VendorName "Sony"
> ModelName "CPD-17F23"
> HorizSync 31.5-64
> VertRefresh 50-120
> EndSection
>
> Section "Monitor"
> Identifier "Monitor_1"
> VendorName "Packard-Bell"
> ModelName "PB8539VG"
> HorizSync 31.5
> VertRefresh 60-70
> EndSection
>
> Section "Screen"
> Identifier "Screen_0"
> Device "Card_0"
> Monitor "Monitor_0"
> DefaultDepth 16
> SubSection "Display"
> Depth 16
> Modes "1024x768"
> EndSubSection
> EndSection
>
> Section "Screen"
> Identifier "Screen_1"
> Device "Card_1"
> Monitor "Monitor_1"
> DefaultDepth 16
> SubSection "Display"
> Depth 16
> Modes "640x480"
> EndSubSection
> EndSection
>
> Section "ServerLayout"
> Identifier "Default Layout"
> Screen "Screen_0"
> Screen "Screen_1" RightOf "Screen_0"
> InputDevice "Keyboard_0"
> InputDevice "Mouse_0"
> EndSection
>
>
> # end of XF86Config
>
>
>
>
> Paul Mackinney wrote:
>
> > Hi,
> >
> > I have a 16 MB dual-head Matrox G400 and a spare 15" monitor, currently
> > running X at 1152x864 w/24 bit depth on my main 17" display. I'm having
> > trouble finding documentation for configuring the second head.
> >
> > I'm running Blackbox on Debian GNU/Linux with a custom kernel to support
> > the Matrox frame buffer, XFree86 Version 4.1.0.1 / X Window System. The
> > XF86Config-4 man page has some good examples for setting up multiple
> > "Monitor" and "Screen" sections, but I'm confused about how to tell it
> > to put the 17" Monitor on the primary head and the 15" Monitor on the
> > second head.
> >
> > Pointers to the right docs and/or specific configuration examples
> > appreciated. Here's the output from dmesg, which seems to indicate that
> > the second screen buffer is being allocated.
> >
> > matroxfb: Matrox G400 (AGP) detected
> > matroxfb: MTRR's turned on
> > matroxfb: 1024x768x8bpp (virtual: 1024x16380)
> > matroxfb: framebuffer at 0xD8000000, mapped to 0xce81f000, size 16777216
> > Console: switching to colour frame buffer device 128x48
> > fb0: MATROX VGA frame buffer device
> > .
> > .
> > .
> > i2c-core.o: adapter DDC:fb0 #0 on i2c-matroxfb registered as adapter 0.
> > i2c-core.o: adapter DDC:fb0 #1 on i2c-matroxfb registered as adapter 1.
> > i2c-core.o: adapter MAVEN:fb0 on i2c-matroxfb registered as adapter 2.
> > i2c-core.o: driver maven registered.
> > i2c-core.o: client [maven client] registered to adapter [MAVEN:fb0 on
> > i2c-matrox
> > fb](pos. 0).
> > matroxfb_crtc2: secondary head of fb0 was registered as fb1
> >
> > TIA,
> >
> > Paul
>
> --
> Simon Hepburn.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
--
Paul Mackinney | Another look at Sept 11
paul@mackinney.net | http://www.copvcia.com/
Reply to: